1 Changes in version 0.2.5.3-alpha - 2014-03-??
2 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
3 two new anti-DoS features for Tor relays, resolves a bug that kept
4 SOCKS5 support for IPv6 from working, fixes several annoying usability
5 issues for bridge users, and removes more old code for unused
8 The Tor 0.2.5.x release series is now in patch-freeze: no feature
9 patches not already written will be considered for inclusion in 0.2.5.x.
11 o Major features (relay security, DoS-resistance):
12 - When deciding whether we have run out of memory and we need to
13 close circuits, also consider memory allocated in buffers for
14 streams attached to each circuit.
16 This change, which extends an anti-DoS feature introduced in
17 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
18 better resist more memory-based DoS attacks than before. Since the
19 MaxMemInCellQueues option now applies to all queues, it is renamed
20 to MaxMemInQueues. This feature fixes bug 10169.
21 - Avoid hash-flooding denial-of-service attacks by using the secure
22 SipHash-2-4 hash function for our hashtables. Without this
23 feature, an attacker could degrade performance of a targeted
24 client or server by flooding their data structures with a large
25 number of entries to be stored at the same hash table position,
26 thereby slowing down the Tor instance. With this feature, hash
27 table positions are derived from a randomized cryptographic key,
28 and an attacker cannot predict which entries will collide. Closes
30 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
31 the default at 8GBytes), to better support Raspberry Pi users. Fixes
32 bug 9686; bugfix on 0.2.4.14-alpha.
34 o Minor features (bridges, pluggable transports):
35 - Bridges now write the SHA1 digest of their identity key
36 fingerprint (that is, a hash of a hash of their public key) to
37 notice-level logs, and to a new hashed-fingerprint file. This
38 information will help bridge operators look up their bridge in
39 Globe and similar tools. Resolves ticket 10884.
40 - Improve the message that Tor displays when running as a bridge
41 using pluggable transports without an Extended ORPort
42 listener. Also, log the message in the log file too. Resolves
44 - Stop giving annoying warning messages when we decide not to launch
45 a pluggable transport proxy that we don't need (because there are
46 no bridges configured to use it). Resolves ticket 5018; bugfix
49 o Minor features (other):
50 - Add a new option, PredictedPortsRelevanceTime, to control how long
51 after having received a request to connect to a given port Tor
52 will try to keep circuits ready in anticipation of future requests
53 for that port. Patch from "unixninja92"; implements ticket 9176.
54 - Generate a warning if any ports are listed in the SocksPolicy,
55 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
56 AuthDirBadExit options. (These options only support address
57 ranges.) Fixes part of ticket 11108.
58 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
61 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
62 - Build without warnings under clang 3.4. (We have some macros that
63 define static functions only some of which will get used later in
64 the module. Starting with clang 3.4, these give a warning unless
65 the unused attribute is set on them.) Resolves ticket 10904.
66 - Fix build warnings about missing "a2x" comment when building the
67 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
68 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
70 o Minor bugfixes (unit tests)
71 - Fix a small bug in the unit tests that might have made the tests
72 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
73 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
75 o Minor bugfixes (client):
76 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
77 generating incorrect SOCKS5 responses, and confusing client
78 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
79 - Raise a control port warning when we fail to connect to all of
80 our bridges. Previously, we didn't inform the controller, and
81 the bootstrap process would stall. Fixes bug 11069; bugfix on
83 - Exit immediately when a process-owning controller exits.
84 Previously, tor relays would wait for a little while after their
85 controller exited, as if they had gotten an INT signal -- but this
86 was problematic, since there was no feedback for the user. To do a
87 clean shutdown, controllers should send an INT signal and give Tor
88 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
89 - Improve the log message when we can't connect to a hidden service
90 because all of the hidden service directory nodes hosting its
91 descriptor are excluded. Improves on our fix for bug 10722, which
92 was a bugfix on 0.2.0.10-alpha.
93 - Stop attempting to connect to bridges before our pluggable
94 transports are configured (harmless but resulted in some erroneous
95 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
97 o Minor bugfixes (relays and bridges):
98 - Non-exit relays no longer launch mock DNS requests to check for
99 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
100 non-exit relays stopped servicing DNS requests. Fixes bug 965;
101 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
102 - Avoid crashing on a malformed resolv.conf file when running a
103 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
104 - Give the correct URL in the warning message when trying to run a
105 relay on an ancient version of Windows. Fixes bug 9393.
106 - Bridges now never collect statistics that were designed for
107 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
108 - Bridges now report complete directory request statistics. Related
109 to bug 5824; bugfix on 0.2.2.1-alpha.
111 o Minor bugfixes (backtrace support):
112 - Support automatic backtraces on more platforms by using the
113 "-fasynchronous-unwind-tables" compiler option. This option is
114 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
115 is on by default and table generation is not. This doesn't yet
116 add Windows support; only Linux, OSX, and some BSDs are affected.
117 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
118 - Avoid strange behavior if two threads hit failed assertions at the
119 same time and both try to log backtraces at once. (Previously, if
120 this had happened, both threads would have stored their intermediate
121 results in the same buffer, and generated junk outputs.) Reported by
122 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
123 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
124 0.2.5.2-alpha; patch from Nick Hopper.
127 - Remove all remaining code related to version-0 hidden service
128 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
129 the rest of bug 10841.
132 - Explain that SocksPolicy, DirPolicy, and similar options don't
133 take port arguments. Fixes the other part of ticket 11108.
134 - Fix the manpage's description of HiddenServiceAuthorizeClient:
135 the maximum client name length is 16, not 19. Fixes bug 11118;
136 bugfix on 0.2.1.6-alpha.
137 - Fix a comment about the rend_server_descriptor_t.protocols field
138 to more accurately describe its range. Also, make that field
139 unsigned, to more accurately reflect its usage. Fixes bug 9099;
140 bugfix on 0.2.1.5-alpha.
141 - Document in the manpage that "KBytes" may also be written as
142 "kilobytes" or "KB", that "Kbits" may also be written as
143 "kilobits", and so forth. Closes ticket 9222.
145 o Code simplifications and refactoring:
146 - Get rid of router->address, since in all cases it was just the
147 string representation of router->addr. Resolves ticket 5528.
149 o Test infrastructure:
150 - Update to the latest version of tinytest.
151 - Improve the tinytest implementation of string operation tests so
152 that comparisons with NULL strings no longer crash the tests; they
153 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
156 Changes in version 0.2.4.21 - 2014-02-28
157 Tor 0.2.4.21 further improves security against potential adversaries who
158 find breaking 1024-bit crypto doable, and backports several stability
159 and robustness patches from the 0.2.5 branch.
161 o Major features (client security):
162 - When we choose a path for a 3-hop circuit, make sure it contains
163 at least one relay that supports the NTor circuit extension
164 handshake. Otherwise, there is a chance that we're building
165 a circuit that's worth attacking by an adversary who finds
166 breaking 1024-bit crypto doable, and that chance changes the game
167 theory. Implements ticket 9777.
170 - Do not treat streams that fail with reason
171 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
172 since it could also indicate an ENETUNREACH connection error. Fixes
173 part of bug 10777; bugfix on 0.2.4.8-alpha.
175 o Code simplification and refactoring:
176 - Remove data structures which were introduced to implement the
177 CellStatistics option: they are now redundant with the new timestamp
178 field in the regular packed_cell_t data structure, which we did
179 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
182 - Always clear OpenSSL bignums before freeing them -- even bignums
183 that don't contain secrets. Resolves ticket 10793. Patch by
185 - Build without warnings under clang 3.4. (We have some macros that
186 define static functions only some of which will get used later in
187 the module. Starting with clang 3.4, these give a warning unless the
188 unused attribute is set on them.) Resolves ticket 10904.
189 - Update geoip and geoip6 files to the February 7 2014 Maxmind
190 GeoLite2 Country database.
193 - Set the listen() backlog limit to the largest actually supported
194 on the system, not to the value in a header file. Fixes bug 9716;
195 bugfix on every released Tor.
196 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
197 exit node as a NOROUTE error, not an INTERNAL error, since they
198 can apparently happen when trying to connect to the wrong sort
199 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
200 - Fix build warnings about missing "a2x" comment when building the
201 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
202 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
203 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
204 not entirely remove it from the connection lists. Fixes bug 9602;
205 bugfix on 0.2.4.4-alpha.
206 - Fix a segmentation fault in our benchmark code when running with
207 Fedora's OpenSSL package, or any other OpenSSL that provides
208 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
209 - Turn "circuit handshake stats since last time" log messages into a
210 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
212 o Documentation fixes:
213 - Document that all but one DirPort entry must have the NoAdvertise
214 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
217 Changes in version 0.2.5.2-alpha - 2014-02-13
218 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
219 like the "poor random number generation" fix and the "building too many
220 circuits" fix. It also further improves security against potential
221 adversaries who find breaking 1024-bit crypto doable, and launches
222 pluggable transports on demand (which gets us closer to integrating
223 pluggable transport support by default -- not to be confused with Tor
224 bundles enabling pluggable transports and bridges by default).
226 o Major features (client security):
227 - When we choose a path for a 3-hop circuit, make sure it contains
228 at least one relay that supports the NTor circuit extension
229 handshake. Otherwise, there is a chance that we're building
230 a circuit that's worth attacking by an adversary who finds
231 breaking 1024-bit crypto doable, and that chance changes the game
232 theory. Implements ticket 9777.
233 - Clients now look at the "usecreatefast" consensus parameter to
234 decide whether to use CREATE_FAST or CREATE cells for the first hop
235 of their circuit. This approach can improve security on connections
236 where Tor's circuit handshake is stronger than the available TLS
237 connection security levels, but the tradeoff is more computational
238 load on guard relays. Implements proposal 221. Resolves ticket 9386.
240 o Major features (bridges):
241 - Don't launch pluggable transport proxies if we don't have any
242 bridges configured that would use them. Now we can list many
243 pluggable transports, and Tor will dynamically start one when it
244 hears a bridge address that needs it. Resolves ticket 5018.
245 - The bridge directory authority now assigns status flags (Stable,
246 Guard, etc) to bridges based on thresholds calculated over all
247 Running bridges. Now bridgedb can finally make use of its features
248 to e.g. include at least one Stable bridge in its answers. Fixes
251 o Major features (other):
252 - Extend ORCONN controller event to include an "ID" parameter,
253 and add four new controller event types CONN_BW, CIRC_BW,
254 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
255 The new events are emitted in private Tor networks only, with the
256 goal of being able to better track performance and load during
257 full-network simulations. Implements proposal 218 and ticket 7359.
258 - On some platforms (currently: recent OSX versions, glibc-based
259 platforms that support the ELF format, and a few other
260 Unix-like operating systems), Tor can now dump stack traces
261 when a crash occurs or an assertion fails. By default, traces
262 are dumped to stderr (if possible) and to any logs that are
263 reporting errors. Implements ticket 9299.
266 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
267 not entirely remove it from the connection lists. Fixes bug 9602;
268 bugfix on 0.2.4.4-alpha.
269 - Do not treat streams that fail with reason
270 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
271 since it could also indicate an ENETUNREACH connection error. Fixes
272 part of bug 10777; bugfix on 0.2.4.8-alpha.
274 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
275 - Do not allow OpenSSL engines to replace the PRNG, even when
276 HardwareAccel is set. The only default builtin PRNG engine uses
277 the Intel RDRAND instruction to replace the entire PRNG, and
278 ignores all attempts to seed it with more entropy. That's
279 cryptographically stupid: the right response to a new alleged
280 entropy source is never to discard all previously used entropy
281 sources. Fixes bug 10402; works around behavior introduced in
282 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
284 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
285 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
286 - Avoid launching spurious extra circuits when a stream is pending.
287 This fixes a bug where any circuit that _wasn't_ unusable for new
288 streams would be treated as if it were, causing extra circuits to
289 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
291 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
292 - No longer stop reading or writing on cpuworker connections when
293 our rate limiting buckets go empty. Now we should handle circuit
294 handshake requests more promptly. Resolves bug 9731.
295 - Stop trying to bootstrap all our directory information from
296 only our first guard. Discovered while fixing bug 9946; bugfix
299 o Minor features (bridges, pluggable transports):
300 - Add threshold cutoffs to the networkstatus document created by
301 the Bridge Authority. Fixes bug 1117.
302 - On Windows, spawn background processes using the CREATE_NO_WINDOW
303 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
304 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
305 Vidalia set this option for us.) Implements ticket 10297.
307 o Minor features (security):
308 - Always clear OpenSSL bignums before freeing them -- even bignums
309 that don't contain secrets. Resolves ticket 10793. Patch by
312 o Minor features (config options and command line):
313 - Add an --allow-missing-torrc commandline option that tells Tor to
314 run even if the configuration file specified by -f is not available.
315 Implements ticket 10060.
316 - Add support for the TPROXY transparent proxying facility on Linux.
317 See documentation for the new TransProxyType option for more
318 details. Implementation by "thomo". Closes ticket 10582.
320 o Minor features (controller):
321 - Add a new "HS_DESC" controller event that reports activities
322 related to hidden service descriptors. Resolves ticket 8510.
323 - New "DROPGUARDS" controller command to forget all current entry
324 guards. Not recommended for ordinary use, since replacing guards
325 too frequently makes several attacks easier. Resolves ticket 9934;
328 o Minor features (build):
329 - Assume that a user using ./configure --host wants to cross-compile,
330 and give an error if we cannot find a properly named
331 tool-chain. Add a --disable-tool-name-check option to proceed
332 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
333 - If we run ./configure and the compiler recognizes -fstack-protector
334 but the linker rejects it, warn the user about a potentially missing
335 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
337 o Minor features (testing):
338 - If Python is installed, "make check" now runs extra tests beyond
339 the unit test scripts.
340 - When bootstrapping a test network, sometimes very few relays get
341 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
342 specify a set of relays which should be voted Guard regardless of
343 their uptime or bandwidth. Addresses ticket 9206.
345 o Minor features (log messages):
346 - When ServerTransportPlugin is set on a bridge, Tor can write more
347 useful statistics about bridge use in its extrainfo descriptors,
348 but only if the Extended ORPort ("ExtORPort") is set too. Add a
349 log message to inform the user in this case. Resolves ticket 9651.
350 - When receiving a new controller connection, log the origin address.
351 Resolves ticket 9698; patch from "sigpipe".
352 - When logging OpenSSL engine status at startup, log the status of
353 more engines. Fixes ticket 10043; patch from Joshua Datko.
354 - Turn "circuit handshake stats since last time" log messages into a
355 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
357 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
358 - Improve the circuit queue out-of-memory handler. Previously, when
359 we ran low on memory, we'd close whichever circuits had the most
360 queued cells. Now, we close those that have the *oldest* queued
361 cells, on the theory that those are most responsible for us
362 running low on memory. Based on analysis from a forthcoming paper
363 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
364 - Generate bootstrapping status update events correctly when fetching
365 microdescriptors. Fixes bug 9927.
366 - Update to the October 2 2013 Maxmind GeoLite Country database.
368 o Minor bugfixes (clients):
369 - When closing a channel that has already been open, do not close
370 pending circuits that were waiting to connect to the same relay.
371 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
374 o Minor bugfixes (relays):
375 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
376 exit node as a NOROUTE error, not an INTERNAL error, since they
377 can apparently happen when trying to connect to the wrong sort
378 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
380 o Minor bugfixes (bridges):
381 - Fix a bug where the first connection works to a bridge that uses a
382 pluggable transport with client-side parameters, but we don't send
383 the client-side parameters on subsequent connections. (We don't
384 use any pluggable transports with client-side parameters yet,
385 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
386 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
388 o Minor bugfixes (node selection):
389 - If ExcludeNodes is set, consider non-excluded hidden service
390 directory servers before excluded ones. Do not consider excluded
391 hidden service directory servers at all if StrictNodes is
392 set. (Previously, we would sometimes decide to connect to those
393 servers, and then realize before we initiated a connection that
394 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
396 - If we set the ExitNodes option but it doesn't include any nodes
397 that have the Exit flag, we would choose not to bootstrap. Now we
398 bootstrap so long as ExitNodes includes nodes which can exit to
399 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
401 o Minor bugfixes (controller and command-line):
402 - If changing a config option via "setconf" fails in a recoverable
403 way, we used to nonetheless write our new control ports to the
404 file described by the "ControlPortWriteToFile" option. Now we only
405 write out that file if we successfully switch to the new config
406 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
407 - When a command-line option such as --version or --help that
408 ordinarily implies --hush appears on the command line along with
409 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
410 only if it appeared later on the command line. Fixes bug 9578;
411 bugfix on 0.2.5.1-alpha.
413 o Minor bugfixes (code correctness):
414 - Previously we used two temporary files when writing descriptors to
415 disk; now we only use one. Fixes bug 1376.
416 - Remove an erroneous (but impossible and thus harmless) pointer
417 comparison that would have allowed compilers to skip a bounds
418 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
419 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
420 - Fix an always-true assertion in pluggable transports code so it
421 actually checks what it was trying to check. Fixes bug 10046;
422 bugfix on 0.2.3.9-alpha. Found by "dcb".
424 o Minor bugfixes (protocol correctness):
425 - When receiving a VERSIONS cell with an odd number of bytes, close
426 the connection immediately since the cell is malformed. Fixes bug
427 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
430 o Minor bugfixes (build):
431 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
432 turned off (that is, without support for v2 link handshakes). Fixes
433 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
434 - Fix compilation warnings and startup issues when running with
435 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
437 - Fix compilation on Solaris 9, which didn't like us having an
438 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
440 o Minor bugfixes (testing):
441 - Fix a segmentation fault in our benchmark code when running with
442 Fedora's OpenSSL package, or any other OpenSSL that provides
443 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
445 o Minor bugfixes (log messages):
446 - Fix a bug where clients using bridges would report themselves
447 as 50% bootstrapped even without a live consensus document.
448 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
449 - Suppress a warning where, if there's only one directory authority
450 in the network, we would complain that votes and signatures cannot
451 be uploaded to other directory authorities. Fixes bug 10842;
452 bugfix on 0.2.2.26-beta.
453 - Report bootstrapping progress correctly when we're downloading
454 microdescriptors. We had updated our "do we have enough microdescs
455 to begin building circuits?" logic most recently in 0.2.4.10-alpha
456 (see bug 5956), but we left the bootstrap status event logic at
457 "how far through getting 1/4 of them are we?" Fixes bug 9958;
458 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
460 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
461 - Avoid a crash bug when starting with a corrupted microdescriptor
462 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
463 - If we fail to dump a previously cached microdescriptor to disk, avoid
464 freeing duplicate data later on. Fixes bug 10423; bugfix on
465 0.2.4.13-alpha. Spotted by "bobnomnom".
467 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
468 - Correctly log long IPv6 exit policies, instead of truncating them
469 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
470 - Our default TLS ecdhe groups were backwards: we meant to be using
471 P224 for relays (for performance win) and P256 for bridges (since
472 it is more common in the wild). Instead we had it backwards. After
473 reconsideration, we decided that the default should be P256 on all
474 hosts, since its security is probably better, and since P224 is
475 reportedly used quite little in the wild. Found by "skruffy" on
476 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
477 - Free directory authority certificate download statuses on exit
478 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
480 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
481 - If the guard we choose first doesn't answer, we would try the
482 second guard, but once we connected to the second guard we would
483 abandon it and retry the first one, slowing down bootstrapping.
484 The fix is to treat all our initially chosen guards as acceptable
485 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
486 - Fix an assertion failure that would occur when disabling the
487 ORPort setting on a running Tor process while accounting was
488 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
489 - When examining the list of network interfaces to find our address,
490 do not consider non-running or disabled network interfaces. Fixes
491 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
492 - Avoid an off-by-one error when checking buffer boundaries when
493 formatting the exit status of a pluggable transport helper.
494 This is probably not an exploitable bug, but better safe than
495 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
498 o Removed code and features:
499 - Clients now reject any directory authority certificates lacking
500 a dir-key-crosscert element. These have been included since
501 0.2.1.9-alpha, so there's no real reason for them to be optional
502 any longer. Completes proposal 157. Resolves ticket 10162.
503 - Remove all code that existed to support the v2 directory system,
504 since there are no longer any v2 directory authorities. Resolves
506 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
507 options, which were used for designating authorities as "Hidden
508 service authorities". There has been no use of hidden service
509 authorities since 0.2.2.1-alpha, when we stopped uploading or
510 downloading v0 hidden service descriptors. Fixes bug 10881; also
511 part of a fix for bug 10841.
513 o Code simplification and refactoring:
514 - Remove some old fallback code designed to keep Tor clients working
515 in a network with only two working relays. Elsewhere in the code we
516 have long since stopped supporting such networks, so there wasn't
517 much point in keeping it around. Addresses ticket 9926.
518 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
519 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
520 - Remove data structures which were introduced to implement the
521 CellStatistics option: they are now redundant with the addition
522 of a timestamp to the regular packed_cell_t data structure, which
523 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
526 o Documentation (man page) fixes:
527 - Update manpage to describe some of the files you can expect to
528 find in Tor's DataDirectory. Addresses ticket 9839.
529 - Document that all but one DirPort entry must have the NoAdvertise
530 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
532 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
533 - Clarify the usage and risks of setting the ContactInfo torrc line
534 for your relay or bridge. Resolves ticket 9854.
535 - Add anchors to the manpage so we can link to the html version of
536 the documentation for specific options. Resolves ticket 9866.
537 - Replace remaining references to DirServer in man page and
538 log entries. Resolves ticket 10124.
541 - Make the "tor-gencert" tool used by directory authority operators
542 create 2048-bit signing keys by default (rather than 1024-bit, since
543 1024-bit is uncomfortably small these days). Addresses ticket 10324.
546 Changes in version 0.2.4.20 - 2013-12-22
547 Tor 0.2.4.20 fixes potentially poor random number generation for users
548 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
549 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
550 and 4) have no state file in their DataDirectory (as would happen on
551 first start). Users who generated relay or hidden service identity
552 keys in such a situation should discard them and generate new ones.
554 This release also fixes a logic error that caused Tor clients to build
555 many more preemptive circuits than they actually need.
558 - Do not allow OpenSSL engines to replace the PRNG, even when
559 HardwareAccel is set. The only default builtin PRNG engine uses
560 the Intel RDRAND instruction to replace the entire PRNG, and
561 ignores all attempts to seed it with more entropy. That's
562 cryptographically stupid: the right response to a new alleged
563 entropy source is never to discard all previously used entropy
564 sources. Fixes bug 10402; works around behavior introduced in
565 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
567 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
568 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
569 - Avoid launching spurious extra circuits when a stream is pending.
570 This fixes a bug where any circuit that _wasn't_ unusable for new
571 streams would be treated as if it were, causing extra circuits to
572 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
575 - Avoid a crash bug when starting with a corrupted microdescriptor
576 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
577 - If we fail to dump a previously cached microdescriptor to disk, avoid
578 freeing duplicate data later on. Fixes bug 10423; bugfix on
579 0.2.4.13-alpha. Spotted by "bobnomnom".
582 Changes in version 0.2.4.19 - 2013-12-11
583 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
584 (1986-2013). Aaron worked on diverse projects including helping to guide
585 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
586 transparency to the U.S government's PACER documents, and contributing
587 design and development for Tor and Tor2Web. Aaron was one of the latest
588 martyrs in our collective fight for civil liberties and human rights,
589 and his death is all the more painful because he was one of us.
591 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
592 a new circuit handshake and link encryption that use ECC to provide
593 better security and efficiency; makes relays better manage circuit
594 creation requests; uses "directory guards" to reduce client enumeration
595 risks; makes bridges collect and report statistics about the pluggable
596 transports they support; cleans up and improves our geoip database;
597 gets much closer to IPv6 support for clients, bridges, and relays; makes
598 directory authorities use measured bandwidths rather than advertised
599 ones when computing flags and thresholds; disables client-side DNS
600 caching to reduce tracking risks; and fixes a big bug in bridge
601 reachability testing. This release introduces two new design
602 abstractions in the code: a new "channel" abstraction between circuits
603 and or_connections to allow for implementing alternate relay-to-relay
604 transports, and a new "circuitmux" abstraction storing the queue of
605 circuits for a channel. The release also includes many stability,
606 security, and privacy fixes.
609 Changes in version 0.2.4.18-rc - 2013-11-16
610 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
611 series. It takes a variety of fixes from the 0.2.5.x branch to improve
612 stability, performance, and better handling of edge cases.
615 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
616 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
617 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
618 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
619 them to solve bug 6033.)
622 - No longer stop reading or writing on cpuworker connections when
623 our rate limiting buckets go empty. Now we should handle circuit
624 handshake requests more promptly. Resolves bug 9731.
625 - If we are unable to save a microdescriptor to the journal, do not
626 drop it from memory and then reattempt downloading it. Fixes bug
627 9645; bugfix on 0.2.2.6-alpha.
628 - Stop trying to bootstrap all our directory information from
629 only our first guard. Discovered while fixing bug 9946; bugfix
631 - The new channel code sometimes lost track of in-progress circuits,
632 causing long-running clients to stop building new circuits. The
633 fix is to always call circuit_n_chan_done(chan, 0) from
634 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
636 o Minor bugfixes (on 0.2.4.x):
637 - Correctly log long IPv6 exit policies, instead of truncating them
638 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
639 - Our default TLS ecdhe groups were backwards: we meant to be using
640 P224 for relays (for performance win) and P256 for bridges (since
641 it is more common in the wild). Instead we had it backwards. After
642 reconsideration, we decided that the default should be P256 on all
643 hosts, since its security is probably better, and since P224 is
644 reportedly used quite little in the wild. Found by "skruffy" on
645 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
646 - Free directory authority certificate download statuses on exit
647 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
649 o Minor bugfixes (on 0.2.3.x and earlier):
650 - If the guard we choose first doesn't answer, we would try the
651 second guard, but once we connected to the second guard we would
652 abandon it and retry the first one, slowing down bootstrapping.
653 The fix is to treat all our initially chosen guards as acceptable
654 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
655 - Fix an assertion failure that would occur when disabling the
656 ORPort setting on a running Tor process while accounting was
657 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
658 - When examining the list of network interfaces to find our address,
659 do not consider non-running or disabled network interfaces. Fixes
660 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
661 - Avoid an off-by-one error when checking buffer boundaries when
662 formatting the exit status of a pluggable transport helper.
663 This is probably not an exploitable bug, but better safe than
664 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
667 o Minor features (protecting client timestamps):
668 - Clients no longer send timestamps in their NETINFO cells. These were
669 not used for anything, and they provided one small way for clients
670 to be distinguished from each other as they moved from network to
671 network or behind NAT. Implements part of proposal 222.
672 - Clients now round timestamps in INTRODUCE cells down to the nearest
673 10 minutes. If a new Support022HiddenServices option is set to 0, or
674 if it's set to "auto" and the feature is disabled in the consensus,
675 the timestamp is sent as 0 instead. Implements part of proposal 222.
676 - Stop sending timestamps in AUTHENTICATE cells. This is not such
677 a big deal from a security point of view, but it achieves no actual
678 good purpose, and isn't needed. Implements part of proposal 222.
679 - Reduce down accuracy of timestamps in hidden service descriptors.
680 Implements part of proposal 222.
682 o Minor features (other):
683 - Improve the circuit queue out-of-memory handler. Previously, when
684 we ran low on memory, we'd close whichever circuits had the most
685 queued cells. Now, we close those that have the *oldest* queued
686 cells, on the theory that those are most responsible for us
687 running low on memory. Based on analysis from a forthcoming paper
688 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
689 - Generate bootstrapping status update events correctly when fetching
690 microdescriptors. Fixes bug 9927.
691 - Update to the October 2 2013 Maxmind GeoLite Country database.
693 o Documentation fixes:
694 - Clarify the usage and risks of setting the ContactInfo torrc line
695 for your relay or bridge. Resolves ticket 9854.
696 - Add anchors to the manpage so we can link to the html version of
697 the documentation for specific options. Resolves ticket 9866.
698 - Replace remaining references to DirServer in man page and
699 log entries. Resolves ticket 10124.
702 Changes in version 0.2.5.1-alpha - 2013-10-02
703 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
704 on Linux, allows bridges that offer pluggable transports to report usage
705 statistics, fixes many issues to make testing easier, and provides
706 a pile of minor features and bugfixes that have been waiting for a
707 release of the new branch.
709 This is the first alpha release in a new series, so expect there to
710 be bugs. Users who would rather test out a more stable branch should
711 stay with 0.2.4.x for now.
713 o Major features (security):
714 - Use the seccomp2 syscall filtering facility on Linux to limit
715 which system calls Tor can invoke. This is an experimental,
716 Linux-only feature to provide defense-in-depth against unknown
717 attacks. To try turning it on, set "Sandbox 1" in your torrc
718 file. Please be ready to report bugs. We hope to add support
719 for better sandboxing in the future, including more fine-grained
720 filters, better division of responsibility, and support for more
721 platforms. This work has been done by Cristian-Matei Toader for
722 Google Summer of Code.
723 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
724 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
725 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
726 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
727 them to solve bug 6033.)
729 o Major features (other):
730 - Add support for passing arguments to managed pluggable transport
731 proxies. Implements ticket 3594.
732 - Bridges now track GeoIP information and the number of their users
733 even when pluggable transports are in use, and report usage
734 statistics in their extra-info descriptors. Resolves tickets 4773
736 - Make testing Tor networks bootstrap better: lower directory fetch
737 retry schedules and maximum interval without directory requests,
738 and raise maximum download tries. Implements ticket 6752.
739 - Add make target 'test-network' to run tests on a Chutney network.
740 Implements ticket 8530.
741 - The ntor handshake is now on-by-default, no matter what the
742 directory authorities recommend. Implements ticket 8561.
745 - Instead of writing destroy cells directly to outgoing connection
746 buffers, queue them and intersperse them with other outgoing cells.
747 This can prevent a set of resource starvation conditions where too
748 many pending destroy cells prevent data cells from actually getting
749 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
750 bugfix on 0.2.0.1-alpha.
751 - If we are unable to save a microdescriptor to the journal, do not
752 drop it from memory and then reattempt downloading it. Fixes bug
753 9645; bugfix on 0.2.2.6-alpha.
754 - The new channel code sometimes lost track of in-progress circuits,
755 causing long-running clients to stop building new circuits. The
756 fix is to always call circuit_n_chan_done(chan, 0) from
757 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
760 - Tor now builds each source file in two modes: a mode that avoids
761 exposing identifiers needlessly, and another mode that exposes
762 more identifiers for testing. This lets the compiler do better at
763 optimizing the production code, while enabling us to take more
764 radical measures to let the unit tests test things.
765 - The production builds no longer include functions used only in
766 the unit tests; all functions exposed from a module only for
767 unit-testing are now static in production builds.
768 - Add an --enable-coverage configuration option to make the unit
769 tests (and a new src/or/tor-cov target) to build with gcov test
773 - We now have rudimentary function mocking support that our unit
774 tests can use to test functions in isolation. Function mocking
775 lets the tests temporarily replace a function's dependencies with
776 stub functions, so that the tests can check the function without
777 invoking the other functions it calls.
778 - Add more unit tests for the <circid,channel>->circuit map, and
779 the destroy-cell-tracking code to fix bug 7912.
780 - Unit tests for failing cases of the TAP onion handshake.
781 - More unit tests for address-manipulation functions.
783 o Minor features (protecting client timestamps):
784 - Clients no longer send timestamps in their NETINFO cells. These were
785 not used for anything, and they provided one small way for clients
786 to be distinguished from each other as they moved from network to
787 network or behind NAT. Implements part of proposal 222.
788 - Clients now round timestamps in INTRODUCE cells down to the nearest
789 10 minutes. If a new Support022HiddenServices option is set to 0, or
790 if it's set to "auto" and the feature is disabled in the consensus,
791 the timestamp is sent as 0 instead. Implements part of proposal 222.
792 - Stop sending timestamps in AUTHENTICATE cells. This is not such
793 a big deal from a security point of view, but it achieves no actual
794 good purpose, and isn't needed. Implements part of proposal 222.
795 - Reduce down accuracy of timestamps in hidden service descriptors.
796 Implements part of proposal 222.
798 o Minor features (config options):
799 - Config (torrc) lines now handle fingerprints which are missing
800 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
801 - Support a --dump-config option to print some or all of the
802 configured options. Mainly useful for debugging the command-line
803 option parsing code. Helps resolve ticket 4647.
804 - Raise awareness of safer logging: notify user of potentially
805 unsafe config options, like logging more verbosely than severity
806 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
807 - Add a new configuration option TestingV3AuthVotingStartOffset
808 that bootstraps a network faster by changing the timing for
809 consensus votes. Addresses ticket 8532.
810 - Add a new torrc option "ServerTransportOptions" that allows
811 bridge operators to pass configuration parameters to their
812 pluggable transports. Resolves ticket 8929.
813 - The config (torrc) file now accepts bandwidth and space limits in
814 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
815 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
818 o Minor features (build):
819 - Add support for `--library-versions` flag. Implements ticket 6384.
820 - Return the "unexpected sendme" warnings to a warn severity, but make
821 them rate limited, to help diagnose ticket 8093.
822 - Detect a missing asciidoc, and warn the user about it, during
823 configure rather than at build time. Fixes issue 6506. Patch from
826 o Minor features (other):
827 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
828 sockets in a single system call. Implements ticket 5129.
829 - Log current accounting state (bytes sent and received + remaining
830 time for the current accounting period) in the relay's heartbeat
831 message. Implements ticket 5526; patch from Peter Retzlaff.
832 - Implement the TRANSPORT_LAUNCHED control port event that
833 notifies controllers about new launched pluggable
834 transports. Resolves ticket 5609.
835 - If we're using the pure-C 32-bit curve25519_donna implementation
836 of curve25519, build it with the -fomit-frame-pointer option to
837 make it go faster on register-starved hosts. This improves our
838 handshake performance by about 6% on i386 hosts without nacl.
840 - Update to the September 4 2013 Maxmind GeoLite Country database.
843 - Set the listen() backlog limit to the largest actually supported
844 on the system, not to the value in a header file. Fixes bug 9716;
845 bugfix on every released Tor.
846 - No longer accept malformed http headers when parsing urls from
847 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
849 - In munge_extrainfo_into_routerinfo(), check the return value of
850 memchr(). This would have been a serious issue if we ever passed
851 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
853 - On the chance that somebody manages to build Tor on a
854 platform where time_t is unsigned, correct the way that
855 microdesc_add_to_cache() handles negative time arguments.
856 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
857 - Reject relative control socket paths and emit a warning. Previously,
858 single-component control socket paths would be rejected, but Tor
859 would not log why it could not validate the config. Fixes bug 9258;
860 bugfix on 0.2.3.16-alpha.
862 o Minor bugfixes (command line):
863 - Use a single command-line parser for parsing torrc options on the
864 command line and for finding special command-line options to avoid
865 inconsistent behavior for torrc option arguments that have the same
866 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
868 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
869 9573; bugfix on 0.0.9pre5.
871 o Minor fixes (build, auxiliary programs):
872 - Stop preprocessing the "torify" script with autoconf, since
873 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
875 - The tor-fw-helper program now follows the standard convention and
876 exits with status code "0" on success. Fixes bug 9030; bugfix on
877 0.2.3.1-alpha. Patch by Arlo Breault.
878 - Corrected ./configure advice for what openssl dev package you should
879 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
881 o Minor code improvements:
882 - Remove constants and tests for PKCS1 padding; it's insecure and
883 shouldn't be used for anything new. Fixes bug 8792; patch
885 - Remove instances of strcpy() from the unit tests. They weren't
886 hurting anything, since they were only in the unit tests, but it's
887 embarassing to have strcpy() in the code at all, and some analysis
888 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
889 0.2.3.8-alpha. Patch from Arlo Breault.
892 - Remove migration code from when we renamed the "cached-routers"
893 file to "cached-descriptors" back in 0.2.0.8-alpha. This
894 incidentally resolves ticket 6502 by cleaning up the related code
895 a bit. Patch from Akshay Hebbar.
897 o Code simplification and refactoring:
898 - Extract the common duplicated code for creating a subdirectory
899 of the data directory and writing to a file in it. Fixes ticket
900 4282; patch from Peter Retzlaff.
901 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
902 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
903 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
904 - Add a set of accessor functions for the circuit timeout data
905 structure. Fixes ticket 6153; patch from "piet".
906 - Clean up exit paths from connection_listener_new(). Closes ticket
907 8789. Patch from Arlo Breault.
908 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
909 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
910 - Use a doubly-linked list to implement the global circuit list.
911 Resolves ticket 9108. Patch from Marek Majkowski.
912 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
915 Changes in version 0.2.4.17-rc - 2013-09-05
916 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
917 series. It adds an emergency step to help us tolerate the massive
918 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
919 circuit-level handshakes now effectively jump the queue compared to
920 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
921 big bug hindering bridge reachability tests.
924 - Relays now process the new "NTor" circuit-level handshake requests
925 with higher priority than the old "TAP" circuit-level handshake
926 requests. We still process some TAP requests to not totally starve
927 0.2.3 clients when NTor becomes popular. A new consensus parameter
928 "NumNTorsPerTAP" lets us tune the balance later if we need to.
929 Implements ticket 9574.
932 - If the circuit build timeout logic is disabled (via the consensus,
933 or because we are an authority), then don't build testing circuits.
934 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
935 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
936 previously they did not, which prevented them from receiving
937 successful connections from relays for self-test or bandwidth
938 testing. Also, when a relay is extending a circuit to a bridge,
939 it needs to send a NETINFO cell, even when the bridge hasn't sent
940 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
941 - If the time to download the next old-style networkstatus is in
942 the future, do not decline to consider whether to download the
943 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
947 - Avoid double-closing the listener socket in our socketpair()
948 replacement (used on Windows) in the case where the addresses on
949 our opened sockets don't match what we expected. Fixes bug 9400;
950 bugfix on 0.0.2pre7. Found by Coverity.
952 o Minor fixes (config options):
953 - Avoid overflows when the user sets MaxCircuitDirtiness to a
954 ridiculously high value, by imposing a (ridiculously high) 30-day
955 maximum on MaxCircuitDirtiness.
956 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
957 message is logged at notice, not at info.
958 - Warn and fail if a server is configured not to advertise any
959 ORPorts at all. (We need *something* to put in our descriptor,
960 or we just won't work.)
963 - Track how many "TAP" and "NTor" circuit handshake requests we get,
964 and how many we complete, and log it every hour to help relay
965 operators follow trends in network load. Addresses ticket 9658.
966 - Update to the August 7 2013 Maxmind GeoLite Country database.
969 Changes in version 0.2.4.16-rc - 2013-08-10
970 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
971 series. It fixes several crash bugs in the 0.2.4 branch.
974 - Fix a bug in the voting algorithm that could yield incorrect results
975 when a non-naming authority declared too many flags. Fixes bug 9200;
976 bugfix on 0.2.0.3-alpha.
977 - Fix an uninitialized read that could in some cases lead to a remote
978 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
979 Anybody running a hidden service on the experimental 0.2.4.x
980 branch should upgrade. (This is, so far as we know, unrelated to
982 - Avoid an assertion failure when processing DNS replies without the
983 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
984 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
985 0.2.4.15-rc. Found by stem integration tests.
988 - Fix an invalid memory read that occured when a pluggable
989 transport proxy failed its configuration protocol.
990 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
991 - When evaluating whether to use a connection that we haven't
992 decided is canonical using a recent link protocol version,
993 decide that it's canonical only if it used address _does_
994 match the desired address. Fixes bug 9309; bugfix on
995 0.2.4.4-alpha. Reported by skruffy.
996 - Make the default behavior of NumDirectoryGuards be to track
997 NumEntryGuards. Now a user who changes only NumEntryGuards will get
998 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
999 - Fix a spurious compilation warning with some older versions of
1000 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
1003 - Update to the July 3 2013 Maxmind GeoLite Country database.
1006 Changes in version 0.2.4.15-rc - 2013-07-01
1007 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
1008 series. It fixes a few smaller bugs, but generally appears stable.
1009 Please test it and let us know whether it is!
1012 - When receiving a new configuration file via the control port's
1013 LOADCONF command, do not treat the defaults file as absent.
1014 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
1017 - Issue a warning when running with the bufferevents backend enabled.
1018 It's still not stable, and people should know that they're likely
1019 to hit unexpected problems. Closes ticket 9147.
1022 Changes in version 0.2.4.14-alpha - 2013-06-18
1023 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
1024 present in 0.2.4.13-alpha.
1027 - When we have too much memory queued in circuits (according to a new
1028 MaxMemInCellQueues option), close the circuits consuming the most
1029 memory. This prevents us from running out of memory as a relay if
1030 circuits fill up faster than they can be drained. Fixes bug 9063;
1031 bugfix on the 54th commit of Tor. This bug is a further fix beyond
1032 bug 6252, whose fix was merged into 0.2.3.21-rc.
1034 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
1035 where we tried to solve this issue simply by imposing an upper limit
1036 on the number of queued cells for a single circuit. That approach
1037 proved to be problematic, since there are ways to provoke clients to
1038 send a number of cells in excess of any such reasonable limit. Fixes
1039 bug 9072; bugfix on 0.2.4.13-alpha.
1041 - Limit hidden service descriptors to at most ten introduction
1042 points, to slow one kind of guard enumeration. Fixes bug 9002;
1043 bugfix on 0.1.1.11-alpha.
1046 Changes in version 0.2.4.13-alpha - 2013-06-14
1047 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
1048 vulnerabilities, makes socks5 username/password circuit isolation
1049 actually actually work (this time for sure!), and cleans up a bunch
1050 of other issues in preparation for a release candidate.
1052 o Major bugfixes (robustness):
1053 - Close any circuit that has too many cells queued on it. Fixes
1054 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
1055 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
1056 - Prevent the get_freelists() function from running off the end of
1057 the list of freelists if it somehow gets an unrecognized
1058 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
1060 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
1061 when an exit connection with optimistic data succeeds immediately
1062 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
1064 - Fix a directory authority crash bug when building a consensus
1065 using an older consensus as its basis. Fixes bug 8833. Bugfix
1069 - Avoid a memory leak where we would leak a consensus body when we
1070 find that a consensus which we couldn't previously verify due to
1071 missing certificates is now verifiable. Fixes bug 8719; bugfix
1073 - We used to always request authority certificates by identity digest,
1074 meaning we'd get the newest one even when we wanted one with a
1075 different signing key. Then we would complain about being given
1076 a certificate we already had, and never get the one we really
1077 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
1078 resource to request the one we want. Fixes bug 5595; bugfix on
1080 - Follow the socks5 protocol when offering username/password
1081 authentication. The fix for bug 8117 exposed this bug, and it
1082 turns out real-world applications like Pidgin do care. Bugfix on
1083 0.2.3.2-alpha; fixes bug 8879.
1084 - Prevent failures on Windows Vista and later when rebuilding the
1085 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
1086 bugfix on 0.2.4.12-alpha.
1089 - Fix an impossible buffer overrun in the AES unit tests. Fixes
1090 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
1091 - If for some reason we fail to write a microdescriptor while
1092 rebuilding the cache, do not let the annotations from that
1093 microdescriptor linger in the cache file, and do not let the
1094 microdescriptor stay recorded as present in its old location.
1095 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
1096 - Fix a memory leak that would occur whenever a configuration
1097 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
1098 - Paste the description for PathBias parameters from the man
1099 page into or.h, so the code documents them too. Fixes bug 7982;
1100 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
1101 - Relays now treat a changed IPv6 ORPort as sufficient reason to
1102 publish an updated descriptor. Fixes bug 6026; bugfix on
1104 - When launching a resolve request on behalf of an AF_UNIX control
1105 socket, omit the address field of the new entry connection, used in
1106 subsequent controller events, rather than letting tor_dup_addr()
1107 set it to "<unknown address type>". Fixes bug 8639; bugfix on
1110 o Minor bugfixes (log messages):
1111 - Fix a scaling issue in the path bias accounting code that
1112 resulted in "Bug:" log messages from either
1113 pathbias_scale_close_rates() or pathbias_count_build_success().
1114 This represents a bugfix on a previous bugfix: the original fix
1115 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
1117 - Give a less useless error message when the user asks for an IPv4
1118 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
1122 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
1123 to tolerate bug 8093 for now.
1124 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
1125 in directory authority votes to describe whether they have enough
1126 measured bandwidths to ignore advertised (relay descriptor)
1127 bandwidth claims. Resolves ticket 8711.
1128 - Update to the June 5 2013 Maxmind GeoLite Country database.
1130 o Removed documentation:
1131 - Remove some of the older contents of doc/ as obsolete; move others
1132 to torspec.git. Fixes bug 8965.
1134 o Code simplification and refactoring:
1135 - Avoid using character buffers when constructing most directory
1136 objects: this approach was unwieldy and error-prone. Instead,
1137 build smartlists of strings, and concatenate them when done.
1140 Changes in version 0.2.4.12-alpha - 2013-04-18
1141 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
1142 process for lengthening the guard rotation period, makes directory
1143 authority opinions in the consensus a bit less gameable, makes socks5
1144 username/password circuit isolation actually work, and fixes a wide
1145 variety of other issues.
1148 - Raise the default time that a client keeps an entry guard from
1149 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
1150 2012 paper. (We would make it even longer, but we need better client
1151 load balancing first.) Also, make the guard lifetime controllable
1152 via a new GuardLifetime torrc option and a GuardLifetime consensus
1153 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
1154 - Directory authorities now prefer using measured bandwidths to
1155 advertised ones when computing flags and thresholds. Resolves
1157 - Directory authorities that have more than a threshold number
1158 of relays with measured bandwidths now treat relays with unmeasured
1159 bandwidths as having bandwidth 0. Resolves ticket 8435.
1161 o Major bugfixes (assert / resource use):
1162 - Avoid a bug where our response to TLS renegotiation under certain
1163 network conditions could lead to a busy-loop, with 100% CPU
1164 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
1165 - Avoid an assertion when we discover that we'd like to write a cell
1166 onto a closing connection: just discard the cell. Fixes another
1167 case of bug 7350; bugfix on 0.2.4.4-alpha.
1169 o Major bugfixes (client-side privacy):
1170 - When we mark a circuit as unusable for new circuits, have it
1171 continue to be unusable for new circuits even if MaxCircuitDirtiness
1172 is increased too much at the wrong time, or the system clock jumps
1173 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
1174 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
1175 which have resolved to internal addresses") is set, apply that
1176 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
1177 - When an exit relay rejects a stream with reason "exit policy", but
1178 we only know an exit policy summary (e.g. from the microdesc
1179 consensus) for it, do not mark the relay as useless for all exiting.
1180 Instead, mark just the circuit as unsuitable for that particular
1181 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
1182 - Allow applications to get proper stream isolation with
1183 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
1184 username/password authentication also offer "no authentication". Tor
1185 had previously preferred "no authentication", so the applications
1186 never actually sent Tor their auth details. Now Tor selects
1187 username/password authentication if it's offered. You can disable
1188 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
1189 bug 8117; bugfix on 0.2.3.3-alpha.
1191 o Major bugfixes (other):
1192 - When unable to find any working directory nodes to use as a
1193 directory guard, give up rather than adding the same non-working
1194 nodes to the directory guard list over and over. Fixes bug 8231;
1195 bugfix on 0.2.4.8-alpha.
1198 - Reject as invalid most directory objects containing a NUL.
1199 Belt-and-suspender fix for bug 8037.
1200 - In our testsuite, create temporary directories with a bit more
1201 entropy in their name to make name collisions less likely. Fixes
1203 - Add CACHED keyword to ADDRMAP events in the control protocol
1204 to indicate whether a DNS result will be cached or not. Resolves
1206 - Update to the April 3 2013 Maxmind GeoLite Country database.
1208 o Minor features (build):
1209 - Detect and reject attempts to build Tor with threading support
1210 when OpenSSL has been compiled without threading support.
1212 - Clarify that when autoconf is checking for nacl, it is checking
1213 specifically for nacl with a fast curve25519 implementation.
1215 - Warn if building on a platform with an unsigned time_t: there
1216 are too many places where Tor currently assumes that time_t can
1217 hold negative values. We'd like to fix them all, but probably
1220 o Minor bugfixes (build):
1221 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
1222 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
1223 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
1224 - Add the old src/or/micro-revision.i filename to CLEANFILES.
1225 On the off chance that somebody has one, it will go away as soon
1226 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
1227 - Build Tor correctly on 32-bit platforms where the compiler can build
1228 but not run code using the "uint128_t" construction. Fixes bug 8587;
1229 bugfix on 0.2.4.8-alpha.
1230 - Fix compilation warning with some versions of clang that would
1231 prefer the -Wswitch-enum compiler flag to warn about switch
1232 statements with missing enum values, even if those switch
1233 statements have a "default:" statement. Fixes bug 8598; bugfix
1236 o Minor bugfixes (protocol):
1237 - Fix the handling of a TRUNCATE cell when it arrives while the
1238 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
1239 - Fix a misframing issue when reading the version numbers in a
1240 VERSIONS cell. Previously we would recognize [00 01 00 02] as
1241 'version 1, version 2, and version 0x100', when it should have
1242 only included versions 1 and 2. Fixes bug 8059; bugfix on
1243 0.2.0.10-alpha. Reported pseudonymously.
1244 - Make the format and order of STREAM events for DNS lookups
1245 consistent among the various ways to launch DNS lookups. Fixes
1246 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
1247 - Correct our check for which versions of Tor support the EXTEND2
1248 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
1249 later, when support was really added in version 0.2.4.8-alpha.
1250 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
1252 o Minor bugfixes (other):
1253 - Correctly store microdescriptors and extrainfo descriptors with
1254 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
1255 Bug reported by "cypherpunks".
1256 - Increase the width of the field used to remember a connection's
1257 link protocol version to two bytes. Harmless for now, since the
1258 only currently recognized versions are one byte long. Reported
1259 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
1260 - If the state file's path bias counts are invalid (presumably from a
1261 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
1262 additional checks and log messages to the scaling of Path Bias
1263 counts, in case there still are remaining issues with scaling.
1264 Should help resolve bug 8235.
1265 - Eliminate several instances where we use "Nickname=ID" to refer to
1266 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
1267 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
1268 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
1270 o Minor bugfixes (syscalls):
1271 - Always check the return values of functions fcntl() and
1272 setsockopt(). We don't believe these are ever actually failing in
1273 practice, but better safe than sorry. Also, checking these return
1274 values should please analysis tools like Coverity. Patch from
1275 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
1276 - Use direct writes rather than stdio when building microdescriptor
1277 caches, in an attempt to mitigate bug 8031, or at least make it
1280 o Minor bugfixes (config):
1281 - When rejecting a configuration because we were unable to parse a
1282 quoted string, log an actual error message. Fixes bug 7950; bugfix
1284 - Behave correctly when the user disables LearnCircuitBuildTimeout
1285 but doesn't tell us what they would like the timeout to be. Fixes
1286 bug 6304; bugfix on 0.2.2.14-alpha.
1287 - When autodetecting the number of CPUs, use the number of available
1288 CPUs in preference to the number of configured CPUs. Inform the
1289 user if this reduces the number of available CPUs. Fixes bug 8002;
1290 bugfix on 0.2.3.1-alpha.
1291 - Make it an error when you set EntryNodes but disable UseGuardNodes,
1292 since it will (surprisingly to some users) ignore EntryNodes. Fixes
1293 bug 8180; bugfix on 0.2.3.11-alpha.
1294 - Allow TestingTorNetworks to override the 4096-byte minimum for
1295 the Fast threshold. Otherwise they can't bootstrap until they've
1296 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
1297 - Fix some logic errors when the user manually overrides the
1298 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
1301 o Minor bugfixes (log messages to help diagnose bugs):
1302 - If we fail to free a microdescriptor because of bug 7164, log
1303 the filename and line number from which we tried to free it.
1304 - Add another diagnostic to the heartbeat message: track and log
1305 overhead that TLS is adding to the data we write. If this is
1306 high, we are sending too little data to SSL_write at a time.
1307 Diagnostic for bug 7707.
1308 - Add more detail to a log message about relaxed timeouts, to help
1310 - Warn more aggressively when flushing microdescriptors to a
1311 microdescriptor cache fails, in an attempt to mitigate bug 8031,
1312 or at least make it more diagnosable.
1313 - Improve debugging output to help track down bug 8185 ("Bug:
1314 outgoing relay cell has n_chan==NULL. Dropping.")
1315 - Log the purpose of a path-bias testing circuit correctly.
1316 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
1318 o Minor bugfixes (0.2.4.x log messages that were too noisy):
1319 - Don't attempt to relax the timeout of already opened 1-hop circuits.
1320 They might never timeout. This should eliminate some/all cases of
1321 the relaxed timeout log message.
1322 - Use circuit creation time for network liveness evaluation. This
1323 should eliminate warning log messages about liveness caused
1324 by changes in timeout evaluation. Fixes bug 6572; bugfix on
1326 - Reduce a path bias length check from notice to info. The message
1327 is triggered when creating controller circuits. Fixes bug 8196;
1328 bugfix on 0.2.4.8-alpha.
1329 - Fix a path state issue that triggered a notice during relay startup.
1330 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
1331 - Reduce occurrences of warns about circuit purpose in
1332 connection_ap_expire_building(). Fixes bug 8477; bugfix on
1335 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
1336 - If we encounter a write failure on a SOCKS connection before we
1337 finish our SOCKS handshake, don't warn that we closed the
1338 connection before we could send a SOCKS reply. Fixes bug 8427;
1339 bugfix on 0.1.0.1-rc.
1340 - Correctly recognize that [::1] is a loopback address. Fixes
1341 bug 8377; bugfix on 0.2.1.3-alpha.
1342 - Fix a directory authority warn caused when we have a large amount
1343 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
1344 - Don't log inappropriate heartbeat messages when hibernating: a
1345 hibernating node is _expected_ to drop out of the consensus,
1346 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
1347 bugfix on 0.2.3.1-alpha.
1348 - Don't complain about bootstrapping problems while hibernating.
1349 These complaints reflect a general code problem, but not one
1350 with any problematic effects (no connections are actually
1351 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
1353 o Documentation fixes:
1354 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
1355 names match. Fixes bug 7768.
1356 - Make the torify manpage no longer refer to tsocks; torify hasn't
1357 supported tsocks since 0.2.3.14-alpha.
1358 - Make the tor manpage no longer reference tsocks.
1359 - Fix the GeoIPExcludeUnknown documentation to refer to
1360 ExcludeExitNodes rather than the currently nonexistent
1361 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
1364 - The tor-tsocks.conf is no longer distributed or installed. We
1365 recommend that tsocks users use torsocks instead. Resolves
1369 Changes in version 0.2.4.11-alpha - 2013-03-11
1370 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
1371 more robust, makes hidden service authentication work again, and
1372 resolves a DPI fingerprint for Tor's SSL transport.
1374 o Major features (directory authorities):
1375 - Directory authorities now support a new consensus method (17)
1376 where they cap the published bandwidth of servers for which
1377 insufficient bandwidth measurements exist. Fixes part of bug 2286.
1378 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
1379 serve any v2 directory information. Now we can test disabling the
1380 old deprecated v2 directory format, and see whether doing so has
1381 any effect on network load. Begins to fix bug 6783.
1382 - Directory authorities now include inside each vote a statement of
1383 the performance thresholds they used when assigning flags.
1384 Implements ticket 8151.
1386 o Major bugfixes (directory authorities):
1387 - Stop marking every relay as having been down for one hour every
1388 time we restart a directory authority. These artificial downtimes
1389 were messing with our Stable and Guard flag calculations. Fixes
1390 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
1392 o Major bugfixes (hidden services):
1393 - Allow hidden service authentication to succeed again. When we
1394 refactored the hidden service introduction code back
1395 in 0.2.4.1-alpha, we didn't update the code that checks
1396 whether authentication information is present, causing all
1397 authentication checks to return "false". Fix for bug 8207; bugfix
1398 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
1400 o Minor features (relays, bridges):
1401 - Make bridge relays check once a minute for whether their IP
1402 address has changed, rather than only every 15 minutes. Resolves
1404 - Refactor resolve_my_address() so it returns the method by which we
1405 decided our public IP address (explicitly configured, resolved from
1406 explicit hostname, guessed from interfaces, learned by gethostname).
1407 Now we can provide more helpful log messages when a relay guesses
1408 its IP address incorrectly (e.g. due to unexpected lines in
1409 /etc/hosts). Resolves ticket 2267.
1410 - Teach bridge-using clients to avoid 0.2.2 bridges when making
1411 microdescriptor-related dir requests, and only fall back to normal
1412 descriptors if none of their bridges can handle microdescriptors
1413 (as opposed to the fix in ticket 4013, which caused them to fall
1414 back to normal descriptors if *any* of their bridges preferred
1415 them). Resolves ticket 4994.
1416 - Randomize the lifetime of our SSL link certificate, so censors can't
1417 use the static value for filtering Tor flows. Resolves ticket 8443;
1418 related to ticket 4014 which was included in 0.2.2.33.
1420 o Minor features (portability):
1421 - Tweak the curve25519-donna*.c implementations to tolerate systems
1422 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
1423 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
1424 the signs of types during autoconf. This is better than our old
1425 approach, which didn't work when cross-compiling.
1426 - Detect the sign of enum values, rather than assuming that MSC is the
1427 only compiler where enum types are all signed. Fixes bug 7727;
1428 bugfix on 0.2.4.10-alpha.
1430 o Minor features (other):
1431 - Say "KBytes" rather than "KB" in the man page (for various values
1432 of K), to further reduce confusion about whether Tor counts in
1433 units of memory or fractions of units of memory. Resolves ticket 7054.
1434 - Clear the high bit on curve25519 public keys before passing them to
1435 our backend, in case we ever wind up using a backend that doesn't do
1436 so itself. If we used such a backend, and *didn't* clear the high bit,
1437 we could wind up in a situation where users with such backends would
1438 be distinguishable from users without. Fixes bug 8121; bugfix on
1440 - Update to the March 6 2013 Maxmind GeoLite Country database.
1442 o Minor bugfixes (clients):
1443 - When we receive a RELAY_END cell with the reason DONE, or with no
1444 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
1445 status as "connection refused". Previously we reported these cases
1446 as success but then immediately closed the connection. Fixes bug
1447 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
1448 - Downgrade an assertion in connection_ap_expire_beginning to an
1449 LD_BUG message. The fix for bug 8024 should prevent this message
1450 from displaying, but just in case, a warn that we can diagnose
1451 is better than more assert crashes. Fixes bug 8065; bugfix on
1453 - Lower path use bias thresholds to .80 for notice and .60 for warn.
1454 Also make the rate limiting flags for the path use bias log messages
1455 independent from the original path bias flags. Fixes bug 8161;
1456 bugfix on 0.2.4.10-alpha.
1458 o Minor bugfixes (relays):
1459 - Stop trying to resolve our hostname so often (e.g. every time we
1460 think about doing a directory fetch). Now we reuse the cached
1461 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
1462 and 2410 (bugfix on 0.1.2.2-alpha).
1463 - Stop sending a stray "(null)" in some cases for the server status
1464 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
1466 - When choosing which stream on a formerly stalled circuit to wake
1467 first, make better use of the platform's weak RNG. Previously,
1468 we had been using the % ("modulo") operator to try to generate a
1469 1/N chance of picking each stream, but this behaves badly with
1470 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
1472 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
1473 Irix's random() only return 15 bits; Solaris's random() returns more
1474 bits but its RAND_MAX says it only returns 15, and so on. Motivated
1475 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
1477 o Minor bugfixes (directory authorities):
1478 - Directory authorities now use less space when formatting identical
1479 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
1482 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
1483 - Avoid leaking memory if we fail to compute a consensus signature
1484 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
1485 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
1487 - Fix a memory leak during safe-cookie controller authentication.
1488 Bugfix on 0.2.3.13-alpha.
1489 - Avoid memory leak of IPv6 policy content if we fail to format it into
1490 a router descriptor. Bugfix on 0.2.4.7-alpha.
1492 o Minor bugfixes (other code correctness issues):
1493 - Avoid a crash if we fail to generate an extrainfo descriptor.
1494 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
1496 - When detecting the largest possible file descriptor (in order to
1497 close all file descriptors when launching a new program), actually
1498 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
1499 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
1501 - Fix a copy-and-paste error when adding a missing A1 to a routerset
1502 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
1503 Bugfix on 0.2.4.10-alpha.
1504 - Fix an impossible-to-trigger integer overflow when estimating how
1505 long our onionskin queue would take. (This overflow would require us
1506 to accept 4 million onionskins before processing 100 of them.) Fixes
1507 bug 8210; bugfix on 0.2.4.10-alpha.
1509 o Code simplification and refactoring:
1510 - Add a wrapper function for the common "log a message with a
1514 Changes in version 0.2.4.10-alpha - 2013-02-04
1515 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
1516 certain attacks that flood the network with relays; changes the queue
1517 for circuit create requests from a sized-based limit to a time-based
1518 limit; resumes building with MSVC on Windows; and fixes a wide variety
1521 o Major bugfixes (directory authority):
1522 - When computing directory thresholds, ignore any rejected-as-sybil
1523 nodes during the computation so that they can't influence Fast,
1524 Guard, etc. (We should have done this for proposal 109.) Fixes
1526 - When marking a node as a likely sybil, reset its uptime metrics
1527 to zero, so that it cannot time towards getting marked as Guard,
1528 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
1532 - When a TLS write is partially successful but incomplete, remember
1533 that the flushed part has been flushed, and notice that bytes were
1534 actually written. Reported and fixed pseudonymously. Fixes bug
1535 7708; bugfix on Tor 0.1.0.5-rc.
1536 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
1537 ID: these could be used to create unexpected streams and circuits
1538 which would count as "present" to some parts of Tor but "absent"
1539 to others, leading to zombie circuits and streams or to a bandwidth
1540 denial-of-service. Fixes bug 7889; bugfix on every released version
1541 of Tor. Reported by "oftc_must_be_destroyed".
1542 - Rename all macros in our local copy of queue.h to begin with "TOR_".
1543 This change seems the only good way to permanently prevent conflicts
1544 with queue.h on various operating systems. Fixes bug 8107; bugfix
1547 o Major features (relay):
1548 - Instead of limiting the number of queued onionskins (aka circuit
1549 create requests) to a fixed, hard-to-configure number, we limit
1550 the size of the queue based on how many we expect to be able to
1551 process in a given amount of time. We estimate the time it will
1552 take to process an onionskin based on average processing time
1553 of previous onionskins. Closes ticket 7291. You'll never have to
1554 configure MaxOnionsPending again.
1556 o Major features (portability):
1557 - Resume building correctly with MSVC and Makefile.nmake. This patch
1558 resolves numerous bugs and fixes reported by ultramage, including
1559 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
1560 - Make the ntor and curve25519 code build correctly with MSVC.
1561 Fix on 0.2.4.8-alpha.
1564 - When directory authorities are computing thresholds for flags,
1565 never let the threshold for the Fast flag fall below 4096
1566 bytes. Also, do not consider nodes with extremely low bandwidths
1567 when deciding thresholds for various directory flags. This change
1568 should raise our threshold for Fast relays, possibly in turn
1569 improving overall network performance; see ticket 1854. Resolves
1571 - The Tor client now ignores sub-domain components of a .onion
1572 address. This change makes HTTP "virtual" hosting
1573 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
1574 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
1575 hosted on the same hidden service. Implements proposal 204.
1576 - We compute the overhead from passing onionskins back and forth to
1577 cpuworkers, and report it when dumping statistics in response to
1578 SIGUSR1. Supports ticket 7291.
1580 o Minor features (path selection):
1581 - When deciding whether we have enough descriptors to build circuits,
1582 instead of looking at raw relay counts, look at which fraction
1583 of (bandwidth-weighted) paths we're able to build. This approach
1584 keeps clients from building circuits if their paths are likely to
1585 stand out statistically. The default fraction of paths needed is
1586 taken from the consensus directory; you can override it with the
1587 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
1588 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
1589 and we have GeoIP information, also exclude all nodes with unknown
1590 countries "??" and "A1". This behavior is controlled by the
1591 new GeoIPExcludeUnknown option: you can make such nodes always
1592 excluded with "GeoIPExcludeUnknown 1", and disable the feature
1593 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
1594 gets you the default behavior. Implements feature 7706.
1595 - Path Use Bias: Perform separate accounting for successful circuit
1596 use. Keep separate statistics on stream attempt rates versus stream
1597 success rates for each guard. Provide configurable thresholds to
1598 determine when to emit log messages or disable use of guards that
1599 fail too many stream attempts. Resolves ticket 7802.
1601 o Minor features (log messages):
1602 - When learning a fingerprint for a bridge, log its corresponding
1603 transport type. Implements ticket 7896.
1604 - Improve the log message when "Bug/attack: unexpected sendme cell
1605 from client" occurs, to help us track bug 8093.
1608 - Remove a couple of extraneous semicolons that were upsetting the
1609 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
1610 bugfix on 0.2.2.1-alpha.
1611 - Remove a source of rounding error during path bias count scaling;
1612 don't count cannibalized circuits as used for path bias until we
1613 actually try to use them; and fix a circuit_package_relay_cell()
1614 warning message about n_chan==NULL. Fixes bug 7802.
1615 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
1616 actually link against nacl when we're configured to use it. Fixes
1617 bug 7972; bugfix on 0.2.4.8-alpha.
1618 - Compile correctly with the --disable-curve25519 option. Fixes
1619 bug 8153; bugfix on 0.2.4.8-alpha.
1621 o Build improvements:
1622 - Do not report status verbosely from autogen.sh unless the -v flag
1623 is specified. Fixes issue 4664. Patch from Onizuka.
1624 - Replace all calls to snprintf() outside of src/ext with
1625 tor_snprintf(). Also remove the #define to replace snprintf with
1626 _snprintf on Windows; they have different semantics, and all of
1627 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
1628 - Try to detect if we are ever building on a platform where
1629 memset(...,0,...) does not set the value of a double to 0.0. Such
1630 platforms are permitted by the C standard, though in practice
1631 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
1632 currently support them, but it's better to detect them and fail
1633 than to perform erroneously.
1636 - Stop exporting estimates of v2 and v3 directory traffic shares
1637 in extrainfo documents. They were unneeded and sometimes inaccurate.
1638 Also stop exporting any v2 directory request statistics. Resolves
1640 - Drop support for detecting and warning about versions of Libevent
1641 before 1.3e. Nothing reasonable ships with them any longer;
1642 warning the user about them shouldn't be needed. Resolves ticket
1645 o Code simplifications and refactoring:
1646 - Rename "isin" functions to "contains", for grammar. Resolves
1648 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
1649 with the natural logarithm function from the system libm. Resolves
1653 Changes in version 0.2.4.9-alpha - 2013-01-15
1654 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
1658 - Fix backward compatibility logic when receiving an embedded ntor
1659 handshake tunneled in a CREATE cell. This clears up the "Bug:
1660 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
1664 Changes in version 0.2.4.8-alpha - 2013-01-14
1665 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
1666 risks, adds a new stronger and faster circuit handshake, and offers
1667 stronger and faster link encryption when both sides support it.
1670 - Preliminary support for directory guards (proposal 207): when
1671 possible, clients now use their entry guards for non-anonymous
1672 directory requests. This can help prevent client enumeration. Note
1673 that this behavior only works when we have a usable consensus
1674 directory, and when options about what to download are more or less
1675 standard. In the future we should re-bootstrap from our guards,
1676 rather than re-bootstrapping from the preconfigured list of
1677 directory sources that ships with Tor. Resolves ticket 6526.
1678 - Tor relays and clients now support a better CREATE/EXTEND cell
1679 format, allowing the sender to specify multiple address, identity,
1680 and handshake types. Implements Robert Ransom's proposal 200;
1683 o Major features (new circuit handshake):
1684 - Tor now supports a new circuit extension handshake designed by Ian
1685 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
1686 circuit extension handshake, later called "TAP", was a bit slow
1687 (especially on the relay side), had a fragile security proof, and
1688 used weaker keys than we'd now prefer. The new circuit handshake
1689 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
1690 function, making it significantly more secure than the older
1691 handshake, and significantly faster. Tor can use one of two built-in
1692 pure-C curve25519-donna implementations by Adam Langley, or it
1693 can link against the "nacl" library for a tuned version if present.
1695 The built-in version is very fast for 64-bit systems when building
1696 with GCC. The built-in 32-bit version is still faster than the
1697 old TAP protocol, but using libnacl is better on most such hosts.
1699 Clients don't currently use this protocol by default, since
1700 comparatively few clients support it so far. To try it, set
1701 UseNTorHandshake to 1.
1703 Implements proposal 216; closes ticket 7202.
1705 o Major features (better link encryption):
1706 - Relays can now enable the ECDHE TLS ciphersuites when available
1707 and appropriate. These ciphersuites let us negotiate forward-secure
1708 TLS secret keys more safely and more efficiently than with our
1709 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
1710 public relays prefer the (faster) P224 group, and bridges prefer
1711 the (more common) P256 group; you can override this with the
1714 Enabling these ciphers was a little tricky, since for a long time,
1715 clients had been claiming to support them without actually doing
1716 so, in order to foil fingerprinting. But with the client-side
1717 implementation of proposal 198 in 0.2.3.17-beta, clients can now
1718 match the ciphers from recent Firefox versions *and* list the
1719 ciphers they actually mean, so relays can believe such clients
1720 when they advertise ECDHE support in their TLS ClientHello messages.
1722 This feature requires clients running 0.2.3.17-beta or later,
1723 and requires both sides to be running OpenSSL 1.0.0 or later
1724 with ECC support. OpenSSL 1.0.1, with the compile-time option
1725 "enable-ec_nistp_64_gcc_128", is highly recommended.
1727 Implements the relay side of proposal 198; closes ticket 7200.
1730 - Avoid crashing when, as a relay without IPv6-exit support, a
1731 client insists on getting an IPv6 address or nothing. Fixes bug
1732 7814; bugfix on 0.2.4.7-alpha.
1735 - Improve circuit build timeout handling for hidden services.
1736 In particular: adjust build timeouts more accurately depending
1737 upon the number of hop-RTTs that a particular circuit type
1738 undergoes. Additionally, launch intro circuits in parallel
1739 if they timeout, and take the first one to reply as valid.
1740 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
1741 separate error codes; or at least, don't break for that reason.
1742 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
1743 - Update to the January 2 2013 Maxmind GeoLite Country database.
1745 o Minor features (testing):
1746 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
1747 (P-256) Diffie-Hellman handshakes to src/or/bench.
1748 - Add benchmark functions to test onion handshake performance.
1750 o Minor features (path bias detection):
1751 - Alter the Path Bias log messages to be more descriptive in terms
1752 of reporting timeouts and other statistics.
1753 - Create three levels of Path Bias log messages, as opposed to just
1754 two. These are configurable via consensus as well as via the torrc
1755 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
1756 The default values are 0.70, 0.50, and 0.30 respectively.
1757 - Separate the log message levels from the decision to drop guards,
1758 which also is available via torrc option PathBiasDropGuards.
1759 PathBiasDropGuards still defaults to 0 (off).
1760 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
1761 in combination with PathBiasExtremeRate.
1762 - Increase the default values for PathBiasScaleThreshold and
1763 PathBiasCircThreshold from (200, 20) to (300, 150).
1764 - Add in circuit usage accounting to path bias. If we try to use a
1765 built circuit but fail for any reason, it counts as path bias.
1766 Certain classes of circuits where the adversary gets to pick your
1767 destination node are exempt from this accounting. Usage accounting
1768 can be specifically disabled via consensus parameter or torrc.
1769 - Convert all internal path bias state to double-precision floating
1770 point, to avoid roundoff error and other issues.
1771 - Only record path bias information for circuits that have completed
1772 *two* hops. Assuming end-to-end tagging is the attack vector, this
1773 makes us more resilient to ambient circuit failure without any
1774 detection capability loss.
1776 o Minor bugfixes (log messages):
1777 - Rate-limit the "No circuits are opened. Relaxed timeout for a
1778 circuit with channel state open..." message to once per hour to
1779 keep it from filling the notice logs. Mitigates bug 7799 but does
1780 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
1781 - Avoid spurious warnings when configuring multiple client ports of
1782 which only some are nonlocal. Previously, we had claimed that some
1783 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
1786 o Code simplifications and refactoring:
1787 - Get rid of a couple of harmless clang warnings, where we compared
1788 enums to ints. These warnings are newly introduced in clang 3.2.
1789 - Split the onion.c file into separate modules for the onion queue
1790 and the different handshakes it supports.
1791 - Remove the marshalling/unmarshalling code for sending requests to
1792 cpuworkers over a socket, and instead just send structs. The
1793 recipient will always be the same Tor binary as the sender, so
1794 any encoding is overkill.
1797 Changes in version 0.2.4.7-alpha - 2012-12-24
1798 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
1799 directory mirrors for more robust bootstrapping; fixes more issues where
1800 clients with changing network conditions refuse to make any circuits;
1801 adds initial support for exiting to IPv6 addresses; resumes being able
1802 to update our GeoIP database, and includes the geoip6 file this time;
1803 turns off the client-side DNS cache by default due to privacy risks;
1804 and fixes a variety of other issues.
1806 o Major features (client resilience):
1807 - Add a new "FallbackDir" torrc option to use when we can't use
1808 a directory mirror from the consensus (either because we lack a
1809 consensus, or because they're all down). Currently, all authorities
1810 are fallbacks by default, and there are no other default fallbacks,
1811 but that will change. This option will allow us to give clients a
1812 longer list of servers to try to get a consensus from when first
1813 connecting to the Tor network, and thereby reduce load on the
1814 directory authorities. Implements proposal 206, "Preconfigured
1815 directory sources for bootstrapping". We also removed the old
1816 "FallbackNetworkstatus" option, since we never got it working well
1817 enough to use it. Closes bug 572.
1818 - If we have no circuits open, use a relaxed timeout (the
1819 95-percentile cutoff) until a circuit succeeds. This heuristic
1820 should allow Tor to succeed at building circuits even when the
1821 network connection drastically changes. Should help with bug 3443.
1823 o Major features (IPv6):
1824 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
1825 connectivity, then set the IPv6Exit flag to 1. Also make sure your
1826 exit policy reads as you would like: the address * applies to all
1827 address families, whereas *4 is IPv4 address only, and *6 is IPv6
1828 addresses only. On the client side, you'll need to wait until the
1829 authorities have upgraded, wait for enough exits to support IPv6,
1830 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
1831 ticket 5547, implements proposal 117 as revised in proposal 208.
1833 We DO NOT recommend that clients with actual anonymity needs start
1834 using IPv6 over Tor yet, since not enough exits support it yet.
1836 o Major features (geoip database):
1837 - Maxmind began labelling Tor relays as being in country "A1",
1838 which breaks by-country node selection inside Tor. Now we use a
1839 script to replace "A1" ("Anonymous Proxy") entries in our geoip
1840 file with real country codes. This script fixes about 90% of "A1"
1841 entries automatically and uses manual country code assignments to
1842 fix the remaining 10%. See src/config/README.geoip for details.
1843 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
1844 Country database, as modified above.
1846 o Major bugfixes (client-side DNS):
1847 - Turn off the client-side DNS cache by default. Updating and using
1848 the DNS cache is now configurable on a per-client-port
1849 level. SOCKSPort, DNSPort, etc lines may now contain
1850 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
1851 cache these types of DNS answers when we receive them from an
1852 exit node in response to an application request on this port, and
1853 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
1854 cached DNS answers of these types, we shouldn't use them. It's
1855 potentially risky to use cached DNS answers at the client, since
1856 doing so can indicate to one exit what answers we've gotten
1857 for DNS lookups in the past. With IPv6, this becomes especially
1858 problematic. Using cached DNS answers for requests on the same
1859 circuit would present less linkability risk, since all traffic
1860 on a circuit is already linkable, but it would also provide
1861 little performance benefit: the exit node caches DNS replies
1862 too. Implements a simplified version of Proposal 205. Implements
1865 o Major bugfixes (other):
1866 - Alter circuit build timeout measurement to start at the point
1867 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
1868 initialization). This should make our timeout measurements more
1869 uniform. Previously, we were sometimes including ORconn setup time
1870 in our circuit build time measurements. Should resolve bug 3443.
1871 - Fix an assertion that could trigger in hibernate_go_dormant() when
1872 closing an or_connection_t: call channel_mark_for_close() rather
1873 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
1875 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
1876 7655; bugfix on 0.2.4.6-alpha.
1879 - Add a new torrc option "ServerTransportListenAddr" to let bridge
1880 operators select the address where their pluggable transports will
1881 listen for connections. Resolves ticket 7013.
1882 - Allow an optional $ before the node identity digest in the
1883 controller command GETINFO ns/id/<identity>, for consistency with
1884 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
1885 - Log packaged cell fullness as part of the heartbeat message.
1886 Diagnosis to try to determine the extent of bug 7743.
1888 o Minor features (IPv6):
1889 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
1890 prefer to hand out virtual IPv6 addresses, since there are more of
1891 them and we can't run out. To override this behavior and make IPv4
1892 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
1893 or DNSPort you're using for resolving. Implements ticket 7571.
1894 - AutomapHostsOnResolve responses are now randomized, to avoid
1895 annoying situations where Tor is restarted and applications
1896 connect to the wrong addresses.
1897 - Never try more than 1000 times to pick a new virtual address when
1898 AutomapHostsOnResolve is set. That's good enough so long as we
1899 aren't close to handing out our entire virtual address space;
1900 if you're getting there, it's best to switch to IPv6 virtual
1904 - The ADDRMAP command can no longer generate an ill-formed error
1905 code on a failed MAPADDRESS. It now says "internal" rather than
1906 an English sentence fragment with spaces in the middle. Bugfix on
1908 - Fix log messages and comments to avoid saying "GMT" when we mean
1909 "UTC". Fixes bug 6113.
1910 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1912 - Fix a crash when debugging unit tests on Windows: deallocate a
1913 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1914 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1917 - The DirServer option is now DirAuthority, for consistency with
1918 current naming patterns. You can still use the old DirServer form.
1920 o Code simplification and refactoring:
1921 - Move the client-side address-map/virtual-address/DNS-cache code
1922 out of connection_edge.c into a new addressmap.c module.
1923 - Remove unused code for parsing v1 directories and "running routers"
1924 documents. Fixes bug 6887.
1927 Changes in version 0.2.3.25 - 2012-11-19
1928 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1929 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1930 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1931 programmer, and friend. Unstinting in his dedication to the cause of
1932 freedom, he inspired and helped many of us as we began our work on
1933 anonymity, and inspires us still. Please honor his memory by writing
1934 software to protect people's freedoms, and by helping others to do so.
1936 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1937 significantly reduced directory overhead (via microdescriptors),
1938 enormous crypto performance improvements for fast relays on new
1939 enough hardware, a new v3 TLS handshake protocol that can better
1940 resist fingerprinting, support for protocol obfuscation plugins (aka
1941 pluggable transports), better scalability for hidden services, IPv6
1942 support for bridges, performance improvements like allowing clients
1943 to skip the first round-trip on the circuit ("optimistic data") and
1944 refilling token buckets more often, a new "stream isolation" design
1945 to isolate different applications on different circuits, and many
1946 stability, security, and privacy fixes.
1949 - Tor tries to wipe potentially sensitive data after using it, so
1950 that if some subsequent security failure exposes Tor's memory,
1951 the damage will be limited. But we had a bug where the compiler
1952 was eliminating these wipe operations when it decided that the
1953 memory was no longer visible to a (correctly running) program,
1954 hence defeating our attempt at defense in depth. We fix that
1955 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1956 is unlikely to optimize away. Future versions of Tor may use
1957 a less ridiculously heavy approach for this. Fixes bug 7352.
1958 Reported in an article by Andrey Karpov.
1961 - Fix a harmless bug when opting against publishing a relay descriptor
1962 because DisableNetwork is set. Fixes bug 7464; bugfix on
1966 Changes in version 0.2.4.6-alpha - 2012-11-13
1967 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
1968 makes our defense-in-depth memory wiping more reliable, and begins to
1969 count IPv6 addresses in bridge statistics,
1972 - Fix an assertion failure that could occur when closing a connection
1973 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
1975 - Tor tries to wipe potentially sensitive data after using it, so
1976 that if some subsequent security failure exposes Tor's memory,
1977 the damage will be limited. But we had a bug where the compiler
1978 was eliminating these wipe operations when it decided that the
1979 memory was no longer visible to a (correctly running) program,
1980 hence defeating our attempt at defense in depth. We fix that
1981 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1982 is unlikely to optimize away. Future versions of Tor may use
1983 a less ridiculously heavy approach for this. Fixes bug 7352.
1984 Reported in an article by Andrey Karpov.
1987 - Add GeoIP database for IPv6 addresses. The new config option
1989 - Bridge statistics now count bridge clients connecting over IPv6:
1990 bridge statistics files now list "bridge-ip-versions" and
1991 extra-info documents list "geoip6-db-digest". The control protocol
1992 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1993 implementation by "shkoo", addressing ticket 5055.
1996 - Warn when we are binding low ports when hibernation is enabled;
1997 previously we had warned when we were _advertising_ low ports with
1998 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1999 - Fix a harmless bug when opting against publishing a relay descriptor
2000 because DisableNetwork is set. Fixes bug 7464; bugfix on
2002 - Add warning message when a managed proxy dies during configuration.
2003 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
2004 - Fix a linking error when building tor-fw-helper without miniupnp.
2005 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
2006 - Check for closing an or_connection_t without going through correct
2007 channel functions; emit a warning and then call
2008 connection_or_close_for_error() so we don't assert as in bugs 7212
2010 - Compile correctly on compilers without C99 designated initializer
2011 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
2012 - Avoid a possible assert that can occur when channel_send_destroy() is
2013 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
2014 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
2015 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
2016 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
2017 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
2019 o Code simplification and refactoring:
2020 - Start using OpenBSD's implementation of queue.h, so that we don't
2021 need to hand-roll our own pointer and list structures whenever we
2022 need them. (We can't rely on a sys/queue.h, since some operating
2023 systems don't have them, and the ones that do have them don't all
2024 present the same extensions.)
2027 Changes in version 0.2.4.5-alpha - 2012-10-25
2028 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
2029 two important security vulnerabilities that could lead to remotely
2030 triggerable relay crashes, fix a major bug that was preventing clients
2031 from choosing suitable exit nodes, and refactor some of our code.
2033 o Major bugfixes (security, also in 0.2.3.24-rc):
2034 - Fix a group of remotely triggerable assertion failures related to
2035 incorrect link protocol negotiation. Found, diagnosed, and fixed
2036 by "some guy from France". Fix for CVE-2012-2250; bugfix on
2038 - Fix a denial of service attack by which any directory authority
2039 could crash all the others, or by which a single v2 directory
2040 authority could crash everybody downloading v2 directory
2041 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
2043 o Major bugfixes (also in 0.2.3.24-rc):
2044 - When parsing exit policy summaries from microdescriptors, we had
2045 previously been ignoring the last character in each one, so that
2046 "accept 80,443,8080" would be treated by clients as indicating
2047 a node that allows access to ports 80, 443, and 808. That would
2048 lead to clients attempting connections that could never work,
2049 and ignoring exit nodes that would support their connections. Now
2050 clients parse these exit policy summaries correctly. Fixes bug 7192;
2051 bugfix on 0.2.3.1-alpha.
2053 o Minor bugfixes (also in 0.2.3.24-rc):
2054 - Clients now consider the ClientRejectInternalAddresses config option
2055 when using a microdescriptor consensus stanza to decide whether
2056 an exit relay would allow exiting to an internal address. Fixes
2057 bug 7190; bugfix on 0.2.3.1-alpha.
2060 - Only disable TLS session ticket support when running as a TLS
2061 server. Now clients will blend better with regular Firefox
2062 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
2064 o Code simplification and refactoring:
2065 - Start using OpenBSD's implementation of queue.h (originally by
2067 - Move the entry node code from circuitbuild.c to its own file.
2068 - Move the circuit build timeout tracking code from circuitbuild.c
2072 Changes in version 0.2.3.24-rc - 2012-10-25
2073 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
2074 could lead to remotely triggerable relay crashes, and fixes
2075 a major bug that was preventing clients from choosing suitable exit
2078 o Major bugfixes (security):
2079 - Fix a group of remotely triggerable assertion failures related to
2080 incorrect link protocol negotiation. Found, diagnosed, and fixed
2081 by "some guy from France". Fix for CVE-2012-2250; bugfix on
2083 - Fix a denial of service attack by which any directory authority
2084 could crash all the others, or by which a single v2 directory
2085 authority could crash everybody downloading v2 directory
2086 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
2089 - When parsing exit policy summaries from microdescriptors, we had
2090 previously been ignoring the last character in each one, so that
2091 "accept 80,443,8080" would be treated by clients as indicating
2092 a node that allows access to ports 80, 443, and 808. That would
2093 lead to clients attempting connections that could never work,
2094 and ignoring exit nodes that would support their connections. Now
2095 clients parse these exit policy summaries correctly. Fixes bug 7192;
2096 bugfix on 0.2.3.1-alpha.
2099 - Clients now consider the ClientRejectInternalAddresses config option
2100 when using a microdescriptor consensus stanza to decide whether
2101 an exit relay would allow exiting to an internal address. Fixes
2102 bug 7190; bugfix on 0.2.3.1-alpha.
2105 Changes in version 0.2.4.4-alpha - 2012-10-20
2106 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
2107 vulnerability introduced by a change in OpenSSL, fixes a remotely
2108 triggerable assert, and adds new channel_t and circuitmux_t abstractions
2109 that will make it easier to test new connection transport and cell
2110 scheduling algorithms.
2112 o New directory authorities (also in 0.2.3.23-rc):
2113 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
2114 authority. Closes ticket 5749.
2116 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
2117 - Disable TLS session tickets. OpenSSL's implementation was giving
2118 our TLS session keys the lifetime of our TLS context objects, when
2119 perfect forward secrecy would want us to discard anything that
2120 could decrypt a link connection as soon as the link connection
2121 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
2122 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
2123 - Discard extraneous renegotiation attempts once the V3 link
2124 protocol has been initiated. Failure to do so left us open to
2125 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
2126 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
2128 o Internal abstraction features:
2129 - Introduce new channel_t abstraction between circuits and
2130 or_connection_t to allow for implementing alternate OR-to-OR
2131 transports. A channel_t is an abstract object which can either be a
2132 cell-bearing channel, which is responsible for authenticating and
2133 handshaking with the remote OR and transmitting cells to and from
2134 it, or a listening channel, which spawns new cell-bearing channels
2135 at the request of remote ORs. Implements part of ticket 6465.
2136 - Also new is the channel_tls_t subclass of channel_t, adapting it
2137 to the existing or_connection_t code. The V2/V3 protocol handshaking
2138 code which formerly resided in command.c has been moved below the
2139 channel_t abstraction layer and may be found in channeltls.c now.
2140 Implements the rest of ticket 6465.
2141 - Introduce new circuitmux_t storing the queue of circuits for
2142 a channel; this encapsulates and abstracts the queue logic and
2143 circuit selection policy, and allows the latter to be overridden
2144 easily by switching out a policy object. The existing EWMA behavior
2145 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
2147 o Required libraries:
2148 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
2149 strongly recommended.
2152 - Warn users who run hidden services on a Tor client with
2153 UseEntryGuards disabled that their hidden services will be
2154 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
2155 attack which motivated Tor to support entry guards in the first
2156 place). Resolves ticket 6889.
2157 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
2158 dhill. Resolves ticket 6982.
2159 - Option OutboundBindAddress can be specified multiple times and
2160 accepts IPv6 addresses. Resolves ticket 6876.
2162 o Minor bugfixes (also in 0.2.3.23-rc):
2163 - Don't serve or accept v2 hidden service descriptors over a
2164 relay's DirPort. It's never correct to do so, and disabling it
2165 might make it more annoying to exploit any bugs that turn up in the
2166 descriptor-parsing code. Fixes bug 7149.
2167 - Fix two cases in src/or/transports.c where we were calling
2168 fmt_addr() twice in a parameter list. Bug found by David
2169 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
2170 - Fix memory leaks whenever we logged any message about the "path
2171 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
2172 - When relays refuse a "create" cell because their queue of pending
2173 create cells is too big (typically because their cpu can't keep up
2174 with the arrival rate), send back reason "resource limit" rather
2175 than reason "internal", so network measurement scripts can get a
2176 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
2179 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
2180 - Free some more still-in-use memory at exit, to make hunting for
2181 memory leaks easier. Resolves bug 7029.
2182 - When a Tor client gets a "truncated" relay cell, the first byte of
2183 its payload specifies why the circuit was truncated. We were
2184 ignoring this 'reason' byte when tearing down the circuit, resulting
2185 in the controller not being told why the circuit closed. Now we
2186 pass the reason from the truncated cell to the controller. Bugfix
2187 on 0.1.2.3-alpha; fixes bug 7039.
2188 - Downgrade "Failed to hand off onionskin" messages to "debug"
2189 severity, since they're typically redundant with the "Your computer
2190 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
2191 - Make clients running with IPv6 bridges connect over IPv6 again,
2192 even without setting new config options ClientUseIPv6 and
2193 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
2194 - Use square brackets around IPv6 addresses in numerous places
2195 that needed them, including log messages, HTTPS CONNECT proxy
2196 requests, TransportProxy statefile entries, and pluggable transport
2197 extra-info lines. Fixes bug 7011; patch by David Fifield.
2199 o Code refactoring and cleanup:
2200 - Source files taken from other packages now reside in src/ext;
2201 previously they were scattered around the rest of Tor.
2202 - Avoid use of reserved identifiers in our C code. The C standard
2203 doesn't like us declaring anything that starts with an
2204 underscore, so let's knock it off before we get in trouble. Fix
2205 for bug 1031; bugfix on the first Tor commit.
2208 Changes in version 0.2.3.23-rc - 2012-10-20
2209 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
2210 vulnerability introduced by a change in OpenSSL, and fixes a variety
2211 of smaller bugs in preparation for the release.
2213 o New directory authorities:
2214 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
2215 authority. Closes ticket 5749.
2217 o Major bugfixes (security/privacy):
2218 - Disable TLS session tickets. OpenSSL's implementation was giving
2219 our TLS session keys the lifetime of our TLS context objects, when
2220 perfect forward secrecy would want us to discard anything that
2221 could decrypt a link connection as soon as the link connection
2222 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
2223 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
2224 - Discard extraneous renegotiation attempts once the V3 link
2225 protocol has been initiated. Failure to do so left us open to
2226 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
2227 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
2230 - Fix a possible crash bug when checking for deactivated circuits
2231 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
2232 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
2234 o Minor bugfixes (on 0.2.3.x):
2235 - Fix two cases in src/or/transports.c where we were calling
2236 fmt_addr() twice in a parameter list. Bug found by David
2237 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
2238 - Convert an assert in the pathbias code to a log message. The assert
2239 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
2240 bugfix on 0.2.3.17-beta.
2241 - Fix memory leaks whenever we logged any message about the "path
2242 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
2244 o Minor bugfixes (on 0.2.2.x and earlier):
2245 - Don't serve or accept v2 hidden service descriptors over a relay's
2246 DirPort. It's never correct to do so, and disabling it might
2247 make it more annoying to exploit any bugs that turn up in the
2248 descriptor-parsing code. Fixes bug 7149.
2249 - When relays refuse a "create" cell because their queue of pending
2250 create cells is too big (typically because their cpu can't keep up
2251 with the arrival rate), send back reason "resource limit" rather
2252 than reason "internal", so network measurement scripts can get a
2253 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
2254 - Correct file sizes when reading binary files on Cygwin, to avoid
2255 a bug where Tor would fail to read its state file. Fixes bug 6844;
2256 bugfix on 0.1.2.7-alpha.
2257 - Avoid undefined behaviour when parsing the list of supported
2258 rendezvous/introduction protocols in a hidden service descriptor.
2259 Previously, Tor would have confused (as-yet-unused) protocol version
2260 numbers greater than 32 with lower ones on many platforms. Fixes
2261 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
2263 o Documentation fixes:
2264 - Clarify that hidden services are TCP only. Fixes bug 6024.
2267 Changes in version 0.2.4.3-alpha - 2012-09-22
2268 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
2269 assertion, resumes letting relays test reachability of their DirPort,
2270 and cleans up a bunch of smaller bugs.
2273 - Fix an assertion failure in tor_timegm() that could be triggered
2274 by a badly formatted directory object. Bug found by fuzzing with
2275 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2278 - Fix a possible crash bug when checking for deactivated circuits
2279 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
2280 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
2281 - Allow routers to detect that their own DirPorts are running. When
2282 we removed support for versions_supports_begindir, we also
2283 accidentally removed the mechanism we used to self-test our
2284 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
2285 bugfix on 0.2.4.2-alpha.
2287 o Security features:
2288 - Switch to a completely time-invariant approach for picking nodes
2289 weighted by bandwidth. Our old approach would run through the
2290 part of the loop after it had made its choice slightly slower
2291 than it ran through the part of the loop before it had made its
2292 choice. Addresses ticket 6538.
2293 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
2294 by tor2web clients allows hidden services to identify tor2web
2295 clients through their repeated selection of the same rendezvous
2296 and introduction point circuit endpoints (their guards). Resolves
2300 - Enable Tor to read configuration, state, and key information from
2301 a FIFO. Previously Tor would only read from files with a positive
2302 stat.st_size. Code from meejah; fixes bug 6044.
2305 - Correct file sizes when reading binary files on Cygwin, to avoid
2306 a bug where Tor would fail to read its state file. Fixes bug 6844;
2307 bugfix on 0.1.2.7-alpha.
2308 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
2309 bugfix on 0.2.0.3-alpha.
2310 - When complaining about a client port on a public address, log
2311 which address we're complaining about. Fixes bug 4020; bugfix on
2312 0.2.3.3-alpha. Patch by Tom Fitzhenry.
2313 - Convert an assert in the pathbias code to a log message. The assert
2314 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
2315 bugfix on 0.2.3.17-beta.
2316 - Our new buildsystem was overzealous about rebuilding manpages: it
2317 would rebuild them all whenever any one of them changed. Now our
2318 dependency checking should be correct. Fixes bug 6843; bugfix on
2320 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
2321 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
2322 - Correct log printout about which address family is preferred
2323 when connecting to a bridge with both an IPv4 and IPv6 OR port.
2324 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
2326 o Minor bugfixes (code cleanliness):
2327 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
2328 with large values. This situation was untriggered, but nevertheless
2329 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
2330 - Reject consensus votes with more than 64 known-flags. We aren't even
2331 close to that limit yet, and our code doesn't handle it correctly.
2332 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
2333 - Avoid undefined behaviour when parsing the list of supported
2334 rendezvous/introduction protocols in a hidden service descriptor.
2335 Previously, Tor would have confused (as-yet-unused) protocol version
2336 numbers greater than 32 with lower ones on many platforms. Fixes
2337 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
2338 - Fix handling of rendezvous client authorization types over 8.
2339 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
2340 - Fix building with older versions of GCC (2.95, for one) that don't
2341 like preprocessor directives inside macro arguments. Found by
2342 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
2343 - Switch weighted node selection rule from using a list of doubles
2344 to using a list of int64_t. This change should make the process
2345 slightly easier to debug and maintain. Needed to finish ticket 6538.
2347 o Code simplification and refactoring:
2348 - Move the generic "config" code into a new file, and have "config.c"
2349 hold only torrc- and state-related code. Resolves ticket 6823.
2350 - Move the core of our "choose a weighted element at random" logic
2351 into its own function, and give it unit tests. Now the logic is
2352 testable, and a little less fragile too.
2353 - Removed the testing_since field of node_t, which hasn't been used
2354 for anything since 0.2.0.9-alpha.
2356 o Documentation fixes:
2357 - Clarify that hidden services are TCP only. Fixes bug 6024.
2358 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
2362 Changes in version 0.2.3.22-rc - 2012-09-11
2363 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
2367 - Fix an assertion failure in tor_timegm() that could be triggered
2368 by a badly formatted directory object. Bug found by fuzzing with
2369 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2372 - Avoid segfault when starting up having run with an extremely old
2373 version of Tor and parsing its state file. Fixes bug 6801; bugfix
2377 Changes in version 0.2.2.39 - 2012-09-11
2378 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
2382 - Fix an assertion failure in tor_timegm() that could be triggered
2383 by a badly formatted directory object. Bug found by fuzzing with
2384 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2385 - Do not crash when comparing an address with port value 0 to an
2386 address policy. This bug could have been used to cause a remote
2387 assertion failure by or against directory authorities, or to
2388 allow some applications to crash clients. Fixes bug 6690; bugfix
2392 Changes in version 0.2.4.2-alpha - 2012-09-10
2393 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
2394 raises the default rate limiting even more, and makes the bootstrapping
2395 log messages less noisy.
2398 - Automatically forward the TCP ports of pluggable transport
2399 proxies using tor-fw-helper if PortForwarding is enabled. Implements
2403 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
2404 to 1GB/1GB. The previous defaults were intended to be "basically
2405 infinite", but it turns out they're now limiting our 100mbit+
2406 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
2407 last time we raised it).
2410 - Detect when we're running with a version of OpenSSL other than the
2411 one we compiled with. This has occasionally given people hard-to-
2413 - Log fewer lines at level "notice" about our OpenSSL and Libevent
2414 versions and capabilities when everything is going right. Resolves
2415 part of ticket 6736.
2416 - Directory authorities no long accept descriptors for any version of
2417 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
2418 These versions are insecure, unsupported, or both. Implements
2422 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
2423 to start with a triple-underscore so the controller won't touch it.
2424 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
2425 - Avoid segfault when starting up having run with an extremely old
2426 version of Tor and parsing its state file. Fixes bug 6801; bugfix
2428 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
2429 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
2430 - Don't follow the NULL pointer if microdescriptor generation fails.
2431 (This does not appear to be triggerable, but it's best to be safe.)
2432 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
2433 - Fix mis-declared dependencies on src/common/crypto.c and
2434 src/or/tor_main.c that could break out-of-tree builds under some
2435 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
2436 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
2437 6778; bugfix on 0.2.4.1-alpha.
2438 - Fix a harmless (in this case) build warning for implicitly
2439 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
2442 - Now that all versions before 0.2.2.x are disallowed, we no longer
2443 need to work around their missing features. Thus we can remove a
2444 bunch of compatibility code.
2447 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
2448 TCP ports to forward. In the past it only accepted two ports:
2449 the ORPort and the DirPort.
2452 Changes in version 0.2.4.1-alpha - 2012-09-05
2453 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
2454 bridgedb; lets relays use IPv6 addresses and directory authorities
2455 advertise them; and switches to a cleaner build interface.
2457 This is the first alpha release in a new series, so expect there to
2458 be bugs. Users who would rather test out a more stable branch should
2459 stay with 0.2.3.x for now.
2461 o Major features (bridges):
2462 - Bridges now report the pluggable transports they support to the
2463 bridge authority, so it can pass the supported transports on to
2464 bridgedb and/or eventually do reachability testing. Implements
2467 o Major features (IPv6):
2468 - Bridge authorities now accept IPv6 bridge addresses and include
2469 them in network status documents. Implements ticket 5534.
2470 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
2471 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
2472 to happen. Implements ticket 5535.
2473 - All kind of relays, not just bridges, can now advertise an IPv6
2474 OR port. Implements ticket 6362.
2475 - Directory authorities vote on IPv6 OR ports using the new consensus
2476 method 14. Implements ticket 6363.
2478 o Major features (build):
2479 - Switch to a nonrecursive Makefile structure. Now instead of each
2480 Makefile.am invoking other Makefile.am's, there is a master
2481 Makefile.am that includes the others. This change makes our build
2482 process slightly more maintainable, and improves parallelism for
2483 building with make -j. Original patch by Stewart Smith; various
2484 fixes by Jim Meyering.
2485 - Where available, we now use automake's "silent" make rules by
2486 default, so that warnings are easier to spot. You can get the old
2487 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
2489 o Minor features (code security and spec conformance):
2490 - Clear keys and key-derived material left on the stack in
2491 rendservice.c and rendclient.c. Check return value of
2492 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
2493 These fixes should make us more forward-secure against cold-boot
2494 attacks and the like. Fixes bug 2385.
2495 - Reject EXTEND cells sent to nonexistent streams. According to the
2496 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
2497 we were only checking for stream IDs that were currently in use.
2498 Found while hunting for more instances of bug 6271. Bugfix on
2499 0.0.2pre8, which introduced incremental circuit construction.
2501 o Minor features (streamlining);
2502 - No longer include the "opt" prefix when generating routerinfos
2503 or v2 directories: it has been needless since Tor 0.1.2. Closes
2505 - Remove some now-needless code that tried to aggressively flush
2506 OR connections as data was added to them. Since 0.2.0.1-alpha, our
2507 cell queue logic has saved us from the failure mode that this code
2508 was supposed to prevent. Removing this code will limit the number
2509 of baroque control flow paths through Tor's network logic. Reported
2510 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
2512 o Minor features (controller):
2513 - Add a "GETINFO signal/names" control port command. Implements
2515 - Provide default values for all options via "GETINFO config/defaults".
2516 Implements ticket 4971.
2518 o Minor features (IPv6):
2519 - New config option "AuthDirHasIPv6Connectivity 1" that directory
2520 authorities should set if they have IPv6 connectivity and want to
2521 do reachability tests for IPv6 relays. Implements feature 5974.
2522 - A relay with an IPv6 OR port now sends that address in NETINFO
2523 cells (in addition to its other address). Implements ticket 6364.
2525 o Minor features (log messages):
2526 - Omit the first heartbeat log message, because it never has anything
2527 useful to say, and it clutters up the bootstrapping messages.
2528 Resolves ticket 6758.
2529 - Don't log about reloading the microdescriptor cache at startup. Our
2530 bootstrap warnings are supposed to tell the user when there's a
2531 problem, and our bootstrap notices say when there isn't. Resolves
2532 ticket 6759; bugfix on 0.2.2.6-alpha.
2533 - Don't log "I learned some more directory information" when we're
2534 reading cached directory information. Reserve it for when new
2535 directory information arrives in response to a fetch. Resolves
2537 - Prevent rounding error in path bias counts when scaling
2538 them down, and use the correct scale factor default. Also demote
2539 some path bias related log messages down a level and make others
2540 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
2541 - We no longer warn so much when generating manpages from their
2544 o Code simplifications and refactoring:
2545 - Enhance our internal sscanf replacement so that we can eliminate
2546 the last remaining uses of the system sscanf. (Though those uses
2547 of sscanf were safe, sscanf itself is generally error prone, so
2548 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
2550 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
2551 - Move last_reachable and testing_since from routerinfo_t to node_t.
2552 Implements ticket 5529.
2553 - Add replaycache_t structure, functions and unit tests, then refactor
2554 rend_service_introduce() to be more clear to read, improve, debug,
2555 and test. Resolves bug 6177.
2556 - Finally remove support for malloc_good_size and malloc_usable_size.
2557 We had hoped that these functions would let us eke a little more
2558 memory out of our malloc implementation. Unfortunately, the only
2559 implementations that provided these functions are also ones that
2560 are already efficient about not overallocation: they never got us
2561 more than 7 or so bytes per allocation. Removing them saves us a
2562 little code complexity and a nontrivial amount of build complexity.
2565 - Tor maintainers now require Automake version 1.9 or later to build
2566 Tor from the Git repository. (Automake is not required when building
2567 from a source distribution.)
2570 Changes in version 0.2.3.21-rc - 2012-09-05
2571 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
2572 series. It fixes a trio of potential security bugs, fixes a bug where
2573 we were leaving some of the fast relays out of the microdescriptor
2574 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
2575 and cleans up other smaller issues.
2577 o Major bugfixes (security):
2578 - Tear down the circuit if we get an unexpected SENDME cell. Clients
2579 could use this trick to make their circuits receive cells faster
2580 than our flow control would have allowed, or to gum up the network,
2581 or possibly to do targeted memory denial-of-service attacks on
2582 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
2583 from July 2002, before the release of Tor 0.0.0. We had committed
2584 this patch previously, but we had to revert it because of bug 6271.
2585 Now that 6271 is fixed, this patch appears to work.
2586 - Reject any attempt to extend to an internal address. Without
2587 this fix, a router could be used to probe addresses on an internal
2588 network to see whether they were accepting connections. Fixes bug
2589 6710; bugfix on 0.0.8pre1.
2590 - Do not crash when comparing an address with port value 0 to an
2591 address policy. This bug could have been used to cause a remote
2592 assertion failure by or against directory authorities, or to
2593 allow some applications to crash clients. Fixes bug 6690; bugfix
2597 - Remove the upper bound on microdescriptor length. We were hitting
2598 the limit for routers with complex exit policies or family
2599 declarations, causing clients to not use them. Fixes the first
2600 piece of bug 6404; fix on 0.2.2.6-alpha.
2601 - Detect "ORPort 0" as meaning, uniformly, that we're not running
2602 as a relay. Previously, some of our code would treat the presence
2603 of any ORPort line as meaning that we should act like a relay,
2604 even though our new listener code would correctly not open any
2605 ORPorts for ORPort 0. Similar bugs in other Port options are also
2606 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
2609 - Avoid a pair of double-free and use-after-mark bugs that can
2610 occur with certain timings in canceled and re-received DNS
2611 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
2612 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
2613 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
2614 - Allow one-hop directory fetching circuits the full "circuit build
2615 timeout" period, rather than just half of it, before failing them
2616 and marking the relay down. This fix should help reduce cases where
2617 clients declare relays (or worse, bridges) unreachable because
2618 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
2619 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
2621 - Authorities no longer include any router in their microdescriptor
2622 consensuses for which they couldn't generate or agree on a
2623 microdescriptor. Fixes the second piece of bug 6404; fix on
2625 - Detect and reject attempts to specify both "FooPort" and
2626 "FooPort 0" in the same configuration domain. (It's still okay
2627 to have a FooPort in your configuration file, and use "FooPort 0"
2628 on the command line to disable it.) Fixes the second half of bug
2629 6507; bugfix on 0.2.3.3-alpha.
2630 - Make wildcarded addresses (that is, ones beginning with "*.") work
2631 when provided via the controller's MapAddress command. Previously,
2632 they were accepted, but we never actually noticed that they were
2633 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
2634 - Avoid crashing on a malformed state file where EntryGuardPathBias
2635 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
2636 - Add a (probably redundant) memory clear between iterations of
2637 the router status voting loop, to prevent future coding errors
2638 where data might leak between iterations of the loop. Resolves
2641 o Minor bugfixes (log messages):
2642 - Downgrade "set buildtimeout to low value" messages to "info"
2643 severity; they were never an actual problem, there was never
2644 anything reasonable to do about them, and they tended to spam logs
2645 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
2646 - Downgrade path-bias warning messages to "info". We'll try to get
2647 them working better in 0.2.4. Add internal circuit construction
2648 state to protect against the noisy warn message "Unexpectedly high
2649 circuit_successes". Also add some additional rate-limited notice
2650 messages to help determine the root cause of the warn. Fixes bug
2651 6475. Bugfix against 0.2.3.17-beta.
2652 - Move log message when unable to find a microdesc in a routerstatus
2653 entry to parse time. Previously we'd spam this warning every time
2654 we tried to figure out which microdescriptors to download. Fixes
2655 the third piece of bug 6404; fix on 0.2.3.18-rc.
2658 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
2659 change when the authority is deciding whether to accept a newly
2660 uploaded descriptor. Implements ticket 6423.
2661 - Add missing documentation for consensus and microdesc files.
2662 Resolves ticket 6732.
2665 Changes in version 0.2.2.38 - 2012-08-12
2666 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
2667 attack that could in theory leak path information.
2670 - Avoid an uninitialized memory read when reading a vote or consensus
2671 document that has an unrecognized flavor name. This read could
2672 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2673 - Try to leak less information about what relays a client is
2674 choosing to a side-channel attacker. Previously, a Tor client would
2675 stop iterating through the list of available relays as soon as it
2676 had chosen one, thus finishing a little earlier when it picked
2677 a router earlier in the list. If an attacker can recover this
2678 timing information (nontrivial but not proven to be impossible),
2679 they could learn some coarse-grained information about which relays
2680 a client was picking (middle nodes in particular are likelier to
2681 be affected than exits). The timing attack might be mitigated by
2682 other factors (see bug 6537 for some discussion), but it's best
2683 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2686 Changes in version 0.2.3.20-rc - 2012-08-05
2687 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
2688 series. It fixes a pair of code security bugs and a potential anonymity
2689 issue, updates our RPM spec files, and cleans up other smaller issues.
2692 - Avoid read-from-freed-memory and double-free bugs that could occur
2693 when a DNS request fails while launching it. Fixes bug 6480;
2694 bugfix on 0.2.0.1-alpha.
2695 - Avoid an uninitialized memory read when reading a vote or consensus
2696 document that has an unrecognized flavor name. This read could
2697 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2698 - Try to leak less information about what relays a client is
2699 choosing to a side-channel attacker. Previously, a Tor client would
2700 stop iterating through the list of available relays as soon as it
2701 had chosen one, thus finishing a little earlier when it picked
2702 a router earlier in the list. If an attacker can recover this
2703 timing information (nontrivial but not proven to be impossible),
2704 they could learn some coarse-grained information about which relays
2705 a client was picking (middle nodes in particular are likelier to
2706 be affected than exits). The timing attack might be mitigated by
2707 other factors (see bug 6537 for some discussion), but it's best
2708 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2711 - Try to make the warning when giving an obsolete SOCKSListenAddress
2712 a little more useful.
2713 - Terminate active server managed proxies if Tor stops being a
2714 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
2715 - Provide a better error message about possible OSX Asciidoc failure
2716 reasons. Fixes bug 6436.
2717 - Warn when Tor is configured to use accounting in a way that can
2718 link a hidden service to some other hidden service or public
2719 address. Resolves ticket 6490.
2722 - Check return value of fputs() when writing authority certificate
2723 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
2724 - Ignore ServerTransportPlugin lines when Tor is not configured as
2725 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
2726 - When disabling guards for having too high a proportion of failed
2727 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
2731 - Update our default RPM spec files to work with mock and rpmbuild
2732 on RHEL/Fedora. They have an updated set of dependencies and
2733 conflicts, a fix for an ancient typo when creating the "_tor"
2734 user, and better instructions. Thanks to Ondrej Mikle for the
2735 patch series. Fixes bug 6043.
2738 - Make it possible to set the TestingTorNetwork configuration
2739 option using AlternateDirAuthority and AlternateBridgeAuthority
2740 as an alternative to setting DirServer. Addresses ticket 6377.
2743 - Clarify the documentation for the Alternate*Authority options.
2745 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
2747 o Code simplification and refactoring:
2748 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
2749 10 lines. Also, don't nest them. Doing so in the past has
2750 led to hard-to-debug code. The new style is to use the
2751 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
2754 Changes in version 0.2.3.19-rc - 2012-07-06
2755 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
2756 series. It fixes the compile on Windows, reverts to a GeoIP database
2757 that isn't as broken, and fixes a flow control bug that has been around
2758 since the beginning of Tor.
2761 - Fix a bug handling SENDME cells on nonexistent streams that could
2762 result in bizarre window values. Report and patch contributed
2763 pseudonymously. Fixes part of bug 6271. This bug was introduced
2764 before the first Tor release, in svn commit r152.
2765 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
2766 June 2012 database, Maxmind marked many Tor relays as country "A1",
2767 which will cause risky behavior for clients that set EntryNodes
2768 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
2769 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
2770 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
2773 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
2774 bugfix on 0.2.1.10-alpha.
2777 Changes in version 0.2.3.18-rc - 2012-06-28
2778 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
2779 series. It fixes a few smaller bugs, but generally appears stable.
2780 Please test it and let us know whether it is!
2783 - Allow wildcarded mapaddress targets to be specified on the
2784 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
2785 - Make our linker option detection code more robust against linkers
2786 such as on FreeBSD 8, where a bad combination of options completes
2787 successfully but makes an unrunnable binary. Fixes bug 6173;
2788 bugfix on 0.2.3.17-beta.
2790 o Minor bugfixes (on 0.2.2.x and earlier):
2791 - Avoid a false positive in the util/threads unit test by increasing
2792 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
2793 - Replace "Sending publish request" log messages with "Launching
2794 upload", so that they no longer confusingly imply that we're
2795 sending something to a directory we might not even be connected
2796 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
2797 - Make sure to set *socket_error in all error cases in
2798 connection_connect(), so it can't produce a warning about
2799 errno being zero from errno_to_orconn_end_reason(). Bugfix on
2800 0.2.1.1-alpha; resolves ticket 6028.
2801 - Downgrade "Got a certificate, but we already have it" log messages
2802 from warning to info, except when we're a dirauth. Fixes bug 5238;
2803 bugfix on 0.2.1.7-alpha.
2804 - When checking for requested signatures on the latest consensus
2805 before serving it to a client, make sure to check the right
2806 consensus flavor. Bugfix on 0.2.2.6-alpha.
2807 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
2808 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
2810 o Minor bugfixes (on 0.2.3.x):
2811 - Make format_helper_exit_status() avoid unnecessary space padding
2812 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
2814 - Downgrade a message about cleaning the microdescriptor cache to
2815 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
2816 - Log a BUG message at severity INFO if we have a networkstatus with
2817 a missing entry for some microdescriptor. Continues on a patch
2819 - Improve the log message when a managed proxy fails to launch. Fixes
2820 bug 5099; bugfix on 0.2.3.6-alpha.
2821 - Don't do DNS lookups when parsing corrupted managed proxy protocol
2822 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
2823 - When formatting wildcarded address mappings for the controller,
2824 be sure to include "*." as appropriate. Partially fixes bug 6244;
2825 bugfix on 0.2.3.9-alpha.
2826 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
2827 Bugfix on 0.2.3.13-alpha.
2828 - Stop logging messages about running with circuit timeout learning
2829 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
2830 - Disable a spurious warning about reading on a marked and flushing
2831 connection. We shouldn't be doing that, but apparently we
2832 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
2833 - Fix a bug that stopped AllowDotExit from working on addresses
2834 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
2837 o Code simplification, refactoring, unit tests:
2838 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
2839 Libevent's notion of cached time when possible.
2840 - Remove duplicate code for invoking getrlimit() from control.c.
2841 - Add a unit test for the environment_variable_names_equal function.
2844 - Document the --defaults-torrc option, and the new (in 0.2.3)
2845 semantics for overriding, extending, and clearing lists of
2846 options. Closes bug 4748.
2849 Changes in version 0.2.3.17-beta - 2012-06-15
2850 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
2851 gets our TLS handshake back on track for being able to blend in with
2852 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
2853 with Vidalia, and otherwise continues to get us closer to a release
2857 - Enable gcc and ld hardening by default. Resolves ticket 5210.
2858 - Update TLS cipher list to match Firefox 8 and later. Resolves
2860 - Implement the client side of proposal 198: remove support for
2861 clients falsely claiming to support standard ciphersuites that
2862 they can actually provide. As of modern OpenSSL versions, it's not
2863 necessary to fake any standard ciphersuite, and doing so prevents
2864 us from using better ciphersuites in the future, since servers
2865 can't know whether an advertised ciphersuite is really supported or
2866 not. Some hosts -- notably, ones with very old versions of OpenSSL
2867 or where OpenSSL has been built with ECC disabled -- will stand
2868 out because of this change; TBB users should not be affected.
2871 - Change the default value for DynamicDHGroups (introduced in
2872 0.2.3.9-alpha) to 0. This feature can make Tor relays less
2873 identifiable by their use of the mod_ssl DH group, but at
2874 the cost of some usability (#4721) and bridge tracing (#6087)
2875 regressions. Resolves ticket 5598.
2876 - Send a CRLF at the end of each STATUS_* control protocol event. This
2877 bug tickled a bug in Vidalia which would make it freeze. Fixes
2878 bug 6094; bugfix on 0.2.3.16-alpha.
2881 - Disable writing on marked-for-close connections when they are
2882 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
2883 bug 5263; bugfix on 0.0.2pre13, where we first added a special
2884 case for flushing marked connections.
2885 - Detect SSL handshake even when the initial attempt to write the
2886 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
2887 - Change the AllowDotExit rules so they should actually work.
2888 We now enforce AllowDotExit only immediately after receiving an
2889 address via SOCKS or DNSPort: other sources are free to provide
2890 .exit addresses after the resolution occurs. Fixes bug 3940;
2891 bugfix on 0.2.2.1-alpha.
2892 - Fix a (harmless) integer overflow in cell statistics reported by
2893 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2894 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
2895 right places and never depends on the consensus parameters or
2896 computes adaptive timeouts when it is disabled. Fixes bug 5049;
2897 bugfix on 0.2.2.14-alpha.
2898 - When building Tor on Windows with -DUNICODE (not default), ensure
2899 that error messages, filenames, and DNS server names are always
2900 NUL-terminated when we convert them to a single-byte encoding.
2901 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2902 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
2903 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
2904 - Fix an edge case where TestingTorNetwork is set but the authorities
2905 and relays all have an uptime of zero, where the private Tor network
2906 could briefly lack support for hidden services. Fixes bug 3886;
2907 bugfix on 0.2.2.18-alpha.
2908 - Correct the manpage's descriptions for the default values of
2909 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
2911 - Fix the documentation for the --hush and --quiet command line
2912 options, which changed their behavior back in 0.2.3.3-alpha.
2913 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
2917 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2918 more information to it, so that we can track it down in case it
2919 returns again. Mitigates bug 5235.
2920 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2921 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2922 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2923 - Warn the user when HTTPProxy, but no other proxy type, is
2924 configured. This can cause surprising behavior: it doesn't send
2925 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2926 directory traffic only. Resolves ticket 4663.
2927 - Issue a notice if a guard completes less than 40% of your circuits.
2928 Threshold is configurable by torrc option PathBiasNoticeRate and
2929 consensus parameter pb_noticepct. There is additional, off-by-
2930 default code to disable guards which fail too many circuits.
2931 Addresses ticket 5458.
2932 - Update to the June 6 2012 Maxmind GeoLite Country database.
2934 o Code simplifications and refactoring:
2935 - Remove validate_pluggable_transports_config(): its warning
2936 message is now handled by connection_or_connect().
2939 Changes in version 0.2.2.37 - 2012-06-06
2940 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2941 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2945 - Work around a bug in OpenSSL that broke renegotiation with TLS
2946 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2947 the v2 Tor connection protocol when both sides were using OpenSSL
2948 1.0.1 would fail. Resolves ticket 6033.
2949 - When waiting for a client to renegotiate, don't allow it to add
2950 any bytes to the input buffer. This fixes a potential DoS issue.
2951 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2952 - Fix an edge case where if we fetch or publish a hidden service
2953 descriptor, we might build a 4-hop circuit and then use that circuit
2954 for exiting afterwards -- even if the new last hop doesn't obey our
2955 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2958 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2959 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2962 - Tell GCC and Clang to check for any errors in format strings passed
2963 to the tor_v*(print|scan)f functions.
2966 Changes in version 0.2.3.16-alpha - 2012-06-05
2967 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
2968 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2969 currently). It also fixes a variety of smaller bugs and other cleanups
2970 that get us closer to a release candidate.
2972 o Major bugfixes (general):
2973 - Work around a bug in OpenSSL that broke renegotiation with TLS
2974 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2975 the v2 Tor connection protocol when both sides were using OpenSSL
2976 1.0.1 would fail. Resolves ticket 6033.
2977 - When waiting for a client to renegotiate, don't allow it to add
2978 any bytes to the input buffer. This fixes a potential DoS issue.
2979 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2980 - Pass correct OR address to managed proxies (like obfsproxy),
2981 even when ORListenAddress is used. Fixes bug 4865; bugfix on
2983 - The advertised platform of a router now includes only its operating
2984 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
2985 service pack level (for Windows) or its CPU architecture (for Unix).
2986 We also no longer include the "git-XYZ" tag in the version. Resolves
2989 o Major bugfixes (clients):
2990 - If we are unable to find any exit that supports our predicted ports,
2991 stop calling them predicted, so that we don't loop and build
2992 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2993 which introduced predicted ports.
2994 - Fix an edge case where if we fetch or publish a hidden service
2995 descriptor, we might build a 4-hop circuit and then use that circuit
2996 for exiting afterwards -- even if the new last hop doesn't obey our
2997 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2998 - Check at each new consensus whether our entry guards were picked
2999 long enough ago that we should rotate them. Previously, we only
3000 did this check at startup, which could lead to us holding a guard
3001 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
3002 - When fetching a bridge descriptor from a bridge authority,
3003 always do so anonymously, whether we have been able to open
3004 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
3005 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
3006 but we'll need to wait for bug 6010 before it's actually usable.
3008 o Major bugfixes (directory authorities):
3009 - When computing weight parameters, behave more robustly in the
3010 presence of a bad bwweightscale value. Previously, the authorities
3011 would crash if they agreed on a sufficiently broken weight_scale
3012 value: now, they use a reasonable default and carry on. Partial
3013 fix for 5786; bugfix on 0.2.2.17-alpha.
3014 - Check more thoroughly to prevent a rogue authority from
3015 double-voting on any consensus directory parameter. Previously,
3016 authorities would crash in this case if the total number of
3017 votes for any parameter exceeded the number of active voters,
3018 but would let it pass otherwise. Partial fix for bug 5786; bugfix
3022 - Rate-limit log messages when asked to connect anonymously to
3023 a private address. When these hit, they tended to hit fast and
3024 often. Also, don't bother trying to connect to addresses that we
3025 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
3026 reply makes us think we have been lied to, even when the address the
3027 client tried to connect to was "localhost." Resolves ticket 2822.
3028 - Allow packagers to insert an extra string in server descriptor
3029 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
3030 Resolves the rest of ticket 2988.
3031 - Raise the threshold of server descriptors needed (75%) and exit
3032 server descriptors needed (50%) before we will declare ourselves
3033 bootstrapped. This will make clients start building circuits a
3034 little later, but makes the initially constructed circuits less
3035 skewed and less in conflict with further directory fetches. Fixes
3037 - Close any connection that sends unrecognized junk before the
3038 handshake. Solves an issue noted in bug 4369.
3039 - Improve log messages about managed transports. Resolves ticket 5070.
3040 - Tag a bridge's descriptor as "never to be sent unencrypted".
3041 This shouldn't matter, since bridges don't open non-anonymous
3042 connections to the bridge authority and don't allow unencrypted
3043 directory connections from clients, but we might as well make
3044 sure. Closes bug 5139.
3045 - Expose our view of whether we have gone dormant to the controller,
3046 via a new "GETINFO dormant" value. Torbutton and other controllers
3047 can use this to avoid doing periodic requests through Tor while
3048 it's dormant (bug 4718). Fixes bug 5954.
3049 - Tell GCC and Clang to check for any errors in format strings passed
3050 to the tor_v*(print|scan)f functions.
3051 - Update to the May 1 2012 Maxmind GeoLite Country database.
3053 o Minor bugfixes (already included in 0.2.2.36):
3054 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
3055 Fixes bug 5346; bugfix on 0.0.8pre3.
3056 - Correct parsing of certain date types in parse_http_time().
3057 Without this patch, If-Modified-Since would behave
3058 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
3059 Esteban Manchado Velázques.
3060 - Make our number-parsing functions always treat too-large values
3061 as an error, even when those values exceed the width of the
3062 underlying type. Previously, if the caller provided these
3063 functions with minima or maxima set to the extreme values of the
3064 underlying integer type, these functions would return those
3065 values on overflow rather than treating overflow as an error.
3066 Fixes part of bug 5786; bugfix on 0.0.9.
3067 - If we hit the error case where routerlist_insert() replaces an
3068 existing (old) server descriptor, make sure to remove that
3069 server descriptor from the old_routers list. Fix related to bug
3070 1776. Bugfix on 0.2.2.18-alpha.
3071 - Clarify the behavior of MaxCircuitDirtiness with hidden service
3072 circuits. Fixes issue 5259.
3074 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
3075 - Prevent a null-pointer dereference when receiving a data cell
3076 for a nonexistent stream when the circuit in question has an
3077 empty deliver window. We don't believe this is triggerable,
3078 since we don't currently allow deliver windows to become empty,
3079 but the logic is tricky enough that it's better to make the code
3080 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
3081 - Fix a memory leak when trying to launch a DNS request when the
3082 network is disabled or the nameservers are unconfigurable. Fixes
3083 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
3084 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
3085 - Don't hold a Windows file handle open for every file mapping;
3086 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
3088 - Avoid O(n^2) performance characteristics when parsing a large
3089 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
3090 - Format more doubles with %f, not %lf. Patch from grarpamp to make
3091 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
3093 - Make our replacement implementation of strtok_r() compatible with
3094 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
3095 bugfix on 0.2.2.1-alpha.
3096 - Fix a NULL-pointer dereference on a badly formed
3097 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
3098 bugfix on 0.2.2.9-alpha.
3099 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
3100 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
3101 - Defensively refactor rend_mid_rendezvous() so that protocol
3102 violations and length checks happen in the beginning. Fixes
3104 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
3105 that IPv6 stuff will compile on MSVC, and compilation issues
3106 will be easier to track down. Fixes bug 5861.
3108 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
3109 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
3110 resource exhaustion, so that clients can adjust their load to
3111 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
3112 started using END_STREAM_REASON_RESOURCELIMIT.
3113 - Don't check for whether the address we're using for outbound
3114 connections has changed until after the outbound connection has
3115 completed. On Windows, getsockname() doesn't succeed until the
3116 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
3117 - If the configuration tries to set MyFamily on a bridge, refuse to
3118 do so, and warn about the security implications. Fixes bug 4657;
3119 bugfix on 0.2.0.3-alpha.
3120 - If the client fails to set a reasonable set of ciphersuites
3121 during its v2 handshake renegotiation, allow the renegotiation to
3122 continue nevertheless (i.e. send all the required certificates).
3123 Fixes bug 4591; bugfix on 0.2.0.20-rc.
3124 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
3125 option is set to 0 (which Vidalia version 0.2.16 now does when
3126 a SAVECONF attempt fails), perform other actions that SIGHUP
3127 usually causes (like reopening the logs). Fixes bug 5095; bugfix
3129 - If we fail to write a microdescriptor to the disk cache, do not
3130 continue replacing the old microdescriptor file. Fixes bug 2954;
3131 bugfix on 0.2.2.6-alpha.
3132 - Exit nodes don't need to fetch certificates for authorities that
3133 they don't recognize; only directory authorities, bridges,
3134 and caches need to do that. Fixes part of bug 2297; bugfix on
3136 - Correctly handle checking the permissions on the parent
3137 directory of a control socket in the root directory. Bug found
3138 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
3140 - When told to add a bridge with the same digest as a preexisting
3141 bridge but a different addr:port, change the addr:port as
3142 requested. Previously we would not notice the change. Fixes half
3143 of bug 5603; fix on 0.2.2.26-beta.
3144 - End AUTHCHALLENGE error messages (in the control protocol) with
3145 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
3147 o Minor bugfixes (on 0.2.3.x):
3148 - Turn an assertion (that the number of handshakes received as a
3149 server is not < 1) into a warning. Fixes bug 4873; bugfix on
3151 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
3152 we had reversed them when the answer was cached.) Fixes bug
3153 5723; bugfix on 0.2.3.1-alpha.
3154 - Work correctly on Linux systems with accept4 support advertised in
3155 their headers, but without accept4 support in the kernel. Fix
3156 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
3157 - When told to add a bridge with the same addr:port as a preexisting
3158 bridge but a different transport, change the transport as
3159 requested. Previously we would not notice the change. Fixes half
3160 of bug 5603; fix on 0.2.3.2-alpha.
3161 - Avoid a "double-reply" warning when replying to a SOCKS request
3162 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
3163 bugfix on 0.2.3.4-alpha.
3164 - Fix a bug where a bridge authority crashes if it has seen no
3165 directory requests when it's time to write statistics to disk.
3166 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
3168 - Don't try to open non-control listeners when DisableNetwork is set.
3169 Previously, we'd open all listeners, then immediately close them.
3170 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
3171 - Don't abort the managed proxy protocol if the managed proxy
3172 sends us an unrecognized line; ignore it instead. Fixes bug
3173 5910; bugfix on 0.2.3.9-alpha.
3174 - Fix a compile warning in crypto.c when compiling with clang 3.1.
3175 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
3176 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
3177 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
3178 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
3179 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
3180 - Resolve numerous small warnings and build issues with MSVC. Resolves
3183 o Documentation fixes:
3184 - Improve the manual's documentation for the NT Service command-line
3185 options. Addresses ticket 3964.
3186 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
3187 - Document the changes to the ORPort and DirPort options, and the
3188 fact that {OR/Dir}ListenAddress is now unnecessary (and
3189 therefore deprecated). Resolves ticket 5597.
3192 - Remove the torrc.bridge file: we don't use it for anything, and
3193 it had become badly desynchronized from torrc.sample. Resolves
3197 Changes in version 0.2.2.36 - 2012-05-24
3198 Tor 0.2.2.36 updates the addresses for two of the eight directory
3199 authorities, fixes some potential anonymity and security issues,
3200 and fixes several crash bugs.
3202 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
3203 known flaws, and nobody should be using them. You should upgrade. If
3204 you're using a Linux or BSD and its packages are obsolete, stop using
3205 those packages and upgrade anyway.
3207 o Directory authority changes:
3208 - Change IP address for maatuska (v3 directory authority).
3209 - Change IP address for ides (v3 directory authority), and rename
3213 - When building or running with any version of OpenSSL earlier
3214 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
3215 versions have a bug (CVE-2011-4576) in which their block cipher
3216 padding includes uninitialized data, potentially leaking sensitive
3217 information to any peer with whom they make a SSLv3 connection. Tor
3218 does not use SSL v3 by default, but a hostile client or server
3219 could force an SSLv3 connection in order to gain information that
3220 they shouldn't have been able to get. The best solution here is to
3221 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
3222 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
3223 to make sure that the bug can't happen.
3224 - Never use a bridge or a controller-supplied node as an exit, even
3225 if its exit policy allows it. Found by wanoskarnet. Fixes bug
3226 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
3227 and 0.2.0.3-alpha (for bridge-purpose descriptors).
3228 - Only build circuits if we have a sufficient threshold of the total
3229 descriptors that are marked in the consensus with the "Exit"
3230 flag. This mitigates an attack proposed by wanoskarnet, in which
3231 all of a client's bridges collude to restrict the exit nodes that
3232 the client knows about. Fixes bug 5343.
3233 - Provide controllers with a safer way to implement the cookie
3234 authentication mechanism. With the old method, if another locally
3235 running program could convince a controller that it was the Tor
3236 process, then that program could trick the controller into telling
3237 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
3238 authentication method uses a challenge-response approach to prevent
3239 this attack. Fixes bug 5185; implements proposal 193.
3242 - Avoid logging uninitialized data when unable to decode a hidden
3243 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
3244 - Avoid a client-side assertion failure when receiving an INTRODUCE2
3245 cell on a general purpose circuit. Fixes bug 5644; bugfix on
3247 - Fix builds when the path to sed, openssl, or sha1sum contains
3248 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3250 - Correct our replacements for the timeradd() and timersub() functions
3251 on platforms that lack them (for example, Windows). The timersub()
3252 function is used when expiring circuits, while timeradd() is
3253 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
3254 bugfix on 0.2.2.24-alpha.
3255 - Fix the SOCKET_OK test that we use to tell when socket
3256 creation fails so that it works on Win64. Fixes part of bug 4533;
3257 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
3260 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
3261 Fixes bug 5346; bugfix on 0.0.8pre3.
3262 - Make our number-parsing functions always treat too-large values
3263 as an error, even when those values exceed the width of the
3264 underlying type. Previously, if the caller provided these
3265 functions with minima or maxima set to the extreme values of the
3266 underlying integer type, these functions would return those
3267 values on overflow rather than treating overflow as an error.
3268 Fixes part of bug 5786; bugfix on 0.0.9.
3269 - Older Linux kernels erroneously respond to strange nmap behavior
3270 by having accept() return successfully with a zero-length
3271 socket. When this happens, just close the connection. Previously,
3272 we would try harder to learn the remote address: but there was
3273 no such remote address to learn, and our method for trying to
3274 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3275 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3276 - Correct parsing of certain date types in parse_http_time().
3277 Without this patch, If-Modified-Since would behave
3278 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
3279 Esteban Manchado Velázques.
3280 - Change the BridgePassword feature (part of the "bridge community"
3281 design, which is not yet implemented) to use a time-independent
3282 comparison. The old behavior might have allowed an adversary
3283 to use timing to guess the BridgePassword value. Fixes bug 5543;
3284 bugfix on 0.2.0.14-alpha.
3285 - Detect and reject certain misformed escape sequences in
3286 configuration values. Previously, these values would cause us
3287 to crash if received in a torrc file or over an authenticated
3288 control port. Bug found by Esteban Manchado Velázquez, and
3289 independently by Robert Connolly from Matta Consulting who further
3290 noted that it allows a post-authentication heap overflow. Patch
3291 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3292 bugfix on 0.2.0.16-alpha.
3293 - Fix a compile warning when using the --enable-openbsd-malloc
3294 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3295 - During configure, detect when we're building with clang version
3296 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3297 CFLAGS. clang doesn't support them yet.
3298 - When sending an HTTP/1.1 proxy request, include a Host header.
3299 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
3300 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
3301 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
3302 - If we hit the error case where routerlist_insert() replaces an
3303 existing (old) server descriptor, make sure to remove that
3304 server descriptor from the old_routers list. Fix related to bug
3305 1776. Bugfix on 0.2.2.18-alpha.
3307 o Minor bugfixes (documentation and log messages):
3308 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3309 Fixes bug 4856; bugfix on Tor 0.0.6.
3310 - Update "ClientOnly" man page entry to explain that there isn't
3311 really any point to messing with it. Resolves ticket 5005.
3312 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3313 directory authority option (introduced in Tor 0.2.2.34).
3314 - Downgrade the "We're missing a certificate" message from notice
3315 to info: people kept mistaking it for a real problem, whereas it
3316 is seldom the problem even when we are failing to bootstrap. Fixes
3317 bug 5067; bugfix on 0.2.0.10-alpha.
3318 - Correctly spell "connect" in a log message on failure to create a
3319 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
3320 - Clarify the behavior of MaxCircuitDirtiness with hidden service
3321 circuits. Fixes issue 5259.
3324 - Directory authorities now reject versions of Tor older than
3325 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3326 inclusive. These versions accounted for only a small fraction of
3327 the Tor network, and have numerous known security issues. Resolves
3329 - Update to the May 1 2012 Maxmind GeoLite Country database.
3332 - When sending or relaying a RELAY_EARLY cell, we used to convert
3333 it to a RELAY cell if the connection was using the v1 link
3334 protocol. This was a workaround for older versions of Tor, which
3335 didn't handle RELAY_EARLY cells properly. Now that all supported
3336 versions can handle RELAY_EARLY cells, and now that we're enforcing
3337 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3338 remove this workaround. Addresses bug 4786.
3341 Changes in version 0.2.3.15-alpha - 2012-04-30
3342 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
3343 the development branch build on Windows again.
3345 o Minor bugfixes (on 0.2.2.x and earlier):
3346 - Make sure that there are no unhandled pending TLS errors before
3347 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
3348 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
3349 Bugfix on 0.1.0.5-rc; fixes bug 4528.
3350 - Fix an assert that directory authorities could trigger on sighup
3351 during some configuration state transitions. We now don't treat
3352 it as a fatal error when the new descriptor we just generated in
3353 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
3354 - After we pick a directory mirror, we would refuse to use it if
3355 it's in our ExcludeExitNodes list, resulting in mysterious failures
3356 to bootstrap for people who just wanted to avoid exiting from
3357 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
3358 - When building with --enable-static-tor on OpenBSD, do not
3359 erroneously attempt to link -lrt. Fixes bug 5103.
3361 o Minor bugfixes (on 0.2.3.x):
3362 - When Tor is built with kernel headers from a recent (last few
3363 years) Linux kernel, do not fail to run on older (pre-2.6.28
3364 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
3365 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
3367 - Fix compilation with miniupnpc version 1.6; patch from
3368 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
3369 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
3370 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
3371 - Fix compilation on platforms without unistd.h, or where environ
3372 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
3375 - Directory authorities are now a little more lenient at accepting
3376 older router descriptors, or newer router descriptors that don't
3377 make big changes. This should help ameliorate past and future
3378 issues where routers think they have uploaded valid descriptors,
3379 but the authorities don't think so. Fix for ticket 2479.
3380 - Make the code that clients use to detect an address change be
3381 IPv6-aware, so that it won't fill clients' logs with error
3382 messages when trying to get the IPv4 address of an IPv6
3383 connection. Implements ticket 5537.
3386 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
3387 authorities needed to use it for a while to keep the network working
3388 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
3389 that was six months ago. As of now, it should no longer be needed
3393 Changes in version 0.2.3.14-alpha - 2012-04-23
3394 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
3395 candidate. It also dramatically speeds up AES: fast relays should
3396 consider switching to the newer OpenSSL library.
3398 o Directory authority changes:
3399 - Change IP address for ides (v3 directory authority), and rename
3403 - Avoid logging uninitialized data when unable to decode a hidden
3404 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
3405 - Avoid a client-side assertion failure when receiving an INTRODUCE2
3406 cell on a general purpose circuit. Fixes bug 5644; bugfix on
3408 - If authorities are unable to get a v2 consensus document from other
3409 directory authorities, they no longer fall back to fetching
3410 them from regular directory caches. Fixes bug 5635; bugfix on
3411 0.2.2.26-beta, where routers stopped downloading v2 consensus
3413 - When we start a Tor client with a normal consensus already cached,
3414 be willing to download a microdescriptor consensus. Fixes bug 4011;
3415 fix on 0.2.3.1-alpha.
3417 o Major features (performance):
3418 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
3419 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
3420 vectorized AES implementations as appropriate. These can be much,
3421 much faster than other AES implementations.
3423 o Minor bugfixes (0.2.2.x and earlier):
3424 - Don't launch more than 10 service-side introduction-point circuits
3425 for a hidden service in five minutes. Previously, we would consider
3426 launching more introduction-point circuits if at least one second
3427 had passed without any introduction-point circuits failing. Fixes
3428 bug 4607; bugfix on 0.0.7pre1.
3429 - Change the BridgePassword feature (part of the "bridge community"
3430 design, which is not yet implemented) to use a time-independent
3431 comparison. The old behavior might have allowed an adversary
3432 to use timing to guess the BridgePassword value. Fixes bug 5543;
3433 bugfix on 0.2.0.14-alpha.
3434 - Enforce correct return behavior of tor_vsscanf() when the '%%'
3435 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
3436 - When sending an HTTP/1.1 proxy request, include a Host header.
3437 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
3438 - Don't log that we have "decided to publish new relay descriptor"
3439 unless we are actually publishing a descriptor. Fixes bug 3942;
3440 bugfix on 0.2.2.28-beta.
3442 o Minor bugfixes (0.2.3.x):
3443 - Fix a bug where a bridge authority crashes (on a failed assert)
3444 if it has seen no directory requests when it's time to write
3445 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
3446 - Fix bug stomping on ORPort option NoListen and ignoring option
3447 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
3448 - In the testsuite, provide a large enough buffer in the tor_sscanf
3449 unit test. Otherwise we'd overrun that buffer and crash during
3450 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
3452 - Make sure we create the keys directory if it doesn't exist and we're
3453 about to store the dynamic Diffie-Hellman parameters. Fixes bug
3454 5572; bugfix on 0.2.3.13-alpha.
3455 - Fix a small memory leak when trying to decode incorrect base16
3456 authenticator during SAFECOOKIE authentication. Found by
3457 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
3460 - Add more information to a log statement that might help track down
3461 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
3462 non-IP address" messages (or any Bug messages, for that matter!),
3463 please let us know about it.
3464 - Relays now understand an IPv6 address when they get one from a
3465 directory server. Resolves ticket 4875.
3466 - Resolve IPv6 addresses in bridge and entry statistics to country
3467 code "??" which means we at least count them. Resolves ticket 5053;
3468 improves on 0.2.3.9-alpha.
3469 - Update to the April 3 2012 Maxmind GeoLite Country database.
3470 - Begin a doc/state-contents.txt file to explain the contents of
3471 the Tor state file. Fixes bug 2987.
3473 o Default torrc changes:
3474 - Stop listing "socksport 9050" in torrc.sample. We open a socks
3475 port on 9050 by default anyway, so this should not change anything
3477 - Stop mentioning the deprecated *ListenAddress options in
3478 torrc.sample. Fixes bug 5438.
3479 - Document unit of bandwidth related options in sample torrc.
3483 - The "torify" script no longer supports the "tsocks" socksifier
3484 tool, since tsocks doesn't support DNS and UDP right for Tor.
3485 Everyone should be using torsocks instead. Fixes bugs 3530 and
3486 5180. Based on a patch by "ugh".
3489 - Change the symmetric cipher interface so that creating and
3490 initializing a stream cipher are no longer separate functions.
3491 - Remove all internal support for unpadded RSA. We never used it, and
3492 it would be a bad idea to start.
3495 Changes in version 0.2.3.13-alpha - 2012-03-26
3496 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
3497 in managed pluggable transports, as well as providing other cleanups
3498 that get us closer to a release candidate.
3500 o Directory authority changes:
3501 - Change IP address for maatuska (v3 directory authority).
3504 - Provide controllers with a safer way to implement the cookie
3505 authentication mechanism. With the old method, if another locally
3506 running program could convince a controller that it was the Tor
3507 process, then that program could trick the controller into telling
3508 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
3509 authentication method uses a challenge-response approach to prevent
3510 this attack. Fixes bug 5185, implements proposal 193.
3511 - Never use a bridge or a controller-supplied node as an exit, even
3512 if its exit policy allows it. Found by wanoskarnet. Fixes bug
3513 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
3514 and 0.2.0.3-alpha (for bridge-purpose descriptors).
3515 - Only build circuits if we have a sufficient threshold of the total
3516 descriptors that are marked in the consensus with the "Exit"
3517 flag. This mitigates an attack proposed by wanoskarnet, in which
3518 all of a client's bridges collude to restrict the exit nodes that
3519 the client knows about. Fixes bug 5343.
3521 o Major bugfixes (on Tor 0.2.3.x):
3522 - Avoid an assert when managed proxies like obfsproxy are configured,
3523 and we receive HUP signals or setconf attempts too rapidly. This
3524 situation happens most commonly when Vidalia tries to attach to
3525 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
3526 bugfix on 0.2.3.6-alpha.
3527 - Fix a relay-side pluggable transports bug where managed proxies were
3528 unreachable from the Internet, because Tor asked them to bind on
3529 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
3530 - Stop discarding command-line arguments when TestingTorNetwork
3531 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
3532 0.2.3.9-alpha, where task 4552 added support for two layers of
3534 - Resume allowing the unit tests to run in gdb. This was accidentally
3535 made impossible when the DisableDebuggerAttachment option was
3536 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
3537 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
3538 0.2.3.11-alpha. Reported by Anthony G. Basile.
3540 o Minor bugfixes (on 0.2.2.x and earlier):
3541 - Ensure we don't cannibalize circuits that are longer than three hops
3542 already, so we don't end up making circuits with 5 or more
3543 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
3544 0.1.0.1-rc which introduced cannibalization.
3545 - Detect and reject certain misformed escape sequences in
3546 configuration values. Previously, these values would cause us
3547 to crash if received in a torrc file or over an authenticated
3548 control port. Bug found by Esteban Manchado Velázquez, and
3549 independently by Robert Connolly from Matta Consulting who further
3550 noted that it allows a post-authentication heap overflow. Patch
3551 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3552 bugfix on 0.2.0.16-alpha.
3553 - Fix a compile warning when using the --enable-openbsd-malloc
3554 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3555 - Directory caches no longer refuse to clean out descriptors because
3556 of missing v2 networkstatus documents, unless they're configured
3557 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
3558 0.2.2.26-beta. Patch by Daniel Bryg.
3559 - Update to the latest version of the tinytest unit testing framework.
3560 This includes a couple of bugfixes that can be relevant for
3561 running forked unit tests on Windows, and removes all reserved
3564 o Minor bugfixes (on 0.2.3.x):
3565 - On a failed pipe() call, don't leak file descriptors. Fixes bug
3566 4296; bugfix on 0.2.3.1-alpha.
3567 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
3568 until after we have received a CERTS cell. Fixes bug 4361; bugfix
3569 on 0.2.3.6-alpha. Patch by "frosty".
3570 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
3571 option, so that the IP stack doesn't decide to use it for IPv4
3572 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
3573 - Ensure that variables set in Tor's environment cannot override
3574 environment variables that Tor passes to a managed
3575 pluggable-transport proxy. Previously, Tor would pass every
3576 variable in its environment to managed proxies along with the new
3577 ones, in such a way that on many operating systems, the inherited
3578 environment variables would override those which Tor tried to
3579 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
3580 bugfix on 0.2.3.9-alpha for Windows.
3583 - A wide variety of new unit tests by Esteban Manchado Velázquez.
3584 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
3585 - Update to the March 6 2012 Maxmind GeoLite Country database.
3588 Changes in version 0.2.3.12-alpha - 2012-02-13
3589 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
3590 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
3591 when Tor is configured to use a pluggable transport like obfsproxy.
3594 - Fix builds when the path to sed, openssl, or sha1sum contains
3595 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3597 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
3598 connections. This change should allow busy exit relays to stop
3599 running out of available sockets as quickly. Fixes bug 4950;
3600 bugfix on 0.2.2.26-beta.
3601 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
3602 would ask the bridge for microdescriptors, which are only supported
3603 in 0.2.3.x, and then fail to bootstrap when it didn't get the
3604 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
3605 - Properly set up obfsproxy's environment when in managed mode. The
3606 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
3607 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
3608 5076 and 5082; bugfix on 0.2.3.6-alpha.
3611 - Use the dead_strip option when building Tor on OS X. This reduces
3612 binary size by almost 19% when linking openssl and libevent
3613 statically, which we do for Tor Browser Bundle.
3614 - Fix broken URLs in the sample torrc file, and tell readers about
3615 the OutboundBindAddress, ExitPolicyRejectPrivate, and
3616 PublishServerDescriptor options. Addresses bug 4652.
3617 - Update to the February 7 2012 Maxmind GeoLite Country database.
3620 - Downgrade the "We're missing a certificate" message from notice
3621 to info: people kept mistaking it for a real problem, whereas it
3622 is seldom the problem even when we are failing to bootstrap. Fixes
3623 bug 5067; bugfix on 0.2.0.10-alpha.
3624 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
3625 managed pluggable transport server proxy's environment.
3626 Previously, we would put it there, even though Tor doesn't
3627 implement an 'extended server port' yet, and even though Tor
3628 almost certainly isn't listening at that address. For now, we set
3629 it to an empty string to avoid crashing older obfsproxies. Bugfix
3631 - Log the heartbeat message every HeartbeatPeriod seconds, not every
3632 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
3633 0.2.3.1-alpha. Bug reported by Scott Bennett.
3634 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
3635 bugfix on 0.2.3.11-alpha.
3636 - Update "ClientOnly" man page entry to explain that there isn't
3637 really any point to messing with it. Resolves ticket 5005.
3638 - Use the correct CVE number for CVE-2011-4576 in our comments and
3639 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
3642 o Code simplifications and refactoring:
3643 - Use the _WIN32 macro throughout our code to detect Windows.
3644 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
3648 Changes in version 0.2.3.11-alpha - 2012-01-22
3649 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
3650 the last step of the plan to limit maximum circuit length, includes
3651 a wide variety of hidden service performance and correctness fixes,
3652 works around an OpenSSL security flaw if your distro is too stubborn
3653 to upgrade, and fixes a bunch of smaller issues.
3656 - Now that Tor 0.2.0.x is completely deprecated, enable the final
3657 part of "Proposal 110: Avoiding infinite length circuits" by
3658 refusing all circuit-extend requests that do not use a relay_early
3659 cell. This change helps Tor resist a class of denial-of-service
3660 attacks by limiting the maximum circuit length.
3661 - Adjust the number of introduction points that a hidden service
3662 will try to maintain based on how long its introduction points
3663 remain in use and how many introductions they handle. Fixes
3665 - Try to use system facilities for enumerating local interface
3666 addresses, before falling back to our old approach (which was
3667 binding a UDP socket, and calling getsockname() on it). That
3668 approach was scaring OS X users whose draconian firewall
3669 software warned about binding to UDP sockets, regardless of
3670 whether packets were sent. Now we try to use getifaddrs(),
3671 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
3672 system supports. Resolves ticket 1827.
3674 o Major security workaround:
3675 - When building or running with any version of OpenSSL earlier
3676 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
3677 versions have a bug (CVE-2011-4576) in which their block cipher
3678 padding includes uninitialized data, potentially leaking sensitive
3679 information to any peer with whom they make a SSLv3 connection. Tor
3680 does not use SSL v3 by default, but a hostile client or server
3681 could force an SSLv3 connection in order to gain information that
3682 they shouldn't have been able to get. The best solution here is to
3683 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
3684 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
3685 to make sure that the bug can't happen.
3688 - Fix the SOCKET_OK test that we use to tell when socket
3689 creation fails so that it works on Win64. Fixes part of bug 4533;
3690 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
3691 - Correct our replacements for the timeradd() and timersub() functions
3692 on platforms that lack them (for example, Windows). The timersub()
3693 function is used when expiring circuits, while timeradd() is
3694 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
3695 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
3696 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
3697 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
3698 bug at runtime, not compile time, because some distributions hack
3699 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
3700 on 0.2.3.9-alpha. Found by Pascal.
3702 o Minor features (controller):
3703 - Use absolute path names when reporting the torrc filename in the
3704 control protocol, so a controller can more easily find the torrc
3705 file. Resolves bug 1101.
3706 - Extend the control protocol to report flags that control a circuit's
3707 path selection in CIRC events and in replies to 'GETINFO
3708 circuit-status'. Implements part of ticket 2411.
3709 - Extend the control protocol to report the hidden service address
3710 and current state of a hidden-service-related circuit in CIRC
3711 events and in replies to 'GETINFO circuit-status'. Implements part
3713 - When reporting the path to the cookie file to the controller,
3714 give an absolute path. Resolves ticket 4881.
3715 - Allow controllers to request an event notification whenever a
3716 circuit is cannibalized or its purpose is changed. Implements
3717 part of ticket 3457.
3718 - Include the creation time of a circuit in CIRC and CIRC2
3719 control-port events and the list produced by the 'GETINFO
3720 circuit-status' control-port command.
3722 o Minor features (directory authorities):
3723 - Directory authorities now reject versions of Tor older than
3724 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3725 inclusive. These versions accounted for only a small fraction of
3726 the Tor network, and have numerous known security issues. Resolves
3728 - Authority operators can now vote for all relays in a given
3729 set of countries to be BadDir/BadExit/Invalid/Rejected.
3730 - Provide two consensus parameters (FastFlagMinThreshold and
3731 FastFlagMaxThreshold) to control the range of allowable bandwidths
3732 for the Fast directory flag. These allow authorities to run
3733 experiments on appropriate requirements for being a "Fast" node.
3734 The AuthDirFastGuarantee config value still applies. Implements
3736 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3737 directory authority option (introduced in Tor 0.2.2.34).
3739 o Minor features (other):
3740 - Don't disable the DirPort when we cannot exceed our AccountingMax
3741 limit during this interval because the effective bandwidthrate is
3742 low enough. This is useful in a situation where AccountMax is only
3743 used as an additional safeguard or to provide statistics.
3744 - Prepend an informative header to generated dynamic_dh_params files.
3745 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
3746 EntryNodes will have no effect. Resolves issue 2571.
3747 - Log more useful messages when we fail to disable debugger
3749 - Log which authority we're missing votes from when we go to fetch
3750 them from the other auths.
3751 - Log (at debug level) whenever a circuit's purpose is changed.
3752 - Add missing documentation for the MaxClientCircuitsPending,
3753 UseMicrodescriptors, UserspaceIOCPBuffers, and
3754 _UseFilteringSSLBufferevents options, all introduced during
3756 - Update to the January 3 2012 Maxmind GeoLite Country database.
3758 o Minor bugfixes (hidden services):
3759 - Don't close hidden service client circuits which have almost
3760 finished connecting to their destination when they reach
3761 the normal circuit-build timeout. Previously, we would close
3762 introduction circuits which are waiting for an acknowledgement
3763 from the introduction point, and rendezvous circuits which have
3764 been specified in an INTRODUCE1 cell sent to a hidden service,
3765 after the normal CBT. Now, we mark them as 'timed out', and launch
3766 another rendezvous attempt in parallel. This behavior change can
3767 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
3768 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
3769 - Don't close hidden-service-side rendezvous circuits when they
3770 reach the normal circuit-build timeout. This behaviour change can
3771 be disabled using the new
3772 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
3773 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
3774 - Make sure we never mark the wrong rendezvous circuit as having
3775 had its introduction cell acknowleged by the introduction-point
3776 relay. Previously, when we received an INTRODUCE_ACK cell on a
3777 client-side hidden-service introduction circuit, we might have
3778 marked a rendezvous circuit other than the one we specified in
3779 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
3780 a warning message and interfered with the hidden service
3781 connection-establishment process. Fixes bug 4759; bugfix on
3782 0.2.3.3-alpha, when we added the stream-isolation feature which
3783 might cause Tor to open multiple rendezvous circuits for the same
3785 - Don't trigger an assertion failure when we mark a new client-side
3786 hidden-service introduction circuit for close during the process
3787 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
3790 o Minor bugfixes (log messages):
3791 - Correctly spell "connect" in a log message on failure to create a
3792 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
3794 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3795 Fixes bug 4856; bugfix on Tor 0.0.6.
3796 - Fix the log message describing how we work around discovering
3797 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
3798 4837; bugfix on 0.2.2.9-alpha.
3799 - When logging about a disallowed .exit name, do not also call it
3800 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
3802 o Minor bugfixes (build fixes):
3803 - During configure, detect when we're building with clang version
3804 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3805 CFLAGS. clang doesn't support them yet.
3806 - During configure, search for library containing cos function as
3807 libm lives in libcore on some platforms (BeOS/Haiku). Linking
3808 against libm was hard-coded before. Fixes the first part of bug
3809 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
3811 - Detect attempts to build Tor on (as yet hypothetical) versions
3812 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
3813 fix for bug 4533. Bugfix on 0.2.2.28-beta.
3814 - Preprocessor directives should not be put inside the arguments
3815 of a macro. This would break compilation with GCC releases prior
3816 to version 3.3. We would never recommend such an old GCC version,
3817 but it is apparently required for binary compatibility on some
3818 platforms (namely, certain builds of Haiku). Fixes the other part
3819 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
3822 o Minor bugfixes (other):
3823 - Older Linux kernels erroneously respond to strange nmap behavior
3824 by having accept() return successfully with a zero-length
3825 socket. When this happens, just close the connection. Previously,
3826 we would try harder to learn the remote address: but there was
3827 no such remote address to learn, and our method for trying to
3828 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3829 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3830 - Fix null-pointer access that could occur if TLS allocation failed.
3831 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
3832 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
3833 accidentally been reverted.
3834 - Fix our implementation of crypto_random_hostname() so it can't
3835 overflow on ridiculously large inputs. (No Tor version has ever
3836 provided this kind of bad inputs, but let's be correct in depth.)
3837 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
3838 - Find more places in the code that should have been testing for
3839 invalid sockets using the SOCKET_OK macro. Required for a fix
3840 for bug 4533. Bugfix on 0.2.2.28-beta.
3841 - Fix an assertion failure when, while running with bufferevents, a
3842 connection finishes connecting after it is marked for close, but
3843 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
3844 - test_util_spawn_background_ok() hardcoded the expected value
3845 for ENOENT to 2. This isn't portable as error numbers are
3846 platform specific, and particularly the hurd has ENOENT at
3847 0x40000002. Construct expected string at runtime, using the correct
3848 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
3849 - Reject attempts to disable DisableDebuggerAttachment while Tor is
3850 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
3851 - Use an appropriate-width type for sockets in tor-fw-helper on
3852 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
3855 - When sending or relaying a RELAY_EARLY cell, we used to convert
3856 it to a RELAY cell if the connection was using the v1 link
3857 protocol. This was a workaround for older versions of Tor, which
3858 didn't handle RELAY_EARLY cells properly. Now that all supported
3859 versions can handle RELAY_EARLY cells, and now that we're enforcing
3860 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3861 remove this workaround. Addresses bug 4786.
3863 o Code simplifications and refactoring:
3864 - Use OpenSSL's built-in SSL_state_string_long() instead of our
3865 own homebrewed ssl_state_to_string() replacement. Patch from
3866 Emile Snyder. Fixes bug 4653.
3867 - Use macros to indicate OpenSSL versions, so we don't need to worry
3868 about accidental hexadecimal bit shifts.
3869 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
3871 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
3872 - Use the smartlist_add_asprintf() alias more consistently.
3873 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
3874 invalid value, rather than just -1.
3875 - Rename a handful of old identifiers, mostly related to crypto
3876 structures and crypto functions. By convention, our "create an
3877 object" functions are called "type_new()", our "free an object"
3878 functions are called "type_free()", and our types indicate that
3879 they are types only with a final "_t". But a handful of older
3880 types and functions broke these rules, with function names like
3881 "type_create" or "subsystem_op_type", or with type names like
3885 Changes in version 0.2.3.10-alpha - 2011-12-16
3886 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
3887 Tor's buffers code. Absolutely everybody should upgrade.
3889 The bug relied on an incorrect calculation when making data continuous
3890 in one of our IO buffers, if the first chunk of the buffer was
3891 misaligned by just the wrong amount. The miscalculation would allow an
3892 attacker to overflow a piece of heap-allocated memory. To mount this
3893 attack, the attacker would need to either open a SOCKS connection to
3894 Tor's SocksPort (usually restricted to localhost), or target a Tor
3895 instance configured to make its connections through a SOCKS proxy
3896 (which Tor does not do by default).
3898 Good security practice requires that all heap-overflow bugs should be
3899 presumed to be exploitable until proven otherwise, so we are treating
3900 this as a potential code execution attack. Please upgrade immediately!
3901 This bug does not affect bufferevents-based builds of Tor. Special
3902 thanks to "Vektor" for reporting this issue to us!
3904 This release also contains a few minor bugfixes for issues discovered
3908 - Fix a heap overflow bug that could occur when trying to pull
3909 data into the first chunk of a buffer, when that chunk had
3910 already had some data drained from it. Fixes CVE-2011-2778;
3911 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3914 - If we can't attach streams to a rendezvous circuit when we
3915 finish connecting to a hidden service, clear the rendezvous
3916 circuit's stream-isolation state and try to attach streams
3917 again. Previously, we cleared rendezvous circuits' isolation
3918 state either too early (if they were freshly built) or not at all
3919 (if they had been built earlier and were cannibalized). Bugfix on
3920 0.2.3.3-alpha; fixes bug 4655.
3921 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
3922 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
3923 - Fix an assertion failure when a relay with accounting enabled
3924 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
3927 - Update to the December 6 2011 Maxmind GeoLite Country database.
3930 Changes in version 0.2.2.35 - 2011-12-16
3931 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3932 buffers code. Absolutely everybody should upgrade.
3934 The bug relied on an incorrect calculation when making data continuous
3935 in one of our IO buffers, if the first chunk of the buffer was
3936 misaligned by just the wrong amount. The miscalculation would allow an
3937 attacker to overflow a piece of heap-allocated memory. To mount this
3938 attack, the attacker would need to either open a SOCKS connection to
3939 Tor's SocksPort (usually restricted to localhost), or target a Tor
3940 instance configured to make its connections through a SOCKS proxy
3941 (which Tor does not do by default).
3943 Good security practice requires that all heap-overflow bugs should be
3944 presumed to be exploitable until proven otherwise, so we are treating
3945 this as a potential code execution attack. Please upgrade immediately!
3946 This bug does not affect bufferevents-based builds of Tor. Special
3947 thanks to "Vektor" for reporting this issue to us!
3949 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3950 crash bugs for unusual configurations, and a long-term bug that
3951 would prevent Tor from starting on Windows machines with draconian
3954 With this release, we remind everyone that 0.2.0.x has reached its
3955 formal end-of-life. Those Tor versions have many known flaws, and
3956 nobody should be using them. You should upgrade -- ideally to the
3957 0.2.2.x series. If you're using a Linux or BSD and its packages are
3958 obsolete, stop using those packages and upgrade anyway.
3960 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3961 longer receive support after some time in early 2012.
3964 - Fix a heap overflow bug that could occur when trying to pull
3965 data into the first chunk of a buffer, when that chunk had
3966 already had some data drained from it. Fixes CVE-2011-2778;
3967 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3968 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3969 that it doesn't attempt to allocate a socketpair. This could cause
3970 some problems on Windows systems with overzealous firewalls. Fix for
3971 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3973 - If we mark an OR connection for close based on a cell we process,
3974 don't process any further cells on it. We already avoid further
3975 reads on marked-for-close connections, but now we also discard the
3976 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3977 which was the first version where we might mark a connection for
3978 close based on processing a cell on it.
3979 - Correctly sanity-check that we don't underflow on a memory
3980 allocation (and then assert) for hidden service introduction
3981 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3982 bugfix on 0.2.1.5-alpha.
3983 - Fix a memory leak when we check whether a hidden service
3984 descriptor has any usable introduction points left. Fixes bug
3985 4424. Bugfix on 0.2.2.25-alpha.
3986 - Don't crash when we're running as a relay and don't have a GeoIP
3987 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3988 we've had in the 0.2.3.x branch already.
3989 - When running as a client, do not print a misleading (and plain
3990 wrong) log message that we're collecting "directory request"
3991 statistics: clients don't collect statistics. Also don't create a
3992 useless (because empty) stats file in the stats/ directory. Fixes
3993 bug 4353; bugfix on 0.2.2.34.
3996 - Detect failure to initialize Libevent. This fix provides better
3997 detection for future instances of bug 4457.
3998 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3999 function. This was eating up hideously large amounts of time on some
4000 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
4001 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4002 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4004 - Don't warn about unused log_mutex in log.c when building with
4005 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
4006 0.1.0.6-rc which introduced --disable-threads.
4007 - When configuring, starting, or stopping an NT service, stop
4008 immediately after the service configuration attempt has succeeded
4009 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
4010 - When sending a NETINFO cell, include the original address
4011 received for the other side, not its canonical address. Found
4012 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
4013 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
4014 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
4015 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
4016 occurred when a client tried to fetch a descriptor for a bridge
4017 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
4018 - Backport fixes for a pair of compilation warnings on Windows.
4019 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
4020 - If we had ever tried to call tor_addr_to_str on an address of
4021 unknown type, we would have done a strdup on an uninitialized
4022 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
4023 Reported by "troll_un".
4024 - Correctly detect and handle transient lookup failures from
4025 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
4026 Reported by "troll_un".
4027 - Fix null-pointer access that could occur if TLS allocation failed.
4028 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
4029 - Use tor_socket_t type for listener argument to accept(). Fixes bug
4030 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
4033 - Add two new config options for directory authorities:
4034 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
4035 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
4036 that is always sufficient to satisfy the bandwidth requirement for
4037 the Guard flag. Now it will be easier for researchers to simulate
4038 Tor networks with different values. Resolves ticket 4484.
4039 - When Tor ignores a hidden service specified in its configuration,
4040 include the hidden service's directory in the warning message.
4041 Previously, we would only tell the user that some hidden service
4042 was ignored. Bugfix on 0.0.6; fixes bug 4426.
4043 - Update to the December 6 2011 Maxmind GeoLite Country database.
4045 o Packaging changes:
4046 - Make it easier to automate expert package builds on Windows,
4047 by removing an absolute path from makensis.exe command.
4050 Changes in version 0.2.1.32 - 2011-12-16
4051 Tor 0.2.1.32 backports important security and privacy fixes for
4052 oldstable. This release is intended only for package maintainers and
4053 others who cannot use the 0.2.2 stable series. All others should be
4054 using Tor 0.2.2.x or newer.
4056 The Tor 0.2.1.x series will reach formal end-of-life some time in
4057 early 2012; we will stop releasing patches for it then.
4059 o Major bugfixes (also included in 0.2.2.x):
4060 - Correctly sanity-check that we don't underflow on a memory
4061 allocation (and then assert) for hidden service introduction
4062 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4063 bugfix on 0.2.1.5-alpha.
4064 - Fix a heap overflow bug that could occur when trying to pull
4065 data into the first chunk of a buffer, when that chunk had
4066 already had some data drained from it. Fixes CVE-2011-2778;
4067 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4070 - Update to the December 6 2011 Maxmind GeoLite Country database.
4073 Changes in version 0.2.3.9-alpha - 2011-12-08
4074 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
4075 a "DisableNetwork" security feature that bundles can use to avoid
4076 touching the network until bridges are configured, moves forward on
4077 the pluggable transport design, fixes a flaw in the hidden service
4078 design that unnecessarily prevented clients with wrong clocks from
4079 reaching hidden services, and fixes a wide variety of other issues.
4082 - Clients can now connect to private bridges over IPv6. Bridges
4083 still need at least one IPv4 address in order to connect to
4084 other relays. Note that we don't yet handle the case where the
4085 user has two bridge lines for the same bridge (one IPv4, one
4086 IPv6). Implements parts of proposal 186.
4087 - New "DisableNetwork" config option to prevent Tor from launching any
4088 connections or accepting any connections except on a control port.
4089 Bundles and controllers can set this option before letting Tor talk
4090 to the rest of the network, for example to prevent any connections
4091 to a non-bridge address. Packages like Orbot can also use this
4092 option to instruct Tor to save power when the network is off.
4093 - Clients and bridges can now be configured to use a separate
4094 "transport" proxy. This approach makes the censorship arms race
4095 easier by allowing bridges to use protocol obfuscation plugins. It
4096 implements the "managed proxy" part of proposal 180 (ticket 3472).
4097 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
4098 implementation. It makes AES_CTR about 7% faster than our old one
4099 (which was about 10% faster than the one OpenSSL used to provide).
4100 Resolves ticket 4526.
4101 - Add a "tor2web mode" for clients that want to connect to hidden
4102 services non-anonymously (and possibly more quickly). As a safety
4103 measure to try to keep users from turning this on without knowing
4104 what they are doing, tor2web mode must be explicitly enabled at
4105 compile time, and a copy of Tor compiled to run in tor2web mode
4106 cannot be used as a normal Tor client. Implements feature 2553.
4107 - Add experimental support for running on Windows with IOCP and no
4108 kernel-space socket buffers. This feature is controlled by a new
4109 "UserspaceIOCPBuffers" config option (off by default), which has
4110 no effect unless Tor has been built with support for bufferevents,
4111 is running on Windows, and has enabled IOCP. This may, in the long
4112 run, help solve or mitigate bug 98.
4113 - Use a more secure consensus parameter voting algorithm. Now at
4114 least three directory authorities or a majority of them must
4115 vote on a given parameter before it will be included in the
4116 consensus. Implements proposal 178.
4119 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
4120 They used to check that the timestamp was within 30 minutes
4121 of their system clock, so they could cap the size of their
4122 replay-detection cache, but that approach unnecessarily refused
4123 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
4124 the v3 intro-point protocol (the first one which sent a timestamp
4125 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
4126 - Only use the EVP interface when AES acceleration is enabled,
4127 to avoid a 5-7% performance regression. Resolves issue 4525;
4128 bugfix on 0.2.3.8-alpha.
4130 o Privacy/anonymity features (bridge detection):
4131 - Make bridge SSL certificates a bit more stealthy by using random
4132 serial numbers, in the same fashion as OpenSSL when generating
4133 self-signed certificates. Implements ticket 4584.
4134 - Introduce a new config option "DynamicDHGroups", enabled by
4135 default, which provides each bridge with a unique prime DH modulus
4136 to be used during SSL handshakes. This option attempts to help
4137 against censors who might use the Apache DH modulus as a static
4138 identifier for bridges. Addresses ticket 4548.
4140 o Minor features (new/different config options):
4141 - New configuration option "DisableDebuggerAttachment" (on by default)
4142 to prevent basic debugging attachment attempts by other processes.
4143 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
4144 - Allow MapAddress directives to specify matches against super-domains,
4145 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
4146 Implements issue 933.
4147 - Slightly change behavior of "list" options (that is, config
4148 options that can appear more than once) when they appear both in
4149 torrc and on the command line. Previously, the command-line options
4150 would be appended to the ones from torrc. Now, the command-line
4151 options override the torrc options entirely. This new behavior
4152 allows the user to override list options (like exit policies and
4153 ports to listen on) from the command line, rather than simply
4154 appending to the list.
4155 - You can get the old (appending) command-line behavior for "list"
4156 options by prefixing the option name with a "+".
4157 - You can remove all the values for a "list" option from the command
4158 line without adding any new ones by prefixing the option name
4160 - Add experimental support for a "defaults" torrc file to be parsed
4161 before the regular torrc. Torrc options override the defaults file's
4162 options in the same way that the command line overrides the torrc.
4163 The SAVECONF controller command saves only those options which
4164 differ between the current configuration and the defaults file. HUP
4165 reloads both files. (Note: This is an experimental feature; its
4166 behavior will probably be refined in future 0.2.3.x-alpha versions
4167 to better meet packagers' needs.) Implements task 4552.
4170 - Try to make the introductory warning message that Tor prints on
4171 startup more useful for actually finding help and information.
4172 Resolves ticket 2474.
4173 - Running "make version" now displays the version of Tor that
4174 we're about to build. Idea from katmagic; resolves issue 4400.
4175 - Expire old or over-used hidden service introduction points.
4176 Required by fix for bug 3460.
4177 - Move the replay-detection cache for the RSA-encrypted parts of
4178 INTRODUCE2 cells to the introduction point data structures.
4179 Previously, we would use one replay-detection cache per hidden
4180 service. Required by fix for bug 3460.
4181 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
4182 public key replay-detection cache from 60 minutes to 5 minutes. This
4183 replay-detection cache is now used only to detect multiple
4184 INTRODUCE2 cells specifying the same rendezvous point, so we can
4185 avoid launching multiple simultaneous attempts to connect to it.
4187 o Minor bugfixes (on Tor 0.2.2.x and earlier):
4188 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4189 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4191 - Fix a minor formatting issue in one of tor-gencert's error messages.
4193 - Prevent a false positive from the check-spaces script, by disabling
4194 the "whitespace between function name and (" check for functions
4196 - Fix a log message suggesting that people contact a non-existent
4197 email address. Fixes bug 3448.
4198 - Fix null-pointer access that could occur if TLS allocation failed.
4199 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
4200 - Report a real bootstrap problem to the controller on router
4201 identity mismatch. Previously we just said "foo", which probably
4202 made a lot of sense at the time. Fixes bug 4169; bugfix on
4204 - If we had ever tried to call tor_addr_to_str() on an address of
4205 unknown type, we would have done a strdup() on an uninitialized
4206 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
4207 Reported by "troll_un".
4208 - Correctly detect and handle transient lookup failures from
4209 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
4210 Reported by "troll_un".
4211 - Use tor_socket_t type for listener argument to accept(). Fixes bug
4212 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
4213 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
4214 bug 4532; found by "troll_un".
4216 o Minor bugfixes (on Tor 0.2.3.x):
4217 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
4219 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
4220 circuit for use as a hidden service client's rendezvous point.
4221 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
4222 with help from wanoskarnet.
4223 - Restore behavior of overriding SocksPort, ORPort, and similar
4224 options from the command line. Bugfix on 0.2.3.3-alpha.
4227 - Properly handle the case where the build-tree is not the same
4228 as the source tree when generating src/common/common_sha1.i,
4229 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
4230 bugfix on 0.2.0.1-alpha.
4232 o Code simplifications, cleanups, and refactorings:
4233 - Remove the pure attribute from all functions that used it
4234 previously. In many cases we assigned it incorrectly, because the
4235 functions might assert or call impure functions, and we don't have
4236 evidence that keeping the pure attribute is worthwhile. Implements
4237 changes suggested in ticket 4421.
4238 - Remove some dead code spotted by coverity. Fixes cid 432.
4239 Bugfix on 0.2.3.1-alpha, closes bug 4637.
4242 Changes in version 0.2.3.8-alpha - 2011-11-22
4243 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
4244 socketpair-related bug that has been bothering Windows users. It adds
4245 support to serve microdescriptors to controllers, so Vidalia's network
4246 map can resume listing relays (once Vidalia implements its side),
4247 and adds better support for hardware AES acceleration. Finally, it
4248 starts the process of adjusting the bandwidth cutoff for getting the
4249 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
4250 that tiny relays harm performance more than they help network capacity.
4253 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
4254 that it doesn't attempt to allocate a socketpair. This could cause
4255 some problems on Windows systems with overzealous firewalls. Fix for
4256 bug 4457; workaround for Libevent versions 2.0.1-alpha through
4258 - Correctly sanity-check that we don't underflow on a memory
4259 allocation (and then assert) for hidden service introduction
4260 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4261 bugfix on 0.2.1.5-alpha.
4262 - Remove the artificially low cutoff of 20KB to guarantee the Fast
4263 flag. In the past few years the average relay speed has picked
4264 up, and while the "top 7/8 of the network get the Fast flag" and
4265 "all relays with 20KB or more of capacity get the Fast flag" rules
4266 used to have the same result, now the top 7/8 of the network has
4267 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
4268 - Fix a rare assertion failure when checking whether a v0 hidden
4269 service descriptor has any usable introduction points left, and
4270 we don't have enough information to build a circuit to the first
4271 intro point named in the descriptor. The HS client code in
4272 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
4273 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
4274 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
4275 - Make bridge authorities not crash when they are asked for their own
4276 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
4277 - When running as a client, do not print a misleading (and plain
4278 wrong) log message that we're collecting "directory request"
4279 statistics: clients don't collect statistics. Also don't create a
4280 useless (because empty) stats file in the stats/ directory. Fixes
4281 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
4284 - Allow Tor controllers like Vidalia to obtain the microdescriptor
4285 for a relay by identity digest or nickname. Previously,
4286 microdescriptors were only available by their own digests, so a
4287 controller would have to ask for and parse the whole microdescriptor
4288 consensus in order to look up a single relay's microdesc. Fixes
4289 bug 3832; bugfix on 0.2.3.1-alpha.
4290 - Use OpenSSL's EVP interface for AES encryption, so that all AES
4291 operations can use hardware acceleration (if present). Resolves
4294 o Minor bugfixes (on 0.2.2.x and earlier):
4295 - Detect failure to initialize Libevent. This fix provides better
4296 detection for future instances of bug 4457.
4297 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
4298 function. This was eating up hideously large amounts of time on some
4299 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
4300 - Don't warn about unused log_mutex in log.c when building with
4301 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
4302 0.1.0.6-rc which introduced --disable-threads.
4303 - Allow manual 'authenticate' commands to the controller interface
4304 from netcat (nc) as well as telnet. We were rejecting them because
4305 they didn't come with the expected whitespace at the end of the
4306 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
4307 - Fix some (not actually triggerable) buffer size checks in usage of
4308 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
4310 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
4311 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
4312 - When configuring, starting, or stopping an NT service, stop
4313 immediately after the service configuration attempt has succeeded
4314 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
4315 - When sending a NETINFO cell, include the original address
4316 received for the other side, not its canonical address. Found
4317 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
4318 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
4319 can pick them up when the tests aren't disabled. Bugfix on
4320 0.2.2.4-alpha which introduced tinytest.
4321 - Fix a memory leak when we check whether a hidden service
4322 descriptor has any usable introduction points left. Fixes bug
4323 4424. Bugfix on 0.2.2.25-alpha.
4324 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
4325 occurred when a client tried to fetch a descriptor for a bridge
4326 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
4328 o Minor bugfixes (on 0.2.3.x):
4329 - Make util unit tests build correctly with MSVC. Bugfix on
4330 0.2.3.3-alpha. Patch by Gisle Vanem.
4331 - Successfully detect AUTH_CHALLENGE cells with no recognized
4332 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
4334 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
4335 it should still send a NETINFO cell to allow the connection to
4336 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
4338 - Log less loudly when we get an invalid authentication certificate
4339 from a source other than a directory authority: it's not unusual
4340 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
4342 - Tolerate servers with more clock skew in their authentication
4343 certificates than previously. Fixes bug 4371; bugfix on
4345 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
4346 on 0.2.3.4-alpha and 0.2.3.6-alpha.
4349 - Add two new config options for directory authorities:
4350 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
4351 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
4352 that is always sufficient to satisfy the bandwidth requirement for
4353 the Guard flag. Now it will be easier for researchers to simulate
4354 Tor networks with different values. Resolves ticket 4484.
4355 - When Tor ignores a hidden service specified in its configuration,
4356 include the hidden service's directory in the warning message.
4357 Previously, we would only tell the user that some hidden service
4358 was ignored. Bugfix on 0.0.6; fixes bug 4426.
4359 - When we fail to initialize Libevent, retry with IOCP disabled so we
4360 don't need to turn on multi-threading support in Libevent, which in
4361 turn requires a working socketpair(). This is a workaround for bug
4362 4457, which affects Libevent versions from 2.0.1-alpha through
4364 - Detect when we try to build on a platform that doesn't define
4365 AF_UNSPEC to 0. We don't work there, so refuse to compile.
4366 - Update to the November 1 2011 Maxmind GeoLite Country database.
4368 o Packaging changes:
4369 - Make it easier to automate expert package builds on Windows,
4370 by removing an absolute path from makensis.exe command.
4372 o Code simplifications and refactoring:
4373 - Remove some redundant #include directives throughout the code.
4374 Patch from Andrea Gelmini.
4375 - Unconditionally use OpenSSL's AES implementation instead of our
4376 old built-in one. OpenSSL's AES has been better for a while, and
4377 relatively few servers should still be on any version of OpenSSL
4378 that doesn't have good optimized assembly AES.
4379 - Use the name "CERTS" consistently to refer to the new cell type;
4380 we were calling it CERT in some places and CERTS in others.
4383 - Numerous new unit tests for functions in util.c and address.c by
4385 - The long-disabled benchmark tests are now split into their own
4386 ./src/test/bench binary.
4387 - The benchmark tests can now use more accurate timers than
4388 gettimeofday() when such timers are available.
4391 Changes in version 0.2.3.7-alpha - 2011-10-30
4392 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
4393 the new v3 handshake. It also resolves yet another bridge address
4397 - If we mark an OR connection for close based on a cell we process,
4398 don't process any further cells on it. We already avoid further
4399 reads on marked-for-close connections, but now we also discard the
4400 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
4401 which was the first version where we might mark a connection for
4402 close based on processing a cell on it.
4403 - Fix a double-free bug that would occur when we received an invalid
4404 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
4405 bugfix on 0.2.3.6-alpha.
4406 - Bridges no longer include their address in NETINFO cells on outgoing
4407 OR connections, to allow them to blend in better with clients.
4408 Removes another avenue for enumerating bridges. Reported by
4409 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
4410 cells were introduced.
4413 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
4414 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
4417 Changes in version 0.2.3.6-alpha - 2011-10-26
4418 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
4419 anonymity vulnerability where an attacker can deanonymize Tor
4420 users. Everybody should upgrade.
4422 This release also features support for a new v3 connection handshake
4423 protocol, and fixes to make hidden service connections more robust.
4426 - Implement a new handshake protocol (v3) for authenticating Tors to
4427 each other over TLS. It should be more resistant to fingerprinting
4428 than previous protocols, and should require less TLS hacking for
4429 future Tor implementations. Implements proposal 176.
4430 - Allow variable-length padding cells to disguise the length of
4431 Tor's TLS records. Implements part of proposal 184.
4433 o Privacy/anonymity fixes (clients):
4434 - Clients and bridges no longer send TLS certificate chains on
4435 outgoing OR connections. Previously, each client or bridge would
4436 use the same cert chain for all outgoing OR connections until
4437 its IP address changes, which allowed any relay that the client
4438 or bridge contacted to determine which entry guards it is using.
4439 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4440 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4441 no longer considers that connection as suitable for satisfying a
4442 circuit EXTEND request. Now relays can protect clients from the
4443 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4444 - Directory authorities no longer assign the Guard flag to relays
4445 that haven't upgraded to the above "refuse EXTEND requests
4446 to client connections" fix. Now directory authorities can
4447 protect clients from the CVE-2011-2768 issue even if neither
4448 the clients nor the relays have upgraded yet. There's a new
4449 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
4450 to let us transition smoothly, else tomorrow there would be no
4453 o Major bugfixes (hidden services):
4454 - Improve hidden service robustness: when an attempt to connect to
4455 a hidden service ends, be willing to refetch its hidden service
4456 descriptors from each of the HSDir relays responsible for them
4457 immediately. Previously, we would not consider refetching the
4458 service's descriptors from each HSDir for 15 minutes after the last
4459 fetch, which was inconvenient if the hidden service was not running
4460 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
4461 - When one of a hidden service's introduction points appears to be
4462 unreachable, stop trying it. Previously, we would keep trying
4463 to build circuits to the introduction point until we lost the
4464 descriptor, usually because the user gave up and restarted Tor.
4465 Partly fixes bug 3825.
4466 - Don't launch a useless circuit after failing to use one of a
4467 hidden service's introduction points. Previously, we would
4468 launch a new introduction circuit, but not set the hidden service
4469 which that circuit was intended to connect to, so it would never
4470 actually be used. A different piece of code would then create a
4471 new introduction circuit correctly. Bug reported by katmagic and
4472 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
4474 o Major bugfixes (other):
4475 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4476 that they initiated. Relays could distinguish incoming bridge
4477 connections from client connections, creating another avenue for
4478 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4479 Found by "frosty_un".
4480 - Don't update the AccountingSoftLimitHitAt state file entry whenever
4481 tor gets started. This prevents a wrong average bandwidth
4482 estimate, which would cause relays to always start a new accounting
4483 interval at the earliest possible moment. Fixes bug 2003; bugfix
4484 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
4485 immensely in tracking this bug down.
4486 - Fix a crash bug when changing node restrictions while a DNS lookup
4487 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
4490 o Minor bugfixes (on 0.2.2.x and earlier):
4491 - When a hidden service turns an extra service-side introduction
4492 circuit into a general-purpose circuit, free the rend_data and
4493 intro_key fields first, so we won't leak memory if the circuit
4494 is cannibalized for use as another service-side introduction
4495 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
4496 - Rephrase the log message emitted if the TestSocks check is
4497 successful. Patch from Fabian Keil; fixes bug 4094.
4498 - Bridges now skip DNS self-tests, to act a little more stealthily.
4499 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
4500 bridges. Patch by "warms0x".
4501 - Remove a confusing dollar sign from the example fingerprint in the
4502 man page, and also make the example fingerprint a valid one. Fixes
4503 bug 4309; bugfix on 0.2.1.3-alpha.
4504 - Fix internal bug-checking logic that was supposed to catch
4505 failures in digest generation so that it will fail more robustly
4506 if we ask for a nonexistent algorithm. Found by Coverity Scan.
4507 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
4508 - Report any failure in init_keys() calls launched because our
4509 IP address has changed. Spotted by Coverity Scan. Bugfix on
4510 0.1.1.4-alpha; fixes CID 484.
4512 o Minor bugfixes (on 0.2.3.x):
4513 - Fix a bug in configure.in that kept it from building a configure
4514 script with autoconf versions earlier than 2.61. Fixes bug 2430;
4515 bugfix on 0.2.3.1-alpha.
4516 - Don't warn users that they are exposing a client port to the
4517 Internet if they have specified an RFC1918 address. Previously,
4518 we would warn if the user had specified any non-loopback
4519 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
4520 - Fix memory leaks in the failing cases of the new SocksPort and
4521 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
4522 fixes coverity CIDs 485, 486, and 487.
4525 - When a hidden service's introduction point times out, consider
4526 trying it again during the next attempt to connect to the
4527 HS. Previously, we would not try it again unless a newly fetched
4528 descriptor contained it. Required by fixes for bugs 1297 and 3825.
4529 - The next version of Windows will be called Windows 8, and it has
4530 a major version of 6, minor version of 2. Correctly identify that
4531 version instead of calling it "Very recent version". Resolves
4532 ticket 4153; reported by funkstar.
4533 - The Bridge Authority now writes statistics on how many bridge
4534 descriptors it gave out in total, and how many unique descriptors
4535 it gave out. It also lists how often the most and least commonly
4536 fetched descriptors were given out, as well as the median and
4537 25th/75th percentile. Implements tickets 4200 and 4294.
4538 - Update to the October 4 2011 Maxmind GeoLite Country database.
4540 o Code simplifications and refactoring:
4541 - Remove some old code to remember statistics about which descriptors
4542 we've served as a directory mirror. The feature wasn't used and
4543 is outdated now that microdescriptors are around.
4544 - Rename Tor functions that turn strings into addresses, so that
4545 "parse" indicates that no hostname resolution occurs, and
4546 "lookup" indicates that hostname resolution may occur. This
4547 should help prevent mistakes in the future. Fixes bug 3512.
4550 Changes in version 0.2.2.34 - 2011-10-26
4551 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
4552 can deanonymize Tor users. Everybody should upgrade.
4554 The attack relies on four components: 1) Clients reuse their TLS cert
4555 when talking to different relays, so relays can recognize a user by
4556 the identity key in her cert. 2) An attacker who knows the client's
4557 identity key can probe each guard relay to see if that identity key
4558 is connected to that guard relay right now. 3) A variety of active
4559 attacks in the literature (starting from "Low-Cost Traffic Analysis
4560 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
4561 discover the guard relays that a Tor user visiting the website is using.
4562 4) Clients typically pick three guards at random, so the set of guards
4563 for a given user could well be a unique fingerprint for her. This
4564 release fixes components #1 and #2, which is enough to block the attack;
4565 the other two remain as open research problems. Special thanks to
4566 "frosty_un" for reporting the issue to us!
4568 Clients should upgrade so they are no longer recognizable by the TLS
4569 certs they present. Relays should upgrade so they no longer allow a
4570 remote attacker to probe them to test whether unpatched clients are
4571 currently connected to them.
4573 This release also fixes several vulnerabilities that allow an attacker
4574 to enumerate bridge relays. Some bridge enumeration attacks still
4575 remain; see for example proposal 188.
4577 o Privacy/anonymity fixes (clients):
4578 - Clients and bridges no longer send TLS certificate chains on
4579 outgoing OR connections. Previously, each client or bridge would
4580 use the same cert chain for all outgoing OR connections until
4581 its IP address changes, which allowed any relay that the client
4582 or bridge contacted to determine which entry guards it is using.
4583 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4584 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4585 no longer considers that connection as suitable for satisfying a
4586 circuit EXTEND request. Now relays can protect clients from the
4587 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4588 - Directory authorities no longer assign the Guard flag to relays
4589 that haven't upgraded to the above "refuse EXTEND requests
4590 to client connections" fix. Now directory authorities can
4591 protect clients from the CVE-2011-2768 issue even if neither
4592 the clients nor the relays have upgraded yet. There's a new
4593 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
4594 to let us transition smoothly, else tomorrow there would be no
4597 o Privacy/anonymity fixes (bridge enumeration):
4598 - Bridge relays now do their directory fetches inside Tor TLS
4599 connections, like all the other clients do, rather than connecting
4600 directly to the DirPort like public relays do. Removes another
4601 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4602 - Bridges relays now build circuits for themselves in a more similar
4603 way to how clients build them. Removes another avenue for
4604 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4605 when bridges were introduced.
4606 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4607 that they initiated. Relays could distinguish incoming bridge
4608 connections from client connections, creating another avenue for
4609 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4610 Found by "frosty_un".
4613 - Fix a crash bug when changing node restrictions while a DNS lookup
4614 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
4616 - Don't launch a useless circuit after failing to use one of a
4617 hidden service's introduction points. Previously, we would
4618 launch a new introduction circuit, but not set the hidden service
4619 which that circuit was intended to connect to, so it would never
4620 actually be used. A different piece of code would then create a
4621 new introduction circuit correctly. Bug reported by katmagic and
4622 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
4625 - Change an integer overflow check in the OpenBSD_Malloc code so
4626 that GCC is less likely to eliminate it as impossible. Patch
4627 from Mansour Moufid. Fixes bug 4059.
4628 - When a hidden service turns an extra service-side introduction
4629 circuit into a general-purpose circuit, free the rend_data and
4630 intro_key fields first, so we won't leak memory if the circuit
4631 is cannibalized for use as another service-side introduction
4632 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
4633 - Bridges now skip DNS self-tests, to act a little more stealthily.
4634 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
4635 bridges. Patch by "warms0x".
4636 - Fix internal bug-checking logic that was supposed to catch
4637 failures in digest generation so that it will fail more robustly
4638 if we ask for a nonexistent algorithm. Found by Coverity Scan.
4639 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
4640 - Report any failure in init_keys() calls launched because our
4641 IP address has changed. Spotted by Coverity Scan. Bugfix on
4642 0.1.1.4-alpha; fixes CID 484.
4644 o Minor bugfixes (log messages and documentation):
4645 - Remove a confusing dollar sign from the example fingerprint in the
4646 man page, and also make the example fingerprint a valid one. Fixes
4647 bug 4309; bugfix on 0.2.1.3-alpha.
4648 - The next version of Windows will be called Windows 8, and it has
4649 a major version of 6, minor version of 2. Correctly identify that
4650 version instead of calling it "Very recent version". Resolves
4651 ticket 4153; reported by funkstar.
4652 - Downgrade log messages about circuit timeout calibration from
4653 "notice" to "info": they don't require or suggest any human
4654 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4655 bugfix on 0.2.2.14-alpha.
4658 - Turn on directory request statistics by default and include them in
4659 extra-info descriptors. Don't break if we have no GeoIP database.
4660 Backported from 0.2.3.1-alpha; implements ticket 3951.
4661 - Update to the October 4 2011 Maxmind GeoLite Country database.
4664 Changes in version 0.2.1.31 - 2011-10-26
4665 Tor 0.2.1.31 backports important security and privacy fixes for
4666 oldstable. This release is intended only for package maintainers and
4667 others who cannot use the 0.2.2 stable series. All others should be
4668 using Tor 0.2.2.x or newer.
4670 o Security fixes (also included in 0.2.2.x):
4671 - Replace all potentially sensitive memory comparison operations
4672 with versions whose runtime does not depend on the data being
4673 compared. This will help resist a class of attacks where an
4674 adversary can use variations in timing information to learn
4675 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4676 implementation by Robert Ransom based partially on code by DJB.)
4677 - Fix an assert in parsing router descriptors containing IPv6
4678 addresses. This one took down the directory authorities when
4679 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4681 o Privacy/anonymity fixes (also included in 0.2.2.x):
4682 - Clients and bridges no longer send TLS certificate chains on
4683 outgoing OR connections. Previously, each client or bridge would
4684 use the same cert chain for all outgoing OR connections until
4685 its IP address changes, which allowed any relay that the client
4686 or bridge contacted to determine which entry guards it is using.
4687 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4688 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4689 no longer considers that connection as suitable for satisfying a
4690 circuit EXTEND request. Now relays can protect clients from the
4691 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4692 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4693 that they initiated. Relays could distinguish incoming bridge
4694 connections from client connections, creating another avenue for
4695 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4696 Found by "frosty_un".
4697 - When receiving a hidden service descriptor, check that it is for
4698 the hidden service we wanted. Previously, Tor would store any
4699 hidden service descriptors that a directory gave it, whether it
4700 wanted them or not. This wouldn't have let an attacker impersonate
4701 a hidden service, but it did let directories pre-seed a client
4702 with descriptors that it didn't want. Bugfix on 0.0.6.
4703 - Avoid linkability based on cached hidden service descriptors: forget
4704 all hidden service descriptors cached as a client when processing a
4705 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4706 - Make the bridge directory authority refuse to answer directory
4707 requests for "all" descriptors. It used to include bridge
4708 descriptors in its answer, which was a major information leak.
4709 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4710 - Don't attach new streams to old rendezvous circuits after SIGNAL
4711 NEWNYM. Previously, we would keep using an existing rendezvous
4712 circuit if it remained open (i.e. if it were kept open by a
4713 long-lived stream, or if a new stream were attached to it before
4714 Tor could notice that it was old and no longer in use). Bugfix on
4715 0.1.1.15-rc; fixes bug 3375.
4717 o Minor bugfixes (also included in 0.2.2.x):
4718 - When we restart our relay, we might get a successful connection
4719 from the outside before we've started our reachability tests,
4720 triggering a warning: "ORPort found reachable, but I have no
4721 routerinfo yet. Failing to inform controller of success." This
4722 bug was harmless unless Tor is running under a controller
4723 like Vidalia, in which case the controller would never get a
4724 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4726 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4727 enabled. Fixes bug 1526.
4728 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4729 anything since 0.2.1.16-rc.
4730 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4731 None of the cases where we did this before were wrong, but by making
4732 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4733 - Fix a rare crash bug that could occur when a client was configured
4734 with a large number of bridges. Fixes bug 2629; bugfix on
4735 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4736 - Correct the warning displayed when a rendezvous descriptor exceeds
4737 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4739 - Fix an uncommon assertion failure when running with DNSPort under
4740 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4741 - When warning about missing zlib development packages during compile,
4742 give the correct package names. Bugfix on 0.2.0.1-alpha.
4743 - Require that introduction point keys and onion keys have public
4744 exponent 65537. Bugfix on 0.2.0.10-alpha.
4745 - Do not crash when our configuration file becomes unreadable, for
4746 example due to a permissions change, between when we start up
4747 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4749 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4751 - Always NUL-terminate the sun_path field of a sockaddr_un before
4752 passing it to the kernel. (Not a security issue: kernels are
4753 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4754 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4755 - Don't stack-allocate the list of supplementary GIDs when we're
4756 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4757 could take up to 256K, which is way too much stack. Found by
4758 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4760 o Minor bugfixes (only in 0.2.1.x):
4761 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
4762 rely on them. Bugfix on 0.2.1.30.
4763 - Use git revisions instead of svn revisions when generating our
4764 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4766 o Minor features (also included in 0.2.2.x):
4767 - Adjust the expiration time on our SSL session certificates to
4768 better match SSL certs seen in the wild. Resolves ticket 4014.
4769 - Allow nameservers with IPv6 address. Resolves bug 2574.
4770 - Update to the October 4 2011 Maxmind GeoLite Country database.
4773 Changes in version 0.2.3.5-alpha - 2011-09-28
4774 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
4775 bridge relays; fixes an assertion error that many users started hitting
4776 today; and adds the ability to refill token buckets more often than
4777 once per second, allowing significant performance improvements.
4780 - Bridge relays now do their directory fetches inside Tor TLS
4781 connections, like all the other clients do, rather than connecting
4782 directly to the DirPort like public relays do. Removes another
4783 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4784 - Bridges relays now build circuits for themselves in a more similar
4785 way to how clients build them. Removes another avenue for
4786 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4787 when bridges were introduced.
4790 - Fix an "Assertion md->held_by_node == 1 failed" error that could
4791 occur when the same microdescriptor was referenced by two node_t
4792 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
4794 o Major features (networking):
4795 - Add a new TokenBucketRefillInterval option to refill token buckets
4796 more frequently than once per second. This should improve network
4797 performance, alleviate queueing problems, and make traffic less
4798 bursty. Implements proposal 183; closes ticket 3630. Design by
4799 Florian Tschorsch and Björn Scheuermann; implementation by
4803 - Change an integer overflow check in the OpenBSD_Malloc code so
4804 that GCC is less likely to eliminate it as impossible. Patch
4805 from Mansour Moufid. Fixes bug 4059.
4807 o Minor bugfixes (usability):
4808 - Downgrade log messages about circuit timeout calibration from
4809 "notice" to "info": they don't require or suggest any human
4810 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4811 bugfix on 0.2.2.14-alpha.
4813 o Minor features (diagnostics):
4814 - When the system call to create a listener socket fails, log the
4815 error message explaining why. This may help diagnose bug 4027.
4818 Changes in version 0.2.3.4-alpha - 2011-09-13
4819 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
4820 tweak to Tor's TLS handshake that makes relays and bridges that run
4821 this new version reachable from Iran again. It also fixes a few new
4822 bugs in 0.2.3.x, and teaches relays to recognize when they're not
4823 listed in the network consensus and republish.
4825 o Major bugfixes (also part of 0.2.2.33):
4826 - Avoid an assertion failure when reloading a configuration with
4827 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4828 3923; bugfix on 0.2.2.25-alpha.
4830 o Minor features (security, also part of 0.2.2.33):
4831 - Check for replays of the public-key encrypted portion of an
4832 INTRODUCE1 cell, in addition to the current check for replays of
4833 the g^x value. This prevents a possible class of active attacks
4834 by an attacker who controls both an introduction point and a
4835 rendezvous point, and who uses the malleability of AES-CTR to
4836 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4837 that these attacks are infeasible (requiring the attacker to send
4838 on the order of zettabytes of altered cells in a short interval),
4839 but we'd rather block them off in case there are any classes of
4840 this attack that we missed. Reported by Willem Pinckaers.
4842 o Minor features (also part of 0.2.2.33):
4843 - Adjust the expiration time on our SSL session certificates to
4844 better match SSL certs seen in the wild. Resolves ticket 4014.
4845 - Change the default required uptime for a relay to be accepted as
4846 a HSDir (hidden service directory) from 24 hours to 25 hours.
4847 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4848 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4849 authorities to abstain from voting on assignment of the HSDir
4850 consensus flag. Related to bug 2649.
4851 - Update to the September 6 2011 Maxmind GeoLite Country database.
4853 o Minor bugfixes (also part of 0.2.2.33):
4854 - Demote the 'replay detected' log message emitted when a hidden
4855 service receives the same Diffie-Hellman public key in two different
4856 INTRODUCE2 cells to info level. A normal Tor client can cause that
4857 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4858 fixes part of bug 2442.
4859 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4860 level. There is nothing that a hidden service's operator can do
4861 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4863 - Clarify a log message specifying the characters permitted in
4864 HiddenServiceAuthorizeClient client names. Previously, the log
4865 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4866 given the impression that every ASCII character between "+" and "_"
4867 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4869 o Build fixes (also part of 0.2.2.33):
4870 - Clean up some code issues that prevented Tor from building on older
4871 BSDs. Fixes bug 3894; reported by "grarpamp".
4872 - Search for a platform-specific version of "ar" when cross-compiling.
4873 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4876 - Fix a bug where the SocksPort option (for example) would get
4877 ignored and replaced by the default if a SocksListenAddress
4878 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
4882 - Relays now try regenerating and uploading their descriptor more
4883 frequently if they are not listed in the consensus, or if the
4884 version of their descriptor listed in the consensus is too
4885 old. This fix should prevent situations where a server declines
4886 to re-publish itself because it has done so too recently, even
4887 though the authorities decided not to list its recent-enough
4888 descriptor. Fix for bug 3327.
4891 - Relays now include a reason for regenerating their descriptors
4892 in an HTTP header when uploading to the authorities. This will
4893 make it easier to debug descriptor-upload issues in the future.
4894 - When starting as root and then changing our UID via the User
4895 control option, and we have a ControlSocket configured, make sure
4896 that the ControlSocket is owned by the same account that Tor will
4897 run under. Implements ticket 3421; fix by Jérémy Bobbio.
4900 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
4901 utility function used in the control-port code). This shouldn't
4902 ever happen unless Tor is completely out of memory, but if it did
4903 happen and Tor somehow recovered from it, Tor could have sent a log
4904 message to a control port in the middle of a reply to a controller
4905 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
4906 - Make 'FetchUselessDescriptors' cause all descriptor types and
4907 all consensus types (including microdescriptors) to get fetched.
4908 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
4911 - Make a new "entry connection" struct as an internal subtype of "edge
4912 connection", to simplify the code and make exit connections smaller.
4915 Changes in version 0.2.2.33 - 2011-09-13
4916 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
4917 TLS handshake that makes relays and bridges that run this new version
4918 reachable from Iran again.
4921 - Avoid an assertion failure when reloading a configuration with
4922 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4923 3923; bugfix on 0.2.2.25-alpha.
4925 o Minor features (security):
4926 - Check for replays of the public-key encrypted portion of an
4927 INTRODUCE1 cell, in addition to the current check for replays of
4928 the g^x value. This prevents a possible class of active attacks
4929 by an attacker who controls both an introduction point and a
4930 rendezvous point, and who uses the malleability of AES-CTR to
4931 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4932 that these attacks are infeasible (requiring the attacker to send
4933 on the order of zettabytes of altered cells in a short interval),
4934 but we'd rather block them off in case there are any classes of
4935 this attack that we missed. Reported by Willem Pinckaers.
4938 - Adjust the expiration time on our SSL session certificates to
4939 better match SSL certs seen in the wild. Resolves ticket 4014.
4940 - Change the default required uptime for a relay to be accepted as
4941 a HSDir (hidden service directory) from 24 hours to 25 hours.
4942 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4943 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4944 authorities to abstain from voting on assignment of the HSDir
4945 consensus flag. Related to bug 2649.
4946 - Update to the September 6 2011 Maxmind GeoLite Country database.
4948 o Minor bugfixes (documentation and log messages):
4949 - Correct the man page to explain that HashedControlPassword and
4950 CookieAuthentication can both be set, in which case either method
4951 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4952 when we decided to allow these config options to both be set. Issue
4954 - Demote the 'replay detected' log message emitted when a hidden
4955 service receives the same Diffie-Hellman public key in two different
4956 INTRODUCE2 cells to info level. A normal Tor client can cause that
4957 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4958 fixes part of bug 2442.
4959 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4960 level. There is nothing that a hidden service's operator can do
4961 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4963 - Clarify a log message specifying the characters permitted in
4964 HiddenServiceAuthorizeClient client names. Previously, the log
4965 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4966 given the impression that every ASCII character between "+" and "_"
4967 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4970 - Provide a substitute implementation of lround() for MSVC, which
4971 apparently lacks it. Patch from Gisle Vanem.
4972 - Clean up some code issues that prevented Tor from building on older
4973 BSDs. Fixes bug 3894; reported by "grarpamp".
4974 - Search for a platform-specific version of "ar" when cross-compiling.
4975 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4978 Changes in version 0.2.3.3-alpha - 2011-09-01
4979 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
4980 security, and provides client-side support for the microdescriptor
4981 and optimistic data features introduced earlier in the 0.2.3.x
4982 series. It also includes numerous critical bugfixes in the (optional)
4983 bufferevent-based networking backend.
4985 o Major features (stream isolation):
4986 - You can now configure Tor so that streams from different
4987 applications are isolated on different circuits, to prevent an
4988 attacker who sees your streams as they leave an exit node from
4989 linking your sessions to one another. To do this, choose some way
4990 to distinguish the applications: have them connect to different
4991 SocksPorts, or have one of them use SOCKS4 while the other uses
4992 SOCKS5, or have them pass different authentication strings to the
4993 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4994 degree of isolation you need. This implements Proposal 171.
4995 - There's a new syntax for specifying multiple client ports (such as
4996 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4997 multiple *Port entries with full addr:port syntax on each.
4998 The old *ListenAddress format is still supported, but you can't
4999 mix it with the new *Port syntax.
5001 o Major features (other):
5002 - Enable microdescriptor fetching by default for clients. This allows
5003 clients to download a much smaller amount of directory information.
5004 To disable it (and go back to the old-style consensus and
5005 descriptors), set "UseMicrodescriptors 0" in your torrc file.
5006 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
5007 "PortForwarding" config option), now supports Windows.
5008 - When using an exit relay running 0.2.3.x, clients can now
5009 "optimistically" send data before the exit relay reports that
5010 the stream has opened. This saves a round trip when starting
5011 connections where the client speaks first (such as web browsing).
5012 This behavior is controlled by a consensus parameter (currently
5013 disabled). To turn it on or off manually, use the "OptimisticData"
5014 torrc option. Implements proposal 181; code by Ian Goldberg.
5016 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
5017 - When using IOCP on Windows, we need to enable Libevent windows
5019 - The IOCP backend now works even when the user has not specified
5020 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
5021 Fixes part of bug 3752.
5022 - Correctly record the bytes we've read and written when using
5023 bufferevents, so that we can include them in our bandwidth history
5024 and advertised bandwidth. Fixes bug 3803.
5025 - Apply rate-limiting only at the bottom of a chain of filtering
5026 bufferevents. This prevents us from filling up internal read
5027 buffers and violating rate-limits when filtering bufferevents
5028 are enabled. Fixes part of bug 3804.
5029 - Add high-watermarks to the output buffers for filtered
5030 bufferevents. This prevents us from filling up internal write
5031 buffers and wasting CPU cycles when filtering bufferevents are
5032 enabled. Fixes part of bug 3804.
5033 - Correctly notice when data has been written from a bufferevent
5034 without flushing it completely. Fixes bug 3805.
5035 - Fix a bug where server-side tunneled bufferevent-based directory
5036 streams would get closed prematurely. Fixes bug 3814.
5037 - Fix a use-after-free error with per-connection rate-limiting
5038 buckets. Fixes bug 3888.
5040 o Major bugfixes (also part of 0.2.2.31-rc):
5041 - If we're configured to write our ControlPorts to disk, only write
5042 them after switching UID and creating the data directory. This way,
5043 we don't fail when starting up with a nonexistent DataDirectory
5044 and a ControlPortWriteToFile setting based on that directory. Fixes
5045 bug 3747; bugfix on Tor 0.2.2.26-beta.
5048 - Added a new CONF_CHANGED event so that controllers can be notified
5049 of any configuration changes made by other controllers, or by the
5050 user. Implements ticket 1692.
5051 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
5052 leak when using bufferevents, and lets Libevent worry about how to
5053 best copy data out of a buffer.
5054 - Replace files in stats/ rather than appending to them. Now that we
5055 include statistics in extra-info descriptors, it makes no sense to
5056 keep old statistics forever. Implements ticket 2930.
5058 o Minor features (build compatibility):
5059 - Limited, experimental support for building with nmake and MSVC.
5060 - Provide a substitute implementation of lround() for MSVC, which
5061 apparently lacks it. Patch from Gisle Vanem.
5063 o Minor features (also part of 0.2.2.31-rc):
5064 - Update to the August 2 2011 Maxmind GeoLite Country database.
5066 o Minor bugfixes (on 0.2.3.x-alpha):
5067 - Fix a spurious warning when parsing SOCKS requests with
5068 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
5069 - Get rid of a harmless warning that could happen on relays running
5070 with bufferevents. The warning was caused by someone doing an http
5071 request to a relay's orport. Also don't warn for a few related
5072 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
5074 o Minor bugfixes (on 2.2.x and earlier):
5075 - Correct the man page to explain that HashedControlPassword and
5076 CookieAuthentication can both be set, in which case either method
5077 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
5078 when we decided to allow these config options to both be set. Issue
5080 - The "--quiet" and "--hush" options now apply not only to Tor's
5081 behavior before logs are configured, but also to Tor's behavior in
5082 the absense of configured logs. Fixes bug 3550; bugfix on
5085 o Minor bugfixes (also part of 0.2.2.31-rc):
5086 - Write several files in text mode, on OSes that distinguish text
5087 mode from binary mode (namely, Windows). These files are:
5088 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
5089 that collect those statistics; 'client_keys' and 'hostname' for
5090 hidden services that use authentication; and (in the tor-gencert
5091 utility) newly generated identity and signing keys. Previously,
5092 we wouldn't specify text mode or binary mode, leading to an
5093 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
5094 the DirRecordUsageByCountry option which would have triggered
5095 the assertion failure was added), although this assertion failure
5096 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
5097 - Selectively disable deprecation warnings on OS X because Lion
5098 started deprecating the shipped copy of openssl. Fixes bug 3643.
5099 - Remove an extra pair of quotation marks around the error
5100 message in control-port STATUS_GENERAL BUG events. Bugfix on
5101 0.1.2.6-alpha; fixes bug 3732.
5102 - When unable to format an address as a string, report its value
5103 as "???" rather than reusing the last formatted address. Bugfix
5106 o Code simplifications and refactoring:
5107 - Rewrite the listener-selection logic so that parsing which ports
5108 we want to listen on is now separate from binding to the ports
5112 - Building Tor with bufferevent support now requires Libevent
5113 2.0.13-stable or later. Previous versions of Libevent had bugs in
5114 SSL-related bufferevents and related issues that would make Tor
5115 work badly with bufferevents. Requiring 2.0.13-stable also allows
5116 Tor with bufferevents to take advantage of Libevent APIs
5117 introduced after 2.0.8-rc.
5120 Changes in version 0.2.2.32 - 2011-08-27
5121 The Tor 0.2.2 release series is dedicated to the memory of Andreas
5122 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
5123 a founder of the PETS community, a leader in our field, a mentor,
5124 and a friend. He left us with these words: "I had the possibility
5125 to contribute to this world that is not as it should be. I hope I
5126 could help in some areas to make the world a better place, and that
5127 I could also encourage other people to be engaged in improving the
5128 world. Please, stay engaged. This world needs you, your love, your
5129 initiative -- now I cannot be part of that anymore."
5131 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
5132 ready. More than two years in the making, this release features improved
5133 client performance and hidden service reliability, better compatibility
5134 for Android, correct behavior for bridges that listen on more than
5135 one address, more extensible and flexible directory object handling,
5136 better reporting of network statistics, improved code security, and
5137 many many other features and bugfixes.
5140 Changes in version 0.2.2.31-rc - 2011-08-17
5141 Tor 0.2.2.31-rc is the second and hopefully final release candidate
5142 for the Tor 0.2.2.x series.
5145 - Remove an extra pair of quotation marks around the error
5146 message in control-port STATUS_GENERAL BUG events. Bugfix on
5147 0.1.2.6-alpha; fixes bug 3732.
5148 - If we're configured to write our ControlPorts to disk, only write
5149 them after switching UID and creating the data directory. This way,
5150 we don't fail when starting up with a nonexistent DataDirectory
5151 and a ControlPortWriteToFile setting based on that directory. Fixes
5152 bug 3747; bugfix on Tor 0.2.2.26-beta.
5155 - Update to the August 2 2011 Maxmind GeoLite Country database.
5158 - Allow GETINFO fingerprint to return a fingerprint even when
5159 we have not yet built a router descriptor. Fixes bug 3577;
5160 bugfix on 0.2.0.1-alpha.
5161 - Write several files in text mode, on OSes that distinguish text
5162 mode from binary mode (namely, Windows). These files are:
5163 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
5164 that collect those statistics; 'client_keys' and 'hostname' for
5165 hidden services that use authentication; and (in the tor-gencert
5166 utility) newly generated identity and signing keys. Previously,
5167 we wouldn't specify text mode or binary mode, leading to an
5168 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
5169 the DirRecordUsageByCountry option which would have triggered
5170 the assertion failure was added), although this assertion failure
5171 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
5172 - Selectively disable deprecation warnings on OS X because Lion
5173 started deprecating the shipped copy of openssl. Fixes bug 3643.
5174 - When unable to format an address as a string, report its value
5175 as "???" rather than reusing the last formatted address. Bugfix
5179 Changes in version 0.2.3.2-alpha - 2011-07-18
5180 Tor 0.2.3.2-alpha introduces two new experimental features:
5181 microdescriptors and pluggable transports. It also continues cleaning
5182 up a variety of recently introduced features.
5185 - Clients can now use microdescriptors instead of regular descriptors
5186 to build circuits. Microdescriptors are authority-generated
5187 summaries of regular descriptors' contents, designed to change
5188 very rarely (see proposal 158 for details). This feature is
5189 designed to save bandwidth, especially for clients on slow internet
5190 connections. It's off by default for now, since nearly no caches
5191 support it, but it will be on-by-default for clients in a future
5192 version. You can use the UseMicrodescriptors option to turn it on.
5193 - Tor clients using bridges can now be configured to use a separate
5194 'transport' proxy for each bridge. This approach helps to resist
5195 censorship by allowing bridges to use protocol obfuscation
5196 plugins. It implements part of proposal 180. Implements ticket 2841.
5197 - While we're trying to bootstrap, record how many TLS connections
5198 fail in each state, and report which states saw the most failures
5199 in response to any bootstrap failures. This feature may speed up
5200 diagnosis of censorship events. Implements ticket 3116.
5202 o Major bugfixes (on 0.2.3.1-alpha):
5203 - When configuring a large set of nodes in EntryNodes (as with
5204 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
5205 random subset to be guards, and choose them in random
5206 order. Fixes bug 2798.
5207 - Tor could crash when remembering a consensus in a non-used consensus
5208 flavor without having a current consensus set. Fixes bug 3361.
5209 - Comparing an unknown address to a microdescriptor's shortened exit
5210 policy would always give a "rejected" result. Fixes bug 3599.
5211 - Using microdescriptors as a client no longer prevents Tor from
5212 uploading and downloading hidden service descriptors. Fixes
5216 - Allow nameservers with IPv6 address. Resolves bug 2574.
5217 - Accept attempts to include a password authenticator in the
5218 handshake, as supported by SOCKS5. This handles SOCKS clients that
5219 don't know how to omit a password when authenticating. Resolves
5221 - When configuring a large set of nodes in EntryNodes, and there are
5222 enough of them listed as Guard so that we don't need to consider
5223 the non-guard entries, prefer the ones listed with the Guard flag.
5224 - Check for and recover from inconsistency in the microdescriptor
5225 cache. This will make it harder for us to accidentally free a
5226 microdescriptor without removing it from the appropriate data
5227 structures. Fixes issue 3135; issue noted by "wanoskarnet".
5228 - Log SSL state transitions at log level DEBUG, log domain
5229 HANDSHAKE. This can be useful for debugging censorship events.
5230 Implements ticket 3264.
5231 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
5232 implements ticket 3439.
5234 o Minor bugfixes (on 0.2.3.1-alpha):
5235 - Do not free all general-purpose regular descriptors just
5236 because microdescriptor use is enabled. Fixes bug 3113.
5237 - Correctly link libevent_openssl when --enable-static-libevent
5238 is passed to configure. Fixes bug 3118.
5239 - Bridges should not complain during their heartbeat log messages that
5240 they are unlisted in the consensus: that's more or less the point
5241 of being a bridge. Fixes bug 3183.
5242 - Report a SIGNAL event to controllers when acting on a delayed
5243 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
5244 event to the controller if we acted on a SIGNAL NEWNYM command
5245 immediately, and otherwise not report a SIGNAL event for the
5246 command at all. Fixes bug 3349.
5247 - Fix a crash when handling the SIGNAL controller command or
5248 reporting ERR-level status events with bufferevents enabled. Found
5249 by Robert Ransom. Fixes bug 3367.
5250 - Always ship the tor-fw-helper manpage in our release tarballs.
5251 Fixes bug 3389. Reported by Stephen Walker.
5252 - Fix a class of double-mark-for-close bugs when bufferevents
5253 are enabled. Fixes bug 3403.
5254 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
5255 - Add SIGNAL to the list returned by the 'GETINFO events/names'
5256 control-port command. Fixes part of bug 3465.
5257 - Prevent using negative indices during unit test runs when read_all()
5258 fails. Spotted by coverity.
5259 - Fix a rare memory leak when checking the nodelist without it being
5260 present. Found by coverity.
5261 - Only try to download a microdescriptor-flavored consensus from
5262 a directory cache that provides them.
5264 o Minor bugfixes (on 0.2.2.x and earlier):
5265 - Assert that hidden-service-related operations are not performed
5266 using single-hop circuits. Previously, Tor would assert that
5267 client-side streams are not attached to single-hop circuits,
5268 but not that other sensitive operations on the client and service
5269 side are not performed using single-hop circuits. Fixes bug 3332;
5271 - Don't publish a new relay descriptor when we reload our onion key,
5272 unless the onion key has actually changed. Fixes bug 3263 and
5273 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
5274 - Allow GETINFO fingerprint to return a fingerprint even when
5275 we have not yet built a router descriptor. Fixes bug 3577;
5276 bugfix on 0.2.0.1-alpha.
5277 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
5278 on 0.2.2.4-alpha; fixes bug 3427.
5280 o Code simplification and refactoring:
5281 - Use tor_sscanf() in place of scanf() in more places through the
5282 code. This makes us a little more locale-independent, and
5283 should help shut up code-analysis tools that can't tell
5284 a safe sscanf string from a dangerous one.
5285 - Use tt_assert(), not tor_assert(), for checking for test failures.
5286 This makes the unit tests more able to go on in the event that
5288 - Split connection_about_to_close() into separate functions for each
5292 - On Windows, we now define the _WIN32_WINNT macros only if they
5293 are not already defined. This lets the person building Tor decide,
5294 if they want, to require a later version of Windows.
5297 Changes in version 0.2.2.30-rc - 2011-07-07
5298 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
5299 series. It fixes a few smaller bugs, but generally appears stable.
5300 Please test it and let us know whether it is!
5303 - Send a SUCCEEDED stream event to the controller when a reverse
5304 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
5305 discovered by katmagic.
5306 - Always NUL-terminate the sun_path field of a sockaddr_un before
5307 passing it to the kernel. (Not a security issue: kernels are
5308 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5309 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5310 - Don't stack-allocate the list of supplementary GIDs when we're
5311 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
5312 could take up to 256K, which is way too much stack. Found by
5313 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
5314 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
5315 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
5316 fixes part of bug 3465.
5317 - Fix a memory leak when receiving a descriptor for a hidden
5318 service we didn't ask for. Found by Coverity; CID #30. Bugfix
5322 - Update to the July 1 2011 Maxmind GeoLite Country database.
5325 Changes in version 0.2.2.29-beta - 2011-06-20
5326 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
5327 have bridge lines in their torrc but don't want to use them; gets
5328 us closer to having the control socket feature working on Debian;
5329 and fixes a variety of smaller bugs.
5332 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
5333 When we changed the default behavior to "use bridges if any
5334 are listed in the torrc", we surprised users who had bridges
5335 in their torrc files but who didn't actually want to use them.
5336 Partial resolution for bug 3354.
5339 - Don't attach new streams to old rendezvous circuits after SIGNAL
5340 NEWNYM. Previously, we would keep using an existing rendezvous
5341 circuit if it remained open (i.e. if it were kept open by a
5342 long-lived stream, or if a new stream were attached to it before
5343 Tor could notice that it was old and no longer in use). Bugfix on
5344 0.1.1.15-rc; fixes bug 3375.
5347 - Fix a bug when using ControlSocketsGroupWritable with User. The
5348 directory's group would be checked against the current group, not
5349 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
5350 bugfix on 0.2.2.26-beta.
5351 - Make connection_printf_to_buf()'s behaviour sane. Its callers
5352 expect it to emit a CRLF iff the format string ends with CRLF;
5353 it actually emitted a CRLF iff (a) the format string ended with
5354 CRLF or (b) the resulting string was over 1023 characters long or
5355 (c) the format string did not end with CRLF *and* the resulting
5356 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
5357 fixes part of bug 3407.
5358 - Make send_control_event_impl()'s behaviour sane. Its callers
5359 expect it to always emit a CRLF at the end of the string; it
5360 might have emitted extra control characters as well. Bugfix on
5361 0.1.1.9-alpha; fixes another part of bug 3407.
5362 - Make crypto_rand_int() check the value of its input correctly.
5363 Previously, it accepted values up to UINT_MAX, but could return a
5364 negative number if given a value above INT_MAX+1. Found by George
5365 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
5366 - Avoid a segfault when reading a malformed circuit build state
5367 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
5369 - When asked about a DNS record type we don't support via a
5370 client DNSPort, reply with NOTIMPL rather than an empty
5371 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
5372 - Fix a rare memory leak during stats writing. Found by coverity.
5375 - Update to the June 1 2011 Maxmind GeoLite Country database.
5377 o Code simplifications and refactoring:
5378 - Remove some dead code as indicated by coverity.
5379 - Remove a few dead assignments during router parsing. Found by
5381 - Add some forgotten return value checks during unit tests. Found
5383 - Don't use 1-bit wide signed bit fields. Found by coverity.
5386 Changes in version 0.2.2.28-beta - 2011-06-04
5387 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
5388 fixed a big bug in whether relays stay in the consensus consistently,
5389 we moved closer to handling bridges and hidden services correctly,
5390 and we started the process of better handling the dreaded "my Vidalia
5391 died, and now my Tor demands a password when I try to reconnect to it"
5395 - Don't decide to make a new descriptor when receiving a HUP signal.
5396 This bug has caused a lot of 0.2.2.x relays to disappear from the
5397 consensus periodically. Fixes the most common case of triggering
5398 bug 1810; bugfix on 0.2.2.7-alpha.
5399 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
5400 - Don't try to build descriptors if "ORPort auto" is set and we
5401 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
5403 - Resolve a crash that occurred when setting BridgeRelay to 1 with
5404 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
5405 - Apply circuit timeouts to opened hidden-service-related circuits
5406 based on the correct start time. Previously, we would apply the
5407 circuit build timeout based on time since the circuit's creation;
5408 it was supposed to be applied based on time since the circuit
5409 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
5410 - Use the same circuit timeout for client-side introduction
5411 circuits as for other four-hop circuits, rather than the timeout
5412 for single-hop directory-fetch circuits; the shorter timeout may
5413 have been appropriate with the static circuit build timeout in
5414 0.2.1.x and earlier, but caused many hidden service access attempts
5415 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
5416 on 0.2.2.2-alpha; fixes another part of bug 1297.
5417 - In ticket 2511 we fixed a case where you could use an unconfigured
5418 bridge if you had configured it as a bridge the last time you ran
5419 Tor. Now fix another edge case: if you had configured it as a bridge
5420 but then switched to a different bridge via the controller, you
5421 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
5425 - Add an __OwningControllerProcess configuration option and a
5426 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
5427 that when it exits, Tor will shut down. Implements feature 3049.
5428 - If "UseBridges 1" is set and no bridges are configured, Tor will
5429 now refuse to build any circuits until some bridges are set.
5430 If "UseBridges auto" is set, Tor will use bridges if they are
5431 configured and we are not running as a server, but otherwise will
5432 make circuits as usual. The new default is "auto". Patch by anonym,
5433 so the Tails LiveCD can stop automatically revealing you as a Tor
5437 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5438 - Remove a trailing asterisk from "exit-policy/default" in the
5439 output of the control port command "GETINFO info/names". Bugfix
5441 - Use a wide type to hold sockets when built for 64-bit Windows builds.
5443 - Warn when the user configures two HiddenServiceDir lines that point
5444 to the same directory. Bugfix on 0.0.6 (the version introducing
5445 HiddenServiceDir); fixes bug 3289.
5446 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
5447 part of bug 2748; bugfix on 0.2.0.10-alpha.
5448 - Log malformed requests for rendezvous descriptors as protocol
5449 warnings, not warnings. Also, use a more informative log message
5450 in case someone sees it at log level warning without prior
5451 info-level messages. Fixes the other part of bug 2748; bugfix
5453 - Clear the table recording the time of the last request for each
5454 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
5455 Previously, we would clear our HS descriptor cache on SIGNAL
5456 NEWNYM, but if we had previously retrieved a descriptor (or tried
5457 to) from every directory responsible for it, we would refuse to
5458 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
5460 - Fix a log message that said "bits" while displaying a value in
5461 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
5463 - When checking for 1024-bit keys, check for 1024 bits, not 128
5464 bytes. This allows Tor to correctly discard keys of length 1017
5465 through 1023. Bugfix on 0.0.9pre5.
5468 - Relays now log the reason for publishing a new relay descriptor,
5469 so we have a better chance of hunting down instances of bug 1810.
5470 Resolves ticket 3252.
5471 - Revise most log messages that refer to nodes by nickname to
5472 instead use the "$key=nickname at address" format. This should be
5473 more useful, especially since nicknames are less and less likely
5474 to be unique. Resolves ticket 3045.
5475 - Log (at info level) when purging pieces of hidden-service-client
5476 state because of SIGNAL NEWNYM.
5479 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5480 anything since 0.2.1.16-rc.
5483 Changes in version 0.2.2.27-beta - 2011-05-18
5484 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
5485 release, and also adds a few more general bugfixes.
5488 - Fix a crash bug when changing bridges in a running Tor process.
5489 Fixes bug 3213; bugfix on 0.2.2.26-beta.
5490 - When the controller configures a new bridge, don't wait 10 to 60
5491 seconds before trying to fetch its descriptor. Bugfix on
5492 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
5495 - Require that onion keys have exponent 65537 in microdescriptors too.
5496 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
5497 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
5498 Changed the limit to 512 characters by removing base64 newlines.
5499 Fixes bug 2752. Fix by Michael Yakubovich.
5500 - When a client starts or stops using bridges, never use a circuit
5501 that was built before the configuration change. This behavior could
5502 put at risk a user who uses bridges to ensure that her traffic
5503 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
5507 Changes in version 0.2.2.26-beta - 2011-05-17
5508 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
5509 also introduces a new "socksport auto" approach that should make it
5510 easier to run multiple Tors on the same system, and does a lot of
5511 cleanup to get us closer to a release candidate.
5513 o Security/privacy fixes:
5514 - Replace all potentially sensitive memory comparison operations
5515 with versions whose runtime does not depend on the data being
5516 compared. This will help resist a class of attacks where an
5517 adversary can use variations in timing information to learn
5518 sensitive data. Fix for one case of bug 3122. (Safe memcmp
5519 implementation by Robert Ransom based partially on code by DJB.)
5520 - When receiving a hidden service descriptor, check that it is for
5521 the hidden service we wanted. Previously, Tor would store any
5522 hidden service descriptors that a directory gave it, whether it
5523 wanted them or not. This wouldn't have let an attacker impersonate
5524 a hidden service, but it did let directories pre-seed a client
5525 with descriptors that it didn't want. Bugfix on 0.0.6.
5526 - On SIGHUP, do not clear out all TrackHostExits mappings, client
5527 DNS cache entries, and virtual address mappings: that's what
5528 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
5531 - The options SocksPort, ControlPort, and so on now all accept a
5532 value "auto" that opens a socket on an OS-selected port. A
5533 new ControlPortWriteToFile option tells Tor to write its
5534 actual control port or ports to a chosen file. If the option
5535 ControlPortFileGroupReadable is set, the file is created as
5536 group-readable. Now users can run two Tor clients on the same
5537 system without needing to manually mess with parameters. Resolves
5538 part of ticket 3076.
5539 - Set SO_REUSEADDR on all sockets, not just listeners. This should
5540 help busy exit nodes avoid running out of useable ports just
5541 because all the ports have been used in the near past. Resolves
5545 - New "GETINFO net/listeners/(type)" controller command to return
5546 a list of addresses and ports that are bound for listeners for a
5547 given connection type. This is useful when the user has configured
5548 "SocksPort auto" and the controller needs to know which port got
5549 chosen. Resolves another part of ticket 3076.
5550 - Add a new ControlSocketsGroupWritable configuration option: when
5551 it is turned on, ControlSockets are group-writeable by the default
5552 group of the current user. Patch by Jérémy Bobbio; implements
5554 - Tor now refuses to create a ControlSocket in a directory that is
5555 world-readable (or group-readable if ControlSocketsGroupWritable
5556 is 0). This is necessary because some operating systems do not
5557 enforce permissions on an AF_UNIX sockets. Permissions on the
5558 directory holding the socket, however, seems to work everywhere.
5559 - Rate-limit a warning about failures to download v2 networkstatus
5560 documents. Resolves part of bug 1352.
5561 - Backport code from 0.2.3.x that allows directory authorities to
5562 clean their microdescriptor caches. Needed to resolve bug 2230.
5563 - When an HTTPS proxy reports "403 Forbidden", we now explain
5564 what it means rather than calling it an unexpected status code.
5565 Closes bug 2503. Patch from Michael Yakubovich.
5566 - Update to the May 1 2011 Maxmind GeoLite Country database.
5569 - Authorities now clean their microdesc cache periodically and when
5570 reading from disk initially, not only when adding new descriptors.
5571 This prevents a bug where we could lose microdescriptors. Bugfix
5572 on 0.2.2.6-alpha. Fixes bug 2230.
5573 - Do not crash when our configuration file becomes unreadable, for
5574 example due to a permissions change, between when we start up
5575 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5577 - Avoid a bug that would keep us from replacing a microdescriptor
5578 cache on Windows. (We would try to replace the file while still
5579 holding it open. That's fine on Unix, but Windows doesn't let us
5580 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
5581 - Add missing explanations for the authority-related torrc options
5582 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
5583 man page. Resolves issue 2379.
5584 - As an authority, do not upload our own vote or signature set to
5585 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
5586 it would get flagged as a duplicate. Resolves bug 3026.
5587 - Accept hidden service descriptors if we think we might be a hidden
5588 service directory, regardless of what our consensus says. This
5589 helps robustness, since clients and hidden services can sometimes
5590 have a more up-to-date view of the network consensus than we do,
5591 and if they think that the directory authorities list us a HSDir,
5592 we might actually be one. Related to bug 2732; bugfix on
5594 - When a controller changes TrackHostExits, remove mappings for
5595 hosts that should no longer have their exits tracked. Bugfix on
5597 - When a controller changes VirtualAddrNetwork, remove any mappings
5598 for hosts that were automapped to the old network. Bugfix on
5600 - When a controller changes one of the AutomapHosts* options, remove
5601 any mappings for hosts that should no longer be automapped. Bugfix
5603 - Do not reset the bridge descriptor download status every time we
5604 re-parse our configuration or get a configuration change. Fixes
5605 bug 3019; bugfix on 0.2.0.3-alpha.
5607 o Minor bugfixes (code cleanup):
5608 - When loading the microdesc journal, remember its current size.
5609 In 0.2.2, this helps prevent the microdesc journal from growing
5610 without limit on authorities (who are the only ones to use it in
5611 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5612 Fix posted by "cypherpunks."
5613 - The microdesc journal is supposed to get rebuilt only if it is
5614 at least _half_ the length of the store, not _twice_ the length
5615 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5616 - Fix a potential null-pointer dereference while computing a
5617 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
5619 - Avoid a possible null-pointer dereference when rebuilding the mdesc
5620 cache without actually having any descriptors to cache. Bugfix on
5621 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
5622 - If we fail to compute the identity digest of a v3 legacy keypair,
5623 warn, and don't use a buffer-full of junk instead. Bugfix on
5624 0.2.1.1-alpha; fixes bug 3106.
5625 - Resolve an untriggerable issue in smartlist_string_num_isin(),
5626 where if the function had ever in the future been used to check
5627 for the presence of a too-large number, it would have given an
5628 incorrect result. (Fortunately, we only used it for 16-bit
5629 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
5630 - Require that introduction point keys and onion handshake keys
5631 have a public exponent of 65537. Starts to fix bug 3207; bugfix
5635 - Caches no longer download and serve v2 networkstatus documents
5636 unless FetchV2Networkstatus flag is set: these documents haven't
5637 haven't been used by clients or relays since 0.2.0.x. Resolves
5641 Changes in version 0.2.3.1-alpha - 2011-05-05
5642 Tor 0.2.3.1-alpha adds some new experimental features, including support
5643 for an improved network IO backend, IOCP networking on Windows,
5644 microdescriptor caching, "fast-start" support for streams, and automatic
5645 home router configuration. There are also numerous internal improvements
5646 to try to make the code easier for developers to work with.
5648 This is the first alpha release in a new series, so expect there to be
5649 bugs. Users who would rather test out a more stable branch should
5650 stay with 0.2.2.x for now.
5653 - Tor can now optionally build with the "bufferevents" buffered IO
5654 backend provided by Libevent 2. To use this feature, make sure you
5655 have the latest possible version of Libevent, and pass the
5656 --enable-bufferevents flag to configure when building Tor from
5657 source. This feature will make our networking code more flexible,
5658 let us stack layers on each other, and let us use more efficient
5659 zero-copy transports where available.
5660 - As an experimental feature, Tor can use IOCP for networking on Windows.
5661 Once this code is tuned and optimized, it promises much better
5662 performance than the select-based backend we've used in the past. To
5663 try this feature, you must build Tor with Libevent 2, configure Tor
5664 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
5665 your torrc. There are known bugs here: only try this if you can help
5666 debug it as it breaks.
5667 - The EntryNodes option can now include country codes like {de} or IP
5668 addresses or network masks. Previously we had disallowed these options
5669 because we didn't have an efficient way to keep the list up to
5670 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
5671 - Exit nodes now accept and queue data on not-yet-connected streams.
5672 Previously, the client wasn't allowed to send data until the stream was
5673 connected, which slowed down all connections. This change will enable
5674 clients to perform a "fast-start" on streams and send data without
5675 having to wait for a confirmation that the stream has opened. (Patch
5676 from Ian Goldberg; implements the server side of Proposal 174.)
5677 - Tor now has initial support for automatic port mapping on the many
5678 home routers that support NAT-PMP or UPnP. (Not yet supported on
5679 Windows). To build the support code, you'll need to have libnatpnp
5680 library and/or the libminiupnpc library, and you'll need to enable the
5681 feature specifically by passing "--enable-upnp" and/or
5682 "--enable-natpnp" to configure. To turn it on, use the new
5683 PortForwarding option.
5684 - Caches now download, cache, and serve multiple "flavors" of the
5685 consensus, including a flavor that describes microdescriptors.
5686 - Caches now download, cache, and serve microdescriptors -- small
5687 summaries of router descriptors that are authenticated by all of the
5688 directory authorities. Once enough caches are running this code,
5689 clients will be able to save significant amounts of directory bandwidth
5690 by downloading microdescriptors instead of router descriptors.
5693 - Make logging resolution configurable with a new LogTimeGranularity
5694 option, and change the default from 1 millisecond to 1 second.
5695 Implements enhancement 1668.
5696 - We log which torrc file we're using on startup. Implements ticket
5698 - Ordinarily, Tor does not count traffic from private addresses (like
5699 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
5700 There is now a new option, CountPrivateBandwidth, to disable this
5701 behavior. Patch from Daniel Cagara.
5702 - New --enable-static-tor configure option for building Tor as
5703 statically as possible. Idea, general hackery and thoughts from
5704 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
5706 - If you set the NumCPUs option to 0, Tor will now try to detect how
5707 many CPUs you have. This is the new default behavior.
5708 - Turn on directory request statistics by default and include them in
5709 extra-info descriptors. Don't break if we have no GeoIP database.
5710 - Relays that set "ConnDirectionStatistics 1" write statistics on the
5711 bidirectional use of connections to disk every 24 hours.
5712 - Add a GeoIP file digest to the extra-info descriptor. Implements
5714 - The NodeFamily option -- which let you declare that you want to
5715 consider nodes to be part of a family whether they list themselves
5716 that way or not -- now allows IP address ranges and country codes.
5717 - Add a new 'Heartbeat' log message type to periodically log a message
5718 describing Tor's status at level Notice. This feature is meant for
5719 operators who log at notice, and want to make sure that their Tor
5720 server is still working. Implementation by George Kadianakis.
5722 o Minor bugfixes (on 0.2.2.25-alpha):
5723 - When loading the microdesc journal, remember its current size.
5724 In 0.2.2, this helps prevent the microdesc journal from growing
5725 without limit on authorities (who are the only ones to use it in
5726 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5727 Fix posted by "cypherpunks."
5728 - The microdesc journal is supposed to get rebuilt only if it is
5729 at least _half_ the length of the store, not _twice_ the length
5730 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5731 - If as an authority we fail to compute the identity digest of a v3
5732 legacy keypair, warn, and don't use a buffer-full of junk instead.
5733 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
5734 - Authorities now clean their microdesc cache periodically and when
5735 reading from disk initially, not only when adding new descriptors.
5736 This prevents a bug where we could lose microdescriptors. Bugfix
5739 o Minor features (controller):
5740 - Add a new SIGNAL event to the controller interface so that
5741 controllers can be notified when Tor handles a signal. Resolves
5742 issue 1955. Patch by John Brooks.
5743 - Add a new GETINFO option to get total bytes read and written. Patch
5744 from pipe, revised by atagar. Resolves ticket 2345.
5745 - Implement some GETINFO controller fields to provide information about
5746 the Tor process's pid, euid, username, and resource limits.
5749 - Our build system requires automake 1.6 or later to create the
5750 Makefile.in files. Previously, you could have used 1.4.
5751 This only affects developers and people building Tor from git;
5752 people who build Tor from the source distribution without changing
5753 the Makefile.am files should be fine.
5754 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
5755 so on. This is more robust against some of the failure modes
5756 associated with running the autotools pieces on their own.
5758 o Minor packaging issues:
5759 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
5760 already created. Patch from Andreas Stieger. Fixes bug 2573.
5762 o Code simplifications and refactoring:
5763 - A major revision to our internal node-selecting and listing logic.
5764 Tor already had at least two major ways to look at the question of
5765 "which Tor servers do we know about": a list of router descriptors,
5766 and a list of entries in the current consensus. With
5767 microdescriptors, we're adding a third. Having so many systems
5768 without an abstraction layer over them was hurting the codebase.
5769 Now, we have a new "node_t" abstraction that presents a consistent
5770 interface to a client's view of a Tor node, and holds (nearly) all
5771 of the mutable state formerly in routerinfo_t and routerstatus_t.
5772 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
5773 no longer link against Libevent: they never used it, but
5774 our library structure used to force them to link it.
5777 - Remove some old code to work around even older versions of Tor that
5778 used forked processes to handle DNS requests. Such versions of Tor
5779 are no longer in use as servers.
5781 o Documentation fixes:
5782 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
5783 - Add missing documentation for the authority-related torrc options
5784 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
5788 Changes in version 0.2.2.25-alpha - 2011-04-29
5789 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
5790 robust, routers no longer overreport their bandwidth, Win7 should crash
5791 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
5792 now prevents hidden service-related activity from being linkable. It
5793 provides more information to Vidalia so you can see if your bridge is
5794 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
5795 StrictNodes configuration options to make them more reliable, more
5796 understandable, and more regularly applied. If you use those options,
5797 please see the revised documentation for them in the manual page.
5800 - Relays were publishing grossly inflated bandwidth values because
5801 they were writing their state files wrong--now they write the
5802 correct value. Also, resume reading bandwidth history from the
5803 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
5804 - Improve hidden service robustness: When we find that we have
5805 extended a hidden service's introduction circuit to a relay not
5806 listed as an introduction point in the HS descriptor we currently
5807 have, retry with an introduction point from the current
5808 descriptor. Previously we would just give up. Fixes bugs 1024 and
5809 1930; bugfix on 0.2.0.10-alpha.
5810 - Clients now stop trying to use an exit node associated with a given
5811 destination by TrackHostExits if they fail to reach that exit node.
5812 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
5813 - Fix crash bug on platforms where gmtime and localtime can return
5814 NULL. Windows 7 users were running into this one. Fixes part of bug
5815 2077. Bugfix on all versions of Tor. Found by boboper.
5817 o Security and stability fixes:
5818 - Don't double-free a parsable, but invalid, microdescriptor, even if
5819 it is followed in the blob we're parsing by an unparsable
5820 microdescriptor. Fixes an issue reported in a comment on bug 2954.
5821 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
5822 - If the Nickname configuration option isn't given, Tor would pick a
5823 nickname based on the local hostname as the nickname for a relay.
5824 Because nicknames are not very important in today's Tor and the
5825 "Unnamed" nickname has been implemented, this is now problematic
5826 behavior: It leaks information about the hostname without being
5827 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
5828 introduced the Unnamed nickname. Reported by tagnaq.
5829 - Fix an uncommon assertion failure when running with DNSPort under
5830 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5831 - Avoid linkability based on cached hidden service descriptors: forget
5832 all hidden service descriptors cached as a client when processing a
5833 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5836 - Export GeoIP information on bridge usage to controllers even if we
5837 have not yet been running for 24 hours. Now Vidalia bridge operators
5838 can get more accurate and immediate feedback about their
5839 contributions to the network.
5841 o Major features and bugfixes (node selection):
5842 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
5843 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
5844 options. Previously, we had been ambiguous in describing what
5845 counted as an "exit" node, and what operations exactly "StrictNodes
5846 0" would permit. This created confusion when people saw nodes built
5847 through unexpected circuits, and made it hard to tell real bugs from
5848 surprises. Now the intended behavior is:
5849 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
5850 a node that delivers user traffic outside the Tor network.
5851 . "Entry", in the context of EntryNodes, means a node used as the
5852 first hop of a multihop circuit. It doesn't include direct
5853 connections to directory servers.
5854 . "ExcludeNodes" applies to all nodes.
5855 . "StrictNodes" changes the behavior of ExcludeNodes only. When
5856 StrictNodes is set, Tor should avoid all nodes listed in
5857 ExcludeNodes, even when it will make user requests fail. When
5858 StrictNodes is *not* set, then Tor should follow ExcludeNodes
5859 whenever it can, except when it must use an excluded node to
5860 perform self-tests, connect to a hidden service, provide a
5861 hidden service, fulfill a .exit request, upload directory
5862 information, or fetch directory information.
5863 Collectively, the changes to implement the behavior fix bug 1090.
5864 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
5865 a node is listed in both, it's treated as excluded.
5866 - ExcludeNodes now applies to directory nodes -- as a preference if
5867 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
5868 Don't exclude all the directory authorities and set StrictNodes to 1
5869 unless you really want your Tor to break.
5870 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
5871 - ExcludeExitNodes now overrides .exit requests.
5872 - We don't use bridges listed in ExcludeNodes.
5873 - When StrictNodes is 1:
5874 . We now apply ExcludeNodes to hidden service introduction points
5875 and to rendezvous points selected by hidden service users. This
5876 can make your hidden service less reliable: use it with caution!
5877 . If we have used ExcludeNodes on ourself, do not try relay
5878 reachability self-tests.
5879 . If we have excluded all the directory authorities, we will not
5880 even try to upload our descriptor if we're a relay.
5881 . Do not honor .exit requests to an excluded node.
5882 - Remove a misfeature that caused us to ignore the Fast/Stable flags
5883 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
5884 - When the set of permitted nodes changes, we now remove any mappings
5885 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
5887 - We never cannibalize a circuit that had excluded nodes on it, even
5888 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
5889 - Revert a change where we would be laxer about attaching streams to
5890 circuits than when building the circuits. This was meant to prevent
5891 a set of bugs where streams were never attachable, but our improved
5892 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
5893 - Keep track of how many times we launch a new circuit to handle a
5894 given stream. Too many launches could indicate an inconsistency
5895 between our "launch a circuit to handle this stream" logic and our
5896 "attach this stream to one of the available circuits" logic.
5897 - Improve log messages related to excluded nodes.
5900 - Fix a spurious warning when moving from a short month to a long
5901 month on relays with month-based BandwidthAccounting. Bugfix on
5902 0.2.2.17-alpha; fixes bug 3020.
5903 - When a client finds that an origin circuit has run out of 16-bit
5904 stream IDs, we now mark it as unusable for new streams. Previously,
5905 we would try to close the entire circuit. Bugfix on 0.0.6.
5906 - Add a forgotten cast that caused a compile warning on OS X 10.6.
5907 Bugfix on 0.2.2.24-alpha.
5908 - Be more careful about reporting the correct error from a failed
5909 connect() system call. Under some circumstances, it was possible to
5910 look at an incorrect value for errno when sending the end reason.
5911 Bugfix on 0.1.0.1-rc.
5912 - Correctly handle an "impossible" overflow cases in connection byte
5913 counting, where we write or read more than 4GB on an edge connection
5914 in a single second. Bugfix on 0.1.2.8-beta.
5915 - Correct the warning displayed when a rendezvous descriptor exceeds
5916 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5918 - Clients and hidden services now use HSDir-flagged relays for hidden
5919 service descriptor downloads and uploads even if the relays have no
5920 DirPort set and the client has disabled TunnelDirConns. This will
5921 eventually allow us to give the HSDir flag to relays with no
5922 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5923 - Downgrade "no current certificates known for authority" message from
5924 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5925 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
5926 2917. Bugfix on 0.1.1.1-alpha.
5927 - Only limit the lengths of single HS descriptors, even when multiple
5928 HS descriptors are published to an HSDir relay in a single POST
5929 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5930 - Write the current time into the LastWritten line in our state file,
5931 rather than the time from the previous write attempt. Also, stop
5932 trying to use a time of -1 in our log statements. Fixes bug 3039;
5933 bugfix on 0.2.2.14-alpha.
5934 - Be more consistent in our treatment of file system paths. "~" should
5935 get expanded to the user's home directory in the Log config option.
5936 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
5937 feature for the -f and --DataDirectory options.
5940 - Make sure every relay writes a state file at least every 12 hours.
5941 Previously, a relay could go for weeks without writing its state
5942 file, and on a crash could lose its bandwidth history, capacity
5943 estimates, client country statistics, and so on. Addresses bug 3012.
5944 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5945 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5946 clients are already deprecated because of security bugs.
5947 - Don't allow v0 hidden service authorities to act as clients.
5948 Required by fix for bug 3000.
5949 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5950 by fix for bug 3000.
5951 - Ensure that no empty [dirreq-](read|write)-history lines are added
5952 to an extrainfo document. Implements ticket 2497.
5954 o Code simplification and refactoring:
5955 - Remove workaround code to handle directory responses from servers
5956 that had bug 539 (they would send HTTP status 503 responses _and_
5957 send a body too). Since only server versions before
5958 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5959 keep the workaround in place.
5960 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5961 handling calculations where we have a known amount of clock skew and
5962 an allowed amount of unknown skew. But we only used it in three
5963 places, and we never adjusted the known/unknown skew values. This is
5964 still something we might want to do someday, but if we do, we'll
5965 want to do it differently.
5966 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5967 None of the cases where we did this before were wrong, but by making
5968 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5969 - Use GetTempDir to find the proper temporary directory location on
5970 Windows when generating temporary files for the unit tests. Patch by
5974 Changes in version 0.2.2.24-alpha - 2011-04-08
5975 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
5976 prevented Tor clients from effectively using "multihomed" bridges,
5977 that is, bridges that listen on multiple ports or IP addresses so users
5978 can continue to use some of their addresses even if others get blocked.
5981 - Fix a bug where bridge users who configure the non-canonical
5982 address of a bridge automatically switch to its canonical
5983 address. If a bridge listens at more than one address, it should be
5984 able to advertise those addresses independently and any non-blocked
5985 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
5987 - If you configured Tor to use bridge A, and then quit and
5988 configured Tor to use bridge B instead, it would happily continue
5989 to use bridge A if it's still reachable. While this behavior is
5990 a feature if your goal is connectivity, in some scenarios it's a
5991 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5992 - Directory authorities now use data collected from their own
5993 uptime observations when choosing whether to assign the HSDir flag
5994 to relays, instead of trusting the uptime value the relay reports in
5995 its descriptor. This change helps prevent an attack where a small
5996 set of nodes with frequently-changing identity keys can blackhole
5997 a hidden service. (Only authorities need upgrade; others will be
5998 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
6001 - When we restart our relay, we might get a successful connection
6002 from the outside before we've started our reachability tests,
6003 triggering a warning: "ORPort found reachable, but I have no
6004 routerinfo yet. Failing to inform controller of success." This
6005 bug was harmless unless Tor is running under a controller
6006 like Vidalia, in which case the controller would never get a
6007 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
6009 - Make directory authorities more accurate at recording when
6010 relays that have failed several reachability tests became
6011 unreachable, so we can provide more accuracy at assigning Stable,
6012 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
6013 - Fix an issue that prevented static linking of libevent on
6014 some platforms (notably Linux). Fixes bug 2698; bugfix on
6015 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
6016 the --with-static-libevent configure option).
6017 - We now ask the other side of a stream (the client or the exit)
6018 for more data on that stream when the amount of queued data on
6019 that stream dips low enough. Previously, we wouldn't ask the
6020 other side for more data until either it sent us more data (which
6021 it wasn't supposed to do if it had exhausted its window!) or we
6022 had completely flushed all our queued data. This flow control fix
6023 should improve throughput. Fixes bug 2756; bugfix on the earliest
6024 released versions of Tor (svn commit r152).
6025 - Avoid a double-mark-for-free warning when failing to attach a
6026 transparent proxy connection. (We thought we had fixed this in
6027 0.2.2.23-alpha, but it turns out our fix was checking the wrong
6028 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
6029 bug) and 0.2.2.23-alpha (the incorrect fix).
6030 - When warning about missing zlib development packages during compile,
6031 give the correct package names. Bugfix on 0.2.0.1-alpha.
6034 - Directory authorities now log the source of a rejected POSTed v3
6036 - Make compilation with clang possible when using
6037 --enable-gcc-warnings by removing two warning options that clang
6038 hasn't implemented yet and by fixing a few warnings. Implements
6040 - When expiring circuits, use microsecond timers rather than
6041 one-second timers. This can avoid an unpleasant situation where a
6042 circuit is launched near the end of one second and expired right
6043 near the beginning of the next, and prevent fluctuations in circuit
6045 - Use computed circuit-build timeouts to decide when to launch
6046 parallel introduction circuits for hidden services. (Previously,
6047 we would retry after 15 seconds.)
6048 - Update to the April 1 2011 Maxmind GeoLite Country database.
6051 - Create the /var/run/tor directory on startup on OpenSUSE if it is
6052 not already created. Patch from Andreas Stieger. Fixes bug 2573.
6054 o Documentation changes:
6055 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
6056 - Resolve all doxygen warnings except those for missing documentation.
6058 - Add doxygen documentation for more functions, fields, and types.
6061 Changes in version 0.2.2.23-alpha - 2011-03-08
6062 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
6063 they restart they don't lose their bandwidth capacity estimate. This
6064 release also fixes a diverse set of user-facing bugs, ranging from
6065 relays overrunning their rate limiting to clients falsely warning about
6066 clock skew to bridge descriptor leaks by our bridge directory authority.
6069 - Stop sending a CLOCK_SKEW controller status event whenever
6070 we fetch directory information from a relay that has a wrong clock.
6071 Instead, only inform the controller when it's a trusted authority
6072 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
6073 the rest of bug 1074.
6074 - Fix an assert in parsing router descriptors containing IPv6
6075 addresses. This one took down the directory authorities when
6076 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
6077 - Make the bridge directory authority refuse to answer directory
6078 requests for "all" descriptors. It used to include bridge
6079 descriptors in its answer, which was a major information leak.
6080 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
6081 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
6082 Tor would ignore their RelayBandwidthBurst setting,
6083 potentially using more bandwidth than expected. Bugfix on
6084 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
6085 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
6086 hidserv" in her torrc. The 'hidserv' argument never controlled
6087 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
6090 - Relays now save observed peak bandwidth throughput rates to their
6091 state file (along with total usage, which was already saved)
6092 so that they can determine their correct estimated bandwidth on
6093 restart. Resolves bug 1863, where Tor relays would reset their
6094 estimated bandwidth to 0 after restarting.
6095 - Directory authorities now take changes in router IP address and
6096 ORPort into account when determining router stability. Previously,
6097 if a router changed its IP or ORPort, the authorities would not
6098 treat it as having any downtime for the purposes of stability
6099 calculation, whereas clients would experience downtime since the
6100 change could take a while to propagate to them. Resolves issue 1035.
6101 - Enable Address Space Layout Randomization (ASLR) and Data Execution
6102 Prevention (DEP) by default on Windows to make it harder for
6103 attackers to exploit vulnerabilities. Patch from John Brooks.
6105 o Minor bugfixes (on 0.2.1.x and earlier):
6106 - Fix a rare crash bug that could occur when a client was configured
6107 with a large number of bridges. Fixes bug 2629; bugfix on
6108 0.2.1.2-alpha. Bugfix by trac user "shitlei".
6109 - Avoid a double mark-for-free warning when failing to attach a
6110 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
6112 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
6113 found by "cypherpunks". This bug was introduced before the first
6114 Tor release, in svn commit r110.
6115 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
6116 don't mention them in the manpage. Fixes bug 2450; issue
6117 spotted by keb and G-Lo.
6118 - Fix a bug in bandwidth history state parsing that could have been
6119 triggered if a future version of Tor ever changed the timing
6120 granularity at which bandwidth history is measured. Bugfix on
6122 - When a relay decides that its DNS is too broken for it to serve
6123 as an exit server, it advertised itself as a non-exit, but
6124 continued to act as an exit. This could create accidental
6125 partitioning opportunities for users. Instead, if a relay is
6126 going to advertise reject *:* as its exit policy, it should
6127 really act with exit policy "reject *:*". Fixes bug 2366.
6128 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
6129 - In the special case where you configure a public exit relay as your
6130 bridge, Tor would be willing to use that exit relay as the last
6131 hop in your circuit as well. Now we fail that circuit instead.
6132 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
6133 - Fix a bug with our locking implementation on Windows that couldn't
6134 correctly detect when a file was already locked. Fixes bug 2504,
6135 bugfix on 0.2.1.6-alpha.
6136 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
6137 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
6139 - Set target port in get_interface_address6() correctly. Bugfix
6140 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
6141 - Directory authorities are now more robust to hops back in time
6142 when calculating router stability. Previously, if a run of uptime
6143 or downtime appeared to be negative, the calculation could give
6144 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
6146 - Fix an assert that got triggered when using the TestingTorNetwork
6147 configuration option and then issuing a GETINFO config-text control
6148 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
6150 o Minor bugfixes (on 0.2.2.x):
6151 - Clients should not weight BadExit nodes as Exits in their node
6152 selection. Similarly, directory authorities should not count BadExit
6153 bandwidth as Exit bandwidth when computing bandwidth-weights.
6154 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
6155 - Correctly clear our dir_read/dir_write history when there is an
6156 error parsing any bw history value from the state file. Bugfix on
6158 - Resolve a bug in verifying signatures of directory objects
6159 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
6160 Fixes bug 2409. Found by "piebeer".
6161 - Bridge authorities no longer crash on SIGHUP when they try to
6162 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
6166 - Log less aggressively about circuit timeout changes, and improve
6167 some other circuit timeout messages. Resolves bug 2004.
6168 - Log a little more clearly about the times at which we're no longer
6169 accepting new connections. Resolves bug 2181.
6170 - Reject attempts at the client side to open connections to private
6171 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
6172 a randomly chosen exit node. Attempts to do so are always
6173 ill-defined, generally prevented by exit policies, and usually
6174 in error. This will also help to detect loops in transparent
6175 proxy configurations. You can disable this feature by setting
6176 "ClientRejectInternalAddresses 0" in your torrc.
6177 - Always treat failure to allocate an RSA key as an unrecoverable
6179 - Update to the March 1 2011 Maxmind GeoLite Country database.
6181 o Minor features (log subsystem):
6182 - Add documentation for configuring logging at different severities in
6183 different log domains. We've had this feature since 0.2.1.1-alpha,
6184 but for some reason it never made it into the manpage. Fixes
6186 - Make it simpler to specify "All log domains except for A and B".
6187 Previously you needed to say "[*,~A,~B]". Now you can just say
6189 - Add a "LogMessageDomains 1" option to include the domains of log
6190 messages along with the messages. Without this, there's no way
6191 to use log domains without reading the source or doing a lot
6194 o Packaging changes:
6195 - Stop shipping the Tor specs files and development proposal documents
6196 in the tarball. They are now in a separate git repository at
6197 git://git.torproject.org/torspec.git
6200 Changes in version 0.2.1.30 - 2011-02-23
6201 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
6202 change is a slight tweak to Tor's TLS handshake that makes relays
6203 and bridges that run this new version reachable from Iran again.
6204 We don't expect this tweak will win the arms race long-term, but it
6205 buys us time until we roll out a better solution.
6208 - Stop sending a CLOCK_SKEW controller status event whenever
6209 we fetch directory information from a relay that has a wrong clock.
6210 Instead, only inform the controller when it's a trusted authority
6211 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
6212 the rest of bug 1074.
6213 - Fix a bounds-checking error that could allow an attacker to
6214 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
6216 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
6217 Tor would ignore their RelayBandwidthBurst setting,
6218 potentially using more bandwidth than expected. Bugfix on
6219 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
6220 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
6221 hidserv" in her torrc. The 'hidserv' argument never controlled
6222 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
6225 - Adjust our TLS Diffie-Hellman parameters to match those used by
6227 - Update to the February 1 2011 Maxmind GeoLite Country database.
6230 - Check for and reject overly long directory certificates and
6231 directory tokens before they have a chance to hit any assertions.
6232 Bugfix on 0.2.1.28. Found by "doorss".
6233 - Bring the logic that gathers routerinfos and assesses the
6234 acceptability of circuits into line. This prevents a Tor OP from
6235 getting locked in a cycle of choosing its local OR as an exit for a
6236 path (due to a .exit request) and then rejecting the circuit because
6237 its OR is not listed yet. It also prevents Tor clients from using an
6238 OR running in the same instance as an exit (due to a .exit request)
6239 if the OR does not meet the same requirements expected of an OR
6240 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
6242 o Packaging changes:
6243 - Stop shipping the Tor specs files and development proposal documents
6244 in the tarball. They are now in a separate git repository at
6245 git://git.torproject.org/torspec.git
6246 - Do not include Git version tags as though they are SVN tags when
6247 generating a tarball from inside a repository that has switched
6248 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
6251 Changes in version 0.2.2.22-alpha - 2011-01-25
6252 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
6253 main other change is a slight tweak to Tor's TLS handshake that makes
6254 relays and bridges that run this new version reachable from Iran again.
6255 We don't expect this tweak will win the arms race long-term, but it
6256 will buy us a bit more time until we roll out a better solution.
6259 - Fix a bounds-checking error that could allow an attacker to
6260 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
6262 - Don't assert when changing from bridge to relay or vice versa
6263 via the controller. The assert happened because we didn't properly
6264 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
6265 bug 2433. Reported by bastik.
6268 - Adjust our TLS Diffie-Hellman parameters to match those used by
6270 - Provide a log message stating which geoip file we're parsing
6271 instead of just stating that we're parsing the geoip file.
6272 Implements ticket 2432.
6275 - Check for and reject overly long directory certificates and
6276 directory tokens before they have a chance to hit any assertions.
6277 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
6280 Changes in version 0.2.2.21-alpha - 2011-01-15
6281 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
6282 continues our recent code security audit work. The main fix resolves
6283 a remote heap overflow vulnerability that can allow remote code
6284 execution (CVE-2011-0427). Other fixes address a variety of assert
6285 and crash bugs, most of which we think are hard to exploit remotely.
6287 o Major bugfixes (security), also included in 0.2.1.29:
6288 - Fix a heap overflow bug where an adversary could cause heap
6289 corruption. This bug probably allows remote code execution
6290 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
6292 - Prevent a denial-of-service attack by disallowing any
6293 zlib-compressed data whose compression factor is implausibly
6294 high. Fixes part of bug 2324; reported by "doorss".
6295 - Zero out a few more keys in memory before freeing them. Fixes
6296 bug 2384 and part of bug 2385. These key instances found by
6297 "cypherpunks", based on Andrew Case's report about being able
6298 to find sensitive data in Tor's memory space if you have enough
6299 permissions. Bugfix on 0.0.2pre9.
6301 o Major bugfixes (crashes), also included in 0.2.1.29:
6302 - Prevent calls to Libevent from inside Libevent log handlers.
6303 This had potential to cause a nasty set of crashes, especially
6304 if running Libevent with debug logging enabled, and running
6305 Tor with a controller watching for low-severity log messages.
6306 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
6307 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
6308 underflow errors there too. Fixes the other part of bug 2324.
6309 - Fix a bug where we would assert if we ever had a
6310 cached-descriptors.new file (or another file read directly into
6311 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
6312 on 0.2.1.25. Found by doorss.
6313 - Fix some potential asserts and parsing issues with grossly
6314 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
6317 o Minor bugfixes (other), also included in 0.2.1.29:
6318 - Fix a bug with handling misformed replies to reverse DNS lookup
6319 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
6320 bug reported by doorss.
6321 - Fix compilation on mingw when a pthreads compatibility library
6322 has been installed. (We don't want to use it, so we shouldn't
6323 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
6324 - Fix a bug where we would declare that we had run out of virtual
6325 addresses when the address space was only half-exhausted. Bugfix
6327 - Correctly handle the case where AutomapHostsOnResolve is set but
6328 no virtual addresses are available. Fixes bug 2328; bugfix on
6329 0.1.2.1-alpha. Bug found by doorss.
6330 - Correctly handle wrapping around when we run out of virtual
6331 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
6333 o Minor features, also included in 0.2.1.29:
6334 - Update to the January 1 2011 Maxmind GeoLite Country database.
6335 - Introduce output size checks on all of our decryption functions.
6337 o Build changes, also included in 0.2.1.29:
6338 - Tor does not build packages correctly with Automake 1.6 and earlier;
6339 added a check to Makefile.am to make sure that we're building with
6340 Automake 1.7 or later.
6341 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
6342 because we built it with a too-old version of automake. Thus that
6343 release broke ./configure --enable-openbsd-malloc, which is popular
6344 among really fast exit relays on Linux.
6346 o Major bugfixes, new in 0.2.2.21-alpha:
6347 - Prevent crash/heap corruption when the cbtnummodes consensus
6348 parameter is set to 0 or large values. Fixes bug 2317; bugfix
6351 o Major features, new in 0.2.2.21-alpha:
6352 - Introduce minimum/maximum values that clients will believe
6353 from the consensus. Now we'll have a better chance to avoid crashes
6354 or worse when a consensus param has a weird value.
6356 o Minor features, new in 0.2.2.21-alpha:
6357 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
6358 used on bridges, and it makes bridge scanning somewhat easier.
6359 - If writing the state file to disk fails, wait up to an hour before
6360 retrying again, rather than trying again each second. Fixes bug
6361 2346; bugfix on Tor 0.1.1.3-alpha.
6362 - Make Libevent log messages get delivered to controllers later,
6363 and not from inside the Libevent log handler. This prevents unsafe
6364 reentrant Libevent calls while still letting the log messages
6366 - Detect platforms that brokenly use a signed size_t, and refuse to
6367 build there. Found and analyzed by doorss and rransom.
6368 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
6371 o Minor bugfixes, new in 0.2.2.21-alpha:
6372 - Handle SOCKS messages longer than 128 bytes long correctly, rather
6373 than waiting forever for them to finish. Fixes bug 2330; bugfix
6374 on 0.2.0.16-alpha. Found by doorss.
6375 - Add assertions to check for overflow in arguments to
6376 base32_encode() and base32_decode(); fix a signed-unsigned
6377 comparison there too. These bugs are not actually reachable in Tor,
6378 but it's good to prevent future errors too. Found by doorss.
6379 - Correctly detect failures to create DNS requests when using Libevent
6380 versions before v2. (Before Libevent 2, we used our own evdns
6381 implementation. Its return values for Libevent's evdns_resolve_*()
6382 functions are not consistent with those from Libevent.) Fixes bug
6383 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
6385 o Documentation, new in 0.2.2.21-alpha:
6386 - Document the default socks host and port (127.0.0.1:9050) for
6390 Changes in version 0.2.1.29 - 2011-01-15
6391 Tor 0.2.1.29 continues our recent code security audit work. The main
6392 fix resolves a remote heap overflow vulnerability that can allow remote
6393 code execution. Other fixes address a variety of assert and crash bugs,
6394 most of which we think are hard to exploit remotely.
6396 o Major bugfixes (security):
6397 - Fix a heap overflow bug where an adversary could cause heap
6398 corruption. This bug probably allows remote code execution
6399 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
6401 - Prevent a denial-of-service attack by disallowing any
6402 zlib-compressed data whose compression factor is implausibly
6403 high. Fixes part of bug 2324; reported by "doorss".
6404 - Zero out a few more keys in memory before freeing them. Fixes
6405 bug 2384 and part of bug 2385. These key instances found by
6406 "cypherpunks", based on Andrew Case's report about being able
6407 to find sensitive data in Tor's memory space if you have enough
6408 permissions. Bugfix on 0.0.2pre9.
6410 o Major bugfixes (crashes):
6411 - Prevent calls to Libevent from inside Libevent log handlers.
6412 This had potential to cause a nasty set of crashes, especially
6413 if running Libevent with debug logging enabled, and running
6414 Tor with a controller watching for low-severity log messages.
6415 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
6416 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
6417 underflow errors there too. Fixes the other part of bug 2324.
6418 - Fix a bug where we would assert if we ever had a
6419 cached-descriptors.new file (or another file read directly into
6420 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
6421 on 0.2.1.25. Found by doorss.
6422 - Fix some potential asserts and parsing issues with grossly
6423 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
6426 o Minor bugfixes (other):
6427 - Fix a bug with handling misformed replies to reverse DNS lookup
6428 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
6429 bug reported by doorss.
6430 - Fix compilation on mingw when a pthreads compatibility library
6431 has been installed. (We don't want to use it, so we shouldn't
6432 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
6433 - Fix a bug where we would declare that we had run out of virtual
6434 addresses when the address space was only half-exhausted. Bugfix
6436 - Correctly handle the case where AutomapHostsOnResolve is set but
6437 no virtual addresses are available. Fixes bug 2328; bugfix on
6438 0.1.2.1-alpha. Bug found by doorss.
6439 - Correctly handle wrapping around to when we run out of virtual
6440 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
6441 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
6442 because we built it with a too-old version of automake. Thus that
6443 release broke ./configure --enable-openbsd-malloc, which is popular
6444 among really fast exit relays on Linux.
6447 - Update to the January 1 2011 Maxmind GeoLite Country database.
6448 - Introduce output size checks on all of our decryption functions.
6451 - Tor does not build packages correctly with Automake 1.6 and earlier;
6452 added a check to Makefile.am to make sure that we're building with
6453 Automake 1.7 or later.
6456 Changes in version 0.2.2.20-alpha - 2010-12-17
6457 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
6458 exploitable bugs. We also fix a variety of other significant bugs,
6459 change the IP address for one of our directory authorities, and update
6460 the minimum version that Tor relays must run to join the network.
6463 - Fix a remotely exploitable bug that could be used to crash instances
6464 of Tor remotely by overflowing on the heap. Remote-code execution
6465 hasn't been confirmed, but can't be ruled out. Everyone should
6466 upgrade. Bugfix on the 0.1.1 series and later.
6467 - Fix a bug that could break accounting on 64-bit systems with large
6468 time_t values, making them hibernate for impossibly long intervals.
6469 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
6470 - Fix a logic error in directory_fetches_from_authorities() that
6471 would cause all _non_-exits refusing single-hop-like circuits
6472 to fetch from authorities, when we wanted to have _exits_ fetch
6473 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
6475 - Fix a stream fairness bug that would cause newer streams on a given
6476 circuit to get preference when reading bytes from the origin or
6477 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
6478 introduced before the first Tor release, in svn revision r152.
6480 o Directory authority changes:
6481 - Change IP address and ports for gabelmoo (v3 directory authority).
6484 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
6485 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
6486 - Fix an off-by-one error in calculating some controller command
6487 argument lengths. Fortunately, this mistake is harmless since
6488 the controller code does redundant NUL termination too. Found by
6489 boboper. Bugfix on 0.1.1.1-alpha.
6490 - Do not dereference NULL if a bridge fails to build its
6491 extra-info descriptor. Found by an anonymous commenter on
6492 Trac. Bugfix on 0.2.2.19-alpha.
6495 - Update to the December 1 2010 Maxmind GeoLite Country database.
6496 - Directory authorities now reject relays running any versions of
6497 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
6498 known bugs that keep RELAY_EARLY cells from working on rendezvous
6499 circuits. Followup to fix for bug 2081.
6500 - Directory authorities now reject relays running any version of Tor
6501 older than 0.2.0.26-rc. That version is the earliest that fetches
6502 current directory information correctly. Fixes bug 2156.
6503 - Report only the top 10 ports in exit-port stats in order not to
6504 exceed the maximum extra-info descriptor length of 50 KB. Implements
6508 Changes in version 0.2.1.28 - 2010-12-17
6509 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
6510 exploitable bugs. We also took this opportunity to change the IP address
6511 for one of our directory authorities, and to update the geoip database
6515 - Fix a remotely exploitable bug that could be used to crash instances
6516 of Tor remotely by overflowing on the heap. Remote-code execution
6517 hasn't been confirmed, but can't be ruled out. Everyone should
6518 upgrade. Bugfix on the 0.1.1 series and later.
6520 o Directory authority changes:
6521 - Change IP address and ports for gabelmoo (v3 directory authority).
6524 - Update to the December 1 2010 Maxmind GeoLite Country database.
6527 Changes in version 0.2.1.27 - 2010-11-23
6528 Yet another OpenSSL security patch broke its compatibility with Tor:
6529 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
6530 also took this opportunity to fix several crash bugs, integrate a new
6531 directory authority, and update the bundled GeoIP database.
6534 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
6535 No longer set the tlsext_host_name extension on server SSL objects;
6536 but continue to set it on client SSL objects. Our goal in setting
6537 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
6538 bugfix on 0.2.1.1-alpha.
6539 - Do not log messages to the controller while shrinking buffer
6540 freelists. Doing so would sometimes make the controller connection
6541 try to allocate a buffer chunk, which would mess up the internals
6542 of the freelist and cause an assertion failure. Fixes bug 1125;
6543 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
6544 - Learn our external IP address when we're a relay or bridge, even if
6545 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
6546 where we introduced bridge relays that don't need to publish to
6547 be useful. Fixes bug 2050.
6548 - Do even more to reject (and not just ignore) annotations on
6549 router descriptors received anywhere but from the cache. Previously
6550 we would ignore such annotations at first, but cache them to disk
6551 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
6552 - When you're using bridges and your network goes away and your
6553 bridges get marked as down, recover when you attempt a new socks
6554 connection (if the network is back), rather than waiting up to an
6555 hour to try fetching new descriptors for your bridges. Bugfix on
6556 0.2.0.3-alpha; fixes bug 1981.
6559 - Move to the November 2010 Maxmind GeoLite country db (rather
6560 than the June 2009 ip-to-country GeoIP db) for our statistics that
6561 count how many users relays are seeing from each country. Now we'll
6562 have more accurate data, especially for many African countries.
6564 o New directory authorities:
6565 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6569 - Fix an assertion failure that could occur in directory caches or
6570 bridge users when using a very short voting interval on a testing
6571 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
6573 - Enforce multiplicity rules when parsing annotations. Bugfix on
6574 0.2.0.8-alpha. Found by piebeer.
6575 - Allow handshaking OR connections to take a full KeepalivePeriod
6576 seconds to handshake. Previously, we would close them after
6577 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6578 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6580 - When building with --enable-gcc-warnings on OpenBSD, disable
6581 warnings in system headers. This makes --enable-gcc-warnings
6582 pass on OpenBSD 4.8.
6585 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6586 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6587 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6588 Servers can start sending this code when enough clients recognize
6589 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
6590 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6591 Patch from mingw-san.
6594 - Remove the old debian/ directory from the main Tor distribution.
6595 The official Tor-for-debian git repository lives at the URL
6596 https://git.torproject.org/debian/tor.git
6597 - Stop shipping the old doc/website/ directory in the tarball. We
6598 changed the website format in late 2010, and what we shipped in
6599 0.2.1.26 really wasn't that useful anyway.
6602 Changes in version 0.2.2.19-alpha - 2010-11-22
6603 Yet another OpenSSL security patch broke its compatibility with Tor:
6604 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
6607 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
6608 No longer set the tlsext_host_name extension on server SSL objects;
6609 but continue to set it on client SSL objects. Our goal in setting
6610 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
6611 bugfix on 0.2.1.1-alpha.
6614 - Try harder not to exceed the maximum length of 50 KB when writing
6615 statistics to extra-info descriptors. This bug was triggered by very
6616 fast relays reporting exit-port, entry, and dirreq statistics.
6617 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
6618 - Publish a router descriptor even if generating an extra-info
6619 descriptor fails. Previously we would not publish a router
6620 descriptor without an extra-info descriptor; this can cause fast
6621 exit relays collecting exit-port statistics to drop from the
6622 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
6625 Changes in version 0.2.2.18-alpha - 2010-11-16
6626 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
6627 us lately, makes unpublished bridge relays able to detect their IP
6628 address, and fixes a wide variety of other bugs to get us much closer
6629 to a stable release.
6632 - Do even more to reject (and not just ignore) annotations on
6633 router descriptors received anywhere but from the cache. Previously
6634 we would ignore such annotations at first, but cache them to disk
6635 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
6636 - Do not log messages to the controller while shrinking buffer
6637 freelists. Doing so would sometimes make the controller connection
6638 try to allocate a buffer chunk, which would mess up the internals
6639 of the freelist and cause an assertion failure. Fixes bug 1125;
6640 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
6641 - Learn our external IP address when we're a relay or bridge, even if
6642 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
6643 where we introduced bridge relays that don't need to publish to
6644 be useful. Fixes bug 2050.
6645 - Maintain separate TLS contexts and certificates for incoming and
6646 outgoing connections in bridge relays. Previously we would use the
6647 same TLS contexts and certs for incoming and outgoing connections.
6648 Bugfix on 0.2.0.3-alpha; addresses bug 988.
6649 - Maintain separate identity keys for incoming and outgoing TLS
6650 contexts in bridge relays. Previously we would use the same
6651 identity keys for incoming and outgoing TLS contexts. Bugfix on
6652 0.2.0.3-alpha; addresses the other half of bug 988.
6653 - Avoid an assertion failure when we as an authority receive a
6654 duplicate upload of a router descriptor that we already have,
6655 but which we previously considered an obsolete descriptor.
6656 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
6657 - Avoid a crash bug triggered by looking at a dangling pointer while
6658 setting the network status consensus. Found by Robert Ransom.
6659 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
6660 - Fix a logic error where servers that _didn't_ act as exits would
6661 try to keep their server lists more aggressively up to date than
6662 exits, when it was supposed to be the other way around. Bugfix
6665 o Minor bugfixes (on Tor 0.2.1.x and earlier):
6666 - When we're trying to guess whether we know our IP address as
6667 a relay, we would log various ways that we failed to guess
6668 our address, but never log that we ended up guessing it
6669 successfully. Now add a log line to help confused and anxious
6670 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
6671 - Bring the logic that gathers routerinfos and assesses the
6672 acceptability of circuits into line. This prevents a Tor OP from
6673 getting locked in a cycle of choosing its local OR as an exit for a
6674 path (due to a .exit request) and then rejecting the circuit because
6675 its OR is not listed yet. It also prevents Tor clients from using an
6676 OR running in the same instance as an exit (due to a .exit request)
6677 if the OR does not meet the same requirements expected of an OR
6678 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
6679 - Correctly describe errors that occur when generating a TLS object.
6680 Previously we would attribute them to a failure while generating a
6681 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
6683 - Enforce multiplicity rules when parsing annotations. Bugfix on
6684 0.2.0.8-alpha. Found by piebeer.
6685 - Fix warnings that newer versions of autoconf produced during
6686 ./autogen.sh. These warnings appear to be harmless in our case,
6687 but they were extremely verbose. Fixes bug 2020.
6689 o Minor bugfixes (on Tor 0.2.2.x):
6690 - Enable protection of small arrays whenever we build with gcc
6691 hardening features, not only when also building with warnings
6692 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
6695 - Make hidden services work better in private Tor networks by not
6696 requiring any uptime to join the hidden service descriptor
6697 DHT. Implements ticket 2088.
6698 - Rate-limit the "your application is giving Tor only an IP address"
6699 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
6700 - When AllowSingleHopExits is set, print a warning to explain to the
6701 relay operator why most clients are avoiding her relay.
6702 - Update to the November 1 2010 Maxmind GeoLite Country database.
6704 o Code simplifications and refactoring:
6705 - When we fixed bug 1038 we had to put in a restriction not to send
6706 RELAY_EARLY cells on rend circuits. This was necessary as long
6707 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
6708 active. Now remove this obsolete check. Resolves bug 2081.
6709 - Some options used different conventions for uppercasing of acronyms
6710 when comparing manpage and source. Fix those in favor of the
6711 manpage, as it makes sense to capitalize acronyms.
6712 - Remove the torrc.complete file. It hasn't been kept up to date
6713 and users will have better luck checking out the manpage.
6714 - Remove the obsolete "NoPublish" option; it has been flagged
6715 as obsolete and has produced a warning since 0.1.1.18-rc.
6716 - Remove everything related to building the expert bundle for OS X.
6717 It has confused many users, doesn't work right on OS X 10.6,
6718 and is hard to get rid of once installed. Resolves bug 1274.
6721 Changes in version 0.2.2.17-alpha - 2010-09-30
6722 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
6723 to use one-hop circuits (which can put the exit relays at higher risk,
6724 plus unbalance the network); fixes a big bug in bandwidth accounting
6725 for relays that want to limit their monthly bandwidth use; fixes a
6726 big pile of bugs in how clients tolerate temporary network failure;
6727 and makes our adaptive circuit build timeout feature (which improves
6728 client performance if your network is fast while not breaking things
6729 if your network is slow) better handle bad networks.
6732 - Exit relays now try harder to block exit attempts from unknown
6733 relays, to make it harder for people to use them as one-hop proxies
6734 a la tortunnel. Controlled by the refuseunknownexits consensus
6735 parameter (currently enabled), or you can override it on your
6736 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
6738 o Major bugfixes (0.2.1.x and earlier):
6739 - Fix a bug in bandwidth accounting that could make us use twice
6740 the intended bandwidth when our interval start changes due to
6741 daylight saving time. Now we tolerate skew in stored vs computed
6742 interval starts: if the start of the period changes by no more than
6743 50% of the period's duration, we remember bytes that we transferred
6744 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
6745 - Always search the Windows system directory for system DLLs, and
6746 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
6747 - When you're using bridges and your network goes away and your
6748 bridges get marked as down, recover when you attempt a new socks
6749 connection (if the network is back), rather than waiting up to an
6750 hour to try fetching new descriptors for your bridges. Bugfix on
6751 0.2.0.3-alpha; fixes bug 1981.
6753 o Major bugfixes (on 0.2.2.x):
6754 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
6756 - Fix a segfault that could happen when operating a bridge relay with
6757 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
6758 - The consensus bandwidth-weights (used by clients to choose fast
6759 relays) entered an unexpected edge case in September where
6760 Exits were much scarcer than Guards, resulting in bad weight
6761 recommendations. Now we compute them using new constraints that
6762 should succeed in all cases. Also alter directory authorities to
6763 not include the bandwidth-weights line if they fail to produce
6764 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
6765 - When weighting bridges during path selection, we used to trust
6766 the bandwidths they provided in their descriptor, only capping them
6767 at 10MB/s. This turned out to be problematic for two reasons:
6768 Bridges could claim to handle a lot more traffic then they
6769 actually would, thus making more clients pick them and have a
6770 pretty effective DoS attack. The other issue is that new bridges
6771 that might not have a good estimate for their bw capacity yet
6772 would not get used at all unless no other bridges are available
6773 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
6775 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
6776 - Ignore cannibalized circuits when recording circuit build times.
6777 This should provide for a minor performance improvement for hidden
6778 service users using 0.2.2.14-alpha, and should remove two spurious
6779 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
6780 - Simplify the logic that causes us to decide if the network is
6781 unavailable for purposes of recording circuit build times. If we
6782 receive no cells whatsoever for the entire duration of a circuit's
6783 full measured lifetime, the network is probably down. Also ignore
6784 one-hop directory fetching circuit timeouts when calculating our
6785 circuit build times. These changes should hopefully reduce the
6786 cases where we see ridiculous circuit build timeouts for people
6787 with spotty wireless connections. Fixes part of bug 1772; bugfix
6789 - Prevent the circuit build timeout from becoming larger than
6790 the maximum build time we have ever seen. Also, prevent the time
6791 period for measurement circuits from becoming larger than twice that
6792 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
6795 - When we run out of directory information such that we can't build
6796 circuits, but then get enough that we can build circuits, log when
6797 we actually construct a circuit, so the user has a better chance of
6798 knowing what's going on. Fixes bug 1362.
6799 - Be more generous with how much bandwidth we'd use up (with
6800 accounting enabled) before entering "soft hibernation". Previously,
6801 we'd refuse new connections and circuits once we'd used up 95% of
6802 our allotment. Now, we use up 95% of our allotment, AND make sure
6803 that we have no more than 500MB (or 3 hours of expected traffic,
6804 whichever is lower) remaining before we enter soft hibernation.
6805 - If we've configured EntryNodes and our network goes away and/or all
6806 our entrynodes get marked down, optimistically retry them all when
6807 a new socks application request appears. Fixes bug 1882.
6808 - Add some more defensive programming for architectures that can't
6809 handle unaligned integer accesses. We don't know of any actual bugs
6810 right now, but that's the best time to fix them. Fixes bug 1943.
6811 - Support line continuations in the torrc config file. If a line
6812 ends with a single backslash character, the newline is ignored, and
6813 the configuration value is treated as continuing on the next line.
6816 o Minor bugfixes (on 0.2.1.x and earlier):
6817 - For bandwidth accounting, calculate our expected bandwidth rate
6818 based on the time during which we were active and not in
6819 soft-hibernation during the last interval. Previously, we were
6820 also considering the time spent in soft-hibernation. If this
6821 was a long time, we would wind up underestimating our bandwidth
6822 by a lot, and skewing our wakeup time towards the start of the
6823 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
6825 o Minor bugfixes (on 0.2.2.x):
6826 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
6827 which were disabled by the circuit build timeout changes in
6828 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
6829 - Make sure we don't warn about missing bandwidth weights when
6830 choosing bridges or other relays not in the consensus. Bugfix on
6831 0.2.2.10-alpha; fixes bug 1805.
6832 - In our logs, do not double-report signatures from unrecognized
6833 authorities both as "from unknown authority" and "not
6834 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
6837 Changes in version 0.2.2.16-alpha - 2010-09-17
6838 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
6839 evident at exit relays), and also continues to resolve all the little
6840 bugs that have been filling up trac lately.
6842 o Major bugfixes (stream-level fairness):
6843 - When receiving a circuit-level SENDME for a blocked circuit, try
6844 to package cells fairly from all the streams that had previously
6845 been blocked on that circuit. Previously, we had started with the
6846 oldest stream, and allowed each stream to potentially exhaust
6847 the circuit's package window. This gave older streams on any
6848 given circuit priority over newer ones. Fixes bug 1937. Detected
6849 originally by Camilo Viecco. This bug was introduced before the
6850 first Tor release, in svn commit r152: it is the new winner of
6851 the longest-lived bug prize.
6852 - When the exit relay got a circuit-level sendme cell, it started
6853 reading on the exit streams, even if had 500 cells queued in the
6854 circuit queue already, so the circuit queue just grew and grew in
6855 some cases. We fix this by not re-enabling reading on receipt of a
6856 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
6857 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
6859 - Newly created streams were allowed to read cells onto circuits,
6860 even if the circuit's cell queue was blocked and waiting to drain.
6861 This created potential unfairness, as older streams would be
6862 blocked, but newer streams would gladly fill the queue completely.
6863 We add code to detect this situation and prevent any stream from
6864 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
6868 - Update to the September 1 2010 Maxmind GeoLite Country database.
6869 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
6870 not. This would lead to a cookie that is still not group readable.
6871 Closes bug 1843. Suggested by katmagic.
6872 - When logging a rate-limited warning, we now mention how many messages
6873 got suppressed since the last warning.
6874 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
6875 do individual connection-level rate limiting of clients. The torrc
6876 config options with the same names trump the consensus params, if
6877 both are present. Replaces the old "bwconnrate" and "bwconnburst"
6878 consensus params which were broken from 0.2.2.7-alpha through
6879 0.2.2.14-alpha. Closes bug 1947.
6880 - When a router changes IP address or port, authorities now launch
6881 a new reachability test for it. Implements ticket 1899.
6882 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
6883 2 no signature, 4 required" messages about consensus signatures
6884 easier to read, and make sure they get logged at the same severity
6885 as the messages explaining which keys are which. Fixes bug 1290.
6886 - Don't warn when we have a consensus that we can't verify because
6887 of missing certificates, unless those certificates are ones
6888 that we have been trying and failing to download. Fixes bug 1145.
6889 - If you configure your bridge with a known identity fingerprint,
6890 and the bridge authority is unreachable (as it is in at least
6891 one country now), fall back to directly requesting the descriptor
6892 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
6894 - When building with --enable-gcc-warnings on OpenBSD, disable
6895 warnings in system headers. This makes --enable-gcc-warnings
6896 pass on OpenBSD 4.8.
6898 o Minor bugfixes (on 0.2.1.x and earlier):
6899 - Authorities will now attempt to download consensuses if their
6900 own efforts to make a live consensus have failed. This change
6901 means authorities that restart will fetch a valid consensus, and
6902 it means authorities that didn't agree with the current consensus
6903 will still fetch and serve it if it has enough signatures. Bugfix
6904 on 0.2.0.9-alpha; fixes bug 1300.
6905 - Ensure DNS requests launched by "RESOLVE" commands from the
6906 controller respect the __LeaveStreamsUnattached setconf options. The
6907 same goes for requests launched via DNSPort or transparent
6908 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
6909 - Allow handshaking OR connections to take a full KeepalivePeriod
6910 seconds to handshake. Previously, we would close them after
6911 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6912 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6914 - Rate-limit "Failed to hand off onionskin" warnings.
6915 - Never relay a cell for a circuit we have already destroyed.
6916 Between marking a circuit as closeable and finally closing it,
6917 it may have been possible for a few queued cells to get relayed,
6918 even though they would have been immediately dropped by the next
6919 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6920 - Never queue a cell for a circuit that's already been marked
6922 - Never vote for a server as "Running" if we have a descriptor for
6923 it claiming to be hibernating, and that descriptor was published
6924 more recently than our last contact with the server. Bugfix on
6925 0.2.0.3-alpha; fixes bug 911.
6926 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6929 o Minor bugfixes (on 0.2.2.x):
6930 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
6931 down if a directory fetch fails and you've configured either
6932 bridges or EntryNodes. The intent was to mark the relay as down
6933 _unless_ you're using bridges or EntryNodes, since if you are
6934 then you could quickly run out of entry points.
6935 - Fix the Windows directory-listing code. A bug introduced in
6936 0.2.2.14-alpha could make Windows directory servers forget to load
6937 some of their cached v2 networkstatus files.
6938 - Really allow clients to use relays as bridges. Fixes bug 1776;
6939 bugfix on 0.2.2.15-alpha.
6940 - Demote a warn to info that happens when the CellStatistics option
6941 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
6942 Reported by Moritz Bartl.
6943 - On Windows, build correctly either with or without Unicode support.
6944 This is necessary so that Tor can support fringe platforms like
6945 Windows 98 (which has no Unicode), or Windows CE (which has no
6946 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
6949 - Add a unit test for cross-platform directory-listing code.
6952 Changes in version 0.2.2.15-alpha - 2010-08-18
6953 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
6954 fixes a variety of other bugs that were preventing performance
6955 experiments from moving forward, fixes several bothersome memory leaks,
6956 and generally closes a lot of smaller bugs that have been filling up
6960 - Stop assigning the HSDir flag to relays that disable their
6961 DirPort (and thus will refuse to answer directory requests). This
6962 fix should dramatically improve the reachability of hidden services:
6963 hidden services and hidden service clients pick six HSDir relays
6964 to store and retrieve the hidden service descriptor, and currently
6965 about half of the HSDir relays will refuse to work. Bugfix on
6966 0.2.0.10-alpha; fixes part of bug 1693.
6967 - The PerConnBWRate and Burst config options, along with the
6968 bwconnrate and bwconnburst consensus params, initialized each conn's
6969 token bucket values only when the connection is established. Now we
6970 update them if the config options change, and update them every time
6971 we get a new consensus. Otherwise we can encounter an ugly edge
6972 case where we initialize an OR conn to client-level bandwidth,
6973 but then later the relay joins the consensus and we leave it
6974 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
6975 - Fix a regression that caused Tor to rebind its ports if it receives
6976 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6979 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6980 should give us approximately 40-50% more Guard-flagged nodes,
6981 improving the anonymity the Tor network can provide and also
6982 decreasing the dropoff in throughput that relays experience when
6983 they first get the Guard flag.
6984 - Allow enabling or disabling the *Statistics config options while
6988 - Update to the August 1 2010 Maxmind GeoLite Country database.
6989 - Have the controller interface give a more useful message than
6990 "Internal Error" in response to failed GETINFO requests.
6991 - Warn when the same option is provided more than once in a torrc
6992 file, on the command line, or in a single SETCONF statement, and
6993 the option is one that only accepts a single line. Closes bug 1384.
6994 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6995 Patch from mingw-san.
6996 - Add support for the country code "{??}" in torrc options like
6997 ExcludeNodes, to indicate all routers of unknown country. Closes
6999 - Relays report the number of bytes spent on answering directory
7000 requests in extra-info descriptors similar to {read,write}-history.
7001 Implements enhancement 1790.
7003 o Minor bugfixes (on 0.2.1.x and earlier):
7004 - Complain if PublishServerDescriptor is given multiple arguments that
7005 include 0 or 1. This configuration will be rejected in the future.
7006 Bugfix on 0.2.0.1-alpha; closes bug 1107.
7007 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
7008 Bugfix on 0.2.0.13-alpha; closes bug 928.
7009 - Change "Application request when we're believed to be offline."
7010 notice to "Application request when we haven't used client
7011 functionality lately.", to clarify that it's not an error. Bugfix
7012 on 0.0.9.3; fixes bug 1222.
7013 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
7014 would return "551 Internal error" rather than "552 Unrecognized key
7015 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
7016 - Users can't configure a regular relay to be their bridge. It didn't
7017 work because when Tor fetched the bridge descriptor, it found
7018 that it already had it, and didn't realize that the purpose of the
7019 descriptor had changed. Now we replace routers with a purpose other
7020 than bridge with bridge descriptors when fetching them. Bugfix on
7021 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
7022 refetch the descriptor with router purpose 'general', disabling
7024 - Fix a rare bug in rend_fn unit tests: we would fail a test when
7025 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
7026 on 0.2.0.10-alpha; fixes bug 1808.
7027 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
7028 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
7029 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
7030 Servers can start sending this code when enough clients recognize
7031 it. Also update the spec to reflect this new reason. Bugfix on
7032 0.1.0.1-rc; fixes part of bug 1793.
7033 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
7034 when we switch from being a public relay to a bridge. Otherwise
7035 there will still be clients that see the relay in their consensus,
7036 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
7038 - Instead of giving an assertion failure on an internal mismatch
7039 on estimated freelist size, just log a BUG warning and try later.
7040 Mitigates but does not fix bug 1125.
7041 - Fix an assertion failure that could occur in caches or bridge users
7042 when using a very short voting interval on a testing network.
7043 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
7045 o Minor bugfixes (on 0.2.2.x):
7046 - Alter directory authorities to always consider Exit-flagged nodes
7047 as potential Guard nodes in their votes. The actual decision to
7048 use Exits as Guards is done in the consensus bandwidth weights.
7049 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
7050 - When the controller is reporting the purpose of circuits that
7051 didn't finish building before the circuit build timeout, it was
7052 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
7053 - Our libevent version parsing code couldn't handle versions like
7054 1.4.14b-stable and incorrectly warned the user about using an
7055 old and broken version of libevent. Treat 1.4.14b-stable like
7056 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
7058 - Don't use substitution references like $(VAR:MOD) when
7059 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
7060 '$(:x)' to 'x' rather than the empty string. This bites us in
7061 doc/ when configured with --disable-asciidoc. Bugfix on
7062 0.2.2.9-alpha; fixes bug 1773.
7063 - Remove a spurious hidden service server-side log notice about
7064 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
7066 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
7068 - Correctly report written bytes on linked connections. Found while
7069 implementing 1790. Bugfix on 0.2.2.4-alpha.
7070 - Fix three memory leaks: one in circuit_build_times_parse_state(),
7071 one in dirvote_add_signatures_to_pending_consensus(), and one every
7072 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
7073 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
7075 o Code simplifications and refactoring:
7076 - Take a first step towards making or.h smaller by splitting out
7077 function definitions for all source files in src/or/. Leave
7078 structures and defines in or.h for now.
7079 - Remove a bunch of unused function declarations as well as a block of
7080 #if 0'd code from the unit tests. Closes bug 1824.
7081 - New unit tests for exit-port history statistics; refactored exit
7082 statistics code to be more easily tested.
7083 - Remove the old debian/ directory from the main Tor distribution.
7084 The official Tor-for-debian git repository lives at the URL
7085 https://git.torproject.org/debian/tor.git
7088 Changes in version 0.2.2.14-alpha - 2010-07-12
7089 Tor 0.2.2.14-alpha greatly improves client-side handling of
7090 circuit build timeouts, which are used to estimate speed and improve
7091 performance. We also move to a much better GeoIP database, port Tor to
7092 Windows CE, introduce new compile flags that improve code security,
7093 add an eighth v3 directory authority, and address a lot of more
7097 - Tor directory authorities no longer crash when started with a
7098 cached-microdesc-consensus file in their data directory. Bugfix
7099 on 0.2.2.6-alpha; fixes bug 1532.
7100 - Treat an unset $HOME like an empty $HOME rather than triggering an
7101 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
7102 - Ignore negative and large circuit build timeout values that can
7103 happen during a suspend or hibernate. These values caused various
7104 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
7105 - Alter calculation of Pareto distribution parameter 'Xm' for
7106 Circuit Build Timeout learning to use the weighted average of the
7107 top N=3 modes (because we have three entry guards). Considering
7108 multiple modes should improve the timeout calculation in some cases,
7109 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
7111 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
7112 right censored distribution model. This approach improves over the
7113 synthetic timeout generation approach that was producing insanely
7114 high timeout values. Now we calculate build timeouts using truncated
7115 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
7116 - Do not close circuits that are under construction when they reach
7117 the circuit build timeout. Instead, leave them building (but do not
7118 use them) for up until the time corresponding to the 95th percentile
7119 on the Pareto CDF or 60 seconds, whichever is greater. This is done
7120 to provide better data for the new Pareto model. This percentile
7121 can be controlled by the consensus.
7124 - Move to the June 2010 Maxmind GeoLite country db (rather than the
7125 June 2009 ip-to-country GeoIP db) for our statistics that count
7126 how many users relays are seeing from each country. Now we have
7127 more accurate data for many African countries.
7128 - Port Tor to build and run correctly on Windows CE systems, using
7129 the wcecompat library. Contributed by Valerio Lupi.
7130 - New "--enable-gcc-hardening" ./configure flag (off by default)
7131 to turn on gcc compile time hardening options. It ensures
7132 that signed ints have defined behavior (-fwrapv), enables
7133 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
7134 with canaries (-fstack-protector-all), turns on ASLR protection if
7135 supported by the kernel (-fPIE, -pie), and adds additional security
7136 related warnings. Verified to work on Mac OS X and Debian Lenny.
7137 - New "--enable-linker-hardening" ./configure flag (off by default)
7138 to turn on ELF specific hardening features (relro, now). This does
7139 not work with Mac OS X or any other non-ELF binary format.
7141 o New directory authorities:
7142 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
7146 - New config option "WarnUnsafeSocks 0" disables the warning that
7147 occurs whenever Tor receives a socks handshake using a version of
7148 the socks protocol that can only provide an IP address (rather
7149 than a hostname). Setups that do DNS locally over Tor are fine,
7150 and we shouldn't spam the logs in that case.
7151 - Convert the HACKING file to asciidoc, and add a few new sections
7152 to it, explaining how we use Git, how we make changelogs, and
7153 what should go in a patch.
7154 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
7155 event, to give information on the current rate of circuit timeouts
7156 over our stored history.
7157 - Add ability to disable circuit build time learning via consensus
7158 parameter and via a LearnCircuitBuildTimeout config option. Also
7159 automatically disable circuit build time calculation if we are
7160 either a AuthoritativeDirectory, or if we fail to write our state
7161 file. Fixes bug 1296.
7162 - More gracefully handle corrupt state files, removing asserts
7163 in favor of saving a backup and resetting state.
7164 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
7168 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7170 - When a2x fails, mention that the user could disable manpages instead
7171 of trying to fix their asciidoc installation.
7172 - Where available, use Libevent 2.0's periodic timers so that our
7173 once-per-second cleanup code gets called even more closely to
7174 once per second than it would otherwise. Fixes bug 943.
7175 - If you run a bridge that listens on multiple IP addresses, and
7176 some user configures a bridge address that uses a different IP
7177 address than your bridge writes in its router descriptor, and the
7178 user doesn't specify an identity key, their Tor would discard the
7179 descriptor because "it isn't one of our configured bridges", and
7180 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
7181 Bugfix on 0.2.0.3-alpha.
7182 - If OpenSSL fails to make a duplicate of a private or public key, log
7183 an error message and try to exit cleanly. May help with debugging
7184 if bug 1209 ever remanifests.
7185 - Save a couple bytes in memory allocation every time we escape
7186 certain characters in a string. Patch from Florian Zumbiehl.
7187 - Make it explicit that we don't cannibalize one-hop circuits. This
7188 happens in the wild, but doesn't turn out to be a problem because
7189 we fortunately don't use those circuits. Many thanks to outofwords
7190 for the initial analysis and to swissknife who confirmed that
7191 two-hop circuits are actually created.
7192 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
7193 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
7194 - Eliminate a case where a circuit build time warning was displayed
7195 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
7198 Changes in version 0.2.1.26 - 2010-05-02
7199 Tor 0.2.1.26 addresses the recent connection and memory overload
7200 problems we've been seeing on relays, especially relays with their
7201 DirPort open. If your relay has been crashing, or you turned it off
7202 because it used too many resources, give this release a try.
7204 This release also fixes yet another instance of broken OpenSSL libraries
7205 that was causing some relays to drop out of the consensus.
7208 - Teach relays to defend themselves from connection overload. Relays
7209 now close idle circuits early if it looks like they were intended
7210 for directory fetches. Relays are also more aggressive about closing
7211 TLS connections that have no circuits on them. Such circuits are
7212 unlikely to be re-used, and tens of thousands of them were piling
7213 up at the fast relays, causing the relays to run out of sockets
7214 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
7215 their directory fetches over TLS).
7216 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
7217 that claim to be earlier than 0.9.8m, but which have in reality
7218 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
7219 behavior. Possible fix for some cases of bug 1346.
7220 - Directory mirrors were fetching relay descriptors only from v2
7221 directory authorities, rather than v3 authorities like they should.
7222 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
7223 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
7226 - Finally get rid of the deprecated and now harmful notion of "clique
7227 mode", where directory authorities maintain TLS connections to
7231 - In the util/threads test, no longer free the test_mutex before all
7232 worker threads have finished. Bugfix on 0.2.1.6-alpha.
7233 - The master thread could starve the worker threads quite badly on
7234 certain systems, causing them to run only partially in the allowed
7235 window. This resulted in test failures. Now the master thread sleeps
7236 occasionally for a few microseconds while the two worker-threads
7237 compete for the mutex. Bugfix on 0.2.0.1-alpha.
7240 Changes in version 0.2.2.13-alpha - 2010-04-24
7241 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
7242 problems we've been seeing on relays, especially relays with their
7243 DirPort open. If your relay has been crashing, or you turned it off
7244 because it used too many resources, give this release a try.
7247 - Teach relays to defend themselves from connection overload. Relays
7248 now close idle circuits early if it looks like they were intended
7249 for directory fetches. Relays are also more aggressive about closing
7250 TLS connections that have no circuits on them. Such circuits are
7251 unlikely to be re-used, and tens of thousands of them were piling
7252 up at the fast relays, causing the relays to run out of sockets
7253 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
7254 their directory fetches over TLS).
7257 - Finally get rid of the deprecated and now harmful notion of "clique
7258 mode", where directory authorities maintain TLS connections to
7260 - Directory authorities now do an immediate reachability check as soon
7261 as they hear about a new relay. This change should slightly reduce
7262 the time between setting up a relay and getting listed as running
7263 in the consensus. It should also improve the time between setting
7264 up a bridge and seeing use by bridge users.
7265 - Directory authorities no longer launch a TLS connection to every
7266 relay as they startup. Now that we have 2k+ descriptors cached,
7267 the resulting network hiccup is becoming a burden. Besides,
7268 authorities already avoid voting about Running for the first half
7269 hour of their uptime.
7272 Changes in version 0.2.2.12-alpha - 2010-04-20
7273 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
7274 handle and vote on descriptors. It was causing relays to drop out of
7278 - Many relays have been falling out of the consensus lately because
7279 not enough authorities know about their descriptor for them to get
7280 a majority of votes. When we deprecated the v2 directory protocol,
7281 we got rid of the only way that v3 authorities can hear from each
7282 other about other descriptors. Now authorities examine every v3
7283 vote for new descriptors, and fetch them from that authority. Bugfix
7285 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
7286 and a warning in or.h related to bandwidth_weight_rule_t that
7287 prevented clean compile on OS X. Fixes bug 1363; bugfix on
7289 - Fix a segfault on relays when DirReqStatistics is enabled
7290 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
7294 - Demote a confusing TLS warning that relay operators might get when
7295 someone tries to talk to their OrPort. It is neither the operator's
7296 fault nor can they do anything about it. Fixes bug 1364; bugfix
7300 Changes in version 0.2.2.11-alpha - 2010-04-15
7301 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
7302 libraries that was causing some relays to drop out of the consensus.
7305 - Directory mirrors were fetching relay descriptors only from v2
7306 directory authorities, rather than v3 authorities like they should.
7307 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
7308 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
7309 - Fix a parsing error that made every possible value of
7310 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
7311 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
7312 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
7313 about the option without breaking older ones.
7314 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
7315 that claim to be earlier than 0.9.8m, but which have in reality
7316 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
7317 behavior. Possible fix for some cases of bug 1346.
7320 - Experiment with a more aggressive approach to preventing clients
7321 from making one-hop exit streams. Exit relays who want to try it
7322 out can set "RefuseUnknownExits 1" in their torrc, and then look
7323 for "Attempt by %s to open a stream" log messages. Let us know
7325 - Add support for statically linking zlib by specifying
7326 --enable-static-zlib, to go with our support for statically linking
7327 openssl and libevent. Resolves bug 1358.
7330 - Fix a segfault that happens whenever a Tor client that is using
7331 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
7333 - When we cleaned up the contrib/tor-exit-notice.html file, we left
7334 out the first line. Fixes bug 1295.
7335 - When building the manpage from a tarball, we required asciidoc, but
7336 the asciidoc -> roff/html conversion was already done for the
7337 tarball. Make 'make' complain only when we need asciidoc (either
7338 because we're compiling directly from git, or because we altered
7339 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
7340 - When none of the directory authorities vote on any params, Tor
7341 segfaulted when trying to make the consensus from the votes. We
7342 didn't trigger the bug in practice, because authorities do include
7343 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
7346 - In the util/threads test, no longer free the test_mutex before all
7347 worker threads have finished. Bugfix on 0.2.1.6-alpha.
7348 - The master thread could starve the worker threads quite badly on
7349 certain systems, causing them to run only partially in the allowed
7350 window. This resulted in test failures. Now the master thread sleeps
7351 occasionally for a few microseconds while the two worker-threads
7352 compete for the mutex. Bugfix on 0.2.0.1-alpha.
7355 Changes in version 0.2.2.10-alpha - 2010-03-07
7356 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
7357 could prevent relays from guessing their IP address correctly. It also
7358 starts the groundwork for another client-side performance boost, since
7359 currently we're not making efficient use of relays that have both the
7360 Guard flag and the Exit flag.
7363 - Fix a regression from our patch for bug 1244 that caused relays
7364 to guess their IP address incorrectly if they didn't set Address
7365 in their torrc and/or their address fails to resolve. Bugfix on
7366 0.2.2.9-alpha; fixes bug 1269.
7368 o Major features (performance):
7369 - Directory authorities now compute consensus weightings that instruct
7370 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
7371 and no flag. Clients that use these weightings will distribute
7372 network load more evenly across these different relay types. The
7373 weightings are in the consensus so we can change them globally in
7374 the future. Extra thanks to "outofwords" for finding some nasty
7375 security bugs in the first implementation of this feature.
7377 o Minor features (performance):
7378 - Always perform router selections using weighted relay bandwidth,
7379 even if we don't need a high capacity circuit at the time. Non-fast
7380 circuits now only differ from fast ones in that they can use relays
7381 not marked with the Fast flag. This "feature" could turn out to
7382 be a horrible bug; we should investigate more before it goes into
7386 - Allow disabling building of the manpages. Skipping the manpage
7387 speeds up the build considerably.
7389 o Minor bugfixes (on 0.2.2.x):
7390 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
7391 Bugfix on 0.2.2.9-alpha.
7392 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
7393 config option. Bugfix on 0.2.2.7-alpha.
7394 - Ship the asciidoc-helper file in the tarball, so that people can
7395 build from source if they want to, and touching the .1.txt files
7396 doesn't break the build. Bugfix on 0.2.2.9-alpha.
7398 o Minor bugfixes (on 0.2.1.x or earlier):
7399 - Fix a dereference-then-NULL-check sequence when publishing
7400 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
7402 - Fix another dereference-then-NULL-check sequence. Bugfix on
7403 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
7404 - Make sure we treat potentially not NUL-terminated strings correctly.
7405 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
7407 o Code simplifications and refactoring:
7408 - Fix some urls in the exit notice file and make it XHTML1.1 strict
7409 compliant. Based on a patch from Christian Kujau.
7410 - Don't use sed in asciidoc-helper anymore.
7411 - Make the build process fail if asciidoc cannot be found and
7412 building with asciidoc isn't disabled.
7415 Changes in version 0.2.2.9-alpha - 2010-02-22
7416 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
7417 location of a directory authority, and cleans up a bunch of small bugs.
7419 o Directory authority changes:
7420 - Change IP address for dannenberg (v3 directory authority), and
7421 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
7422 service directory authority) from the list.
7425 - Make Tor work again on the latest OS X: when deciding whether to
7426 use strange flags to turn TLS renegotiation on, detect the OpenSSL
7427 version at run-time, not compile time. We need to do this because
7428 Apple doesn't update its dev-tools headers when it updates its
7429 libraries in a security patch.
7430 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
7431 that could happen on 32-bit platforms with 64-bit time_t. Also fix
7432 a memory leak when requesting a hidden service descriptor we've
7433 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
7435 - Authorities could be tricked into giving out the Exit flag to relays
7436 that didn't allow exiting to any ports. This bug could screw
7437 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
7438 1238. Bug discovered by Martin Kowalczyk.
7439 - When freeing a session key, zero it out completely. We only zeroed
7440 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
7441 patched by ekir. Fixes bug 1254.
7444 - Fix static compilation by listing the openssl libraries in the right
7445 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
7446 - Resume handling .exit hostnames in a special way: originally we
7447 stripped the .exit part and used the requested exit relay. In
7448 0.2.2.1-alpha we stopped treating them in any special way, meaning
7449 if you use a .exit address then Tor will pass it on to the exit
7450 relay. Now we reject the .exit stream outright, since that behavior
7451 might be more expected by the user. Found and diagnosed by Scott
7452 Bennett and Downie on or-talk.
7453 - Don't spam the controller with events when we have no file
7454 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
7455 for log messages was already solved from bug 748.)
7456 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
7458 - Make the DNSPort option work with libevent 2.x. Don't alter the
7459 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
7460 - Emit a GUARD DROPPED controller event for a case we missed.
7461 - Make more fields in the controller protocol case-insensitive, since
7462 control-spec.txt said they were.
7463 - Refactor resolve_my_address() to not use gethostbyname() anymore.
7464 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
7465 - Fix a spec conformance issue: the network-status-version token
7466 must be the first token in a v3 consensus or vote. Discovered by
7467 parakeep. Bugfix on 0.2.0.3-alpha.
7469 o Code simplifications and refactoring:
7470 - Generate our manpage and HTML documentation using Asciidoc. This
7471 change should make it easier to maintain the documentation, and
7473 - Remove the --enable-iphone option. According to reports from Marco
7474 Bonetti, Tor builds fine without any special tweaking on recent
7475 iPhone SDK versions.
7476 - Removed some unnecessary files from the source distribution. The
7477 AUTHORS file has now been merged into the people page on the
7478 website. The roadmaps and design doc can now be found in the
7479 projects directory in svn.
7480 - Enabled various circuit build timeout constants to be controlled
7481 by consensus parameters. Also set better defaults for these
7482 parameters based on experimentation on broadband and simulated
7486 - The 'EXTENDCIRCUIT' control port command can now be used with
7487 a circ id of 0 and no path. This feature will cause Tor to build
7488 a new 'fast' general purpose circuit using its own path selection
7490 - Added a BUILDTIMEOUT_SET controller event to describe changes
7491 to the circuit build timeout.
7492 - Future-proof the controller protocol a bit by ignoring keyword
7493 arguments we do not recognize.
7494 - Expand homedirs passed to tor-checkkey. This should silence a
7495 coverity complaint about passing a user-supplied string into
7496 open() without checking it.
7499 Changes in version 0.2.1.25 - 2010-03-16
7500 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
7501 prevent relays from guessing their IP address correctly. It also fixes
7502 several minor potential security bugs.
7505 - Fix a regression from our patch for bug 1244 that caused relays
7506 to guess their IP address incorrectly if they didn't set Address
7507 in their torrc and/or their address fails to resolve. Bugfix on
7508 0.2.1.23; fixes bug 1269.
7509 - When freeing a session key, zero it out completely. We only zeroed
7510 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
7511 patched by ekir. Fixes bug 1254.
7514 - Fix a dereference-then-NULL-check sequence when publishing
7515 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
7517 - Fix another dereference-then-NULL-check sequence. Bugfix on
7518 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
7519 - Make sure we treat potentially not NUL-terminated strings correctly.
7520 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
7524 Changes in version 0.2.1.24 - 2010-02-21
7525 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
7529 - Work correctly out-of-the-box with even more vendor-patched versions
7530 of OpenSSL. In particular, make it so Debian and OS X don't need
7531 customized patches to run/build.
7534 Changes in version 0.2.1.23 - 2010-02-13
7535 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
7536 again on the latest OS X, and updates the location of a directory
7539 o Major bugfixes (performance):
7540 - We were selecting our guards uniformly at random, and then weighting
7541 which of our guards we'd use uniformly at random. This imbalance
7542 meant that Tor clients were severely limited on throughput (and
7543 probably latency too) by the first hop in their circuit. Now we
7544 select guards weighted by currently advertised bandwidth. We also
7545 automatically discard guards picked using the old algorithm. Fixes
7546 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7549 - Make Tor work again on the latest OS X: when deciding whether to
7550 use strange flags to turn TLS renegotiation on, detect the OpenSSL
7551 version at run-time, not compile time. We need to do this because
7552 Apple doesn't update its dev-tools headers when it updates its
7553 libraries in a security patch.
7554 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
7555 that could happen on 32-bit platforms with 64-bit time_t. Also fix
7556 a memory leak when requesting a hidden service descriptor we've
7557 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
7560 o Directory authority changes:
7561 - Change IP address for dannenberg (v3 directory authority), and
7562 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
7563 service directory authority) from the list.
7566 - Refactor resolve_my_address() to not use gethostbyname() anymore.
7567 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
7570 - Avoid a mad rush at the beginning of each month when each client
7571 rotates half of its guards. Instead we spread the rotation out
7572 throughout the month, but we still avoid leaving a precise timestamp
7573 in the state file about when we first picked the guard. Improves
7574 over the behavior introduced in 0.1.2.17.
7577 Changes in version 0.2.2.8-alpha - 2010-01-26
7578 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
7579 causing bridge relays to disappear. If you're running a bridge,
7583 - Fix a memory corruption bug on bridges that occured during the
7584 inclusion of stats data in extra-info descriptors. Also fix the
7585 interface for geoip_get_bridge_stats* to prevent similar bugs in
7586 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
7587 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
7590 - Ignore OutboundBindAddress when connecting to localhost.
7591 Connections to localhost need to come _from_ localhost, or else
7592 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
7596 Changes in version 0.2.2.7-alpha - 2010-01-19
7597 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
7598 as laying the groundwork for further relay-side performance fixes. It
7599 also starts cleaning up client behavior with respect to the EntryNodes,
7600 ExitNodes, and StrictNodes config options.
7602 This release also rotates two directory authority keys, due to a
7603 security breach of some of the Torproject servers.
7605 o Directory authority changes:
7606 - Rotate keys (both v3 identity and relay identity) for moria1
7609 o Major features (performance):
7610 - We were selecting our guards uniformly at random, and then weighting
7611 which of our guards we'd use uniformly at random. This imbalance
7612 meant that Tor clients were severely limited on throughput (and
7613 probably latency too) by the first hop in their circuit. Now we
7614 select guards weighted by currently advertised bandwidth. We also
7615 automatically discard guards picked using the old algorithm. Fixes
7616 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7617 - When choosing which cells to relay first, relays can now favor
7618 circuits that have been quiet recently, to provide lower latency
7619 for low-volume circuits. By default, relays enable or disable this
7620 feature based on a setting in the consensus. You can override
7621 this default by using the new "CircuitPriorityHalflife" config
7622 option. Design and code by Ian Goldberg, Can Tang, and Chris
7624 - Add separate per-conn write limiting to go with the per-conn read
7625 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
7626 but never per-conn write limits.
7627 - New consensus params "bwconnrate" and "bwconnburst" to let us
7628 rate-limit client connections as they enter the network. It's
7629 controlled in the consensus so we can turn it on and off for
7630 experiments. It's starting out off. Based on proposal 163.
7632 o Major features (relay selection options):
7633 - Switch to a StrictNodes config option, rather than the previous
7634 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
7635 "StrictExcludeNodes" option.
7636 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
7637 change during a config reload, mark and discard all our origin
7638 circuits. This fix should address edge cases where we change the
7639 config options and but then choose a circuit that we created before
7641 - If EntryNodes or ExitNodes are set, be more willing to use an
7642 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
7644 - Make EntryNodes config option much more aggressive even when
7645 StrictNodes is not set. Before it would prepend your requested
7646 entrynodes to your list of guard nodes, but feel free to use others
7647 after that. Now it chooses only from your EntryNodes if any of
7648 those are available, and only falls back to others if a) they're
7649 all down and b) StrictNodes is not set.
7650 - Now we refresh your entry guards from EntryNodes at each consensus
7651 fetch -- rather than just at startup and then they slowly rot as
7652 the network changes.
7655 - Stop bridge directory authorities from answering dbg-stability.txt
7656 directory queries, which would let people fetch a list of all
7657 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7660 - Log a notice when we get a new control connection. Now it's easier
7661 for security-conscious users to recognize when a local application
7662 is knocking on their controller door. Suggested by bug 1196.
7663 - New config option "CircuitStreamTimeout" to override our internal
7664 timeout schedule for how many seconds until we detach a stream from
7665 a circuit and try a new circuit. If your network is particularly
7666 slow, you might want to set this to a number like 60.
7667 - New controller command "getinfo config-text". It returns the
7668 contents that Tor would write if you send it a SAVECONF command,
7669 so the controller can write the file to disk itself.
7670 - New options for SafeLogging to allow scrubbing only log messages
7671 generated while acting as a relay.
7672 - Ship the bridges spec file in the tarball too.
7673 - Avoid a mad rush at the beginning of each month when each client
7674 rotates half of its guards. Instead we spread the rotation out
7675 throughout the month, but we still avoid leaving a precise timestamp
7676 in the state file about when we first picked the guard. Improves
7677 over the behavior introduced in 0.1.2.17.
7679 o Minor bugfixes (compiling):
7680 - Fix compilation on OS X 10.3, which has a stub mlockall() but
7681 hides it. Bugfix on 0.2.2.6-alpha.
7682 - Fix compilation on Solaris by removing support for the
7683 DisableAllSwap config option. Solaris doesn't have an rlimit for
7684 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
7687 o Minor bugfixes (crashes):
7688 - Do not segfault when writing buffer stats when we haven't observed
7689 a single circuit to report about. Found by Fabian Lanze. Bugfix on
7691 - If we're in the pathological case where there's no exit bandwidth
7692 but there is non-exit bandwidth, or no guard bandwidth but there
7693 is non-guard bandwidth, don't crash during path selection. Bugfix
7695 - Fix an impossible-to-actually-trigger buffer overflow in relay
7696 descriptor generation. Bugfix on 0.1.0.15.
7698 o Minor bugfixes (privacy):
7699 - Fix an instance where a Tor directory mirror might accidentally
7700 log the IP address of a misbehaving Tor client. Bugfix on
7702 - Don't list Windows capabilities in relay descriptors. We never made
7703 use of them, and maybe it's a bad idea to publish them. Bugfix
7706 o Minor bugfixes (other):
7707 - Resolve an edge case in path weighting that could make us misweight
7708 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
7709 - Fix statistics on client numbers by country as seen by bridges that
7710 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
7711 intervals instead of variable 12-to-48-hour intervals.
7712 - After we free an internal connection structure, overwrite it
7713 with a different memory value than we use for overwriting a freed
7714 internal circuit structure. Should help with debugging. Suggested
7716 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
7720 - Remove the HSAuthorityRecordStats option that version 0 hidden
7721 service authorities could have used to track statistics of overall
7722 hidden service usage.
7725 Changes in version 0.2.1.22 - 2010-01-19
7726 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
7727 authorities -- it would tell you its whole history of bridge descriptors
7728 if you make the right directory request. This stable update also
7729 rotates two of the seven v3 directory authority keys and locations.
7731 o Directory authority changes:
7732 - Rotate keys (both v3 identity and relay identity) for moria1
7736 - Stop bridge directory authorities from answering dbg-stability.txt
7737 directory queries, which would let people fetch a list of all
7738 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7741 Changes in version 0.2.1.21 - 2009-12-21
7742 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
7743 library. If you use Tor on Linux / Unix and you're getting SSL
7744 renegotiation errors, upgrading should help. We also recommend an
7745 upgrade if you're an exit relay.
7748 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7749 handshake from working unless we explicitly tell OpenSSL that we
7750 are using SSL renegotiation safely. We are, of course, but OpenSSL
7751 0.9.8l won't work unless we say we are.
7752 - Avoid crashing if the client is trying to upload many bytes and the
7753 circuit gets torn down at the same time, or if the flip side
7754 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
7757 - Do not refuse to learn about authority certs and v2 networkstatus
7758 documents that are older than the latest consensus. This bug might
7759 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7760 Spotted and fixed by xmux.
7761 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
7762 trigger platform-specific option misparsing case found by Coverity
7764 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
7765 trigger assert. Fixes bug 1173.
7768 Changes in version 0.2.2.6-alpha - 2009-11-19
7769 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
7770 support for the new lower-footprint "microdescriptor" directory design,
7771 future-proofing our consensus format against new hash functions or
7772 other changes, and an Android port. It also makes Tor compatible with
7773 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
7776 - Directory authorities can now create, vote on, and serve multiple
7777 parallel formats of directory data as part of their voting process.
7778 Partially implements Proposal 162: "Publish the consensus in
7780 - Directory authorities can now agree on and publish small summaries
7781 of router information that clients can use in place of regular
7782 server descriptors. This transition will eventually allow clients
7783 to use far less bandwidth for downloading information about the
7784 network. Begins the implementation of Proposal 158: "Clients
7785 download consensus + microdescriptors".
7786 - The directory voting system is now extensible to use multiple hash
7787 algorithms for signatures and resource selection. Newer formats
7788 are signed with SHA256, with a possibility for moving to a better
7789 hash algorithm in the future.
7790 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
7791 current and future memory pages via mlockall(). On supported
7792 platforms (modern Linux and probably BSD but not Windows or OS X),
7793 this should effectively disable any and all attempts to page out
7794 memory. This option requires that you start your Tor as root --
7795 if you use DisableAllSwap, please consider using the User option
7796 to properly reduce the privileges of your Tor.
7797 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
7798 to help Tor build correctly for Android phones.
7801 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7802 handshake from working unless we explicitly tell OpenSSL that we
7803 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
7804 won't work unless we say we are.
7807 - Fix a crash bug when trying to initialize the evdns module in
7808 Libevent 2. Bugfix on 0.2.1.16-rc.
7809 - Stop logging at severity 'warn' when some other Tor client tries
7810 to establish a circuit with us using weak DH keys. It's a protocol
7811 violation, but that doesn't mean ordinary users need to hear about
7812 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
7813 - Do not refuse to learn about authority certs and v2 networkstatus
7814 documents that are older than the latest consensus. This bug might
7815 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7816 Spotted and fixed by xmux.
7817 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
7818 - If all authorities restart at once right before a consensus vote,
7819 nobody will vote about "Running", and clients will get a consensus
7820 with no usable relays. Instead, authorities refuse to build a
7821 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
7822 - If your relay can't keep up with the number of incoming create
7823 cells, it would log one warning per failure into your logs. Limit
7824 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
7825 - Bridges now use "reject *:*" as their default exit policy. Bugfix
7826 on 0.2.0.3-alpha; fixes bug 1113.
7827 - Fix a memory leak on directory authorities during voting that was
7828 introduced in 0.2.2.1-alpha. Found via valgrind.
7831 Changes in version 0.2.1.20 - 2009-10-15
7832 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
7833 services at once, prepares for more performance improvements, and
7834 fixes a bunch of smaller bugs.
7836 The Windows and OS X bundles also include a more recent Vidalia,
7837 and switch from Privoxy to Polipo.
7839 The OS X installers are now drag and drop. It's best to un-install
7840 Tor/Vidalia and then install this new bundle, rather than upgrade. If
7841 you want to upgrade, you'll need to update the paths for Tor and Polipo
7842 in the Vidalia Settings window.
7845 - Send circuit or stream sendme cells when our window has decreased
7846 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7847 by Karsten when testing the "reduce circuit window" performance
7848 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7849 before the release of Tor 0.0.0. This is the new winner of the
7851 - Fix a remotely triggerable memory leak when a consensus document
7852 contains more than one signature from the same voter. Bugfix on
7854 - Avoid segfault in rare cases when finishing an introduction circuit
7855 as a client and finding out that we don't have an introduction key
7856 for it. Fixes bug 1073. Reported by Aaron Swartz.
7859 - Tor now reads the "circwindow" parameter out of the consensus,
7860 and uses that value for its circuit package window rather than the
7861 default of 1000 cells. Begins the implementation of proposal 168.
7863 o New directory authorities:
7864 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7866 - Move moria1 and tonga to alternate IP addresses.
7869 - Fix a signed/unsigned compile warning in 0.2.1.19.
7870 - Fix possible segmentation fault on directory authorities. Bugfix on
7872 - Fix an extremely rare infinite recursion bug that could occur if
7873 we tried to log a message after shutting down the log subsystem.
7874 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7875 - Fix an obscure bug where hidden services on 64-bit big-endian
7876 systems might mis-read the timestamp in v3 introduce cells, and
7877 refuse to connect back to the client. Discovered by "rotor".
7878 Bugfix on 0.2.1.6-alpha.
7879 - We were triggering a CLOCK_SKEW controller status event whenever
7880 we connect via the v2 connection protocol to any relay that has
7881 a wrong clock. Instead, we should only inform the controller when
7882 it's a trusted authority that claims our clock is wrong. Bugfix
7883 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7884 - We were telling the controller about CHECKING_REACHABILITY and
7885 REACHABILITY_FAILED status events whenever we launch a testing
7886 circuit or notice that one has failed. Instead, only tell the
7887 controller when we want to inform the user of overall success or
7888 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7890 - Don't warn when we're using a circuit that ends with a node
7891 excluded in ExcludeExitNodes, but the circuit is not used to access
7892 the outside world. This should help fix bug 1090. Bugfix on
7894 - Work around a small memory leak in some versions of OpenSSL that
7895 stopped the memory used by the hostname TLS extension from being
7899 - Add a "getinfo status/accepted-server-descriptor" controller
7900 command, which is the recommended way for controllers to learn
7901 whether our server descriptor has been successfully received by at
7902 least on directory authority. Un-recommend good-server-descriptor
7903 getinfo and status events until we have a better design for them.
7906 Changes in version 0.2.2.5-alpha - 2009-10-11
7907 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
7910 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
7912 o Directory authorities:
7913 - Temporarily (just for this release) move dizum to an alternate
7917 Changes in version 0.2.2.4-alpha - 2009-10-10
7918 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
7919 introduces a new unit test framework, shifts directry authority
7920 addresses around to reduce the impact from recent blocking events,
7921 and fixes a few smaller bugs.
7924 - Fix several more asserts in the circuit_build_times code, for
7925 example one that causes Tor to fail to start once we have
7926 accumulated 5000 build times in the state file. Bugfixes on
7927 0.2.2.2-alpha; fixes bug 1108.
7929 o New directory authorities:
7930 - Move moria1 and Tonga to alternate IP addresses.
7933 - Log SSL state transitions at debug level during handshake, and
7934 include SSL states in error messages. This may help debug future
7935 SSL handshake issues.
7936 - Add a new "Handshake" log domain for activities that happen
7937 during the TLS handshake.
7938 - Revert to the "June 3 2009" ip-to-country file. The September one
7939 seems to have removed most US IP addresses.
7940 - Directory authorities now reject Tor relays with versions less than
7941 0.1.2.14. This step cuts out four relays from the current network,
7942 none of which are very big.
7945 - Fix a couple of smaller issues with gathering statistics. Bugfixes
7947 - Fix two memory leaks in the error case of
7948 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
7949 - Don't count one-hop circuits when we're estimating how long it
7950 takes circuits to build on average. Otherwise we'll set our circuit
7951 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
7952 - Directory authorities no longer change their opinion of, or vote on,
7953 whether a router is Running, unless they have themselves been
7954 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
7957 o Code simplifications and refactoring:
7958 - Revise our unit tests to use the "tinytest" framework, so we
7959 can run tests in their own processes, have smarter setup/teardown
7960 code, and so on. The unit test code has moved to its own
7961 subdirectory, and has been split into multiple modules.
7964 Changes in version 0.2.2.3-alpha - 2009-09-23
7965 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
7968 - Fix an overzealous assert in our new circuit build timeout code.
7969 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
7972 - If the networkstatus consensus tells us that we should use a
7973 negative circuit package window, ignore it. Otherwise we'll
7974 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
7977 Changes in version 0.2.2.2-alpha - 2009-09-21
7978 Tor 0.2.2.2-alpha introduces our latest performance improvement for
7979 clients: Tor tracks the average time it takes to build a circuit, and
7980 avoids using circuits that take too long to build. For fast connections,
7981 this feature can cut your expected latency in half. For slow or flaky
7982 connections, it could ruin your Tor experience. Let us know if it does!
7985 - Tor now tracks how long it takes to build client-side circuits
7986 over time, and adapts its timeout to local network performance.
7987 Since a circuit that takes a long time to build will also provide
7988 bad performance, we get significant latency improvements by
7989 discarding the slowest 20% of circuits. Specifically, Tor creates
7990 circuits more aggressively than usual until it has enough data
7991 points for a good timeout estimate. Implements proposal 151.
7992 We are especially looking for reports (good and bad) from users with
7993 both EDGE and broadband connections that can move from broadband
7994 to EDGE and find out if the build-time data in the .tor/state gets
7995 reset without loss of Tor usability. You should also see a notice
7996 log message telling you that Tor has reset its timeout.
7997 - Directory authorities can now vote on arbitary integer values as
7998 part of the consensus process. This is designed to help set
7999 network-wide parameters. Implements proposal 167.
8000 - Tor now reads the "circwindow" parameter out of the consensus,
8001 and uses that value for its circuit package window rather than the
8002 default of 1000 cells. Begins the implementation of proposal 168.
8005 - Fix a remotely triggerable memory leak when a consensus document
8006 contains more than one signature from the same voter. Bugfix on
8010 - Fix an extremely rare infinite recursion bug that could occur if
8011 we tried to log a message after shutting down the log subsystem.
8012 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
8013 - Fix parsing for memory or time units given without a space between
8014 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
8015 - A networkstatus vote must contain exactly one signature. Spec
8016 conformance issue. Bugfix on 0.2.0.3-alpha.
8017 - Fix an obscure bug where hidden services on 64-bit big-endian
8018 systems might mis-read the timestamp in v3 introduce cells, and
8019 refuse to connect back to the client. Discovered by "rotor".
8020 Bugfix on 0.2.1.6-alpha.
8021 - We were triggering a CLOCK_SKEW controller status event whenever
8022 we connect via the v2 connection protocol to any relay that has
8023 a wrong clock. Instead, we should only inform the controller when
8024 it's a trusted authority that claims our clock is wrong. Bugfix
8025 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
8026 - We were telling the controller about CHECKING_REACHABILITY and
8027 REACHABILITY_FAILED status events whenever we launch a testing
8028 circuit or notice that one has failed. Instead, only tell the
8029 controller when we want to inform the user of overall success or
8030 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
8032 - Don't warn when we're using a circuit that ends with a node
8033 excluded in ExcludeExitNodes, but the circuit is not used to access
8034 the outside world. This should help fix bug 1090, but more problems
8035 remain. Bugfix on 0.2.1.6-alpha.
8036 - Work around a small memory leak in some versions of OpenSSL that
8037 stopped the memory used by the hostname TLS extension from being
8039 - Make our 'torify' script more portable; if we have only one of
8040 'torsocks' or 'tsocks' installed, don't complain to the user;
8041 and explain our warning about tsocks better.
8044 - Add a "getinfo status/accepted-server-descriptor" controller
8045 command, which is the recommended way for controllers to learn
8046 whether our server descriptor has been successfully received by at
8047 least on directory authority. Un-recommend good-server-descriptor
8048 getinfo and status events until we have a better design for them.
8049 - Update to the "September 4 2009" ip-to-country file.
8052 Changes in version 0.2.2.1-alpha - 2009-08-26
8053 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
8054 Tor clients to bootstrap on networks where only port 80 is reachable,
8055 makes it more straightforward to support hardware crypto accelerators,
8056 and starts the groundwork for gathering stats safely at relays.
8059 - Start the process of disabling ".exit" address notation, since it
8060 can be used for a variety of esoteric application-level attacks
8061 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
8064 o New directory authorities:
8065 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
8069 - New AccelName and AccelDir options add support for dynamic OpenSSL
8070 hardware crypto acceleration engines.
8071 - Tor now supports tunneling all of its outgoing connections over
8072 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
8073 configuration options. Code by Christopher Davis.
8076 - Send circuit or stream sendme cells when our window has decreased
8077 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
8078 by Karsten when testing the "reduce circuit window" performance
8079 patch. Bugfix on the 54th commit on Tor -- from July 2002,
8080 before the release of Tor 0.0.0. This is the new winner of the
8083 o New options for gathering stats safely:
8084 - Directory mirrors that set "DirReqStatistics 1" write statistics
8085 about directory requests to disk every 24 hours. As compared to the
8086 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
8087 1) stats are written to disk exactly every 24 hours; 2) estimated
8088 shares of v2 and v3 requests are determined as mean values, not at
8089 the end of a measurement period; 3) unresolved requests are listed
8090 with country code '??'; 4) directories also measure download times.
8091 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
8092 number of exit streams and transferred bytes per port to disk every
8094 - Relays that set "CellStatistics 1" write statistics on how long
8095 cells spend in their circuit queues to disk every 24 hours.
8096 - Entry nodes that set "EntryStatistics 1" write statistics on the
8097 rough number and origins of connecting clients to disk every 24
8099 - Relays that write any of the above statistics to disk and set
8100 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
8101 their extra-info documents.
8104 - New --digests command-line switch to output the digests of the
8105 source files Tor was built with.
8106 - The "torify" script now uses torsocks where available.
8107 - The memarea code now uses a sentinel value at the end of each area
8108 to make sure nothing writes beyond the end of an area. This might
8109 help debug some conceivable causes of bug 930.
8110 - Time and memory units in the configuration file can now be set to
8111 fractional units. For example, "2.5 GB" is now a valid value for
8113 - Certain Tor clients (such as those behind check.torproject.org) may
8114 want to fetch the consensus in an extra early manner. To enable this
8115 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
8116 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
8117 as only certain clients who must have this information sooner should
8119 - Instead of adding the svn revision to the Tor version string, report
8120 the git commit (when we're building from a git checkout).
8123 - If any of the v3 certs we download are unparseable, we should
8124 actually notice the failure so we don't retry indefinitely. Bugfix
8125 on 0.2.0.x; reported by "rotator".
8126 - If the cached cert file is unparseable, warn but don't exit.
8127 - Fix possible segmentation fault on directory authorities. Bugfix on
8129 - When Tor fails to parse a descriptor of any kind, dump it to disk.
8130 Might help diagnosing bug 1051.
8132 o Deprecated and removed features:
8133 - The controller no longer accepts the old obsolete "addr-mappings/"
8134 or "unregistered-servers-" GETINFO values.
8135 - Hidden services no longer publish version 0 descriptors, and clients
8136 do not request or use version 0 descriptors. However, the old hidden
8137 service authorities still accept and serve version 0 descriptors
8138 when contacted by older hidden services/clients.
8139 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
8140 always on; using them is necessary for correct forward-compatible
8142 - Remove support for .noconnect style addresses. Nobody was using
8143 them, and they provided another avenue for detecting Tor users
8144 via application-level web tricks.
8146 o Packaging changes:
8147 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
8148 installer bundles. See
8149 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
8150 for details of what's new in Vidalia 0.2.3.
8151 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
8152 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
8153 configuration file, rather than the old Privoxy.
8154 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
8155 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
8156 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
8157 better compatibility with OS X 10.6, aka Snow Leopard.
8158 - OS X Vidalia Bundle: The multi-package installer is now replaced
8159 by a simple drag and drop to the /Applications folder. This change
8160 occurred with the upgrade to Vidalia 0.2.3.
8163 Changes in version 0.2.1.19 - 2009-07-28
8164 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
8165 services on Tor 0.2.1.3-alpha through 0.2.1.18.
8168 - Make accessing hidden services on 0.2.1.x work right again.
8169 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
8170 part of patch provided by "optimist".
8173 - When a relay/bridge is writing out its identity key fingerprint to
8174 the "fingerprint" file and to its logs, write it without spaces. Now
8175 it will look like the fingerprints in our bridges documentation,
8176 and confuse fewer users.
8179 - Relays no longer publish a new server descriptor if they change
8180 their MaxAdvertisedBandwidth config option but it doesn't end up
8181 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
8182 fixes bug 1026. Patch from Sebastian.
8183 - Avoid leaking memory every time we get a create cell but we have
8184 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
8185 fixes bug 1034. Reported by BarkerJr.
8188 Changes in version 0.2.1.18 - 2009-07-24
8189 Tor 0.2.1.18 lays the foundations for performance improvements,
8190 adds status events to help users diagnose bootstrap problems, adds
8191 optional authentication/authorization for hidden services, fixes a
8192 variety of potential anonymity problems, and includes a huge pile of
8193 other features and bug fixes.
8196 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
8199 Changes in version 0.2.1.17-rc - 2009-07-07
8200 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
8201 candidate for the 0.2.1.x series. It lays the groundwork for further
8202 client performance improvements, and also fixes a big bug with directory
8203 authorities that were causing them to assign Guard and Stable flags
8206 The Windows bundles also finally include the geoip database that we
8207 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
8208 should actually install Torbutton rather than giving you a cryptic
8209 failure message (oops).
8212 - Clients now use the bandwidth values in the consensus, rather than
8213 the bandwidth values in each relay descriptor. This approach opens
8214 the door to more accurate bandwidth estimates once the directory
8215 authorities start doing active measurements. Implements more of
8219 - When Tor clients restart after 1-5 days, they discard all their
8220 cached descriptors as too old, but they still use the cached
8221 consensus document. This approach is good for robustness, but
8222 bad for performance: since they don't know any bandwidths, they
8223 end up choosing at random rather than weighting their choice by
8224 speed. Fixed by the above feature of putting bandwidths in the
8225 consensus. Bugfix on 0.2.0.x.
8226 - Directory authorities were neglecting to mark relays down in their
8227 internal histories if the relays fall off the routerlist without
8228 ever being found unreachable. So there were relays in the histories
8229 that haven't been seen for eight months, and are listed as being
8230 up for eight months. This wreaked havoc on the "median wfu"
8231 and "median mtbf" calculations, in turn making Guard and Stable
8232 flags very wrong, hurting network performance. Fixes bugs 696 and
8233 969. Bugfix on 0.2.0.6-alpha.
8236 - Serve the DirPortFrontPage page even when we have been approaching
8237 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
8238 - The control port would close the connection before flushing long
8239 replies, such as the network consensus, if a QUIT command was issued
8240 before the reply had completed. Now, the control port flushes all
8241 pending replies before closing the connection. Also fixed a spurious
8242 warning when a QUIT command is issued after a malformed or rejected
8243 AUTHENTICATE command, but before the connection was closed. Patch
8244 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
8245 - When we can't find an intro key for a v2 hidden service descriptor,
8246 fall back to the v0 hidden service descriptor and log a bug message.
8247 Workaround for bug 1024.
8248 - Fix a log message that did not respect the SafeLogging option.
8252 - If we're a relay and we change our IP address, be more verbose
8253 about the reason that made us change. Should help track down
8254 further bugs for relays on dynamic IP addresses.
8257 Changes in version 0.2.0.35 - 2009-06-24
8259 - Avoid crashing in the presence of certain malformed descriptors.
8260 Found by lark, and by automated fuzzing.
8261 - Fix an edge case where a malicious exit relay could convince a
8262 controller that the client's DNS question resolves to an internal IP
8263 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
8266 - Finally fix the bug where dynamic-IP relays disappear when their
8267 IP address changes: directory mirrors were mistakenly telling
8268 them their old address if they asked via begin_dir, so they
8269 never got an accurate answer about their new address, so they
8270 just vanished after a day. For belt-and-suspenders, relays that
8271 don't set Address in their config now avoid using begin_dir for
8272 all direct connections. Should fix bugs 827, 883, and 900.
8273 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
8274 that would occur on some exit nodes when DNS failures and timeouts
8275 occurred in certain patterns. Fix for bug 957.
8278 - When starting with a cache over a few days old, do not leak
8279 memory for the obsolete router descriptors in it. Bugfix on
8280 0.2.0.33; fixes bug 672.
8281 - Hidden service clients didn't use a cached service descriptor that
8282 was older than 15 minutes, but wouldn't fetch a new one either,
8283 because there was already one in the cache. Now, fetch a v2
8284 descriptor unless the same descriptor was added to the cache within
8285 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
8288 Changes in version 0.2.1.16-rc - 2009-06-20
8289 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
8290 a bunch of minor bugs.
8293 - Fix an edge case where a malicious exit relay could convince a
8294 controller that the client's DNS question resolves to an internal IP
8295 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
8297 o Major performance improvements (on 0.2.0.x):
8298 - Disable and refactor some debugging checks that forced a linear scan
8299 over the whole server-side DNS cache. These accounted for over 50%
8300 of CPU time on a relatively busy exit node's gprof profile. Found
8302 - Disable some debugging checks that appeared in exit node profile
8306 - Update to the "June 3 2009" ip-to-country file.
8307 - Do not have tor-resolve automatically refuse all .onion addresses;
8308 if AutomapHostsOnResolve is set in your torrc, this will work fine.
8310 o Minor bugfixes (on 0.2.0.x):
8311 - Log correct error messages for DNS-related network errors on
8313 - Fix a race condition that could cause crashes or memory corruption
8314 when running as a server with a controller listening for log
8316 - Avoid crashing when we have a policy specified in a DirPolicy or
8317 SocksPolicy or ReachableAddresses option with ports set on it,
8318 and we re-load the policy. May fix bug 996.
8319 - Hidden service clients didn't use a cached service descriptor that
8320 was older than 15 minutes, but wouldn't fetch a new one either,
8321 because there was already one in the cache. Now, fetch a v2
8322 descriptor unless the same descriptor was added to the cache within
8323 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
8325 o Minor bugfixes (on 0.2.1.x):
8326 - Don't warn users about low port and hibernation mix when they
8327 provide a *ListenAddress directive to fix that. Bugfix on
8329 - When switching back and forth between bridge mode, do not start
8330 gathering GeoIP data until two hours have passed.
8331 - Do not complain that the user has requested an excluded node as
8332 an exit when the node is not really an exit. This could happen
8333 because the circuit was for testing, or an introduction point.
8337 Changes in version 0.2.1.15-rc - 2009-05-25
8338 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
8339 series. It fixes a major bug on fast exit relays, as well as a variety
8342 o Major bugfixes (on 0.2.0.x):
8343 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
8344 that would occur on some exit nodes when DNS failures and timeouts
8345 occurred in certain patterns. Fix for bug 957.
8347 o Minor bugfixes (on 0.2.0.x):
8348 - Actually return -1 in the error case for read_bandwidth_usage().
8349 Harmless bug, since we currently don't care about the return value
8350 anywhere. Bugfix on 0.2.0.9-alpha.
8351 - Provide a more useful log message if bug 977 (related to buffer
8352 freelists) ever reappears, and do not crash right away.
8353 - Fix an assertion failure on 64-bit platforms when we allocated
8354 memory right up to the end of a memarea, then realigned the memory
8355 one step beyond the end. Fixes a possible cause of bug 930.
8356 - Protect the count of open sockets with a mutex, so we can't
8357 corrupt it when two threads are closing or opening sockets at once.
8358 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
8359 - Don't allow a bridge to publish its router descriptor to a
8360 non-bridge directory authority. Fixes part of bug 932.
8361 - When we change to or from being a bridge, reset our counts of
8362 client usage by country. Fixes bug 932.
8363 - Fix a bug that made stream bandwidth get misreported to the
8365 - Stop using malloc_usable_size() to use more area than we had
8366 actually allocated: it was safe, but made valgrind really unhappy.
8367 - Fix a memory leak when v3 directory authorities load their keys
8368 and cert from disk. Bugfix on 0.2.0.1-alpha.
8370 o Minor bugfixes (on 0.2.1.x):
8371 - Fix use of freed memory when deciding to mark a non-addable
8372 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
8375 Changes in version 0.2.1.14-rc - 2009-04-12
8376 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
8377 series. It begins fixing some major performance problems, and also
8378 finally addresses the bug that was causing relays on dynamic IP
8379 addresses to fall out of the directory.
8382 - Clients replace entry guards that were chosen more than a few months
8383 ago. This change should significantly improve client performance,
8384 especially once more people upgrade, since relays that have been
8385 a guard for a long time are currently overloaded.
8387 o Major bugfixes (on 0.2.0):
8388 - Finally fix the bug where dynamic-IP relays disappear when their
8389 IP address changes: directory mirrors were mistakenly telling
8390 them their old address if they asked via begin_dir, so they
8391 never got an accurate answer about their new address, so they
8392 just vanished after a day. For belt-and-suspenders, relays that
8393 don't set Address in their config now avoid using begin_dir for
8394 all direct connections. Should fix bugs 827, 883, and 900.
8395 - Relays were falling out of the networkstatus consensus for
8396 part of a day if they changed their local config but the
8397 authorities discarded their new descriptor as "not sufficiently
8398 different". Now directory authorities accept a descriptor as changed
8399 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
8401 - Avoid crashing in the presence of certain malformed descriptors.
8402 Found by lark, and by automated fuzzing.
8405 - When generating circuit events with verbose nicknames for
8406 controllers, try harder to look up nicknames for routers on a
8407 circuit. (Previously, we would look in the router descriptors we had
8408 for nicknames, but not in the consensus.) Partial fix for bug 941.
8409 - If the bridge config line doesn't specify a port, assume 443.
8410 This makes bridge lines a bit smaller and easier for users to
8412 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
8413 bytes (aka 20KB/s), to match our documentation. Also update
8414 directory authorities so they always assign the Fast flag to relays
8415 with 20KB/s of capacity. Now people running relays won't suddenly
8416 find themselves not seeing any use, if the network gets faster
8418 - Update to the "April 3 2009" ip-to-country file.
8421 - Avoid trying to print raw memory to the logs when we decide to
8422 give up on downloading a given relay descriptor. Bugfix on
8424 - In tor-resolve, when the Tor client to use is specified by
8425 <hostname>:<port>, actually use the specified port rather than
8426 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
8427 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
8428 - When starting with a cache over a few days old, do not leak
8429 memory for the obsolete router descriptors in it. Bugfix on
8431 - Avoid double-free on list of successfully uploaded hidden
8432 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
8433 - Change memarea_strndup() implementation to work even when
8434 duplicating a string at the end of a page. This bug was
8435 harmless for now, but could have meant crashes later. Fix by
8436 lark. Bugfix on 0.2.1.1-alpha.
8437 - Limit uploaded directory documents to be 16M rather than 500K.
8438 The directory authorities were refusing v3 consensus votes from
8439 other authorities, since the votes are now 504K. Fixes bug 959;
8440 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
8441 - Directory authorities should never send a 503 "busy" response to
8442 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
8446 Changes in version 0.2.1.13-alpha - 2009-03-09
8447 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
8448 cleanups. We're finally getting close to a release candidate.
8451 - Correctly update the list of which countries we exclude as
8452 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
8453 lark. Bugfix on 0.2.1.6-alpha.
8455 o Minor bugfixes (on 0.2.0.x and earlier):
8456 - Automatically detect MacOSX versions earlier than 10.4.0, and
8457 disable kqueue from inside Tor when running with these versions.
8458 We previously did this from the startup script, but that was no
8459 help to people who didn't use the startup script. Resolves bug 863.
8460 - When we had picked an exit node for a connection, but marked it as
8461 "optional", and it turned out we had no onion key for the exit,
8462 stop wanting that exit and try again. This situation may not
8463 be possible now, but will probably become feasible with proposal
8464 158. Spotted by rovv. Fixes another case of bug 752.
8465 - Clients no longer cache certificates for authorities they do not
8466 recognize. Bugfix on 0.2.0.9-alpha.
8467 - When we can't transmit a DNS request due to a network error, retry
8468 it after a while, and eventually transmit a failing response to
8469 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
8470 - If the controller claimed responsibility for a stream, but that
8471 stream never finished making its connection, it would live
8472 forever in circuit_wait state. Now we close it after SocksTimeout
8473 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
8474 - Drop begin cells to a hidden service if they come from the middle
8475 of a circuit. Patch from lark.
8476 - When we erroneously receive two EXTEND cells for the same circuit
8477 ID on the same connection, drop the second. Patch from lark.
8478 - Fix a crash that occurs on exit nodes when a nameserver request
8479 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
8480 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
8482 - Do not assume that a stack-allocated character array will be
8483 64-bit aligned on platforms that demand that uint64_t access is
8484 aligned. Possible fix for bug 604.
8485 - Parse dates and IPv4 addresses in a locale- and libc-independent
8486 manner, to avoid platform-dependent behavior on malformed input.
8487 - Build correctly when configured to build outside the main source
8488 path. Patch from Michael Gold.
8489 - We were already rejecting relay begin cells with destination port
8490 of 0. Now also reject extend cells with destination port or address
8491 of 0. Suggested by lark.
8493 o Minor bugfixes (on 0.2.1.x):
8494 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
8495 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
8496 - If we're an exit node, scrub the IP address to which we are exiting
8497 in the logs. Bugfix on 0.2.1.8-alpha.
8500 - On Linux, use the prctl call to re-enable core dumps when the user
8502 - New controller event NEWCONSENSUS that lists the networkstatus
8503 lines for every recommended relay. Now controllers like Torflow
8504 can keep up-to-date on which relays they should be using.
8505 - Update to the "February 26 2009" ip-to-country file.
8508 Changes in version 0.2.0.34 - 2009-02-08
8509 Tor 0.2.0.34 features several more security-related fixes. You should
8510 upgrade, especially if you run an exit relay (remote crash) or a
8511 directory authority (remote infinite loop), or you're on an older
8512 (pre-XP) or not-recently-patched Windows (remote exploit).
8514 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
8515 have many known flaws, and nobody should be using them. You should
8516 upgrade. If you're using a Linux or BSD and its packages are obsolete,
8517 stop using those packages and upgrade anyway.
8520 - Fix an infinite-loop bug on handling corrupt votes under certain
8521 circumstances. Bugfix on 0.2.0.8-alpha.
8522 - Fix a temporary DoS vulnerability that could be performed by
8523 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
8524 - Avoid a potential crash on exit nodes when processing malformed
8525 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
8526 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8527 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8530 - Fix compilation on systems where time_t is a 64-bit integer.
8531 Patch from Matthias Drochner.
8532 - Don't consider expiring already-closed client connections. Fixes
8533 bug 893. Bugfix on 0.0.2pre20.
8536 Changes in version 0.2.1.12-alpha - 2009-02-08
8537 Tor 0.2.1.12-alpha features several more security-related fixes. You
8538 should upgrade, especially if you run an exit relay (remote crash) or
8539 a directory authority (remote infinite loop), or you're on an older
8540 (pre-XP) or not-recently-patched Windows (remote exploit). It also
8541 includes a big pile of minor bugfixes and cleanups.
8544 - Fix an infinite-loop bug on handling corrupt votes under certain
8545 circumstances. Bugfix on 0.2.0.8-alpha.
8546 - Fix a temporary DoS vulnerability that could be performed by
8547 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
8548 - Avoid a potential crash on exit nodes when processing malformed
8549 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
8552 - Let controllers actually ask for the "clients_seen" event for
8553 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
8554 reported by Matt Edman.
8555 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
8557 - Fix a bug in address parsing that was preventing bridges or hidden
8558 service targets from being at IPv6 addresses.
8559 - Solve a bug that kept hardware crypto acceleration from getting
8560 enabled when accounting was turned on. Fixes bug 907. Bugfix on
8562 - Remove a bash-ism from configure.in to build properly on non-Linux
8563 platforms. Bugfix on 0.2.1.1-alpha.
8564 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
8565 headers. Bugfix on 0.2.0.10-alpha.
8566 - Don't consider expiring already-closed client connections. Fixes
8567 bug 893. Bugfix on 0.0.2pre20.
8568 - Fix another interesting corner-case of bug 891 spotted by rovv:
8569 Previously, if two hosts had different amounts of clock drift, and
8570 one of them created a new connection with just the wrong timing,
8571 the other might decide to deprecate the new connection erroneously.
8572 Bugfix on 0.1.1.13-alpha.
8573 - Resolve a very rare crash bug that could occur when the user forced
8574 a nameserver reconfiguration during the middle of a nameserver
8575 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
8576 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
8577 Bugfix on 0.2.1.7-alpha.
8578 - If we're using bridges and our network goes away, be more willing
8579 to forgive our bridges and try again when we get an application
8580 request. Bugfix on 0.2.0.x.
8583 - Support platforms where time_t is 64 bits long. (Congratulations,
8584 NetBSD!) Patch from Matthias Drochner.
8585 - Add a 'getinfo status/clients-seen' controller command, in case
8586 controllers want to hear clients_seen events but connect late.
8589 - Disable GCC's strict alias optimization by default, to avoid the
8590 likelihood of its introducing subtle bugs whenever our code violates
8591 the letter of C99's alias rules.
8594 Changes in version 0.2.0.33 - 2009-01-21
8595 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
8596 useful to users. It also finally fixes a bug where a relay or client
8597 that's been off for many days would take a long time to bootstrap.
8599 This update also fixes an important security-related bug reported by
8600 Ilja van Sprundel. You should upgrade. (We'll send out more details
8601 about the bug once people have had some time to upgrade.)
8604 - Fix a heap-corruption bug that may be remotely triggerable on
8605 some platforms. Reported by Ilja van Sprundel.
8608 - When a stream at an exit relay is in state "resolving" or
8609 "connecting" and it receives an "end" relay cell, the exit relay
8610 would silently ignore the end cell and not close the stream. If
8611 the client never closes the circuit, then the exit relay never
8612 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
8614 - When sending CREATED cells back for a given circuit, use a 64-bit
8615 connection ID to find the right connection, rather than an addr:port
8616 combination. Now that we can have multiple OR connections between
8617 the same ORs, it is no longer possible to use addr:port to uniquely
8618 identify a connection.
8619 - Bridge relays that had DirPort set to 0 would stop fetching
8620 descriptors shortly after startup, and then briefly resume
8621 after a new bandwidth test and/or after publishing a new bridge
8622 descriptor. Bridge users that try to bootstrap from them would
8623 get a recent networkstatus but would get descriptors from up to
8624 18 hours earlier, meaning most of the descriptors were obsolete
8625 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8626 - Prevent bridge relays from serving their 'extrainfo' document
8627 to anybody who asks, now that extrainfo docs include potentially
8628 sensitive aggregated client geoip summaries. Bugfix on
8630 - If the cached networkstatus consensus is more than five days old,
8631 discard it rather than trying to use it. In theory it could be
8632 useful because it lists alternate directory mirrors, but in practice
8633 it just means we spend many minutes trying directory mirrors that
8634 are long gone from the network. Also discard router descriptors as
8635 we load them if they are more than five days old, since the onion
8636 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
8639 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8640 could make gcc generate non-functional binary search code. Bugfix
8642 - Build correctly on platforms without socklen_t.
8643 - Compile without warnings on solaris.
8644 - Avoid potential crash on internal error during signature collection.
8645 Fixes bug 864. Patch from rovv.
8646 - Correct handling of possible malformed authority signing key
8647 certificates with internal signature types. Fixes bug 880.
8648 Bugfix on 0.2.0.3-alpha.
8649 - Fix a hard-to-trigger resource leak when logging credential status.
8651 - When we can't initialize DNS because the network is down, do not
8652 automatically stop Tor from starting. Instead, we retry failed
8653 dns_init() every 10 minutes, and change the exit policy to reject
8654 *:* until one succeeds. Fixes bug 691.
8655 - Use 64 bits instead of 32 bits for connection identifiers used with
8656 the controller protocol, to greatly reduce risk of identifier reuse.
8657 - When we're choosing an exit node for a circuit, and we have
8658 no pending streams, choose a good general exit rather than one that
8659 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8660 - Fix another case of assuming, when a specific exit is requested,
8661 that we know more than the user about what hosts it allows.
8662 Fixes one case of bug 752. Patch from rovv.
8663 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8664 seconds. Warn the user if lower values are given in the
8665 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8666 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8667 user if lower values are given in the configuration. Bugfix on
8668 0.1.1.17-rc. Patch by Sebastian.
8669 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
8670 the cache because we already had a v0 descriptor with the same ID.
8671 Bugfix on 0.2.0.18-alpha.
8672 - Fix a race condition when freeing keys shared between main thread
8673 and CPU workers that could result in a memory leak. Bugfix on
8674 0.1.0.1-rc. Fixes bug 889.
8675 - Send a valid END cell back when a client tries to connect to a
8676 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8677 840. Patch from rovv.
8678 - Check which hops rendezvous stream cells are associated with to
8679 prevent possible guess-the-streamid injection attacks from
8680 intermediate hops. Fixes another case of bug 446. Based on patch
8682 - If a broken client asks a non-exit router to connect somewhere,
8683 do not even do the DNS lookup before rejecting the connection.
8684 Fixes another case of bug 619. Patch from rovv.
8685 - When a relay gets a create cell it can't decrypt (e.g. because it's
8686 using the wrong onion key), we were dropping it and letting the
8687 client time out. Now actually answer with a destroy cell. Fixes
8688 bug 904. Bugfix on 0.0.2pre8.
8690 o Minor bugfixes (hidden services):
8691 - Do not throw away existing introduction points on SIGHUP. Bugfix on
8692 0.0.6pre1. Patch by Karsten. Fixes bug 874.
8695 - Report the case where all signatures in a detached set are rejected
8696 differently than the case where there is an error handling the
8698 - When we realize that another process has modified our cached
8699 descriptors, print out a more useful error message rather than
8700 triggering an assertion. Fixes bug 885. Patch from Karsten.
8701 - Implement the 0x20 hack to better resist DNS poisoning: set the
8702 case on outgoing DNS requests randomly, and reject responses that do
8703 not match the case correctly. This logic can be disabled with the
8704 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
8705 of servers that do not reliably preserve case in replies. See
8706 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8708 - Check DNS replies for more matching fields to better resist DNS
8710 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8711 compress cells, which are basically all encrypted, compressed, or
8715 Changes in version 0.2.1.11-alpha - 2009-01-20
8716 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
8717 week it will take a long time to bootstrap again" bug. It also fixes
8718 an important security-related bug reported by Ilja van Sprundel. You
8719 should upgrade. (We'll send out more details about the bug once people
8720 have had some time to upgrade.)
8723 - Fix a heap-corruption bug that may be remotely triggerable on
8724 some platforms. Reported by Ilja van Sprundel.
8727 - Discard router descriptors as we load them if they are more than
8728 five days old. Otherwise if Tor is off for a long time and then
8729 starts with cached descriptors, it will try to use the onion
8730 keys in those obsolete descriptors when building circuits. Bugfix
8731 on 0.2.0.x. Fixes bug 887.
8734 - Try to make sure that the version of Libevent we're running with
8735 is binary-compatible with the one we built with. May address bug
8737 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
8738 for bug 905. Bugfix on 0.2.1.7-alpha.
8739 - Add a new --enable-local-appdata configuration switch to change
8740 the default location of the datadir on win32 from APPDATA to
8741 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
8742 entirely. Patch from coderman.
8745 - Make outbound DNS packets respect the OutboundBindAddress setting.
8746 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
8747 - When our circuit fails at the first hop (e.g. we get a destroy
8748 cell back), avoid using that OR connection anymore, and also
8749 tell all the one-hop directory requests waiting for it that they
8750 should fail. Bugfix on 0.2.1.3-alpha.
8751 - In the torify(1) manpage, mention that tsocks will leak your
8755 Changes in version 0.2.1.10-alpha - 2009-01-06
8756 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
8757 would make the bridge relay not so useful if it had DirPort set to 0,
8758 and one that could let an attacker learn a little bit of information
8759 about the bridge's users), and a bug that would cause your Tor relay
8760 to ignore a circuit create request it can't decrypt (rather than reply
8761 with an error). It also fixes a wide variety of other bugs.
8764 - If the cached networkstatus consensus is more than five days old,
8765 discard it rather than trying to use it. In theory it could
8766 be useful because it lists alternate directory mirrors, but in
8767 practice it just means we spend many minutes trying directory
8768 mirrors that are long gone from the network. Helps bug 887 a bit;
8770 - Bridge relays that had DirPort set to 0 would stop fetching
8771 descriptors shortly after startup, and then briefly resume
8772 after a new bandwidth test and/or after publishing a new bridge
8773 descriptor. Bridge users that try to bootstrap from them would
8774 get a recent networkstatus but would get descriptors from up to
8775 18 hours earlier, meaning most of the descriptors were obsolete
8776 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8777 - Prevent bridge relays from serving their 'extrainfo' document
8778 to anybody who asks, now that extrainfo docs include potentially
8779 sensitive aggregated client geoip summaries. Bugfix on
8783 - New controller event "clients_seen" to report a geoip-based summary
8784 of which countries we've seen clients from recently. Now controllers
8785 like Vidalia can show bridge operators that they're actually making
8787 - Build correctly against versions of OpenSSL 0.9.8 or later built
8788 without support for deprecated functions.
8789 - Update to the "December 19 2008" ip-to-country file.
8791 o Minor bugfixes (on 0.2.0.x):
8792 - Authorities now vote for the Stable flag for any router whose
8793 weighted MTBF is at least 5 days, regardless of the mean MTBF.
8794 - Do not remove routers as too old if we do not have any consensus
8795 document. Bugfix on 0.2.0.7-alpha.
8796 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8797 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8798 - When an exit relay resolves a stream address to a local IP address,
8799 do not just keep retrying that same exit relay over and
8800 over. Instead, just close the stream. Addresses bug 872. Bugfix
8801 on 0.2.0.32. Patch from rovv.
8802 - If a hidden service sends us an END cell, do not consider
8803 retrying the connection; just close it. Patch from rovv.
8804 - When we made bridge authorities stop serving bridge descriptors over
8805 unencrypted links, we also broke DirPort reachability testing for
8806 bridges. So bridges with a non-zero DirPort were printing spurious
8807 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
8808 - When a relay gets a create cell it can't decrypt (e.g. because it's
8809 using the wrong onion key), we were dropping it and letting the
8810 client time out. Now actually answer with a destroy cell. Fixes
8811 bug 904. Bugfix on 0.0.2pre8.
8812 - Squeeze 2-5% out of client performance (according to oprofile) by
8813 improving the implementation of some policy-manipulation functions.
8815 o Minor bugfixes (on 0.2.1.x):
8816 - Make get_interface_address() function work properly again; stop
8817 guessing the wrong parts of our address as our address.
8818 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
8819 send on that circuit. Otherwise we might violate the proposal-110
8820 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
8822 - When we're sending non-EXTEND cells to the first hop in a circuit,
8823 for example to use an encrypted directory connection, we don't need
8824 to use RELAY_EARLY cells: the first hop knows what kind of cell
8825 it is, and nobody else can even see the cell type. Conserving
8826 RELAY_EARLY cells makes it easier to cannibalize circuits like
8828 - Stop logging nameserver addresses in reverse order.
8829 - If we are retrying a directory download slowly over and over, do
8830 not automatically give up after the 254th failure. Bugfix on
8832 - Resume reporting accurate "stream end" reasons to the local control
8833 port. They were lost in the changes for Proposal 148. Bugfix on
8836 o Deprecated and removed features:
8837 - The old "tor --version --version" command, which would print out
8838 the subversion "Id" of most of the source files, is now removed. It
8839 turned out to be less useful than we'd expected, and harder to
8842 o Code simplifications and refactoring:
8843 - Change our header file guard macros to be less likely to conflict
8844 with system headers. Adam Langley noticed that we were conflicting
8845 with log.h on Android.
8846 - Tool-assisted documentation cleanup. Nearly every function or
8847 static variable in Tor should have its own documentation now.
8850 Changes in version 0.2.1.9-alpha - 2008-12-25
8851 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
8853 o New directory authorities:
8854 - gabelmoo (the authority run by Karsten Loesing) now has a new
8858 - Never use a connection with a mismatched address to extend a
8859 circuit, unless that connection is canonical. A canonical
8860 connection is one whose address is authenticated by the router's
8861 identity key, either in a NETINFO cell or in a router descriptor.
8862 - Avoid a possible memory corruption bug when receiving hidden service
8863 descriptors. Bugfix on 0.2.1.6-alpha.
8866 - Fix a logic error that would automatically reject all but the first
8867 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
8868 part of bug 813/868. Bug spotted by coderman.
8869 - When a stream at an exit relay is in state "resolving" or
8870 "connecting" and it receives an "end" relay cell, the exit relay
8871 would silently ignore the end cell and not close the stream. If
8872 the client never closes the circuit, then the exit relay never
8873 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
8875 - When we can't initialize DNS because the network is down, do not
8876 automatically stop Tor from starting. Instead, retry failed
8877 dns_init() every 10 minutes, and change the exit policy to reject
8878 *:* until one succeeds. Fixes bug 691.
8881 - Give a better error message when an overzealous init script says
8882 "sudo -u username tor --user username". Makes Bug 882 easier for
8884 - When a directory authority gives us a new guess for our IP address,
8885 log which authority we used. Hopefully this will help us debug
8886 the recent complaints about bad IP address guesses.
8887 - Detect svn revision properly when we're using git-svn.
8888 - Try not to open more than one descriptor-downloading connection
8889 to an authority at once. This should reduce load on directory
8890 authorities. Fixes bug 366.
8891 - Add cross-certification to newly generated certificates, so that
8892 a signing key is enough information to look up a certificate.
8893 Partial implementation of proposal 157.
8894 - Start serving certificates by <identity digest, signing key digest>
8895 pairs. Partial implementation of proposal 157.
8896 - Clients now never report any stream end reason except 'MISC'.
8897 Implements proposal 148.
8898 - On platforms with a maximum syslog string length, truncate syslog
8899 messages to that length ourselves, rather than relying on the
8900 system to do it for us.
8901 - Optimize out calls to time(NULL) that occur for every IO operation,
8902 or for every cell. On systems where time() is a slow syscall,
8903 this fix will be slightly helpful.
8904 - Exit servers can now answer resolve requests for ip6.arpa addresses.
8905 - When we download a descriptor that we then immediately (as
8906 a directory authority) reject, do not retry downloading it right
8907 away. Should save some bandwidth on authorities. Fix for bug
8908 888. Patch by Sebastian Hahn.
8909 - When a download gets us zero good descriptors, do not notify
8910 Tor that new directory information has arrived.
8911 - Avoid some nasty corner cases in the logic for marking connections
8912 as too old or obsolete or noncanonical for circuits. Partial
8915 o Minor features (controller):
8916 - New CONSENSUS_ARRIVED event to note when a new consensus has
8917 been fetched and validated.
8918 - When we realize that another process has modified our cached
8919 descriptors file, print out a more useful error message rather
8920 than triggering an assertion. Fixes bug 885. Patch from Karsten.
8921 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8922 controllers to prevent SIGHUP from reloading the
8923 configuration. Fixes bug 856.
8926 - Resume using the correct "REASON=" stream when telling the
8927 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
8928 - When a canonical connection appears later in our internal list
8929 than a noncanonical one for a given OR ID, always use the
8930 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8932 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8933 seconds. Warn the user if lower values are given in the
8934 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8935 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8936 user if lower values are given in the configuration. Bugfix on
8937 0.1.1.17-rc. Patch by Sebastian.
8938 - Fix a race condition when freeing keys shared between main thread
8939 and CPU workers that could result in a memory leak. Bugfix on
8940 0.1.0.1-rc. Fixes bug 889.
8942 o Minor bugfixes (hidden services):
8943 - Do not throw away existing introduction points on SIGHUP (bugfix on
8944 0.0.6pre1); also, do not stall hidden services because we're
8945 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
8946 by John Brooks. Patch by Karsten. Fixes bug 874.
8947 - Fix a memory leak when we decline to add a v2 rendezvous
8948 descriptor to the cache because we already had a v0 descriptor
8949 with the same ID. Bugfix on 0.2.0.18-alpha.
8951 o Deprecated and removed features:
8952 - RedirectExits has been removed. It was deprecated since
8954 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8955 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8956 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8958 o Code simplifications and refactoring:
8959 - Rename the confusing or_is_obsolete field to the more appropriate
8960 is_bad_for_new_circs, and move it to or_connection_t where it
8962 - Move edge-only flags from connection_t to edge_connection_t: not
8963 only is this better coding, but on machines of plausible alignment,
8964 it should save 4-8 bytes per connection_t. "Every little bit helps."
8965 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8966 for consistency; keep old option working for backward compatibility.
8967 - Simplify the code for finding connections to use for a circuit.
8970 Changes in version 0.2.1.8-alpha - 2008-12-08
8971 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
8972 builds better on unusual platforms like Solaris and old OS X, and
8973 fixes a variety of other issues.
8976 - New DirPortFrontPage option that takes an html file and publishes
8977 it as "/" on the DirPort. Now relay operators can provide a
8978 disclaimer without needing to set up a separate webserver. There's
8979 a sample disclaimer in contrib/tor-exit-notice.html.
8982 - When the client is choosing entry guards, now it selects at most
8983 one guard from a given relay family. Otherwise we could end up with
8984 all of our entry points into the network run by the same operator.
8985 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
8988 - Fix a DOS opportunity during the voting signature collection process
8989 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8990 - Fix a possible segfault when establishing an exit connection. Bugfix
8994 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
8996 - Made Tor a little less aggressive about deleting expired
8997 certificates. Partial fix for bug 854.
8998 - Stop doing unaligned memory access that generated bus errors on
8999 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
9000 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
9001 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
9002 - Make USR2 log-level switch take effect immediately. Bugfix on
9004 - If one win32 nameserver fails to get added, continue adding the
9005 rest, and don't automatically fail.
9006 - Use fcntl() for locking when flock() is not available. Should fix
9007 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
9008 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
9009 could make gcc generate non-functional binary search code. Bugfix
9011 - Build correctly on platforms without socklen_t.
9012 - Avoid potential crash on internal error during signature collection.
9013 Fixes bug 864. Patch from rovv.
9014 - Do not use C's stdio library for writing to log files. This will
9015 improve logging performance by a minute amount, and will stop
9016 leaking fds when our disk is full. Fixes bug 861.
9017 - Stop erroneous use of O_APPEND in cases where we did not in fact
9018 want to re-seek to the end of a file before every last write().
9019 - Correct handling of possible malformed authority signing key
9020 certificates with internal signature types. Fixes bug 880. Bugfix
9022 - Fix a hard-to-trigger resource leak when logging credential status.
9026 - Directory mirrors no longer fetch the v1 directory or
9027 running-routers files. They are obsolete, and nobody asks for them
9028 anymore. This is the first step to making v1 authorities obsolete.
9030 o Minor features (controller):
9031 - Return circuit purposes in response to GETINFO circuit-status. Fixes
9035 Changes in version 0.2.0.32 - 2008-11-20
9036 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
9037 packages (and maybe other packages) noticed by Theo de Raadt, fixes
9038 a smaller security flaw that might allow an attacker to access local
9039 services, further improves hidden service performance, and fixes a
9040 variety of other issues.
9043 - The "User" and "Group" config options did not clear the
9044 supplementary group entries for the Tor process. The "User" option
9045 is now more robust, and we now set the groups to the specified
9046 user's primary group. The "Group" option is now ignored. For more
9047 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
9048 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
9049 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
9050 - The "ClientDNSRejectInternalAddresses" config option wasn't being
9051 consistently obeyed: if an exit relay refuses a stream because its
9052 exit policy doesn't allow it, we would remember what IP address
9053 the relay said the destination address resolves to, even if it's
9054 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
9057 - Fix a DOS opportunity during the voting signature collection process
9058 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
9060 o Major bugfixes (hidden services):
9061 - When fetching v0 and v2 rendezvous service descriptors in parallel,
9062 we were failing the whole hidden service request when the v0
9063 descriptor fetch fails, even if the v2 fetch is still pending and
9064 might succeed. Similarly, if the last v2 fetch fails, we were
9065 failing the whole hidden service request even if a v0 fetch is
9066 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
9067 - When extending a circuit to a hidden service directory to upload a
9068 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
9069 requests failed, because the router descriptor has not been
9070 downloaded yet. In these cases, do not attempt to upload the
9071 rendezvous descriptor, but wait until the router descriptor is
9072 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
9073 descriptor from a hidden service directory for which the router
9074 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
9078 - Fix several infrequent memory leaks spotted by Coverity.
9079 - When testing for libevent functions, set the LDFLAGS variable
9080 correctly. Found by Riastradh.
9081 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
9082 bootstrapping with tunneled directory connections. Bugfix on
9083 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
9084 - When asked to connect to A.B.exit:80, if we don't know the IP for A
9085 and we know that server B rejects most-but-not all connections to
9086 port 80, we would previously reject the connection. Now, we assume
9087 the user knows what they were asking for. Fixes bug 752. Bugfix
9088 on 0.0.9rc5. Diagnosed by BarkerJr.
9089 - If we overrun our per-second write limits a little, count this as
9090 having used up our write allocation for the second, and choke
9091 outgoing directory writes. Previously, we had only counted this when
9092 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
9093 Bugfix on 0.2.0.x (??).
9094 - Remove the old v2 directory authority 'lefkada' from the default
9095 list. It has been gone for many months.
9096 - Stop doing unaligned memory access that generated bus errors on
9097 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
9098 - Make USR2 log-level switch take effect immediately. Bugfix on
9101 o Minor bugfixes (controller):
9102 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
9103 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
9106 Changes in version 0.2.1.7-alpha - 2008-11-08
9107 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
9108 packages (and maybe other packages) noticed by Theo de Raadt, fixes
9109 a smaller security flaw that might allow an attacker to access local
9110 services, adds better defense against DNS poisoning attacks on exit
9111 relays, further improves hidden service performance, and fixes a
9112 variety of other issues.
9115 - The "ClientDNSRejectInternalAddresses" config option wasn't being
9116 consistently obeyed: if an exit relay refuses a stream because its
9117 exit policy doesn't allow it, we would remember what IP address
9118 the relay said the destination address resolves to, even if it's
9119 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
9120 - The "User" and "Group" config options did not clear the
9121 supplementary group entries for the Tor process. The "User" option
9122 is now more robust, and we now set the groups to the specified
9123 user's primary group. The "Group" option is now ignored. For more
9124 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
9125 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
9126 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
9127 - Do not use or believe expired v3 authority certificates. Patch
9128 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
9131 - Now NodeFamily and MyFamily config options allow spaces in
9132 identity fingerprints, so it's easier to paste them in.
9133 Suggested by Lucky Green.
9134 - Implement the 0x20 hack to better resist DNS poisoning: set the
9135 case on outgoing DNS requests randomly, and reject responses that do
9136 not match the case correctly. This logic can be disabled with the
9137 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
9138 of servers that do not reliably preserve case in replies. See
9139 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
9141 - Preserve case in replies to DNSPort requests in order to support
9142 the 0x20 hack for resisting DNS poisoning attacks.
9144 o Hidden service performance improvements:
9145 - When the client launches an introduction circuit, retry with a
9146 new circuit after 30 seconds rather than 60 seconds.
9147 - Launch a second client-side introduction circuit in parallel
9148 after a delay of 15 seconds (based on work by Christian Wilms).
9149 - Hidden services start out building five intro circuits rather
9150 than three, and when the first three finish they publish a service
9151 descriptor using those. Now we publish our service descriptor much
9152 faster after restart.
9155 - Minor fix in the warning messages when you're having problems
9156 bootstrapping; also, be more forgiving of bootstrap problems when
9157 we're still making incremental progress on a given bootstrap phase.
9158 - When we're choosing an exit node for a circuit, and we have
9159 no pending streams, choose a good general exit rather than one that
9160 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
9161 - Send a valid END cell back when a client tries to connect to a
9162 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
9163 840. Patch from rovv.
9164 - If a broken client asks a non-exit router to connect somewhere,
9165 do not even do the DNS lookup before rejecting the connection.
9166 Fixes another case of bug 619. Patch from rovv.
9167 - Fix another case of assuming, when a specific exit is requested,
9168 that we know more than the user about what hosts it allows.
9169 Fixes another case of bug 752. Patch from rovv.
9170 - Check which hops rendezvous stream cells are associated with to
9171 prevent possible guess-the-streamid injection attacks from
9172 intermediate hops. Fixes another case of bug 446. Based on patch
9174 - Avoid using a negative right-shift when comparing 32-bit
9175 addresses. Possible fix for bug 845 and bug 811.
9176 - Make the assert_circuit_ok() function work correctly on circuits that
9177 have already been marked for close.
9178 - Fix read-off-the-end-of-string error in unit tests when decoding
9179 introduction points.
9180 - Fix uninitialized size field for memory area allocation: may improve
9181 memory performance during directory parsing.
9182 - Treat duplicate certificate fetches as failures, so that we do
9183 not try to re-fetch an expired certificate over and over and over.
9184 - Do not say we're fetching a certificate when we'll in fact skip it
9185 because of a pending download.
9188 Changes in version 0.2.1.6-alpha - 2008-09-30
9189 Tor 0.2.1.6-alpha further improves performance and robustness of
9190 hidden services, starts work on supporting per-country relay selection,
9191 and fixes a variety of smaller issues.
9194 - Implement proposal 121: make it possible to build hidden services
9195 that only certain clients are allowed to connect to. This is
9196 enforced at several points, so that unauthorized clients are unable
9197 to send INTRODUCE cells to the service, or even (depending on the
9198 type of authentication) to learn introduction points. This feature
9199 raises the bar for certain kinds of active attacks against hidden
9200 services. Code by Karsten Loesing.
9201 - Relays now store and serve v2 hidden service descriptors by default,
9202 i.e., the new default value for HidServDirectoryV2 is 1. This is
9203 the last step in proposal 114, which aims to make hidden service
9204 lookups more reliable.
9205 - Start work to allow node restrictions to include country codes. The
9206 syntax to exclude nodes in a country with country code XX is
9207 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
9208 refinement to decide what config options should take priority if
9209 you ask to both use a particular node and exclude it.
9210 - Allow ExitNodes list to include IP ranges and country codes, just
9211 like the Exclude*Nodes lists. Patch from Robert Hogan.
9214 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
9215 Tor to fail to start if you had it configured to use a bridge
9216 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
9217 - When extending a circuit to a hidden service directory to upload a
9218 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
9219 requests failed, because the router descriptor had not been
9220 downloaded yet. In these cases, we now wait until the router
9221 descriptor is downloaded, and then retry. Likewise, clients
9222 now skip over a hidden service directory if they don't yet have
9223 its router descriptor, rather than futilely requesting it and
9224 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
9226 - When fetching v0 and v2 rendezvous service descriptors in parallel,
9227 we were failing the whole hidden service request when the v0
9228 descriptor fetch fails, even if the v2 fetch is still pending and
9229 might succeed. Similarly, if the last v2 fetch fails, we were
9230 failing the whole hidden service request even if a v0 fetch is
9231 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
9232 - DNS replies need to have names matching their requests, but
9233 these names should be in the questions section, not necessarily
9234 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
9237 - Update to the "September 1 2008" ip-to-country file.
9238 - Allow ports 465 and 587 in the default exit policy again. We had
9239 rejected them in 0.1.0.15, because back in 2005 they were commonly
9240 misconfigured and ended up as spam targets. We hear they are better
9241 locked down these days.
9242 - Use a lockfile to make sure that two Tor processes are not
9243 simultaneously running with the same datadir.
9244 - Serve the latest v3 networkstatus consensus via the control
9245 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
9246 - Better logging about stability/reliability calculations on directory
9248 - Drop the requirement to have an open dir port for storing and
9249 serving v2 hidden service descriptors.
9250 - Directory authorities now serve a /tor/dbg-stability.txt URL to
9251 help debug WFU and MTBF calculations.
9252 - Implement most of Proposal 152: allow specialized servers to permit
9253 single-hop circuits, and clients to use those servers to build
9254 single-hop circuits when using a specialized controller. Patch
9255 from Josh Albrecht. Resolves feature request 768.
9256 - Add a -p option to tor-resolve for specifying the SOCKS port: some
9257 people find host:port too confusing.
9258 - Make TrackHostExit mappings expire a while after their last use, not
9259 after their creation. Patch from Robert Hogan.
9260 - Provide circuit purposes along with circuit events to the controller.
9263 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
9265 - Fixed some memory leaks -- some quite frequent, some almost
9266 impossible to trigger -- based on results from Coverity.
9267 - When testing for libevent functions, set the LDFLAGS variable
9268 correctly. Found by Riastradh.
9269 - Fix an assertion bug in parsing policy-related options; possible fix
9271 - Catch and report a few more bootstrapping failure cases when Tor
9272 fails to establish a TCP connection. Cleanup on 0.2.1.x.
9273 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
9274 bootstrapping with tunneled directory connections. Bugfix on
9275 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
9276 - When asked to connect to A.B.exit:80, if we don't know the IP for A
9277 and we know that server B rejects most-but-not all connections to
9278 port 80, we would previously reject the connection. Now, we assume
9279 the user knows what they were asking for. Fixes bug 752. Bugfix
9280 on 0.0.9rc5. Diagnosed by BarkerJr.
9281 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
9282 service directories if they have no advertised dir port. Bugfix
9284 - If we overrun our per-second write limits a little, count this as
9285 having used up our write allocation for the second, and choke
9286 outgoing directory writes. Previously, we had only counted this when
9287 we had met our limits precisely. Fixes bug 824. Patch by rovv.
9288 Bugfix on 0.2.0.x (??).
9289 - Avoid a "0 divided by 0" calculation when calculating router uptime
9290 at directory authorities. Bugfix on 0.2.0.8-alpha.
9291 - Make DNS resolved controller events into "CLOSED", not
9292 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
9294 - Fix a bug where an unreachable relay would establish enough
9295 reachability testing circuits to do a bandwidth test -- if
9296 we already have a connection to the middle hop of the testing
9297 circuit, then it could establish the last hop by using the existing
9298 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
9299 circuits no longer use entry guards in 0.2.1.3-alpha.
9300 - If we have correct permissions on $datadir, we complain to stdout
9301 and fail to start. But dangerous permissions on
9302 $datadir/cached-status/ would cause us to open a log and complain
9303 there. Now complain to stdout and fail to start in both cases. Fixes
9304 bug 820, reported by seeess.
9305 - Remove the old v2 directory authority 'lefkada' from the default
9306 list. It has been gone for many months.
9308 o Code simplifications and refactoring:
9309 - Revise the connection_new functions so that a more typesafe variant
9310 exists. This will work better with Coverity, and let us find any
9311 actual mistakes we're making here.
9312 - Refactor unit testing logic so that dmalloc can be used sensibly
9313 with unit tests to check for memory leaks.
9314 - Move all hidden-service related fields from connection and circuit
9315 structure to substructures: this way they won't eat so much memory.
9318 Changes in version 0.2.0.31 - 2008-09-03
9319 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
9320 a big bug we're seeing where in rare cases traffic from one Tor stream
9321 gets mixed into another stream, and fixes a variety of smaller issues.
9324 - Make sure that two circuits can never exist on the same connection
9325 with the same circuit ID, even if one is marked for close. This
9326 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
9327 - Relays now reject risky extend cells: if the extend cell includes
9328 a digest of all zeroes, or asks to extend back to the relay that
9329 sent the extend cell, tear down the circuit. Ideas suggested
9331 - If not enough of our entry guards are available so we add a new
9332 one, we might use the new one even if it overlapped with the
9333 current circuit's exit relay (or its family). Anonymity bugfix
9334 pointed out by rovv.
9337 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
9338 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
9339 - Correctly detect the presence of the linux/netfilter_ipv4.h header
9340 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
9341 - Pick size of default geoip filename string correctly on windows.
9342 Fixes bug 806. Bugfix on 0.2.0.30.
9343 - Make the autoconf script accept the obsolete --with-ssl-dir
9344 option as an alias for the actually-working --with-openssl-dir
9345 option. Fix the help documentation to recommend --with-openssl-dir.
9346 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
9347 - When using the TransPort option on OpenBSD, and using the User
9348 option to change UID and drop privileges, make sure to open
9349 /dev/pf before dropping privileges. Fixes bug 782. Patch from
9350 Christopher Davis. Bugfix on 0.1.2.1-alpha.
9351 - Try to attach connections immediately upon receiving a RENDEZVOUS2
9352 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
9353 on the client side when connecting to a hidden service. Bugfix
9354 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
9355 - When closing an application-side connection because its circuit is
9356 getting torn down, generate the stream event correctly. Bugfix on
9357 0.1.2.x. Anonymous patch.
9360 Changes in version 0.2.1.5-alpha - 2008-08-31
9361 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
9362 in a lot of the infrastructure for adding authorization to hidden
9363 services, lays the groundwork for having clients read their load
9364 balancing information out of the networkstatus consensus rather than
9365 the individual router descriptors, addresses two potential anonymity
9366 issues, and fixes a variety of smaller issues.
9369 - Convert many internal address representations to optionally hold
9371 - Generate and accept IPv6 addresses in many protocol elements.
9372 - Make resolver code handle nameservers located at ipv6 addresses.
9373 - Begin implementation of proposal 121 ("Client authorization for
9374 hidden services"): configure hidden services with client
9375 authorization, publish descriptors for them, and configure
9376 authorization data for hidden services at clients. The next
9377 step is to actually access hidden services that perform client
9379 - More progress toward proposal 141: Network status consensus
9380 documents and votes now contain bandwidth information for each
9381 router and a summary of that router's exit policy. Eventually this
9382 will be used by clients so that they do not have to download every
9383 known descriptor before building circuits.
9385 o Major bugfixes (on 0.2.0.x and before):
9386 - When sending CREATED cells back for a given circuit, use a 64-bit
9387 connection ID to find the right connection, rather than an addr:port
9388 combination. Now that we can have multiple OR connections between
9389 the same ORs, it is no longer possible to use addr:port to uniquely
9390 identify a connection.
9391 - Relays now reject risky extend cells: if the extend cell includes
9392 a digest of all zeroes, or asks to extend back to the relay that
9393 sent the extend cell, tear down the circuit. Ideas suggested
9395 - If not enough of our entry guards are available so we add a new
9396 one, we might use the new one even if it overlapped with the
9397 current circuit's exit relay (or its family). Anonymity bugfix
9398 pointed out by rovv.
9401 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
9402 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
9403 - When using the TransPort option on OpenBSD, and using the User
9404 option to change UID and drop privileges, make sure to open /dev/pf
9405 before dropping privileges. Fixes bug 782. Patch from Christopher
9406 Davis. Bugfix on 0.1.2.1-alpha.
9407 - Correctly detect the presence of the linux/netfilter_ipv4.h header
9408 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
9409 - Add a missing safe_str() call for a debug log message.
9410 - Use 64 bits instead of 32 bits for connection identifiers used with
9411 the controller protocol, to greatly reduce risk of identifier reuse.
9412 - Make the autoconf script accept the obsolete --with-ssl-dir
9413 option as an alias for the actually-working --with-openssl-dir
9414 option. Fix the help documentation to recommend --with-openssl-dir.
9415 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
9418 - Rate-limit too-many-sockets messages: when they happen, they happen
9419 a lot. Resolves bug 748.
9420 - Resist DNS poisoning a little better by making sure that names in
9421 answer sections match.
9422 - Print the SOCKS5 error message string as well as the error code
9423 when a tor-resolve request fails. Patch from Jacob.
9426 Changes in version 0.2.1.4-alpha - 2008-08-04
9427 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
9430 - The address part of exit policies was not correctly written
9431 to router descriptors. This generated router descriptors that failed
9432 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
9434 - Tor triggered a false assert when extending a circuit to a relay
9435 but we already have a connection open to that relay. Noticed by
9436 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
9439 - Fix a hidden service logging bug: in some edge cases, the router
9440 descriptor of a previously picked introduction point becomes
9441 obsolete and we need to give up on it rather than continually
9442 complaining that it has become obsolete. Observed by xiando. Bugfix
9446 - Take out the TestVia config option, since it was a workaround for
9447 a bug that was fixed in Tor 0.1.1.21.
9450 Changes in version 0.2.1.3-alpha - 2008-08-03
9451 Tor 0.2.1.3-alpha implements most of the pieces to prevent
9452 infinite-length circuit attacks (see proposal 110); fixes a bug that
9453 might cause exit relays to corrupt streams they send back; allows
9454 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
9455 ExcludeExitNodes config options; and fixes a big pile of bugs.
9457 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
9458 - Send a bootstrap problem "warn" event on the first problem if the
9459 reason is NO_ROUTE (that is, our network is down).
9462 - Implement most of proposal 110: The first K cells to be sent
9463 along a circuit are marked as special "early" cells; only K "early"
9464 cells will be allowed. Once this code is universal, we can block
9465 certain kinds of DOS attack by requiring that EXTEND commands must
9466 be sent using an "early" cell.
9469 - Try to attach connections immediately upon receiving a RENDEZVOUS2
9470 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
9471 on the client side when connecting to a hidden service. Bugfix
9472 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
9473 - Ensure that two circuits can never exist on the same connection
9474 with the same circuit ID, even if one is marked for close. This
9475 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
9478 - When relays do their initial bandwidth measurement, don't limit
9479 to just our entry guards for the test circuits. Otherwise we tend
9480 to have multiple test circuits going through a single entry guard,
9481 which makes our bandwidth test less accurate. Fixes part of bug 654;
9482 patch contributed by Josh Albrecht.
9483 - Add an ExcludeExitNodes option so users can list a set of nodes
9484 that should be be excluded from the exit node position, but
9485 allowed elsewhere. Implements proposal 151.
9486 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
9487 ExcludeNodes and ExcludeExitNodes lists.
9488 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
9489 be more efficient. Formerly it was quadratic in the number of
9490 servers; now it should be linear. Fixes bug 509.
9491 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
9492 and n_conn_id_digest fields into a separate structure that's
9493 only needed when the circuit has not yet attached to an n_conn.
9496 - Change the contrib/tor.logrotate script so it makes the new
9497 logs as "_tor:_tor" rather than the default, which is generally
9498 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
9499 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
9500 warnings (occasionally), but it can also cause the compiler to
9501 eliminate error-checking code. Suggested by Peter Gutmann.
9502 - When a hidden service is giving up on an introduction point candidate
9503 that was not included in the last published rendezvous descriptor,
9504 don't reschedule publication of the next descriptor. Fixes bug 763.
9506 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
9507 HiddenServiceExcludeNodes as obsolete: they never worked properly,
9508 and nobody claims to be using them. Fixes bug 754. Bugfix on
9509 0.1.0.1-rc. Patch from Christian Wilms.
9510 - Fix a small alignment and memory-wasting bug on buffer chunks.
9513 o Minor bugfixes (controller):
9514 - When closing an application-side connection because its circuit
9515 is getting torn down, generate the stream event correctly.
9516 Bugfix on 0.1.2.x. Anonymous patch.
9519 - Remove all backward-compatibility code to support relays running
9520 versions of Tor so old that they no longer work at all on the
9524 Changes in version 0.2.0.30 - 2008-07-15
9526 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
9527 warnings (occasionally), but it can also cause the compiler to
9528 eliminate error-checking code. Suggested by Peter Gutmann.
9531 Changes in version 0.2.0.29-rc - 2008-07-08
9532 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
9533 hidden-service performance bugs, and fixes a bunch of smaller bugs.
9536 - If you have more than one bridge but don't know their keys,
9537 you would only launch a request for the descriptor of the first one
9538 on your list. (Tor considered launching requests for the others, but
9539 found that it already had a connection on the way for $0000...0000
9540 so it didn't open another.) Bugfix on 0.2.0.x.
9541 - If you have more than one bridge but don't know their keys, and the
9542 connection to one of the bridges failed, you would cancel all
9543 pending bridge connections. (After all, they all have the same
9544 digest.) Bugfix on 0.2.0.x.
9545 - When a hidden service was trying to establish an introduction point,
9546 and Tor had built circuits preemptively for such purposes, we
9547 were ignoring all the preemptive circuits and launching a new one
9548 instead. Bugfix on 0.2.0.14-alpha.
9549 - When a hidden service was trying to establish an introduction point,
9550 and Tor *did* manage to reuse one of the preemptively built
9551 circuits, it didn't correctly remember which one it used,
9552 so it asked for another one soon after, until there were no
9553 more preemptive circuits, at which point it launched one from
9554 scratch. Bugfix on 0.0.9.x.
9555 - Make directory servers include the X-Your-Address-Is: http header in
9556 their responses even for begin_dir conns. Now clients who only
9557 ever use begin_dir connections still have a way to learn their IP
9558 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
9561 - Fix a macro/CPP interaction that was confusing some compilers:
9562 some GCCs don't like #if/#endif pairs inside macro arguments.
9564 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
9565 Fixes bug 704; fix from Steven Murdoch.
9566 - When opening /dev/null in finish_daemonize(), do not pass the
9567 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
9568 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
9569 - Correctly detect transparent proxy support on Linux hosts that
9570 require in.h to be included before netfilter_ipv4.h. Patch
9572 - Disallow session resumption attempts during the renegotiation
9573 stage of the v2 handshake protocol. Clients should never be trying
9574 session resumption at this point, but apparently some did, in
9575 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
9576 found by Geoff Goodell.
9579 Changes in version 0.2.1.2-alpha - 2008-06-20
9580 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
9581 make it easier to set up your own private Tor network; fixes several
9582 big bugs with using more than one bridge relay; fixes a big bug with
9583 offering hidden services quickly after Tor starts; and uses a better
9584 API for reporting potential bootstrapping problems to the controller.
9587 - New TestingTorNetwork config option to allow adjustment of
9588 previously constant values that, while reasonable, could slow
9589 bootstrapping. Implements proposal 135. Patch from Karsten.
9592 - If you have more than one bridge but don't know their digests,
9593 you would only learn a request for the descriptor of the first one
9594 on your list. (Tor considered launching requests for the others, but
9595 found that it already had a connection on the way for $0000...0000
9596 so it didn't open another.) Bugfix on 0.2.0.x.
9597 - If you have more than one bridge but don't know their digests,
9598 and the connection to one of the bridges failed, you would cancel
9599 all pending bridge connections. (After all, they all have the
9600 same digest.) Bugfix on 0.2.0.x.
9601 - When establishing a hidden service, introduction points that
9602 originate from cannibalized circuits are completely ignored and not
9603 included in rendezvous service descriptors. This might be another
9604 reason for delay in making a hidden service available. Bugfix
9605 from long ago (0.0.9.x?)
9608 - Allow OpenSSL to use dynamic locks if it wants.
9609 - When building a consensus, do not include routers that are down.
9610 This will cut down 30% to 40% on consensus size. Implements
9612 - In directory authorities' approved-routers files, allow
9613 fingerprints with or without space.
9614 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
9615 controller can query our current bootstrap state in case it attaches
9616 partway through and wants to catch up.
9617 - Send an initial "Starting" bootstrap status event, so we have a
9618 state to start out in.
9621 - Asking for a conditional consensus at .../consensus/<fingerprints>
9622 would crash a dirserver if it did not already have a
9623 consensus. Bugfix on 0.2.1.1-alpha.
9624 - Clean up some macro/CPP interactions: some GCC versions don't like
9625 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
9628 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
9629 - Directory authorities shouldn't complain about bootstrapping
9630 problems just because they do a lot of reachability testing and
9631 some of the connection attempts fail.
9632 - Start sending "count" and "recommendation" key/value pairs in
9633 bootstrap problem status events, so the controller can hear about
9634 problems even before Tor decides they're worth reporting for sure.
9635 - If you're using bridges, generate "bootstrap problem" warnings
9636 as soon as you run out of working bridges, rather than waiting
9637 for ten failures -- which will never happen if you have less than
9639 - If we close our OR connection because there's been a circuit
9640 pending on it for too long, we were telling our bootstrap status
9641 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
9644 Changes in version 0.2.1.1-alpha - 2008-06-13
9645 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
9646 were making the Tor process bloat especially on Linux; makes our TLS
9647 handshake blend in better; sends "bootstrap phase" status events to
9648 the controller, so it can keep the user informed of progress (and
9649 problems) fetching directory information and establishing circuits;
9650 and adds a variety of smaller features.
9653 - More work on making our TLS handshake blend in: modify the list
9654 of ciphers advertised by OpenSSL in client mode to even more
9655 closely resemble a common web browser. We cheat a little so that
9656 we can advertise ciphers that the locally installed OpenSSL doesn't
9658 - Start sending "bootstrap phase" status events to the controller,
9659 so it can keep the user informed of progress fetching directory
9660 information and establishing circuits. Also inform the controller
9661 if we think we're stuck at a particular bootstrap phase. Implements
9663 - Resume using OpenSSL's RAND_poll() for better (and more portable)
9664 cross-platform entropy collection again. We used to use it, then
9665 stopped using it because of a bug that could crash systems that
9666 called RAND_poll when they had a lot of fds open. It looks like the
9667 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
9668 at startup, and to call RAND_poll() when we reseed later only if
9669 we have a non-buggy OpenSSL version.
9672 - When we choose to abandon a new entry guard because we think our
9673 older ones might be better, close any circuits pending on that
9674 new entry guard connection. This fix should make us recover much
9675 faster when our network is down and then comes back. Bugfix on
9676 0.1.2.8-beta; found by lodger.
9678 o Memory fixes and improvements:
9679 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
9680 to avoid unused RAM in buffer chunks and memory pools.
9681 - Speed up parsing and cut down on memory fragmentation by using
9682 stack-style allocations for parsing directory objects. Previously,
9683 this accounted for over 40% of allocations from within Tor's code
9684 on a typical directory cache.
9685 - Use a Bloom filter rather than a digest-based set to track which
9686 descriptors we need to keep around when we're cleaning out old
9687 router descriptors. This speeds up the computation significantly,
9688 and may reduce fragmentation.
9689 - Reduce the default smartlist size from 32 to 16; it turns out that
9690 most smartlists hold around 8-12 elements tops.
9691 - Make dumpstats() log the fullness and size of openssl-internal
9693 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
9694 patch to their OpenSSL, turn it on to save memory on servers. This
9695 patch will (with any luck) get included in a mainline distribution
9697 - Never use OpenSSL compression: it wastes RAM and CPU trying to
9698 compress cells, which are basically all encrypted, compressed,
9702 - Stop reloading the router list from disk for no reason when we
9703 run out of reachable directory mirrors. Once upon a time reloading
9704 it would set the 'is_running' flag back to 1 for them. It hasn't
9705 done that for a long time.
9706 - In very rare situations new hidden service descriptors were
9707 published earlier than 30 seconds after the last change to the
9708 service. (We currently think that a hidden service descriptor
9709 that's been stable for 30 seconds is worth publishing.)
9712 - Allow separate log levels to be configured for different logging
9713 domains. For example, this allows one to log all notices, warnings,
9714 or errors, plus all memory management messages of level debug or
9715 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
9716 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
9717 and stop using a warning that had become unfixably verbose under
9719 - New --hush command-line option similar to --quiet. While --quiet
9720 disables all logging to the console on startup, --hush limits the
9721 output to messages of warning and error severity.
9722 - Servers support a new URL scheme for consensus downloads that
9723 allows the client to specify which authorities are trusted.
9724 The server then only sends the consensus if the client will trust
9725 it. Otherwise a 404 error is sent back. Clients use this
9726 new scheme when the server supports it (meaning it's running
9727 0.2.1.1-alpha or later). Implements proposal 134.
9728 - New configure/torrc options (--enable-geoip-stats,
9729 DirRecordUsageByCountry) to record how many IPs we've served
9730 directory info to in each country code, how many status documents
9731 total we've sent to each country code, and what share of the total
9732 directory requests we should expect to see.
9733 - Use the TLS1 hostname extension to more closely resemble browser
9735 - Lots of new unit tests.
9736 - Add a macro to implement the common pattern of iterating through
9737 two parallel lists in lockstep.
9740 Changes in version 0.2.0.28-rc - 2008-06-13
9741 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
9742 performance bug, and fixes a bunch of smaller bugs.
9745 - Fix a bug where, when we were choosing the 'end stream reason' to
9746 put in our relay end cell that we send to the exit relay, Tor
9747 clients on Windows were sometimes sending the wrong 'reason'. The
9748 anonymity problem is that exit relays may be able to guess whether
9749 the client is running Windows, thus helping partition the anonymity
9750 set. Down the road we should stop sending reasons to exit relays,
9751 or otherwise prevent future versions of this bug.
9754 - While setting up a hidden service, some valid introduction circuits
9755 were overlooked and abandoned. This might be the reason for
9756 the long delay in making a hidden service available. Bugfix on
9760 - Update to the "June 9 2008" ip-to-country file.
9761 - Run 'make test' as part of 'make dist', so we stop releasing so
9762 many development snapshots that fail their unit tests.
9765 - When we're checking if we have enough dir info for each relay
9766 to begin establishing circuits, make sure that we actually have
9767 the descriptor listed in the consensus, not just any descriptor.
9769 - Bridge relays no longer print "xx=0" in their extrainfo document
9770 for every single country code in the geoip db. Bugfix on
9772 - Only warn when we fail to load the geoip file if we were planning to
9773 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
9774 - If we change our MaxAdvertisedBandwidth and then reload torrc,
9775 Tor won't realize it should publish a new relay descriptor. Fixes
9776 bug 688, reported by mfr. Bugfix on 0.1.2.x.
9777 - When we haven't had any application requests lately, don't bother
9778 logging that we have expired a bunch of descriptors. Bugfix
9780 - Make relay cells written on a connection count as non-padding when
9781 tracking how long a connection has been in use. Bugfix on
9782 0.2.0.1-alpha. Spotted by lodger.
9783 - Fix unit tests in 0.2.0.27-rc.
9784 - Fix compile on Windows.
9787 Changes in version 0.2.0.27-rc - 2008-06-03
9788 Tor 0.2.0.27-rc adds a few features we left out of the earlier
9789 release candidates. In particular, we now include an IP-to-country
9790 GeoIP database, so controllers can easily look up what country a
9791 given relay is in, and so bridge relays can give us some sanitized
9792 summaries about which countries are making use of bridges. (See proposal
9793 126-geoip-fetching.txt for details.)
9796 - Include an IP-to-country GeoIP file in the tarball, so bridge
9797 relays can report sanitized summaries of the usage they're seeing.
9800 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
9801 Robert Hogan. Fixes the first part of bug 681.
9802 - Make bridge authorities never serve extrainfo docs.
9803 - Add support to detect Libevent versions in the 1.4.x series
9805 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
9806 - Include a new contrib/tor-exit-notice.html file that exit relay
9807 operators can put on their website to help reduce abuse queries.
9810 - When tunneling an encrypted directory connection, and its first
9811 circuit fails, do not leave it unattached and ask the controller
9812 to deal. Fixes the second part of bug 681.
9813 - Make bridge authorities correctly expire old extrainfo documents
9817 Changes in version 0.2.0.26-rc - 2008-05-13
9818 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
9819 in Debian's OpenSSL packages. All users running any 0.2.0.x version
9820 should upgrade, whether they're running Debian or not.
9822 o Major security fixes:
9823 - Use new V3 directory authority keys on the tor26, gabelmoo, and
9824 moria1 V3 directory authorities. The old keys were generated with
9825 a vulnerable version of Debian's OpenSSL package, and must be
9826 considered compromised. Other authorities' keys were not generated
9827 with an affected version of OpenSSL.
9830 - List authority signatures as "unrecognized" based on DirServer
9831 lines, not on cert cache. Bugfix on 0.2.0.x.
9834 - Add a new V3AuthUseLegacyKey option to make it easier for
9835 authorities to change their identity keys if they have to.
9838 Changes in version 0.2.0.25-rc - 2008-04-23
9839 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
9842 - Remember to initialize threading before initializing logging.
9843 Otherwise, many BSD-family implementations will crash hard on
9844 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
9847 - Authorities correctly free policies on bad servers on
9848 exit. Fixes bug 672. Bugfix on 0.2.0.x.
9851 Changes in version 0.2.0.24-rc - 2008-04-22
9852 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
9853 v3 directory authority, makes relays with dynamic IP addresses and no
9854 DirPort notice more quickly when their IP address changes, fixes a few
9855 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
9857 o New directory authorities:
9858 - Take lefkada out of the list of v3 directory authorities, since
9859 it has been down for months.
9860 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
9864 - Detect address changes more quickly on non-directory mirror
9865 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
9867 o Minor features (security):
9868 - Reject requests for reverse-dns lookup of names that are in
9869 a private address space. Patch from lodger.
9870 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
9873 o Minor bugfixes (crashes):
9874 - Avoid a rare assert that can trigger when Tor doesn't have much
9875 directory information yet and it tries to fetch a v2 hidden
9876 service descriptor. Fixes bug 651, reported by nwf.
9877 - Initialize log mutex before initializing dmalloc. Otherwise,
9878 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
9879 - Use recursive pthread mutexes in order to avoid deadlock when
9880 logging debug-level messages to a controller. Bug spotted by nwf,
9881 bugfix on 0.2.0.16-alpha.
9883 o Minor bugfixes (resource management):
9884 - Keep address policies from leaking memory: start their refcount
9885 at 1, not 2. Bugfix on 0.2.0.16-alpha.
9886 - Free authority certificates on exit, so they don't look like memory
9887 leaks. Bugfix on 0.2.0.19-alpha.
9888 - Free static hashtables for policy maps and for TLS connections on
9889 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
9890 - Avoid allocating extra space when computing consensuses on 64-bit
9891 platforms. Bug spotted by aakova.
9893 o Minor bugfixes (misc):
9894 - Do not read the configuration file when we've only been told to
9895 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
9896 based on patch from Sebastian Hahn.
9897 - Exit relays that are used as a client can now reach themselves
9898 using the .exit notation, rather than just launching an infinite
9899 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
9900 - When attempting to open a logfile fails, tell us why.
9901 - Fix a dumb bug that was preventing us from knowing that we should
9902 preemptively build circuits to handle expected directory requests.
9903 Fixes bug 660. Bugfix on 0.1.2.x.
9904 - Warn less verbosely about clock skew from netinfo cells from
9905 untrusted sources. Fixes bug 663.
9906 - Make controller stream events for DNS requests more consistent,
9907 by adding "new stream" events for DNS requests, and removing
9908 spurious "stream closed" events" for cached reverse resolves.
9909 Patch from mwenge. Fixes bug 646.
9910 - Correctly notify one-hop connections when a circuit build has
9911 failed. Possible fix for bug 669. Found by lodger.
9914 Changes in version 0.2.0.23-rc - 2008-03-24
9915 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
9916 makes bootstrapping faster if the first directory mirror you contact
9917 is down. The bundles also include the new Vidalia 0.1.2 release.
9920 - When a tunneled directory request is made to a directory server
9921 that's down, notice after 30 seconds rather than 120 seconds. Also,
9922 fail any begindir streams that are pending on it, so they can
9923 retry elsewhere. This was causing multi-minute delays on bootstrap.
9926 Changes in version 0.2.0.22-rc - 2008-03-18
9927 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
9928 enables encrypted directory connections by default for non-relays, fixes
9929 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
9930 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
9933 - Enable encrypted directory connections by default for non-relays,
9934 so censor tools that block Tor directory connections based on their
9935 plaintext patterns will no longer work. This means Tor works in
9936 certain censored countries by default again.
9939 - Make sure servers always request certificates from clients during
9940 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
9941 - Do not enter a CPU-eating loop when a connection is closed in
9942 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
9943 diagnosed by lodger; bugfix on 0.2.0.20-rc.
9944 - Fix assertion failure that could occur when a blocked circuit
9945 became unblocked, and it had pending client DNS requests. Bugfix
9946 on 0.2.0.1-alpha. Fixes bug 632.
9948 o Minor bugfixes (on 0.1.2.x):
9949 - Generate "STATUS_SERVER" events rather than misspelled
9950 "STATUS_SEVER" events. Caught by mwenge.
9951 - When counting the number of bytes written on a TLS connection,
9952 look at the BIO actually used for writing to the network, not
9953 at the BIO used (sometimes) to buffer data for the network.
9954 Looking at different BIOs could result in write counts on the
9955 order of ULONG_MAX. Fixes bug 614.
9956 - On Windows, correctly detect errors when listing the contents of
9957 a directory. Fix from lodger.
9959 o Minor bugfixes (on 0.2.0.x):
9960 - Downgrade "sslv3 alert handshake failure" message to INFO.
9961 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
9962 left BandwidthRate and BandwidthBurst at the default, we would be
9963 silently limited by those defaults. Now raise them to match the
9964 RelayBandwidth* values.
9965 - Fix the SVK version detection logic to work correctly on a branch.
9966 - Make --enable-openbsd-malloc work correctly on Linux with alpha
9967 CPUs. Fixes bug 625.
9968 - Logging functions now check that the passed severity is sane.
9969 - Use proper log levels in the testsuite call of
9970 get_interface_address6().
9971 - When using a nonstandard malloc, do not use the platform values for
9972 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
9973 - Make the openbsd malloc code use 8k pages on alpha CPUs and
9975 - Detect mismatched page sizes when using --enable-openbsd-malloc.
9976 - Avoid double-marked-for-close warning when certain kinds of invalid
9977 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
9978 for bug 617. Bugfix on 0.2.0.1-alpha.
9979 - Make sure that the "NULL-means-reject *:*" convention is followed by
9980 all the policy manipulation functions, avoiding some possible crash
9981 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
9982 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
9983 actually works, and doesn't warn about every single reverse lookup.
9984 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
9987 - Only log guard node status when guard node status has changed.
9988 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9989 make "INFO" 75% less verbose.
9992 Changes in version 0.2.0.21-rc - 2008-03-02
9993 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
9994 makes Tor work well with Vidalia again, fixes a rare assert bug,
9995 and fixes a pair of more minor bugs. The bundles also include Vidalia
9996 0.1.0 and Torbutton 1.1.16.
9999 - The control port should declare that it requires password auth
10000 when HashedControlSessionPassword is set too. Patch from Matt Edman;
10001 bugfix on 0.2.0.20-rc. Fixes bug 615.
10002 - Downgrade assert in connection_buckets_decrement() to a log message.
10003 This may help us solve bug 614, and in any case will make its
10004 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
10005 - We were sometimes miscounting the number of bytes read from the
10006 network, causing our rate limiting to not be followed exactly.
10007 Bugfix on 0.2.0.16-alpha. Reported by lodger.
10010 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
10011 OpenSSL versions should have been working fine. Diagnosis and patch
10012 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
10013 Bugfix on 0.2.0.20-rc.
10016 Changes in version 0.2.0.20-rc - 2008-02-24
10017 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
10018 makes more progress towards normalizing Tor's TLS handshake, makes
10019 hidden services work better again, helps relays bootstrap if they don't
10020 know their IP address, adds optional support for linking in openbsd's
10021 allocator or tcmalloc, allows really fast relays to scale past 15000
10022 sockets, and fixes a bunch of minor bugs reported by Veracode.
10025 - Enable the revised TLS handshake based on the one designed by
10026 Steven Murdoch in proposal 124, as revised in proposal 130. It
10027 includes version negotiation for OR connections as described in
10028 proposal 105. The new handshake is meant to be harder for censors
10029 to fingerprint, and it adds the ability to detect certain kinds of
10030 man-in-the-middle traffic analysis attacks. The version negotiation
10031 feature will allow us to improve Tor's link protocol more safely
10033 - Choose which bridge to use proportional to its advertised bandwidth,
10034 rather than uniformly at random. This should speed up Tor for
10035 bridge users. Also do this for people who set StrictEntryNodes.
10036 - When a TrackHostExits-chosen exit fails too many times in a row,
10037 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
10040 - Resolved problems with (re-)fetching hidden service descriptors.
10041 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
10042 and 0.2.0.19-alpha.
10043 - If we only ever used Tor for hidden service lookups or posts, we
10044 would stop building circuits and start refusing connections after
10045 24 hours, since we falsely believed that Tor was dormant. Reported
10046 by nwf; bugfix on 0.1.2.x.
10047 - Servers that don't know their own IP address should go to the
10048 authorities for their first directory fetch, even if their DirPort
10049 is off or if they don't know they're reachable yet. This will help
10050 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
10051 - When counting the number of open sockets, count not only the number
10052 of sockets we have received from the socket() call, but also
10053 the number we've gotten from accept() and socketpair(). This bug
10054 made us fail to count all sockets that we were using for incoming
10055 connections. Bugfix on 0.2.0.x.
10056 - Fix code used to find strings within buffers, when those strings
10057 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
10058 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
10059 - Add a new __HashedControlSessionPassword option for controllers
10060 to use for one-off session password hashes that shouldn't get
10061 saved to disk by SAVECONF --- Vidalia users were accumulating a
10062 pile of HashedControlPassword lines in their torrc files, one for
10063 each time they had restarted Tor and then clicked Save. Make Tor
10064 automatically convert "HashedControlPassword" to this new option but
10065 only when it's given on the command line. Partial fix for bug 586.
10067 o Minor features (performance):
10068 - Tune parameters for cell pool allocation to minimize amount of
10070 - Add OpenBSD malloc code from phk as an optional malloc
10071 replacement on Linux: some glibc libraries do very poorly
10072 with Tor's memory allocation patterns. Pass
10073 --enable-openbsd-malloc to get the replacement malloc code.
10074 - Add a --with-tcmalloc option to the configure script to link
10075 against tcmalloc (if present). Does not yet search for
10076 non-system include paths.
10077 - Stop imposing an arbitrary maximum on the number of file descriptors
10078 used for busy servers. Bug reported by Olaf Selke; patch from
10081 o Minor features (other):
10082 - When SafeLogging is disabled, log addresses along with all TLS
10084 - When building with --enable-gcc-warnings, check for whether Apple's
10085 warning "-Wshorten-64-to-32" is available.
10086 - Add a --passphrase-fd argument to the tor-gencert command for
10089 o Minor bugfixes (memory leaks and code problems):
10090 - We were leaking a file descriptor if Tor started with a zero-length
10091 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
10092 - Detect size overflow in zlib code. Reported by Justin Ferguson and
10094 - We were comparing the raw BridgePassword entry with a base64'ed
10095 version of it, when handling a "/tor/networkstatus-bridges"
10096 directory request. Now compare correctly. Noticed by Veracode.
10097 - Recover from bad tracked-since value in MTBF-history file.
10098 Should fix bug 537.
10099 - Alter the code that tries to recover from unhandled write
10100 errors, to not try to flush onto a socket that's given us
10101 unhandled errors. Bugfix on 0.1.2.x.
10102 - Make Unix controlsockets work correctly on OpenBSD. Patch from
10103 tup. Bugfix on 0.2.0.3-alpha.
10105 o Minor bugfixes (other):
10106 - If we have an extra-info document for our server, always make
10107 it available on the control port, even if we haven't gotten
10108 a copy of it from an authority yet. Patch from mwenge.
10109 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
10110 - Directory mirrors no longer include a guess at the client's IP
10111 address if the connection appears to be coming from the same /24
10112 network; it was producing too many wrong guesses.
10113 - Make the new hidden service code respect the SafeLogging setting.
10114 Bugfix on 0.2.0.x. Patch from Karsten.
10115 - When starting as an authority, do not overwrite all certificates
10116 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
10117 - If we're trying to flush the last bytes on a connection (for
10118 example, when answering a directory request), reset the
10119 time-to-give-up timeout every time we manage to write something
10120 on the socket. Bugfix on 0.1.2.x.
10121 - Change the behavior of "getinfo status/good-server-descriptor"
10122 so it doesn't return failure when any authority disappears.
10123 - Even though the man page said that "TrackHostExits ." should
10124 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
10125 - Report TLS "zero return" case as a "clean close" and "IO error"
10126 as a "close". Stop calling closes "unexpected closes": existing
10127 Tors don't use SSL_close(), so having a connection close without
10128 the TLS shutdown handshake is hardly unexpected.
10129 - Send NAMESERVER_STATUS messages for a single failed nameserver
10132 o Code simplifications and refactoring:
10133 - Remove the tor_strpartition function: its logic was confused,
10134 and it was only used for one thing that could be implemented far
10138 Changes in version 0.2.0.19-alpha - 2008-02-09
10139 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
10140 handshake, makes path selection for relays more secure and IP address
10141 guessing more robust, and generally fixes a lot of bugs in preparation
10142 for calling the 0.2.0 branch stable.
10145 - Do not include recognizeable strings in the commonname part of
10146 Tor's x509 certificates.
10149 - If we're a relay, avoid picking ourselves as an introduction point,
10150 a rendezvous point, or as the final hop for internal circuits. Bug
10151 reported by taranis and lodger. Bugfix on 0.1.2.x.
10152 - Patch from "Andrew S. Lists" to catch when we contact a directory
10153 mirror at IP address X and he says we look like we're coming from
10154 IP address X. Bugfix on 0.1.2.x.
10156 o Minor features (security):
10157 - Be more paranoid about overwriting sensitive memory on free(),
10158 as a defensive programming tactic to ensure forward secrecy.
10160 o Minor features (directory authority):
10161 - Actually validate the options passed to AuthDirReject,
10162 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
10163 - Reject router descriptors with out-of-range bandwidthcapacity or
10164 bandwidthburst values.
10166 o Minor features (controller):
10167 - Reject controller commands over 1MB in length. This keeps rogue
10168 processes from running us out of memory.
10170 o Minor features (misc):
10171 - Give more descriptive well-formedness errors for out-of-range
10172 hidden service descriptor/protocol versions.
10173 - Make memory debugging information describe more about history
10174 of cell allocation, so we can help reduce our memory use.
10176 o Deprecated features (controller):
10177 - The status/version/num-versioning and status/version/num-concurring
10178 GETINFO options are no longer useful in the v3 directory protocol:
10179 treat them as deprecated, and warn when they're used.
10182 - When our consensus networkstatus has been expired for a while, stop
10183 being willing to build circuits using it. Fixes bug 401. Bugfix
10185 - Directory caches now fetch certificates from all authorities
10186 listed in a networkstatus consensus, even when they do not
10187 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
10188 - When connecting to a bridge without specifying its key, insert
10189 the connection into the identity-to-connection map as soon as
10190 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
10191 - Detect versions of OS X where malloc_good_size() is present in the
10192 library but never actually declared. Resolves bug 587. Bugfix
10194 - Stop incorrectly truncating zlib responses to directory authority
10195 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
10196 - Stop recommending that every server operator send mail to tor-ops.
10197 Resolves bug 597. Bugfix on 0.1.2.x.
10198 - Don't trigger an assert if we start a directory authority with a
10199 private IP address (like 127.0.0.1).
10200 - Avoid possible failures when generating a directory with routers
10201 with over-long versions strings, or too many flags set. Bugfix
10203 - If an attempt to launch a DNS resolve request over the control
10204 port fails because we have overrun the limit on the number of
10205 connections, tell the controller that the request has failed.
10206 - Avoid using too little bandwidth when our clock skips a few
10207 seconds. Bugfix on 0.1.2.x.
10208 - Fix shell error when warning about missing packages in configure
10209 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
10210 - Do not become confused when receiving a spurious VERSIONS-like
10211 cell from a confused v1 client. Bugfix on 0.2.0.x.
10212 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
10213 introduction points for a hidden service have failed. Patch from
10214 Karsten Loesing. Bugfix on 0.2.0.x.
10216 o Code simplifications and refactoring:
10217 - Remove some needless generality from cpuworker code, for improved
10219 - Stop overloading the circuit_t.onionskin field for both "onionskin
10220 from a CREATE cell that we are waiting for a cpuworker to be
10221 assigned" and "onionskin from an EXTEND cell that we are going to
10222 send to an OR as soon as we are connected". Might help with bug 600.
10223 - Add an in-place version of aes_crypt() so that we can avoid doing a
10224 needless memcpy() call on each cell payload.
10227 Changes in version 0.2.0.18-alpha - 2008-01-25
10228 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
10229 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
10230 that can warn or reject connections to ports generally associated with
10231 vulnerable-plaintext protocols.
10233 o New directory authorities:
10234 - Set up dannenberg (run by CCC) as the sixth v3 directory
10238 - Fix a major memory leak when attempting to use the v2 TLS
10239 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
10240 - We accidentally enabled the under-development v2 TLS handshake
10241 code, which was causing log entries like "TLS error while
10242 renegotiating handshake". Disable it again. Resolves bug 590.
10243 - We were computing the wrong Content-Length: header for directory
10244 responses that need to be compressed on the fly, causing clients
10245 asking for those items to always fail. Bugfix on 0.2.0.x; partially
10249 - Avoid going directly to the directory authorities even if you're a
10250 relay, if you haven't found yourself reachable yet or if you've
10251 decided not to advertise your dirport yet. Addresses bug 556.
10252 - If we've gone 12 hours since our last bandwidth check, and we
10253 estimate we have less than 50KB bandwidth capacity but we could
10254 handle more, do another bandwidth test.
10255 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
10256 Tor can warn and/or refuse connections to ports commonly used with
10257 vulnerable-plaintext protocols. Currently we warn on ports 23,
10258 109, 110, and 143, but we don't reject any.
10261 - When we setconf ClientOnly to 1, close any current OR and Dir
10262 listeners. Reported by mwenge.
10263 - When we get a consensus that's been signed by more people than
10264 we expect, don't log about it; it's not a big deal. Reported
10268 - Don't answer "/tor/networkstatus-bridges" directory requests if
10269 the request isn't encrypted.
10270 - Make "ClientOnly 1" config option disable directory ports too.
10271 - Patches from Karsten Loesing to make v2 hidden services more
10272 robust: work even when there aren't enough HSDir relays available;
10273 retry when a v2 rend desc fetch fails; but don't retry if we
10274 already have a usable v0 rend desc.
10277 Changes in version 0.2.0.17-alpha - 2008-01-17
10278 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
10281 - Make the tor-gencert man page get included correctly in the tarball.
10284 Changes in version 0.2.0.16-alpha - 2008-01-17
10285 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
10286 Loesing, and generally cleans up a lot of features and minor bugs.
10288 o New directory authorities:
10289 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
10292 o Major performance improvements:
10293 - Switch our old ring buffer implementation for one more like that
10294 used by free Unix kernels. The wasted space in a buffer with 1mb
10295 of data will now be more like 8k than 1mb. The new implementation
10296 also avoids realloc();realloc(); patterns that can contribute to
10297 memory fragmentation.
10300 - Configuration files now accept C-style strings as values. This
10301 helps encode characters not allowed in the current configuration
10302 file format, such as newline or #. Addresses bug 557.
10303 - Although we fixed bug 539 (where servers would send HTTP status 503
10304 responses _and_ send a body too), there are still servers out
10305 there that haven't upgraded. Therefore, make clients parse such
10306 bodies when they receive them.
10307 - When we're not serving v2 directory information, there is no reason
10308 to actually keep any around. Remove the obsolete files and directory
10309 on startup if they are very old and we aren't going to serve them.
10311 o Minor performance improvements:
10312 - Reference-count and share copies of address policy entries; only 5%
10313 of them were actually distinct.
10314 - Never walk through the list of logs if we know that no log is
10315 interested in a given message.
10318 - When an authority has not signed a consensus, do not try to
10319 download a nonexistent "certificate with key 00000000". Bugfix
10320 on 0.2.0.x. Fixes bug 569.
10321 - Fix a rare assert error when we're closing one of our threads:
10322 use a mutex to protect the list of logs, so we never write to the
10323 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
10324 bug 575, which is kind of the revenge of bug 222.
10325 - Patch from Karsten Loesing to complain less at both the client
10326 and the relay when a relay used to have the HSDir flag but doesn't
10327 anymore, and we try to upload a hidden service descriptor.
10328 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
10330 - Do not try to download missing certificates until we have tried
10331 to check our fallback consensus. Fixes bug 583.
10332 - Make bridges round reported GeoIP stats info up to the nearest
10333 estimate, not down. Now we can distinguish between "0 people from
10334 this country" and "1 person from this country".
10335 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
10336 - Avoid possible segfault if key generation fails in
10337 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
10338 - Avoid segfault in the case where a badly behaved v2 versioning
10339 directory sends a signed networkstatus with missing client-versions.
10341 - Avoid segfaults on certain complex invocations of
10342 router_get_by_hexdigest(). Bugfix on 0.1.2.
10343 - Correct bad index on array access in parse_http_time(). Bugfix
10345 - Fix possible bug in vote generation when server versions are present
10346 but client versions are not.
10347 - Fix rare bug on REDIRECTSTREAM control command when called with no
10348 port set: it could erroneously report an error when none had
10350 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
10351 compressing large objects and find ourselves with more than 4k
10352 left over. Bugfix on 0.2.0.
10353 - Fix a small memory leak when setting up a hidden service.
10354 - Fix a few memory leaks that could in theory happen under bizarre
10356 - Fix an assert if we post a general-purpose descriptor via the
10357 control port but that descriptor isn't mentioned in our current
10358 network consensus. Bug reported by Jon McLachlan; bugfix on
10361 o Minor features (controller):
10362 - Get NS events working again. Patch from tup.
10363 - The GETCONF command now escapes and quotes configuration values
10364 that don't otherwise fit into the torrc file.
10365 - The SETCONF command now handles quoted values correctly.
10367 o Minor features (directory authorities):
10368 - New configuration options to override default maximum number of
10369 servers allowed on a single IP address. This is important for
10370 running a test network on a single host.
10371 - Actually implement the -s option to tor-gencert.
10372 - Add a manual page for tor-gencert.
10374 o Minor features (bridges):
10375 - Bridge authorities no longer serve bridge descriptors over
10376 unencrypted connections.
10378 o Minor features (other):
10379 - Add hidden services and DNSPorts to the list of things that make
10380 Tor accept that it has running ports. Change starting Tor with no
10381 ports from a fatal error to a warning; we might change it back if
10382 this turns out to confuse anybody. Fixes bug 579.
10385 Changes in version 0.1.2.19 - 2008-01-17
10386 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
10387 exit policy a little bit more conservative so it's safer to run an
10388 exit relay on a home system, and fixes a variety of smaller issues.
10391 - Exit policies now reject connections that are addressed to a
10392 relay's public (external) IP address too, unless
10393 ExitPolicyRejectPrivate is turned off. We do this because too
10394 many relays are running nearby to services that trust them based
10395 on network address.
10398 - When the clock jumps forward a lot, do not allow the bandwidth
10399 buckets to become negative. Fixes bug 544.
10400 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
10401 on every successful resolve. Reported by Mike Perry.
10402 - Purge old entries from the "rephist" database and the hidden
10403 service descriptor database even when DirPort is zero.
10404 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
10405 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
10406 crashing or mis-answering these requests.
10407 - When we decide to send a 503 response to a request for servers, do
10408 not then also send the server descriptors: this defeats the whole
10409 purpose. Fixes bug 539.
10412 - Changing the ExitPolicyRejectPrivate setting should cause us to
10413 rebuild our server descriptor.
10414 - Fix handling of hex nicknames when answering controller requests for
10415 networkstatus by name, or when deciding whether to warn about
10416 unknown routers in a config option. (Patch from mwenge.)
10417 - Fix a couple of hard-to-trigger autoconf problems that could result
10418 in really weird results on platforms whose sys/types.h files define
10419 nonstandard integer types.
10420 - Don't try to create the datadir when running --verify-config or
10421 --hash-password. Resolves bug 540.
10422 - If we were having problems getting a particular descriptor from the
10423 directory caches, and then we learned about a new descriptor for
10424 that router, we weren't resetting our failure count. Reported
10426 - Although we fixed bug 539 (where servers would send HTTP status 503
10427 responses _and_ send a body too), there are still servers out there
10428 that haven't upgraded. Therefore, make clients parse such bodies
10429 when they receive them.
10430 - Run correctly on systems where rlim_t is larger than unsigned long.
10431 This includes some 64-bit systems.
10432 - Run correctly on platforms (like some versions of OS X 10.5) where
10433 the real limit for number of open files is OPEN_FILES, not rlim_max
10434 from getrlimit(RLIMIT_NOFILES).
10435 - Avoid a spurious free on base64 failure.
10436 - Avoid segfaults on certain complex invocations of
10437 router_get_by_hexdigest().
10438 - Fix rare bug on REDIRECTSTREAM control command when called with no
10439 port set: it could erroneously report an error when none had
10443 Changes in version 0.2.0.15-alpha - 2007-12-25
10444 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
10445 features added in 0.2.0.13-alpha.
10448 - Fix several remotely triggerable asserts based on DirPort requests
10449 for a v2 or v3 networkstatus object before we were prepared. This
10450 was particularly bad for 0.2.0.13 and later bridge relays, who
10451 would never have a v2 networkstatus and would thus always crash
10452 when used. Bugfixes on 0.2.0.x.
10453 - Estimate the v3 networkstatus size more accurately, rather than
10454 estimating it at zero bytes and giving it artificially high priority
10455 compared to other directory requests. Bugfix on 0.2.0.x.
10458 - Fix configure.in logic for cross-compilation.
10459 - When we load a bridge descriptor from the cache, and it was
10460 previously unreachable, mark it as retriable so we won't just
10461 ignore it. Also, try fetching a new copy immediately. Bugfixes
10463 - The bridge GeoIP stats were counting other relays, for example
10464 self-reachability and authority-reachability tests.
10467 - Support compilation to target iPhone; patch from cjacker huang.
10468 To build for iPhone, pass the --enable-iphone option to configure.
10471 Changes in version 0.2.0.14-alpha - 2007-12-23
10473 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
10474 without a datadirectory from a previous Tor install. Reported
10476 - Fix a crash when we fetch a descriptor that turns out to be
10477 unexpected (it used to be in our networkstatus when we started
10478 fetching it, but it isn't in our current networkstatus), and we
10479 aren't using bridges. Bugfix on 0.2.0.x.
10480 - Fix a crash when accessing hidden services: it would work the first
10481 time you use a given introduction point for your service, but
10482 on subsequent requests we'd be using garbage memory. Fixed by
10483 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
10484 - Fix a crash when we load a bridge descriptor from disk but we don't
10485 currently have a Bridge line for it in our torrc. Bugfix on
10489 - If bridge authorities set BridgePassword, they will serve a
10490 snapshot of known bridge routerstatuses from their DirPort to
10491 anybody who knows that password. Unset by default.
10494 - Make the unit tests build again.
10495 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
10496 - Make PublishServerDescriptor default to 1, so the default doesn't
10497 have to change as we invent new directory protocol versions.
10498 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
10499 be included unless sys/time.h is already included. Fixes
10500 bug 553. Bugfix on 0.2.0.x.
10501 - If we receive a general-purpose descriptor and then receive an
10502 identical bridge-purpose descriptor soon after, don't discard
10503 the next one as a duplicate.
10506 - If BridgeRelay is set to 1, then the default for
10507 PublishServerDescriptor is now "bridge" rather than "v2,v3".
10508 - If the user sets RelayBandwidthRate but doesn't set
10509 RelayBandwidthBurst, then make them equal rather than erroring out.
10512 Changes in version 0.2.0.13-alpha - 2007-12-21
10513 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
10514 Goodell, fixes many more bugs, and adds a lot of infrastructure for
10517 o New directory authorities:
10518 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
10522 - Only update guard status (usable / not usable) once we have
10523 enough directory information. This was causing us to always pick
10524 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
10525 causing us to discard all our guards on startup if we hadn't been
10526 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
10527 - Purge old entries from the "rephist" database and the hidden
10528 service descriptor databases even when DirPort is zero. Bugfix
10530 - We were ignoring our RelayBandwidthRate for the first 30 seconds
10531 after opening a circuit -- even a relayed circuit. Bugfix on
10533 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
10534 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
10535 crashing or mis-answering these types of requests.
10536 - Relays were publishing their server descriptor to v1 and v2
10537 directory authorities, but they didn't try publishing to v3-only
10538 authorities. Fix this; and also stop publishing to v1 authorities.
10540 - When we were reading router descriptors from cache, we were ignoring
10541 the annotations -- so for example we were reading in bridge-purpose
10542 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
10543 - When we decided to send a 503 response to a request for servers, we
10544 were then also sending the server descriptors: this defeats the
10545 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
10548 - Bridge relays now behave like clients with respect to time
10549 intervals for downloading new consensus documents -- otherwise they
10550 stand out. Bridge users now wait until the end of the interval,
10551 so their bridge relay will be sure to have a new consensus document.
10552 - Three new config options (AlternateDirAuthority,
10553 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
10554 user selectively replace the default directory authorities by type,
10555 rather than the all-or-nothing replacement that DirServer offers.
10556 - Tor can now be configured to read a GeoIP file from disk in one
10557 of two formats. This can be used by controllers to map IP addresses
10558 to countries. Eventually, it may support exit-by-country.
10559 - When possible, bridge relays remember which countries users
10560 are coming from, and report aggregate information in their
10561 extra-info documents, so that the bridge authorities can learn
10562 where Tor is blocked.
10563 - Bridge directory authorities now do reachability testing on the
10564 bridges they know. They provide router status summaries to the
10565 controller via "getinfo ns/purpose/bridge", and also dump summaries
10566 to a file periodically.
10567 - Stop fetching directory info so aggressively if your DirPort is
10568 on but your ORPort is off; stop fetching v2 dir info entirely.
10569 You can override these choices with the new FetchDirInfoEarly
10573 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
10574 consensus documents when there are too many relays at a single
10575 IP address. Now clear it in v2 network status documents too, and
10576 also clear it in routerinfo_t when the relay is no longer listed
10577 in the relevant networkstatus document.
10578 - Don't crash if we get an unexpected value for the
10579 PublishServerDescriptor config option. Reported by Matt Edman;
10580 bugfix on 0.2.0.9-alpha.
10581 - Our new v2 hidden service descriptor format allows descriptors
10582 that have no introduction points. But Tor crashed when we tried
10583 to build a descriptor with no intro points (and it would have
10584 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
10585 by Karsten Loesing.
10586 - Fix building with dmalloc 5.5.2 with glibc.
10587 - Reject uploaded descriptors and extrainfo documents if they're
10588 huge. Otherwise we'll cache them all over the network and it'll
10589 clog everything up. Reported by Aljosha Judmayer.
10590 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
10591 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
10592 - When the DANGEROUS_VERSION controller status event told us we're
10593 running an obsolete version, it used the string "OLD" to describe
10594 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
10595 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
10596 - If we can't expand our list of entry guards (e.g. because we're
10597 using bridges or we have StrictEntryNodes set), don't mark relays
10598 down when they fail a directory request. Otherwise we're too quick
10599 to mark all our entry points down. Bugfix on 0.1.2.x.
10600 - Fix handling of hex nicknames when answering controller requests for
10601 networkstatus by name, or when deciding whether to warn about unknown
10602 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
10603 - Fix a couple of hard-to-trigger autoconf problems that could result
10604 in really weird results on platforms whose sys/types.h files define
10605 nonstandard integer types. Bugfix on 0.1.2.x.
10606 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
10607 - Don't crash on name lookup when we have no current consensus. Fixes
10608 bug 538; bugfix on 0.2.0.x.
10609 - Only Tors that want to mirror the v2 directory info should
10610 create the "cached-status" directory in their datadir. (All Tors
10611 used to create it.) Bugfix on 0.2.0.9-alpha.
10612 - Directory authorities should only automatically download Extra Info
10613 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
10616 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
10617 consumers. (We already do this on HUP.)
10618 - Authorities and caches fetch the v2 networkstatus documents
10619 less often, now that v3 is encouraged.
10620 - Add a new config option BridgeRelay that specifies you want to
10621 be a bridge relay. Right now the only difference is that it makes
10622 you answer begin_dir requests, and it makes you cache dir info,
10623 even if your DirPort isn't on.
10624 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
10625 ask about source, timestamp of arrival, purpose, etc. We need
10626 something like this to help Vidalia not do GeoIP lookups on bridge
10628 - Allow multiple HashedControlPassword config lines, to support
10629 multiple controller passwords.
10630 - Authorities now decide whether they're authoritative for a given
10631 router based on the router's purpose.
10632 - New config options AuthDirBadDir and AuthDirListBadDirs for
10633 authorities to mark certain relays as "bad directories" in the
10634 networkstatus documents. Also supports the "!baddir" directive in
10635 the approved-routers file.
10638 Changes in version 0.2.0.12-alpha - 2007-11-16
10639 This twelfth development snapshot fixes some more build problems as
10640 well as a few minor bugs.
10643 - Make it build on OpenBSD again. Patch from tup.
10644 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
10645 package-building for Red Hat, OS X, etc.
10647 o Minor bugfixes (on 0.1.2.x):
10648 - Changing the ExitPolicyRejectPrivate setting should cause us to
10649 rebuild our server descriptor.
10651 o Minor bugfixes (on 0.2.0.x):
10652 - When we're lacking a consensus, don't try to perform rendezvous
10653 operations. Reported by Karsten Loesing.
10654 - Fix a small memory leak whenever we decide against using a
10655 newly picked entry guard. Reported by Mike Perry.
10656 - When authorities detected more than two relays running on the same
10657 IP address, they were clearing all the status flags but forgetting
10658 to clear the "hsdir" flag. So clients were being told that a
10659 given relay was the right choice for a v2 hsdir lookup, yet they
10660 never had its descriptor because it was marked as 'not running'
10662 - If we're trying to fetch a bridge descriptor and there's no way
10663 the bridge authority could help us (for example, we don't know
10664 a digest, or there is no bridge authority), don't be so eager to
10665 fall back to asking the bridge authority.
10666 - If we're using bridges or have strictentrynodes set, and our
10667 chosen exit is in the same family as all our bridges/entry guards,
10668 then be flexible about families.
10671 - When we negotiate a v2 link-layer connection (not yet implemented),
10672 accept RELAY_EARLY cells and turn them into RELAY cells if we've
10673 negotiated a v1 connection for their next step. Initial code for
10677 Changes in version 0.2.0.11-alpha - 2007-11-12
10678 This eleventh development snapshot fixes some build problems with
10679 the previous snapshot. It also includes a more secure-by-default exit
10680 policy for relays, fixes an enormous memory leak for exit relays, and
10681 fixes another bug where servers were falling out of the directory list.
10684 - Exit policies now reject connections that are addressed to a
10685 relay's public (external) IP address too, unless
10686 ExitPolicyRejectPrivate is turned off. We do this because too
10687 many relays are running nearby to services that trust them based
10688 on network address. Bugfix on 0.1.2.x.
10691 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
10692 on every successful resolve. Reported by Mike Perry; bugfix
10694 - On authorities, never downgrade to old router descriptors simply
10695 because they're listed in the consensus. This created a catch-22
10696 where we wouldn't list a new descriptor because there was an
10697 old one in the consensus, and we couldn't get the new one in the
10698 consensus because we wouldn't list it. Possible fix for bug 548.
10699 Also, this might cause bug 543 to appear on authorities; if so,
10700 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
10702 o Packaging fixes on 0.2.0.10-alpha:
10703 - We were including instructions about what to do with the
10704 src/config/fallback-consensus file, but we weren't actually
10705 including it in the tarball. Disable all of that for now.
10708 - Allow people to say PreferTunnelledDirConns rather than
10709 PreferTunneledDirConns, for those alternate-spellers out there.
10712 - Don't reevaluate all the information from our consensus document
10713 just because we've downloaded a v2 networkstatus that we intend
10714 to cache. Fixes bug 545; bugfix on 0.2.0.x.
10717 Changes in version 0.2.0.10-alpha - 2007-11-10
10718 This tenth development snapshot adds a third v3 directory authority
10719 run by Mike Perry, adds most of Karsten Loesing's new hidden service
10720 descriptor format, fixes a bad crash bug and new bridge bugs introduced
10721 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
10722 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
10723 addresses many more minor issues.
10725 o New directory authorities:
10726 - Set up ides (run by Mike Perry) as the third v3 directory authority.
10729 - Allow tunnelled directory connections to ask for an encrypted
10730 "begin_dir" connection or an anonymized "uses a full Tor circuit"
10731 connection independently. Now we can make anonymized begin_dir
10732 connections for (e.g.) more secure hidden service posting and
10734 - More progress on proposal 114: code from Karsten Loesing to
10735 implement new hidden service descriptor format.
10736 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
10737 accommodate the growing number of servers that use the default
10738 and are reaching it.
10739 - Directory authorities use a new formula for selecting which nodes
10740 to advertise as Guards: they must be in the top 7/8 in terms of
10741 how long we have known about them, and above the median of those
10742 nodes in terms of weighted fractional uptime.
10743 - Make "not enough dir info yet" warnings describe *why* Tor feels
10744 it doesn't have enough directory info yet.
10747 - Stop servers from crashing if they set a Family option (or
10748 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
10750 - Make bridge users work again -- the move to v3 directories in
10751 0.2.0.9-alpha had introduced a number of bugs that made bridges
10752 no longer work for clients.
10753 - When the clock jumps forward a lot, do not allow the bandwidth
10754 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
10756 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
10757 - When the consensus lists a router descriptor that we previously were
10758 mirroring, but that we considered non-canonical, reload the
10759 descriptor as canonical. This fixes bug 543 where Tor servers
10760 would start complaining after a few days that they don't have
10761 enough directory information to build a circuit.
10762 - Consider replacing the current consensus when certificates arrive
10763 that make the pending consensus valid. Previously, we were only
10764 considering replacement when the new certs _didn't_ help.
10765 - Fix an assert error on startup if we didn't already have the
10766 consensus and certs cached in our datadirectory: we were caching
10767 the consensus in consensus_waiting_for_certs but then free'ing it
10769 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
10770 Request) if we need more v3 certs but we've already got pending
10771 requests for all of them.
10772 - Correctly back off from failing certificate downloads. Fixes
10774 - Authorities don't vote on the Running flag if they have been running
10775 for less than 30 minutes themselves. Fixes bug 547, where a newly
10776 started authority would vote that everyone was down.
10778 o New requirements:
10779 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
10780 it, it had no AES, and it hasn't seen any security patches since
10784 - Clients now hold circuitless TLS connections open for 1.5 times
10785 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
10786 rebuild a new circuit over them within that timeframe. Previously,
10787 they held them open only for KeepalivePeriod (5 minutes).
10788 - Use "If-Modified-Since" to avoid retrieving consensus
10789 networkstatuses that we already have.
10790 - When we have no consensus, check FallbackNetworkstatusFile (defaults
10791 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
10792 we start knowing some directory caches.
10793 - When we receive a consensus from the future, warn about skew.
10794 - Improve skew reporting: try to give the user a better log message
10795 about how skewed they are, and how much this matters.
10796 - When we have a certificate for an authority, believe that
10797 certificate's claims about the authority's IP address.
10798 - New --quiet command-line option to suppress the default console log.
10799 Good in combination with --hash-password.
10800 - Authorities send back an X-Descriptor-Not-New header in response to
10801 an accepted-but-discarded descriptor upload. Partially implements
10803 - Make the log message for "tls error. breaking." more useful.
10804 - Better log messages about certificate downloads, to attempt to
10805 track down the second incarnation of bug 546.
10807 o Minor features (bridges):
10808 - If bridge users set UpdateBridgesFromAuthority, but the digest
10809 they ask for is a 404 from the bridge authority, they now fall
10810 back to trying the bridge directly.
10811 - Bridges now use begin_dir to publish their server descriptor to
10812 the bridge authority, even when they haven't set TunnelDirConns.
10814 o Minor features (controller):
10815 - When reporting clock skew, and we know that the clock is _at least
10816 as skewed_ as some value, but we don't know the actual value,
10817 report the value as a "minimum skew."
10820 - Update linux-tor-prio.sh script to allow QoS based on the uid of
10821 the Tor process. Patch from Marco Bonetti with tweaks from Mike
10825 - Refuse to start if both ORPort and UseBridges are set. Bugfix
10826 on 0.2.0.x, suggested by Matt Edman.
10827 - Don't stop fetching descriptors when FetchUselessDescriptors is
10828 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
10829 reported by tup and ioerror.
10830 - Better log message on vote from unknown authority.
10831 - Don't log "Launching 0 request for 0 router" message.
10833 o Minor bugfixes (memory leaks):
10834 - Stop leaking memory every time we parse a v3 certificate. Bugfix
10836 - Stop leaking memory every time we load a v3 certificate. Bugfix
10837 on 0.2.0.1-alpha. Fixes bug 536.
10838 - Stop leaking a cached networkstatus on exit. Bugfix on
10840 - Stop leaking voter information every time we free a consensus.
10841 Bugfix on 0.2.0.3-alpha.
10842 - Stop leaking signed data every time we check a voter signature.
10843 Bugfix on 0.2.0.3-alpha.
10844 - Stop leaking a signature every time we fail to parse a consensus or
10845 a vote. Bugfix on 0.2.0.3-alpha.
10846 - Stop leaking v2_download_status_map on shutdown. Bugfix on
10848 - Stop leaking conn->nickname every time we make a connection to a
10849 Tor relay without knowing its expected identity digest (e.g. when
10850 using bridges). Bugfix on 0.2.0.3-alpha.
10852 - Minor bugfixes (portability):
10853 - Run correctly on platforms where rlim_t is larger than unsigned
10854 long, and/or where the real limit for number of open files is
10855 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
10856 particular, these may be needed for OS X 10.5.
10859 Changes in version 0.1.2.18 - 2007-10-28
10860 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
10861 hidden service introduction that were causing huge delays, and a big
10862 bug that was causing some servers to disappear from the network status
10863 lists for a few hours each day.
10865 o Major bugfixes (crashes):
10866 - If a connection is shut down abruptly because of something that
10867 happened inside connection_flushed_some(), do not call
10868 connection_finished_flushing(). Should fix bug 451:
10869 "connection_stop_writing: Assertion conn->write_event failed"
10870 Bugfix on 0.1.2.7-alpha.
10871 - Fix possible segfaults in functions called from
10872 rend_process_relay_cell().
10874 o Major bugfixes (hidden services):
10875 - Hidden services were choosing introduction points uniquely by
10876 hexdigest, but when constructing the hidden service descriptor
10877 they merely wrote the (potentially ambiguous) nickname.
10878 - Clients now use the v2 intro format for hidden service
10879 connections: they specify their chosen rendezvous point by identity
10880 digest rather than by (potentially ambiguous) nickname. These
10881 changes could speed up hidden service connections dramatically.
10883 o Major bugfixes (other):
10884 - Stop publishing a new server descriptor just because we get a
10885 HUP signal. This led (in a roundabout way) to some servers getting
10886 dropped from the networkstatus lists for a few hours each day.
10887 - When looking for a circuit to cannibalize, consider family as well
10888 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10889 circuit cannibalization).
10890 - When a router wasn't listed in a new networkstatus, we were leaving
10891 the flags for that router alone -- meaning it remained Named,
10892 Running, etc -- even though absence from the networkstatus means
10893 that it shouldn't be considered to exist at all anymore. Now we
10894 clear all the flags for routers that fall out of the networkstatus
10895 consensus. Fixes bug 529.
10898 - Don't try to access (or alter) the state file when running
10899 --list-fingerprint or --verify-config or --hash-password. Resolves
10901 - When generating information telling us how to extend to a given
10902 router, do not try to include the nickname if it is
10903 absent. Resolves bug 467.
10904 - Fix a user-triggerable segfault in expand_filename(). (There isn't
10905 a way to trigger this remotely.)
10906 - When sending a status event to the controller telling it that an
10907 OR address is reachable, set the port correctly. (Previously we
10908 were reporting the dir port.)
10909 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10910 command. Bugfix on 0.1.2.17.
10911 - When loading bandwidth history, do not believe any information in
10912 the future. Fixes bug 434.
10913 - When loading entry guard information, do not believe any information
10915 - When we have our clock set far in the future and generate an
10916 onion key, then re-set our clock to be correct, we should not stop
10917 the onion key from getting rotated.
10918 - On some platforms, accept() can return a broken address. Detect
10919 this more quietly, and deal accordingly. Fixes bug 483.
10920 - It's not actually an error to find a non-pending entry in the DNS
10921 cache when canceling a pending resolve. Don't log unless stuff
10922 is fishy. Resolves bug 463.
10923 - Don't reset trusted dir server list when we set a configuration
10924 option. Patch from Robert Hogan.
10925 - Don't try to create the datadir when running --verify-config or
10926 --hash-password. Resolves bug 540.
10929 Changes in version 0.2.0.9-alpha - 2007-10-24
10930 This ninth development snapshot switches clients to the new v3 directory
10931 system; allows servers to be listed in the network status even when they
10932 have the same nickname as a registered server; and fixes many other
10933 bugs including a big one that was causing some servers to disappear
10934 from the network status lists for a few hours each day.
10936 o Major features (directory system):
10937 - Clients now download v3 consensus networkstatus documents instead
10938 of v2 networkstatus documents. Clients and caches now base their
10939 opinions about routers on these consensus documents. Clients only
10940 download router descriptors listed in the consensus.
10941 - Authorities now list servers who have the same nickname as
10942 a different named server, but list them with a new flag,
10943 "Unnamed". Now we can list servers that happen to pick the same
10944 nickname as a server that registered two years ago and then
10945 disappeared. Partially implements proposal 122.
10946 - If the consensus lists a router as "Unnamed", the name is assigned
10947 to a different router: do not identify the router by that name.
10948 Partially implements proposal 122.
10949 - Authorities can now come to a consensus on which method to use to
10950 compute the consensus. This gives us forward compatibility.
10953 - Stop publishing a new server descriptor just because we HUP or
10954 when we find our DirPort to be reachable but won't actually publish
10955 it. New descriptors without any real changes are dropped by the
10956 authorities, and can screw up our "publish every 18 hours" schedule.
10958 - When a router wasn't listed in a new networkstatus, we were leaving
10959 the flags for that router alone -- meaning it remained Named,
10960 Running, etc -- even though absence from the networkstatus means
10961 that it shouldn't be considered to exist at all anymore. Now we
10962 clear all the flags for routers that fall out of the networkstatus
10963 consensus. Fixes bug 529; bugfix on 0.1.2.x.
10964 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
10965 extrainfo documents and then discard them immediately for not
10966 matching the latest router. Bugfix on 0.2.0.1-alpha.
10968 o Minor features (v3 directory protocol):
10969 - Allow tor-gencert to generate a new certificate without replacing
10971 - Allow certificates to include an address.
10972 - When we change our directory-cache settings, reschedule all voting
10973 and download operations.
10974 - Reattempt certificate downloads immediately on failure, as long as
10975 we haven't failed a threshold number of times yet.
10976 - Delay retrying consensus downloads while we're downloading
10977 certificates to verify the one we just got. Also, count getting a
10978 consensus that we already have (or one that isn't valid) as a failure,
10979 and count failing to get the certificates after 20 minutes as a
10981 - Build circuits and download descriptors even if our consensus is a
10982 little expired. (This feature will go away once authorities are
10985 o Minor features (router descriptor cache):
10986 - If we find a cached-routers file that's been sitting around for more
10987 than 28 days unmodified, then most likely it's a leftover from
10988 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10990 - When we (as a cache) download a descriptor because it was listed
10991 in a consensus, remember when the consensus was supposed to expire,
10992 and don't expire the descriptor until then.
10994 o Minor features (performance):
10995 - Call routerlist_remove_old_routers() much less often. This should
10996 speed startup, especially on directory caches.
10997 - Don't try to launch new descriptor downloads quite so often when we
10998 already have enough directory information to build circuits.
10999 - Base64 decoding was actually showing up on our profile when parsing
11000 the initial descriptor file; switch to an in-process all-at-once
11001 implementation that's about 3.5x times faster than calling out to
11004 o Minor features (compilation):
11005 - Detect non-ASCII platforms (if any still exist) and refuse to
11006 build there: some of our code assumes that 'A' is 65 and so on.
11008 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
11009 - Make the "next period" votes into "current period" votes immediately
11010 after publishing the consensus; avoid a heisenbug that made them
11011 stick around indefinitely.
11012 - When we discard a vote as a duplicate, do not report this as
11014 - Treat missing v3 keys or certificates as an error when running as a
11015 v3 directory authority.
11016 - When we're configured to be a v3 authority, but we're only listed
11017 as a non-v3 authority in our DirServer line for ourself, correct
11019 - If an authority doesn't have a qualified hostname, just put
11020 its address in the vote. This fixes the problem where we referred to
11021 "moria on moria:9031."
11022 - Distinguish between detached signatures for the wrong period, and
11023 detached signatures for a divergent vote.
11024 - Fix a small memory leak when computing a consensus.
11025 - When there's no concensus, we were forming a vote every 30
11026 minutes, but writing the "valid-after" line in our vote based
11027 on our configured V3AuthVotingInterval: so unless the intervals
11028 matched up, we immediately rejected our own vote because it didn't
11029 start at the voting interval that caused us to construct a vote.
11031 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
11032 - Delete unverified-consensus when the real consensus is set.
11033 - Consider retrying a consensus networkstatus fetch immediately
11034 after one fails: don't wait 60 seconds to notice.
11035 - When fetching a consensus as a cache, wait until a newer consensus
11036 should exist before trying to replace the current one.
11037 - Use a more forgiving schedule for retrying failed consensus
11038 downloads than for other types.
11040 o Minor bugfixes (other directory issues):
11041 - Correct the implementation of "download votes by digest." Bugfix on
11043 - Authorities no longer send back "400 you're unreachable please fix
11044 it" errors to Tor servers that aren't online all the time. We're
11045 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
11047 o Minor bugfixes (controller):
11048 - Don't reset trusted dir server list when we set a configuration
11049 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
11050 - Respond to INT and TERM SIGNAL commands before we execute the
11051 signal, in case the signal shuts us down. We had a patch in
11052 0.1.2.1-alpha that tried to do this by queueing the response on
11053 the connection's buffer before shutting down, but that really
11054 isn't the same thing at all. Bug located by Matt Edman.
11056 o Minor bugfixes (misc):
11057 - Correctly check for bad options to the "PublishServerDescriptor"
11058 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
11059 - Stop leaking memory on failing case of base32_decode, and make
11060 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
11061 - Don't try to download extrainfo documents when we're trying to
11062 fetch enough directory info to build a circuit: having enough
11063 info should get priority. Bugfix on 0.2.0.x.
11064 - Don't complain that "your server has not managed to confirm that its
11065 ports are reachable" if we haven't been able to build any circuits
11066 yet. Bug found by spending four hours without a v3 consensus. Bugfix
11068 - Detect the reason for failing to mmap a descriptor file we just
11069 wrote, and give a more useful log message. Fixes bug 533. Bugfix
11072 o Code simplifications and refactoring:
11073 - Remove support for the old bw_accounting file: we've been storing
11074 bandwidth accounting information in the state file since
11075 0.1.2.5-alpha. This may result in bandwidth accounting errors
11076 if you try to upgrade from 0.1.1.x or earlier, or if you try to
11077 downgrade to 0.1.1.x or earlier.
11078 - New convenience code to locate a file within the DataDirectory.
11079 - Move non-authority functionality out of dirvote.c.
11080 - Refactor the arguments for router_pick_{directory_|trusteddir}server
11081 so that they all take the same named flags.
11084 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
11085 Unix users an easy way to script their Tor process (e.g. by
11086 adjusting bandwidth based on the time of the day).
11089 Changes in version 0.2.0.8-alpha - 2007-10-12
11090 This eighth development snapshot fixes a crash bug that's been bothering
11091 us since February 2007, lets bridge authorities store a list of bridge
11092 descriptors they've seen, gets v3 directory voting closer to working,
11093 starts caching v3 directory consensus documents on directory mirrors,
11094 and fixes a variety of smaller issues including some minor memory leaks.
11096 o Major features (router descriptor cache):
11097 - Store routers in a file called cached-descriptors instead of in
11098 cached-routers. Initialize cached-descriptors from cached-routers
11099 if the old format is around. The new format allows us to store
11100 annotations along with descriptors.
11101 - Use annotations to record the time we received each descriptor, its
11102 source, and its purpose.
11103 - Disable the SETROUTERPURPOSE controller command: it is now
11105 - Controllers should now specify cache=no or cache=yes when using
11106 the +POSTDESCRIPTOR command.
11107 - Bridge authorities now write bridge descriptors to disk, meaning
11108 we can export them to other programs and begin distributing them
11111 o Major features (directory authorities):
11112 - When a v3 authority is missing votes or signatures, it now tries
11114 - Directory authorities track weighted fractional uptime as well as
11115 weighted mean-time-between failures. WFU is suitable for deciding
11116 whether a node is "usually up", while MTBF is suitable for deciding
11117 whether a node is "likely to stay up." We need both, because
11118 "usually up" is a good requirement for guards, while "likely to
11119 stay up" is a good requirement for long-lived connections.
11121 o Major features (v3 directory system):
11122 - Caches now download v3 network status documents as needed,
11123 and download the descriptors listed in them.
11124 - All hosts now attempt to download and keep fresh v3 authority
11125 certificates, and re-attempt after failures.
11126 - More internal-consistency checks for vote parsing.
11128 o Major bugfixes (crashes):
11129 - If a connection is shut down abruptly because of something that
11130 happened inside connection_flushed_some(), do not call
11131 connection_finished_flushing(). Should fix bug 451. Bugfix on
11134 o Major bugfixes (performance):
11135 - Fix really bad O(n^2) performance when parsing a long list of
11136 routers: Instead of searching the entire list for an "extra-info "
11137 string which usually wasn't there, once for every routerinfo
11138 we read, just scan lines forward until we find one we like.
11140 - When we add data to a write buffer in response to the data on that
11141 write buffer getting low because of a flush, do not consider the
11142 newly added data as a candidate for immediate flushing, but rather
11143 make it wait until the next round of writing. Otherwise, we flush
11144 and refill recursively, and a single greedy TLS connection can
11145 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
11147 o Minor features (v3 authority system):
11148 - Add more ways for tools to download the votes that lead to the
11150 - Send a 503 when low on bandwidth and a vote, consensus, or
11151 certificate is requested.
11152 - If-modified-since is now implemented properly for all kinds of
11153 certificate requests.
11155 o Minor bugfixes (network statuses):
11156 - Tweak the implementation of proposal 109 slightly: allow at most
11157 two Tor servers on the same IP address, except if it's the location
11158 of a directory authority, in which case allow five. Bugfix on
11161 o Minor bugfixes (controller):
11162 - When sending a status event to the controller telling it that an
11163 OR address is reachable, set the port correctly. (Previously we
11164 were reporting the dir port.) Bugfix on 0.1.2.x.
11166 o Minor bugfixes (v3 directory system):
11167 - Fix logic to look up a cert by its signing key digest. Bugfix on
11169 - Only change the reply to a vote to "OK" if it's not already
11170 set. This gets rid of annoying "400 OK" log messages, which may
11171 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
11172 - When we get a valid consensus, recompute the voting schedule.
11173 - Base the valid-after time of a vote on the consensus voting
11174 schedule, not on our preferred schedule.
11175 - Make the return values and messages from signature uploads and
11176 downloads more sensible.
11177 - Fix a memory leak when serving votes and consensus documents, and
11178 another when serving certificates.
11180 o Minor bugfixes (performance):
11181 - Use a slightly simpler string hashing algorithm (copying Python's
11182 instead of Java's) and optimize our digest hashing algorithm to take
11183 advantage of 64-bit platforms and to remove some possibly-costly
11185 - Fix a minor memory leak whenever we parse guards from our state
11186 file. Bugfix on 0.2.0.7-alpha.
11187 - Fix a minor memory leak whenever we write out a file. Bugfix on
11189 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11190 command. Bugfix on 0.2.0.5-alpha.
11192 o Minor bugfixes (portability):
11193 - On some platforms, accept() can return a broken address. Detect
11194 this more quietly, and deal accordingly. Fixes bug 483.
11195 - Stop calling tor_strlower() on uninitialized memory in some cases.
11196 Bugfix in 0.2.0.7-alpha.
11198 o Minor bugfixes (usability):
11199 - Treat some 403 responses from directory servers as INFO rather than
11200 WARN-severity events.
11201 - It's not actually an error to find a non-pending entry in the DNS
11202 cache when canceling a pending resolve. Don't log unless stuff is
11203 fishy. Resolves bug 463.
11205 o Minor bugfixes (anonymity):
11206 - Never report that we've used more bandwidth than we're willing to
11207 relay: it leaks how much non-relay traffic we're using. Resolves
11209 - When looking for a circuit to cannibalize, consider family as well
11210 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
11211 circuit cannibalization).
11213 o Code simplifications and refactoring:
11214 - Make a bunch of functions static. Remove some dead code.
11215 - Pull out about a third of the really big routerlist.c; put it in a
11216 new module, networkstatus.c.
11217 - Merge the extra fields in local_routerstatus_t back into
11218 routerstatus_t: we used to need one routerstatus_t for each
11219 authority's opinion, plus a local_routerstatus_t for the locally
11220 computed consensus opinion. To save space, we put the locally
11221 modified fields into local_routerstatus_t, and only the common
11222 stuff into routerstatus_t. But once v3 directories are in use,
11223 clients and caches will no longer need to hold authority opinions;
11224 thus, the rationale for keeping the types separate is now gone.
11225 - Make the code used to reschedule and reattempt downloads more
11227 - Turn all 'Are we a directory server/mirror?' logic into a call to
11229 - Remove the code to generate the oldest (v1) directory format.
11230 The code has been disabled since 0.2.0.5-alpha.
11233 Changes in version 0.2.0.7-alpha - 2007-09-21
11234 This seventh development snapshot makes bridges work again, makes bridge
11235 authorities work for the first time, fixes two huge performance flaws
11236 in hidden services, and fixes a variety of minor issues.
11238 o New directory authorities:
11239 - Set up moria1 and tor26 as the first v3 directory authorities. See
11240 doc/spec/dir-spec.txt for details on the new directory design.
11242 o Major bugfixes (crashes):
11243 - Fix possible segfaults in functions called from
11244 rend_process_relay_cell(). Bugfix on 0.1.2.x.
11246 o Major bugfixes (bridges):
11247 - Fix a bug that made servers send a "404 Not found" in response to
11248 attempts to fetch their server descriptor. This caused Tor servers
11249 to take many minutes to establish reachability for their DirPort,
11250 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
11251 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
11252 users configure that and specify a bridge with an identity
11253 fingerprint, now they will lookup the bridge descriptor at the
11254 default bridge authority via a one-hop tunnel, but once circuits
11255 are established they will switch to a three-hop tunnel for later
11256 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
11258 o Major bugfixes (hidden services):
11259 - Hidden services were choosing introduction points uniquely by
11260 hexdigest, but when constructing the hidden service descriptor
11261 they merely wrote the (potentially ambiguous) nickname.
11262 - Clients now use the v2 intro format for hidden service
11263 connections: they specify their chosen rendezvous point by identity
11264 digest rather than by (potentially ambiguous) nickname. Both
11265 are bugfixes on 0.1.2.x, and they could speed up hidden service
11266 connections dramatically. Thanks to Karsten Loesing.
11268 o Minor features (security):
11269 - As a client, do not believe any server that tells us that an
11270 address maps to an internal address space.
11271 - Make it possible to enable HashedControlPassword and
11272 CookieAuthentication at the same time.
11274 o Minor features (guard nodes):
11275 - Tag every guard node in our state file with the version that
11276 we believe added it, or with our own version if we add it. This way,
11277 if a user temporarily runs an old version of Tor and then switches
11278 back to a new one, she doesn't automatically lose her guards.
11280 o Minor features (speed):
11281 - When implementing AES counter mode, update only the portions of the
11282 counter buffer that need to change, and don't keep separate
11283 network-order and host-order counters when they are the same (i.e.,
11284 on big-endian hosts.)
11286 o Minor features (controller):
11287 - Accept LF instead of CRLF on controller, since some software has a
11288 hard time generating real Internet newlines.
11289 - Add GETINFO values for the server status events
11290 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
11293 o Removed features:
11294 - Routers no longer include bandwidth-history lines in their
11295 descriptors; this information is already available in extra-info
11296 documents, and including it in router descriptors took up 60%
11297 (!) of compressed router descriptor downloads. Completes
11298 implementation of proposal 104.
11299 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
11300 and TorControl.py, as they use the old v0 controller protocol,
11301 and are obsoleted by TorFlow anyway.
11302 - Drop support for v1 rendezvous descriptors, since we never used
11303 them anyway, and the code has probably rotted by now. Based on
11304 patch from Karsten Loesing.
11305 - On OSX, stop warning the user that kqueue support in libevent is
11306 "experimental", since it seems to have worked fine for ages.
11309 - When generating information telling us how to extend to a given
11310 router, do not try to include the nickname if it is absent. Fixes
11311 bug 467. Bugfix on 0.2.0.3-alpha.
11312 - Fix a user-triggerable (but not remotely-triggerable) segfault
11313 in expand_filename(). Bugfix on 0.1.2.x.
11314 - Fix a memory leak when freeing incomplete requests from DNSPort.
11315 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
11316 - Don't try to access (or alter) the state file when running
11317 --list-fingerprint or --verify-config or --hash-password. (Resolves
11318 bug 499.) Bugfix on 0.1.2.x.
11319 - Servers used to decline to publish their DirPort if their
11320 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
11321 were below a threshold. Now they only look at BandwidthRate and
11322 RelayBandwidthRate. Bugfix on 0.1.2.x.
11323 - Remove an optimization in the AES counter-mode code that assumed
11324 that the counter never exceeded 2^68. When the counter can be set
11325 arbitrarily as an IV (as it is by Karsten's new hidden services
11326 code), this assumption no longer holds. Bugfix on 0.1.2.x.
11327 - Resume listing "AUTHORITY" flag for authorities in network status.
11328 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
11330 o Code simplifications and refactoring:
11331 - Revamp file-writing logic so we don't need to have the entire
11332 contents of a file in memory at once before we write to disk. Tor,
11334 - Turn "descriptor store" into a full-fledged type.
11335 - Move all NT services code into a separate source file.
11336 - Unify all code that computes medians, percentile elements, etc.
11337 - Get rid of a needless malloc when parsing address policies.
11340 Changes in version 0.1.2.17 - 2007-08-30
11341 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
11342 X bundles. Vidalia 0.0.14 makes authentication required for the
11343 ControlPort in the default configuration, which addresses important
11344 security risks. Everybody who uses Vidalia (or another controller)
11347 In addition, this Tor update fixes major load balancing problems with
11348 path selection, which should speed things up a lot once many people
11351 o Major bugfixes (security):
11352 - We removed support for the old (v0) control protocol. It has been
11353 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
11354 become more of a headache than it's worth.
11356 o Major bugfixes (load balancing):
11357 - When choosing nodes for non-guard positions, weight guards
11358 proportionally less, since they already have enough load. Patch
11360 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
11361 will allow fast Tor servers to get more attention.
11362 - When we're upgrading from an old Tor version, forget our current
11363 guards and pick new ones according to the new weightings. These
11364 three load balancing patches could raise effective network capacity
11365 by a factor of four. Thanks to Mike Perry for measurements.
11367 o Major bugfixes (stream expiration):
11368 - Expire not-yet-successful application streams in all cases if
11369 they've been around longer than SocksTimeout. Right now there are
11370 some cases where the stream will live forever, demanding a new
11371 circuit every 15 seconds. Fixes bug 454; reported by lodger.
11373 o Minor features (controller):
11374 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
11375 is valid before any authentication has been received. It tells
11376 a controller what kind of authentication is expected, and what
11377 protocol is spoken. Implements proposal 119.
11379 o Minor bugfixes (performance):
11380 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
11381 greatly speeding up loading cached-routers from disk on startup.
11382 - Disable sentinel-based debugging for buffer code: we squashed all
11383 the bugs that this was supposed to detect a long time ago, and now
11384 its only effect is to change our buffer sizes from nice powers of
11385 two (which platform mallocs tend to like) to values slightly over
11386 powers of two (which make some platform mallocs sad).
11388 o Minor bugfixes (misc):
11389 - If exit bandwidth ever exceeds one third of total bandwidth, then
11390 use the correct formula to weight exit nodes when choosing paths.
11391 Based on patch from Mike Perry.
11392 - Choose perfectly fairly among routers when choosing by bandwidth and
11393 weighting by fraction of bandwidth provided by exits. Previously, we
11394 would choose with only approximate fairness, and correct ourselves
11395 if we ran off the end of the list.
11396 - If we require CookieAuthentication but we fail to write the
11397 cookie file, we would warn but not exit, and end up in a state
11398 where no controller could authenticate. Now we exit.
11399 - If we require CookieAuthentication, stop generating a new cookie
11400 every time we change any piece of our config.
11401 - Refuse to start with certain directory authority keys, and
11402 encourage people using them to stop.
11403 - Terminate multi-line control events properly. Original patch
11405 - Fix a minor memory leak when we fail to find enough suitable
11406 servers to choose a circuit.
11407 - Stop leaking part of the descriptor when we run into a particularly
11408 unparseable piece of it.
11411 Changes in version 0.2.0.6-alpha - 2007-08-26
11412 This sixth development snapshot features a new Vidalia version in the
11413 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
11414 the ControlPort in the default configuration, which addresses important
11417 In addition, this snapshot fixes major load balancing problems
11418 with path selection, which should speed things up a lot once many
11419 people have upgraded. The directory authorities also use a new
11420 mean-time-between-failure approach to tracking which servers are stable,
11421 rather than just looking at the most recent uptime.
11423 o New directory authorities:
11424 - Set up Tonga as the default bridge directory authority.
11427 - Directory authorities now track servers by weighted
11428 mean-times-between-failures. When we have 4 or more days of data,
11429 use measured MTBF rather than declared uptime to decide whether
11430 to call a router Stable. Implements proposal 108.
11432 o Major bugfixes (load balancing):
11433 - When choosing nodes for non-guard positions, weight guards
11434 proportionally less, since they already have enough load. Patch
11436 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
11437 will allow fast Tor servers to get more attention.
11438 - When we're upgrading from an old Tor version, forget our current
11439 guards and pick new ones according to the new weightings. These
11440 three load balancing patches could raise effective network capacity
11441 by a factor of four. Thanks to Mike Perry for measurements.
11443 o Major bugfixes (descriptor parsing):
11444 - Handle unexpected whitespace better in malformed descriptors. Bug
11445 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
11448 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
11449 GETINFO for Torstat to use until it can switch to using extrainfos.
11450 - Optionally (if built with -DEXPORTMALLINFO) export the output
11451 of mallinfo via http, as tor/mallinfo.txt. Only accessible
11455 - Do not intermix bridge routers with controller-added
11456 routers. (Bugfix on 0.2.0.x)
11457 - Do not fail with an assert when accept() returns an unexpected
11458 address family. Addresses but does not wholly fix bug 483. (Bugfix
11460 - Let directory authorities startup even when they can't generate
11461 a descriptor immediately, e.g. because they don't know their
11463 - Stop putting the authentication cookie in a file called "0"
11464 in your working directory if you don't specify anything for the
11465 new CookieAuthFile option. Reported by Matt Edman.
11466 - Make it possible to read the PROTOCOLINFO response in a way that
11467 conforms to our control-spec. Reported by Matt Edman.
11468 - Fix a minor memory leak when we fail to find enough suitable
11469 servers to choose a circuit. Bugfix on 0.1.2.x.
11470 - Stop leaking part of the descriptor when we run into a particularly
11471 unparseable piece of it. Bugfix on 0.1.2.x.
11472 - Unmap the extrainfo cache file on exit.
11475 Changes in version 0.2.0.5-alpha - 2007-08-19
11476 This fifth development snapshot fixes compilation on Windows again;
11477 fixes an obnoxious client-side bug that slowed things down and put
11478 extra load on the network; gets us closer to using the v3 directory
11479 voting scheme; makes it easier for Tor controllers to use cookie-based
11480 authentication; and fixes a variety of other bugs.
11482 o Removed features:
11483 - Version 1 directories are no longer generated in full. Instead,
11484 authorities generate and serve "stub" v1 directories that list
11485 no servers. This will stop Tor versions 0.1.0.x and earlier from
11486 working, but (for security reasons) nobody should be running those
11489 o Major bugfixes (compilation, 0.2.0.x):
11490 - Try to fix Win32 compilation again: improve checking for IPv6 types.
11491 - Try to fix MSVC compilation: build correctly on platforms that do
11492 not define s6_addr16 or s6_addr32.
11493 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
11496 o Major bugfixes (stream expiration):
11497 - Expire not-yet-successful application streams in all cases if
11498 they've been around longer than SocksTimeout. Right now there are
11499 some cases where the stream will live forever, demanding a new
11500 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
11501 reported by lodger.
11503 o Minor features (directory servers):
11504 - When somebody requests a list of statuses or servers, and we have
11505 none of those, return a 404 rather than an empty 200.
11507 o Minor features (directory voting):
11508 - Store v3 consensus status consensuses on disk, and reload them
11511 o Minor features (security):
11512 - Warn about unsafe ControlPort configurations.
11513 - Refuse to start with certain directory authority keys, and
11514 encourage people using them to stop.
11516 o Minor features (controller):
11517 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
11518 is valid before any authentication has been received. It tells
11519 a controller what kind of authentication is expected, and what
11520 protocol is spoken. Implements proposal 119.
11521 - New config option CookieAuthFile to choose a new location for the
11522 cookie authentication file, and config option
11523 CookieAuthFileGroupReadable to make it group-readable.
11525 o Minor features (unit testing):
11526 - Add command-line arguments to unit-test executable so that we can
11527 invoke any chosen test from the command line rather than having
11528 to run the whole test suite at once; and so that we can turn on
11529 logging for the unit tests.
11531 o Minor bugfixes (on 0.1.2.x):
11532 - If we require CookieAuthentication but we fail to write the
11533 cookie file, we would warn but not exit, and end up in a state
11534 where no controller could authenticate. Now we exit.
11535 - If we require CookieAuthentication, stop generating a new cookie
11536 every time we change any piece of our config.
11537 - When loading bandwidth history, do not believe any information in
11538 the future. Fixes bug 434.
11539 - When loading entry guard information, do not believe any information
11541 - When we have our clock set far in the future and generate an
11542 onion key, then re-set our clock to be correct, we should not stop
11543 the onion key from getting rotated.
11544 - Clean up torrc sample config file.
11545 - Do not automatically run configure from autogen.sh. This
11546 non-standard behavior tended to annoy people who have built other
11549 o Minor bugfixes (on 0.2.0.x):
11550 - Fix a bug with AutomapHostsOnResolve that would always cause
11551 the second request to fail. Bug reported by Kate. Bugfix on
11553 - Fix a bug in ADDRMAP controller replies that would sometimes
11554 try to print a NULL. Patch from tup.
11555 - Read v3 directory authority keys from the right location.
11556 - Numerous bugfixes to directory voting code.
11559 Changes in version 0.1.2.16 - 2007-08-01
11560 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
11561 remote attacker in certain situations to rewrite the user's torrc
11562 configuration file. This can completely compromise anonymity of users
11563 in most configurations, including those running the Vidalia bundles,
11564 TorK, etc. Or worse.
11566 o Major security fixes:
11567 - Close immediately after missing authentication on control port;
11568 do not allow multiple authentication attempts.
11571 Changes in version 0.2.0.4-alpha - 2007-08-01
11572 This fourth development snapshot fixes a critical security vulnerability
11573 for most users, specifically those running Vidalia, TorK, etc. Everybody
11574 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
11576 o Major security fixes:
11577 - Close immediately after missing authentication on control port;
11578 do not allow multiple authentication attempts.
11580 o Major bugfixes (compilation):
11581 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
11584 o Minor features (performance):
11585 - Be even more aggressive about releasing RAM from small
11586 empty buffers. Thanks to our free-list code, this shouldn't be too
11587 performance-intensive.
11588 - Disable sentinel-based debugging for buffer code: we squashed all
11589 the bugs that this was supposed to detect a long time ago, and
11590 now its only effect is to change our buffer sizes from nice
11591 powers of two (which platform mallocs tend to like) to values
11592 slightly over powers of two (which make some platform mallocs sad).
11593 - Log malloc statistics from mallinfo() on platforms where it
11597 Changes in version 0.2.0.3-alpha - 2007-07-29
11598 This third development snapshot introduces new experimental
11599 blocking-resistance features and a preliminary version of the v3
11600 directory voting design, and includes many other smaller features
11604 - The first pieces of our "bridge" design for blocking-resistance
11605 are implemented. People can run bridge directory authorities;
11606 people can run bridges; and people can configure their Tor clients
11607 with a set of bridges to use as the first hop into the Tor network.
11608 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
11610 - Create listener connections before we setuid to the configured
11611 User and Group. Now non-Windows users can choose port values
11612 under 1024, start Tor as root, and have Tor bind those ports
11613 before it changes to another UID. (Windows users could already
11615 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
11616 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
11617 on "vserver" accounts. (Patch from coderman.)
11618 - Be even more aggressive about separating local traffic from relayed
11619 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
11621 o Major features (experimental):
11622 - First cut of code for "v3 dir voting": directory authorities will
11623 vote on a common network status document rather than each publishing
11624 their own opinion. This code needs more testing and more corner-case
11625 handling before it's ready for use.
11628 - Directory authorities now call routers Fast if their bandwidth is
11629 at least 100KB/s, and consider their bandwidth adequate to be a
11630 Guard if it is at least 250KB/s, no matter the medians. This fix
11631 complements proposal 107. [Bugfix on 0.1.2.x]
11632 - Directory authorities now never mark more than 3 servers per IP as
11633 Valid and Running. (Implements proposal 109, by Kevin Bauer and
11635 - Minor change to organizationName and commonName generation
11636 procedures in TLS certificates during Tor handshakes, to invalidate
11637 some earlier censorware approaches. This is not a long-term
11638 solution, but applying it will give us a bit of time to look into
11639 the epidemiology of countermeasures as they spread.
11641 o Major bugfixes (directory):
11642 - Rewrite directory tokenization code to never run off the end of
11643 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
11645 o Minor features (controller):
11646 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
11647 match requests to applications. (Patch from Robert Hogan.)
11648 - Report address and port correctly on connections to DNSPort. (Patch
11649 from Robert Hogan.)
11650 - Add a RESOLVE command to launch hostname lookups. (Original patch
11651 from Robert Hogan.)
11652 - Add GETINFO status/enough-dir-info to let controllers tell whether
11653 Tor has downloaded sufficient directory information. (Patch
11655 - You can now use the ControlSocket option to tell Tor to listen for
11656 controller connections on Unix domain sockets on systems that
11657 support them. (Patch from Peter Palfrader.)
11658 - STREAM NEW events are generated for DNSPort requests and for
11659 tunneled directory connections. (Patch from Robert Hogan.)
11660 - New "GETINFO address-mappings/*" command to get address mappings
11661 with expiry information. "addr-mappings/*" is now deprecated.
11664 o Minor features (misc):
11665 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
11667 - The tor-gencert tool for v3 directory authorities now creates all
11668 files as readable to the file creator only, and write-protects
11669 the authority identity key.
11670 - When dumping memory usage, list bytes used in buffer memory
11672 - When running with dmalloc, dump more stats on hup and on exit.
11673 - Directory authorities now fail quickly and (relatively) harmlessly
11674 if they generate a network status document that is somehow
11677 o Traffic load balancing improvements:
11678 - If exit bandwidth ever exceeds one third of total bandwidth, then
11679 use the correct formula to weight exit nodes when choosing paths.
11680 (Based on patch from Mike Perry.)
11681 - Choose perfectly fairly among routers when choosing by bandwidth and
11682 weighting by fraction of bandwidth provided by exits. Previously, we
11683 would choose with only approximate fairness, and correct ourselves
11684 if we ran off the end of the list. [Bugfix on 0.1.2.x]
11686 o Performance improvements:
11687 - Be more aggressive with freeing buffer RAM or putting it on the
11689 - Use Critical Sections rather than Mutexes for synchronizing threads
11690 on win32; Mutexes are heavier-weight, and designed for synchronizing
11693 o Deprecated and removed features:
11694 - RedirectExits is now deprecated.
11695 - Stop allowing address masks that do not correspond to bit prefixes.
11696 We have warned about these for a really long time; now it's time
11697 to reject them. (Patch from croup.)
11699 o Minor bugfixes (directory):
11700 - Fix another crash bug related to extra-info caching. (Bug found by
11701 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
11702 - Directories no longer return a "304 not modified" when they don't
11703 have the networkstatus the client asked for. Also fix a memory
11704 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
11705 - We had accidentally labelled 0.1.2.x directory servers as not
11706 suitable for begin_dir requests, and had labelled no directory
11707 servers as suitable for uploading extra-info documents. [Bugfix
11710 o Minor bugfixes (dns):
11711 - Fix a crash when DNSPort is set more than once. (Patch from Robert
11712 Hogan.) [Bugfix on 0.2.0.2-alpha]
11713 - Add DNSPort connections to the global connection list, so that we
11714 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
11716 - Fix a dangling reference that could lead to a crash when DNSPort is
11717 changed or closed (Patch from Robert Hogan.) [Bugfix on
11720 o Minor bugfixes (controller):
11721 - Provide DNS expiry times in GMT, not in local time. For backward
11722 compatibility, ADDRMAP events only provide GMT expiry in an extended
11723 field. "GETINFO address-mappings" always does the right thing.
11724 - Use CRLF line endings properly in NS events.
11725 - Terminate multi-line control events properly. (Original patch
11726 from tup.) [Bugfix on 0.1.2.x-alpha]
11727 - Do not include spaces in SOURCE_ADDR fields in STREAM
11728 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
11731 Changes in version 0.1.2.15 - 2007-07-17
11732 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
11733 problems, fixes compilation on BSD, and fixes a variety of other
11734 bugs. Everybody should upgrade.
11736 o Major bugfixes (compilation):
11737 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
11739 o Major bugfixes (crashes):
11740 - Try even harder not to dereference the first character after
11741 an mmap(). Reported by lodger.
11742 - Fix a crash bug in directory authorities when we re-number the
11743 routerlist while inserting a new router.
11744 - When the cached-routers file is an even multiple of the page size,
11745 don't run off the end and crash. (Fixes bug 455; based on idea
11747 - Fix eventdns.c behavior on Solaris: It is critical to include
11748 orconfig.h _before_ sys/types.h, so that we can get the expected
11749 definition of _FILE_OFFSET_BITS.
11751 o Major bugfixes (security):
11752 - Fix a possible buffer overrun when using BSD natd support. Bug
11754 - When sending destroy cells from a circuit's origin, don't include
11755 the reason for tearing down the circuit. The spec says we didn't,
11756 and now we actually don't. Reported by lodger.
11757 - Keep streamids from different exits on a circuit separate. This
11758 bug may have allowed other routers on a given circuit to inject
11759 cells into streams. Reported by lodger; fixes bug 446.
11760 - If there's a never-before-connected-to guard node in our list,
11761 never choose any guards past it. This way we don't expand our
11762 guard list unless we need to.
11764 o Minor bugfixes (guard nodes):
11765 - Weight guard selection by bandwidth, so that low-bandwidth nodes
11766 don't get overused as guards.
11768 o Minor bugfixes (directory):
11769 - Correctly count the number of authorities that recommend each
11770 version. Previously, we were under-counting by 1.
11771 - Fix a potential crash bug when we load many server descriptors at
11772 once and some of them make others of them obsolete. Fixes bug 458.
11774 o Minor bugfixes (hidden services):
11775 - Stop tearing down the whole circuit when the user asks for a
11776 connection to a port that the hidden service didn't configure.
11779 o Minor bugfixes (misc):
11780 - On Windows, we were preventing other processes from reading
11781 cached-routers while Tor was running. Reported by janbar.
11782 - Fix a possible (but very unlikely) bug in picking routers by
11783 bandwidth. Add a log message to confirm that it is in fact
11784 unlikely. Patch from lodger.
11785 - Backport a couple of memory leak fixes.
11786 - Backport miscellaneous cosmetic bugfixes.
11789 Changes in version 0.2.0.2-alpha - 2007-06-02
11790 o Major bugfixes on 0.2.0.1-alpha:
11791 - Fix an assertion failure related to servers without extra-info digests.
11792 Resolves bugs 441 and 442.
11794 o Minor features (directory):
11795 - Support "If-Modified-Since" when answering HTTP requests for
11796 directories, running-routers documents, and network-status documents.
11797 (There's no need to support it for router descriptors, since those
11798 are downloaded by descriptor digest.)
11800 o Minor build issues:
11801 - Clear up some MIPSPro compiler warnings.
11802 - When building from a tarball on a machine that happens to have SVK
11803 installed, report the micro-revision as whatever version existed
11804 in the tarball, not as "x".
11807 Changes in version 0.2.0.1-alpha - 2007-06-01
11808 This early development snapshot provides new features for people running
11809 Tor as both a client and a server (check out the new RelayBandwidth
11810 config options); lets Tor run as a DNS proxy; and generally moves us
11811 forward on a lot of fronts.
11813 o Major features, server usability:
11814 - New config options RelayBandwidthRate and RelayBandwidthBurst:
11815 a separate set of token buckets for relayed traffic. Right now
11816 relayed traffic is defined as answers to directory requests, and
11817 OR connections that don't have any local circuits on them.
11819 o Major features, client usability:
11820 - A client-side DNS proxy feature to replace the need for
11821 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
11822 for DNS requests on port 9999, use the Tor network to resolve them
11823 anonymously, and send the reply back like a regular DNS server.
11824 The code still only implements a subset of DNS.
11825 - Make PreferTunneledDirConns and TunnelDirConns work even when
11826 we have no cached directory info. This means Tor clients can now
11827 do all of their connections protected by TLS.
11829 o Major features, performance and efficiency:
11830 - Directory authorities accept and serve "extra info" documents for
11831 routers. These documents contain fields from router descriptors
11832 that aren't usually needed, and that use a lot of excess
11833 bandwidth. Once these fields are removed from router descriptors,
11834 the bandwidth savings should be about 60%. [Partially implements
11836 - Servers upload extra-info documents to any authority that accepts
11837 them. Authorities (and caches that have been configured to download
11838 extra-info documents) download them as needed. [Partially implements
11840 - Change the way that Tor buffers data that it is waiting to write.
11841 Instead of queueing data cells in an enormous ring buffer for each
11842 client->OR or OR->OR connection, we now queue cells on a separate
11843 queue for each circuit. This lets us use less slack memory, and
11844 will eventually let us be smarter about prioritizing different kinds
11846 - Use memory pools to allocate cells with better speed and memory
11847 efficiency, especially on platforms where malloc() is inefficient.
11848 - Stop reading on edge connections when their corresponding circuit
11849 buffers are full; start again as the circuits empty out.
11851 o Major features, other:
11852 - Add an HSAuthorityRecordStats option that hidden service authorities
11853 can use to track statistics of overall hidden service usage without
11854 logging information that would be very useful to an attacker.
11855 - Start work implementing multi-level keys for directory authorities:
11856 Add a standalone tool to generate key certificates. (Proposal 103.)
11859 - Directory authorities now call routers Stable if they have an
11860 uptime of at least 30 days, even if that's not the median uptime
11861 in the network. Implements proposal 107, suggested by Kevin Bauer
11864 o Minor fixes (resource management):
11865 - Count the number of open sockets separately from the number
11866 of active connection_t objects. This will let us avoid underusing
11867 our allocated connection limit.
11868 - We no longer use socket pairs to link an edge connection to an
11869 anonymous directory connection or a DirPort test connection.
11870 Instead, we track the link internally and transfer the data
11871 in-process. This saves two sockets per "linked" connection (at the
11872 client and at the server), and avoids the nasty Windows socketpair()
11874 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
11875 for every single inactive connection_t. Free items from the
11876 4k/16k-buffer free lists when they haven't been used for a while.
11878 o Minor features (build):
11879 - Make autoconf search for libevent, openssl, and zlib consistently.
11880 - Update deprecated macros in configure.in.
11881 - When warning about missing headers, tell the user to let us
11882 know if the compile succeeds anyway, so we can downgrade the
11884 - Include the current subversion revision as part of the version
11885 string: either fetch it directly if we're in an SVN checkout, do
11886 some magic to guess it if we're in an SVK checkout, or use
11887 the last-detected version if we're building from a .tar.gz.
11888 Use this version consistently in log messages.
11890 o Minor features (logging):
11891 - Always prepend "Bug: " to any log message about a bug.
11892 - Put a platform string (e.g. "Linux i686") in the startup log
11893 message, so when people paste just their logs, we know if it's
11894 OpenBSD or Windows or what.
11895 - When logging memory usage, break down memory used in buffers by
11898 o Minor features (directory system):
11899 - New config option V2AuthoritativeDirectory that all directory
11900 authorities should set. This will let future authorities choose
11901 not to serve V2 directory information.
11902 - Directory authorities allow multiple router descriptors and/or extra
11903 info documents to be uploaded in a single go. This will make
11904 implementing proposal 104 simpler.
11906 o Minor features (controller):
11907 - Add a new config option __DisablePredictedCircuits designed for
11908 use by the controller, when we don't want Tor to build any circuits
11910 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
11911 so we can exit from the middle of the circuit.
11912 - Implement "getinfo status/circuit-established".
11913 - Implement "getinfo status/version/..." so a controller can tell
11914 whether the current version is recommended, and whether any versions
11915 are good, and how many authorities agree. (Patch from shibz.)
11917 o Minor features (hidden services):
11918 - Allow multiple HiddenServicePort directives with the same virtual
11919 port; when they occur, the user is sent round-robin to one
11920 of the target ports chosen at random. Partially fixes bug 393 by
11921 adding limited ad-hoc round-robining.
11923 o Minor features (other):
11925 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11926 resolve request for hosts matching a given pattern causes Tor to
11927 generate an internal virtual address mapping for that host. This
11928 allows DNSPort to work sensibly with hidden service users. By
11929 default, .exit and .onion addresses are remapped; the list of
11930 patterns can be reconfigured with AutomapHostsSuffixes.
11931 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11932 address. Thanks to the AutomapHostsOnResolve option, this is no
11933 longer a completely silly thing to do.
11934 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11935 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11936 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11937 minus 1 byte: the actual maximum declared bandwidth.
11939 o Removed features:
11940 - Removed support for the old binary "version 0" controller protocol.
11941 This has been deprecated since 0.1.1, and warnings have been issued
11942 since 0.1.2. When we encounter a v0 control message, we now send
11943 back an error and close the connection.
11944 - Remove the old "dns worker" server DNS code: it hasn't been default
11945 since 0.1.2.2-alpha, and all the servers seem to be using the new
11948 o Minor bugfixes (portability):
11949 - Even though Windows is equally happy with / and \ as path separators,
11950 try to use \ consistently on Windows and / consistently on Unix: it
11951 makes the log messages nicer.
11952 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11953 - Read resolv.conf files correctly on platforms where read() returns
11954 partial results on small file reads.
11956 o Minor bugfixes (directory):
11957 - Correctly enforce that elements of directory objects do not appear
11958 more often than they are allowed to appear.
11959 - When we are reporting the DirServer line we just parsed, we were
11960 logging the second stanza of the key fingerprint, not the first.
11962 o Minor bugfixes (logging):
11963 - When we hit an EOF on a log (probably because we're shutting down),
11964 don't try to remove the log from the list: just mark it as
11965 unusable. (Bulletproofs against bug 222.)
11967 o Minor bugfixes (other):
11968 - In the exitlist script, only consider the most recently published
11969 server descriptor for each server. Also, when the user requests
11970 a list of servers that _reject_ connections to a given address,
11971 explicitly exclude the IPs that also have servers that accept
11972 connections to that address. (Resolves bug 405.)
11973 - Stop allowing hibernating servers to be "stable" or "fast".
11974 - On Windows, we were preventing other processes from reading
11975 cached-routers while Tor was running. (Reported by janbar)
11976 - Make the NodeFamilies config option work. (Reported by
11977 lodger -- it has never actually worked, even though we added it
11979 - Check return values from pthread_mutex functions.
11980 - Don't save non-general-purpose router descriptors to the disk cache,
11981 because we have no way of remembering what their purpose was when
11983 - Add even more asserts to hunt down bug 417.
11984 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
11985 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
11986 Add a log message to confirm that it is in fact unlikely.
11988 o Minor bugfixes (controller):
11989 - Make 'getinfo fingerprint' return a 551 error if we're not a
11990 server, so we match what the control spec claims we do. Reported
11992 - Fix a typo in an error message when extendcircuit fails that
11993 caused us to not follow the \r\n-based delimiter protocol. Reported
11996 o Code simplifications and refactoring:
11997 - Stop passing around circuit_t and crypt_path_t pointers that are
11998 implicit in other procedure arguments.
11999 - Drop the old code to choke directory connections when the
12000 corresponding OR connections got full: thanks to the cell queue
12001 feature, OR conns don't get full any more.
12002 - Make dns_resolve() handle attaching connections to circuits
12003 properly, so the caller doesn't have to.
12004 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
12005 - Keep the connection array as a dynamic smartlist_t, rather than as
12006 a fixed-sized array. This is important, as the number of connections
12007 is becoming increasingly decoupled from the number of sockets.
12010 Changes in version 0.1.2.14 - 2007-05-25
12011 Tor 0.1.2.14 changes the addresses of two directory authorities (this
12012 change especially affects those who serve or use hidden services),
12013 and fixes several other crash- and security-related bugs.
12015 o Directory authority changes:
12016 - Two directory authorities (moria1 and moria2) just moved to new
12017 IP addresses. This change will particularly affect those who serve
12018 or use hidden services.
12020 o Major bugfixes (crashes):
12021 - If a directory server runs out of space in the connection table
12022 as it's processing a begin_dir request, it will free the exit stream
12023 but leave it attached to the circuit, leading to unpredictable
12024 behavior. (Reported by seeess, fixes bug 425.)
12025 - Fix a bug in dirserv_remove_invalid() that would cause authorities
12026 to corrupt memory under some really unlikely scenarios.
12027 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
12028 - Avoid segfaults when reading from mmaped descriptor file. (Reported
12031 o Major bugfixes (security):
12032 - When choosing an entry guard for a circuit, avoid using guards
12033 that are in the same family as the chosen exit -- not just guards
12034 that are exactly the chosen exit. (Reported by lodger.)
12036 o Major bugfixes (resource management):
12037 - If a directory authority is down, skip it when deciding where to get
12038 networkstatus objects or descriptors. Otherwise we keep asking
12039 every 10 seconds forever. Fixes bug 384.
12040 - Count it as a failure if we fetch a valid network-status but we
12041 don't want to keep it. Otherwise we'll keep fetching it and keep
12042 not wanting to keep it. Fixes part of bug 422.
12043 - If all of our dirservers have given us bad or no networkstatuses
12044 lately, then stop hammering them once per minute even when we
12045 think they're failed. Fixes another part of bug 422.
12048 - Actually set the purpose correctly for descriptors inserted with
12049 purpose=controller.
12050 - When we have k non-v2 authorities in our DirServer config,
12051 we ignored the last k authorities in the list when updating our
12053 - Correctly back-off from requesting router descriptors that we are
12054 having a hard time downloading.
12055 - Read resolv.conf files correctly on platforms where read() returns
12056 partial results on small file reads.
12057 - Don't rebuild the entire router store every time we get 32K of
12058 routers: rebuild it when the journal gets very large, or when
12059 the gaps in the store get very large.
12062 - When routers publish SVN revisions in their router descriptors,
12063 authorities now include those versions correctly in networkstatus
12065 - Warn when using a version of libevent before 1.3b to run a server on
12066 OSX or BSD: these versions interact badly with userspace threads.
12069 Changes in version 0.1.2.13 - 2007-04-24
12070 This release features some major anonymity fixes, such as safer path
12071 selection; better client performance; faster bootstrapping, better
12072 address detection, and better DNS support for servers; write limiting as
12073 well as read limiting to make servers easier to run; and a huge pile of
12074 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
12076 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
12077 of the Freenode IRC network, remembering his patience and vision for
12078 free speech on the Internet.
12081 - Fix a memory leak when we ask for "all" networkstatuses and we
12082 get one we don't recognize.
12083 - Add more asserts to hunt down bug 417.
12084 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
12087 Changes in version 0.1.2.12-rc - 2007-03-16
12089 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
12090 directory information requested inside Tor connections (i.e. via
12091 begin_dir cells). It only triggered when the same connection was
12092 serving other data at the same time. Reported by seeess.
12095 - When creating a circuit via the controller, send a 'launched'
12096 event when we're done, so we follow the spec better.
12099 Changes in version 0.1.2.11-rc - 2007-03-15
12100 o Minor bugfixes (controller), reported by daejees:
12101 - Correct the control spec to match how the code actually responds
12102 to 'getinfo addr-mappings/*'.
12103 - The control spec described a GUARDS event, but the code
12104 implemented a GUARD event. Standardize on GUARD, but let people
12105 ask for GUARDS too.
12108 Changes in version 0.1.2.10-rc - 2007-03-07
12109 o Major bugfixes (Windows):
12110 - Do not load the NT services library functions (which may not exist)
12111 just to detect if we're a service trying to shut down. Now we run
12112 on Win98 and friends again.
12114 o Minor bugfixes (other):
12115 - Clarify a couple of log messages.
12116 - Fix a misleading socks5 error number.
12119 Changes in version 0.1.2.9-rc - 2007-03-02
12120 o Major bugfixes (Windows):
12121 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
12122 of the usual GCC "%llu". This prevents a bug when saving 64-bit
12123 int configuration values: the high-order 32 bits would get
12124 truncated. In particular, we were being bitten by the default
12125 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
12126 and maybe also bug 397.)
12128 o Minor bugfixes (performance):
12129 - Use OpenSSL's AES implementation on platforms where it's faster.
12130 This could save us as much as 10% CPU usage.
12132 o Minor bugfixes (server):
12133 - Do not rotate onion key immediately after setting it for the first
12136 o Minor bugfixes (directory authorities):
12137 - Stop calling servers that have been hibernating for a long time
12138 "stable". Also, stop letting hibernating or obsolete servers affect
12139 uptime and bandwidth cutoffs.
12140 - Stop listing hibernating servers in the v1 directory.
12142 o Minor bugfixes (hidden services):
12143 - Upload hidden service descriptors slightly less often, to reduce
12144 load on authorities.
12146 o Minor bugfixes (other):
12147 - Fix an assert that could trigger if a controller quickly set then
12148 cleared EntryNodes. Bug found by Udo van den Heuvel.
12149 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
12151 - Fix a potential race condition in the rpm installer. Found by
12153 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
12154 of 2 as indicating that the server is completely bad; it sometimes
12155 means that the server is just bad for the request in question. (may fix
12156 the last of bug 326.)
12157 - Disable encrypted directory connections when we don't have a server
12158 descriptor for the destination. We'll get this working again in
12162 Changes in version 0.1.2.8-beta - 2007-02-26
12163 o Major bugfixes (crashes):
12164 - Stop crashing when the controller asks us to resetconf more than
12165 one config option at once. (Vidalia 0.0.11 does this.)
12166 - Fix a crash that happened on Win98 when we're given command-line
12167 arguments: don't try to load NT service functions from advapi32.dll
12168 except when we need them. (Bug introduced in 0.1.2.7-alpha;
12170 - Fix a longstanding obscure crash bug that could occur when
12171 we run out of DNS worker processes. (Resolves bug 390.)
12173 o Major bugfixes (hidden services):
12174 - Correctly detect whether hidden service descriptor downloads are
12175 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
12177 o Major bugfixes (accounting):
12178 - When we start during an accounting interval before it's time to wake
12179 up, remember to wake up at the correct time. (May fix bug 342.)
12181 o Minor bugfixes (controller):
12182 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
12183 clear the corresponding on_circuit variable, and remember later
12184 that we don't need to send a redundant CLOSED event. Resolves part
12186 - Report events where a resolve succeeded or where we got a socks
12187 protocol error correctly, rather than calling both of them
12189 - Change reported stream target addresses to IP consistently when
12190 we finally get the IP from an exit node.
12191 - Send log messages to the controller even if they happen to be very
12194 o Minor bugfixes (other):
12195 - Display correct results when reporting which versions are
12196 recommended, and how recommended they are. (Resolves bug 383.)
12197 - Improve our estimates for directory bandwidth to be less random:
12198 guess that an unrecognized directory will have the average bandwidth
12199 from all known directories, not that it will have the average
12200 bandwidth from those directories earlier than it on the list.
12201 - If we start a server with ClientOnly 1, then set ClientOnly to 0
12202 and hup, stop triggering an assert based on an empty onion_key.
12203 - On platforms with no working mmap() equivalent, don't warn the
12204 user when cached-routers doesn't exist.
12205 - Warn the user when mmap() [or its equivalent] fails for some reason
12206 other than file-not-found.
12207 - Don't warn the user when cached-routers.new doesn't exist: that's
12208 perfectly fine when starting up for the first time.
12209 - When EntryNodes are configured, rebuild the guard list to contain,
12210 in order: the EntryNodes that were guards before; the rest of the
12211 EntryNodes; the nodes that were guards before.
12212 - Mask out all signals in sub-threads; only the libevent signal
12213 handler should be processing them. This should prevent some crashes
12214 on some machines using pthreads. (Patch from coderman.)
12215 - Fix switched arguments on memset in the implementation of
12216 tor_munmap() for systems with no mmap() call.
12217 - When Tor receives a router descriptor that it asked for, but
12218 no longer wants (because it has received fresh networkstatuses
12219 in the meantime), do not warn the user. Cache the descriptor if
12220 we're a cache; drop it if we aren't.
12221 - Make earlier entry guards _really_ get retried when the network
12223 - On a malformed DNS reply, always give an error to the corresponding
12225 - Build with recent libevents on platforms that do not define the
12226 nonstandard types "u_int8_t" and friends.
12228 o Minor features (controller):
12229 - Warn the user when an application uses the obsolete binary v0
12230 control protocol. We're planning to remove support for it during
12231 the next development series, so it's good to give people some
12233 - Add STREAM_BW events to report per-entry-stream bandwidth
12234 use. (Patch from Robert Hogan.)
12235 - Rate-limit SIGNEWNYM signals in response to controllers that
12236 impolitely generate them for every single stream. (Patch from
12237 mwenge; closes bug 394.)
12238 - Make REMAP stream events have a SOURCE (cache or exit), and
12239 make them generated in every case where we get a successful
12240 connected or resolved cell.
12242 o Minor bugfixes (performance):
12243 - Call router_have_min_dir_info half as often. (This is showing up in
12244 some profiles, but not others.)
12245 - When using GCC, make log_debug never get called at all, and its
12246 arguments never get evaluated, when no debug logs are configured.
12247 (This is showing up in some profiles, but not others.)
12250 - Remove some never-implemented options. Mark PathlenCoinWeight as
12252 - Implement proposal 106: Stop requiring clients to have well-formed
12253 certificates; stop checking nicknames in certificates. (Clients
12254 have certificates so that they can look like Tor servers, but in
12255 the future we might want to allow them to look like regular TLS
12256 clients instead. Nicknames in certificates serve no purpose other
12257 than making our protocol easier to recognize on the wire.)
12258 - Revise messages on handshake failure again to be even more clear about
12259 which are incoming connections and which are outgoing.
12260 - Discard any v1 directory info that's over 1 month old (for
12261 directories) or over 1 week old (for running-routers lists).
12262 - Do not warn when individual nodes in the configuration's EntryNodes,
12263 ExitNodes, etc are down: warn only when all possible nodes
12264 are down. (Fixes bug 348.)
12265 - Always remove expired routers and networkstatus docs before checking
12266 whether we have enough information to build circuits. (Fixes
12268 - Put a lower-bound on MaxAdvertisedBandwidth.
12271 Changes in version 0.1.2.7-alpha - 2007-02-06
12272 o Major bugfixes (rate limiting):
12273 - Servers decline directory requests much more aggressively when
12274 they're low on bandwidth. Otherwise they end up queueing more and
12275 more directory responses, which can't be good for latency.
12276 - But never refuse directory requests from local addresses.
12277 - Fix a memory leak when sending a 503 response for a networkstatus
12279 - Be willing to read or write on local connections (e.g. controller
12280 connections) even when the global rate limiting buckets are empty.
12281 - If our system clock jumps back in time, don't publish a negative
12282 uptime in the descriptor. Also, don't let the global rate limiting
12283 buckets go absurdly negative.
12284 - Flush local controller connection buffers periodically as we're
12285 writing to them, so we avoid queueing 4+ megabytes of data before
12288 o Major bugfixes (NT services):
12289 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
12290 command-line flag so that admins can override the default by saying
12291 "tor --service install --user "SomeUser"". This will not affect
12292 existing installed services. Also, warn the user that the service
12293 will look for its configuration file in the service user's
12294 %appdata% directory. (We can't do the 'hardwire the user's appdata
12295 directory' trick any more, since we may not have read access to that
12298 o Major bugfixes (other):
12299 - Previously, we would cache up to 16 old networkstatus documents
12300 indefinitely, if they came from nontrusted authorities. Now we
12301 discard them if they are more than 10 days old.
12302 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
12304 - Detect and reject malformed DNS responses containing circular
12306 - If exits are rare enough that we're not marking exits as guards,
12307 ignore exit bandwidth when we're deciding the required bandwidth
12309 - When we're handling a directory connection tunneled over Tor,
12310 don't fill up internal memory buffers with all the data we want
12311 to tunnel; instead, only add it if the OR connection that will
12312 eventually receive it has some room for it. (This can lead to
12313 slowdowns in tunneled dir connections; a better solution will have
12314 to wait for 0.2.0.)
12316 o Minor bugfixes (dns):
12317 - Add some defensive programming to eventdns.c in an attempt to catch
12318 possible memory-stomping bugs.
12319 - Detect and reject DNS replies containing IPv4 or IPv6 records with
12320 an incorrect number of bytes. (Previously, we would ignore the
12322 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
12323 in the correct order, and doesn't crash.
12324 - Free memory held in recently-completed DNS lookup attempts on exit.
12325 This was not a memory leak, but may have been hiding memory leaks.
12326 - Handle TTL values correctly on reverse DNS lookups.
12327 - Treat failure to parse resolv.conf as an error.
12329 o Minor bugfixes (other):
12330 - Fix crash with "tor --list-fingerprint" (reported by seeess).
12331 - When computing clock skew from directory HTTP headers, consider what
12332 time it was when we finished asking for the directory, not what
12334 - Expire socks connections if they spend too long waiting for the
12335 handshake to finish. Previously we would let them sit around for
12336 days, if the connecting application didn't close them either.
12337 - And if the socks handshake hasn't started, don't send a
12338 "DNS resolve socks failed" handshake reply; just close it.
12339 - Stop using C functions that OpenBSD's linker doesn't like.
12340 - Don't launch requests for descriptors unless we have networkstatuses
12341 from at least half of the authorities. This delays the first
12342 download slightly under pathological circumstances, but can prevent
12343 us from downloading a bunch of descriptors we don't need.
12344 - Do not log IPs with TLS failures for incoming TLS
12345 connections. (Fixes bug 382.)
12346 - If the user asks to use invalid exit nodes, be willing to use
12348 - Stop using the reserved ac_cv namespace in our configure script.
12349 - Call stat() slightly less often; use fstat() when possible.
12350 - Refactor the way we handle pending circuits when an OR connection
12351 completes or fails, in an attempt to fix a rare crash bug.
12352 - Only rewrite a conn's address based on X-Forwarded-For: headers
12353 if it's a parseable public IP address; and stop adding extra quotes
12354 to the resulting address.
12357 - Weight directory requests by advertised bandwidth. Now we can
12358 let servers enable write limiting but still allow most clients to
12359 succeed at their directory requests. (We still ignore weights when
12360 choosing a directory authority; I hope this is a feature.)
12363 - Create a new file ReleaseNotes which was the old ChangeLog. The
12364 new ChangeLog file now includes the summaries for all development
12366 - Check for addresses with invalid characters at the exit as well
12367 as at the client, and warn less verbosely when they fail. You can
12368 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
12369 - Adapt a patch from goodell to let the contrib/exitlist script
12370 take arguments rather than require direct editing.
12371 - Inform the server operator when we decide not to advertise a
12372 DirPort due to AccountingMax enabled or a low BandwidthRate. It
12373 was confusing Zax, so now we're hopefully more helpful.
12374 - Bring us one step closer to being able to establish an encrypted
12375 directory tunnel without knowing a descriptor first. Still not
12376 ready yet. As part of the change, now assume we can use a
12377 create_fast cell if we don't know anything about a router.
12378 - Allow exit nodes to use nameservers running on ports other than 53.
12379 - Servers now cache reverse DNS replies.
12380 - Add an --ignore-missing-torrc command-line option so that we can
12381 get the "use sensible defaults if the configuration file doesn't
12382 exist" behavior even when specifying a torrc location on the command
12385 o Minor features (controller):
12386 - Track reasons for OR connection failure; make these reasons
12387 available via the controller interface. (Patch from Mike Perry.)
12388 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
12389 can learn when clients are sending malformed hostnames to Tor.
12390 - Clean up documentation for controller status events.
12391 - Add a REMAP status to stream events to note that a stream's
12392 address has changed because of a cached address or a MapAddress
12396 Changes in version 0.1.2.6-alpha - 2007-01-09
12398 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
12399 connection handles more than 4 gigs in either direction, we crash.
12400 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
12401 advertised exit node, somebody might try to exit from us when
12402 we're bootstrapping and before we've built our descriptor yet.
12403 Refuse the connection rather than crashing.
12406 - Warn if we (as a server) find that we've resolved an address that we
12407 weren't planning to resolve.
12408 - Warn that using select() on any libevent version before 1.1 will be
12409 unnecessarily slow (even for select()).
12410 - Flush ERR-level controller status events just like we currently
12411 flush ERR-level log events, so that a Tor shutdown doesn't prevent
12412 the controller from learning about current events.
12414 o Minor features (more controller status events):
12415 - Implement EXTERNAL_ADDRESS server status event so controllers can
12416 learn when our address changes.
12417 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
12418 can learn when directories reject our descriptor.
12419 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
12420 can learn when a client application is speaking a non-socks protocol
12422 - Implement DANGEROUS_SOCKS client status event so controllers
12423 can learn when a client application is leaking DNS addresses.
12424 - Implement BUG general status event so controllers can learn when
12425 Tor is unhappy about its internal invariants.
12426 - Implement CLOCK_SKEW general status event so controllers can learn
12427 when Tor thinks the system clock is set incorrectly.
12428 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
12429 server status events so controllers can learn when their descriptors
12430 are accepted by a directory.
12431 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
12432 server status events so controllers can learn about Tor's progress in
12433 deciding whether it's reachable from the outside.
12434 - Implement BAD_LIBEVENT general status event so controllers can learn
12435 when we have a version/method combination in libevent that needs to
12437 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
12438 and DNS_USELESS server status events so controllers can learn
12439 about changes to DNS server status.
12441 o Minor features (directory):
12442 - Authorities no longer recommend exits as guards if this would shift
12443 too much load to the exit nodes.
12446 Changes in version 0.1.2.5-alpha - 2007-01-06
12448 - Enable write limiting as well as read limiting. Now we sacrifice
12449 capacity if we're pushing out lots of directory traffic, rather
12450 than overrunning the user's intended bandwidth limits.
12451 - Include TLS overhead when counting bandwidth usage; previously, we
12452 would count only the bytes sent over TLS, but not the bytes used
12454 - Support running the Tor service with a torrc not in the same
12455 directory as tor.exe and default to using the torrc located in
12456 the %appdata%\Tor\ of the user who installed the service. Patch
12458 - Servers now check for the case when common DNS requests are going to
12459 wildcarded addresses (i.e. all getting the same answer), and change
12460 their exit policy to reject *:* if it's happening.
12461 - Implement BEGIN_DIR cells, so we can connect to the directory
12462 server via TLS to do encrypted directory requests rather than
12463 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
12464 config options if you like.
12466 o Minor features (config and docs):
12467 - Start using the state file to store bandwidth accounting data:
12468 the bw_accounting file is now obsolete. We'll keep generating it
12469 for a while for people who are still using 0.1.2.4-alpha.
12470 - Try to batch changes to the state file so that we do as few
12471 disk writes as possible while still storing important things in
12473 - The state file and the bw_accounting file get saved less often when
12474 the AvoidDiskWrites config option is set.
12475 - Make PIDFile work on Windows (untested).
12476 - Add internal descriptions for a bunch of configuration options:
12477 accessible via controller interface and in comments in saved
12479 - Reject *:563 (NNTPS) in the default exit policy. We already reject
12480 NNTP by default, so this seems like a sensible addition.
12481 - Clients now reject hostnames with invalid characters. This should
12482 avoid some inadvertent info leaks. Add an option
12483 AllowNonRFC953Hostnames to disable this behavior, in case somebody
12484 is running a private network with hosts called @, !, and #.
12485 - Add a maintainer script to tell us which options are missing
12486 documentation: "make check-docs".
12487 - Add a new address-spec.txt document to describe our special-case
12488 addresses: .exit, .onion, and .noconnnect.
12490 o Minor features (DNS):
12491 - Ongoing work on eventdns infrastructure: now it has dns server
12492 and ipv6 support. One day Tor will make use of it.
12493 - Add client-side caching for reverse DNS lookups.
12494 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
12495 - When we change nameservers or IP addresses, reset and re-launch
12496 our tests for DNS hijacking.
12498 o Minor features (directory):
12499 - Authorities now specify server versions in networkstatus. This adds
12500 about 2% to the size of compressed networkstatus docs, and allows
12501 clients to tell which servers support BEGIN_DIR and which don't.
12502 The implementation is forward-compatible with a proposed future
12503 protocol version scheme not tied to Tor versions.
12504 - DirServer configuration lines now have an orport= option so
12505 clients can open encrypted tunnels to the authorities without
12506 having downloaded their descriptors yet. Enabled for moria1,
12507 moria2, tor26, and lefkada now in the default configuration.
12508 - Directory servers are more willing to send a 503 "busy" if they
12509 are near their write limit, especially for v1 directory requests.
12510 Now they can use their limited bandwidth for actual Tor traffic.
12511 - Clients track responses with status 503 from dirservers. After a
12512 dirserver has given us a 503, we try not to use it until an hour has
12513 gone by, or until we have no dirservers that haven't given us a 503.
12514 - When we get a 503 from a directory, and we're not a server, we don't
12515 count the failure against the total number of failures allowed
12516 for the thing we're trying to download.
12517 - Report X-Your-Address-Is correctly from tunneled directory
12518 connections; don't report X-Your-Address-Is when it's an internal
12519 address; and never believe reported remote addresses when they're
12521 - Protect against an unlikely DoS attack on directory servers.
12522 - Add a BadDirectory flag to network status docs so that authorities
12523 can (eventually) tell clients about caches they believe to be
12526 o Minor features (controller):
12527 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
12528 - Reimplement GETINFO so that info/names stays in sync with the
12530 - Implement "GETINFO fingerprint".
12531 - Implement "SETEVENTS GUARD" so controllers can get updates on
12532 entry guard status as it changes.
12534 o Minor features (clean up obsolete pieces):
12535 - Remove some options that have been deprecated since at least
12536 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
12537 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
12538 to set log options.
12539 - We no longer look for identity and onion keys in "identity.key" and
12540 "onion.key" -- these were replaced by secret_id_key and
12541 secret_onion_key in 0.0.8pre1.
12542 - We no longer require unrecognized directory entries to be
12545 o Major bugfixes (security):
12546 - Stop sending the HttpProxyAuthenticator string to directory
12547 servers when directory connections are tunnelled through Tor.
12548 - Clients no longer store bandwidth history in the state file.
12549 - Do not log introduction points for hidden services if SafeLogging
12551 - When generating bandwidth history, round down to the nearest
12552 1k. When storing accounting data, round up to the nearest 1k.
12553 - When we're running as a server, remember when we last rotated onion
12554 keys, so that we will rotate keys once they're a week old even if
12555 we never stay up for a week ourselves.
12557 o Major bugfixes (other):
12558 - Fix a longstanding bug in eventdns that prevented the count of
12559 timed-out resolves from ever being reset. This bug caused us to
12560 give up on a nameserver the third time it timed out, and try it
12561 10 seconds later... and to give up on it every time it timed out
12563 - Take out the '5 second' timeout from the connection retry
12564 schedule. Now the first connect attempt will wait a full 10
12565 seconds before switching to a new circuit. Perhaps this will help
12566 a lot. Based on observations from Mike Perry.
12567 - Fix a bug on the Windows implementation of tor_mmap_file() that
12568 would prevent the cached-routers file from ever loading. Reported
12572 - Fix an assert failure when a directory authority sets
12573 AuthDirRejectUnlisted and then receives a descriptor from an
12574 unlisted router. Reported by seeess.
12575 - Avoid a double-free when parsing malformed DirServer lines.
12576 - Fix a bug when a BSD-style PF socket is first used. Patch from
12578 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
12579 to resolve an address at a given exit node even when they ask for
12581 - Servers no longer ever list themselves in their "family" line,
12582 even if configured to do so. This makes it easier to configure
12583 family lists conveniently.
12584 - When running as a server, don't fall back to 127.0.0.1 when no
12585 nameservers are configured in /etc/resolv.conf; instead, make the
12586 user fix resolv.conf or specify nameservers explicitly. (Resolves
12588 - Stop accepting certain malformed ports in configured exit policies.
12589 - Don't re-write the fingerprint file every restart, unless it has
12591 - Stop warning when a single nameserver fails: only warn when _all_ of
12592 our nameservers have failed. Also, when we only have one nameserver,
12593 raise the threshold for deciding that the nameserver is dead.
12594 - Directory authorities now only decide that routers are reachable
12595 if their identity keys are as expected.
12596 - When the user uses bad syntax in the Log config line, stop
12597 suggesting other bad syntax as a replacement.
12598 - Correctly detect ipv6 DNS capability on OpenBSD.
12600 o Minor bugfixes (controller):
12601 - Report the circuit number correctly in STREAM CLOSED events. Bug
12602 reported by Mike Perry.
12603 - Do not report bizarre values for results of accounting GETINFOs
12604 when the last second's write or read exceeds the allotted bandwidth.
12605 - Report "unrecognized key" rather than an empty string when the
12606 controller tries to fetch a networkstatus that doesn't exist.
12609 Changes in version 0.1.1.26 - 2006-12-14
12610 o Security bugfixes:
12611 - Stop sending the HttpProxyAuthenticator string to directory
12612 servers when directory connections are tunnelled through Tor.
12613 - Clients no longer store bandwidth history in the state file.
12614 - Do not log introduction points for hidden services if SafeLogging
12618 - Fix an assert failure when a directory authority sets
12619 AuthDirRejectUnlisted and then receives a descriptor from an
12620 unlisted router (reported by seeess).
12623 Changes in version 0.1.2.4-alpha - 2006-12-03
12625 - Add support for using natd; this allows FreeBSDs earlier than
12626 5.1.2 to have ipfw send connections through Tor without using
12627 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
12630 - Make all connections to addresses of the form ".noconnect"
12631 immediately get closed. This lets application/controller combos
12632 successfully test whether they're talking to the same Tor by
12633 watching for STREAM events.
12634 - Make cross.sh cross-compilation script work even when autogen.sh
12635 hasn't been run. (Patch from Michael Mohr.)
12636 - Statistics dumped by -USR2 now include a breakdown of public key
12637 operations, for profiling.
12640 - Fix a major leak when directory authorities parse their
12641 approved-routers list, a minor memory leak when we fail to pick
12642 an exit node, and a few rare leaks on errors.
12643 - Handle TransPort connections even when the server sends data before
12644 the client sends data. Previously, the connection would just hang
12645 until the client sent data. (Patch from tup based on patch from
12647 - Avoid assert failure when our cached-routers file is empty on
12651 - Don't log spurious warnings when we see a circuit close reason we
12652 don't recognize; it's probably just from a newer version of Tor.
12653 - Have directory authorities allow larger amounts of drift in uptime
12654 without replacing the server descriptor: previously, a server that
12655 restarted every 30 minutes could have 48 "interesting" descriptors
12657 - Start linking to the Tor specification and Tor reference manual
12658 correctly in the Windows installer.
12659 - Add Vidalia to the OS X uninstaller script, so when we uninstall
12660 Tor/Privoxy we also uninstall Vidalia.
12661 - Resume building on Irix64, and fix a lot of warnings from its
12662 MIPSpro C compiler.
12663 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
12664 when we're running as a client.
12667 Changes in version 0.1.1.25 - 2006-11-04
12669 - When a client asks us to resolve (rather than connect to)
12670 an address, and we have a cached answer, give them the cached
12671 answer. Previously, we would give them no answer at all.
12672 - We were building exactly the wrong circuits when we predict
12673 hidden service requirements, meaning Tor would have to build all
12674 its circuits on demand.
12675 - If none of our live entry guards have a high uptime, but we
12676 require a guard with a high uptime, try adding a new guard before
12677 we give up on the requirement. This patch should make long-lived
12678 connections more stable on average.
12679 - When testing reachability of our DirPort, don't launch new
12680 tests when there's already one in progress -- unreachable
12681 servers were stacking up dozens of testing streams.
12683 o Security bugfixes:
12684 - When the user sends a NEWNYM signal, clear the client-side DNS
12685 cache too. Otherwise we continue to act on previous information.
12688 - Avoid a memory corruption bug when creating a hash table for
12690 - Avoid possibility of controller-triggered crash when misusing
12691 certain commands from a v0 controller on platforms that do not
12692 handle printf("%s",NULL) gracefully.
12693 - Avoid infinite loop on unexpected controller input.
12694 - Don't log spurious warnings when we see a circuit close reason we
12695 don't recognize; it's probably just from a newer version of Tor.
12696 - Add Vidalia to the OS X uninstaller script, so when we uninstall
12697 Tor/Privoxy we also uninstall Vidalia.
12700 Changes in version 0.1.2.3-alpha - 2006-10-29
12702 - Prepare for servers to publish descriptors less often: never
12703 discard a descriptor simply for being too old until either it is
12704 recommended by no authorities, or until we get a better one for
12705 the same router. Make caches consider retaining old recommended
12706 routers for even longer.
12707 - If most authorities set a BadExit flag for a server, clients
12708 don't think of it as a general-purpose exit. Clients only consider
12709 authorities that advertise themselves as listing bad exits.
12710 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
12711 headers for content, so that we can work better in the presence of
12712 caching HTTP proxies.
12713 - Allow authorities to list nodes as bad exits by fingerprint or by
12716 o Minor features, controller:
12717 - Add a REASON field to CIRC events; for backward compatibility, this
12718 field is sent only to controllers that have enabled the extended
12719 event format. Also, add additional reason codes to explain why
12720 a given circuit has been destroyed or truncated. (Patches from
12722 - Add a REMOTE_REASON field to extended CIRC events to tell the
12723 controller about why a remote OR told us to close a circuit.
12724 - Stream events also now have REASON and REMOTE_REASON fields,
12725 working much like those for circuit events.
12726 - There's now a GETINFO ns/... field so that controllers can ask Tor
12727 about the current status of a router.
12728 - A new event type "NS" to inform a controller when our opinion of
12729 a router's status has changed.
12730 - Add a GETINFO events/names and GETINFO features/names so controllers
12731 can tell which events and features are supported.
12732 - A new CLEARDNSCACHE signal to allow controllers to clear the
12733 client-side DNS cache without expiring circuits.
12735 o Security bugfixes:
12736 - When the user sends a NEWNYM signal, clear the client-side DNS
12737 cache too. Otherwise we continue to act on previous information.
12740 - Avoid sending junk to controllers or segfaulting when a controller
12741 uses EVENT_NEW_DESC with verbose nicknames.
12742 - Stop triggering asserts if the controller tries to extend hidden
12743 service circuits (reported by mwenge).
12744 - Avoid infinite loop on unexpected controller input.
12745 - When the controller does a "GETINFO network-status", tell it
12746 about even those routers whose descriptors are very old, and use
12747 long nicknames where appropriate.
12748 - Change NT service functions to be loaded on demand. This lets us
12749 build with MinGW without breaking Tor for Windows 98 users.
12750 - Do DirPort reachability tests less often, since a single test
12751 chews through many circuits before giving up.
12752 - In the hidden service example in torrc.sample, stop recommending
12753 esoteric and discouraged hidden service options.
12754 - When stopping an NT service, wait up to 10 sec for it to actually
12755 stop. Patch from Matt Edman; resolves bug 295.
12756 - Fix handling of verbose nicknames with ORCONN controller events:
12757 make them show up exactly when requested, rather than exactly when
12759 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
12760 printing a duplicate "$" in the keys we send (reported by mwenge).
12761 - Correctly set maximum connection limit on Cygwin. (This time
12763 - Try to detect Windows correctly when cross-compiling.
12764 - Detect the size of the routers file correctly even if it is
12765 corrupted (on systems without mmap) or not page-aligned (on systems
12766 with mmap). This bug was harmless.
12767 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
12768 to open a stream fails; now we do in more cases. This should
12769 make clients able to find a good exit faster in some cases, since
12770 unhandleable requests will now get an error rather than timing out.
12771 - Resolve two memory leaks when rebuilding the on-disk router cache
12772 (reported by fookoowa).
12773 - Clean up minor code warnings suggested by the MIPSpro C compiler,
12774 and reported by some Centos users.
12775 - Controller signals now work on non-Unix platforms that don't define
12776 SIGUSR1 and SIGUSR2 the way we expect.
12777 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
12778 values before failing, and always enables eventdns.
12779 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
12780 Try to fix this in configure.in by checking for most functions
12781 before we check for libevent.
12784 Changes in version 0.1.2.2-alpha - 2006-10-07
12786 - Make our async eventdns library on-by-default for Tor servers,
12787 and plan to deprecate the separate dnsworker threads.
12788 - Add server-side support for "reverse" DNS lookups (using PTR
12789 records so clients can determine the canonical hostname for a given
12790 IPv4 address). Only supported by servers using eventdns; servers
12791 now announce in their descriptors whether they support eventdns.
12792 - Specify and implement client-side SOCKS5 interface for reverse DNS
12793 lookups (see doc/socks-extensions.txt).
12794 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
12795 connect to directory servers through Tor. Previously, clients needed
12796 to find Tor exits to make private connections to directory servers.
12797 - Avoid choosing Exit nodes for entry or middle hops when the
12798 total bandwidth available from non-Exit nodes is much higher than
12799 the total bandwidth available from Exit nodes.
12800 - Workaround for name servers (like Earthlink's) that hijack failing
12801 DNS requests and replace the no-such-server answer with a "helpful"
12802 redirect to an advertising-driven search portal. Also work around
12803 DNS hijackers who "helpfully" decline to hijack known-invalid
12804 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
12805 lets you turn it off.
12806 - Send out a burst of long-range padding cells once we've established
12807 that we're reachable. Spread them over 4 circuits, so hopefully
12808 a few will be fast. This exercises our bandwidth and bootstraps
12809 us into the directory more quickly.
12811 o New/improved config options:
12812 - Add new config option "ResolvConf" to let the server operator
12813 choose an alternate resolve.conf file when using eventdns.
12814 - Add an "EnforceDistinctSubnets" option to control our "exclude
12815 servers on the same /16" behavior. It's still on by default; this
12816 is mostly for people who want to operate private test networks with
12817 all the machines on the same subnet.
12818 - If one of our entry guards is on the ExcludeNodes list, or the
12819 directory authorities don't think it's a good guard, treat it as
12820 if it were unlisted: stop using it as a guard, and throw it off
12821 the guards list if it stays that way for a long time.
12822 - Allow directory authorities to be marked separately as authorities
12823 for the v1 directory protocol, the v2 directory protocol, and
12824 as hidden service directories, to make it easier to retire old
12825 authorities. V1 authorities should set "HSAuthoritativeDir 1"
12826 to continue being hidden service authorities too.
12827 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
12829 o Minor features, controller:
12830 - Fix CIRC controller events so that controllers can learn the
12831 identity digests of non-Named servers used in circuit paths.
12832 - Let controllers ask for more useful identifiers for servers. Instead
12833 of learning identity digests for un-Named servers and nicknames
12834 for Named servers, the new identifiers include digest, nickname,
12835 and indication of Named status. Off by default; see control-spec.txt
12836 for more information.
12837 - Add a "getinfo address" controller command so it can display Tor's
12838 best guess to the user.
12839 - New controller event to alert the controller when our server
12840 descriptor has changed.
12841 - Give more meaningful errors on controller authentication failure.
12843 o Minor features, other:
12844 - When asked to resolve a hostname, don't use non-exit servers unless
12845 requested to do so. This allows servers with broken DNS to be
12846 useful to the network.
12847 - Divide eventdns log messages into warn and info messages.
12848 - Reserve the nickname "Unnamed" for routers that can't pick
12849 a hostname: any router can call itself Unnamed; directory
12850 authorities will never allocate Unnamed to any particular router;
12851 clients won't believe that any router is the canonical Unnamed.
12852 - Only include function names in log messages for info/debug messages.
12853 For notice/warn/err, the content of the message should be clear on
12854 its own, and printing the function name only confuses users.
12855 - Avoid some false positives during reachability testing: don't try
12856 to test via a server that's on the same /24 as us.
12857 - If we fail to build a circuit to an intended enclave, and it's
12858 not mandatory that we use that enclave, stop wanting it.
12859 - When eventdns is enabled, allow multithreaded builds on NetBSD and
12860 OpenBSD. (We had previously disabled threads on these platforms
12861 because they didn't have working thread-safe resolver functions.)
12863 o Major bugfixes, anonymity/security:
12864 - If a client asked for a server by name, and there's a named server
12865 in our network-status but we don't have its descriptor yet, we
12866 could return an unnamed server instead.
12867 - Fix NetBSD bug that could allow someone to force uninitialized RAM
12868 to be sent to a server's DNS resolver. This only affects NetBSD
12869 and other platforms that do not bounds-check tolower().
12870 - Reject (most) attempts to use Tor circuits with length one. (If
12871 many people start using Tor as a one-hop proxy, exit nodes become
12872 a more attractive target for compromise.)
12873 - Just because your DirPort is open doesn't mean people should be
12874 able to remotely teach you about hidden service descriptors. Now
12875 only accept rendezvous posts if you've got HSAuthoritativeDir set.
12877 o Major bugfixes, other:
12878 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
12879 - When a client asks the server to resolve (not connect to)
12880 an address, and it has a cached answer, give them the cached answer.
12881 Previously, the server would give them no answer at all.
12882 - Allow really slow clients to not hang up five minutes into their
12883 directory downloads (suggested by Adam J. Richter).
12884 - We were building exactly the wrong circuits when we anticipated
12885 hidden service requirements, meaning Tor would have to build all
12886 its circuits on demand.
12887 - Avoid crashing when we mmap a router cache file of size 0.
12888 - When testing reachability of our DirPort, don't launch new
12889 tests when there's already one in progress -- unreachable
12890 servers were stacking up dozens of testing streams.
12892 o Minor bugfixes, correctness:
12893 - If we're a directory mirror and we ask for "all" network status
12894 documents, we would discard status documents from authorities
12895 we don't recognize.
12896 - Avoid a memory corruption bug when creating a hash table for
12898 - Avoid controller-triggered crash when misusing certain commands
12899 from a v0 controller on platforms that do not handle
12900 printf("%s",NULL) gracefully.
12901 - Don't crash when a controller sends a third argument to an
12902 "extendcircuit" request.
12903 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12904 response; fix error code when "getinfo dir/status/" fails.
12905 - Avoid crash when telling controller stream-status and a stream
12907 - Patch from Adam Langley to fix assert() in eventdns.c.
12908 - Fix a debug log message in eventdns to say "X resolved to Y"
12909 instead of "X resolved to X".
12910 - Make eventdns give strings for DNS errors, not just error numbers.
12911 - Track unreachable entry guards correctly: don't conflate
12912 'unreachable by us right now' with 'listed as down by the directory
12913 authorities'. With the old code, if a guard was unreachable by
12914 us but listed as running, it would clog our guard list forever.
12915 - Behave correctly in case we ever have a network with more than
12916 2GB/s total advertised capacity.
12917 - Make TrackExitHosts case-insensitive, and fix the behavior of
12918 ".suffix" TrackExitHosts items to avoid matching in the middle of
12920 - Finally fix the openssl warnings from newer gccs that believe that
12921 ignoring a return value is okay, but casting a return value and
12922 then ignoring it is a sign of madness.
12923 - Prevent the contrib/exitlist script from printing the same
12924 result more than once.
12925 - Patch from Steve Hildrey: Generate network status correctly on
12926 non-versioning dirservers.
12927 - Don't listen to the X-Your-Address-Is hint if you did the lookup
12928 via Tor; otherwise you'll think you're the exit node's IP address.
12930 o Minor bugfixes, performance:
12931 - Two small performance improvements on parsing descriptors.
12932 - Major performance improvement on inserting descriptors: change
12933 algorithm from O(n^2) to O(n).
12934 - Make the common memory allocation path faster on machines where
12935 malloc(0) returns a pointer.
12936 - Start remembering X-Your-Address-Is directory hints even if you're
12937 a client, so you can become a server more smoothly.
12938 - Avoid duplicate entries on MyFamily line in server descriptor.
12940 o Packaging, features:
12941 - Remove architecture from OS X builds. The official builds are
12942 now universal binaries.
12943 - The Debian package now uses --verify-config when (re)starting,
12944 to distinguish configuration errors from other errors.
12945 - Update RPMs to require libevent 1.1b.
12947 o Packaging, bugfixes:
12948 - Patches so Tor builds with MinGW on Windows.
12949 - Patches so Tor might run on Cygwin again.
12950 - Resume building on non-gcc compilers and ancient gcc. Resume
12951 building with the -O0 compile flag. Resume building cleanly on
12953 - Run correctly on OS X platforms with case-sensitive filesystems.
12954 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
12955 - Add autoconf checks so Tor can build on Solaris x86 again.
12958 - Documented (and renamed) ServerDNSSearchDomains and
12959 ServerDNSResolvConfFile options.
12960 - Be clearer that the *ListenAddress directives can be repeated
12964 Changes in version 0.1.1.24 - 2006-09-29
12966 - Allow really slow clients to not hang up five minutes into their
12967 directory downloads (suggested by Adam J. Richter).
12968 - Fix major performance regression from 0.1.0.x: instead of checking
12969 whether we have enough directory information every time we want to
12970 do something, only check when the directory information has changed.
12971 This should improve client CPU usage by 25-50%.
12972 - Don't crash if, after a server has been running for a while,
12973 it can't resolve its hostname.
12976 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12977 - Don't crash when the controller receives a third argument to an
12978 "extendcircuit" request.
12979 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12980 response; fix error code when "getinfo dir/status/" fails.
12981 - Fix configure.in to not produce broken configure files with
12982 more recent versions of autoconf. Thanks to Clint for his auto*
12984 - Fix security bug on NetBSD that could allow someone to force
12985 uninitialized RAM to be sent to a server's DNS resolver. This
12986 only affects NetBSD and other platforms that do not bounds-check
12988 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12989 methods: these are known to be buggy.
12990 - If we're a directory mirror and we ask for "all" network status
12991 documents, we would discard status documents from authorities
12992 we don't recognize.
12995 Changes in version 0.1.2.1-alpha - 2006-08-27
12997 - Add "eventdns" async dns library from Adam Langley, tweaked to
12998 build on OSX and Windows. Only enabled if you pass the
12999 --enable-eventdns argument to configure.
13000 - Allow servers with no hostname or IP address to learn their
13001 IP address by asking the directory authorities. This code only
13002 kicks in when you would normally have exited with a "no address"
13003 error. Nothing's authenticated, so use with care.
13004 - Rather than waiting a fixed amount of time between retrying
13005 application connections, we wait only 5 seconds for the first,
13006 10 seconds for the second, and 15 seconds for each retry after
13007 that. Hopefully this will improve the expected user experience.
13008 - Patch from Tup to add support for transparent AP connections:
13009 this basically bundles the functionality of trans-proxy-tor
13010 into the Tor mainline. Now hosts with compliant pf/netfilter
13011 implementations can redirect TCP connections straight to Tor
13012 without diverting through SOCKS. Needs docs.
13013 - Busy directory servers save lots of memory by spooling server
13014 descriptors, v1 directories, and v2 networkstatus docs to buffers
13015 as needed rather than en masse. Also mmap the cached-routers
13016 files, so we don't need to keep the whole thing in memory too.
13017 - Automatically avoid picking more than one node from the same
13018 /16 network when constructing a circuit.
13019 - Revise and clean up the torrc.sample that we ship with; add
13020 a section for BandwidthRate and BandwidthBurst.
13023 - Split circuit_t into origin_circuit_t and or_circuit_t, and
13024 split connection_t into edge, or, dir, control, and base structs.
13025 These will save quite a bit of memory on busy servers, and they'll
13026 also help us track down bugs in the code and bugs in the spec.
13027 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
13028 or later. Log when we are doing this, so we can diagnose it when
13029 it fails. (Also, recommend libevent 1.1b for kqueue and
13030 win32 methods; deprecate libevent 1.0b harder; make libevent
13031 recommendation system saner.)
13032 - Start being able to build universal binaries on OS X (thanks
13034 - Export the default exit policy via the control port, so controllers
13035 don't need to guess what it is / will be later.
13036 - Add a man page entry for ProtocolWarnings.
13037 - Add TestVia config option to the man page.
13038 - Remove even more protocol-related warnings from Tor server logs,
13039 such as bad TLS handshakes and malformed begin cells.
13040 - Stop fetching descriptors if you're not a dir mirror and you
13041 haven't tried to establish any circuits lately. [This currently
13042 causes some dangerous behavior, because when you start up again
13043 you'll use your ancient server descriptors.]
13044 - New DirPort behavior: if you have your dirport set, you download
13045 descriptors aggressively like a directory mirror, whether or not
13046 your ORPort is set.
13047 - Get rid of the router_retry_connections notion. Now routers
13048 no longer try to rebuild long-term connections to directory
13049 authorities, and directory authorities no longer try to rebuild
13050 long-term connections to all servers. We still don't hang up
13051 connections in these two cases though -- we need to look at it
13052 more carefully to avoid flapping, and we likely need to wait til
13053 0.1.1.x is obsolete.
13054 - Drop compatibility with obsolete Tors that permit create cells
13055 to have the wrong circ_id_type.
13056 - Re-enable per-connection rate limiting. Get rid of the "OP
13057 bandwidth" concept. Lay groundwork for "bandwidth classes" --
13058 separate global buckets that apply depending on what sort of conn
13060 - Start publishing one minute or so after we find our ORPort
13061 to be reachable. This will help reduce the number of descriptors
13062 we have for ourselves floating around, since it's quite likely
13063 other things (e.g. DirPort) will change during that minute too.
13064 - Fork the v1 directory protocol into its own spec document,
13065 and mark dir-spec.txt as the currently correct (v2) spec.
13068 - When we find our DirPort to be reachable, publish a new descriptor
13069 so we'll tell the world (reported by pnx).
13070 - Publish a new descriptor after we hup/reload. This is important
13071 if our config has changed such that we'll want to start advertising
13072 our DirPort now, etc.
13073 - Allow Tor to start when RunAsDaemon is set but no logs are set.
13074 - When we have a state file we cannot parse, tell the user and
13075 move it aside. Now we avoid situations where the user starts
13076 Tor in 1904, Tor writes a state file with that timestamp in it,
13077 the user fixes her clock, and Tor refuses to start.
13078 - Fix configure.in to not produce broken configure files with
13079 more recent versions of autoconf. Thanks to Clint for his auto*
13081 - "tor --verify-config" now exits with -1(255) or 0 depending on
13082 whether the config options are bad or good.
13083 - Resolve bug 321 when using dnsworkers: append a period to every
13084 address we resolve at the exit node, so that we do not accidentally
13085 pick up local addresses, and so that failing searches are retried
13086 in the resolver search domains. (This is already solved for
13087 eventdns.) (This breaks Blossom servers for now.)
13088 - If we are using an exit enclave and we can't connect, e.g. because
13089 its webserver is misconfigured to not listen on localhost, then
13090 back off and try connecting from somewhere else before we fail.
13093 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
13094 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
13095 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
13096 when the IP address is mapped through MapAddress to a hostname.
13097 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
13098 useless IPv6 DNS resolves.
13099 - Patch suggested by Karsten Loesing: respond to SIGNAL command
13100 before we execute the signal, in case the signal shuts us down.
13101 - Clean up AllowInvalidNodes man page entry.
13102 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
13103 - Add more asserts to track down an assert error on a windows Tor
13104 server with connection_add being called with socket == -1.
13105 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
13106 - Fix misleading log messages: an entry guard that is "unlisted",
13107 as well as not known to be "down" (because we've never heard
13108 of it), is not therefore "up".
13109 - Remove code to special-case "-cvs" ending, since it has not
13110 actually mattered since 0.0.9.
13111 - Make our socks5 handling more robust to broken socks clients:
13112 throw out everything waiting on the buffer in between socks
13113 handshake phases, since they can't possibly (so the theory
13114 goes) have predicted what we plan to respond to them.
13117 Changes in version 0.1.1.23 - 2006-07-30
13119 - Fast Tor servers, especially exit nodes, were triggering asserts
13120 due to a bug in handling the list of pending DNS resolves. Some
13121 bugs still remain here; we're hunting them.
13122 - Entry guards could crash clients by sending unexpected input.
13123 - More fixes on reachability testing: if you find yourself reachable,
13124 then don't ever make any client requests (so you stop predicting
13125 circuits), then hup or have your clock jump, then later your IP
13126 changes, you won't think circuits are working, so you won't try to
13127 test reachability, so you won't publish.
13130 - Avoid a crash if the controller does a resetconf firewallports
13131 and then a setconf fascistfirewall=1.
13132 - Avoid an integer underflow when the dir authority decides whether
13133 a router is stable: we might wrongly label it stable, and compute
13134 a slightly wrong median stability, when a descriptor is published
13136 - Fix a place where we might trigger an assert if we can't build our
13137 own server descriptor yet.
13140 Changes in version 0.1.1.22 - 2006-07-05
13142 - Fix a big bug that was causing servers to not find themselves
13143 reachable if they changed IP addresses. Since only 0.1.1.22+
13144 servers can do reachability testing correctly, now we automatically
13145 make sure to test via one of these.
13146 - Fix to allow clients and mirrors to learn directory info from
13147 descriptor downloads that get cut off partway through.
13148 - Directory authorities had a bug in deciding if a newly published
13149 descriptor was novel enough to make everybody want a copy -- a few
13150 servers seem to be publishing new descriptors many times a minute.
13152 - Fix a rare bug that was causing some servers to complain about
13153 "closing wedged cpuworkers" and skip some circuit create requests.
13154 - Make the Exit flag in directory status documents actually work.
13157 Changes in version 0.1.1.21 - 2006-06-10
13158 o Crash and assert fixes from 0.1.1.20:
13159 - Fix a rare crash on Tor servers that have enabled hibernation.
13160 - Fix a seg fault on startup for Tor networks that use only one
13161 directory authority.
13162 - Fix an assert from a race condition that occurs on Tor servers
13163 while exiting, where various threads are trying to log that they're
13164 exiting, and delete the logs, at the same time.
13165 - Make our unit tests pass again on certain obscure platforms.
13168 - Add support for building SUSE RPM packages.
13169 - Speed up initial bootstrapping for clients: if we are making our
13170 first ever connection to any entry guard, then don't mark it down
13172 - When only one Tor server in the network is labelled as a guard,
13173 and we've already picked him, we would cycle endlessly picking him
13174 again, being unhappy about it, etc. Now we specifically exclude
13175 current guards when picking a new guard.
13176 - Servers send create cells more reliably after the TLS connection
13177 is established: we were sometimes forgetting to send half of them
13178 when we had more than one pending.
13179 - If we get a create cell that asks us to extend somewhere, but the
13180 Tor server there doesn't match the expected digest, we now send
13181 a destroy cell back, rather than silently doing nothing.
13182 - Make options->RedirectExit work again.
13183 - Make cookie authentication for the controller work again.
13184 - Stop being picky about unusual characters in the arguments to
13185 mapaddress. It's none of our business.
13186 - Add a new config option "TestVia" that lets you specify preferred
13187 middle hops to use for test circuits. Perhaps this will let me
13188 debug the reachability problems better.
13190 o Log / documentation fixes:
13191 - If we're a server and some peer has a broken TLS certificate, don't
13192 log about it unless ProtocolWarnings is set, i.e., we want to hear
13193 about protocol violations by others.
13194 - Fix spelling of VirtualAddrNetwork in man page.
13195 - Add a better explanation at the top of the autogenerated torrc file
13196 about what happened to our old torrc.
13199 Changes in version 0.1.1.20 - 2006-05-23
13201 - Downgrade a log severity where servers complain that they're
13203 - Avoid a compile warning on FreeBSD.
13204 - Remove string size limit on NEWDESC messages; solve bug 291.
13205 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
13206 more thoroughly when we're running on windows.
13209 Changes in version 0.1.1.19-rc - 2006-05-03
13211 - Regenerate our local descriptor if it's dirty and we try to use
13212 it locally (e.g. if it changes during reachability detection).
13213 - If we setconf our ORPort to 0, we continued to listen on the
13214 old ORPort and receive connections.
13215 - Avoid a second warning about machine/limits.h on Debian
13217 - Be willing to add our own routerinfo into the routerlist.
13218 Now authorities will include themselves in their directories
13219 and network-statuses.
13220 - Stop trying to upload rendezvous descriptors to every
13221 directory authority: only try the v1 authorities.
13222 - Servers no longer complain when they think they're not
13223 registered with the directory authorities. There were too many
13225 - Backport dist-rpm changes so rpms can be built without errors.
13228 - Implement an option, VirtualAddrMask, to set which addresses
13229 get handed out in response to mapaddress requests. This works
13230 around a bug in tsocks where 127.0.0.0/8 is never socksified.
13233 Changes in version 0.1.1.18-rc - 2006-04-10
13235 - Work harder to download live network-statuses from all the
13236 directory authorities we know about. Improve the threshold
13237 decision logic so we're more robust to edge cases.
13238 - When fetching rendezvous descriptors, we were willing to ask
13239 v2 authorities too, which would always return 404.
13242 - Stop listing down or invalid nodes in the v1 directory. This will
13243 reduce its bulk by about 1/3, and reduce load on directory
13245 - When deciding whether a router is Fast or Guard-worthy, consider
13246 his advertised BandwidthRate and not just the BandwidthCapacity.
13247 - No longer ship INSTALL and README files -- they are useless now.
13248 - Force rpmbuild to behave and honor target_cpu.
13249 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
13250 - Start to include translated versions of the tor-doc-*.html
13251 files, along with the screenshots. Still needs more work.
13252 - Start sending back 512 and 451 errors if mapaddress fails,
13253 rather than not sending anything back at all.
13254 - When we fail to bind or listen on an incoming or outgoing
13255 socket, we should close it before failing. otherwise we just
13256 leak it. (thanks to weasel for finding.)
13257 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
13258 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
13259 - Make NoPublish (even though deprecated) work again.
13260 - Fix a minor security flaw where a versioning auth dirserver
13261 could list a recommended version many times in a row to make
13262 clients more convinced that it's recommended.
13263 - Fix crash bug if there are two unregistered servers running
13264 with the same nickname, one of them is down, and you ask for
13265 them by nickname in your EntryNodes or ExitNodes. Also, try
13266 to pick the one that's running rather than an arbitrary one.
13267 - Fix an infinite loop we could hit if we go offline for too long.
13268 - Complain when we hit WSAENOBUFS on recv() or write() too.
13269 Perhaps this will help us hunt the bug.
13270 - If you're not a versioning dirserver, don't put the string
13271 "client-versions \nserver-versions \n" in your network-status.
13272 - Lower the minimum required number of file descriptors to 1000,
13273 so we can have some overhead for Valgrind on Linux, where the
13274 default ulimit -n is 1024.
13277 - Add tor.dizum.com as the fifth authoritative directory server.
13278 - Add a new config option FetchUselessDescriptors, off by default,
13279 for when you plan to run "exitlist" on your client and you want
13280 to know about even the non-running descriptors.
13283 Changes in version 0.1.1.17-rc - 2006-03-28
13285 - Clients and servers since 0.1.1.10-alpha have been expiring
13286 connections whenever they are idle for 5 minutes and they *do*
13287 have circuits on them. Oops. With this new version, clients will
13288 discard their previous entry guard choices and avoid choosing
13289 entry guards running these flawed versions.
13290 - Fix memory leak when uncompressing concatenated zlib streams. This
13291 was causing substantial leaks over time on Tor servers.
13292 - The v1 directory was including servers as much as 48 hours old,
13293 because that's how the new routerlist->routers works. Now only
13294 include them if they're 20 hours old or less.
13297 - Resume building on irix64, netbsd 2.0, etc.
13298 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
13300 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
13301 and it is confusing some users.
13302 - Mirrors stop caching the v1 directory so often.
13303 - Make the max number of old descriptors that a cache will hold
13304 rise with the number of directory authorities, so we can scale.
13305 - Change our win32 uname() hack to be more forgiving about what
13306 win32 versions it thinks it's found.
13309 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
13311 - When the controller's *setconf commands fail, collect an error
13312 message in a string and hand it back to the controller.
13313 - Make the v2 dir's "Fast" flag based on relative capacity, just
13314 like "Stable" is based on median uptime. Name everything in the
13315 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
13316 - Log server fingerprint on startup, so new server operators don't
13317 have to go hunting around their filesystem for it.
13318 - Return a robots.txt on our dirport to discourage google indexing.
13319 - Let the controller ask for GETINFO dir/status/foo so it can ask
13320 directly rather than connecting to the dir port. Only works when
13321 dirport is set for now.
13323 o New config options rather than constants in the code:
13324 - SocksTimeout: How long do we let a socks connection wait
13325 unattached before we fail it?
13326 - CircuitBuildTimeout: Cull non-open circuits that were born
13327 at least this many seconds ago.
13328 - CircuitIdleTimeout: Cull open clean circuits that were born
13329 at least this many seconds ago.
13332 Changes in version 0.1.1.16-rc - 2006-03-18
13333 o Bugfixes on 0.1.1.15-rc:
13334 - Fix assert when the controller asks to attachstream a connect-wait
13335 or resolve-wait stream.
13336 - Now do address rewriting when the controller asks us to attach
13337 to a particular circuit too. This will let Blossom specify
13338 "moria2.exit" without having to learn what moria2's IP address is.
13339 - Make the "tor --verify-config" command-line work again, so people
13340 can automatically check if their torrc will parse.
13341 - Authoritative dirservers no longer require an open connection from
13342 a server to consider him "reachable". We need this change because
13343 when we add new auth dirservers, old servers won't know not to
13345 - Let Tor build on Sun CC again.
13346 - Fix an off-by-one buffer size in dirserv.c that magically never
13347 hit our three authorities but broke sjmurdoch's own tor network.
13348 - If we as a directory mirror don't know of any v1 directory
13349 authorities, then don't try to cache any v1 directories.
13350 - Stop warning about unknown servers in our family when they are
13351 given as hex digests.
13352 - Stop complaining as quickly to the server operator that he
13353 hasn't registered his nickname/key binding.
13354 - Various cleanups so we can add new V2 Auth Dirservers.
13355 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
13356 reflect the updated flags in our v2 dir protocol.
13357 - Resume allowing non-printable characters for exit streams (both
13358 for connecting and for resolving). Now we tolerate applications
13359 that don't follow the RFCs. But continue to block malformed names
13362 o Bugfixes on 0.1.0.x:
13363 - Fix assert bug in close_logs(): when we close and delete logs,
13364 remove them all from the global "logfiles" list.
13365 - Fix minor integer overflow in calculating when we expect to use up
13366 our bandwidth allocation before hibernating.
13367 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
13368 there are multiple SSLs installed with different versions.
13369 - When we try to be a server and Address is not explicitly set and
13370 our hostname resolves to a private IP address, try to use an
13371 interface address if it has a public address. Now Windows machines
13372 that think of themselves as localhost can work by default.
13375 - Let the controller ask for GETINFO dir/server/foo so it can ask
13376 directly rather than connecting to the dir port.
13377 - Let the controller tell us about certain router descriptors
13378 that it doesn't want Tor to use in circuits. Implement
13379 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
13380 - New config option SafeSocks to reject all application connections
13381 using unsafe socks protocols. Defaults to off.
13384 Changes in version 0.1.1.15-rc - 2006-03-11
13385 o Bugfixes and cleanups:
13386 - When we're printing strings from the network, don't try to print
13387 non-printable characters. This protects us against shell escape
13388 sequence exploits, and also against attacks to fool humans into
13389 misreading their logs.
13390 - Fix a bug where Tor would fail to establish any connections if you
13391 left it off for 24 hours and then started it: we were happy with
13392 the obsolete network statuses, but they all referred to router
13393 descriptors that were too old to fetch, so we ended up with no
13394 valid router descriptors.
13395 - Fix a seg fault in the controller's "getinfo orconn-status"
13396 command while listing status on incoming handshaking connections.
13397 Introduce a status name "NEW" for these connections.
13398 - If we get a linelist or linelist_s config option from the torrc
13399 (e.g. ExitPolicy) and it has no value, warn and skip rather than
13400 silently resetting it to its default.
13401 - Don't abandon entry guards until they've been down or gone for
13403 - Cleaner and quieter log messages.
13406 - New controller signal NEWNYM that makes new application requests
13407 use clean circuits.
13408 - Add a new circuit purpose 'controller' to let the controller ask
13409 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
13410 controller command to let you specify the purpose if you're
13411 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
13412 command to let you change a circuit's purpose after it's been
13414 - Accept "private:*" in routerdesc exit policies; not generated yet
13415 because older Tors do not understand it.
13416 - Add BSD-style contributed startup script "rc.subr" from Peter
13420 Changes in version 0.1.1.14-alpha - 2006-02-20
13421 o Bugfixes on 0.1.1.x:
13422 - Don't die if we ask for a stdout or stderr log (even implicitly)
13423 and we're set to RunAsDaemon -- just warn.
13424 - We still had a few bugs in the OR connection rotation code that
13425 caused directory servers to slowly aggregate connections to other
13426 fast Tor servers. This time for sure!
13427 - Make log entries on Win32 include the name of the function again.
13428 - We were treating a pair of exit policies if they were equal even
13429 if one said accept and the other said reject -- causing us to
13430 not always publish a new descriptor since we thought nothing
13432 - Retry pending server downloads as well as pending networkstatus
13433 downloads when we unexpectedly get a socks request.
13434 - We were ignoring the IS_FAST flag in the directory status,
13435 meaning we were willing to pick trivial-bandwidth nodes for "fast"
13437 - If the controller's SAVECONF command fails (e.g. due to file
13438 permissions), let the controller know that it failed.
13441 - If we're trying to be a Tor server and running Windows 95/98/ME
13442 as a server, explain that we'll likely crash.
13443 - When we're a server, a client asks for an old-style directory,
13444 and our write bucket is empty, don't give it to him. This way
13445 small servers can continue to serve the directory *sometimes*,
13446 without getting overloaded.
13447 - Compress exit policies even more -- look for duplicate lines
13449 - Clients now honor the "guard" flag in the router status when
13450 picking entry guards, rather than looking at is_fast or is_stable.
13451 - Retain unrecognized lines in $DATADIR/state file, so that we can
13452 be forward-compatible.
13453 - Generate 18.0.0.0/8 address policy format in descs when we can;
13454 warn when the mask is not reducible to a bit-prefix.
13455 - Let the user set ControlListenAddress in the torrc. This can be
13456 dangerous, but there are some cases (like a secured LAN) where it
13458 - Split ReachableAddresses into ReachableDirAddresses and
13459 ReachableORAddresses, so we can restrict Dir conns to port 80
13460 and OR conns to port 443.
13461 - Now we can target arch and OS in rpm builds (contributed by
13462 Phobos). Also make the resulting dist-rpm filename match the
13464 - New config options to help controllers: FetchServerDescriptors
13465 and FetchHidServDescriptors for whether to fetch server
13466 info and hidserv info or let the controller do it, and
13467 PublishServerDescriptor and PublishHidServDescriptors.
13468 - Also let the controller set the __AllDirActionsPrivate config
13469 option if you want all directory fetches/publishes to happen via
13470 Tor (it assumes your controller bootstraps your circuits).
13473 Changes in version 0.1.0.17 - 2006-02-17
13474 o Crash bugfixes on 0.1.0.x:
13475 - When servers with a non-zero DirPort came out of hibernation,
13476 sometimes they would trigger an assert.
13478 o Other important bugfixes:
13479 - On platforms that don't have getrlimit (like Windows), we were
13480 artificially constraining ourselves to a max of 1024
13481 connections. Now just assume that we can handle as many as 15000
13482 connections. Hopefully this won't cause other problems.
13484 o Backported features:
13485 - When we're a server, a client asks for an old-style directory,
13486 and our write bucket is empty, don't give it to him. This way
13487 small servers can continue to serve the directory *sometimes*,
13488 without getting overloaded.
13489 - Whenever you get a 503 in response to a directory fetch, try
13490 once more. This will become important once servers start sending
13491 503's whenever they feel busy.
13492 - Fetch a new directory every 120 minutes, not every 40 minutes.
13493 Now that we have hundreds of thousands of users running the old
13494 directory algorithm, it's starting to hurt a lot.
13495 - Bump up the period for forcing a hidden service descriptor upload
13496 from 20 minutes to 1 hour.
13499 Changes in version 0.1.1.13-alpha - 2006-02-09
13500 o Crashes in 0.1.1.x:
13501 - When you tried to setconf ORPort via the controller, Tor would
13502 crash. So people using TorCP to become a server were sad.
13503 - Solve (I hope) the stack-smashing bug that we were seeing on fast
13504 servers. The problem appears to be something do with OpenSSL's
13505 random number generation, or how we call it, or something. Let me
13506 know if the crashes continue.
13507 - Turn crypto hardware acceleration off by default, until we find
13508 somebody smart who can test it for us. (It appears to produce
13509 seg faults in at least some cases.)
13510 - Fix a rare assert error when we've tried all intro points for
13511 a hidden service and we try fetching the service descriptor again:
13512 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
13515 - Fix a major load balance bug: we were round-robining in 16 KB
13516 chunks, and servers with bandwidthrate of 20 KB, while downloading
13517 a 600 KB directory, would starve their other connections. Now we
13518 try to be a bit more fair.
13519 - Dir authorities and mirrors were never expiring the newest
13520 descriptor for each server, causing memory and directory bloat.
13521 - Fix memory-bloating and connection-bloating bug on servers: We
13522 were never closing any connection that had ever had a circuit on
13523 it, because we were checking conn->n_circuits == 0, yet we had a
13524 bug that let it go negative.
13525 - Make Tor work using squid as your http proxy again -- squid
13526 returns an error if you ask for a URL that's too long, and it uses
13527 a really generic error message. Plus, many people are behind a
13528 transparent squid so they don't even realize it.
13529 - On platforms that don't have getrlimit (like Windows), we were
13530 artificially constraining ourselves to a max of 1024
13531 connections. Now just assume that we can handle as many as 15000
13532 connections. Hopefully this won't cause other problems.
13533 - Add a new config option ExitPolicyRejectPrivate which defaults to
13534 1. This means all exit policies will begin with rejecting private
13535 addresses, unless the server operator explicitly turns it off.
13538 - Clients no longer download descriptors for non-running
13540 - Before we add new directory authorities, we should make it
13541 clear that only v1 authorities should receive/publish hidden
13542 service descriptors.
13545 - As soon as we've fetched some more directory info, immediately
13546 try to download more server descriptors. This way we don't have
13547 a 10 second pause during initial bootstrapping.
13548 - Remove even more loud log messages that the server operator can't
13550 - When we're running an obsolete or un-recommended version, make
13551 the log message more clear about what the problem is and what
13552 versions *are* still recommended.
13553 - Provide a more useful warn message when our onion queue gets full:
13554 the CPU is too slow or the exit policy is too liberal.
13555 - Don't warn when we receive a 503 from a dirserver/cache -- this
13556 will pave the way for them being able to refuse if they're busy.
13557 - When we fail to bind a listener, try to provide a more useful
13558 log message: e.g., "Is Tor already running?"
13559 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
13560 Goldberg can prove things about our handshake protocol more
13562 - MaxConn has been obsolete for a while now. Document the ConnLimit
13563 config option, which is a *minimum* number of file descriptors
13564 that must be available else Tor refuses to start.
13565 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
13566 if you log to syslog and want something other than LOG_DAEMON.
13567 - Make dirservers generate a separate "guard" flag to mean,
13568 "would make a good entry guard". Make clients parse it and vote
13569 on it. Not used by clients yet.
13570 - Implement --with-libevent-dir option to ./configure. Also, improve
13571 search techniques to find libevent, and use those for openssl too.
13572 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
13573 - Only start testing reachability once we've established a
13574 circuit. This will make startup on dirservers less noisy.
13575 - Don't try to upload hidden service descriptors until we have
13576 established a circuit.
13577 - Fix the controller's "attachstream 0" command to treat conn like
13578 it just connected, doing address remapping, handling .exit and
13579 .onion idioms, and so on. Now we're more uniform in making sure
13580 that the controller hears about new and closing connections.
13583 Changes in version 0.1.1.12-alpha - 2006-01-11
13584 o Bugfixes on 0.1.1.x:
13585 - The fix to close duplicate server connections was closing all
13586 Tor client connections if they didn't establish a circuit
13587 quickly enough. Oops.
13588 - Fix minor memory issue (double-free) that happened on exit.
13590 o Bugfixes on 0.1.0.x:
13591 - Tor didn't warn when it failed to open a log file.
13594 Changes in version 0.1.1.11-alpha - 2006-01-10
13595 o Crashes in 0.1.1.x:
13596 - Include all the assert/crash fixes from 0.1.0.16.
13597 - If you start Tor and then quit very quickly, there were some
13598 races that tried to free things that weren't allocated yet.
13599 - Fix a rare memory stomp if you're running hidden services.
13600 - Fix segfault when specifying DirServer in config without nickname.
13601 - Fix a seg fault when you finish connecting to a server but at
13602 that moment you dump his server descriptor.
13603 - Extendcircuit and Attachstream controller commands would
13604 assert/crash if you don't give them enough arguments.
13605 - Fix an assert error when we're out of space in the connection_list
13606 and we try to post a hidden service descriptor (reported by weasel).
13607 - If you specify a relative torrc path and you set RunAsDaemon in
13608 your torrc, then it chdir()'s to the new directory. If you HUP,
13609 it tries to load the new torrc location, fails, and exits.
13610 The fix: no longer allow a relative path to torrc using -f.
13613 - Implement "entry guards": automatically choose a handful of entry
13614 nodes and stick with them for all circuits. Only pick new guards
13615 when the ones you have are unsuitable, and if the old guards
13616 become suitable again, switch back. This will increase security
13617 dramatically against certain end-point attacks. The EntryNodes
13618 config option now provides some hints about which entry guards you
13619 want to use most; and StrictEntryNodes means to only use those.
13620 - New directory logic: download by descriptor digest, not by
13621 fingerprint. Caches try to download all listed digests from
13622 authorities; clients try to download "best" digests from caches.
13623 This avoids partitioning and isolating attacks better.
13624 - Make the "stable" router flag in network-status be the median of
13625 the uptimes of running valid servers, and make clients pay
13626 attention to the network-status flags. Thus the cutoff adapts
13627 to the stability of the network as a whole, making IRC, IM, etc
13628 connections more reliable.
13631 - Tor servers with dynamic IP addresses were needing to wait 18
13632 hours before they could start doing reachability testing using
13633 the new IP address and ports. This is because they were using
13634 the internal descriptor to learn what to test, yet they were only
13635 rebuilding the descriptor once they decided they were reachable.
13636 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
13637 to download certain server descriptors, throw them away, and then
13638 fetch them again after 30 minutes. Now mirrors throw away these
13639 server descriptors so clients can't get them.
13640 - We were leaving duplicate connections to other ORs open for a week,
13641 rather than closing them once we detect a duplicate. This only
13642 really affected authdirservers, but it affected them a lot.
13643 - Spread the authdirservers' reachability testing over the entire
13644 testing interval, so we don't try to do 500 TLS's at once every
13648 - If the network is down, and we try to connect to a conn because
13649 we have a circuit in mind, and we timeout (30 seconds) because the
13650 network never answers, we were expiring the circuit, but we weren't
13651 obsoleting the connection or telling the entry_guards functions.
13652 - Some Tor servers process billions of cells per day. These statistics
13653 need to be uint64_t's.
13654 - Check for integer overflows in more places, when adding elements
13655 to smartlists. This could possibly prevent a buffer overflow
13656 on malicious huge inputs. I don't see any, but I haven't looked
13658 - ReachableAddresses kept growing new "reject *:*" lines on every
13660 - When you "setconf log" via the controller, it should remove all
13661 logs. We were automatically adding back in a "log notice stdout".
13662 - Newly bootstrapped Tor networks couldn't establish hidden service
13663 circuits until they had nodes with high uptime. Be more tolerant.
13664 - We were marking servers down when they could not answer every piece
13665 of the directory request we sent them. This was far too harsh.
13666 - Fix the torify (tsocks) config file to not use Tor for localhost
13668 - Directory authorities now go to the proper authority when asking for
13669 a networkstatus, even when they want a compressed one.
13670 - Fix a harmless bug that was causing Tor servers to log
13671 "Got an end because of misc error, but we're not an AP. Closing."
13672 - Authorities were treating their own descriptor changes as cosmetic,
13673 meaning the descriptor available in the network-status and the
13674 descriptor that clients downloaded were different.
13675 - The OS X installer was adding a symlink for tor_resolve but
13676 the binary was called tor-resolve (reported by Thomas Hardly).
13677 - Workaround a problem with some http proxies where they refuse GET
13678 requests that specify "Content-Length: 0" (reported by Adrian).
13679 - Fix wrong log message when you add a "HiddenServiceNodes" config
13680 line without any HiddenServiceDir line (reported by Chris Thomas).
13683 - Write the TorVersion into the state file so we have a prayer of
13684 keeping forward and backward compatibility.
13685 - Revive the FascistFirewall config option rather than eliminating it:
13686 now it's a synonym for ReachableAddresses *:80,*:443.
13687 - Clients choose directory servers from the network status lists,
13688 not from their internal list of router descriptors. Now they can
13689 go to caches directly rather than needing to go to authorities
13691 - Directory authorities ignore router descriptors that have only
13692 cosmetic differences: do this for 0.1.0.x servers now too.
13693 - Add a new flag to network-status indicating whether the server
13694 can answer v2 directory requests too.
13695 - Authdirs now stop whining so loudly about bad descriptors that
13696 they fetch from other dirservers. So when there's a log complaint,
13697 it's for sure from a freshly uploaded descriptor.
13698 - Reduce memory requirements in our structs by changing the order
13700 - There used to be two ways to specify your listening ports in a
13701 server descriptor: on the "router" line and with a separate "ports"
13702 line. Remove support for the "ports" line.
13703 - New config option "AuthDirRejectUnlisted" for auth dirservers as
13704 a panic button: if we get flooded with unusable servers we can
13705 revert to only listing servers in the approved-routers file.
13706 - Auth dir servers can now mark a fingerprint as "!reject" or
13707 "!invalid" in the approved-routers file (as its nickname), to
13708 refuse descriptors outright or include them but marked as invalid.
13709 - Servers store bandwidth history across restarts/crashes.
13710 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
13711 get a better idea of why their circuits failed. Not used yet.
13712 - Directory mirrors now cache up to 16 unrecognized network-status
13713 docs. Now we can add new authdirservers and they'll be cached too.
13714 - When picking a random directory, prefer non-authorities if any
13716 - New controller option "getinfo desc/all-recent" to fetch the
13717 latest server descriptor for every router that Tor knows about.
13720 Changes in version 0.1.0.16 - 2006-01-02
13721 o Crash bugfixes on 0.1.0.x:
13722 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13723 corrupting the heap, losing FDs, or crashing when we need to resize
13724 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13725 - It turns out sparc64 platforms crash on unaligned memory access
13726 too -- so detect and avoid this.
13727 - Handle truncated compressed data correctly (by detecting it and
13729 - Fix possible-but-unlikely free(NULL) in control.c.
13730 - When we were closing connections, there was a rare case that
13731 stomped on memory, triggering seg faults and asserts.
13732 - Avoid potential infinite recursion when building a descriptor. (We
13733 don't know that it ever happened, but better to fix it anyway.)
13734 - We were neglecting to unlink marked circuits from soon-to-close OR
13735 connections, which caused some rare scribbling on freed memory.
13736 - Fix a memory stomping race bug when closing the joining point of two
13737 rendezvous circuits.
13738 - Fix an assert in time parsing found by Steven Murdoch.
13740 o Other bugfixes on 0.1.0.x:
13741 - When we're doing reachability testing, provide more useful log
13742 messages so the operator knows what to expect.
13743 - Do not check whether DirPort is reachable when we are suppressing
13744 advertising it because of hibernation.
13745 - When building with -static or on Solaris, we sometimes needed -ldl.
13746 - When we're deciding whether a stream has enough circuits around
13747 that can handle it, count the freshly dirty ones and not the ones
13748 that are so dirty they won't be able to handle it.
13749 - When we're expiring old circuits, we had a logic error that caused
13750 us to close new rendezvous circuits rather than old ones.
13751 - Give a more helpful log message when you try to change ORPort via
13752 the controller: you should upgrade Tor if you want that to work.
13753 - We were failing to parse Tor versions that start with "Tor ".
13754 - Tolerate faulty streams better: when a stream fails for reason
13755 exitpolicy, stop assuming that the router is lying about his exit
13756 policy. When a stream fails for reason misc, allow it to retry just
13757 as if it was resolvefailed. When a stream has failed three times,
13758 reset its failure count so we can try again and get all three tries.
13761 Changes in version 0.1.1.10-alpha - 2005-12-11
13762 o Correctness bugfixes on 0.1.0.x:
13763 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13764 corrupting the heap, losing FDs, or crashing when we need to resize
13765 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13766 - Stop doing the complex voodoo overkill checking for insecure
13767 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
13768 - When we were closing connections, there was a rare case that
13769 stomped on memory, triggering seg faults and asserts.
13770 - We were neglecting to unlink marked circuits from soon-to-close OR
13771 connections, which caused some rare scribbling on freed memory.
13772 - When we're deciding whether a stream has enough circuits around
13773 that can handle it, count the freshly dirty ones and not the ones
13774 that are so dirty they won't be able to handle it.
13775 - Recover better from TCP connections to Tor servers that are
13776 broken but don't tell you (it happens!); and rotate TLS
13777 connections once a week.
13778 - When we're expiring old circuits, we had a logic error that caused
13779 us to close new rendezvous circuits rather than old ones.
13780 - Fix a scary-looking but apparently harmless bug where circuits
13781 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
13782 servers, and never switch to state CIRCUIT_STATE_OPEN.
13783 - When building with -static or on Solaris, we sometimes needed to
13785 - Give a useful message when people run Tor as the wrong user,
13786 rather than telling them to start chowning random directories.
13787 - We were failing to inform the controller about new .onion streams.
13789 o Security bugfixes on 0.1.0.x:
13790 - Refuse server descriptors if the fingerprint line doesn't match
13791 the included identity key. Tor doesn't care, but other apps (and
13792 humans) might actually be trusting the fingerprint line.
13793 - We used to kill the circuit when we receive a relay command we
13794 don't recognize. Now we just drop it.
13795 - Start obeying our firewall options more rigorously:
13796 . If we can't get to a dirserver directly, try going via Tor.
13797 . Don't ever try to connect (as a client) to a place our
13798 firewall options forbid.
13799 . If we specify a proxy and also firewall options, obey the
13800 firewall options even when we're using the proxy: some proxies
13801 can only proxy to certain destinations.
13802 - Fix a bug found by Lasse Overlier: when we were making internal
13803 circuits (intended to be cannibalized later for rendezvous and
13804 introduction circuits), we were picking them so that they had
13805 useful exit nodes. There was no need for this, and it actually
13806 aids some statistical attacks.
13807 - Start treating internal circuits and exit circuits separately.
13808 It's important to keep them separate because internal circuits
13809 have their last hops picked like middle hops, rather than like
13810 exit hops. So exiting on them will break the user's expectations.
13812 o Bugfixes on 0.1.1.x:
13813 - Take out the mis-feature where we tried to detect IP address
13814 flapping for people with DynDNS, and chose not to upload a new
13815 server descriptor sometimes.
13816 - Try to be compatible with OpenSSL 0.9.6 again.
13817 - Log fix: when the controller is logging about .onion addresses,
13818 sometimes it didn't include the ".onion" part of the address.
13819 - Don't try to modify options->DirServers internally -- if the
13820 user didn't specify any, just add the default ones directly to
13821 the trusted dirserver list. This fixes a bug where people running
13822 controllers would use SETCONF on some totally unrelated config
13823 option, and Tor would start yelling at them about changing their
13825 - Let the controller's redirectstream command specify a port, in
13826 case the controller wants to change that too.
13827 - When we requested a pile of server descriptors, we sometimes
13828 accidentally launched a duplicate request for the first one.
13829 - Bugfix for trackhostexits: write down the fingerprint of the
13830 chosen exit, not its nickname, because the chosen exit might not
13832 - When parsing foo.exit, if foo is unknown, and we are leaving
13833 circuits unattached, set the chosen_exit field and leave the
13834 address empty. This matters because controllers got confused
13836 - Directory authorities no longer try to download server
13837 descriptors that they know they will reject.
13839 o Features and updates:
13840 - Replace balanced trees with hash tables: this should make stuff
13841 significantly faster.
13842 - Resume using the AES counter-mode implementation that we ship,
13843 rather than OpenSSL's. Ours is significantly faster.
13844 - Many other CPU and memory improvements.
13845 - Add a new config option FastFirstHopPK (on by default) so clients
13846 do a trivial crypto handshake for their first hop, since TLS has
13847 already taken care of confidentiality and authentication.
13848 - Add a new config option TestSocks so people can see if their
13849 applications are using socks4, socks4a, socks5-with-ip, or
13850 socks5-with-hostname. This way they don't have to keep mucking
13851 with tcpdump and wondering if something got cached somewhere.
13852 - Warn when listening on a public address for socks. I suspect a
13853 lot of people are setting themselves up as open socks proxies,
13854 and they have no idea that jerks on the Internet are using them,
13855 since they simply proxy the traffic into the Tor network.
13856 - Add "private:*" as an alias in configuration for policies. Now
13857 you can simplify your exit policy rather than needing to list
13858 every single internal or nonroutable network space.
13859 - Add a new controller event type that allows controllers to get
13860 all server descriptors that were uploaded to a router in its role
13861 as authoritative dirserver.
13862 - Start shipping socks-extensions.txt, tor-doc-unix.html,
13863 tor-doc-server.html, and stylesheet.css in the tarball.
13864 - Stop shipping tor-doc.html in the tarball.
13867 Changes in version 0.1.1.9-alpha - 2005-11-15
13868 o Usability improvements:
13869 - Start calling it FooListenAddress rather than FooBindAddress,
13870 since few of our users know what it means to bind an address
13872 - Reduce clutter in server logs. We're going to try to make
13873 them actually usable now. New config option ProtocolWarnings that
13874 lets you hear about how _other Tors_ are breaking the protocol. Off
13876 - Divide log messages into logging domains. Once we put some sort
13877 of interface on this, it will let people looking at more verbose
13878 log levels specify the topics they want to hear more about.
13879 - Make directory servers return better http 404 error messages
13880 instead of a generic "Servers unavailable".
13881 - Check for even more Windows version flags when writing the platform
13882 string in server descriptors, and note any we don't recognize.
13883 - Clean up more of the OpenSSL memory when exiting, so we can detect
13884 memory leaks better.
13885 - Make directory authorities be non-versioning, non-naming by
13886 default. Now we can add new directory servers without requiring
13887 their operators to pay close attention.
13888 - When logging via syslog, include the pid whenever we provide
13889 a log entry. Suggested by Todd Fries.
13891 o Performance improvements:
13892 - Directory servers now silently throw away new descriptors that
13893 haven't changed much if the timestamps are similar. We do this to
13894 tolerate older Tor servers that upload a new descriptor every 15
13895 minutes. (It seemed like a good idea at the time.)
13896 - Inline bottleneck smartlist functions; use fast versions by default.
13897 - Add a "Map from digest to void*" abstraction digestmap_t so we
13898 can do less hex encoding/decoding. Use it in router_get_by_digest()
13899 to resolve a performance bottleneck.
13900 - Allow tor_gzip_uncompress to extract as much as possible from
13901 truncated compressed data. Try to extract as many
13902 descriptors as possible from truncated http responses (when
13903 DIR_PURPOSE_FETCH_ROUTERDESC).
13904 - Make circ->onionskin a pointer, not a static array. moria2 was using
13905 125000 circuit_t's after it had been up for a few weeks, which
13906 translates to 20+ megs of wasted space.
13907 - The private half of our EDH handshake keys are now chosen out
13908 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
13910 o Security improvements:
13911 - Start making directory caches retain old routerinfos, so soon
13912 clients can start asking by digest of descriptor rather than by
13913 fingerprint of server.
13914 - Add half our entropy from RAND_poll in OpenSSL. This knows how
13915 to use egd (if present), openbsd weirdness (if present), vms/os2
13916 weirdness (if we ever port there), and more in the future.
13918 o Bugfixes on 0.1.0.x:
13919 - Do round-robin writes of at most 16 kB per write. This might be
13920 more fair on loaded Tor servers, and it might resolve our Windows
13921 crash bug. It might also slow things down.
13922 - Our TLS handshakes were generating a single public/private
13923 keypair for the TLS context, rather than making a new one for
13924 each new connections. Oops. (But we were still rotating them
13925 periodically, so it's not so bad.)
13926 - When we were cannibalizing a circuit with a particular exit
13927 node in mind, we weren't checking to see if that exit node was
13928 already present earlier in the circuit. Oops.
13929 - When a Tor server's IP changes (e.g. from a dyndns address),
13930 upload a new descriptor so clients will learn too.
13931 - Really busy servers were keeping enough circuits open on stable
13932 connections that they were wrapping around the circuit_id
13933 space. (It's only two bytes.) This exposed a bug where we would
13934 feel free to reuse a circuit_id even if it still exists but has
13935 been marked for close. Try to fix this bug. Some bug remains.
13936 - If we would close a stream early (e.g. it asks for a .exit that
13937 we know would refuse it) but the LeaveStreamsUnattached config
13938 option is set by the controller, then don't close it.
13940 o Bugfixes on 0.1.1.8-alpha:
13941 - Fix a big pile of memory leaks, some of them serious.
13942 - Do not try to download a routerdesc if we would immediately reject
13944 - Resume inserting a newline between all router descriptors when
13945 generating (old style) signed directories, since our spec says
13947 - When providing content-type application/octet-stream for
13948 server descriptors using .z, we were leaving out the
13949 content-encoding header. Oops. (Everything tolerated this just
13950 fine, but that doesn't mean we need to be part of the problem.)
13951 - Fix a potential seg fault in getconf and getinfo using version 1
13952 of the controller protocol.
13953 - Avoid crash: do not check whether DirPort is reachable when we
13954 are suppressing it because of hibernation.
13955 - Make --hash-password not crash on exit.
13958 Changes in version 0.1.1.8-alpha - 2005-10-07
13959 o New features (major):
13960 - Clients don't download or use the directory anymore. Now they
13961 download and use network-statuses from the trusted dirservers,
13962 and fetch individual server descriptors as needed from mirrors.
13963 See dir-spec.txt for all the gory details.
13964 - Be more conservative about whether to advertise our DirPort.
13965 The main change is to not advertise if we're running at capacity
13966 and either a) we could hibernate or b) our capacity is low and
13967 we're using a default DirPort.
13968 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
13970 o New features (minor):
13971 - Try to be smart about when to retry network-status and
13972 server-descriptor fetches. Still needs some tuning.
13973 - Stop parsing, storing, or using running-routers output (but
13974 mirrors still cache and serve it).
13975 - Consider a threshold of versioning dirservers (dirservers who have
13976 an opinion about which Tor versions are still recommended) before
13977 deciding whether to warn the user that he's obsolete.
13978 - Dirservers can now reject/invalidate by key and IP, with the
13979 config options "AuthDirInvalid" and "AuthDirReject". This is
13980 useful since currently we automatically list servers as running
13981 and usable even if we know they're jerks.
13982 - Provide dire warnings to any users who set DirServer; move it out
13983 of torrc.sample and into torrc.complete.
13984 - Add MyFamily to torrc.sample in the server section.
13985 - Add nicknames to the DirServer line, so we can refer to them
13986 without requiring all our users to memorize their IP addresses.
13987 - When we get an EOF or a timeout on a directory connection, note
13988 how many bytes of serverdesc we are dropping. This will help
13989 us determine whether it is smart to parse incomplete serverdesc
13991 - Add a new function to "change pseudonyms" -- that is, to stop
13992 using any currently-dirty circuits for new streams, so we don't
13993 link new actions to old actions. Currently it's only called on
13994 HUP (or SIGNAL RELOAD).
13995 - On sighup, if UseHelperNodes changed to 1, use new circuits.
13996 - Start using RAND_bytes rather than RAND_pseudo_bytes from
13997 OpenSSL. Also, reseed our entropy every hour, not just at
13998 startup. And entropy in 512-bit chunks, not 160-bit chunks.
14000 o Fixes on 0.1.1.7-alpha:
14001 - Nobody ever implemented EVENT_ADDRMAP for control protocol
14002 version 0, so don't let version 0 controllers ask for it.
14003 - If you requested something with too many newlines via the
14004 v1 controller protocol, you could crash tor.
14005 - Fix a number of memory leaks, including some pretty serious ones.
14006 - Re-enable DirPort testing again, so Tor servers will be willing
14007 to advertise their DirPort if it's reachable.
14008 - On TLS handshake, only check the other router's nickname against
14009 its expected nickname if is_named is set.
14011 o Fixes forward-ported from 0.1.0.15:
14012 - Don't crash when we don't have any spare file descriptors and we
14013 try to spawn a dns or cpu worker.
14014 - Make the numbers in read-history and write-history into uint64s,
14015 so they don't overflow and publish negatives in the descriptor.
14017 o Fixes on 0.1.0.x:
14018 - For the OS X package's modified privoxy config file, comment
14019 out the "logfile" line so we don't log everything passed
14021 - We were whining about using socks4 or socks5-with-local-lookup
14022 even when it's an IP in the "virtual" range we designed exactly
14024 - We were leaking some memory every time the client changes IPs.
14025 - Never call free() on tor_malloc()d memory. This will help us
14026 use dmalloc to detect memory leaks.
14027 - Check for named servers when looking them up by nickname;
14028 warn when we'recalling a non-named server by its nickname;
14029 don't warn twice about the same name.
14030 - Try to list MyFamily elements by key, not by nickname, and warn
14031 if we've not heard of the server.
14032 - Make windows platform detection (uname equivalent) smarter.
14033 - It turns out sparc64 doesn't like unaligned access either.
14036 Changes in version 0.1.0.15 - 2005-09-23
14037 o Bugfixes on 0.1.0.x:
14038 - Reject ports 465 and 587 (spam targets) in default exit policy.
14039 - Don't crash when we don't have any spare file descriptors and we
14040 try to spawn a dns or cpu worker.
14041 - Get rid of IgnoreVersion undocumented config option, and make us
14042 only warn, never exit, when we're running an obsolete version.
14043 - Don't try to print a null string when your server finds itself to
14044 be unreachable and the Address config option is empty.
14045 - Make the numbers in read-history and write-history into uint64s,
14046 so they don't overflow and publish negatives in the descriptor.
14047 - Fix a minor memory leak in smartlist_string_remove().
14048 - We were only allowing ourselves to upload a server descriptor at
14049 most every 20 minutes, even if it changed earlier than that.
14050 - Clean up log entries that pointed to old URLs.
14053 Changes in version 0.1.1.7-alpha - 2005-09-14
14054 o Fixes on 0.1.1.6-alpha:
14055 - Exit servers were crashing when people asked them to make a
14056 connection to an address not in their exit policy.
14057 - Looking up a non-existent stream for a v1 control connection would
14059 - Fix a seg fault if we ask a dirserver for a descriptor by
14060 fingerprint but he doesn't know about him.
14061 - SETCONF was appending items to linelists, not clearing them.
14062 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
14063 out and refuse the setconf if it would fail.
14064 - Downgrade the dirserver log messages when whining about
14068 - Add Peter Palfrader's check-tor script to tor/contrib/
14069 It lets you easily check whether a given server (referenced by
14070 nickname) is reachable by you.
14071 - Numerous changes to move towards client-side v2 directories. Not
14074 o Fixes on 0.1.0.x:
14075 - If the user gave tor an odd number of command-line arguments,
14076 we were silently ignoring the last one. Now we complain and fail.
14077 [This wins the oldest-bug prize -- this bug has been present since
14078 November 2002, as released in Tor 0.0.0.]
14079 - Do not use unaligned memory access on alpha, mips, or mipsel.
14080 It *works*, but is very slow, so we treat them as if it doesn't.
14081 - Retry directory requests if we fail to get an answer we like
14082 from a given dirserver (we were retrying before, but only if
14083 we fail to connect).
14084 - When writing the RecommendedVersions line, sort them first.
14085 - When the client asked for a rendezvous port that the hidden
14086 service didn't want to provide, we were sending an IP address
14087 back along with the end cell. Fortunately, it was zero. But stop
14089 - Correct "your server is reachable" log entries to indicate that
14090 it was self-testing that told us so.
14093 Changes in version 0.1.1.6-alpha - 2005-09-09
14094 o Fixes on 0.1.1.5-alpha:
14095 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
14096 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
14097 - Fix bug with tor_memmem finding a match at the end of the string.
14098 - Make unit tests run without segfaulting.
14099 - Resolve some solaris x86 compile warnings.
14100 - Handle duplicate lines in approved-routers files without warning.
14101 - Fix bug where as soon as a server refused any requests due to his
14102 exit policy (e.g. when we ask for localhost and he tells us that's
14103 127.0.0.1 and he won't do it), we decided he wasn't obeying his
14104 exit policy using him for any exits.
14105 - Only do openssl hardware accelerator stuff if openssl version is
14108 o New controller features/fixes:
14109 - Add a "RESETCONF" command so you can set config options like
14110 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
14111 a config option in the torrc with no value, then it clears it
14112 entirely (rather than setting it to its default).
14113 - Add a "GETINFO config-file" to tell us where torrc is.
14114 - Avoid sending blank lines when GETINFO replies should be empty.
14115 - Add a QUIT command for the controller (for using it manually).
14116 - Fix a bug in SAVECONF that was adding default dirservers and
14117 other redundant entries to the torrc file.
14119 o Start on the new directory design:
14120 - Generate, publish, cache, serve new network-status format.
14121 - Publish individual descriptors (by fingerprint, by "all", and by
14123 - Publish client and server recommended versions separately.
14124 - Allow tor_gzip_uncompress() to handle multiple concatenated
14125 compressed strings. Serve compressed groups of router
14126 descriptors. The compression logic here could be more
14128 - Distinguish v1 authorities (all currently trusted directories)
14129 from v2 authorities (all trusted directories).
14130 - Change DirServers config line to note which dirs are v1 authorities.
14131 - Add configuration option "V1AuthoritativeDirectory 1" which
14132 moria1, moria2, and tor26 should set.
14133 - Remove option when getting directory cache to see whether they
14134 support running-routers; they all do now. Replace it with one
14135 to see whether caches support v2 stuff.
14138 - Dirservers now do their own external reachability testing of each
14139 Tor server, and only list them as running if they've been found to
14140 be reachable. We also send back warnings to the server's logs if
14141 it uploads a descriptor that we already believe is unreachable.
14142 - Implement exit enclaves: if we know an IP address for the
14143 destination, and there's a running Tor server at that address
14144 which allows exit to the destination, then extend the circuit to
14145 that exit first. This provides end-to-end encryption and end-to-end
14146 authentication. Also, if the user wants a .exit address or enclave,
14147 use 4 hops rather than 3, and cannibalize a general circ for it
14149 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
14150 controller. Also, rotate dns and cpu workers if the controller
14151 changes options that will affect them; and initialize the dns
14152 worker cache tree whether or not we start out as a server.
14153 - Only upload a new server descriptor when options change, 18
14154 hours have passed, uptime is reset, or bandwidth changes a lot.
14155 - Check [X-]Forwarded-For headers in HTTP requests when generating
14156 log messages. This lets people run dirservers (and caches) behind
14157 Apache but still know which IP addresses are causing warnings.
14159 o Config option changes:
14160 - Replace (Fascist)Firewall* config options with a new
14161 ReachableAddresses option that understands address policies.
14162 For example, "ReachableAddresses *:80,*:443"
14163 - Get rid of IgnoreVersion undocumented config option, and make us
14164 only warn, never exit, when we're running an obsolete version.
14165 - Make MonthlyAccountingStart config option truly obsolete now.
14167 o Fixes on 0.1.0.x:
14168 - Reject ports 465 and 587 in the default exit policy, since
14169 people have started using them for spam too.
14170 - It turns out we couldn't bootstrap a network since we added
14171 reachability detection in 0.1.0.1-rc. Good thing the Tor network
14172 has never gone down. Add an AssumeReachable config option to let
14173 servers and dirservers bootstrap. When we're trying to build a
14174 high-uptime or high-bandwidth circuit but there aren't enough
14175 suitable servers, try being less picky rather than simply failing.
14176 - Our logic to decide if the OR we connected to was the right guy
14177 was brittle and maybe open to a mitm for unverified routers.
14178 - We weren't cannibalizing circuits correctly for
14179 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
14180 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
14181 build those from scratch. This should make hidden services faster.
14182 - Predict required circuits better, with an eye toward making hidden
14183 services faster on the service end.
14184 - Retry streams if the exit node sends back a 'misc' failure. This
14185 should result in fewer random failures. Also, after failing
14186 from resolve failed or misc, reset the num failures, so we give
14187 it a fair shake next time we try.
14188 - Clean up the rendezvous warn log msgs, and downgrade some to info.
14189 - Reduce severity on logs about dns worker spawning and culling.
14190 - When we're shutting down and we do something like try to post a
14191 server descriptor or rendezvous descriptor, don't complain that
14192 we seem to be unreachable. Of course we are, we're shutting down.
14193 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
14194 We don't use them yet, but maybe one day our DNS resolver will be
14195 able to discover them.
14196 - Make ContactInfo mandatory for authoritative directory servers.
14197 - Require server descriptors to list IPv4 addresses -- hostnames
14198 are no longer allowed. This also fixes some potential security
14199 problems with people providing hostnames as their address and then
14200 preferentially resolving them to partition users.
14201 - Change log line for unreachability to explicitly suggest /etc/hosts
14202 as the culprit. Also make it clearer what IP address and ports we're
14203 testing for reachability.
14204 - Put quotes around user-supplied strings when logging so users are
14205 more likely to realize if they add bad characters (like quotes)
14207 - Let auth dir servers start without specifying an Address config
14209 - Make unit tests (and other invocations that aren't the real Tor)
14210 run without launching listeners, creating subdirectories, and so on.
14213 Changes in version 0.1.1.5-alpha - 2005-08-08
14214 o Bugfixes included in 0.1.0.14.
14216 o Bugfixes on 0.1.0.x:
14217 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
14218 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
14219 it would silently using ignore the 6668.
14222 Changes in version 0.1.0.14 - 2005-08-08
14223 o Bugfixes on 0.1.0.x:
14224 - Fix the other half of the bug with crypto handshakes
14226 - Fix an assert trigger if you send a 'signal term' via the
14227 controller when it's listening for 'event info' messages.
14230 Changes in version 0.1.1.4-alpha - 2005-08-04
14231 o Bugfixes included in 0.1.0.13.
14234 - Improve tor_gettimeofday() granularity on windows.
14235 - Make clients regenerate their keys when their IP address changes.
14236 - Implement some more GETINFO goodness: expose helper nodes, config
14237 options, getinfo keys.
14240 Changes in version 0.1.0.13 - 2005-08-04
14241 o Bugfixes on 0.1.0.x:
14242 - Fix a critical bug in the security of our crypto handshakes.
14243 - Fix a size_t underflow in smartlist_join_strings2() that made
14244 it do bad things when you hand it an empty smartlist.
14245 - Fix Windows installer to ship Tor license (thanks to Aphex for
14246 pointing out this oversight) and put a link to the doc directory
14248 - Explicitly set no-unaligned-access for sparc: it turns out the
14249 new gcc's let you compile broken code, but that doesn't make it
14253 Changes in version 0.1.1.3-alpha - 2005-07-23
14254 o Bugfixes on 0.1.1.2-alpha:
14255 - Fix a bug in handling the controller's "post descriptor"
14257 - Fix several bugs in handling the controller's "extend circuit"
14259 - Fix a bug in handling the controller's "stream status" event.
14260 - Fix an assert failure if we have a controller listening for
14261 circuit events and we go offline.
14262 - Re-allow hidden service descriptors to publish 0 intro points.
14263 - Fix a crash when generating your hidden service descriptor if
14264 you don't have enough intro points already.
14266 o New features on 0.1.1.2-alpha:
14267 - New controller function "getinfo accounting", to ask how
14268 many bytes we've used in this time period.
14269 - Experimental support for helper nodes: a lot of the risk from
14270 a small static adversary comes because users pick new random
14271 nodes every time they rebuild a circuit. Now users will try to
14272 stick to the same small set of entry nodes if they can. Not
14273 enabled by default yet.
14275 o Bugfixes on 0.1.0.12:
14276 - If you're an auth dir server, always publish your dirport,
14277 even if you haven't yet found yourself to be reachable.
14278 - Fix a size_t underflow in smartlist_join_strings2() that made
14279 it do bad things when you hand it an empty smartlist.
14282 Changes in version 0.1.0.12 - 2005-07-18
14283 o New directory servers:
14284 - tor26 has changed IP address.
14286 o Bugfixes on 0.1.0.x:
14287 - Fix a possible double-free in tor_gzip_uncompress().
14288 - When --disable-threads is set, do not search for or link against
14289 pthreads libraries.
14290 - Don't trigger an assert if an authoritative directory server
14291 claims its dirport is 0.
14292 - Fix bug with removing Tor as an NT service: some people were
14293 getting "The service did not return an error." Thanks to Matt
14297 Changes in version 0.1.1.2-alpha - 2005-07-15
14298 o New directory servers:
14299 - tor26 has changed IP address.
14301 o Bugfixes on 0.1.0.x, crashes/leaks:
14302 - Port the servers-not-obeying-their-exit-policies fix from
14304 - Fix an fd leak in start_daemon().
14305 - On Windows, you can't always reopen a port right after you've
14306 closed it. So change retry_listeners() to only close and re-open
14307 ports that have changed.
14308 - Fix a possible double-free in tor_gzip_uncompress().
14310 o Bugfixes on 0.1.0.x, usability:
14311 - When tor_socketpair() fails in Windows, give a reasonable
14312 Windows-style errno back.
14313 - Let people type "tor --install" as well as "tor -install" when
14315 want to make it an NT service.
14316 - NT service patch from Matt Edman to improve error messages.
14317 - When the controller asks for a config option with an abbreviated
14318 name, give the full name in our response.
14319 - Correct the man page entry on TrackHostExitsExpire.
14320 - Looks like we were never delivering deflated (i.e. compressed)
14321 running-routers lists, even when asked. Oops.
14322 - When --disable-threads is set, do not search for or link against
14323 pthreads libraries.
14325 o Bugfixes on 0.1.1.x:
14326 - Fix a seg fault with autodetecting which controller version is
14330 - New hidden service descriptor format: put a version in it, and
14331 let people specify introduction/rendezvous points that aren't
14332 in "the directory" (which is subjective anyway).
14333 - Allow the DEBUG controller event to work again. Mark certain log
14334 entries as "don't tell this to controllers", so we avoid cycles.
14337 Changes in version 0.1.0.11 - 2005-06-30
14338 o Bugfixes on 0.1.0.x:
14339 - Fix major security bug: servers were disregarding their
14340 exit policies if clients behaved unexpectedly.
14341 - Make OS X init script check for missing argument, so we don't
14342 confuse users who invoke it incorrectly.
14343 - Fix a seg fault in "tor --hash-password foo".
14344 - The MAPADDRESS control command was broken.
14347 Changes in version 0.1.1.1-alpha - 2005-06-29
14349 - Make OS X init script check for missing argument, so we don't
14350 confuse users who invoke it incorrectly.
14351 - Fix a seg fault in "tor --hash-password foo".
14352 - Fix a possible way to DoS dirservers.
14353 - When we complain that your exit policy implicitly allows local or
14354 private address spaces, name them explicitly so operators can
14356 - Make the log message less scary when all the dirservers are
14357 temporarily unreachable.
14358 - We were printing the number of idle dns workers incorrectly when
14362 - Revised controller protocol (version 1) that uses ascii rather
14363 than binary. Add supporting libraries in python and java so you
14364 can use the controller from your applications without caring how
14365 our protocol works.
14366 - Spiffy new support for crypto hardware accelerators. Can somebody
14370 Changes in version 0.0.9.10 - 2005-06-16
14371 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
14372 - Refuse relay cells that claim to have a length larger than the
14373 maximum allowed. This prevents a potential attack that could read
14374 arbitrary memory (e.g. keys) from an exit server's process
14378 Changes in version 0.1.0.10 - 2005-06-14
14379 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
14380 libevent before 1.1a.
14383 Changes in version 0.1.0.9-rc - 2005-06-09
14385 - Reset buf->highwater every time buf_shrink() is called, not just on
14386 a successful shrink. This was causing significant memory bloat.
14387 - Fix buffer overflow when checking hashed passwords.
14388 - Security fix: if seeding the RNG on Win32 fails, quit.
14389 - Allow seeding the RNG on Win32 even when you're not running as
14391 - Disable threading on Solaris too. Something is wonky with it,
14392 cpuworkers, and reentrant libs.
14393 - Reenable the part of the code that tries to flush as soon as an
14394 OR outbuf has a full TLS record available. Perhaps this will make
14395 OR outbufs not grow as huge except in rare cases, thus saving lots
14396 of CPU time plus memory.
14397 - Reject malformed .onion addresses rather then passing them on as
14398 normal web requests.
14399 - Adapt patch from Adam Langley: fix possible memory leak in
14400 tor_lookup_hostname().
14401 - Initialize libevent later in the startup process, so the logs are
14402 already established by the time we start logging libevent warns.
14403 - Use correct errno on win32 if libevent fails.
14404 - Check and warn about known-bad/slow libevent versions.
14405 - Pay more attention to the ClientOnly config option.
14406 - Have torctl.in/tor.sh.in check for location of su binary (needed
14408 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
14409 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
14410 HttpProxyAuthenticator
14411 - Stop warning about sigpipes in the logs. We're going to
14412 pretend that getting these occassionally is normal and fine.
14413 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
14415 installer screens; and don't put stuff into StartupItems unless
14416 the user asks you to.
14417 - Require servers that use the default dirservers to have public IP
14418 addresses. We have too many servers that are configured with private
14419 IPs and their admins never notice the log entries complaining that
14420 their descriptors are being rejected.
14421 - Add OSX uninstall instructions. An actual uninstall script will
14425 Changes in version 0.1.0.8-rc - 2005-05-23
14427 - It turns out that kqueue on OS X 10.3.9 was causing kernel
14428 panics. Disable kqueue on all OS X Tors.
14429 - Fix RPM: remove duplicate line accidentally added to the rpm
14431 - Disable threads on openbsd too, since its gethostaddr is not
14433 - Tolerate libevent 0.8 since it still works, even though it's
14435 - Enable building on Red Hat 9.0 again.
14436 - Allow the middle hop of the testing circuit to be running any
14437 version, now that most of them have the bugfix to let them connect
14438 to unknown servers. This will allow reachability testing to work
14439 even when 0.0.9.7-0.0.9.9 become obsolete.
14440 - Handle relay cells with rh.length too large. This prevents
14441 a potential attack that could read arbitrary memory (maybe even
14442 keys) from the exit server's process.
14443 - We screwed up the dirport reachability testing when we don't yet
14444 have a cached version of the directory. Hopefully now fixed.
14445 - Clean up router_load_single_router() (used by the controller),
14446 so it doesn't seg fault on error.
14447 - Fix a minor memory leak when somebody establishes an introduction
14448 point at your Tor server.
14449 - If a socks connection ends because read fails, don't warn that
14450 you're not sending a socks reply back.
14453 - Add HttpProxyAuthenticator config option too, that works like
14454 the HttpsProxyAuthenticator config option.
14455 - Encode hashed controller passwords in hex instead of base64,
14456 to make it easier to write controllers.
14459 Changes in version 0.1.0.7-rc - 2005-05-17
14461 - Fix a bug in the OS X package installer that prevented it from
14462 installing on Tiger.
14463 - Fix a script bug in the OS X package installer that made it
14464 complain during installation.
14465 - Find libevent even if it's hiding in /usr/local/ and your
14466 CFLAGS and LDFLAGS don't tell you to look there.
14467 - Be able to link with libevent as a shared library (the default
14468 after 1.0d), even if it's hiding in /usr/local/lib and even
14469 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
14470 assuming you're running gcc. Otherwise fail and give a useful
14472 - Fix a bug in the RPM packager: set home directory for _tor to
14473 something more reasonable when first installing.
14474 - Free a minor amount of memory that is still reachable on exit.
14477 Changes in version 0.1.0.6-rc - 2005-05-14
14479 - Implement --disable-threads configure option. Disable threads on
14480 netbsd by default, because it appears to have no reentrant resolver
14482 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
14483 release (1.1) detects and disables kqueue if it's broken.
14484 - Append default exit policy before checking for implicit internal
14485 addresses. Now we don't log a bunch of complaints on startup
14486 when using the default exit policy.
14487 - Some people were putting "Address " in their torrc, and they had
14488 a buggy resolver that resolved " " to 0.0.0.0. Oops.
14489 - If DataDir is ~/.tor, and that expands to /.tor, then default to
14490 LOCALSTATEDIR/tor instead.
14491 - Fix fragmented-message bug in TorControl.py.
14492 - Resolve a minor bug which would prevent unreachable dirports
14493 from getting suppressed in the published descriptor.
14494 - When the controller gave us a new descriptor, we weren't resolving
14495 it immediately, so Tor would think its address was 0.0.0.0 until
14496 we fetched a new directory.
14497 - Fix an uppercase/lowercase case error in suppressing a bogus
14498 libevent warning on some Linuxes.
14501 - Begin scrubbing sensitive strings from logs by default. Turn off
14502 the config option SafeLogging if you need to do debugging.
14503 - Switch to a new buffer management algorithm, which tries to avoid
14504 reallocing and copying quite as much. In first tests it looks like
14505 it uses *more* memory on average, but less cpu.
14506 - First cut at support for "create-fast" cells. Clients can use
14507 these when extending to their first hop, since the TLS already
14508 provides forward secrecy and authentication. Not enabled on
14510 - When dirservers refuse a router descriptor, we now log its
14511 contactinfo, platform, and the poster's IP address.
14512 - Call tor_free_all instead of connections_free_all after forking, to
14513 save memory on systems that need to fork.
14514 - Whine at you if you're a server and you don't set your contactinfo.
14515 - Implement --verify-config command-line option to check if your torrc
14516 is valid without actually launching Tor.
14517 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
14518 rather than just rejecting it.
14521 Changes in version 0.1.0.5-rc - 2005-04-27
14523 - Stop trying to print a null pointer if an OR conn fails because
14524 we didn't like its cert.
14526 - Switch our internal buffers implementation to use a ring buffer,
14527 to hopefully improve performance for fast servers a lot.
14528 - Add HttpsProxyAuthenticator support (basic auth only), based
14529 on patch from Adam Langley.
14530 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
14531 the fast servers that have been joining lately.
14532 - Give hidden service accesses extra time on the first attempt,
14533 since 60 seconds is often only barely enough. This might improve
14535 - Improve performance for dirservers: stop re-parsing the whole
14536 directory every time you regenerate it.
14537 - Add more debugging info to help us find the weird dns freebsd
14538 pthreads bug; cleaner debug messages to help track future issues.
14541 Changes in version 0.0.9.9 - 2005-04-23
14542 o Bugfixes on 0.0.9.x:
14543 - If unofficial Tor clients connect and send weird TLS certs, our
14544 Tor server triggers an assert. This release contains a minimal
14545 backport from the broader fix that we put into 0.1.0.4-rc.
14548 Changes in version 0.1.0.4-rc - 2005-04-23
14550 - If unofficial Tor clients connect and send weird TLS certs, our
14551 Tor server triggers an assert. Stop asserting, and start handling
14552 TLS errors better in other situations too.
14553 - When the controller asks us to tell it about all the debug-level
14554 logs, it turns out we were generating debug-level logs while
14555 telling it about them, which turns into a bad loop. Now keep
14556 track of whether you're sending a debug log to the controller,
14557 and don't log when you are.
14558 - Fix the "postdescriptor" feature of the controller interface: on
14559 non-complete success, only say "done" once.
14561 - Clients are now willing to load balance over up to 2mB, not 1mB,
14562 of advertised bandwidth capacity.
14563 - Add a NoPublish config option, so you can be a server (e.g. for
14564 testing running Tor servers in other Tor networks) without
14565 publishing your descriptor to the primary dirservers.
14568 Changes in version 0.1.0.3-rc - 2005-04-08
14569 o Improvements on 0.1.0.2-rc:
14570 - Client now retries when streams end early for 'hibernating' or
14571 'resource limit' reasons, rather than failing them.
14572 - More automated handling for dirserver operators:
14573 - Automatically approve nodes running 0.1.0.2-rc or later,
14574 now that the the reachability detection stuff is working.
14575 - Now we allow two unverified servers with the same nickname
14576 but different keys. But if a nickname is verified, only that
14577 nickname+key are allowed.
14578 - If you're an authdirserver connecting to an address:port,
14579 and it's not the OR you were expecting, forget about that
14580 descriptor. If he *was* the one you were expecting, then forget
14581 about all other descriptors for that address:port.
14582 - Allow servers to publish descriptors from 12 hours in the future.
14583 Corollary: only whine about clock skew from the dirserver if
14584 he's a trusted dirserver (since now even verified servers could
14585 have quite wrong clocks).
14586 - Adjust maximum skew and age for rendezvous descriptors: let skew
14587 be 48 hours rather than 90 minutes.
14588 - Efficiency improvements:
14589 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
14590 it much faster to look up a circuit for each relay cell.
14591 - Remove most calls to assert_all_pending_dns_resolves_ok(),
14592 since they're eating our cpu on exit nodes.
14593 - Stop wasting time doing a case insensitive comparison for every
14594 dns name every time we do any lookup. Canonicalize the names to
14595 lowercase and be done with it.
14596 - Start sending 'truncated' cells back rather than destroy cells,
14597 if the circuit closes in front of you. This means we won't have
14598 to abandon partially built circuits.
14599 - Only warn once per nickname from add_nickname_list_to_smartlist
14600 per failure, so an entrynode or exitnode choice that's down won't
14602 - Put a note in the torrc about abuse potential with the default
14604 - Revise control spec and implementation to allow all log messages to
14605 be sent to controller with their severities intact (suggested by
14606 Matt Edman). Update TorControl to handle new log event types.
14607 - Provide better explanation messages when controller's POSTDESCRIPTOR
14609 - Stop putting nodename in the Platform string in server descriptors.
14610 It doesn't actually help, and it is confusing/upsetting some people.
14612 o Bugfixes on 0.1.0.2-rc:
14613 - We were printing the host mask wrong in exit policies in server
14614 descriptors. This isn't a critical bug though, since we were still
14615 obeying the exit policy internally.
14616 - Fix Tor when compiled with libevent but without pthreads: move
14617 connection_unregister() from _connection_free() to
14619 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
14620 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
14621 when we look through the connection array, we'll find any of the
14622 cpu/dnsworkers. This is no good.
14624 o Bugfixes on 0.0.9.8:
14625 - Fix possible bug on threading platforms (e.g. win32) which was
14626 leaking a file descriptor whenever a cpuworker or dnsworker died.
14627 - When using preferred entry or exit nodes, ignore whether the
14628 circuit wants uptime or capacity. They asked for the nodes, they
14630 - chdir() to your datadirectory at the *end* of the daemonize process,
14631 not the beginning. This was a problem because the first time you
14632 run tor, if your datadir isn't there, and you have runasdaemon set
14633 to 1, it will try to chdir to it before it tries to create it. Oops.
14634 - Handle changed router status correctly when dirserver reloads
14635 fingerprint file. We used to be dropping all unverified descriptors
14636 right then. The bug was hidden because we would immediately
14637 fetch a directory from another dirserver, which would include the
14638 descriptors we just dropped.
14639 - When we're connecting to an OR and he's got a different nickname/key
14640 than we were expecting, only complain loudly if we're an OP or a
14641 dirserver. Complaining loudly to the OR admins just confuses them.
14642 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
14643 artificially capped at 500kB.
14646 Changes in version 0.0.9.8 - 2005-04-07
14647 o Bugfixes on 0.0.9.x:
14648 - We have a bug that I haven't found yet. Sometimes, very rarely,
14649 cpuworkers get stuck in the 'busy' state, even though the cpuworker
14650 thinks of itself as idle. This meant that no new circuits ever got
14651 established. Here's a workaround to kill any cpuworker that's been
14652 busy for more than 100 seconds.
14655 Changes in version 0.1.0.2-rc - 2005-04-01
14656 o Bugfixes on 0.1.0.1-rc:
14657 - Fixes on reachability detection:
14658 - Don't check for reachability while hibernating.
14659 - If ORPort is reachable but DirPort isn't, still publish the
14660 descriptor, but zero out DirPort until it's found reachable.
14661 - When building testing circs for ORPort testing, use only
14662 high-bandwidth nodes, so fewer circuits fail.
14663 - Complain about unreachable ORPort separately from unreachable
14664 DirPort, so the user knows what's going on.
14665 - Make sure we only conclude ORPort reachability if we didn't
14666 initiate the conn. Otherwise we could falsely conclude that
14667 we're reachable just because we connected to the guy earlier
14668 and he used that same pipe to extend to us.
14669 - Authdirservers shouldn't do ORPort reachability detection,
14670 since they're in clique mode, so it will be rare to find a
14671 server not already connected to them.
14672 - When building testing circuits, always pick middle hops running
14673 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
14674 bug. (This is a kludge; it will go away when 0.0.9.x becomes
14676 - When we decide we're reachable, actually publish our descriptor
14678 - Fix bug in redirectstream in the controller.
14679 - Fix the state descriptor strings so logs don't claim edge streams
14680 are in a different state than they actually are.
14681 - Use recent libevent features when possible (this only really affects
14682 win32 and osx right now, because the new libevent with these
14683 features hasn't been released yet). Add code to suppress spurious
14685 - Prevent possible segfault in connection_close_unattached_ap().
14686 - Fix newlines on torrc in win32.
14687 - Improve error msgs when tor-resolve fails.
14689 o Improvements on 0.0.9.x:
14690 - New experimental script tor/contrib/ExerciseServer.py (needs more
14691 work) that uses the controller interface to build circuits and
14692 fetch pages over them. This will help us bootstrap servers that
14693 have lots of capacity but haven't noticed it yet.
14694 - New experimental script tor/contrib/PathDemo.py (needs more work)
14695 that uses the controller interface to let you choose whole paths
14697 "<hostname>.<path,separated by dots>.<length of path>.path"
14698 - When we've connected to an OR and handshaked but didn't like
14699 the result, we were closing the conn without sending destroy
14700 cells back for pending circuits. Now send those destroys.
14703 Changes in version 0.0.9.7 - 2005-04-01
14704 o Bugfixes on 0.0.9.x:
14705 - Fix another race crash bug (thanks to Glenn Fink for reporting).
14706 - Compare identity to identity, not to nickname, when extending to
14707 a router not already in the directory. This was preventing us from
14708 extending to unknown routers. Oops.
14709 - Make sure to create OS X Tor user in <500 range, so we aren't
14710 creating actual system users.
14711 - Note where connection-that-hasn't-sent-end was marked, and fix
14712 a few really loud instances of this harmless bug (it's fixed more
14716 Changes in version 0.1.0.1-rc - 2005-03-28
14718 - Add reachability testing. Your Tor server will automatically try
14719 to see if its ORPort and DirPort are reachable from the outside,
14720 and it won't upload its descriptor until it decides they are.
14721 - Handle unavailable hidden services better. Handle slow or busy
14722 hidden services better.
14723 - Add support for CONNECTing through https proxies, with "HttpsProxy"
14725 - New exit policy: accept most low-numbered ports, rather than
14726 rejecting most low-numbered ports.
14727 - More Tor controller support (still experimental). See
14728 http://tor.eff.org/doc/control-spec.txt for all the new features,
14729 including signals to emulate unix signals from any platform;
14730 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
14731 closestream; closecircuit; etc.
14732 - Make nt services work and start on startup on win32 (based on
14733 patch by Matt Edman).
14734 - Add a new AddressMap config directive to rewrite incoming socks
14735 addresses. This lets you, for example, declare an implicit
14736 required exit node for certain sites.
14737 - Add a new TrackHostExits config directive to trigger addressmaps
14738 for certain incoming socks addresses -- for sites that break when
14739 your exit keeps changing (based on patch by Mike Perry).
14740 - Redo the client-side dns cache so it's just an addressmap too.
14741 - Notice when our IP changes, and reset stats/uptime/reachability.
14742 - When an application is using socks5, give him the whole variety of
14743 potential socks5 responses (connect refused, host unreachable, etc),
14744 rather than just "success" or "failure".
14745 - A more sane version numbering system. See
14746 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
14747 - New contributed script "exitlist": a simple python script to
14748 parse directories and find Tor nodes that exit to listed
14750 - New contributed script "privoxy-tor-toggle" to toggle whether
14751 Privoxy uses Tor. Seems to be configured for Debian by default.
14752 - Report HTTP reasons to client when getting a response from directory
14753 servers -- so you can actually know what went wrong.
14754 - New config option MaxAdvertisedBandwidth which lets you advertise
14755 a low bandwidthrate (to not attract as many circuits) while still
14756 allowing a higher bandwidthrate in reality.
14758 o Robustness/stability fixes:
14759 - Make Tor use Niels Provos's libevent instead of its current
14760 poll-but-sometimes-select mess. This will let us use faster async
14761 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
14763 - pthread support now too. This was forced because when we forked,
14764 we ended up wasting a lot of duplicate ram over time. Also switch
14765 to foo_r versions of some library calls to allow reentry and
14767 - Better handling for heterogeneous / unreliable nodes:
14768 - Annotate circuits w/ whether they aim to contain high uptime nodes
14769 and/or high capacity nodes. When building circuits, choose
14771 - This means that every single node in an intro rend circuit,
14772 not just the last one, will have a minimum uptime.
14773 - New config option LongLivedPorts to indicate application streams
14774 that will want high uptime circuits.
14775 - Servers reset uptime when a dir fetch entirely fails. This
14776 hopefully reflects stability of the server's network connectivity.
14777 - If somebody starts his tor server in Jan 2004 and then fixes his
14778 clock, don't make his published uptime be a year.
14779 - Reset published uptime when you wake up from hibernation.
14780 - Introduce a notion of 'internal' circs, which are chosen without
14781 regard to the exit policy of the last hop. Intro and rendezvous
14782 circs must be internal circs, to avoid leaking information. Resolve
14783 and connect streams can use internal circs if they want.
14784 - New circuit pooling algorithm: make sure to have enough circs around
14785 to satisfy any predicted ports, and also make sure to have 2 internal
14786 circs around if we've required internal circs lately (and with high
14787 uptime if we've seen that lately too).
14788 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
14789 which describes how often we retry making new circuits if current
14790 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
14791 how long we're willing to make use of an already-dirty circuit.
14792 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
14793 circ as necessary, if there are any completed ones lying around
14794 when we try to launch one.
14795 - Make hidden services try to establish a rendezvous for 30 seconds,
14796 rather than for n (where n=3) attempts to build a circuit.
14797 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
14798 "ShutdownWaitLength".
14799 - Try to be more zealous about calling connection_edge_end when
14800 things go bad with edge conns in connection.c.
14801 - Revise tor-spec to add more/better stream end reasons.
14802 - Revise all calls to connection_edge_end to avoid sending "misc",
14803 and to take errno into account where possible.
14806 - Fix a race condition that can trigger an assert, when we have a
14807 pending create cell and an OR connection fails right then.
14808 - Fix several double-mark-for-close bugs, e.g. where we were finding
14809 a conn for a cell even if that conn is already marked for close.
14810 - Make sequence of log messages when starting on win32 with no config
14811 file more reasonable.
14812 - When choosing an exit node for a new non-internal circ, don't take
14813 into account whether it'll be useful for any pending x.onion
14814 addresses -- it won't.
14815 - Turn addr_policy_compare from a tristate to a quadstate; this should
14816 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
14817 for google.com" problem.
14818 - Make "platform" string in descriptor more accurate for Win32 servers,
14819 so it's not just "unknown platform".
14820 - Fix an edge case in parsing config options (thanks weasel).
14821 If they say "--" on the commandline, it's not an option.
14822 - Reject odd-looking addresses at the client (e.g. addresses that
14823 contain a colon), rather than having the server drop them because
14825 - tor-resolve requests were ignoring .exit if there was a working circuit
14826 they could use instead.
14827 - REUSEADDR on normal platforms means you can rebind to the port
14828 right after somebody else has let it go. But REUSEADDR on win32
14829 means to let you bind to the port _even when somebody else
14830 already has it bound_! So, don't do that on Win32.
14831 - Change version parsing logic: a version is "obsolete" if it is not
14832 recommended and (1) there is a newer recommended version in the
14833 same series, or (2) there are no recommended versions in the same
14834 series, but there are some recommended versions in a newer series.
14835 A version is "new" if it is newer than any recommended version in
14837 - Stop most cases of hanging up on a socks connection without sending
14841 - Require BandwidthRate to be at least 20kB/s for servers.
14842 - When a dirserver causes you to give a warn, mention which dirserver
14844 - New config option DirAllowPrivateAddresses for authdirservers.
14845 Now by default they refuse router descriptors that have non-IP or
14846 private-IP addresses.
14847 - Stop publishing socksport in the directory, since it's not
14848 actually meant to be public. For compatibility, publish a 0 there
14850 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
14851 smart" value, that is low for servers and high for clients.
14852 - If our clock jumps forward by 100 seconds or more, assume something
14853 has gone wrong with our network and abandon all not-yet-used circs.
14854 - Warn when exit policy implicitly allows local addresses.
14855 - If we get an incredibly skewed timestamp from a dirserver mirror
14856 that isn't a verified OR, don't warn -- it's probably him that's
14858 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
14859 cookies to disk and doesn't log each web request to disk. (Thanks
14860 to Brett Carrington for pointing this out.)
14861 - When a client asks us for a dir mirror and we don't have one,
14862 launch an attempt to get a fresh one.
14863 - If we're hibernating and we get a SIGINT, exit immediately.
14864 - Add --with-dmalloc ./configure option, to track memory leaks.
14865 - And try to free all memory on closing, so we can detect what
14867 - Cache local dns resolves correctly even when they're .exit
14869 - Give a better warning when some other server advertises an
14870 ORPort that is actually an apache running ssl.
14871 - Add "opt hibernating 1" to server descriptor to make it clearer
14872 whether the server is hibernating.
14875 Changes in version 0.0.9.6 - 2005-03-24
14876 o Bugfixes on 0.0.9.x (crashes and asserts):
14877 - Add new end stream reasons to maintainance branch. Fix bug where
14878 reason (8) could trigger an assert. Prevent bug from recurring.
14879 - Apparently win32 stat wants paths to not end with a slash.
14880 - Fix assert triggers in assert_cpath_layer_ok(), where we were
14881 blowing away the circuit that conn->cpath_layer points to, then
14882 checking to see if the circ is well-formed. Backport check to make
14883 sure we dont use the cpath on a closed connection.
14884 - Prevent circuit_resume_edge_reading_helper() from trying to package
14885 inbufs for marked-for-close streams.
14886 - Don't crash on hup if your options->address has become unresolvable.
14887 - Some systems (like OS X) sometimes accept() a connection and tell
14888 you the remote host is 0.0.0.0:0. If this happens, due to some
14889 other mis-features, we get confused; so refuse the conn for now.
14891 o Bugfixes on 0.0.9.x (other):
14892 - Fix harmless but scary "Unrecognized content encoding" warn message.
14893 - Add new stream error reason: TORPROTOCOL reason means "you are not
14894 speaking a version of Tor I understand; say bye-bye to your stream."
14895 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
14896 into the future, now that we are more tolerant of skew. This
14897 resolves a bug where a Tor server would refuse to cache a directory
14898 because all the directories it gets are too far in the future;
14899 yet the Tor server never logs any complaints about clock skew.
14900 - Mac packaging magic: make man pages useable, and do not overwrite
14901 existing torrc files.
14902 - Make OS X log happily to /var/log/tor/tor.log
14905 Changes in version 0.0.9.5 - 2005-02-22
14906 o Bugfixes on 0.0.9.x:
14907 - Fix an assert race at exit nodes when resolve requests fail.
14908 - Stop picking unverified dir mirrors--it only leads to misery.
14909 - Patch from Matt Edman to make NT services work better. Service
14910 support is still not compiled into the executable by default.
14911 - Patch from Dmitri Bely so the Tor service runs better under
14912 the win32 SYSTEM account.
14913 - Make tor-resolve actually work (?) on Win32.
14914 - Fix a sign bug when getrlimit claims to have 4+ billion
14915 file descriptors available.
14916 - Stop refusing to start when bandwidthburst == bandwidthrate.
14917 - When create cells have been on the onion queue more than five
14918 seconds, just send back a destroy and take them off the list.
14921 Changes in version 0.0.9.4 - 2005-02-03
14922 o Bugfixes on 0.0.9:
14923 - Fix an assert bug that took down most of our servers: when
14924 a server claims to have 1 GB of bandwidthburst, don't
14926 - Don't crash as badly if we have spawned the max allowed number
14927 of dnsworkers, or we're out of file descriptors.
14928 - Block more file-sharing ports in the default exit policy.
14929 - MaxConn is now automatically set to the hard limit of max
14930 file descriptors we're allowed (ulimit -n), minus a few for
14932 - Give a clearer message when servers need to raise their
14933 ulimit -n when they start running out of file descriptors.
14934 - SGI Compatibility patches from Jan Schaumann.
14935 - Tolerate a corrupt cached directory better.
14936 - When a dirserver hasn't approved your server, list which one.
14937 - Go into soft hibernation after 95% of the bandwidth is used,
14938 not 99%. This is especially important for daily hibernators who
14939 have a small accounting max. Hopefully it will result in fewer
14940 cut connections when the hard hibernation starts.
14941 - Load-balance better when using servers that claim more than
14942 800kB/s of capacity.
14943 - Make NT services work (experimental, only used if compiled in).
14946 Changes in version 0.0.9.3 - 2005-01-21
14947 o Bugfixes on 0.0.9:
14948 - Backport the cpu use fixes from main branch, so busy servers won't
14949 need as much processor time.
14950 - Work better when we go offline and then come back, or when we
14951 run Tor at boot before the network is up. We do this by
14952 optimistically trying to fetch a new directory whenever an
14953 application request comes in and we think we're offline -- the
14954 human is hopefully a good measure of when the network is back.
14955 - Backport some minimal hidserv bugfixes: keep rend circuits open as
14956 long as you keep using them; actually publish hidserv descriptors
14957 shortly after they change, rather than waiting 20-40 minutes.
14958 - Enable Mac startup script by default.
14959 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
14960 - When you update AllowUnverifiedNodes or FirewallPorts via the
14961 controller's setconf feature, we were always appending, never
14963 - When you update HiddenServiceDir via setconf, it was screwing up
14964 the order of reading the lines, making it fail.
14965 - Do not rewrite a cached directory back to the cache; otherwise we
14966 will think it is recent and not fetch a newer one on startup.
14967 - Workaround for webservers that lie about Content-Encoding: Tor
14968 now tries to autodetect compressed directories and compression
14969 itself. This lets us Proxypass dir fetches through apache.
14972 Changes in version 0.0.9.2 - 2005-01-04
14973 o Bugfixes on 0.0.9 (crashes and asserts):
14974 - Fix an assert on startup when the disk is full and you're logging
14976 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
14977 style address, then we'd crash.
14978 - Fix an assert trigger when the running-routers string we get from
14979 a dirserver is broken.
14980 - Make worker threads start and run on win32. Now win32 servers
14982 - Bandaid (not actually fix, but now it doesn't crash) an assert
14983 where the dns worker dies mysteriously and the main Tor process
14984 doesn't remember anything about the address it was resolving.
14986 o Bugfixes on 0.0.9 (Win32):
14987 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
14988 name out of the warning/assert messages.
14989 - Fix a superficial "unhandled error on read" bug on win32.
14990 - The win32 installer no longer requires a click-through for our
14991 license, since our Free Software license grants rights but does not
14993 - Win32: When connecting to a dirserver fails, try another one
14994 immediately. (This was already working for non-win32 Tors.)
14995 - Stop trying to parse $HOME on win32 when hunting for default
14997 - Make tor-resolve.c work on win32 by calling network_init().
14999 o Bugfixes on 0.0.9 (other):
15000 - Make 0.0.9.x build on Solaris again.
15001 - Due to a fencepost error, we were blowing away the \n when reporting
15002 confvalue items in the controller. So asking for multiple config
15003 values at once couldn't work.
15004 - When listing circuits that are pending on an opening OR connection,
15005 if we're an OR we were listing circuits that *end* at us as
15006 being pending on every listener, dns/cpu worker, etc. Stop that.
15007 - Dirservers were failing to create 'running-routers' or 'directory'
15008 strings if we had more than some threshold of routers. Fix them so
15009 they can handle any number of routers.
15010 - Fix a superficial "Duplicate mark for close" bug.
15011 - Stop checking for clock skew for OR connections, even for servers.
15012 - Fix a fencepost error that was chopping off the last letter of any
15013 nickname that is the maximum allowed nickname length.
15014 - Update URLs in log messages so they point to the new website.
15015 - Fix a potential problem in mangling server private keys while
15016 writing to disk (not triggered yet, as far as we know).
15017 - Include the licenses for other free software we include in Tor,
15018 now that we're shipping binary distributions more regularly.
15021 Changes in version 0.0.9.1 - 2004-12-15
15022 o Bugfixes on 0.0.9:
15023 - Make hibernation actually work.
15024 - Make HashedControlPassword config option work.
15025 - When we're reporting event circuit status to a controller,
15026 don't use the stream status code.
15029 Changes in version 0.0.9 - 2004-12-12
15031 - Clean up manpage and torrc.sample file.
15032 - Clean up severities and text of log warnings.
15034 - Make servers trigger an assert when they enter hibernation.
15037 Changes in version 0.0.9rc7 - 2004-12-08
15038 o Bugfixes on 0.0.9rc:
15039 - Fix a stack-trashing crash when an exit node begins hibernating.
15040 - Avoid looking at unallocated memory while considering which
15041 ports we need to build circuits to cover.
15042 - Stop a sigpipe: when an 'end' cell races with eof from the app,
15043 we shouldn't hold-open-until-flush if the eof arrived first.
15044 - Fix a bug with init_cookie_authentication() in the controller.
15045 - When recommending new-format log lines, if the upper bound is
15046 LOG_ERR, leave it implicit.
15048 o Bugfixes on 0.0.8.1:
15049 - Fix a whole slew of memory leaks.
15050 - Fix isspace() and friends so they still make Solaris happy
15051 but also so they don't trigger asserts on win32.
15052 - Fix parse_iso_time on platforms without strptime (eg win32).
15053 - win32: tolerate extra "readable" events better.
15054 - win32: when being multithreaded, leave parent fdarray open.
15055 - Make unit tests work on win32.
15058 Changes in version 0.0.9rc6 - 2004-12-06
15059 o Bugfixes on 0.0.9pre:
15060 - Clean up some more integer underflow opportunities (not exploitable
15062 - While hibernating, hup should not regrow our listeners.
15063 - Send an end to the streams we close when we hibernate, rather
15064 than just chopping them off.
15065 - React to eof immediately on non-open edge connections.
15067 o Bugfixes on 0.0.8.1:
15068 - Calculate timeout for waiting for a connected cell from the time
15069 we sent the begin cell, not from the time the stream started. If
15070 it took a long time to establish the circuit, we would time out
15071 right after sending the begin cell.
15072 - Fix router_compare_addr_to_addr_policy: it was not treating a port
15073 of * as always matching, so we were picking reject *:* nodes as
15074 exit nodes too. Oops.
15077 - New circuit building strategy: keep a list of ports that we've
15078 used in the past 6 hours, and always try to have 2 circuits open
15079 or on the way that will handle each such port. Seed us with port
15080 80 so web users won't complain that Tor is "slow to start up".
15081 - Make kill -USR1 dump more useful stats about circuits.
15082 - When warning about retrying or giving up, print the address, so
15083 the user knows which one it's talking about.
15084 - If you haven't used a clean circuit in an hour, throw it away,
15085 just to be on the safe side. (This means after 6 hours a totally
15086 unused Tor client will have no circuits open.)
15089 Changes in version 0.0.9rc5 - 2004-12-01
15090 o Bugfixes on 0.0.8.1:
15091 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
15092 - Let resolve conns retry/expire also, rather than sticking around
15094 - If we are using select, make sure we stay within FD_SETSIZE.
15096 o Bugfixes on 0.0.9pre:
15097 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
15098 but doesn't seem to be currently; thanks to Ilja van Sprundel for
15100 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
15101 instead. Impose minima and maxima for all *Period options; impose
15102 even tighter maxima for fetching if we are a caching dirserver.
15103 Clip rather than rejecting.
15104 - Fetch cached running-routers from servers that serve it (that is,
15105 authdirservers and servers running 0.0.9rc5-cvs or later.)
15108 - Accept *:706 (silc) in default exit policy.
15109 - Implement new versioning format for post 0.1.
15110 - Support "foo.nickname.exit" addresses, to let Alice request the
15111 address "foo" as viewed by exit node "nickname". Based on a patch
15113 - Make tor --version --version dump the cvs Id of every file.
15116 Changes in version 0.0.9rc4 - 2004-11-28
15117 o Bugfixes on 0.0.8.1:
15118 - Make windows sockets actually non-blocking (oops), and handle
15119 win32 socket errors better.
15121 o Bugfixes on 0.0.9rc1:
15122 - Actually catch the -USR2 signal.
15125 Changes in version 0.0.9rc3 - 2004-11-25
15126 o Bugfixes on 0.0.8.1:
15127 - Flush the log file descriptor after we print "Tor opening log file",
15128 so we don't see those messages days later.
15130 o Bugfixes on 0.0.9rc1:
15131 - Make tor-resolve work again.
15132 - Avoid infinite loop in tor-resolve if tor hangs up on it.
15133 - Fix an assert trigger for clients/servers handling resolves.
15136 Changes in version 0.0.9rc2 - 2004-11-24
15137 o Bugfixes on 0.0.9rc1:
15138 - I broke socks5 support while fixing the eof bug.
15139 - Allow unitless bandwidths and intervals; they default to bytes
15141 - New servers don't start out hibernating; they are active until
15142 they run out of bytes, so they have a better estimate of how
15143 long it takes, and so their operators can know they're working.
15146 Changes in version 0.0.9rc1 - 2004-11-23
15147 o Bugfixes on 0.0.8.1:
15148 - Finally fix a bug that's been plaguing us for a year:
15149 With high load, circuit package window was reaching 0. Whenever
15150 we got a circuit-level sendme, we were reading a lot on each
15151 socket, but only writing out a bit. So we would eventually reach
15152 eof. This would be noticed and acted on even when there were still
15153 bytes sitting in the inbuf.
15154 - When poll() is interrupted, we shouldn't believe the revents values.
15156 o Bugfixes on 0.0.9pre6:
15157 - Fix hibernate bug that caused pre6 to be broken.
15158 - Don't keep rephist info for routers that haven't had activity for
15159 24 hours. (This matters now that clients have keys, since we track
15161 - Never call close_temp_logs while validating log options.
15162 - Fix backslash-escaping on tor.sh.in and torctl.in.
15165 - Implement weekly/monthly/daily accounting: now you specify your
15166 hibernation properties by
15167 AccountingMax N bytes|KB|MB|GB|TB
15168 AccountingStart day|week|month [day] HH:MM
15169 Defaults to "month 1 0:00".
15170 - Let bandwidth and interval config options be specified as 5 bytes,
15171 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
15172 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
15173 get back to normal.)
15174 - If your requested entry or exit node has advertised bandwidth 0,
15176 - Be more greedy about filling up relay cells -- we try reading again
15177 once we've processed the stuff we read, in case enough has arrived
15178 to fill the last cell completely.
15179 - Apply NT service patch from Osamu Fujino. Still needs more work.
15182 Changes in version 0.0.9pre6 - 2004-11-15
15183 o Bugfixes on 0.0.8.1:
15184 - Fix assert failure on malformed socks4a requests.
15185 - Use identity comparison, not nickname comparison, to choose which
15186 half of circuit-ID-space each side gets to use. This is needed
15187 because sometimes we think of a router as a nickname, and sometimes
15188 as a hex ID, and we can't predict what the other side will do.
15189 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
15190 write() call will fail and we handle it there.
15191 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
15192 and smartlist_len, which are two major profiling offenders.
15194 o Bugfixes on 0.0.9pre5:
15195 - Fix a bug in read_all that was corrupting config files on windows.
15196 - When we're raising the max number of open file descriptors to
15197 'unlimited', don't log that we just raised it to '-1'.
15198 - Include event code with events, as required by control-spec.txt.
15199 - Don't give a fingerprint when clients do --list-fingerprint:
15200 it's misleading, because it will never be the same again.
15201 - Stop using strlcpy in tor_strndup, since it was slowing us
15203 - Remove warn on startup about missing cached-directory file.
15204 - Make kill -USR1 work again.
15205 - Hibernate if we start tor during the "wait for wakeup-time" phase
15206 of an accounting interval. Log our hibernation plans better.
15207 - Authoritative dirservers now also cache their directory, so they
15208 have it on start-up.
15211 - Fetch running-routers; cache running-routers; compress
15212 running-routers; serve compressed running-routers.z
15213 - Add NSI installer script contributed by J Doe.
15214 - Commit VC6 and VC7 workspace/project files.
15215 - Commit a tor.spec for making RPM files, with help from jbash.
15216 - Add contrib/torctl.in contributed by Glenn Fink.
15217 - Implement the control-spec's SAVECONF command, to write your
15218 configuration to torrc.
15219 - Get cookie authentication for the controller closer to working.
15220 - Include control-spec.txt in the tarball.
15221 - When set_conf changes our server descriptor, upload a new copy.
15222 But don't upload it too often if there are frequent changes.
15223 - Document authentication config in man page, and document signals
15225 - Clean up confusing parts of man page and torrc.sample.
15226 - Make expand_filename handle ~ and ~username.
15227 - Use autoconf to enable largefile support where necessary. Use
15228 ftello where available, since ftell can fail at 2GB.
15229 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
15230 log more informatively.
15231 - Give a slightly more useful output for "tor -h".
15232 - Refuse application socks connections to port 0.
15233 - Check clock skew for verified servers, but allow unverified
15234 servers and clients to have any clock skew.
15235 - Break DirFetchPostPeriod into:
15236 - DirFetchPeriod for fetching full directory,
15237 - StatusFetchPeriod for fetching running-routers,
15238 - DirPostPeriod for posting server descriptor,
15239 - RendPostPeriod for posting hidden service descriptors.
15240 - Make sure the hidden service descriptors are at a random offset
15241 from each other, to hinder linkability.
15244 Changes in version 0.0.9pre5 - 2004-11-09
15245 o Bugfixes on 0.0.9pre4:
15246 - Fix a seg fault in unit tests (doesn't affect main program).
15247 - Fix an assert bug where a hidden service provider would fail if
15248 the first hop of his rendezvous circuit was down.
15249 - Hidden service operators now correctly handle version 1 style
15250 INTRODUCE1 cells (nobody generates them still, so not a critical
15252 - If do_hup fails, actually notice.
15253 - Handle more errnos from accept() without closing the listener.
15254 Some OpenBSD machines were closing their listeners because
15255 they ran out of file descriptors.
15256 - Send resolve cells to exit routers that are running a new
15257 enough version of the resolve code to work right.
15258 - Better handling of winsock includes on non-MSV win32 compilers.
15259 - Some people had wrapped their tor client/server in a script
15260 that would restart it whenever it died. This did not play well
15261 with our "shut down if your version is obsolete" code. Now people
15262 don't fetch a new directory if their local cached version is
15264 - Make our autogen.sh work on ksh as well as bash.
15267 - Hibernation: New config option "AccountingMaxKB" lets you
15268 set how many KBytes per month you want to allow your server to
15269 consume. Rather than spreading those bytes out evenly over the
15270 month, we instead hibernate for some of the month and pop up
15271 at a deterministic time, work until the bytes are consumed, then
15272 hibernate again. Config option "MonthlyAccountingStart" lets you
15273 specify which day of the month your billing cycle starts on.
15274 - Control interface: a separate program can now talk to your
15275 client/server over a socket, and get/set config options, receive
15276 notifications of circuits and streams starting/finishing/dying,
15277 bandwidth used, etc. The next step is to get some GUIs working.
15278 Let us know if you want to help out. See doc/control-spec.txt .
15279 - Ship a contrib/tor-control.py as an example script to interact
15280 with the control port.
15281 - "tor --hash-password zzyxz" will output a salted password for
15282 use in authenticating to the control interface.
15283 - New log format in config:
15284 "Log minsev[-maxsev] stdout|stderr|syslog" or
15285 "Log minsev[-maxsev] file /var/foo"
15288 - DirPolicy config option, to let people reject incoming addresses
15289 from their dirserver.
15290 - "tor --list-fingerprint" will list your identity key fingerprint
15292 - Add "pass" target for RedirectExit, to make it easier to break
15293 out of a sequence of RedirectExit rules.
15294 - Clients now generate a TLS cert too, in preparation for having
15295 them act more like real nodes.
15296 - Ship src/win32/ in the tarball, so people can use it to build.
15297 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
15299 - New "router-status" line in directory, to better bind each verified
15300 nickname to its identity key.
15301 - Deprecate unofficial config option abbreviations, and abbreviations
15302 not on the command line.
15303 - Add a pure-C tor-resolve implementation.
15304 - Use getrlimit and friends to ensure we can reach MaxConn (currently
15305 1024) file descriptors.
15307 o Code security improvements, inspired by Ilja:
15308 - Replace sprintf with snprintf. (I think they were all safe, but
15310 - Replace strcpy/strncpy with strlcpy in more places.
15311 - Avoid strcat; use snprintf or strlcat instead.
15312 - snprintf wrapper with consistent (though not C99) overflow behavior.
15315 Changes in version 0.0.9pre4 - 2004-10-17
15316 o Bugfixes on 0.0.9pre3:
15317 - If the server doesn't specify an exit policy, use the real default
15318 exit policy, not reject *:*.
15319 - Ignore fascistfirewall when uploading/downloading hidden service
15320 descriptors, since we go through Tor for those; and when using
15321 an HttpProxy, since we assume it can reach them all.
15322 - When looking for an authoritative dirserver, use only the ones
15323 configured at boot. Don't bother looking in the directory.
15324 - The rest of the fix for get_default_conf_file() on older win32.
15325 - Make 'Routerfile' config option obsolete.
15328 - New 'MyFamily nick1,...' config option for a server to
15329 specify other servers that shouldn't be used in the same circuit
15330 with it. Only believed if nick1 also specifies us.
15331 - New 'NodeFamily nick1,nick2,...' config option for a client to
15332 specify nodes that it doesn't want to use in the same circuit.
15333 - New 'Redirectexit pattern address:port' config option for a
15334 server to redirect exit connections, e.g. to a local squid.
15337 Changes in version 0.0.9pre3 - 2004-10-13
15338 o Bugfixes on 0.0.8.1:
15339 - Better torrc example lines for dirbindaddress and orbindaddress.
15340 - Improved bounds checking on parsed ints (e.g. config options and
15341 the ones we find in directories.)
15342 - Better handling of size_t vs int, so we're more robust on 64
15344 - Fix the rest of the bug where a newly started OR would appear
15345 as unverified even after we've added his fingerprint and hupped
15347 - Fix a bug from 0.0.7: when read() failed on a stream, we would
15348 close it without sending back an end. So 'connection refused'
15349 would simply be ignored and the user would get no response.
15351 o Bugfixes on 0.0.9pre2:
15352 - Serving the cached-on-disk directory to people is bad. We now
15353 provide no directory until we've fetched a fresh one.
15354 - Workaround for bug on windows where cached-directories get crlf
15356 - Make get_default_conf_file() work on older windows too.
15357 - If we write a *:* exit policy line in the descriptor, don't write
15358 any more exit policy lines.
15361 - Use only 0.0.9pre1 and later servers for resolve cells.
15362 - Make the dirservers file obsolete.
15363 - Include a dir-signing-key token in directories to tell the
15364 parsing entity which key is being used to sign.
15365 - Remove the built-in bulky default dirservers string.
15366 - New config option "Dirserver %s:%d [fingerprint]", which can be
15367 repeated as many times as needed. If no dirservers specified,
15368 default to moria1,moria2,tor26.
15369 - Make moria2 advertise a dirport of 80, so people behind firewalls
15370 will be able to get a directory.
15371 - Http proxy support
15372 - Dirservers translate requests for http://%s:%d/x to /x
15373 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
15374 be routed through this host.
15375 - Clients ask for /tor/x rather than /x for new enough dirservers.
15376 This way we can one day coexist peacefully with apache.
15377 - Clients specify a "Host: %s%d" http header, to be compatible
15378 with more proxies, and so running squid on an exit node can work.
15381 Changes in version 0.0.8.1 - 2004-10-13
15383 - Fix a seg fault that can be triggered remotely for Tor
15384 clients/servers with an open dirport.
15385 - Fix a rare assert trigger, where routerinfos for entries in
15386 our cpath would expire while we're building the path.
15387 - Fix a bug in OutboundBindAddress so it (hopefully) works.
15388 - Fix a rare seg fault for people running hidden services on
15389 intermittent connections.
15390 - Fix a bug in parsing opt keywords with objects.
15391 - Fix a stale pointer assert bug when a stream detaches and
15393 - Fix a string format vulnerability (probably not exploitable)
15394 in reporting stats locally.
15395 - Fix an assert trigger: sometimes launching circuits can fail
15396 immediately, e.g. because too many circuits have failed recently.
15397 - Fix a compile warning on 64 bit platforms.
15400 Changes in version 0.0.9pre2 - 2004-10-03
15402 - Make fetching a cached directory work for 64-bit platforms too.
15403 - Make zlib.h a required header, not an optional header.
15406 Changes in version 0.0.9pre1 - 2004-10-01
15408 - Stop using separate defaults for no-config-file and
15409 empty-config-file. Now you have to explicitly turn off SocksPort,
15410 if you don't want it open.
15411 - Fix a bug in OutboundBindAddress so it (hopefully) works.
15412 - Improve man page to mention more of the 0.0.8 features.
15413 - Fix a rare seg fault for people running hidden services on
15414 intermittent connections.
15415 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
15417 - Fix more dns related bugs: send back resolve_failed and end cells
15418 more reliably when the resolve fails, rather than closing the
15419 circuit and then trying to send the cell. Also attach dummy resolve
15420 connections to a circuit *before* calling dns_resolve(), to fix
15421 a bug where cached answers would never be sent in RESOLVED cells.
15422 - When we run out of disk space, or other log writing error, don't
15423 crash. Just stop logging to that log and continue.
15424 - We were starting to daemonize before we opened our logs, so if
15425 there were any problems opening logs, we would complain to stderr,
15426 which wouldn't work, and then mysteriously exit.
15427 - Fix a rare bug where sometimes a verified OR would connect to us
15428 before he'd uploaded his descriptor, which would cause us to
15429 assign conn->nickname as though he's unverified. Now we look through
15430 the fingerprint list to see if he's there.
15431 - Fix a rare assert trigger, where routerinfos for entries in
15432 our cpath would expire while we're building the path.
15435 - Clients can ask dirservers for /dir.z to get a compressed version
15436 of the directory. Only works for servers running 0.0.9, of course.
15437 - Make clients cache directories and use them to seed their router
15438 lists at startup. This means clients have a datadir again.
15439 - Configuration infrastructure support for warning on obsolete
15441 - Respond to content-encoding headers by trying to uncompress as
15443 - Reply with a deflated directory when a client asks for "dir.z".
15444 We could use allow-encodings instead, but allow-encodings isn't
15445 specified in HTTP 1.0.
15446 - Raise the max dns workers from 50 to 100.
15447 - Discourage people from setting their dirfetchpostperiod more often
15448 than once per minute.
15449 - Protect dirservers from overzealous descriptor uploading -- wait
15450 10 seconds after directory gets dirty, before regenerating.
15453 Changes in version 0.0.8 - 2004-08-25
15454 o Port it to SunOS 5.9 / Athena
15457 Changes in version 0.0.8rc2 - 2004-08-20
15458 o Make it compile on cygwin again.
15459 o When picking unverified routers, skip those with low uptime and/or
15460 low bandwidth, depending on what properties you care about.
15463 Changes in version 0.0.8rc1 - 2004-08-18
15464 o Changes from 0.0.7.3:
15466 - Fix assert triggers: if the other side returns an address 0.0.0.0,
15467 don't put it into the client dns cache.
15468 - If a begin failed due to exit policy, but we believe the IP address
15469 should have been allowed, switch that router to exitpolicy reject *:*
15470 until we get our next directory.
15472 - Clients choose nodes proportional to advertised bandwidth.
15473 - Avoid using nodes with low uptime as introduction points.
15474 - Handle servers with dynamic IP addresses: don't replace
15475 options->Address with the resolved one at startup, and
15476 detect our address right before we make a routerinfo each time.
15477 - 'FascistFirewall' option to pick dirservers and ORs on specific
15478 ports; plus 'FirewallPorts' config option to tell FascistFirewall
15479 which ports are open. (Defaults to 80,443)
15480 - Be more aggressive about trying to make circuits when the network
15481 has changed (e.g. when you unsuspend your laptop).
15482 - Check for time skew on http headers; report date in response to
15484 - If the entrynode config line has only one node, don't pick it as
15486 - Add strict{entry|exit}nodes config options. If set to 1, then
15487 we refuse to build circuits that don't include the specified entry
15489 - OutboundBindAddress config option, to bind to a specific
15490 IP address for outgoing connect()s.
15491 - End truncated log entries (e.g. directories) with "[truncated]".
15493 o Patches to 0.0.8preX:
15495 - Patches to compile and run on win32 again (maybe)?
15496 - Fix crash when looking for ~/.torrc with no $HOME set.
15497 - Fix a race bug in the unit tests.
15498 - Handle verified/unverified name collisions better when new
15499 routerinfo's arrive in a directory.
15500 - Sometimes routers were getting entered into the stats before
15501 we'd assigned their identity_digest. Oops.
15502 - Only pick and establish intro points after we've gotten a
15505 - AllowUnverifiedNodes config option to let circuits choose no-name
15506 routers in entry,middle,exit,introduction,rendezvous positions.
15507 Allow middle and rendezvous positions by default.
15508 - Add a man page for tor-resolve.
15511 Changes in version 0.0.7.3 - 2004-08-12
15512 o Stop dnsworkers from triggering an assert failure when you
15513 ask them to resolve the host "".
15516 Changes in version 0.0.8pre3 - 2004-08-09
15517 o Changes from 0.0.7.2:
15518 - Allow multiple ORs with same nickname in routerlist -- now when
15519 people give us one identity key for a nickname, then later
15520 another, we don't constantly complain until the first expires.
15521 - Remember used bandwidth (both in and out), and publish 15-minute
15522 snapshots for the past day into our descriptor.
15523 - You can now fetch $DIRURL/running-routers to get just the
15524 running-routers line, not the whole descriptor list. (But
15525 clients don't use this yet.)
15526 - When people mistakenly use Tor as an http proxy, point them
15527 at the tor-doc.html rather than the INSTALL.
15528 - Remove our mostly unused -- and broken -- hex_encode()
15529 function. Use base16_encode() instead. (Thanks to Timo Lindfors
15530 for pointing out this bug.)
15531 - Rotate onion keys every 12 hours, not every 2 hours, so we have
15532 fewer problems with people using the wrong key.
15533 - Change the default exit policy to reject the default edonkey,
15534 kazaa, gnutella ports.
15535 - Add replace_file() to util.[ch] to handle win32's rename().
15537 o Changes from 0.0.8preX:
15538 - Fix two bugs in saving onion keys to disk when rotating, so
15539 hopefully we'll get fewer people using old onion keys.
15540 - Fix an assert error that was making SocksPolicy not work.
15541 - Be willing to expire routers that have an open dirport -- it's
15542 just the authoritative dirservers we want to not forget.
15543 - Reject tor-resolve requests for .onion addresses early, so we
15544 don't build a whole rendezvous circuit and then fail.
15545 - When you're warning a server that he's unverified, don't cry
15546 wolf unpredictably.
15547 - Fix a race condition: don't try to extend onto a connection
15548 that's still handshaking.
15549 - For servers in clique mode, require the conn to be open before
15550 you'll choose it for your path.
15551 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
15552 end relay cell, etc.
15553 - Measure bandwidth capacity over the last 24 hours, not just 12
15554 - Bugfix: authoritative dirservers were making and signing a new
15555 directory for each client, rather than reusing the cached one.
15558 Changes in version 0.0.8pre2 - 2004-08-04
15559 o Changes from 0.0.7.2:
15561 - Check directory signature _before_ you decide whether you're
15562 you're running an obsolete version and should exit.
15563 - Check directory signature _before_ you parse the running-routers
15564 list to decide who's running or verified.
15565 - Bugfixes and features:
15566 - Check return value of fclose while writing to disk, so we don't
15567 end up with broken files when servers run out of disk space.
15568 - Log a warning if the user uses an unsafe socks variant, so people
15569 are more likely to learn about privoxy or socat.
15570 - Dirservers now include RFC1123-style dates in the HTTP headers,
15571 which one day we will use to better detect clock skew.
15573 o Changes from 0.0.8pre1:
15574 - Make it compile without warnings again on win32.
15575 - Log a warning if you're running an unverified server, to let you
15576 know you might want to get it verified.
15577 - Only pick a default nickname if you plan to be a server.
15580 Changes in version 0.0.8pre1 - 2004-07-23
15582 - Made our unit tests compile again on OpenBSD 3.5, and tor
15583 itself compile again on OpenBSD on a sparc64.
15584 - We were neglecting milliseconds when logging on win32, so
15585 everything appeared to happen at the beginning of each second.
15587 o Protocol changes:
15588 - 'Extend' relay cell payloads now include the digest of the
15589 intended next hop's identity key. Now we can verify that we're
15590 extending to the right router, and also extend to routers we
15591 hadn't heard of before.
15594 - Tor nodes can now act as relays (with an advertised ORPort)
15595 without being manually verified by the dirserver operators.
15596 - Uploaded descriptors of unverified routers are now accepted
15597 by the dirservers, and included in the directory.
15598 - Verified routers are listed by nickname in the running-routers
15599 list; unverified routers are listed as "$<fingerprint>".
15600 - We now use hash-of-identity-key in most places rather than
15601 nickname or addr:port, for improved security/flexibility.
15602 - To avoid Sybil attacks, paths still use only verified servers.
15603 But now we have a chance to play around with hybrid approaches.
15604 - Nodes track bandwidth usage to estimate capacity (not used yet).
15605 - ClientOnly option for nodes that never want to become servers.
15606 - Directory caching.
15607 - "AuthoritativeDir 1" option for the official dirservers.
15608 - Now other nodes (clients and servers) will cache the latest
15609 directory they've pulled down.
15610 - They can enable their DirPort to serve it to others.
15611 - Clients will pull down a directory from any node with an open
15612 DirPort, and check the signature/timestamp correctly.
15613 - Authoritative dirservers now fetch directories from other
15614 authdirservers, to stay better synced.
15615 - Running-routers list tells who's down also, along with noting
15616 if they're verified (listed by nickname) or unverified (listed
15618 - Allow dirservers to serve running-router list separately.
15619 This isn't used yet.
15620 - ORs connect-on-demand to other ORs
15621 - If you get an extend cell to an OR you're not connected to,
15622 connect, handshake, and forward the create cell.
15623 - The authoritative dirservers stay connected to everybody,
15624 and everybody stays connected to 0.0.7 servers, but otherwise
15625 clients/servers expire unused connections after 5 minutes.
15626 - When servers get a sigint, they delay 30 seconds (refusing new
15627 connections) then exit. A second sigint causes immediate exit.
15628 - File and name management:
15629 - Look for .torrc if no CONFDIR "torrc" is found.
15630 - If no datadir is defined, then choose, make, and secure ~/.tor
15632 - If torrc not found, exitpolicy reject *:*.
15633 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
15634 - If no nickname is defined, derive default from hostname.
15635 - Rename secret key files, e.g. identity.key -> secret_id_key,
15636 to discourage people from mailing their identity key to tor-ops.
15637 - Refuse to build a circuit before the directory has arrived --
15638 it won't work anyway, since you won't know the right onion keys
15640 - Try other dirservers immediately if the one you try is down. This
15641 should tolerate down dirservers better now.
15642 - Parse tor version numbers so we can do an is-newer-than check
15643 rather than an is-in-the-list check.
15644 - New socks command 'resolve', to let us shim gethostbyname()
15646 - A 'tor_resolve' script to access the socks resolve functionality.
15647 - A new socks-extensions.txt doc file to describe our
15648 interpretation and extensions to the socks protocols.
15649 - Add a ContactInfo option, which gets published in descriptor.
15650 - Publish OR uptime in descriptor (and thus in directory) too.
15651 - Write tor version at the top of each log file
15652 - New docs in the tarball:
15654 - Document that you should proxy your SSL traffic too.
15657 Changes in version 0.0.7.2 - 2004-07-07
15658 o A better fix for the 0.0.0.0 problem, that will hopefully
15659 eliminate the remaining related assertion failures.
15662 Changes in version 0.0.7.1 - 2004-07-04
15663 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
15664 since internally we use 0.0.0.0 to signify "not yet resolved".
15667 Changes in version 0.0.7 - 2004-06-07
15668 o Updated the man page to reflect the new features.
15671 Changes in version 0.0.7rc2 - 2004-06-06
15672 o Changes from 0.0.7rc1:
15673 - Make it build on Win32 again.
15674 o Changes from 0.0.6.2:
15675 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
15679 Changes in version 0.0.7rc1 - 2004-06-02
15681 - On sighup, we were adding another log without removing the first
15682 one. So log messages would get duplicated n times for n sighups.
15683 - Several cases of using a connection after we'd freed it. The
15684 problem was that connections that are pending resolve are in both
15685 the pending_resolve tree, and also the circuit's resolving_streams
15686 list. When you want to remove one, you must remove it from both.
15687 - Fix a double-mark-for-close where an end cell arrived for a
15688 resolving stream, and then the resolve failed.
15689 - Check directory signatures based on name of signer, not on whom
15690 we got the directory from. This will let us cache directories more
15693 - Crank up some of our constants to handle more users.
15696 Changes in version 0.0.7pre1 - 2004-06-02
15697 o Fixes for crashes and other obnoxious bugs:
15698 - Fix an epipe bug: sometimes when directory connections failed
15699 to connect, we would give them a chance to flush before closing
15701 - When we detached from a circuit because of resolvefailed, we
15702 would immediately try the same circuit twice more, and then
15703 give up on the resolve thinking we'd tried three different
15705 - Limit the number of intro circuits we'll attempt to build for a
15706 hidden service per 15-minute period.
15707 - Check recommended-software string *early*, before actually parsing
15708 the directory. Thus we can detect an obsolete version and exit,
15709 even if the new directory format doesn't parse.
15710 o Fixes for security bugs:
15711 - Remember which nodes are dirservers when you startup, and if a
15712 random OR enables his dirport, don't automatically assume he's
15713 a trusted dirserver.
15715 - Directory connections were asking the wrong poll socket to
15716 start writing, and not asking themselves to start writing.
15717 - When we detached from a circuit because we sent a begin but
15718 didn't get a connected, we would use it again the first time;
15719 but after that we would correctly switch to a different one.
15720 - Stop warning when the first onion decrypt attempt fails; they
15721 will sometimes legitimately fail now that we rotate keys.
15722 - Override unaligned-access-ok check when $host_cpu is ia64 or
15723 arm. Apparently they allow it but the kernel whines.
15724 - Dirservers try to reconnect periodically too, in case connections
15726 - Fix some memory leaks in directory servers.
15727 - Allow backslash in Win32 filenames.
15728 - Made Tor build complain-free on FreeBSD, hopefully without
15729 breaking other BSD builds. We'll see.
15731 - Doxygen markup on all functions and global variables.
15732 - Make directory functions update routerlist, not replace it. So
15733 now directory disagreements are not so critical a problem.
15734 - Remove the upper limit on number of descriptors in a dirserver's
15735 directory (not that we were anywhere close).
15736 - Allow multiple logfiles at different severity ranges.
15737 - Allow *BindAddress to specify ":port" rather than setting *Port
15738 separately. Allow multiple instances of each BindAddress config
15739 option, so you can bind to multiple interfaces if you want.
15740 - Allow multiple exit policy lines, which are processed in order.
15741 Now we don't need that huge line with all the commas in it.
15742 - Enable accept/reject policies on SOCKS connections, so you can bind
15743 to 0.0.0.0 but still control who can use your OP.
15746 Changes in version 0.0.6.2 - 2004-05-16
15747 o Our integrity-checking digest was checking only the most recent cell,
15748 not the previous cells like we'd thought.
15749 Thanks to Stefan Mark for finding the flaw!
15752 Changes in version 0.0.6.1 - 2004-05-06
15753 o Fix two bugs in our AES counter-mode implementation (this affected
15754 onion-level stream encryption, but not TLS-level). It turns
15755 out we were doing something much more akin to a 16-character
15756 polyalphabetic cipher. Oops.
15757 Thanks to Stefan Mark for finding the flaw!
15758 o Retire moria3 as a directory server, and add tor26 as a directory
15762 Changes in version 0.0.6 - 2004-05-02
15763 [version bump only]
15766 Changes in version 0.0.6rc4 - 2004-05-01
15767 o Update the built-in dirservers list to use the new directory format
15768 o Fix a rare seg fault: if a node offering a hidden service attempts
15769 to build a circuit to Alice's rendezvous point and fails before it
15770 reaches the last hop, it retries with a different circuit, but
15772 o Handle windows socket errors correctly.
15775 Changes in version 0.0.6rc3 - 2004-04-28
15776 o Don't expire non-general excess circuits (if we had enough
15777 circuits open, we were expiring rendezvous circuits -- even
15778 when they had a stream attached. oops.)
15779 o Fetch randomness from /dev/urandom better (not via fopen/fread)
15780 o Better debugging for tls errors
15781 o Some versions of openssl have an SSL_pending function that erroneously
15782 returns bytes when there is a non-application record pending.
15783 o Set Content-Type on the directory and hidserv descriptor.
15784 o Remove IVs from cipher code, since AES-ctr has none.
15785 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
15786 o We were using an array of length zero in a few places.
15787 o win32's gethostbyname can't resolve an IP to an IP.
15788 o win32's close can't close a socket.
15791 Changes in version 0.0.6rc2 - 2004-04-26
15792 o Fix a bug where we were closing tls connections intermittently.
15793 It turns out openssl keeps its errors around -- so if an error
15794 happens, and you don't ask about it, and then another openssl
15795 operation happens and succeeds, and you ask if there was an error,
15796 it tells you about the first error. Fun fun.
15797 o Fix a bug that's been lurking since 27 may 03 (!)
15798 When passing back a destroy cell, we would use the wrong circ id.
15799 'Mostly harmless', but still worth fixing.
15800 o Since we don't support truncateds much, don't bother sending them;
15801 just close the circ.
15802 o check for <machine/limits.h> so we build on NetBSD again (I hope).
15803 o don't crash if a conn that sent a begin has suddenly lost its circuit
15804 (this was quite rare).
15807 Changes in version 0.0.6rc1 - 2004-04-25
15808 o We now rotate link (tls context) keys and onion keys.
15809 o CREATE cells now include oaep padding, so you can tell
15810 if you decrypted them correctly.
15811 o Add bandwidthburst to server descriptor.
15812 o Directories now say which dirserver signed them.
15813 o Use a tor_assert macro that logs failed assertions too.
15816 Changes in version 0.0.6pre5 - 2004-04-18
15817 o changes from 0.0.6pre4:
15818 - make tor build on broken freebsd 5.2 installs
15819 - fix a failed assert when you try an intro point, get a nack, and try
15820 a second one and it works.
15821 - when alice uses a port that the hidden service doesn't accept,
15822 it now sends back an end cell (denied by exit policy). otherwise
15823 alice would just have to wait to time out.
15824 - fix another rare bug: when we had tried all the intro
15825 points for a hidden service, we fetched the descriptor
15826 again, but we left our introcirc thinking it had already
15827 sent an intro, so it kept waiting for a response...
15828 - bugfix: when you sleep your hidden-service laptop, as soon
15829 as it wakes up it tries to upload a service descriptor, but
15830 socketpair fails for some reason (localhost not up yet?).
15831 now we simply give up on that upload, and we'll try again later.
15832 i'd still like to find the bug though.
15833 - if an intro circ waiting for an ack dies before getting one, then
15835 - we were reusing stale service descriptors and refetching usable
15839 Changes in version 0.0.6pre4 - 2004-04-14
15840 o changes from 0.0.6pre3:
15841 - when bob fails to connect to the rendezvous point, and his
15842 circ didn't fail because of the rendezvous point itself, then
15843 he retries a couple of times
15844 - we expire introduction and rendezvous circs more thoroughly
15845 (sometimes they were hanging around forever)
15846 - we expire unattached rendezvous streams that have been around
15847 too long (they were sticking around forever).
15848 - fix a measly fencepost error that was crashing everybody with
15852 Changes in version 0.0.6pre3 - 2004-04-14
15853 o changes from 0.0.6pre2:
15854 - make hup work again
15855 - fix some memory leaks for dirservers
15856 - allow more skew in rendezvous descriptor timestamps, to help
15857 handle people like blanu who don't know what time it is
15858 - normal circs are 3 hops, but some rend/intro circs are 4, if
15859 the initiator doesn't get to choose the last hop
15860 - send acks for introductions, so alice can know whether to try
15862 - bob publishes intro points more correctly
15863 o changes from 0.0.5:
15864 - fix an assert trigger that's been plaguing us since the days
15865 of 0.0.2prexx (thanks weasel!)
15866 - retry stream correctly when we fail to connect because of
15867 exit-policy-reject (should try another) or can't-resolve-address
15868 (also should try another, because dns on random internet servers
15870 - when we hup a dirserver and we've *removed* a server from the
15871 approved-routers list, now we remove that server from the
15872 in-memory directories too
15875 Changes in version 0.0.6pre2 - 2004-04-08
15876 o We fixed our base32 implementation. Now it works on all architectures.
15879 Changes in version 0.0.6pre1 - 2004-04-08
15881 - Hidden services and rendezvous points are implemented. Go to
15882 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
15883 hidden services. (This only works via a socks4a proxy such as
15884 Privoxy, and currently it's quite slow.)
15887 Changes in version 0.0.5 - 2004-03-30
15888 [version bump only]
15891 Changes in version 0.0.5rc3 - 2004-03-29
15892 o Install torrc as torrc.sample -- we no longer clobber your
15894 o Re-enable recommendedversion checking (we broke it in rc2, oops)
15895 o Add in a 'notice' log level for things the operator should hear
15896 but that aren't warnings
15899 Changes in version 0.0.5rc2 - 2004-03-29
15900 o Hold socks connection open until reply is flushed (if possible)
15901 o Make exit nodes resolve IPs to IPs immediately, rather than asking
15902 the dns farm to do it.
15903 o Fix c99 aliasing warnings in rephist.c
15904 o Don't include server descriptors that are older than 24 hours in the
15906 o Give socks 'reject' replies their whole 15s to attempt to flush,
15907 rather than seeing the 60s timeout and assuming the flush had failed.
15908 o Clean automake droppings from the cvs repository
15911 Changes in version 0.0.5rc1 - 2004-03-28
15912 o Fix mangled-state bug in directory fetching (was causing sigpipes).
15913 o Only build circuits after we've fetched the directory: clients were
15914 using only the directory servers before they'd fetched a directory.
15915 This also means longer startup time; so it goes.
15916 o Fix an assert trigger where an OP would fail to handshake, and we'd
15917 expect it to have a nickname.
15918 o Work around a tsocks bug: do a socks reject when AP connection dies
15919 early, else tsocks goes into an infinite loop.
15922 Changes in version 0.0.4 - 2004-03-26
15923 o When connecting to a dirserver or OR and the network is down,
15927 Changes in version 0.0.3 - 2004-03-26
15928 o Warn and fail if server chose a nickname with illegal characters
15929 o Port to Solaris and Sparc:
15930 - include missing header fcntl.h
15931 - have autoconf find -lsocket -lnsl automatically
15932 - deal with hardware word alignment
15933 - make uname() work (solaris has a different return convention)
15934 - switch from using signal() to sigaction()
15935 o Preliminary work on reputation system:
15936 - Keep statistics on success/fail of connect attempts; they're published
15937 by kill -USR1 currently.
15938 - Add a RunTesting option to try to learn link state by creating test
15939 circuits, even when SocksPort is off.
15940 - Remove unused open circuits when there are too many.
15943 Changes in version 0.0.2 - 2004-03-19
15944 - Include strlcpy and strlcat for safer string ops
15945 - define INADDR_NONE so we compile (but still not run) on solaris
15948 Changes in version 0.0.2pre27 - 2004-03-14
15950 - Allow internal tor networks (we were rejecting internal IPs,
15951 now we allow them if they're set explicitly).
15952 - And fix a few endian issues.
15955 Changes in version 0.0.2pre26 - 2004-03-14
15957 - If a stream times out after 15s without a connected cell, don't
15958 try that circuit again: try a new one.
15959 - Retry streams at most 4 times. Then give up.
15960 - When a dirserver gets a descriptor from an unknown router, it
15961 logs its fingerprint (so the dirserver operator can choose to
15962 accept it even without mail from the server operator).
15963 - Inform unapproved servers when we reject their descriptors.
15964 - Make tor build on Windows again. It works as a client, who knows
15966 - Clearer instructions in the torrc for how to set up a server.
15967 - Be more efficient about reading fd's when our global token bucket
15968 (used for rate limiting) becomes empty.
15970 - Stop asserting that computers always go forward in time. It's
15972 - When we sent a cell (e.g. destroy) and then marked an OR connection
15973 expired, we might close it before finishing a flush if the other
15974 side isn't reading right then.
15975 - Don't allow dirservers to start if they haven't defined
15976 RecommendedVersions
15977 - We were caching transient dns failures. Oops.
15978 - Prevent servers from publishing an internal IP as their address.
15979 - Address a strcat vulnerability in circuit.c
15982 Changes in version 0.0.2pre25 - 2004-03-04
15984 - Put the OR's IP in its router descriptor, not its fqdn. That way
15985 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15988 - If the user typed in an address that didn't resolve, the server
15992 Changes in version 0.0.2pre24 - 2004-03-03
15994 - Fix an assertion failure in dns.c, where we were trying to dequeue
15995 a pending dns resolve even if it wasn't pending
15996 - Fix a spurious socks5 warning about still trying to write after the
15997 connection is finished.
15998 - Hold certain marked_for_close connections open until they're finished
15999 flushing, rather than losing bytes by closing them too early.
16000 - Correctly report the reason for ending a stream
16001 - Remove some duplicate calls to connection_mark_for_close
16002 - Put switch_id and start_daemon earlier in the boot sequence, so it
16003 will actually try to chdir() to options.DataDirectory
16004 - Make 'make test' exit(1) if a test fails; fix some unit tests
16005 - Make tor fail when you use a config option it doesn't know about,
16006 rather than warn and continue.
16007 - Make --version work
16008 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
16011 Changes in version 0.0.2pre23 - 2004-02-29
16013 - Print a statement when the first circ is finished, so the user
16014 knows it's working.
16015 - If a relay cell is unrecognized at the end of the circuit,
16016 send back a destroy. (So attacks to mutate cells are more
16018 - New config option 'excludenodes' to avoid certain nodes for circuits.
16019 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
16020 so you can collect coredumps there.
16022 - Fix a bug in tls flushing where sometimes data got wedged and
16023 didn't flush until more data got sent. Hopefully this bug was
16024 a big factor in the random delays we were seeing.
16025 - Make 'connected' cells include the resolved IP, so the client
16026 dns cache actually gets populated.
16027 - Disallow changing from ORPort=0 to ORPort>0 on hup.
16028 - When we time-out on a stream and detach from the circuit, send an
16029 end cell down it first.
16030 - Only warn about an unknown router (in exitnodes, entrynodes,
16031 excludenodes) after we've fetched a directory.
16034 Changes in version 0.0.2pre22 - 2004-02-26
16036 - Servers publish less revealing uname information in descriptors.
16037 - More memory tracking and assertions, to crash more usefully when
16039 - If the default torrc isn't there, just use some default defaults.
16040 Plus provide an internal dirservers file if they don't have one.
16041 - When the user tries to use Tor as an http proxy, give them an http
16042 501 failure explaining that we're a socks proxy.
16043 - Dump a new router.desc on hup, to help confused people who change
16044 their exit policies and then wonder why router.desc doesn't reflect
16046 - Clean up the generic tor.sh init script that we ship with.
16048 - If the exit stream is pending on the resolve, and a destroy arrives,
16049 then the stream wasn't getting removed from the pending list. I
16050 think this was the one causing recent server crashes.
16051 - Use a more robust poll on OSX 10.3, since their poll is flaky.
16052 - When it couldn't resolve any dirservers, it was useless from then on.
16053 Now it reloads the RouterFile (or default dirservers) if it has no
16055 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
16056 many users don't even *have* a /usr/local/sbin/.
16059 Changes in version 0.0.2pre21 - 2004-02-18
16061 - There's a ChangeLog file that actually reflects the changelog.
16062 - There's a 'torify' wrapper script, with an accompanying
16063 tor-tsocks.conf, that simplifies the process of using tsocks for
16064 tor. It even has a man page.
16065 - The tor binary gets installed to sbin rather than bin now.
16066 - Retry streams where the connected cell hasn't arrived in 15 seconds
16067 - Clean up exit policy handling -- get the default out of the torrc,
16068 so we can update it without forcing each server operator to fix
16070 - Allow imaps and pop3s in default exit policy
16072 - Prevent picking middleman nodes as the last node in the circuit
16075 Changes in version 0.0.2pre20 - 2004-01-30
16077 - We now have a deb package, and it's in debian unstable. Go to
16078 it, apt-getters. :)
16079 - I've split the TotalBandwidth option into BandwidthRate (how many
16080 bytes per second you want to allow, long-term) and
16081 BandwidthBurst (how many bytes you will allow at once before the cap
16082 kicks in). This better token bucket approach lets you, say, set
16083 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
16084 performance while not exceeding your monthly bandwidth quota.
16085 - Push out a tls record's worth of data once you've got it, rather
16086 than waiting until you've read everything waiting to be read. This
16087 may improve performance by pipelining better. We'll see.
16088 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
16089 from failed circuits (if they haven't been connected yet) and attach
16091 - Expire old streams that haven't managed to connect. Some day we'll
16092 have them reattach to new circuits instead.
16095 - Fix several memory leaks that were causing servers to become bloated
16097 - Fix a few very rare assert triggers. A few more remain.
16098 - Setuid to User _before_ complaining about running as root.
16101 Changes in version 0.0.2pre19 - 2004-01-07
16103 - Fix deadlock condition in dns farm. We were telling a child to die by
16104 closing the parent's file descriptor to him. But newer children were
16105 inheriting the open file descriptor from the parent, and since they
16106 weren't closing it, the socket never closed, so the child never read
16107 eof, so he never knew to exit. Similarly, dns workers were holding
16108 open other sockets, leading to all sorts of chaos.
16109 - New cleaner daemon() code for forking and backgrounding.
16110 - If you log to a file, it now prints an entry at the top of the
16111 logfile so you know it's working.
16112 - The onionskin challenge length was 30 bytes longer than necessary.
16113 - Started to patch up the spec so it's not quite so out of date.
16116 Changes in version 0.0.2pre18 - 2004-01-02
16118 - Fix endian issues with the 'integrity' field in the relay header.
16119 - Fix a potential bug where connections in state
16120 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
16123 Changes in version 0.0.2pre17 - 2003-12-30
16125 - Made --debuglogfile (or any second log file, actually) work.
16126 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
16127 adversary could force us into an infinite loop.
16130 - Each onionskin handshake now includes a hash of the computed key,
16131 to prove the server's identity and help perfect forward secrecy.
16132 - Changed cell size from 256 to 512 bytes (working toward compatibility
16134 - Changed cell length to 2 bytes, and moved it to the relay header.
16135 - Implemented end-to-end integrity checking for the payloads of
16137 - Separated streamid from 'recognized' (otherwise circuits will get
16138 messed up when we try to have streams exit from the middle). We
16139 use the integrity-checking to confirm that a cell is addressed to
16141 - Randomize the initial circid and streamid values, so an adversary who
16142 breaks into a node can't learn how many circuits or streams have
16146 Changes in version 0.0.2pre16 - 2003-12-14
16148 - Fixed a bug that made HUP trigger an assert
16149 - Fixed a bug where a circuit that immediately failed wasn't being
16150 counted as a failed circuit in counting retries.
16153 - Now we close the circuit when we get a truncated cell: otherwise we're
16154 open to an anonymity attack where a bad node in the path truncates
16155 the circuit and then we open streams at him.
16156 - Add port ranges to exit policies
16157 - Add a conservative default exit policy
16158 - Warn if you're running tor as root
16159 - on HUP, retry OR connections and close/rebind listeners
16160 - options.EntryNodes: try these nodes first when picking the first node
16161 - options.ExitNodes: if your best choices happen to include any of
16162 your preferred exit nodes, you choose among just those preferred
16164 - options.ExcludedNodes: nodes that are never picked in path building
16167 Changes in version 0.0.2pre15 - 2003-12-03
16168 o Robustness and bugfixes:
16169 - Sometimes clients would cache incorrect DNS resolves, which would
16170 really screw things up.
16171 - An OP that goes offline would slowly leak all its sockets and stop
16173 - A wide variety of bugfixes in exit node selection, exit policy
16174 handling, and processing pending streams when a new circuit is
16176 - Pick nodes for a path only from those the directory says are up
16177 - Choose randomly from all running dirservers, not always the first one
16178 - Increase allowed http header size for directory fetch.
16179 - Stop writing to stderr (if we're daemonized it will be closed).
16180 - Enable -g always, so cores will be more useful to me.
16181 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
16184 - Wrote a man page. It lists commonly used options.
16187 - Change default loglevel to warn.
16188 - Make PidFile default to null rather than littering in your CWD.
16189 - OnionRouter config option is now obsolete. Instead it just checks
16191 - Moved to a single unified torrc file for both clients and servers.
16194 Changes in version 0.0.2pre14 - 2003-11-29
16195 o Robustness and bugfixes:
16196 - Force the admin to make the DataDirectory himself
16197 - to get ownership/permissions right
16198 - so clients no longer make a DataDirectory and then never use it
16199 - fix bug where a client who was offline for 45 minutes would never
16200 pull down a directory again
16201 - fix (or at least hide really well) the dns assert bug that was
16202 causing server crashes
16203 - warnings and improved robustness wrt clockskew for certs
16204 - use the native daemon(3) to daemonize, when available
16205 - exit if bind() fails
16206 - exit if neither socksport nor orport is defined
16207 - include our own tor_timegm (Win32 doesn't have its own)
16208 - bugfix for win32 with lots of connections
16209 - fix minor bias in PRNG
16210 - make dirserver more robust to corrupt cached directory
16213 - Wrote the design document (woo)
16215 o Circuit building and exit policies:
16216 - Circuits no longer try to use nodes that the directory has told them
16218 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
16219 bitcounts (18.0.0.0/8).
16220 - Make AP connections standby for a circuit if no suitable circuit
16221 exists, rather than failing
16222 - Circuits choose exit node based on addr/port, exit policies, and
16223 which AP connections are standing by
16224 - Bump min pathlen from 2 to 3
16225 - Relay end cells have a payload to describe why the stream ended.
16226 - If the stream failed because of exit policy, try again with a new
16228 - Clients have a dns cache to remember resolved addresses.
16229 - Notice more quickly when we have no working circuits
16232 - APPort is now called SocksPort
16233 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
16235 - RecommendedVersions is now a config variable rather than
16236 hardcoded (for dirservers)
16237 - Reloads config on HUP
16238 - Usage info on -h or --help
16239 - If you set User and Group config vars, it'll setu/gid to them.
16242 Changes in version 0.0.2pre13 - 2003-10-19
16243 o General stability:
16244 - SSL_write no longer fails when it returns WANTWRITE and the number
16245 of bytes in the buf has changed by the next SSL_write call.
16246 - Fix segfault fetching directory when network is down
16247 - Fix a variety of minor memory leaks
16248 - Dirservers reload the fingerprints file on HUP, so I don't have
16249 to take down the network when I approve a new router
16250 - Default server config file has explicit Address line to specify fqdn
16253 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
16254 - Make listener connections not ever alloc bufs
16256 o Autoconf improvements:
16257 - don't clobber an external CFLAGS in ./configure
16258 - Make install now works
16259 - create var/lib/tor on make install
16260 - autocreate a tor.sh initscript to help distribs
16261 - autocreate the torrc and sample-server-torrc with correct paths
16263 o Log files and Daemonizing now work:
16264 - If --DebugLogFile is specified, log to it at -l debug
16265 - If --LogFile is specified, use it instead of commandline
16266 - If --RunAsDaemon is set, tor forks and backgrounds on startup