1 Changes in version 0.2.5.3-alpha - 2014-03-22
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 listener.
42 Also, log the message in the log file too. Resolves ticket 11043.
44 o Minor features (other):
45 - Add a new option, PredictedPortsRelevanceTime, to control how long
46 after having received a request to connect to a given port Tor
47 will try to keep circuits ready in anticipation of future requests
48 for that port. Patch from "unixninja92"; implements ticket 9176.
49 - Generate a warning if any ports are listed in the SocksPolicy,
50 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
51 AuthDirBadExit options. (These options only support address
52 ranges.) Fixes part of ticket 11108.
53 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
56 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
57 - Build without warnings under clang 3.4. (We have some macros that
58 define static functions only some of which will get used later in
59 the module. Starting with clang 3.4, these give a warning unless the
60 unused attribute is set on them.) Resolves ticket 10904.
61 - Fix build warnings about missing "a2x" comment when building the
62 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
63 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
65 o Minor bugfixes (client):
66 - Improve the log message when we can't connect to a hidden service
67 because all of the hidden service directory nodes hosting its
68 descriptor are excluded. Improves on our fix for bug 10722, which
69 was a bugfix on 0.2.0.10-alpha.
70 - Raise a control port warning when we fail to connect to all of
71 our bridges. Previously, we didn't inform the controller, and
72 the bootstrap process would stall. Fixes bug 11069; bugfix on
74 - Exit immediately when a process-owning controller exits.
75 Previously, tor relays would wait for a little while after their
76 controller exited, as if they had gotten an INT signal -- but this
77 was problematic, since there was no feedback for the user. To do a
78 clean shutdown, controllers should send an INT signal and give Tor
79 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
80 - Stop attempting to connect to bridges before our pluggable
81 transports are configured (harmless but resulted in some erroneous
82 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
83 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
84 generating incorrect SOCKS5 responses, and confusing client
85 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
87 o Minor bugfixes (relays and bridges):
88 - Avoid crashing on a malformed resolv.conf file when running a
89 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
90 - Non-exit relays no longer launch mock DNS requests to check for
91 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
92 non-exit relays stopped servicing DNS requests. Fixes bug 965;
93 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
94 - Bridges now report complete directory request statistics. Related
95 to bug 5824; bugfix on 0.2.2.1-alpha.
96 - Bridges now never collect statistics that were designed for
97 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
98 - Stop giving annoying warning messages when we decide not to launch
99 a pluggable transport proxy that we don't need (because there are
100 no bridges configured to use it). Resolves ticket 5018; bugfix
102 - Give the correct URL in the warning message when trying to run a
103 relay on an ancient version of Windows. Fixes bug 9393.
105 o Minor bugfixes (backtrace support):
106 - Support automatic backtraces on more platforms by using the
107 "-fasynchronous-unwind-tables" compiler option. This option is
108 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
109 is on by default and table generation is not. This doesn't yet
110 add Windows support; only Linux, OSX, and some BSDs are affected.
111 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
112 - Avoid strange behavior if two threads hit failed assertions at the
113 same time and both try to log backtraces at once. (Previously, if
114 this had happened, both threads would have stored their intermediate
115 results in the same buffer, and generated junk outputs.) Reported by
116 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
117 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
118 0.2.5.2-alpha; patch from Nick Hopper.
120 o Minor bugfixes (unit tests):
121 - Fix a small bug in the unit tests that might have made the tests
122 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
123 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
126 - Remove all remaining code related to version-0 hidden service
127 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
128 the rest of bug 10841.
131 - Document in the manpage that "KBytes" may also be written as
132 "kilobytes" or "KB", that "Kbits" may also be written as
133 "kilobits", and so forth. Closes ticket 9222.
134 - Document that the ClientOnly config option overrides ORPort.
135 Our old explanation made ClientOnly sound as though it did
136 nothing at all. Resolves bug 9059.
137 - Explain that SocksPolicy, DirPolicy, and similar options don't
138 take port arguments. Fixes the other part of ticket 11108.
139 - Fix a comment about the rend_server_descriptor_t.protocols field
140 to more accurately describe its range. Also, make that field
141 unsigned, to more accurately reflect its usage. Fixes bug 9099;
142 bugfix on 0.2.1.5-alpha.
143 - Fix the manpage's description of HiddenServiceAuthorizeClient:
144 the maximum client name length is 16, not 19. Fixes bug 11118;
145 bugfix on 0.2.1.6-alpha.
147 o Code simplifications and refactoring:
148 - Get rid of router->address, since in all cases it was just the
149 string representation of router->addr. Resolves ticket 5528.
151 o Test infrastructure:
152 - Update to the latest version of tinytest.
153 - Improve the tinytest implementation of string operation tests so
154 that comparisons with NULL strings no longer crash the tests; they
155 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
158 Changes in version 0.2.4.21 - 2014-02-28
159 Tor 0.2.4.21 further improves security against potential adversaries who
160 find breaking 1024-bit crypto doable, and backports several stability
161 and robustness patches from the 0.2.5 branch.
163 o Major features (client security):
164 - When we choose a path for a 3-hop circuit, make sure it contains
165 at least one relay that supports the NTor circuit extension
166 handshake. Otherwise, there is a chance that we're building
167 a circuit that's worth attacking by an adversary who finds
168 breaking 1024-bit crypto doable, and that chance changes the game
169 theory. Implements ticket 9777.
172 - Do not treat streams that fail with reason
173 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
174 since it could also indicate an ENETUNREACH connection error. Fixes
175 part of bug 10777; bugfix on 0.2.4.8-alpha.
177 o Code simplification and refactoring:
178 - Remove data structures which were introduced to implement the
179 CellStatistics option: they are now redundant with the new timestamp
180 field in the regular packed_cell_t data structure, which we did
181 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
184 - Always clear OpenSSL bignums before freeing them -- even bignums
185 that don't contain secrets. Resolves ticket 10793. Patch by
187 - Build without warnings under clang 3.4. (We have some macros that
188 define static functions only some of which will get used later in
189 the module. Starting with clang 3.4, these give a warning unless the
190 unused attribute is set on them.) Resolves ticket 10904.
191 - Update geoip and geoip6 files to the February 7 2014 Maxmind
192 GeoLite2 Country database.
195 - Set the listen() backlog limit to the largest actually supported
196 on the system, not to the value in a header file. Fixes bug 9716;
197 bugfix on every released Tor.
198 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
199 exit node as a NOROUTE error, not an INTERNAL error, since they
200 can apparently happen when trying to connect to the wrong sort
201 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
202 - Fix build warnings about missing "a2x" comment when building the
203 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
204 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
205 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
206 not entirely remove it from the connection lists. Fixes bug 9602;
207 bugfix on 0.2.4.4-alpha.
208 - Fix a segmentation fault in our benchmark code when running with
209 Fedora's OpenSSL package, or any other OpenSSL that provides
210 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
211 - Turn "circuit handshake stats since last time" log messages into a
212 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
214 o Documentation fixes:
215 - Document that all but one DirPort entry must have the NoAdvertise
216 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
219 Changes in version 0.2.5.2-alpha - 2014-02-13
220 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
221 like the "poor random number generation" fix and the "building too many
222 circuits" fix. It also further improves security against potential
223 adversaries who find breaking 1024-bit crypto doable, and launches
224 pluggable transports on demand (which gets us closer to integrating
225 pluggable transport support by default -- not to be confused with Tor
226 bundles enabling pluggable transports and bridges by default).
228 o Major features (client security):
229 - When we choose a path for a 3-hop circuit, make sure it contains
230 at least one relay that supports the NTor circuit extension
231 handshake. Otherwise, there is a chance that we're building
232 a circuit that's worth attacking by an adversary who finds
233 breaking 1024-bit crypto doable, and that chance changes the game
234 theory. Implements ticket 9777.
235 - Clients now look at the "usecreatefast" consensus parameter to
236 decide whether to use CREATE_FAST or CREATE cells for the first hop
237 of their circuit. This approach can improve security on connections
238 where Tor's circuit handshake is stronger than the available TLS
239 connection security levels, but the tradeoff is more computational
240 load on guard relays. Implements proposal 221. Resolves ticket 9386.
242 o Major features (bridges):
243 - Don't launch pluggable transport proxies if we don't have any
244 bridges configured that would use them. Now we can list many
245 pluggable transports, and Tor will dynamically start one when it
246 hears a bridge address that needs it. Resolves ticket 5018.
247 - The bridge directory authority now assigns status flags (Stable,
248 Guard, etc) to bridges based on thresholds calculated over all
249 Running bridges. Now bridgedb can finally make use of its features
250 to e.g. include at least one Stable bridge in its answers. Fixes
253 o Major features (other):
254 - Extend ORCONN controller event to include an "ID" parameter,
255 and add four new controller event types CONN_BW, CIRC_BW,
256 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
257 The new events are emitted in private Tor networks only, with the
258 goal of being able to better track performance and load during
259 full-network simulations. Implements proposal 218 and ticket 7359.
260 - On some platforms (currently: recent OSX versions, glibc-based
261 platforms that support the ELF format, and a few other
262 Unix-like operating systems), Tor can now dump stack traces
263 when a crash occurs or an assertion fails. By default, traces
264 are dumped to stderr (if possible) and to any logs that are
265 reporting errors. Implements ticket 9299.
268 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
269 not entirely remove it from the connection lists. Fixes bug 9602;
270 bugfix on 0.2.4.4-alpha.
271 - Do not treat streams that fail with reason
272 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
273 since it could also indicate an ENETUNREACH connection error. Fixes
274 part of bug 10777; bugfix on 0.2.4.8-alpha.
276 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
277 - Do not allow OpenSSL engines to replace the PRNG, even when
278 HardwareAccel is set. The only default builtin PRNG engine uses
279 the Intel RDRAND instruction to replace the entire PRNG, and
280 ignores all attempts to seed it with more entropy. That's
281 cryptographically stupid: the right response to a new alleged
282 entropy source is never to discard all previously used entropy
283 sources. Fixes bug 10402; works around behavior introduced in
284 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
286 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
287 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
288 - Avoid launching spurious extra circuits when a stream is pending.
289 This fixes a bug where any circuit that _wasn't_ unusable for new
290 streams would be treated as if it were, causing extra circuits to
291 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
293 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
294 - No longer stop reading or writing on cpuworker connections when
295 our rate limiting buckets go empty. Now we should handle circuit
296 handshake requests more promptly. Resolves bug 9731.
297 - Stop trying to bootstrap all our directory information from
298 only our first guard. Discovered while fixing bug 9946; bugfix
301 o Minor features (bridges, pluggable transports):
302 - Add threshold cutoffs to the networkstatus document created by
303 the Bridge Authority. Fixes bug 1117.
304 - On Windows, spawn background processes using the CREATE_NO_WINDOW
305 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
306 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
307 Vidalia set this option for us.) Implements ticket 10297.
309 o Minor features (security):
310 - Always clear OpenSSL bignums before freeing them -- even bignums
311 that don't contain secrets. Resolves ticket 10793. Patch by
314 o Minor features (config options and command line):
315 - Add an --allow-missing-torrc commandline option that tells Tor to
316 run even if the configuration file specified by -f is not available.
317 Implements ticket 10060.
318 - Add support for the TPROXY transparent proxying facility on Linux.
319 See documentation for the new TransProxyType option for more
320 details. Implementation by "thomo". Closes ticket 10582.
322 o Minor features (controller):
323 - Add a new "HS_DESC" controller event that reports activities
324 related to hidden service descriptors. Resolves ticket 8510.
325 - New "DROPGUARDS" controller command to forget all current entry
326 guards. Not recommended for ordinary use, since replacing guards
327 too frequently makes several attacks easier. Resolves ticket 9934;
330 o Minor features (build):
331 - Assume that a user using ./configure --host wants to cross-compile,
332 and give an error if we cannot find a properly named
333 tool-chain. Add a --disable-tool-name-check option to proceed
334 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
335 - If we run ./configure and the compiler recognizes -fstack-protector
336 but the linker rejects it, warn the user about a potentially missing
337 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
339 o Minor features (testing):
340 - If Python is installed, "make check" now runs extra tests beyond
341 the unit test scripts.
342 - When bootstrapping a test network, sometimes very few relays get
343 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
344 specify a set of relays which should be voted Guard regardless of
345 their uptime or bandwidth. Addresses ticket 9206.
347 o Minor features (log messages):
348 - When ServerTransportPlugin is set on a bridge, Tor can write more
349 useful statistics about bridge use in its extrainfo descriptors,
350 but only if the Extended ORPort ("ExtORPort") is set too. Add a
351 log message to inform the user in this case. Resolves ticket 9651.
352 - When receiving a new controller connection, log the origin address.
353 Resolves ticket 9698; patch from "sigpipe".
354 - When logging OpenSSL engine status at startup, log the status of
355 more engines. Fixes ticket 10043; patch from Joshua Datko.
356 - Turn "circuit handshake stats since last time" log messages into a
357 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
359 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
360 - Improve the circuit queue out-of-memory handler. Previously, when
361 we ran low on memory, we'd close whichever circuits had the most
362 queued cells. Now, we close those that have the *oldest* queued
363 cells, on the theory that those are most responsible for us
364 running low on memory. Based on analysis from a forthcoming paper
365 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
366 - Generate bootstrapping status update events correctly when fetching
367 microdescriptors. Fixes bug 9927.
368 - Update to the October 2 2013 Maxmind GeoLite Country database.
370 o Minor bugfixes (clients):
371 - When closing a channel that has already been open, do not close
372 pending circuits that were waiting to connect to the same relay.
373 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
376 o Minor bugfixes (relays):
377 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
378 exit node as a NOROUTE error, not an INTERNAL error, since they
379 can apparently happen when trying to connect to the wrong sort
380 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
382 o Minor bugfixes (bridges):
383 - Fix a bug where the first connection works to a bridge that uses a
384 pluggable transport with client-side parameters, but we don't send
385 the client-side parameters on subsequent connections. (We don't
386 use any pluggable transports with client-side parameters yet,
387 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
388 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
390 o Minor bugfixes (node selection):
391 - If ExcludeNodes is set, consider non-excluded hidden service
392 directory servers before excluded ones. Do not consider excluded
393 hidden service directory servers at all if StrictNodes is
394 set. (Previously, we would sometimes decide to connect to those
395 servers, and then realize before we initiated a connection that
396 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
398 - If we set the ExitNodes option but it doesn't include any nodes
399 that have the Exit flag, we would choose not to bootstrap. Now we
400 bootstrap so long as ExitNodes includes nodes which can exit to
401 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
403 o Minor bugfixes (controller and command-line):
404 - If changing a config option via "setconf" fails in a recoverable
405 way, we used to nonetheless write our new control ports to the
406 file described by the "ControlPortWriteToFile" option. Now we only
407 write out that file if we successfully switch to the new config
408 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
409 - When a command-line option such as --version or --help that
410 ordinarily implies --hush appears on the command line along with
411 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
412 only if it appeared later on the command line. Fixes bug 9578;
413 bugfix on 0.2.5.1-alpha.
415 o Minor bugfixes (code correctness):
416 - Previously we used two temporary files when writing descriptors to
417 disk; now we only use one. Fixes bug 1376.
418 - Remove an erroneous (but impossible and thus harmless) pointer
419 comparison that would have allowed compilers to skip a bounds
420 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
421 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
422 - Fix an always-true assertion in pluggable transports code so it
423 actually checks what it was trying to check. Fixes bug 10046;
424 bugfix on 0.2.3.9-alpha. Found by "dcb".
426 o Minor bugfixes (protocol correctness):
427 - When receiving a VERSIONS cell with an odd number of bytes, close
428 the connection immediately since the cell is malformed. Fixes bug
429 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
432 o Minor bugfixes (build):
433 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
434 turned off (that is, without support for v2 link handshakes). Fixes
435 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
436 - Fix compilation warnings and startup issues when running with
437 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
439 - Fix compilation on Solaris 9, which didn't like us having an
440 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
442 o Minor bugfixes (testing):
443 - Fix a segmentation fault in our benchmark code when running with
444 Fedora's OpenSSL package, or any other OpenSSL that provides
445 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
447 o Minor bugfixes (log messages):
448 - Fix a bug where clients using bridges would report themselves
449 as 50% bootstrapped even without a live consensus document.
450 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
451 - Suppress a warning where, if there's only one directory authority
452 in the network, we would complain that votes and signatures cannot
453 be uploaded to other directory authorities. Fixes bug 10842;
454 bugfix on 0.2.2.26-beta.
455 - Report bootstrapping progress correctly when we're downloading
456 microdescriptors. We had updated our "do we have enough microdescs
457 to begin building circuits?" logic most recently in 0.2.4.10-alpha
458 (see bug 5956), but we left the bootstrap status event logic at
459 "how far through getting 1/4 of them are we?" Fixes bug 9958;
460 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
462 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
463 - Avoid a crash bug when starting with a corrupted microdescriptor
464 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
465 - If we fail to dump a previously cached microdescriptor to disk, avoid
466 freeing duplicate data later on. Fixes bug 10423; bugfix on
467 0.2.4.13-alpha. Spotted by "bobnomnom".
469 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
470 - Correctly log long IPv6 exit policies, instead of truncating them
471 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
472 - Our default TLS ecdhe groups were backwards: we meant to be using
473 P224 for relays (for performance win) and P256 for bridges (since
474 it is more common in the wild). Instead we had it backwards. After
475 reconsideration, we decided that the default should be P256 on all
476 hosts, since its security is probably better, and since P224 is
477 reportedly used quite little in the wild. Found by "skruffy" on
478 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
479 - Free directory authority certificate download statuses on exit
480 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
482 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
483 - If the guard we choose first doesn't answer, we would try the
484 second guard, but once we connected to the second guard we would
485 abandon it and retry the first one, slowing down bootstrapping.
486 The fix is to treat all our initially chosen guards as acceptable
487 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
488 - Fix an assertion failure that would occur when disabling the
489 ORPort setting on a running Tor process while accounting was
490 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
491 - When examining the list of network interfaces to find our address,
492 do not consider non-running or disabled network interfaces. Fixes
493 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
494 - Avoid an off-by-one error when checking buffer boundaries when
495 formatting the exit status of a pluggable transport helper.
496 This is probably not an exploitable bug, but better safe than
497 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
500 o Removed code and features:
501 - Clients now reject any directory authority certificates lacking
502 a dir-key-crosscert element. These have been included since
503 0.2.1.9-alpha, so there's no real reason for them to be optional
504 any longer. Completes proposal 157. Resolves ticket 10162.
505 - Remove all code that existed to support the v2 directory system,
506 since there are no longer any v2 directory authorities. Resolves
508 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
509 options, which were used for designating authorities as "Hidden
510 service authorities". There has been no use of hidden service
511 authorities since 0.2.2.1-alpha, when we stopped uploading or
512 downloading v0 hidden service descriptors. Fixes bug 10881; also
513 part of a fix for bug 10841.
515 o Code simplification and refactoring:
516 - Remove some old fallback code designed to keep Tor clients working
517 in a network with only two working relays. Elsewhere in the code we
518 have long since stopped supporting such networks, so there wasn't
519 much point in keeping it around. Addresses ticket 9926.
520 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
521 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
522 - Remove data structures which were introduced to implement the
523 CellStatistics option: they are now redundant with the addition
524 of a timestamp to the regular packed_cell_t data structure, which
525 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
528 o Documentation (man page) fixes:
529 - Update manpage to describe some of the files you can expect to
530 find in Tor's DataDirectory. Addresses ticket 9839.
531 - Document that all but one DirPort entry must have the NoAdvertise
532 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
534 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
535 - Clarify the usage and risks of setting the ContactInfo torrc line
536 for your relay or bridge. Resolves ticket 9854.
537 - Add anchors to the manpage so we can link to the html version of
538 the documentation for specific options. Resolves ticket 9866.
539 - Replace remaining references to DirServer in man page and
540 log entries. Resolves ticket 10124.
543 - Make the "tor-gencert" tool used by directory authority operators
544 create 2048-bit signing keys by default (rather than 1024-bit, since
545 1024-bit is uncomfortably small these days). Addresses ticket 10324.
548 Changes in version 0.2.4.20 - 2013-12-22
549 Tor 0.2.4.20 fixes potentially poor random number generation for users
550 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
551 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
552 and 4) have no state file in their DataDirectory (as would happen on
553 first start). Users who generated relay or hidden service identity
554 keys in such a situation should discard them and generate new ones.
556 This release also fixes a logic error that caused Tor clients to build
557 many more preemptive circuits than they actually need.
560 - Do not allow OpenSSL engines to replace the PRNG, even when
561 HardwareAccel is set. The only default builtin PRNG engine uses
562 the Intel RDRAND instruction to replace the entire PRNG, and
563 ignores all attempts to seed it with more entropy. That's
564 cryptographically stupid: the right response to a new alleged
565 entropy source is never to discard all previously used entropy
566 sources. Fixes bug 10402; works around behavior introduced in
567 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
569 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
570 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
571 - Avoid launching spurious extra circuits when a stream is pending.
572 This fixes a bug where any circuit that _wasn't_ unusable for new
573 streams would be treated as if it were, causing extra circuits to
574 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
577 - Avoid a crash bug when starting with a corrupted microdescriptor
578 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
579 - If we fail to dump a previously cached microdescriptor to disk, avoid
580 freeing duplicate data later on. Fixes bug 10423; bugfix on
581 0.2.4.13-alpha. Spotted by "bobnomnom".
584 Changes in version 0.2.4.19 - 2013-12-11
585 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
586 (1986-2013). Aaron worked on diverse projects including helping to guide
587 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
588 transparency to the U.S government's PACER documents, and contributing
589 design and development for Tor and Tor2Web. Aaron was one of the latest
590 martyrs in our collective fight for civil liberties and human rights,
591 and his death is all the more painful because he was one of us.
593 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
594 a new circuit handshake and link encryption that use ECC to provide
595 better security and efficiency; makes relays better manage circuit
596 creation requests; uses "directory guards" to reduce client enumeration
597 risks; makes bridges collect and report statistics about the pluggable
598 transports they support; cleans up and improves our geoip database;
599 gets much closer to IPv6 support for clients, bridges, and relays; makes
600 directory authorities use measured bandwidths rather than advertised
601 ones when computing flags and thresholds; disables client-side DNS
602 caching to reduce tracking risks; and fixes a big bug in bridge
603 reachability testing. This release introduces two new design
604 abstractions in the code: a new "channel" abstraction between circuits
605 and or_connections to allow for implementing alternate relay-to-relay
606 transports, and a new "circuitmux" abstraction storing the queue of
607 circuits for a channel. The release also includes many stability,
608 security, and privacy fixes.
611 Changes in version 0.2.4.18-rc - 2013-11-16
612 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
613 series. It takes a variety of fixes from the 0.2.5.x branch to improve
614 stability, performance, and better handling of edge cases.
617 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
618 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
619 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
620 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
621 them to solve bug 6033.)
624 - No longer stop reading or writing on cpuworker connections when
625 our rate limiting buckets go empty. Now we should handle circuit
626 handshake requests more promptly. Resolves bug 9731.
627 - If we are unable to save a microdescriptor to the journal, do not
628 drop it from memory and then reattempt downloading it. Fixes bug
629 9645; bugfix on 0.2.2.6-alpha.
630 - Stop trying to bootstrap all our directory information from
631 only our first guard. Discovered while fixing bug 9946; bugfix
633 - The new channel code sometimes lost track of in-progress circuits,
634 causing long-running clients to stop building new circuits. The
635 fix is to always call circuit_n_chan_done(chan, 0) from
636 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
638 o Minor bugfixes (on 0.2.4.x):
639 - Correctly log long IPv6 exit policies, instead of truncating them
640 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
641 - Our default TLS ecdhe groups were backwards: we meant to be using
642 P224 for relays (for performance win) and P256 for bridges (since
643 it is more common in the wild). Instead we had it backwards. After
644 reconsideration, we decided that the default should be P256 on all
645 hosts, since its security is probably better, and since P224 is
646 reportedly used quite little in the wild. Found by "skruffy" on
647 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
648 - Free directory authority certificate download statuses on exit
649 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
651 o Minor bugfixes (on 0.2.3.x and earlier):
652 - If the guard we choose first doesn't answer, we would try the
653 second guard, but once we connected to the second guard we would
654 abandon it and retry the first one, slowing down bootstrapping.
655 The fix is to treat all our initially chosen guards as acceptable
656 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
657 - Fix an assertion failure that would occur when disabling the
658 ORPort setting on a running Tor process while accounting was
659 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
660 - When examining the list of network interfaces to find our address,
661 do not consider non-running or disabled network interfaces. Fixes
662 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
663 - Avoid an off-by-one error when checking buffer boundaries when
664 formatting the exit status of a pluggable transport helper.
665 This is probably not an exploitable bug, but better safe than
666 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
669 o Minor features (protecting client timestamps):
670 - Clients no longer send timestamps in their NETINFO cells. These were
671 not used for anything, and they provided one small way for clients
672 to be distinguished from each other as they moved from network to
673 network or behind NAT. Implements part of proposal 222.
674 - Clients now round timestamps in INTRODUCE cells down to the nearest
675 10 minutes. If a new Support022HiddenServices option is set to 0, or
676 if it's set to "auto" and the feature is disabled in the consensus,
677 the timestamp is sent as 0 instead. Implements part of proposal 222.
678 - Stop sending timestamps in AUTHENTICATE cells. This is not such
679 a big deal from a security point of view, but it achieves no actual
680 good purpose, and isn't needed. Implements part of proposal 222.
681 - Reduce down accuracy of timestamps in hidden service descriptors.
682 Implements part of proposal 222.
684 o Minor features (other):
685 - Improve the circuit queue out-of-memory handler. Previously, when
686 we ran low on memory, we'd close whichever circuits had the most
687 queued cells. Now, we close those that have the *oldest* queued
688 cells, on the theory that those are most responsible for us
689 running low on memory. Based on analysis from a forthcoming paper
690 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
691 - Generate bootstrapping status update events correctly when fetching
692 microdescriptors. Fixes bug 9927.
693 - Update to the October 2 2013 Maxmind GeoLite Country database.
695 o Documentation fixes:
696 - Clarify the usage and risks of setting the ContactInfo torrc line
697 for your relay or bridge. Resolves ticket 9854.
698 - Add anchors to the manpage so we can link to the html version of
699 the documentation for specific options. Resolves ticket 9866.
700 - Replace remaining references to DirServer in man page and
701 log entries. Resolves ticket 10124.
704 Changes in version 0.2.5.1-alpha - 2013-10-02
705 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
706 on Linux, allows bridges that offer pluggable transports to report usage
707 statistics, fixes many issues to make testing easier, and provides
708 a pile of minor features and bugfixes that have been waiting for a
709 release of the new branch.
711 This is the first alpha release in a new series, so expect there to
712 be bugs. Users who would rather test out a more stable branch should
713 stay with 0.2.4.x for now.
715 o Major features (security):
716 - Use the seccomp2 syscall filtering facility on Linux to limit
717 which system calls Tor can invoke. This is an experimental,
718 Linux-only feature to provide defense-in-depth against unknown
719 attacks. To try turning it on, set "Sandbox 1" in your torrc
720 file. Please be ready to report bugs. We hope to add support
721 for better sandboxing in the future, including more fine-grained
722 filters, better division of responsibility, and support for more
723 platforms. This work has been done by Cristian-Matei Toader for
724 Google Summer of Code.
725 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
726 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
727 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
728 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
729 them to solve bug 6033.)
731 o Major features (other):
732 - Add support for passing arguments to managed pluggable transport
733 proxies. Implements ticket 3594.
734 - Bridges now track GeoIP information and the number of their users
735 even when pluggable transports are in use, and report usage
736 statistics in their extra-info descriptors. Resolves tickets 4773
738 - Make testing Tor networks bootstrap better: lower directory fetch
739 retry schedules and maximum interval without directory requests,
740 and raise maximum download tries. Implements ticket 6752.
741 - Add make target 'test-network' to run tests on a Chutney network.
742 Implements ticket 8530.
743 - The ntor handshake is now on-by-default, no matter what the
744 directory authorities recommend. Implements ticket 8561.
747 - Instead of writing destroy cells directly to outgoing connection
748 buffers, queue them and intersperse them with other outgoing cells.
749 This can prevent a set of resource starvation conditions where too
750 many pending destroy cells prevent data cells from actually getting
751 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
752 bugfix on 0.2.0.1-alpha.
753 - If we are unable to save a microdescriptor to the journal, do not
754 drop it from memory and then reattempt downloading it. Fixes bug
755 9645; bugfix on 0.2.2.6-alpha.
756 - The new channel code sometimes lost track of in-progress circuits,
757 causing long-running clients to stop building new circuits. The
758 fix is to always call circuit_n_chan_done(chan, 0) from
759 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
762 - Tor now builds each source file in two modes: a mode that avoids
763 exposing identifiers needlessly, and another mode that exposes
764 more identifiers for testing. This lets the compiler do better at
765 optimizing the production code, while enabling us to take more
766 radical measures to let the unit tests test things.
767 - The production builds no longer include functions used only in
768 the unit tests; all functions exposed from a module only for
769 unit-testing are now static in production builds.
770 - Add an --enable-coverage configuration option to make the unit
771 tests (and a new src/or/tor-cov target) to build with gcov test
775 - We now have rudimentary function mocking support that our unit
776 tests can use to test functions in isolation. Function mocking
777 lets the tests temporarily replace a function's dependencies with
778 stub functions, so that the tests can check the function without
779 invoking the other functions it calls.
780 - Add more unit tests for the <circid,channel>->circuit map, and
781 the destroy-cell-tracking code to fix bug 7912.
782 - Unit tests for failing cases of the TAP onion handshake.
783 - More unit tests for address-manipulation functions.
785 o Minor features (protecting client timestamps):
786 - Clients no longer send timestamps in their NETINFO cells. These were
787 not used for anything, and they provided one small way for clients
788 to be distinguished from each other as they moved from network to
789 network or behind NAT. Implements part of proposal 222.
790 - Clients now round timestamps in INTRODUCE cells down to the nearest
791 10 minutes. If a new Support022HiddenServices option is set to 0, or
792 if it's set to "auto" and the feature is disabled in the consensus,
793 the timestamp is sent as 0 instead. Implements part of proposal 222.
794 - Stop sending timestamps in AUTHENTICATE cells. This is not such
795 a big deal from a security point of view, but it achieves no actual
796 good purpose, and isn't needed. Implements part of proposal 222.
797 - Reduce down accuracy of timestamps in hidden service descriptors.
798 Implements part of proposal 222.
800 o Minor features (config options):
801 - Config (torrc) lines now handle fingerprints which are missing
802 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
803 - Support a --dump-config option to print some or all of the
804 configured options. Mainly useful for debugging the command-line
805 option parsing code. Helps resolve ticket 4647.
806 - Raise awareness of safer logging: notify user of potentially
807 unsafe config options, like logging more verbosely than severity
808 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
809 - Add a new configuration option TestingV3AuthVotingStartOffset
810 that bootstraps a network faster by changing the timing for
811 consensus votes. Addresses ticket 8532.
812 - Add a new torrc option "ServerTransportOptions" that allows
813 bridge operators to pass configuration parameters to their
814 pluggable transports. Resolves ticket 8929.
815 - The config (torrc) file now accepts bandwidth and space limits in
816 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
817 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
820 o Minor features (build):
821 - Add support for `--library-versions` flag. Implements ticket 6384.
822 - Return the "unexpected sendme" warnings to a warn severity, but make
823 them rate limited, to help diagnose ticket 8093.
824 - Detect a missing asciidoc, and warn the user about it, during
825 configure rather than at build time. Fixes issue 6506. Patch from
828 o Minor features (other):
829 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
830 sockets in a single system call. Implements ticket 5129.
831 - Log current accounting state (bytes sent and received + remaining
832 time for the current accounting period) in the relay's heartbeat
833 message. Implements ticket 5526; patch from Peter Retzlaff.
834 - Implement the TRANSPORT_LAUNCHED control port event that
835 notifies controllers about new launched pluggable
836 transports. Resolves ticket 5609.
837 - If we're using the pure-C 32-bit curve25519_donna implementation
838 of curve25519, build it with the -fomit-frame-pointer option to
839 make it go faster on register-starved hosts. This improves our
840 handshake performance by about 6% on i386 hosts without nacl.
842 - Update to the September 4 2013 Maxmind GeoLite Country database.
845 - Set the listen() backlog limit to the largest actually supported
846 on the system, not to the value in a header file. Fixes bug 9716;
847 bugfix on every released Tor.
848 - No longer accept malformed http headers when parsing urls from
849 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
851 - In munge_extrainfo_into_routerinfo(), check the return value of
852 memchr(). This would have been a serious issue if we ever passed
853 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
855 - On the chance that somebody manages to build Tor on a
856 platform where time_t is unsigned, correct the way that
857 microdesc_add_to_cache() handles negative time arguments.
858 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
859 - Reject relative control socket paths and emit a warning. Previously,
860 single-component control socket paths would be rejected, but Tor
861 would not log why it could not validate the config. Fixes bug 9258;
862 bugfix on 0.2.3.16-alpha.
864 o Minor bugfixes (command line):
865 - Use a single command-line parser for parsing torrc options on the
866 command line and for finding special command-line options to avoid
867 inconsistent behavior for torrc option arguments that have the same
868 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
870 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
871 9573; bugfix on 0.0.9pre5.
873 o Minor fixes (build, auxiliary programs):
874 - Stop preprocessing the "torify" script with autoconf, since
875 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
877 - The tor-fw-helper program now follows the standard convention and
878 exits with status code "0" on success. Fixes bug 9030; bugfix on
879 0.2.3.1-alpha. Patch by Arlo Breault.
880 - Corrected ./configure advice for what openssl dev package you should
881 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
883 o Minor code improvements:
884 - Remove constants and tests for PKCS1 padding; it's insecure and
885 shouldn't be used for anything new. Fixes bug 8792; patch
887 - Remove instances of strcpy() from the unit tests. They weren't
888 hurting anything, since they were only in the unit tests, but it's
889 embarassing to have strcpy() in the code at all, and some analysis
890 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
891 0.2.3.8-alpha. Patch from Arlo Breault.
894 - Remove migration code from when we renamed the "cached-routers"
895 file to "cached-descriptors" back in 0.2.0.8-alpha. This
896 incidentally resolves ticket 6502 by cleaning up the related code
897 a bit. Patch from Akshay Hebbar.
899 o Code simplification and refactoring:
900 - Extract the common duplicated code for creating a subdirectory
901 of the data directory and writing to a file in it. Fixes ticket
902 4282; patch from Peter Retzlaff.
903 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
904 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
905 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
906 - Add a set of accessor functions for the circuit timeout data
907 structure. Fixes ticket 6153; patch from "piet".
908 - Clean up exit paths from connection_listener_new(). Closes ticket
909 8789. Patch from Arlo Breault.
910 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
911 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
912 - Use a doubly-linked list to implement the global circuit list.
913 Resolves ticket 9108. Patch from Marek Majkowski.
914 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
917 Changes in version 0.2.4.17-rc - 2013-09-05
918 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
919 series. It adds an emergency step to help us tolerate the massive
920 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
921 circuit-level handshakes now effectively jump the queue compared to
922 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
923 big bug hindering bridge reachability tests.
926 - Relays now process the new "NTor" circuit-level handshake requests
927 with higher priority than the old "TAP" circuit-level handshake
928 requests. We still process some TAP requests to not totally starve
929 0.2.3 clients when NTor becomes popular. A new consensus parameter
930 "NumNTorsPerTAP" lets us tune the balance later if we need to.
931 Implements ticket 9574.
934 - If the circuit build timeout logic is disabled (via the consensus,
935 or because we are an authority), then don't build testing circuits.
936 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
937 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
938 previously they did not, which prevented them from receiving
939 successful connections from relays for self-test or bandwidth
940 testing. Also, when a relay is extending a circuit to a bridge,
941 it needs to send a NETINFO cell, even when the bridge hasn't sent
942 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
943 - If the time to download the next old-style networkstatus is in
944 the future, do not decline to consider whether to download the
945 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
949 - Avoid double-closing the listener socket in our socketpair()
950 replacement (used on Windows) in the case where the addresses on
951 our opened sockets don't match what we expected. Fixes bug 9400;
952 bugfix on 0.0.2pre7. Found by Coverity.
954 o Minor fixes (config options):
955 - Avoid overflows when the user sets MaxCircuitDirtiness to a
956 ridiculously high value, by imposing a (ridiculously high) 30-day
957 maximum on MaxCircuitDirtiness.
958 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
959 message is logged at notice, not at info.
960 - Warn and fail if a server is configured not to advertise any
961 ORPorts at all. (We need *something* to put in our descriptor,
962 or we just won't work.)
965 - Track how many "TAP" and "NTor" circuit handshake requests we get,
966 and how many we complete, and log it every hour to help relay
967 operators follow trends in network load. Addresses ticket 9658.
968 - Update to the August 7 2013 Maxmind GeoLite Country database.
971 Changes in version 0.2.4.16-rc - 2013-08-10
972 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
973 series. It fixes several crash bugs in the 0.2.4 branch.
976 - Fix a bug in the voting algorithm that could yield incorrect results
977 when a non-naming authority declared too many flags. Fixes bug 9200;
978 bugfix on 0.2.0.3-alpha.
979 - Fix an uninitialized read that could in some cases lead to a remote
980 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
981 Anybody running a hidden service on the experimental 0.2.4.x
982 branch should upgrade. (This is, so far as we know, unrelated to
984 - Avoid an assertion failure when processing DNS replies without the
985 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
986 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
987 0.2.4.15-rc. Found by stem integration tests.
990 - Fix an invalid memory read that occured when a pluggable
991 transport proxy failed its configuration protocol.
992 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
993 - When evaluating whether to use a connection that we haven't
994 decided is canonical using a recent link protocol version,
995 decide that it's canonical only if it used address _does_
996 match the desired address. Fixes bug 9309; bugfix on
997 0.2.4.4-alpha. Reported by skruffy.
998 - Make the default behavior of NumDirectoryGuards be to track
999 NumEntryGuards. Now a user who changes only NumEntryGuards will get
1000 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
1001 - Fix a spurious compilation warning with some older versions of
1002 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
1005 - Update to the July 3 2013 Maxmind GeoLite Country database.
1008 Changes in version 0.2.4.15-rc - 2013-07-01
1009 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
1010 series. It fixes a few smaller bugs, but generally appears stable.
1011 Please test it and let us know whether it is!
1014 - When receiving a new configuration file via the control port's
1015 LOADCONF command, do not treat the defaults file as absent.
1016 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
1019 - Issue a warning when running with the bufferevents backend enabled.
1020 It's still not stable, and people should know that they're likely
1021 to hit unexpected problems. Closes ticket 9147.
1024 Changes in version 0.2.4.14-alpha - 2013-06-18
1025 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
1026 present in 0.2.4.13-alpha.
1029 - When we have too much memory queued in circuits (according to a new
1030 MaxMemInCellQueues option), close the circuits consuming the most
1031 memory. This prevents us from running out of memory as a relay if
1032 circuits fill up faster than they can be drained. Fixes bug 9063;
1033 bugfix on the 54th commit of Tor. This bug is a further fix beyond
1034 bug 6252, whose fix was merged into 0.2.3.21-rc.
1036 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
1037 where we tried to solve this issue simply by imposing an upper limit
1038 on the number of queued cells for a single circuit. That approach
1039 proved to be problematic, since there are ways to provoke clients to
1040 send a number of cells in excess of any such reasonable limit. Fixes
1041 bug 9072; bugfix on 0.2.4.13-alpha.
1043 - Limit hidden service descriptors to at most ten introduction
1044 points, to slow one kind of guard enumeration. Fixes bug 9002;
1045 bugfix on 0.1.1.11-alpha.
1048 Changes in version 0.2.4.13-alpha - 2013-06-14
1049 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
1050 vulnerabilities, makes socks5 username/password circuit isolation
1051 actually actually work (this time for sure!), and cleans up a bunch
1052 of other issues in preparation for a release candidate.
1054 o Major bugfixes (robustness):
1055 - Close any circuit that has too many cells queued on it. Fixes
1056 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
1057 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
1058 - Prevent the get_freelists() function from running off the end of
1059 the list of freelists if it somehow gets an unrecognized
1060 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
1062 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
1063 when an exit connection with optimistic data succeeds immediately
1064 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
1066 - Fix a directory authority crash bug when building a consensus
1067 using an older consensus as its basis. Fixes bug 8833. Bugfix
1071 - Avoid a memory leak where we would leak a consensus body when we
1072 find that a consensus which we couldn't previously verify due to
1073 missing certificates is now verifiable. Fixes bug 8719; bugfix
1075 - We used to always request authority certificates by identity digest,
1076 meaning we'd get the newest one even when we wanted one with a
1077 different signing key. Then we would complain about being given
1078 a certificate we already had, and never get the one we really
1079 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
1080 resource to request the one we want. Fixes bug 5595; bugfix on
1082 - Follow the socks5 protocol when offering username/password
1083 authentication. The fix for bug 8117 exposed this bug, and it
1084 turns out real-world applications like Pidgin do care. Bugfix on
1085 0.2.3.2-alpha; fixes bug 8879.
1086 - Prevent failures on Windows Vista and later when rebuilding the
1087 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
1088 bugfix on 0.2.4.12-alpha.
1091 - Fix an impossible buffer overrun in the AES unit tests. Fixes
1092 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
1093 - If for some reason we fail to write a microdescriptor while
1094 rebuilding the cache, do not let the annotations from that
1095 microdescriptor linger in the cache file, and do not let the
1096 microdescriptor stay recorded as present in its old location.
1097 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
1098 - Fix a memory leak that would occur whenever a configuration
1099 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
1100 - Paste the description for PathBias parameters from the man
1101 page into or.h, so the code documents them too. Fixes bug 7982;
1102 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
1103 - Relays now treat a changed IPv6 ORPort as sufficient reason to
1104 publish an updated descriptor. Fixes bug 6026; bugfix on
1106 - When launching a resolve request on behalf of an AF_UNIX control
1107 socket, omit the address field of the new entry connection, used in
1108 subsequent controller events, rather than letting tor_dup_addr()
1109 set it to "<unknown address type>". Fixes bug 8639; bugfix on
1112 o Minor bugfixes (log messages):
1113 - Fix a scaling issue in the path bias accounting code that
1114 resulted in "Bug:" log messages from either
1115 pathbias_scale_close_rates() or pathbias_count_build_success().
1116 This represents a bugfix on a previous bugfix: the original fix
1117 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
1119 - Give a less useless error message when the user asks for an IPv4
1120 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
1124 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
1125 to tolerate bug 8093 for now.
1126 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
1127 in directory authority votes to describe whether they have enough
1128 measured bandwidths to ignore advertised (relay descriptor)
1129 bandwidth claims. Resolves ticket 8711.
1130 - Update to the June 5 2013 Maxmind GeoLite Country database.
1132 o Removed documentation:
1133 - Remove some of the older contents of doc/ as obsolete; move others
1134 to torspec.git. Fixes bug 8965.
1136 o Code simplification and refactoring:
1137 - Avoid using character buffers when constructing most directory
1138 objects: this approach was unwieldy and error-prone. Instead,
1139 build smartlists of strings, and concatenate them when done.
1142 Changes in version 0.2.4.12-alpha - 2013-04-18
1143 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
1144 process for lengthening the guard rotation period, makes directory
1145 authority opinions in the consensus a bit less gameable, makes socks5
1146 username/password circuit isolation actually work, and fixes a wide
1147 variety of other issues.
1150 - Raise the default time that a client keeps an entry guard from
1151 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
1152 2012 paper. (We would make it even longer, but we need better client
1153 load balancing first.) Also, make the guard lifetime controllable
1154 via a new GuardLifetime torrc option and a GuardLifetime consensus
1155 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
1156 - Directory authorities now prefer using measured bandwidths to
1157 advertised ones when computing flags and thresholds. Resolves
1159 - Directory authorities that have more than a threshold number
1160 of relays with measured bandwidths now treat relays with unmeasured
1161 bandwidths as having bandwidth 0. Resolves ticket 8435.
1163 o Major bugfixes (assert / resource use):
1164 - Avoid a bug where our response to TLS renegotiation under certain
1165 network conditions could lead to a busy-loop, with 100% CPU
1166 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
1167 - Avoid an assertion when we discover that we'd like to write a cell
1168 onto a closing connection: just discard the cell. Fixes another
1169 case of bug 7350; bugfix on 0.2.4.4-alpha.
1171 o Major bugfixes (client-side privacy):
1172 - When we mark a circuit as unusable for new circuits, have it
1173 continue to be unusable for new circuits even if MaxCircuitDirtiness
1174 is increased too much at the wrong time, or the system clock jumps
1175 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
1176 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
1177 which have resolved to internal addresses") is set, apply that
1178 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
1179 - When an exit relay rejects a stream with reason "exit policy", but
1180 we only know an exit policy summary (e.g. from the microdesc
1181 consensus) for it, do not mark the relay as useless for all exiting.
1182 Instead, mark just the circuit as unsuitable for that particular
1183 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
1184 - Allow applications to get proper stream isolation with
1185 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
1186 username/password authentication also offer "no authentication". Tor
1187 had previously preferred "no authentication", so the applications
1188 never actually sent Tor their auth details. Now Tor selects
1189 username/password authentication if it's offered. You can disable
1190 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
1191 bug 8117; bugfix on 0.2.3.3-alpha.
1193 o Major bugfixes (other):
1194 - When unable to find any working directory nodes to use as a
1195 directory guard, give up rather than adding the same non-working
1196 nodes to the directory guard list over and over. Fixes bug 8231;
1197 bugfix on 0.2.4.8-alpha.
1200 - Reject as invalid most directory objects containing a NUL.
1201 Belt-and-suspender fix for bug 8037.
1202 - In our testsuite, create temporary directories with a bit more
1203 entropy in their name to make name collisions less likely. Fixes
1205 - Add CACHED keyword to ADDRMAP events in the control protocol
1206 to indicate whether a DNS result will be cached or not. Resolves
1208 - Update to the April 3 2013 Maxmind GeoLite Country database.
1210 o Minor features (build):
1211 - Detect and reject attempts to build Tor with threading support
1212 when OpenSSL has been compiled without threading support.
1214 - Clarify that when autoconf is checking for nacl, it is checking
1215 specifically for nacl with a fast curve25519 implementation.
1217 - Warn if building on a platform with an unsigned time_t: there
1218 are too many places where Tor currently assumes that time_t can
1219 hold negative values. We'd like to fix them all, but probably
1222 o Minor bugfixes (build):
1223 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
1224 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
1225 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
1226 - Add the old src/or/micro-revision.i filename to CLEANFILES.
1227 On the off chance that somebody has one, it will go away as soon
1228 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
1229 - Build Tor correctly on 32-bit platforms where the compiler can build
1230 but not run code using the "uint128_t" construction. Fixes bug 8587;
1231 bugfix on 0.2.4.8-alpha.
1232 - Fix compilation warning with some versions of clang that would
1233 prefer the -Wswitch-enum compiler flag to warn about switch
1234 statements with missing enum values, even if those switch
1235 statements have a "default:" statement. Fixes bug 8598; bugfix
1238 o Minor bugfixes (protocol):
1239 - Fix the handling of a TRUNCATE cell when it arrives while the
1240 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
1241 - Fix a misframing issue when reading the version numbers in a
1242 VERSIONS cell. Previously we would recognize [00 01 00 02] as
1243 'version 1, version 2, and version 0x100', when it should have
1244 only included versions 1 and 2. Fixes bug 8059; bugfix on
1245 0.2.0.10-alpha. Reported pseudonymously.
1246 - Make the format and order of STREAM events for DNS lookups
1247 consistent among the various ways to launch DNS lookups. Fixes
1248 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
1249 - Correct our check for which versions of Tor support the EXTEND2
1250 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
1251 later, when support was really added in version 0.2.4.8-alpha.
1252 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
1254 o Minor bugfixes (other):
1255 - Correctly store microdescriptors and extrainfo descriptors with
1256 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
1257 Bug reported by "cypherpunks".
1258 - Increase the width of the field used to remember a connection's
1259 link protocol version to two bytes. Harmless for now, since the
1260 only currently recognized versions are one byte long. Reported
1261 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
1262 - If the state file's path bias counts are invalid (presumably from a
1263 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
1264 additional checks and log messages to the scaling of Path Bias
1265 counts, in case there still are remaining issues with scaling.
1266 Should help resolve bug 8235.
1267 - Eliminate several instances where we use "Nickname=ID" to refer to
1268 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
1269 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
1270 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
1272 o Minor bugfixes (syscalls):
1273 - Always check the return values of functions fcntl() and
1274 setsockopt(). We don't believe these are ever actually failing in
1275 practice, but better safe than sorry. Also, checking these return
1276 values should please analysis tools like Coverity. Patch from
1277 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
1278 - Use direct writes rather than stdio when building microdescriptor
1279 caches, in an attempt to mitigate bug 8031, or at least make it
1282 o Minor bugfixes (config):
1283 - When rejecting a configuration because we were unable to parse a
1284 quoted string, log an actual error message. Fixes bug 7950; bugfix
1286 - Behave correctly when the user disables LearnCircuitBuildTimeout
1287 but doesn't tell us what they would like the timeout to be. Fixes
1288 bug 6304; bugfix on 0.2.2.14-alpha.
1289 - When autodetecting the number of CPUs, use the number of available
1290 CPUs in preference to the number of configured CPUs. Inform the
1291 user if this reduces the number of available CPUs. Fixes bug 8002;
1292 bugfix on 0.2.3.1-alpha.
1293 - Make it an error when you set EntryNodes but disable UseGuardNodes,
1294 since it will (surprisingly to some users) ignore EntryNodes. Fixes
1295 bug 8180; bugfix on 0.2.3.11-alpha.
1296 - Allow TestingTorNetworks to override the 4096-byte minimum for
1297 the Fast threshold. Otherwise they can't bootstrap until they've
1298 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
1299 - Fix some logic errors when the user manually overrides the
1300 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
1303 o Minor bugfixes (log messages to help diagnose bugs):
1304 - If we fail to free a microdescriptor because of bug 7164, log
1305 the filename and line number from which we tried to free it.
1306 - Add another diagnostic to the heartbeat message: track and log
1307 overhead that TLS is adding to the data we write. If this is
1308 high, we are sending too little data to SSL_write at a time.
1309 Diagnostic for bug 7707.
1310 - Add more detail to a log message about relaxed timeouts, to help
1312 - Warn more aggressively when flushing microdescriptors to a
1313 microdescriptor cache fails, in an attempt to mitigate bug 8031,
1314 or at least make it more diagnosable.
1315 - Improve debugging output to help track down bug 8185 ("Bug:
1316 outgoing relay cell has n_chan==NULL. Dropping.")
1317 - Log the purpose of a path-bias testing circuit correctly.
1318 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
1320 o Minor bugfixes (0.2.4.x log messages that were too noisy):
1321 - Don't attempt to relax the timeout of already opened 1-hop circuits.
1322 They might never timeout. This should eliminate some/all cases of
1323 the relaxed timeout log message.
1324 - Use circuit creation time for network liveness evaluation. This
1325 should eliminate warning log messages about liveness caused
1326 by changes in timeout evaluation. Fixes bug 6572; bugfix on
1328 - Reduce a path bias length check from notice to info. The message
1329 is triggered when creating controller circuits. Fixes bug 8196;
1330 bugfix on 0.2.4.8-alpha.
1331 - Fix a path state issue that triggered a notice during relay startup.
1332 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
1333 - Reduce occurrences of warns about circuit purpose in
1334 connection_ap_expire_building(). Fixes bug 8477; bugfix on
1337 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
1338 - If we encounter a write failure on a SOCKS connection before we
1339 finish our SOCKS handshake, don't warn that we closed the
1340 connection before we could send a SOCKS reply. Fixes bug 8427;
1341 bugfix on 0.1.0.1-rc.
1342 - Correctly recognize that [::1] is a loopback address. Fixes
1343 bug 8377; bugfix on 0.2.1.3-alpha.
1344 - Fix a directory authority warn caused when we have a large amount
1345 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
1346 - Don't log inappropriate heartbeat messages when hibernating: a
1347 hibernating node is _expected_ to drop out of the consensus,
1348 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
1349 bugfix on 0.2.3.1-alpha.
1350 - Don't complain about bootstrapping problems while hibernating.
1351 These complaints reflect a general code problem, but not one
1352 with any problematic effects (no connections are actually
1353 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
1355 o Documentation fixes:
1356 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
1357 names match. Fixes bug 7768.
1358 - Make the torify manpage no longer refer to tsocks; torify hasn't
1359 supported tsocks since 0.2.3.14-alpha.
1360 - Make the tor manpage no longer reference tsocks.
1361 - Fix the GeoIPExcludeUnknown documentation to refer to
1362 ExcludeExitNodes rather than the currently nonexistent
1363 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
1366 - The tor-tsocks.conf is no longer distributed or installed. We
1367 recommend that tsocks users use torsocks instead. Resolves
1371 Changes in version 0.2.4.11-alpha - 2013-03-11
1372 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
1373 more robust, makes hidden service authentication work again, and
1374 resolves a DPI fingerprint for Tor's SSL transport.
1376 o Major features (directory authorities):
1377 - Directory authorities now support a new consensus method (17)
1378 where they cap the published bandwidth of servers for which
1379 insufficient bandwidth measurements exist. Fixes part of bug 2286.
1380 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
1381 serve any v2 directory information. Now we can test disabling the
1382 old deprecated v2 directory format, and see whether doing so has
1383 any effect on network load. Begins to fix bug 6783.
1384 - Directory authorities now include inside each vote a statement of
1385 the performance thresholds they used when assigning flags.
1386 Implements ticket 8151.
1388 o Major bugfixes (directory authorities):
1389 - Stop marking every relay as having been down for one hour every
1390 time we restart a directory authority. These artificial downtimes
1391 were messing with our Stable and Guard flag calculations. Fixes
1392 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
1394 o Major bugfixes (hidden services):
1395 - Allow hidden service authentication to succeed again. When we
1396 refactored the hidden service introduction code back
1397 in 0.2.4.1-alpha, we didn't update the code that checks
1398 whether authentication information is present, causing all
1399 authentication checks to return "false". Fix for bug 8207; bugfix
1400 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
1402 o Minor features (relays, bridges):
1403 - Make bridge relays check once a minute for whether their IP
1404 address has changed, rather than only every 15 minutes. Resolves
1406 - Refactor resolve_my_address() so it returns the method by which we
1407 decided our public IP address (explicitly configured, resolved from
1408 explicit hostname, guessed from interfaces, learned by gethostname).
1409 Now we can provide more helpful log messages when a relay guesses
1410 its IP address incorrectly (e.g. due to unexpected lines in
1411 /etc/hosts). Resolves ticket 2267.
1412 - Teach bridge-using clients to avoid 0.2.2 bridges when making
1413 microdescriptor-related dir requests, and only fall back to normal
1414 descriptors if none of their bridges can handle microdescriptors
1415 (as opposed to the fix in ticket 4013, which caused them to fall
1416 back to normal descriptors if *any* of their bridges preferred
1417 them). Resolves ticket 4994.
1418 - Randomize the lifetime of our SSL link certificate, so censors can't
1419 use the static value for filtering Tor flows. Resolves ticket 8443;
1420 related to ticket 4014 which was included in 0.2.2.33.
1422 o Minor features (portability):
1423 - Tweak the curve25519-donna*.c implementations to tolerate systems
1424 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
1425 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
1426 the signs of types during autoconf. This is better than our old
1427 approach, which didn't work when cross-compiling.
1428 - Detect the sign of enum values, rather than assuming that MSC is the
1429 only compiler where enum types are all signed. Fixes bug 7727;
1430 bugfix on 0.2.4.10-alpha.
1432 o Minor features (other):
1433 - Say "KBytes" rather than "KB" in the man page (for various values
1434 of K), to further reduce confusion about whether Tor counts in
1435 units of memory or fractions of units of memory. Resolves ticket 7054.
1436 - Clear the high bit on curve25519 public keys before passing them to
1437 our backend, in case we ever wind up using a backend that doesn't do
1438 so itself. If we used such a backend, and *didn't* clear the high bit,
1439 we could wind up in a situation where users with such backends would
1440 be distinguishable from users without. Fixes bug 8121; bugfix on
1442 - Update to the March 6 2013 Maxmind GeoLite Country database.
1444 o Minor bugfixes (clients):
1445 - When we receive a RELAY_END cell with the reason DONE, or with no
1446 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
1447 status as "connection refused". Previously we reported these cases
1448 as success but then immediately closed the connection. Fixes bug
1449 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
1450 - Downgrade an assertion in connection_ap_expire_beginning to an
1451 LD_BUG message. The fix for bug 8024 should prevent this message
1452 from displaying, but just in case, a warn that we can diagnose
1453 is better than more assert crashes. Fixes bug 8065; bugfix on
1455 - Lower path use bias thresholds to .80 for notice and .60 for warn.
1456 Also make the rate limiting flags for the path use bias log messages
1457 independent from the original path bias flags. Fixes bug 8161;
1458 bugfix on 0.2.4.10-alpha.
1460 o Minor bugfixes (relays):
1461 - Stop trying to resolve our hostname so often (e.g. every time we
1462 think about doing a directory fetch). Now we reuse the cached
1463 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
1464 and 2410 (bugfix on 0.1.2.2-alpha).
1465 - Stop sending a stray "(null)" in some cases for the server status
1466 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
1468 - When choosing which stream on a formerly stalled circuit to wake
1469 first, make better use of the platform's weak RNG. Previously,
1470 we had been using the % ("modulo") operator to try to generate a
1471 1/N chance of picking each stream, but this behaves badly with
1472 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
1474 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
1475 Irix's random() only return 15 bits; Solaris's random() returns more
1476 bits but its RAND_MAX says it only returns 15, and so on. Motivated
1477 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
1479 o Minor bugfixes (directory authorities):
1480 - Directory authorities now use less space when formatting identical
1481 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
1484 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
1485 - Avoid leaking memory if we fail to compute a consensus signature
1486 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
1487 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
1489 - Fix a memory leak during safe-cookie controller authentication.
1490 Bugfix on 0.2.3.13-alpha.
1491 - Avoid memory leak of IPv6 policy content if we fail to format it into
1492 a router descriptor. Bugfix on 0.2.4.7-alpha.
1494 o Minor bugfixes (other code correctness issues):
1495 - Avoid a crash if we fail to generate an extrainfo descriptor.
1496 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
1498 - When detecting the largest possible file descriptor (in order to
1499 close all file descriptors when launching a new program), actually
1500 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
1501 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
1503 - Fix a copy-and-paste error when adding a missing A1 to a routerset
1504 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
1505 Bugfix on 0.2.4.10-alpha.
1506 - Fix an impossible-to-trigger integer overflow when estimating how
1507 long our onionskin queue would take. (This overflow would require us
1508 to accept 4 million onionskins before processing 100 of them.) Fixes
1509 bug 8210; bugfix on 0.2.4.10-alpha.
1511 o Code simplification and refactoring:
1512 - Add a wrapper function for the common "log a message with a
1516 Changes in version 0.2.4.10-alpha - 2013-02-04
1517 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
1518 certain attacks that flood the network with relays; changes the queue
1519 for circuit create requests from a sized-based limit to a time-based
1520 limit; resumes building with MSVC on Windows; and fixes a wide variety
1523 o Major bugfixes (directory authority):
1524 - When computing directory thresholds, ignore any rejected-as-sybil
1525 nodes during the computation so that they can't influence Fast,
1526 Guard, etc. (We should have done this for proposal 109.) Fixes
1528 - When marking a node as a likely sybil, reset its uptime metrics
1529 to zero, so that it cannot time towards getting marked as Guard,
1530 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
1534 - When a TLS write is partially successful but incomplete, remember
1535 that the flushed part has been flushed, and notice that bytes were
1536 actually written. Reported and fixed pseudonymously. Fixes bug
1537 7708; bugfix on Tor 0.1.0.5-rc.
1538 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
1539 ID: these could be used to create unexpected streams and circuits
1540 which would count as "present" to some parts of Tor but "absent"
1541 to others, leading to zombie circuits and streams or to a bandwidth
1542 denial-of-service. Fixes bug 7889; bugfix on every released version
1543 of Tor. Reported by "oftc_must_be_destroyed".
1544 - Rename all macros in our local copy of queue.h to begin with "TOR_".
1545 This change seems the only good way to permanently prevent conflicts
1546 with queue.h on various operating systems. Fixes bug 8107; bugfix
1549 o Major features (relay):
1550 - Instead of limiting the number of queued onionskins (aka circuit
1551 create requests) to a fixed, hard-to-configure number, we limit
1552 the size of the queue based on how many we expect to be able to
1553 process in a given amount of time. We estimate the time it will
1554 take to process an onionskin based on average processing time
1555 of previous onionskins. Closes ticket 7291. You'll never have to
1556 configure MaxOnionsPending again.
1558 o Major features (portability):
1559 - Resume building correctly with MSVC and Makefile.nmake. This patch
1560 resolves numerous bugs and fixes reported by ultramage, including
1561 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
1562 - Make the ntor and curve25519 code build correctly with MSVC.
1563 Fix on 0.2.4.8-alpha.
1566 - When directory authorities are computing thresholds for flags,
1567 never let the threshold for the Fast flag fall below 4096
1568 bytes. Also, do not consider nodes with extremely low bandwidths
1569 when deciding thresholds for various directory flags. This change
1570 should raise our threshold for Fast relays, possibly in turn
1571 improving overall network performance; see ticket 1854. Resolves
1573 - The Tor client now ignores sub-domain components of a .onion
1574 address. This change makes HTTP "virtual" hosting
1575 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
1576 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
1577 hosted on the same hidden service. Implements proposal 204.
1578 - We compute the overhead from passing onionskins back and forth to
1579 cpuworkers, and report it when dumping statistics in response to
1580 SIGUSR1. Supports ticket 7291.
1582 o Minor features (path selection):
1583 - When deciding whether we have enough descriptors to build circuits,
1584 instead of looking at raw relay counts, look at which fraction
1585 of (bandwidth-weighted) paths we're able to build. This approach
1586 keeps clients from building circuits if their paths are likely to
1587 stand out statistically. The default fraction of paths needed is
1588 taken from the consensus directory; you can override it with the
1589 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
1590 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
1591 and we have GeoIP information, also exclude all nodes with unknown
1592 countries "??" and "A1". This behavior is controlled by the
1593 new GeoIPExcludeUnknown option: you can make such nodes always
1594 excluded with "GeoIPExcludeUnknown 1", and disable the feature
1595 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
1596 gets you the default behavior. Implements feature 7706.
1597 - Path Use Bias: Perform separate accounting for successful circuit
1598 use. Keep separate statistics on stream attempt rates versus stream
1599 success rates for each guard. Provide configurable thresholds to
1600 determine when to emit log messages or disable use of guards that
1601 fail too many stream attempts. Resolves ticket 7802.
1603 o Minor features (log messages):
1604 - When learning a fingerprint for a bridge, log its corresponding
1605 transport type. Implements ticket 7896.
1606 - Improve the log message when "Bug/attack: unexpected sendme cell
1607 from client" occurs, to help us track bug 8093.
1610 - Remove a couple of extraneous semicolons that were upsetting the
1611 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
1612 bugfix on 0.2.2.1-alpha.
1613 - Remove a source of rounding error during path bias count scaling;
1614 don't count cannibalized circuits as used for path bias until we
1615 actually try to use them; and fix a circuit_package_relay_cell()
1616 warning message about n_chan==NULL. Fixes bug 7802.
1617 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
1618 actually link against nacl when we're configured to use it. Fixes
1619 bug 7972; bugfix on 0.2.4.8-alpha.
1620 - Compile correctly with the --disable-curve25519 option. Fixes
1621 bug 8153; bugfix on 0.2.4.8-alpha.
1623 o Build improvements:
1624 - Do not report status verbosely from autogen.sh unless the -v flag
1625 is specified. Fixes issue 4664. Patch from Onizuka.
1626 - Replace all calls to snprintf() outside of src/ext with
1627 tor_snprintf(). Also remove the #define to replace snprintf with
1628 _snprintf on Windows; they have different semantics, and all of
1629 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
1630 - Try to detect if we are ever building on a platform where
1631 memset(...,0,...) does not set the value of a double to 0.0. Such
1632 platforms are permitted by the C standard, though in practice
1633 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
1634 currently support them, but it's better to detect them and fail
1635 than to perform erroneously.
1638 - Stop exporting estimates of v2 and v3 directory traffic shares
1639 in extrainfo documents. They were unneeded and sometimes inaccurate.
1640 Also stop exporting any v2 directory request statistics. Resolves
1642 - Drop support for detecting and warning about versions of Libevent
1643 before 1.3e. Nothing reasonable ships with them any longer;
1644 warning the user about them shouldn't be needed. Resolves ticket
1647 o Code simplifications and refactoring:
1648 - Rename "isin" functions to "contains", for grammar. Resolves
1650 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
1651 with the natural logarithm function from the system libm. Resolves
1655 Changes in version 0.2.4.9-alpha - 2013-01-15
1656 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
1660 - Fix backward compatibility logic when receiving an embedded ntor
1661 handshake tunneled in a CREATE cell. This clears up the "Bug:
1662 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
1666 Changes in version 0.2.4.8-alpha - 2013-01-14
1667 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
1668 risks, adds a new stronger and faster circuit handshake, and offers
1669 stronger and faster link encryption when both sides support it.
1672 - Preliminary support for directory guards (proposal 207): when
1673 possible, clients now use their entry guards for non-anonymous
1674 directory requests. This can help prevent client enumeration. Note
1675 that this behavior only works when we have a usable consensus
1676 directory, and when options about what to download are more or less
1677 standard. In the future we should re-bootstrap from our guards,
1678 rather than re-bootstrapping from the preconfigured list of
1679 directory sources that ships with Tor. Resolves ticket 6526.
1680 - Tor relays and clients now support a better CREATE/EXTEND cell
1681 format, allowing the sender to specify multiple address, identity,
1682 and handshake types. Implements Robert Ransom's proposal 200;
1685 o Major features (new circuit handshake):
1686 - Tor now supports a new circuit extension handshake designed by Ian
1687 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
1688 circuit extension handshake, later called "TAP", was a bit slow
1689 (especially on the relay side), had a fragile security proof, and
1690 used weaker keys than we'd now prefer. The new circuit handshake
1691 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
1692 function, making it significantly more secure than the older
1693 handshake, and significantly faster. Tor can use one of two built-in
1694 pure-C curve25519-donna implementations by Adam Langley, or it
1695 can link against the "nacl" library for a tuned version if present.
1697 The built-in version is very fast for 64-bit systems when building
1698 with GCC. The built-in 32-bit version is still faster than the
1699 old TAP protocol, but using libnacl is better on most such hosts.
1701 Clients don't currently use this protocol by default, since
1702 comparatively few clients support it so far. To try it, set
1703 UseNTorHandshake to 1.
1705 Implements proposal 216; closes ticket 7202.
1707 o Major features (better link encryption):
1708 - Relays can now enable the ECDHE TLS ciphersuites when available
1709 and appropriate. These ciphersuites let us negotiate forward-secure
1710 TLS secret keys more safely and more efficiently than with our
1711 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
1712 public relays prefer the (faster) P224 group, and bridges prefer
1713 the (more common) P256 group; you can override this with the
1716 Enabling these ciphers was a little tricky, since for a long time,
1717 clients had been claiming to support them without actually doing
1718 so, in order to foil fingerprinting. But with the client-side
1719 implementation of proposal 198 in 0.2.3.17-beta, clients can now
1720 match the ciphers from recent Firefox versions *and* list the
1721 ciphers they actually mean, so relays can believe such clients
1722 when they advertise ECDHE support in their TLS ClientHello messages.
1724 This feature requires clients running 0.2.3.17-beta or later,
1725 and requires both sides to be running OpenSSL 1.0.0 or later
1726 with ECC support. OpenSSL 1.0.1, with the compile-time option
1727 "enable-ec_nistp_64_gcc_128", is highly recommended.
1729 Implements the relay side of proposal 198; closes ticket 7200.
1732 - Avoid crashing when, as a relay without IPv6-exit support, a
1733 client insists on getting an IPv6 address or nothing. Fixes bug
1734 7814; bugfix on 0.2.4.7-alpha.
1737 - Improve circuit build timeout handling for hidden services.
1738 In particular: adjust build timeouts more accurately depending
1739 upon the number of hop-RTTs that a particular circuit type
1740 undergoes. Additionally, launch intro circuits in parallel
1741 if they timeout, and take the first one to reply as valid.
1742 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
1743 separate error codes; or at least, don't break for that reason.
1744 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
1745 - Update to the January 2 2013 Maxmind GeoLite Country database.
1747 o Minor features (testing):
1748 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
1749 (P-256) Diffie-Hellman handshakes to src/or/bench.
1750 - Add benchmark functions to test onion handshake performance.
1752 o Minor features (path bias detection):
1753 - Alter the Path Bias log messages to be more descriptive in terms
1754 of reporting timeouts and other statistics.
1755 - Create three levels of Path Bias log messages, as opposed to just
1756 two. These are configurable via consensus as well as via the torrc
1757 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
1758 The default values are 0.70, 0.50, and 0.30 respectively.
1759 - Separate the log message levels from the decision to drop guards,
1760 which also is available via torrc option PathBiasDropGuards.
1761 PathBiasDropGuards still defaults to 0 (off).
1762 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
1763 in combination with PathBiasExtremeRate.
1764 - Increase the default values for PathBiasScaleThreshold and
1765 PathBiasCircThreshold from (200, 20) to (300, 150).
1766 - Add in circuit usage accounting to path bias. If we try to use a
1767 built circuit but fail for any reason, it counts as path bias.
1768 Certain classes of circuits where the adversary gets to pick your
1769 destination node are exempt from this accounting. Usage accounting
1770 can be specifically disabled via consensus parameter or torrc.
1771 - Convert all internal path bias state to double-precision floating
1772 point, to avoid roundoff error and other issues.
1773 - Only record path bias information for circuits that have completed
1774 *two* hops. Assuming end-to-end tagging is the attack vector, this
1775 makes us more resilient to ambient circuit failure without any
1776 detection capability loss.
1778 o Minor bugfixes (log messages):
1779 - Rate-limit the "No circuits are opened. Relaxed timeout for a
1780 circuit with channel state open..." message to once per hour to
1781 keep it from filling the notice logs. Mitigates bug 7799 but does
1782 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
1783 - Avoid spurious warnings when configuring multiple client ports of
1784 which only some are nonlocal. Previously, we had claimed that some
1785 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
1788 o Code simplifications and refactoring:
1789 - Get rid of a couple of harmless clang warnings, where we compared
1790 enums to ints. These warnings are newly introduced in clang 3.2.
1791 - Split the onion.c file into separate modules for the onion queue
1792 and the different handshakes it supports.
1793 - Remove the marshalling/unmarshalling code for sending requests to
1794 cpuworkers over a socket, and instead just send structs. The
1795 recipient will always be the same Tor binary as the sender, so
1796 any encoding is overkill.
1799 Changes in version 0.2.4.7-alpha - 2012-12-24
1800 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
1801 directory mirrors for more robust bootstrapping; fixes more issues where
1802 clients with changing network conditions refuse to make any circuits;
1803 adds initial support for exiting to IPv6 addresses; resumes being able
1804 to update our GeoIP database, and includes the geoip6 file this time;
1805 turns off the client-side DNS cache by default due to privacy risks;
1806 and fixes a variety of other issues.
1808 o Major features (client resilience):
1809 - Add a new "FallbackDir" torrc option to use when we can't use
1810 a directory mirror from the consensus (either because we lack a
1811 consensus, or because they're all down). Currently, all authorities
1812 are fallbacks by default, and there are no other default fallbacks,
1813 but that will change. This option will allow us to give clients a
1814 longer list of servers to try to get a consensus from when first
1815 connecting to the Tor network, and thereby reduce load on the
1816 directory authorities. Implements proposal 206, "Preconfigured
1817 directory sources for bootstrapping". We also removed the old
1818 "FallbackNetworkstatus" option, since we never got it working well
1819 enough to use it. Closes bug 572.
1820 - If we have no circuits open, use a relaxed timeout (the
1821 95-percentile cutoff) until a circuit succeeds. This heuristic
1822 should allow Tor to succeed at building circuits even when the
1823 network connection drastically changes. Should help with bug 3443.
1825 o Major features (IPv6):
1826 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
1827 connectivity, then set the IPv6Exit flag to 1. Also make sure your
1828 exit policy reads as you would like: the address * applies to all
1829 address families, whereas *4 is IPv4 address only, and *6 is IPv6
1830 addresses only. On the client side, you'll need to wait until the
1831 authorities have upgraded, wait for enough exits to support IPv6,
1832 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
1833 ticket 5547, implements proposal 117 as revised in proposal 208.
1835 We DO NOT recommend that clients with actual anonymity needs start
1836 using IPv6 over Tor yet, since not enough exits support it yet.
1838 o Major features (geoip database):
1839 - Maxmind began labelling Tor relays as being in country "A1",
1840 which breaks by-country node selection inside Tor. Now we use a
1841 script to replace "A1" ("Anonymous Proxy") entries in our geoip
1842 file with real country codes. This script fixes about 90% of "A1"
1843 entries automatically and uses manual country code assignments to
1844 fix the remaining 10%. See src/config/README.geoip for details.
1845 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
1846 Country database, as modified above.
1848 o Major bugfixes (client-side DNS):
1849 - Turn off the client-side DNS cache by default. Updating and using
1850 the DNS cache is now configurable on a per-client-port
1851 level. SOCKSPort, DNSPort, etc lines may now contain
1852 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
1853 cache these types of DNS answers when we receive them from an
1854 exit node in response to an application request on this port, and
1855 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
1856 cached DNS answers of these types, we shouldn't use them. It's
1857 potentially risky to use cached DNS answers at the client, since
1858 doing so can indicate to one exit what answers we've gotten
1859 for DNS lookups in the past. With IPv6, this becomes especially
1860 problematic. Using cached DNS answers for requests on the same
1861 circuit would present less linkability risk, since all traffic
1862 on a circuit is already linkable, but it would also provide
1863 little performance benefit: the exit node caches DNS replies
1864 too. Implements a simplified version of Proposal 205. Implements
1867 o Major bugfixes (other):
1868 - Alter circuit build timeout measurement to start at the point
1869 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
1870 initialization). This should make our timeout measurements more
1871 uniform. Previously, we were sometimes including ORconn setup time
1872 in our circuit build time measurements. Should resolve bug 3443.
1873 - Fix an assertion that could trigger in hibernate_go_dormant() when
1874 closing an or_connection_t: call channel_mark_for_close() rather
1875 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
1877 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
1878 7655; bugfix on 0.2.4.6-alpha.
1881 - Add a new torrc option "ServerTransportListenAddr" to let bridge
1882 operators select the address where their pluggable transports will
1883 listen for connections. Resolves ticket 7013.
1884 - Allow an optional $ before the node identity digest in the
1885 controller command GETINFO ns/id/<identity>, for consistency with
1886 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
1887 - Log packaged cell fullness as part of the heartbeat message.
1888 Diagnosis to try to determine the extent of bug 7743.
1890 o Minor features (IPv6):
1891 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
1892 prefer to hand out virtual IPv6 addresses, since there are more of
1893 them and we can't run out. To override this behavior and make IPv4
1894 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
1895 or DNSPort you're using for resolving. Implements ticket 7571.
1896 - AutomapHostsOnResolve responses are now randomized, to avoid
1897 annoying situations where Tor is restarted and applications
1898 connect to the wrong addresses.
1899 - Never try more than 1000 times to pick a new virtual address when
1900 AutomapHostsOnResolve is set. That's good enough so long as we
1901 aren't close to handing out our entire virtual address space;
1902 if you're getting there, it's best to switch to IPv6 virtual
1906 - The ADDRMAP command can no longer generate an ill-formed error
1907 code on a failed MAPADDRESS. It now says "internal" rather than
1908 an English sentence fragment with spaces in the middle. Bugfix on
1910 - Fix log messages and comments to avoid saying "GMT" when we mean
1911 "UTC". Fixes bug 6113.
1912 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1914 - Fix a crash when debugging unit tests on Windows: deallocate a
1915 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1916 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1919 - The DirServer option is now DirAuthority, for consistency with
1920 current naming patterns. You can still use the old DirServer form.
1922 o Code simplification and refactoring:
1923 - Move the client-side address-map/virtual-address/DNS-cache code
1924 out of connection_edge.c into a new addressmap.c module.
1925 - Remove unused code for parsing v1 directories and "running routers"
1926 documents. Fixes bug 6887.
1929 Changes in version 0.2.3.25 - 2012-11-19
1930 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1931 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1932 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1933 programmer, and friend. Unstinting in his dedication to the cause of
1934 freedom, he inspired and helped many of us as we began our work on
1935 anonymity, and inspires us still. Please honor his memory by writing
1936 software to protect people's freedoms, and by helping others to do so.
1938 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1939 significantly reduced directory overhead (via microdescriptors),
1940 enormous crypto performance improvements for fast relays on new
1941 enough hardware, a new v3 TLS handshake protocol that can better
1942 resist fingerprinting, support for protocol obfuscation plugins (aka
1943 pluggable transports), better scalability for hidden services, IPv6
1944 support for bridges, performance improvements like allowing clients
1945 to skip the first round-trip on the circuit ("optimistic data") and
1946 refilling token buckets more often, a new "stream isolation" design
1947 to isolate different applications on different circuits, and many
1948 stability, security, and privacy fixes.
1951 - Tor tries to wipe potentially sensitive data after using it, so
1952 that if some subsequent security failure exposes Tor's memory,
1953 the damage will be limited. But we had a bug where the compiler
1954 was eliminating these wipe operations when it decided that the
1955 memory was no longer visible to a (correctly running) program,
1956 hence defeating our attempt at defense in depth. We fix that
1957 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1958 is unlikely to optimize away. Future versions of Tor may use
1959 a less ridiculously heavy approach for this. Fixes bug 7352.
1960 Reported in an article by Andrey Karpov.
1963 - Fix a harmless bug when opting against publishing a relay descriptor
1964 because DisableNetwork is set. Fixes bug 7464; bugfix on
1968 Changes in version 0.2.4.6-alpha - 2012-11-13
1969 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
1970 makes our defense-in-depth memory wiping more reliable, and begins to
1971 count IPv6 addresses in bridge statistics,
1974 - Fix an assertion failure that could occur when closing a connection
1975 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
1977 - Tor tries to wipe potentially sensitive data after using it, so
1978 that if some subsequent security failure exposes Tor's memory,
1979 the damage will be limited. But we had a bug where the compiler
1980 was eliminating these wipe operations when it decided that the
1981 memory was no longer visible to a (correctly running) program,
1982 hence defeating our attempt at defense in depth. We fix that
1983 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1984 is unlikely to optimize away. Future versions of Tor may use
1985 a less ridiculously heavy approach for this. Fixes bug 7352.
1986 Reported in an article by Andrey Karpov.
1989 - Add GeoIP database for IPv6 addresses. The new config option
1991 - Bridge statistics now count bridge clients connecting over IPv6:
1992 bridge statistics files now list "bridge-ip-versions" and
1993 extra-info documents list "geoip6-db-digest". The control protocol
1994 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1995 implementation by "shkoo", addressing ticket 5055.
1998 - Warn when we are binding low ports when hibernation is enabled;
1999 previously we had warned when we were _advertising_ low ports with
2000 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
2001 - Fix a harmless bug when opting against publishing a relay descriptor
2002 because DisableNetwork is set. Fixes bug 7464; bugfix on
2004 - Add warning message when a managed proxy dies during configuration.
2005 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
2006 - Fix a linking error when building tor-fw-helper without miniupnp.
2007 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
2008 - Check for closing an or_connection_t without going through correct
2009 channel functions; emit a warning and then call
2010 connection_or_close_for_error() so we don't assert as in bugs 7212
2012 - Compile correctly on compilers without C99 designated initializer
2013 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
2014 - Avoid a possible assert that can occur when channel_send_destroy() is
2015 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
2016 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
2017 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
2018 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
2019 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
2021 o Code simplification and refactoring:
2022 - Start using OpenBSD's implementation of queue.h, so that we don't
2023 need to hand-roll our own pointer and list structures whenever we
2024 need them. (We can't rely on a sys/queue.h, since some operating
2025 systems don't have them, and the ones that do have them don't all
2026 present the same extensions.)
2029 Changes in version 0.2.4.5-alpha - 2012-10-25
2030 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
2031 two important security vulnerabilities that could lead to remotely
2032 triggerable relay crashes, fix a major bug that was preventing clients
2033 from choosing suitable exit nodes, and refactor some of our code.
2035 o Major bugfixes (security, also in 0.2.3.24-rc):
2036 - Fix a group of remotely triggerable assertion failures related to
2037 incorrect link protocol negotiation. Found, diagnosed, and fixed
2038 by "some guy from France". Fix for CVE-2012-2250; bugfix on
2040 - Fix a denial of service attack by which any directory authority
2041 could crash all the others, or by which a single v2 directory
2042 authority could crash everybody downloading v2 directory
2043 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
2045 o Major bugfixes (also in 0.2.3.24-rc):
2046 - When parsing exit policy summaries from microdescriptors, we had
2047 previously been ignoring the last character in each one, so that
2048 "accept 80,443,8080" would be treated by clients as indicating
2049 a node that allows access to ports 80, 443, and 808. That would
2050 lead to clients attempting connections that could never work,
2051 and ignoring exit nodes that would support their connections. Now
2052 clients parse these exit policy summaries correctly. Fixes bug 7192;
2053 bugfix on 0.2.3.1-alpha.
2055 o Minor bugfixes (also in 0.2.3.24-rc):
2056 - Clients now consider the ClientRejectInternalAddresses config option
2057 when using a microdescriptor consensus stanza to decide whether
2058 an exit relay would allow exiting to an internal address. Fixes
2059 bug 7190; bugfix on 0.2.3.1-alpha.
2062 - Only disable TLS session ticket support when running as a TLS
2063 server. Now clients will blend better with regular Firefox
2064 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
2066 o Code simplification and refactoring:
2067 - Start using OpenBSD's implementation of queue.h (originally by
2069 - Move the entry node code from circuitbuild.c to its own file.
2070 - Move the circuit build timeout tracking code from circuitbuild.c
2074 Changes in version 0.2.3.24-rc - 2012-10-25
2075 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
2076 could lead to remotely triggerable relay crashes, and fixes
2077 a major bug that was preventing clients from choosing suitable exit
2080 o Major bugfixes (security):
2081 - Fix a group of remotely triggerable assertion failures related to
2082 incorrect link protocol negotiation. Found, diagnosed, and fixed
2083 by "some guy from France". Fix for CVE-2012-2250; bugfix on
2085 - Fix a denial of service attack by which any directory authority
2086 could crash all the others, or by which a single v2 directory
2087 authority could crash everybody downloading v2 directory
2088 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
2091 - When parsing exit policy summaries from microdescriptors, we had
2092 previously been ignoring the last character in each one, so that
2093 "accept 80,443,8080" would be treated by clients as indicating
2094 a node that allows access to ports 80, 443, and 808. That would
2095 lead to clients attempting connections that could never work,
2096 and ignoring exit nodes that would support their connections. Now
2097 clients parse these exit policy summaries correctly. Fixes bug 7192;
2098 bugfix on 0.2.3.1-alpha.
2101 - Clients now consider the ClientRejectInternalAddresses config option
2102 when using a microdescriptor consensus stanza to decide whether
2103 an exit relay would allow exiting to an internal address. Fixes
2104 bug 7190; bugfix on 0.2.3.1-alpha.
2107 Changes in version 0.2.4.4-alpha - 2012-10-20
2108 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
2109 vulnerability introduced by a change in OpenSSL, fixes a remotely
2110 triggerable assert, and adds new channel_t and circuitmux_t abstractions
2111 that will make it easier to test new connection transport and cell
2112 scheduling algorithms.
2114 o New directory authorities (also in 0.2.3.23-rc):
2115 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
2116 authority. Closes ticket 5749.
2118 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
2119 - Disable TLS session tickets. OpenSSL's implementation was giving
2120 our TLS session keys the lifetime of our TLS context objects, when
2121 perfect forward secrecy would want us to discard anything that
2122 could decrypt a link connection as soon as the link connection
2123 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
2124 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
2125 - Discard extraneous renegotiation attempts once the V3 link
2126 protocol has been initiated. Failure to do so left us open to
2127 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
2128 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
2130 o Internal abstraction features:
2131 - Introduce new channel_t abstraction between circuits and
2132 or_connection_t to allow for implementing alternate OR-to-OR
2133 transports. A channel_t is an abstract object which can either be a
2134 cell-bearing channel, which is responsible for authenticating and
2135 handshaking with the remote OR and transmitting cells to and from
2136 it, or a listening channel, which spawns new cell-bearing channels
2137 at the request of remote ORs. Implements part of ticket 6465.
2138 - Also new is the channel_tls_t subclass of channel_t, adapting it
2139 to the existing or_connection_t code. The V2/V3 protocol handshaking
2140 code which formerly resided in command.c has been moved below the
2141 channel_t abstraction layer and may be found in channeltls.c now.
2142 Implements the rest of ticket 6465.
2143 - Introduce new circuitmux_t storing the queue of circuits for
2144 a channel; this encapsulates and abstracts the queue logic and
2145 circuit selection policy, and allows the latter to be overridden
2146 easily by switching out a policy object. The existing EWMA behavior
2147 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
2149 o Required libraries:
2150 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
2151 strongly recommended.
2154 - Warn users who run hidden services on a Tor client with
2155 UseEntryGuards disabled that their hidden services will be
2156 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
2157 attack which motivated Tor to support entry guards in the first
2158 place). Resolves ticket 6889.
2159 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
2160 dhill. Resolves ticket 6982.
2161 - Option OutboundBindAddress can be specified multiple times and
2162 accepts IPv6 addresses. Resolves ticket 6876.
2164 o Minor bugfixes (also in 0.2.3.23-rc):
2165 - Don't serve or accept v2 hidden service descriptors over a
2166 relay's DirPort. It's never correct to do so, and disabling it
2167 might make it more annoying to exploit any bugs that turn up in the
2168 descriptor-parsing code. Fixes bug 7149.
2169 - Fix two cases in src/or/transports.c where we were calling
2170 fmt_addr() twice in a parameter list. Bug found by David
2171 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
2172 - Fix memory leaks whenever we logged any message about the "path
2173 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
2174 - When relays refuse a "create" cell because their queue of pending
2175 create cells is too big (typically because their cpu can't keep up
2176 with the arrival rate), send back reason "resource limit" rather
2177 than reason "internal", so network measurement scripts can get a
2178 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
2181 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
2182 - Free some more still-in-use memory at exit, to make hunting for
2183 memory leaks easier. Resolves bug 7029.
2184 - When a Tor client gets a "truncated" relay cell, the first byte of
2185 its payload specifies why the circuit was truncated. We were
2186 ignoring this 'reason' byte when tearing down the circuit, resulting
2187 in the controller not being told why the circuit closed. Now we
2188 pass the reason from the truncated cell to the controller. Bugfix
2189 on 0.1.2.3-alpha; fixes bug 7039.
2190 - Downgrade "Failed to hand off onionskin" messages to "debug"
2191 severity, since they're typically redundant with the "Your computer
2192 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
2193 - Make clients running with IPv6 bridges connect over IPv6 again,
2194 even without setting new config options ClientUseIPv6 and
2195 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
2196 - Use square brackets around IPv6 addresses in numerous places
2197 that needed them, including log messages, HTTPS CONNECT proxy
2198 requests, TransportProxy statefile entries, and pluggable transport
2199 extra-info lines. Fixes bug 7011; patch by David Fifield.
2201 o Code refactoring and cleanup:
2202 - Source files taken from other packages now reside in src/ext;
2203 previously they were scattered around the rest of Tor.
2204 - Avoid use of reserved identifiers in our C code. The C standard
2205 doesn't like us declaring anything that starts with an
2206 underscore, so let's knock it off before we get in trouble. Fix
2207 for bug 1031; bugfix on the first Tor commit.
2210 Changes in version 0.2.3.23-rc - 2012-10-20
2211 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
2212 vulnerability introduced by a change in OpenSSL, and fixes a variety
2213 of smaller bugs in preparation for the release.
2215 o New directory authorities:
2216 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
2217 authority. Closes ticket 5749.
2219 o Major bugfixes (security/privacy):
2220 - Disable TLS session tickets. OpenSSL's implementation was giving
2221 our TLS session keys the lifetime of our TLS context objects, when
2222 perfect forward secrecy would want us to discard anything that
2223 could decrypt a link connection as soon as the link connection
2224 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
2225 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
2226 - Discard extraneous renegotiation attempts once the V3 link
2227 protocol has been initiated. Failure to do so left us open to
2228 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
2229 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
2232 - Fix a possible crash bug when checking for deactivated circuits
2233 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
2234 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
2236 o Minor bugfixes (on 0.2.3.x):
2237 - Fix two cases in src/or/transports.c where we were calling
2238 fmt_addr() twice in a parameter list. Bug found by David
2239 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
2240 - Convert an assert in the pathbias code to a log message. The assert
2241 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
2242 bugfix on 0.2.3.17-beta.
2243 - Fix memory leaks whenever we logged any message about the "path
2244 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
2246 o Minor bugfixes (on 0.2.2.x and earlier):
2247 - Don't serve or accept v2 hidden service descriptors over a relay's
2248 DirPort. It's never correct to do so, and disabling it might
2249 make it more annoying to exploit any bugs that turn up in the
2250 descriptor-parsing code. Fixes bug 7149.
2251 - When relays refuse a "create" cell because their queue of pending
2252 create cells is too big (typically because their cpu can't keep up
2253 with the arrival rate), send back reason "resource limit" rather
2254 than reason "internal", so network measurement scripts can get a
2255 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
2256 - Correct file sizes when reading binary files on Cygwin, to avoid
2257 a bug where Tor would fail to read its state file. Fixes bug 6844;
2258 bugfix on 0.1.2.7-alpha.
2259 - Avoid undefined behaviour when parsing the list of supported
2260 rendezvous/introduction protocols in a hidden service descriptor.
2261 Previously, Tor would have confused (as-yet-unused) protocol version
2262 numbers greater than 32 with lower ones on many platforms. Fixes
2263 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
2265 o Documentation fixes:
2266 - Clarify that hidden services are TCP only. Fixes bug 6024.
2269 Changes in version 0.2.4.3-alpha - 2012-09-22
2270 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
2271 assertion, resumes letting relays test reachability of their DirPort,
2272 and cleans up a bunch of smaller bugs.
2275 - Fix an assertion failure in tor_timegm() that could be triggered
2276 by a badly formatted directory object. Bug found by fuzzing with
2277 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2280 - Fix a possible crash bug when checking for deactivated circuits
2281 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
2282 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
2283 - Allow routers to detect that their own DirPorts are running. When
2284 we removed support for versions_supports_begindir, we also
2285 accidentally removed the mechanism we used to self-test our
2286 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
2287 bugfix on 0.2.4.2-alpha.
2289 o Security features:
2290 - Switch to a completely time-invariant approach for picking nodes
2291 weighted by bandwidth. Our old approach would run through the
2292 part of the loop after it had made its choice slightly slower
2293 than it ran through the part of the loop before it had made its
2294 choice. Addresses ticket 6538.
2295 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
2296 by tor2web clients allows hidden services to identify tor2web
2297 clients through their repeated selection of the same rendezvous
2298 and introduction point circuit endpoints (their guards). Resolves
2302 - Enable Tor to read configuration, state, and key information from
2303 a FIFO. Previously Tor would only read from files with a positive
2304 stat.st_size. Code from meejah; fixes bug 6044.
2307 - Correct file sizes when reading binary files on Cygwin, to avoid
2308 a bug where Tor would fail to read its state file. Fixes bug 6844;
2309 bugfix on 0.1.2.7-alpha.
2310 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
2311 bugfix on 0.2.0.3-alpha.
2312 - When complaining about a client port on a public address, log
2313 which address we're complaining about. Fixes bug 4020; bugfix on
2314 0.2.3.3-alpha. Patch by Tom Fitzhenry.
2315 - Convert an assert in the pathbias code to a log message. The assert
2316 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
2317 bugfix on 0.2.3.17-beta.
2318 - Our new buildsystem was overzealous about rebuilding manpages: it
2319 would rebuild them all whenever any one of them changed. Now our
2320 dependency checking should be correct. Fixes bug 6843; bugfix on
2322 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
2323 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
2324 - Correct log printout about which address family is preferred
2325 when connecting to a bridge with both an IPv4 and IPv6 OR port.
2326 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
2328 o Minor bugfixes (code cleanliness):
2329 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
2330 with large values. This situation was untriggered, but nevertheless
2331 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
2332 - Reject consensus votes with more than 64 known-flags. We aren't even
2333 close to that limit yet, and our code doesn't handle it correctly.
2334 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
2335 - Avoid undefined behaviour when parsing the list of supported
2336 rendezvous/introduction protocols in a hidden service descriptor.
2337 Previously, Tor would have confused (as-yet-unused) protocol version
2338 numbers greater than 32 with lower ones on many platforms. Fixes
2339 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
2340 - Fix handling of rendezvous client authorization types over 8.
2341 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
2342 - Fix building with older versions of GCC (2.95, for one) that don't
2343 like preprocessor directives inside macro arguments. Found by
2344 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
2345 - Switch weighted node selection rule from using a list of doubles
2346 to using a list of int64_t. This change should make the process
2347 slightly easier to debug and maintain. Needed to finish ticket 6538.
2349 o Code simplification and refactoring:
2350 - Move the generic "config" code into a new file, and have "config.c"
2351 hold only torrc- and state-related code. Resolves ticket 6823.
2352 - Move the core of our "choose a weighted element at random" logic
2353 into its own function, and give it unit tests. Now the logic is
2354 testable, and a little less fragile too.
2355 - Removed the testing_since field of node_t, which hasn't been used
2356 for anything since 0.2.0.9-alpha.
2358 o Documentation fixes:
2359 - Clarify that hidden services are TCP only. Fixes bug 6024.
2360 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
2364 Changes in version 0.2.3.22-rc - 2012-09-11
2365 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
2369 - Fix an assertion failure in tor_timegm() that could be triggered
2370 by a badly formatted directory object. Bug found by fuzzing with
2371 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2374 - Avoid segfault when starting up having run with an extremely old
2375 version of Tor and parsing its state file. Fixes bug 6801; bugfix
2379 Changes in version 0.2.2.39 - 2012-09-11
2380 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
2384 - Fix an assertion failure in tor_timegm() that could be triggered
2385 by a badly formatted directory object. Bug found by fuzzing with
2386 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2387 - Do not crash when comparing an address with port value 0 to an
2388 address policy. This bug could have been used to cause a remote
2389 assertion failure by or against directory authorities, or to
2390 allow some applications to crash clients. Fixes bug 6690; bugfix
2394 Changes in version 0.2.4.2-alpha - 2012-09-10
2395 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
2396 raises the default rate limiting even more, and makes the bootstrapping
2397 log messages less noisy.
2400 - Automatically forward the TCP ports of pluggable transport
2401 proxies using tor-fw-helper if PortForwarding is enabled. Implements
2405 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
2406 to 1GB/1GB. The previous defaults were intended to be "basically
2407 infinite", but it turns out they're now limiting our 100mbit+
2408 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
2409 last time we raised it).
2412 - Detect when we're running with a version of OpenSSL other than the
2413 one we compiled with. This has occasionally given people hard-to-
2415 - Log fewer lines at level "notice" about our OpenSSL and Libevent
2416 versions and capabilities when everything is going right. Resolves
2417 part of ticket 6736.
2418 - Directory authorities no long accept descriptors for any version of
2419 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
2420 These versions are insecure, unsupported, or both. Implements
2424 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
2425 to start with a triple-underscore so the controller won't touch it.
2426 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
2427 - Avoid segfault when starting up having run with an extremely old
2428 version of Tor and parsing its state file. Fixes bug 6801; bugfix
2430 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
2431 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
2432 - Don't follow the NULL pointer if microdescriptor generation fails.
2433 (This does not appear to be triggerable, but it's best to be safe.)
2434 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
2435 - Fix mis-declared dependencies on src/common/crypto.c and
2436 src/or/tor_main.c that could break out-of-tree builds under some
2437 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
2438 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
2439 6778; bugfix on 0.2.4.1-alpha.
2440 - Fix a harmless (in this case) build warning for implicitly
2441 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
2444 - Now that all versions before 0.2.2.x are disallowed, we no longer
2445 need to work around their missing features. Thus we can remove a
2446 bunch of compatibility code.
2449 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
2450 TCP ports to forward. In the past it only accepted two ports:
2451 the ORPort and the DirPort.
2454 Changes in version 0.2.4.1-alpha - 2012-09-05
2455 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
2456 bridgedb; lets relays use IPv6 addresses and directory authorities
2457 advertise them; and switches to a cleaner build interface.
2459 This is the first alpha release in a new series, so expect there to
2460 be bugs. Users who would rather test out a more stable branch should
2461 stay with 0.2.3.x for now.
2463 o Major features (bridges):
2464 - Bridges now report the pluggable transports they support to the
2465 bridge authority, so it can pass the supported transports on to
2466 bridgedb and/or eventually do reachability testing. Implements
2469 o Major features (IPv6):
2470 - Bridge authorities now accept IPv6 bridge addresses and include
2471 them in network status documents. Implements ticket 5534.
2472 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
2473 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
2474 to happen. Implements ticket 5535.
2475 - All kind of relays, not just bridges, can now advertise an IPv6
2476 OR port. Implements ticket 6362.
2477 - Directory authorities vote on IPv6 OR ports using the new consensus
2478 method 14. Implements ticket 6363.
2480 o Major features (build):
2481 - Switch to a nonrecursive Makefile structure. Now instead of each
2482 Makefile.am invoking other Makefile.am's, there is a master
2483 Makefile.am that includes the others. This change makes our build
2484 process slightly more maintainable, and improves parallelism for
2485 building with make -j. Original patch by Stewart Smith; various
2486 fixes by Jim Meyering.
2487 - Where available, we now use automake's "silent" make rules by
2488 default, so that warnings are easier to spot. You can get the old
2489 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
2491 o Minor features (code security and spec conformance):
2492 - Clear keys and key-derived material left on the stack in
2493 rendservice.c and rendclient.c. Check return value of
2494 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
2495 These fixes should make us more forward-secure against cold-boot
2496 attacks and the like. Fixes bug 2385.
2497 - Reject EXTEND cells sent to nonexistent streams. According to the
2498 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
2499 we were only checking for stream IDs that were currently in use.
2500 Found while hunting for more instances of bug 6271. Bugfix on
2501 0.0.2pre8, which introduced incremental circuit construction.
2503 o Minor features (streamlining);
2504 - No longer include the "opt" prefix when generating routerinfos
2505 or v2 directories: it has been needless since Tor 0.1.2. Closes
2507 - Remove some now-needless code that tried to aggressively flush
2508 OR connections as data was added to them. Since 0.2.0.1-alpha, our
2509 cell queue logic has saved us from the failure mode that this code
2510 was supposed to prevent. Removing this code will limit the number
2511 of baroque control flow paths through Tor's network logic. Reported
2512 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
2514 o Minor features (controller):
2515 - Add a "GETINFO signal/names" control port command. Implements
2517 - Provide default values for all options via "GETINFO config/defaults".
2518 Implements ticket 4971.
2520 o Minor features (IPv6):
2521 - New config option "AuthDirHasIPv6Connectivity 1" that directory
2522 authorities should set if they have IPv6 connectivity and want to
2523 do reachability tests for IPv6 relays. Implements feature 5974.
2524 - A relay with an IPv6 OR port now sends that address in NETINFO
2525 cells (in addition to its other address). Implements ticket 6364.
2527 o Minor features (log messages):
2528 - Omit the first heartbeat log message, because it never has anything
2529 useful to say, and it clutters up the bootstrapping messages.
2530 Resolves ticket 6758.
2531 - Don't log about reloading the microdescriptor cache at startup. Our
2532 bootstrap warnings are supposed to tell the user when there's a
2533 problem, and our bootstrap notices say when there isn't. Resolves
2534 ticket 6759; bugfix on 0.2.2.6-alpha.
2535 - Don't log "I learned some more directory information" when we're
2536 reading cached directory information. Reserve it for when new
2537 directory information arrives in response to a fetch. Resolves
2539 - Prevent rounding error in path bias counts when scaling
2540 them down, and use the correct scale factor default. Also demote
2541 some path bias related log messages down a level and make others
2542 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
2543 - We no longer warn so much when generating manpages from their
2546 o Code simplifications and refactoring:
2547 - Enhance our internal sscanf replacement so that we can eliminate
2548 the last remaining uses of the system sscanf. (Though those uses
2549 of sscanf were safe, sscanf itself is generally error prone, so
2550 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
2552 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
2553 - Move last_reachable and testing_since from routerinfo_t to node_t.
2554 Implements ticket 5529.
2555 - Add replaycache_t structure, functions and unit tests, then refactor
2556 rend_service_introduce() to be more clear to read, improve, debug,
2557 and test. Resolves bug 6177.
2558 - Finally remove support for malloc_good_size and malloc_usable_size.
2559 We had hoped that these functions would let us eke a little more
2560 memory out of our malloc implementation. Unfortunately, the only
2561 implementations that provided these functions are also ones that
2562 are already efficient about not overallocation: they never got us
2563 more than 7 or so bytes per allocation. Removing them saves us a
2564 little code complexity and a nontrivial amount of build complexity.
2567 - Tor maintainers now require Automake version 1.9 or later to build
2568 Tor from the Git repository. (Automake is not required when building
2569 from a source distribution.)
2572 Changes in version 0.2.3.21-rc - 2012-09-05
2573 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
2574 series. It fixes a trio of potential security bugs, fixes a bug where
2575 we were leaving some of the fast relays out of the microdescriptor
2576 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
2577 and cleans up other smaller issues.
2579 o Major bugfixes (security):
2580 - Tear down the circuit if we get an unexpected SENDME cell. Clients
2581 could use this trick to make their circuits receive cells faster
2582 than our flow control would have allowed, or to gum up the network,
2583 or possibly to do targeted memory denial-of-service attacks on
2584 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
2585 from July 2002, before the release of Tor 0.0.0. We had committed
2586 this patch previously, but we had to revert it because of bug 6271.
2587 Now that 6271 is fixed, this patch appears to work.
2588 - Reject any attempt to extend to an internal address. Without
2589 this fix, a router could be used to probe addresses on an internal
2590 network to see whether they were accepting connections. Fixes bug
2591 6710; bugfix on 0.0.8pre1.
2592 - Do not crash when comparing an address with port value 0 to an
2593 address policy. This bug could have been used to cause a remote
2594 assertion failure by or against directory authorities, or to
2595 allow some applications to crash clients. Fixes bug 6690; bugfix
2599 - Remove the upper bound on microdescriptor length. We were hitting
2600 the limit for routers with complex exit policies or family
2601 declarations, causing clients to not use them. Fixes the first
2602 piece of bug 6404; fix on 0.2.2.6-alpha.
2603 - Detect "ORPort 0" as meaning, uniformly, that we're not running
2604 as a relay. Previously, some of our code would treat the presence
2605 of any ORPort line as meaning that we should act like a relay,
2606 even though our new listener code would correctly not open any
2607 ORPorts for ORPort 0. Similar bugs in other Port options are also
2608 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
2611 - Avoid a pair of double-free and use-after-mark bugs that can
2612 occur with certain timings in canceled and re-received DNS
2613 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
2614 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
2615 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
2616 - Allow one-hop directory fetching circuits the full "circuit build
2617 timeout" period, rather than just half of it, before failing them
2618 and marking the relay down. This fix should help reduce cases where
2619 clients declare relays (or worse, bridges) unreachable because
2620 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
2621 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
2623 - Authorities no longer include any router in their microdescriptor
2624 consensuses for which they couldn't generate or agree on a
2625 microdescriptor. Fixes the second piece of bug 6404; fix on
2627 - Detect and reject attempts to specify both "FooPort" and
2628 "FooPort 0" in the same configuration domain. (It's still okay
2629 to have a FooPort in your configuration file, and use "FooPort 0"
2630 on the command line to disable it.) Fixes the second half of bug
2631 6507; bugfix on 0.2.3.3-alpha.
2632 - Make wildcarded addresses (that is, ones beginning with "*.") work
2633 when provided via the controller's MapAddress command. Previously,
2634 they were accepted, but we never actually noticed that they were
2635 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
2636 - Avoid crashing on a malformed state file where EntryGuardPathBias
2637 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
2638 - Add a (probably redundant) memory clear between iterations of
2639 the router status voting loop, to prevent future coding errors
2640 where data might leak between iterations of the loop. Resolves
2643 o Minor bugfixes (log messages):
2644 - Downgrade "set buildtimeout to low value" messages to "info"
2645 severity; they were never an actual problem, there was never
2646 anything reasonable to do about them, and they tended to spam logs
2647 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
2648 - Downgrade path-bias warning messages to "info". We'll try to get
2649 them working better in 0.2.4. Add internal circuit construction
2650 state to protect against the noisy warn message "Unexpectedly high
2651 circuit_successes". Also add some additional rate-limited notice
2652 messages to help determine the root cause of the warn. Fixes bug
2653 6475. Bugfix against 0.2.3.17-beta.
2654 - Move log message when unable to find a microdesc in a routerstatus
2655 entry to parse time. Previously we'd spam this warning every time
2656 we tried to figure out which microdescriptors to download. Fixes
2657 the third piece of bug 6404; fix on 0.2.3.18-rc.
2660 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
2661 change when the authority is deciding whether to accept a newly
2662 uploaded descriptor. Implements ticket 6423.
2663 - Add missing documentation for consensus and microdesc files.
2664 Resolves ticket 6732.
2667 Changes in version 0.2.2.38 - 2012-08-12
2668 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
2669 attack that could in theory leak path information.
2672 - Avoid an uninitialized memory read when reading a vote or consensus
2673 document that has an unrecognized flavor name. This read could
2674 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2675 - Try to leak less information about what relays a client is
2676 choosing to a side-channel attacker. Previously, a Tor client would
2677 stop iterating through the list of available relays as soon as it
2678 had chosen one, thus finishing a little earlier when it picked
2679 a router earlier in the list. If an attacker can recover this
2680 timing information (nontrivial but not proven to be impossible),
2681 they could learn some coarse-grained information about which relays
2682 a client was picking (middle nodes in particular are likelier to
2683 be affected than exits). The timing attack might be mitigated by
2684 other factors (see bug 6537 for some discussion), but it's best
2685 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2688 Changes in version 0.2.3.20-rc - 2012-08-05
2689 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
2690 series. It fixes a pair of code security bugs and a potential anonymity
2691 issue, updates our RPM spec files, and cleans up other smaller issues.
2694 - Avoid read-from-freed-memory and double-free bugs that could occur
2695 when a DNS request fails while launching it. Fixes bug 6480;
2696 bugfix on 0.2.0.1-alpha.
2697 - Avoid an uninitialized memory read when reading a vote or consensus
2698 document that has an unrecognized flavor name. This read could
2699 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2700 - Try to leak less information about what relays a client is
2701 choosing to a side-channel attacker. Previously, a Tor client would
2702 stop iterating through the list of available relays as soon as it
2703 had chosen one, thus finishing a little earlier when it picked
2704 a router earlier in the list. If an attacker can recover this
2705 timing information (nontrivial but not proven to be impossible),
2706 they could learn some coarse-grained information about which relays
2707 a client was picking (middle nodes in particular are likelier to
2708 be affected than exits). The timing attack might be mitigated by
2709 other factors (see bug 6537 for some discussion), but it's best
2710 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2713 - Try to make the warning when giving an obsolete SOCKSListenAddress
2714 a little more useful.
2715 - Terminate active server managed proxies if Tor stops being a
2716 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
2717 - Provide a better error message about possible OSX Asciidoc failure
2718 reasons. Fixes bug 6436.
2719 - Warn when Tor is configured to use accounting in a way that can
2720 link a hidden service to some other hidden service or public
2721 address. Resolves ticket 6490.
2724 - Check return value of fputs() when writing authority certificate
2725 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
2726 - Ignore ServerTransportPlugin lines when Tor is not configured as
2727 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
2728 - When disabling guards for having too high a proportion of failed
2729 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
2733 - Update our default RPM spec files to work with mock and rpmbuild
2734 on RHEL/Fedora. They have an updated set of dependencies and
2735 conflicts, a fix for an ancient typo when creating the "_tor"
2736 user, and better instructions. Thanks to Ondrej Mikle for the
2737 patch series. Fixes bug 6043.
2740 - Make it possible to set the TestingTorNetwork configuration
2741 option using AlternateDirAuthority and AlternateBridgeAuthority
2742 as an alternative to setting DirServer. Addresses ticket 6377.
2745 - Clarify the documentation for the Alternate*Authority options.
2747 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
2749 o Code simplification and refactoring:
2750 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
2751 10 lines. Also, don't nest them. Doing so in the past has
2752 led to hard-to-debug code. The new style is to use the
2753 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
2756 Changes in version 0.2.3.19-rc - 2012-07-06
2757 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
2758 series. It fixes the compile on Windows, reverts to a GeoIP database
2759 that isn't as broken, and fixes a flow control bug that has been around
2760 since the beginning of Tor.
2763 - Fix a bug handling SENDME cells on nonexistent streams that could
2764 result in bizarre window values. Report and patch contributed
2765 pseudonymously. Fixes part of bug 6271. This bug was introduced
2766 before the first Tor release, in svn commit r152.
2767 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
2768 June 2012 database, Maxmind marked many Tor relays as country "A1",
2769 which will cause risky behavior for clients that set EntryNodes
2770 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
2771 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
2772 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
2775 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
2776 bugfix on 0.2.1.10-alpha.
2779 Changes in version 0.2.3.18-rc - 2012-06-28
2780 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
2781 series. It fixes a few smaller bugs, but generally appears stable.
2782 Please test it and let us know whether it is!
2785 - Allow wildcarded mapaddress targets to be specified on the
2786 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
2787 - Make our linker option detection code more robust against linkers
2788 such as on FreeBSD 8, where a bad combination of options completes
2789 successfully but makes an unrunnable binary. Fixes bug 6173;
2790 bugfix on 0.2.3.17-beta.
2792 o Minor bugfixes (on 0.2.2.x and earlier):
2793 - Avoid a false positive in the util/threads unit test by increasing
2794 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
2795 - Replace "Sending publish request" log messages with "Launching
2796 upload", so that they no longer confusingly imply that we're
2797 sending something to a directory we might not even be connected
2798 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
2799 - Make sure to set *socket_error in all error cases in
2800 connection_connect(), so it can't produce a warning about
2801 errno being zero from errno_to_orconn_end_reason(). Bugfix on
2802 0.2.1.1-alpha; resolves ticket 6028.
2803 - Downgrade "Got a certificate, but we already have it" log messages
2804 from warning to info, except when we're a dirauth. Fixes bug 5238;
2805 bugfix on 0.2.1.7-alpha.
2806 - When checking for requested signatures on the latest consensus
2807 before serving it to a client, make sure to check the right
2808 consensus flavor. Bugfix on 0.2.2.6-alpha.
2809 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
2810 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
2812 o Minor bugfixes (on 0.2.3.x):
2813 - Make format_helper_exit_status() avoid unnecessary space padding
2814 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
2816 - Downgrade a message about cleaning the microdescriptor cache to
2817 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
2818 - Log a BUG message at severity INFO if we have a networkstatus with
2819 a missing entry for some microdescriptor. Continues on a patch
2821 - Improve the log message when a managed proxy fails to launch. Fixes
2822 bug 5099; bugfix on 0.2.3.6-alpha.
2823 - Don't do DNS lookups when parsing corrupted managed proxy protocol
2824 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
2825 - When formatting wildcarded address mappings for the controller,
2826 be sure to include "*." as appropriate. Partially fixes bug 6244;
2827 bugfix on 0.2.3.9-alpha.
2828 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
2829 Bugfix on 0.2.3.13-alpha.
2830 - Stop logging messages about running with circuit timeout learning
2831 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
2832 - Disable a spurious warning about reading on a marked and flushing
2833 connection. We shouldn't be doing that, but apparently we
2834 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
2835 - Fix a bug that stopped AllowDotExit from working on addresses
2836 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
2839 o Code simplification, refactoring, unit tests:
2840 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
2841 Libevent's notion of cached time when possible.
2842 - Remove duplicate code for invoking getrlimit() from control.c.
2843 - Add a unit test for the environment_variable_names_equal function.
2846 - Document the --defaults-torrc option, and the new (in 0.2.3)
2847 semantics for overriding, extending, and clearing lists of
2848 options. Closes bug 4748.
2851 Changes in version 0.2.3.17-beta - 2012-06-15
2852 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
2853 gets our TLS handshake back on track for being able to blend in with
2854 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
2855 with Vidalia, and otherwise continues to get us closer to a release
2859 - Enable gcc and ld hardening by default. Resolves ticket 5210.
2860 - Update TLS cipher list to match Firefox 8 and later. Resolves
2862 - Implement the client side of proposal 198: remove support for
2863 clients falsely claiming to support standard ciphersuites that
2864 they can actually provide. As of modern OpenSSL versions, it's not
2865 necessary to fake any standard ciphersuite, and doing so prevents
2866 us from using better ciphersuites in the future, since servers
2867 can't know whether an advertised ciphersuite is really supported or
2868 not. Some hosts -- notably, ones with very old versions of OpenSSL
2869 or where OpenSSL has been built with ECC disabled -- will stand
2870 out because of this change; TBB users should not be affected.
2873 - Change the default value for DynamicDHGroups (introduced in
2874 0.2.3.9-alpha) to 0. This feature can make Tor relays less
2875 identifiable by their use of the mod_ssl DH group, but at
2876 the cost of some usability (#4721) and bridge tracing (#6087)
2877 regressions. Resolves ticket 5598.
2878 - Send a CRLF at the end of each STATUS_* control protocol event. This
2879 bug tickled a bug in Vidalia which would make it freeze. Fixes
2880 bug 6094; bugfix on 0.2.3.16-alpha.
2883 - Disable writing on marked-for-close connections when they are
2884 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
2885 bug 5263; bugfix on 0.0.2pre13, where we first added a special
2886 case for flushing marked connections.
2887 - Detect SSL handshake even when the initial attempt to write the
2888 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
2889 - Change the AllowDotExit rules so they should actually work.
2890 We now enforce AllowDotExit only immediately after receiving an
2891 address via SOCKS or DNSPort: other sources are free to provide
2892 .exit addresses after the resolution occurs. Fixes bug 3940;
2893 bugfix on 0.2.2.1-alpha.
2894 - Fix a (harmless) integer overflow in cell statistics reported by
2895 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2896 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
2897 right places and never depends on the consensus parameters or
2898 computes adaptive timeouts when it is disabled. Fixes bug 5049;
2899 bugfix on 0.2.2.14-alpha.
2900 - When building Tor on Windows with -DUNICODE (not default), ensure
2901 that error messages, filenames, and DNS server names are always
2902 NUL-terminated when we convert them to a single-byte encoding.
2903 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2904 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
2905 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
2906 - Fix an edge case where TestingTorNetwork is set but the authorities
2907 and relays all have an uptime of zero, where the private Tor network
2908 could briefly lack support for hidden services. Fixes bug 3886;
2909 bugfix on 0.2.2.18-alpha.
2910 - Correct the manpage's descriptions for the default values of
2911 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
2913 - Fix the documentation for the --hush and --quiet command line
2914 options, which changed their behavior back in 0.2.3.3-alpha.
2915 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
2919 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2920 more information to it, so that we can track it down in case it
2921 returns again. Mitigates bug 5235.
2922 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2923 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2924 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2925 - Warn the user when HTTPProxy, but no other proxy type, is
2926 configured. This can cause surprising behavior: it doesn't send
2927 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2928 directory traffic only. Resolves ticket 4663.
2929 - Issue a notice if a guard completes less than 40% of your circuits.
2930 Threshold is configurable by torrc option PathBiasNoticeRate and
2931 consensus parameter pb_noticepct. There is additional, off-by-
2932 default code to disable guards which fail too many circuits.
2933 Addresses ticket 5458.
2934 - Update to the June 6 2012 Maxmind GeoLite Country database.
2936 o Code simplifications and refactoring:
2937 - Remove validate_pluggable_transports_config(): its warning
2938 message is now handled by connection_or_connect().
2941 Changes in version 0.2.2.37 - 2012-06-06
2942 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2943 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2947 - Work around a bug in OpenSSL that broke renegotiation with TLS
2948 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2949 the v2 Tor connection protocol when both sides were using OpenSSL
2950 1.0.1 would fail. Resolves ticket 6033.
2951 - When waiting for a client to renegotiate, don't allow it to add
2952 any bytes to the input buffer. This fixes a potential DoS issue.
2953 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2954 - Fix an edge case where if we fetch or publish a hidden service
2955 descriptor, we might build a 4-hop circuit and then use that circuit
2956 for exiting afterwards -- even if the new last hop doesn't obey our
2957 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2960 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2961 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2964 - Tell GCC and Clang to check for any errors in format strings passed
2965 to the tor_v*(print|scan)f functions.
2968 Changes in version 0.2.3.16-alpha - 2012-06-05
2969 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
2970 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2971 currently). It also fixes a variety of smaller bugs and other cleanups
2972 that get us closer to a release candidate.
2974 o Major bugfixes (general):
2975 - Work around a bug in OpenSSL that broke renegotiation with TLS
2976 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2977 the v2 Tor connection protocol when both sides were using OpenSSL
2978 1.0.1 would fail. Resolves ticket 6033.
2979 - When waiting for a client to renegotiate, don't allow it to add
2980 any bytes to the input buffer. This fixes a potential DoS issue.
2981 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2982 - Pass correct OR address to managed proxies (like obfsproxy),
2983 even when ORListenAddress is used. Fixes bug 4865; bugfix on
2985 - The advertised platform of a router now includes only its operating
2986 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
2987 service pack level (for Windows) or its CPU architecture (for Unix).
2988 We also no longer include the "git-XYZ" tag in the version. Resolves
2991 o Major bugfixes (clients):
2992 - If we are unable to find any exit that supports our predicted ports,
2993 stop calling them predicted, so that we don't loop and build
2994 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2995 which introduced predicted ports.
2996 - Fix an edge case where if we fetch or publish a hidden service
2997 descriptor, we might build a 4-hop circuit and then use that circuit
2998 for exiting afterwards -- even if the new last hop doesn't obey our
2999 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3000 - Check at each new consensus whether our entry guards were picked
3001 long enough ago that we should rotate them. Previously, we only
3002 did this check at startup, which could lead to us holding a guard
3003 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
3004 - When fetching a bridge descriptor from a bridge authority,
3005 always do so anonymously, whether we have been able to open
3006 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
3007 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
3008 but we'll need to wait for bug 6010 before it's actually usable.
3010 o Major bugfixes (directory authorities):
3011 - When computing weight parameters, behave more robustly in the
3012 presence of a bad bwweightscale value. Previously, the authorities
3013 would crash if they agreed on a sufficiently broken weight_scale
3014 value: now, they use a reasonable default and carry on. Partial
3015 fix for 5786; bugfix on 0.2.2.17-alpha.
3016 - Check more thoroughly to prevent a rogue authority from
3017 double-voting on any consensus directory parameter. Previously,
3018 authorities would crash in this case if the total number of
3019 votes for any parameter exceeded the number of active voters,
3020 but would let it pass otherwise. Partial fix for bug 5786; bugfix
3024 - Rate-limit log messages when asked to connect anonymously to
3025 a private address. When these hit, they tended to hit fast and
3026 often. Also, don't bother trying to connect to addresses that we
3027 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
3028 reply makes us think we have been lied to, even when the address the
3029 client tried to connect to was "localhost." Resolves ticket 2822.
3030 - Allow packagers to insert an extra string in server descriptor
3031 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
3032 Resolves the rest of ticket 2988.
3033 - Raise the threshold of server descriptors needed (75%) and exit
3034 server descriptors needed (50%) before we will declare ourselves
3035 bootstrapped. This will make clients start building circuits a
3036 little later, but makes the initially constructed circuits less
3037 skewed and less in conflict with further directory fetches. Fixes
3039 - Close any connection that sends unrecognized junk before the
3040 handshake. Solves an issue noted in bug 4369.
3041 - Improve log messages about managed transports. Resolves ticket 5070.
3042 - Tag a bridge's descriptor as "never to be sent unencrypted".
3043 This shouldn't matter, since bridges don't open non-anonymous
3044 connections to the bridge authority and don't allow unencrypted
3045 directory connections from clients, but we might as well make
3046 sure. Closes bug 5139.
3047 - Expose our view of whether we have gone dormant to the controller,
3048 via a new "GETINFO dormant" value. Torbutton and other controllers
3049 can use this to avoid doing periodic requests through Tor while
3050 it's dormant (bug 4718). Fixes bug 5954.
3051 - Tell GCC and Clang to check for any errors in format strings passed
3052 to the tor_v*(print|scan)f functions.
3053 - Update to the May 1 2012 Maxmind GeoLite Country database.
3055 o Minor bugfixes (already included in 0.2.2.36):
3056 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
3057 Fixes bug 5346; bugfix on 0.0.8pre3.
3058 - Correct parsing of certain date types in parse_http_time().
3059 Without this patch, If-Modified-Since would behave
3060 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
3061 Esteban Manchado Velázques.
3062 - Make our number-parsing functions always treat too-large values
3063 as an error, even when those values exceed the width of the
3064 underlying type. Previously, if the caller provided these
3065 functions with minima or maxima set to the extreme values of the
3066 underlying integer type, these functions would return those
3067 values on overflow rather than treating overflow as an error.
3068 Fixes part of bug 5786; bugfix on 0.0.9.
3069 - If we hit the error case where routerlist_insert() replaces an
3070 existing (old) server descriptor, make sure to remove that
3071 server descriptor from the old_routers list. Fix related to bug
3072 1776. Bugfix on 0.2.2.18-alpha.
3073 - Clarify the behavior of MaxCircuitDirtiness with hidden service
3074 circuits. Fixes issue 5259.
3076 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
3077 - Prevent a null-pointer dereference when receiving a data cell
3078 for a nonexistent stream when the circuit in question has an
3079 empty deliver window. We don't believe this is triggerable,
3080 since we don't currently allow deliver windows to become empty,
3081 but the logic is tricky enough that it's better to make the code
3082 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
3083 - Fix a memory leak when trying to launch a DNS request when the
3084 network is disabled or the nameservers are unconfigurable. Fixes
3085 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
3086 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
3087 - Don't hold a Windows file handle open for every file mapping;
3088 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
3090 - Avoid O(n^2) performance characteristics when parsing a large
3091 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
3092 - Format more doubles with %f, not %lf. Patch from grarpamp to make
3093 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
3095 - Make our replacement implementation of strtok_r() compatible with
3096 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
3097 bugfix on 0.2.2.1-alpha.
3098 - Fix a NULL-pointer dereference on a badly formed
3099 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
3100 bugfix on 0.2.2.9-alpha.
3101 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
3102 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
3103 - Defensively refactor rend_mid_rendezvous() so that protocol
3104 violations and length checks happen in the beginning. Fixes
3106 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
3107 that IPv6 stuff will compile on MSVC, and compilation issues
3108 will be easier to track down. Fixes bug 5861.
3110 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
3111 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
3112 resource exhaustion, so that clients can adjust their load to
3113 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
3114 started using END_STREAM_REASON_RESOURCELIMIT.
3115 - Don't check for whether the address we're using for outbound
3116 connections has changed until after the outbound connection has
3117 completed. On Windows, getsockname() doesn't succeed until the
3118 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
3119 - If the configuration tries to set MyFamily on a bridge, refuse to
3120 do so, and warn about the security implications. Fixes bug 4657;
3121 bugfix on 0.2.0.3-alpha.
3122 - If the client fails to set a reasonable set of ciphersuites
3123 during its v2 handshake renegotiation, allow the renegotiation to
3124 continue nevertheless (i.e. send all the required certificates).
3125 Fixes bug 4591; bugfix on 0.2.0.20-rc.
3126 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
3127 option is set to 0 (which Vidalia version 0.2.16 now does when
3128 a SAVECONF attempt fails), perform other actions that SIGHUP
3129 usually causes (like reopening the logs). Fixes bug 5095; bugfix
3131 - If we fail to write a microdescriptor to the disk cache, do not
3132 continue replacing the old microdescriptor file. Fixes bug 2954;
3133 bugfix on 0.2.2.6-alpha.
3134 - Exit nodes don't need to fetch certificates for authorities that
3135 they don't recognize; only directory authorities, bridges,
3136 and caches need to do that. Fixes part of bug 2297; bugfix on
3138 - Correctly handle checking the permissions on the parent
3139 directory of a control socket in the root directory. Bug found
3140 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
3142 - When told to add a bridge with the same digest as a preexisting
3143 bridge but a different addr:port, change the addr:port as
3144 requested. Previously we would not notice the change. Fixes half
3145 of bug 5603; fix on 0.2.2.26-beta.
3146 - End AUTHCHALLENGE error messages (in the control protocol) with
3147 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
3149 o Minor bugfixes (on 0.2.3.x):
3150 - Turn an assertion (that the number of handshakes received as a
3151 server is not < 1) into a warning. Fixes bug 4873; bugfix on
3153 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
3154 we had reversed them when the answer was cached.) Fixes bug
3155 5723; bugfix on 0.2.3.1-alpha.
3156 - Work correctly on Linux systems with accept4 support advertised in
3157 their headers, but without accept4 support in the kernel. Fix
3158 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
3159 - When told to add a bridge with the same addr:port as a preexisting
3160 bridge but a different transport, change the transport as
3161 requested. Previously we would not notice the change. Fixes half
3162 of bug 5603; fix on 0.2.3.2-alpha.
3163 - Avoid a "double-reply" warning when replying to a SOCKS request
3164 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
3165 bugfix on 0.2.3.4-alpha.
3166 - Fix a bug where a bridge authority crashes if it has seen no
3167 directory requests when it's time to write statistics to disk.
3168 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
3170 - Don't try to open non-control listeners when DisableNetwork is set.
3171 Previously, we'd open all listeners, then immediately close them.
3172 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
3173 - Don't abort the managed proxy protocol if the managed proxy
3174 sends us an unrecognized line; ignore it instead. Fixes bug
3175 5910; bugfix on 0.2.3.9-alpha.
3176 - Fix a compile warning in crypto.c when compiling with clang 3.1.
3177 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
3178 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
3179 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
3180 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
3181 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
3182 - Resolve numerous small warnings and build issues with MSVC. Resolves
3185 o Documentation fixes:
3186 - Improve the manual's documentation for the NT Service command-line
3187 options. Addresses ticket 3964.
3188 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
3189 - Document the changes to the ORPort and DirPort options, and the
3190 fact that {OR/Dir}ListenAddress is now unnecessary (and
3191 therefore deprecated). Resolves ticket 5597.
3194 - Remove the torrc.bridge file: we don't use it for anything, and
3195 it had become badly desynchronized from torrc.sample. Resolves
3199 Changes in version 0.2.2.36 - 2012-05-24
3200 Tor 0.2.2.36 updates the addresses for two of the eight directory
3201 authorities, fixes some potential anonymity and security issues,
3202 and fixes several crash bugs.
3204 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
3205 known flaws, and nobody should be using them. You should upgrade. If
3206 you're using a Linux or BSD and its packages are obsolete, stop using
3207 those packages and upgrade anyway.
3209 o Directory authority changes:
3210 - Change IP address for maatuska (v3 directory authority).
3211 - Change IP address for ides (v3 directory authority), and rename
3215 - When building or running with any version of OpenSSL earlier
3216 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
3217 versions have a bug (CVE-2011-4576) in which their block cipher
3218 padding includes uninitialized data, potentially leaking sensitive
3219 information to any peer with whom they make a SSLv3 connection. Tor
3220 does not use SSL v3 by default, but a hostile client or server
3221 could force an SSLv3 connection in order to gain information that
3222 they shouldn't have been able to get. The best solution here is to
3223 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
3224 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
3225 to make sure that the bug can't happen.
3226 - Never use a bridge or a controller-supplied node as an exit, even
3227 if its exit policy allows it. Found by wanoskarnet. Fixes bug
3228 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
3229 and 0.2.0.3-alpha (for bridge-purpose descriptors).
3230 - Only build circuits if we have a sufficient threshold of the total
3231 descriptors that are marked in the consensus with the "Exit"
3232 flag. This mitigates an attack proposed by wanoskarnet, in which
3233 all of a client's bridges collude to restrict the exit nodes that
3234 the client knows about. Fixes bug 5343.
3235 - Provide controllers with a safer way to implement the cookie
3236 authentication mechanism. With the old method, if another locally
3237 running program could convince a controller that it was the Tor
3238 process, then that program could trick the controller into telling
3239 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
3240 authentication method uses a challenge-response approach to prevent
3241 this attack. Fixes bug 5185; implements proposal 193.
3244 - Avoid logging uninitialized data when unable to decode a hidden
3245 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
3246 - Avoid a client-side assertion failure when receiving an INTRODUCE2
3247 cell on a general purpose circuit. Fixes bug 5644; bugfix on
3249 - Fix builds when the path to sed, openssl, or sha1sum contains
3250 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3252 - Correct our replacements for the timeradd() and timersub() functions
3253 on platforms that lack them (for example, Windows). The timersub()
3254 function is used when expiring circuits, while timeradd() is
3255 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
3256 bugfix on 0.2.2.24-alpha.
3257 - Fix the SOCKET_OK test that we use to tell when socket
3258 creation fails so that it works on Win64. Fixes part of bug 4533;
3259 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
3262 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
3263 Fixes bug 5346; bugfix on 0.0.8pre3.
3264 - Make our number-parsing functions always treat too-large values
3265 as an error, even when those values exceed the width of the
3266 underlying type. Previously, if the caller provided these
3267 functions with minima or maxima set to the extreme values of the
3268 underlying integer type, these functions would return those
3269 values on overflow rather than treating overflow as an error.
3270 Fixes part of bug 5786; bugfix on 0.0.9.
3271 - Older Linux kernels erroneously respond to strange nmap behavior
3272 by having accept() return successfully with a zero-length
3273 socket. When this happens, just close the connection. Previously,
3274 we would try harder to learn the remote address: but there was
3275 no such remote address to learn, and our method for trying to
3276 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3277 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3278 - Correct parsing of certain date types in parse_http_time().
3279 Without this patch, If-Modified-Since would behave
3280 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
3281 Esteban Manchado Velázques.
3282 - Change the BridgePassword feature (part of the "bridge community"
3283 design, which is not yet implemented) to use a time-independent
3284 comparison. The old behavior might have allowed an adversary
3285 to use timing to guess the BridgePassword value. Fixes bug 5543;
3286 bugfix on 0.2.0.14-alpha.
3287 - Detect and reject certain misformed escape sequences in
3288 configuration values. Previously, these values would cause us
3289 to crash if received in a torrc file or over an authenticated
3290 control port. Bug found by Esteban Manchado Velázquez, and
3291 independently by Robert Connolly from Matta Consulting who further
3292 noted that it allows a post-authentication heap overflow. Patch
3293 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3294 bugfix on 0.2.0.16-alpha.
3295 - Fix a compile warning when using the --enable-openbsd-malloc
3296 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3297 - During configure, detect when we're building with clang version
3298 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3299 CFLAGS. clang doesn't support them yet.
3300 - When sending an HTTP/1.1 proxy request, include a Host header.
3301 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
3302 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
3303 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
3304 - If we hit the error case where routerlist_insert() replaces an
3305 existing (old) server descriptor, make sure to remove that
3306 server descriptor from the old_routers list. Fix related to bug
3307 1776. Bugfix on 0.2.2.18-alpha.
3309 o Minor bugfixes (documentation and log messages):
3310 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3311 Fixes bug 4856; bugfix on Tor 0.0.6.
3312 - Update "ClientOnly" man page entry to explain that there isn't
3313 really any point to messing with it. Resolves ticket 5005.
3314 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3315 directory authority option (introduced in Tor 0.2.2.34).
3316 - Downgrade the "We're missing a certificate" message from notice
3317 to info: people kept mistaking it for a real problem, whereas it
3318 is seldom the problem even when we are failing to bootstrap. Fixes
3319 bug 5067; bugfix on 0.2.0.10-alpha.
3320 - Correctly spell "connect" in a log message on failure to create a
3321 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
3322 - Clarify the behavior of MaxCircuitDirtiness with hidden service
3323 circuits. Fixes issue 5259.
3326 - Directory authorities now reject versions of Tor older than
3327 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3328 inclusive. These versions accounted for only a small fraction of
3329 the Tor network, and have numerous known security issues. Resolves
3331 - Update to the May 1 2012 Maxmind GeoLite Country database.
3334 - When sending or relaying a RELAY_EARLY cell, we used to convert
3335 it to a RELAY cell if the connection was using the v1 link
3336 protocol. This was a workaround for older versions of Tor, which
3337 didn't handle RELAY_EARLY cells properly. Now that all supported
3338 versions can handle RELAY_EARLY cells, and now that we're enforcing
3339 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3340 remove this workaround. Addresses bug 4786.
3343 Changes in version 0.2.3.15-alpha - 2012-04-30
3344 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
3345 the development branch build on Windows again.
3347 o Minor bugfixes (on 0.2.2.x and earlier):
3348 - Make sure that there are no unhandled pending TLS errors before
3349 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
3350 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
3351 Bugfix on 0.1.0.5-rc; fixes bug 4528.
3352 - Fix an assert that directory authorities could trigger on sighup
3353 during some configuration state transitions. We now don't treat
3354 it as a fatal error when the new descriptor we just generated in
3355 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
3356 - After we pick a directory mirror, we would refuse to use it if
3357 it's in our ExcludeExitNodes list, resulting in mysterious failures
3358 to bootstrap for people who just wanted to avoid exiting from
3359 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
3360 - When building with --enable-static-tor on OpenBSD, do not
3361 erroneously attempt to link -lrt. Fixes bug 5103.
3363 o Minor bugfixes (on 0.2.3.x):
3364 - When Tor is built with kernel headers from a recent (last few
3365 years) Linux kernel, do not fail to run on older (pre-2.6.28
3366 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
3367 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
3369 - Fix compilation with miniupnpc version 1.6; patch from
3370 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
3371 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
3372 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
3373 - Fix compilation on platforms without unistd.h, or where environ
3374 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
3377 - Directory authorities are now a little more lenient at accepting
3378 older router descriptors, or newer router descriptors that don't
3379 make big changes. This should help ameliorate past and future
3380 issues where routers think they have uploaded valid descriptors,
3381 but the authorities don't think so. Fix for ticket 2479.
3382 - Make the code that clients use to detect an address change be
3383 IPv6-aware, so that it won't fill clients' logs with error
3384 messages when trying to get the IPv4 address of an IPv6
3385 connection. Implements ticket 5537.
3388 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
3389 authorities needed to use it for a while to keep the network working
3390 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
3391 that was six months ago. As of now, it should no longer be needed
3395 Changes in version 0.2.3.14-alpha - 2012-04-23
3396 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
3397 candidate. It also dramatically speeds up AES: fast relays should
3398 consider switching to the newer OpenSSL library.
3400 o Directory authority changes:
3401 - Change IP address for ides (v3 directory authority), and rename
3405 - Avoid logging uninitialized data when unable to decode a hidden
3406 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
3407 - Avoid a client-side assertion failure when receiving an INTRODUCE2
3408 cell on a general purpose circuit. Fixes bug 5644; bugfix on
3410 - If authorities are unable to get a v2 consensus document from other
3411 directory authorities, they no longer fall back to fetching
3412 them from regular directory caches. Fixes bug 5635; bugfix on
3413 0.2.2.26-beta, where routers stopped downloading v2 consensus
3415 - When we start a Tor client with a normal consensus already cached,
3416 be willing to download a microdescriptor consensus. Fixes bug 4011;
3417 fix on 0.2.3.1-alpha.
3419 o Major features (performance):
3420 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
3421 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
3422 vectorized AES implementations as appropriate. These can be much,
3423 much faster than other AES implementations.
3425 o Minor bugfixes (0.2.2.x and earlier):
3426 - Don't launch more than 10 service-side introduction-point circuits
3427 for a hidden service in five minutes. Previously, we would consider
3428 launching more introduction-point circuits if at least one second
3429 had passed without any introduction-point circuits failing. Fixes
3430 bug 4607; bugfix on 0.0.7pre1.
3431 - Change the BridgePassword feature (part of the "bridge community"
3432 design, which is not yet implemented) to use a time-independent
3433 comparison. The old behavior might have allowed an adversary
3434 to use timing to guess the BridgePassword value. Fixes bug 5543;
3435 bugfix on 0.2.0.14-alpha.
3436 - Enforce correct return behavior of tor_vsscanf() when the '%%'
3437 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
3438 - When sending an HTTP/1.1 proxy request, include a Host header.
3439 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
3440 - Don't log that we have "decided to publish new relay descriptor"
3441 unless we are actually publishing a descriptor. Fixes bug 3942;
3442 bugfix on 0.2.2.28-beta.
3444 o Minor bugfixes (0.2.3.x):
3445 - Fix a bug where a bridge authority crashes (on a failed assert)
3446 if it has seen no directory requests when it's time to write
3447 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
3448 - Fix bug stomping on ORPort option NoListen and ignoring option
3449 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
3450 - In the testsuite, provide a large enough buffer in the tor_sscanf
3451 unit test. Otherwise we'd overrun that buffer and crash during
3452 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
3454 - Make sure we create the keys directory if it doesn't exist and we're
3455 about to store the dynamic Diffie-Hellman parameters. Fixes bug
3456 5572; bugfix on 0.2.3.13-alpha.
3457 - Fix a small memory leak when trying to decode incorrect base16
3458 authenticator during SAFECOOKIE authentication. Found by
3459 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
3462 - Add more information to a log statement that might help track down
3463 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
3464 non-IP address" messages (or any Bug messages, for that matter!),
3465 please let us know about it.
3466 - Relays now understand an IPv6 address when they get one from a
3467 directory server. Resolves ticket 4875.
3468 - Resolve IPv6 addresses in bridge and entry statistics to country
3469 code "??" which means we at least count them. Resolves ticket 5053;
3470 improves on 0.2.3.9-alpha.
3471 - Update to the April 3 2012 Maxmind GeoLite Country database.
3472 - Begin a doc/state-contents.txt file to explain the contents of
3473 the Tor state file. Fixes bug 2987.
3475 o Default torrc changes:
3476 - Stop listing "socksport 9050" in torrc.sample. We open a socks
3477 port on 9050 by default anyway, so this should not change anything
3479 - Stop mentioning the deprecated *ListenAddress options in
3480 torrc.sample. Fixes bug 5438.
3481 - Document unit of bandwidth related options in sample torrc.
3485 - The "torify" script no longer supports the "tsocks" socksifier
3486 tool, since tsocks doesn't support DNS and UDP right for Tor.
3487 Everyone should be using torsocks instead. Fixes bugs 3530 and
3488 5180. Based on a patch by "ugh".
3491 - Change the symmetric cipher interface so that creating and
3492 initializing a stream cipher are no longer separate functions.
3493 - Remove all internal support for unpadded RSA. We never used it, and
3494 it would be a bad idea to start.
3497 Changes in version 0.2.3.13-alpha - 2012-03-26
3498 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
3499 in managed pluggable transports, as well as providing other cleanups
3500 that get us closer to a release candidate.
3502 o Directory authority changes:
3503 - Change IP address for maatuska (v3 directory authority).
3506 - Provide controllers with a safer way to implement the cookie
3507 authentication mechanism. With the old method, if another locally
3508 running program could convince a controller that it was the Tor
3509 process, then that program could trick the controller into telling
3510 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
3511 authentication method uses a challenge-response approach to prevent
3512 this attack. Fixes bug 5185, implements proposal 193.
3513 - Never use a bridge or a controller-supplied node as an exit, even
3514 if its exit policy allows it. Found by wanoskarnet. Fixes bug
3515 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
3516 and 0.2.0.3-alpha (for bridge-purpose descriptors).
3517 - Only build circuits if we have a sufficient threshold of the total
3518 descriptors that are marked in the consensus with the "Exit"
3519 flag. This mitigates an attack proposed by wanoskarnet, in which
3520 all of a client's bridges collude to restrict the exit nodes that
3521 the client knows about. Fixes bug 5343.
3523 o Major bugfixes (on Tor 0.2.3.x):
3524 - Avoid an assert when managed proxies like obfsproxy are configured,
3525 and we receive HUP signals or setconf attempts too rapidly. This
3526 situation happens most commonly when Vidalia tries to attach to
3527 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
3528 bugfix on 0.2.3.6-alpha.
3529 - Fix a relay-side pluggable transports bug where managed proxies were
3530 unreachable from the Internet, because Tor asked them to bind on
3531 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
3532 - Stop discarding command-line arguments when TestingTorNetwork
3533 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
3534 0.2.3.9-alpha, where task 4552 added support for two layers of
3536 - Resume allowing the unit tests to run in gdb. This was accidentally
3537 made impossible when the DisableDebuggerAttachment option was
3538 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
3539 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
3540 0.2.3.11-alpha. Reported by Anthony G. Basile.
3542 o Minor bugfixes (on 0.2.2.x and earlier):
3543 - Ensure we don't cannibalize circuits that are longer than three hops
3544 already, so we don't end up making circuits with 5 or more
3545 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
3546 0.1.0.1-rc which introduced cannibalization.
3547 - Detect and reject certain misformed escape sequences in
3548 configuration values. Previously, these values would cause us
3549 to crash if received in a torrc file or over an authenticated
3550 control port. Bug found by Esteban Manchado Velázquez, and
3551 independently by Robert Connolly from Matta Consulting who further
3552 noted that it allows a post-authentication heap overflow. Patch
3553 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3554 bugfix on 0.2.0.16-alpha.
3555 - Fix a compile warning when using the --enable-openbsd-malloc
3556 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3557 - Directory caches no longer refuse to clean out descriptors because
3558 of missing v2 networkstatus documents, unless they're configured
3559 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
3560 0.2.2.26-beta. Patch by Daniel Bryg.
3561 - Update to the latest version of the tinytest unit testing framework.
3562 This includes a couple of bugfixes that can be relevant for
3563 running forked unit tests on Windows, and removes all reserved
3566 o Minor bugfixes (on 0.2.3.x):
3567 - On a failed pipe() call, don't leak file descriptors. Fixes bug
3568 4296; bugfix on 0.2.3.1-alpha.
3569 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
3570 until after we have received a CERTS cell. Fixes bug 4361; bugfix
3571 on 0.2.3.6-alpha. Patch by "frosty".
3572 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
3573 option, so that the IP stack doesn't decide to use it for IPv4
3574 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
3575 - Ensure that variables set in Tor's environment cannot override
3576 environment variables that Tor passes to a managed
3577 pluggable-transport proxy. Previously, Tor would pass every
3578 variable in its environment to managed proxies along with the new
3579 ones, in such a way that on many operating systems, the inherited
3580 environment variables would override those which Tor tried to
3581 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
3582 bugfix on 0.2.3.9-alpha for Windows.
3585 - A wide variety of new unit tests by Esteban Manchado Velázquez.
3586 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
3587 - Update to the March 6 2012 Maxmind GeoLite Country database.
3590 Changes in version 0.2.3.12-alpha - 2012-02-13
3591 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
3592 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
3593 when Tor is configured to use a pluggable transport like obfsproxy.
3596 - Fix builds when the path to sed, openssl, or sha1sum contains
3597 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3599 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
3600 connections. This change should allow busy exit relays to stop
3601 running out of available sockets as quickly. Fixes bug 4950;
3602 bugfix on 0.2.2.26-beta.
3603 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
3604 would ask the bridge for microdescriptors, which are only supported
3605 in 0.2.3.x, and then fail to bootstrap when it didn't get the
3606 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
3607 - Properly set up obfsproxy's environment when in managed mode. The
3608 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
3609 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
3610 5076 and 5082; bugfix on 0.2.3.6-alpha.
3613 - Use the dead_strip option when building Tor on OS X. This reduces
3614 binary size by almost 19% when linking openssl and libevent
3615 statically, which we do for Tor Browser Bundle.
3616 - Fix broken URLs in the sample torrc file, and tell readers about
3617 the OutboundBindAddress, ExitPolicyRejectPrivate, and
3618 PublishServerDescriptor options. Addresses bug 4652.
3619 - Update to the February 7 2012 Maxmind GeoLite Country database.
3622 - Downgrade the "We're missing a certificate" message from notice
3623 to info: people kept mistaking it for a real problem, whereas it
3624 is seldom the problem even when we are failing to bootstrap. Fixes
3625 bug 5067; bugfix on 0.2.0.10-alpha.
3626 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
3627 managed pluggable transport server proxy's environment.
3628 Previously, we would put it there, even though Tor doesn't
3629 implement an 'extended server port' yet, and even though Tor
3630 almost certainly isn't listening at that address. For now, we set
3631 it to an empty string to avoid crashing older obfsproxies. Bugfix
3633 - Log the heartbeat message every HeartbeatPeriod seconds, not every
3634 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
3635 0.2.3.1-alpha. Bug reported by Scott Bennett.
3636 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
3637 bugfix on 0.2.3.11-alpha.
3638 - Update "ClientOnly" man page entry to explain that there isn't
3639 really any point to messing with it. Resolves ticket 5005.
3640 - Use the correct CVE number for CVE-2011-4576 in our comments and
3641 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
3644 o Code simplifications and refactoring:
3645 - Use the _WIN32 macro throughout our code to detect Windows.
3646 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
3650 Changes in version 0.2.3.11-alpha - 2012-01-22
3651 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
3652 the last step of the plan to limit maximum circuit length, includes
3653 a wide variety of hidden service performance and correctness fixes,
3654 works around an OpenSSL security flaw if your distro is too stubborn
3655 to upgrade, and fixes a bunch of smaller issues.
3658 - Now that Tor 0.2.0.x is completely deprecated, enable the final
3659 part of "Proposal 110: Avoiding infinite length circuits" by
3660 refusing all circuit-extend requests that do not use a relay_early
3661 cell. This change helps Tor resist a class of denial-of-service
3662 attacks by limiting the maximum circuit length.
3663 - Adjust the number of introduction points that a hidden service
3664 will try to maintain based on how long its introduction points
3665 remain in use and how many introductions they handle. Fixes
3667 - Try to use system facilities for enumerating local interface
3668 addresses, before falling back to our old approach (which was
3669 binding a UDP socket, and calling getsockname() on it). That
3670 approach was scaring OS X users whose draconian firewall
3671 software warned about binding to UDP sockets, regardless of
3672 whether packets were sent. Now we try to use getifaddrs(),
3673 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
3674 system supports. Resolves ticket 1827.
3676 o Major security workaround:
3677 - When building or running with any version of OpenSSL earlier
3678 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
3679 versions have a bug (CVE-2011-4576) in which their block cipher
3680 padding includes uninitialized data, potentially leaking sensitive
3681 information to any peer with whom they make a SSLv3 connection. Tor
3682 does not use SSL v3 by default, but a hostile client or server
3683 could force an SSLv3 connection in order to gain information that
3684 they shouldn't have been able to get. The best solution here is to
3685 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
3686 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
3687 to make sure that the bug can't happen.
3690 - Fix the SOCKET_OK test that we use to tell when socket
3691 creation fails so that it works on Win64. Fixes part of bug 4533;
3692 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
3693 - Correct our replacements for the timeradd() and timersub() functions
3694 on platforms that lack them (for example, Windows). The timersub()
3695 function is used when expiring circuits, while timeradd() is
3696 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
3697 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
3698 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
3699 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
3700 bug at runtime, not compile time, because some distributions hack
3701 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
3702 on 0.2.3.9-alpha. Found by Pascal.
3704 o Minor features (controller):
3705 - Use absolute path names when reporting the torrc filename in the
3706 control protocol, so a controller can more easily find the torrc
3707 file. Resolves bug 1101.
3708 - Extend the control protocol to report flags that control a circuit's
3709 path selection in CIRC events and in replies to 'GETINFO
3710 circuit-status'. Implements part of ticket 2411.
3711 - Extend the control protocol to report the hidden service address
3712 and current state of a hidden-service-related circuit in CIRC
3713 events and in replies to 'GETINFO circuit-status'. Implements part
3715 - When reporting the path to the cookie file to the controller,
3716 give an absolute path. Resolves ticket 4881.
3717 - Allow controllers to request an event notification whenever a
3718 circuit is cannibalized or its purpose is changed. Implements
3719 part of ticket 3457.
3720 - Include the creation time of a circuit in CIRC and CIRC2
3721 control-port events and the list produced by the 'GETINFO
3722 circuit-status' control-port command.
3724 o Minor features (directory authorities):
3725 - Directory authorities now reject versions of Tor older than
3726 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3727 inclusive. These versions accounted for only a small fraction of
3728 the Tor network, and have numerous known security issues. Resolves
3730 - Authority operators can now vote for all relays in a given
3731 set of countries to be BadDir/BadExit/Invalid/Rejected.
3732 - Provide two consensus parameters (FastFlagMinThreshold and
3733 FastFlagMaxThreshold) to control the range of allowable bandwidths
3734 for the Fast directory flag. These allow authorities to run
3735 experiments on appropriate requirements for being a "Fast" node.
3736 The AuthDirFastGuarantee config value still applies. Implements
3738 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3739 directory authority option (introduced in Tor 0.2.2.34).
3741 o Minor features (other):
3742 - Don't disable the DirPort when we cannot exceed our AccountingMax
3743 limit during this interval because the effective bandwidthrate is
3744 low enough. This is useful in a situation where AccountMax is only
3745 used as an additional safeguard or to provide statistics.
3746 - Prepend an informative header to generated dynamic_dh_params files.
3747 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
3748 EntryNodes will have no effect. Resolves issue 2571.
3749 - Log more useful messages when we fail to disable debugger
3751 - Log which authority we're missing votes from when we go to fetch
3752 them from the other auths.
3753 - Log (at debug level) whenever a circuit's purpose is changed.
3754 - Add missing documentation for the MaxClientCircuitsPending,
3755 UseMicrodescriptors, UserspaceIOCPBuffers, and
3756 _UseFilteringSSLBufferevents options, all introduced during
3758 - Update to the January 3 2012 Maxmind GeoLite Country database.
3760 o Minor bugfixes (hidden services):
3761 - Don't close hidden service client circuits which have almost
3762 finished connecting to their destination when they reach
3763 the normal circuit-build timeout. Previously, we would close
3764 introduction circuits which are waiting for an acknowledgement
3765 from the introduction point, and rendezvous circuits which have
3766 been specified in an INTRODUCE1 cell sent to a hidden service,
3767 after the normal CBT. Now, we mark them as 'timed out', and launch
3768 another rendezvous attempt in parallel. This behavior change can
3769 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
3770 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
3771 - Don't close hidden-service-side rendezvous circuits when they
3772 reach the normal circuit-build timeout. This behaviour change can
3773 be disabled using the new
3774 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
3775 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
3776 - Make sure we never mark the wrong rendezvous circuit as having
3777 had its introduction cell acknowleged by the introduction-point
3778 relay. Previously, when we received an INTRODUCE_ACK cell on a
3779 client-side hidden-service introduction circuit, we might have
3780 marked a rendezvous circuit other than the one we specified in
3781 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
3782 a warning message and interfered with the hidden service
3783 connection-establishment process. Fixes bug 4759; bugfix on
3784 0.2.3.3-alpha, when we added the stream-isolation feature which
3785 might cause Tor to open multiple rendezvous circuits for the same
3787 - Don't trigger an assertion failure when we mark a new client-side
3788 hidden-service introduction circuit for close during the process
3789 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
3792 o Minor bugfixes (log messages):
3793 - Correctly spell "connect" in a log message on failure to create a
3794 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
3796 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3797 Fixes bug 4856; bugfix on Tor 0.0.6.
3798 - Fix the log message describing how we work around discovering
3799 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
3800 4837; bugfix on 0.2.2.9-alpha.
3801 - When logging about a disallowed .exit name, do not also call it
3802 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
3804 o Minor bugfixes (build fixes):
3805 - During configure, detect when we're building with clang version
3806 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3807 CFLAGS. clang doesn't support them yet.
3808 - During configure, search for library containing cos function as
3809 libm lives in libcore on some platforms (BeOS/Haiku). Linking
3810 against libm was hard-coded before. Fixes the first part of bug
3811 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
3813 - Detect attempts to build Tor on (as yet hypothetical) versions
3814 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
3815 fix for bug 4533. Bugfix on 0.2.2.28-beta.
3816 - Preprocessor directives should not be put inside the arguments
3817 of a macro. This would break compilation with GCC releases prior
3818 to version 3.3. We would never recommend such an old GCC version,
3819 but it is apparently required for binary compatibility on some
3820 platforms (namely, certain builds of Haiku). Fixes the other part
3821 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
3824 o Minor bugfixes (other):
3825 - Older Linux kernels erroneously respond to strange nmap behavior
3826 by having accept() return successfully with a zero-length
3827 socket. When this happens, just close the connection. Previously,
3828 we would try harder to learn the remote address: but there was
3829 no such remote address to learn, and our method for trying to
3830 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3831 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3832 - Fix null-pointer access that could occur if TLS allocation failed.
3833 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
3834 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
3835 accidentally been reverted.
3836 - Fix our implementation of crypto_random_hostname() so it can't
3837 overflow on ridiculously large inputs. (No Tor version has ever
3838 provided this kind of bad inputs, but let's be correct in depth.)
3839 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
3840 - Find more places in the code that should have been testing for
3841 invalid sockets using the SOCKET_OK macro. Required for a fix
3842 for bug 4533. Bugfix on 0.2.2.28-beta.
3843 - Fix an assertion failure when, while running with bufferevents, a
3844 connection finishes connecting after it is marked for close, but
3845 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
3846 - test_util_spawn_background_ok() hardcoded the expected value
3847 for ENOENT to 2. This isn't portable as error numbers are
3848 platform specific, and particularly the hurd has ENOENT at
3849 0x40000002. Construct expected string at runtime, using the correct
3850 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
3851 - Reject attempts to disable DisableDebuggerAttachment while Tor is
3852 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
3853 - Use an appropriate-width type for sockets in tor-fw-helper on
3854 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
3857 - When sending or relaying a RELAY_EARLY cell, we used to convert
3858 it to a RELAY cell if the connection was using the v1 link
3859 protocol. This was a workaround for older versions of Tor, which
3860 didn't handle RELAY_EARLY cells properly. Now that all supported
3861 versions can handle RELAY_EARLY cells, and now that we're enforcing
3862 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3863 remove this workaround. Addresses bug 4786.
3865 o Code simplifications and refactoring:
3866 - Use OpenSSL's built-in SSL_state_string_long() instead of our
3867 own homebrewed ssl_state_to_string() replacement. Patch from
3868 Emile Snyder. Fixes bug 4653.
3869 - Use macros to indicate OpenSSL versions, so we don't need to worry
3870 about accidental hexadecimal bit shifts.
3871 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
3873 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
3874 - Use the smartlist_add_asprintf() alias more consistently.
3875 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
3876 invalid value, rather than just -1.
3877 - Rename a handful of old identifiers, mostly related to crypto
3878 structures and crypto functions. By convention, our "create an
3879 object" functions are called "type_new()", our "free an object"
3880 functions are called "type_free()", and our types indicate that
3881 they are types only with a final "_t". But a handful of older
3882 types and functions broke these rules, with function names like
3883 "type_create" or "subsystem_op_type", or with type names like
3887 Changes in version 0.2.3.10-alpha - 2011-12-16
3888 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
3889 Tor's buffers code. Absolutely everybody should upgrade.
3891 The bug relied on an incorrect calculation when making data continuous
3892 in one of our IO buffers, if the first chunk of the buffer was
3893 misaligned by just the wrong amount. The miscalculation would allow an
3894 attacker to overflow a piece of heap-allocated memory. To mount this
3895 attack, the attacker would need to either open a SOCKS connection to
3896 Tor's SocksPort (usually restricted to localhost), or target a Tor
3897 instance configured to make its connections through a SOCKS proxy
3898 (which Tor does not do by default).
3900 Good security practice requires that all heap-overflow bugs should be
3901 presumed to be exploitable until proven otherwise, so we are treating
3902 this as a potential code execution attack. Please upgrade immediately!
3903 This bug does not affect bufferevents-based builds of Tor. Special
3904 thanks to "Vektor" for reporting this issue to us!
3906 This release also contains a few minor bugfixes for issues discovered
3910 - Fix a heap overflow bug that could occur when trying to pull
3911 data into the first chunk of a buffer, when that chunk had
3912 already had some data drained from it. Fixes CVE-2011-2778;
3913 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3916 - If we can't attach streams to a rendezvous circuit when we
3917 finish connecting to a hidden service, clear the rendezvous
3918 circuit's stream-isolation state and try to attach streams
3919 again. Previously, we cleared rendezvous circuits' isolation
3920 state either too early (if they were freshly built) or not at all
3921 (if they had been built earlier and were cannibalized). Bugfix on
3922 0.2.3.3-alpha; fixes bug 4655.
3923 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
3924 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
3925 - Fix an assertion failure when a relay with accounting enabled
3926 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
3929 - Update to the December 6 2011 Maxmind GeoLite Country database.
3932 Changes in version 0.2.2.35 - 2011-12-16
3933 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3934 buffers code. Absolutely everybody should upgrade.
3936 The bug relied on an incorrect calculation when making data continuous
3937 in one of our IO buffers, if the first chunk of the buffer was
3938 misaligned by just the wrong amount. The miscalculation would allow an
3939 attacker to overflow a piece of heap-allocated memory. To mount this
3940 attack, the attacker would need to either open a SOCKS connection to
3941 Tor's SocksPort (usually restricted to localhost), or target a Tor
3942 instance configured to make its connections through a SOCKS proxy
3943 (which Tor does not do by default).
3945 Good security practice requires that all heap-overflow bugs should be
3946 presumed to be exploitable until proven otherwise, so we are treating
3947 this as a potential code execution attack. Please upgrade immediately!
3948 This bug does not affect bufferevents-based builds of Tor. Special
3949 thanks to "Vektor" for reporting this issue to us!
3951 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3952 crash bugs for unusual configurations, and a long-term bug that
3953 would prevent Tor from starting on Windows machines with draconian
3956 With this release, we remind everyone that 0.2.0.x has reached its
3957 formal end-of-life. Those Tor versions have many known flaws, and
3958 nobody should be using them. You should upgrade -- ideally to the
3959 0.2.2.x series. If you're using a Linux or BSD and its packages are
3960 obsolete, stop using those packages and upgrade anyway.
3962 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3963 longer receive support after some time in early 2012.
3966 - Fix a heap overflow bug that could occur when trying to pull
3967 data into the first chunk of a buffer, when that chunk had
3968 already had some data drained from it. Fixes CVE-2011-2778;
3969 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3970 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3971 that it doesn't attempt to allocate a socketpair. This could cause
3972 some problems on Windows systems with overzealous firewalls. Fix for
3973 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3975 - If we mark an OR connection for close based on a cell we process,
3976 don't process any further cells on it. We already avoid further
3977 reads on marked-for-close connections, but now we also discard the
3978 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3979 which was the first version where we might mark a connection for
3980 close based on processing a cell on it.
3981 - Correctly sanity-check that we don't underflow on a memory
3982 allocation (and then assert) for hidden service introduction
3983 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3984 bugfix on 0.2.1.5-alpha.
3985 - Fix a memory leak when we check whether a hidden service
3986 descriptor has any usable introduction points left. Fixes bug
3987 4424. Bugfix on 0.2.2.25-alpha.
3988 - Don't crash when we're running as a relay and don't have a GeoIP
3989 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3990 we've had in the 0.2.3.x branch already.
3991 - When running as a client, do not print a misleading (and plain
3992 wrong) log message that we're collecting "directory request"
3993 statistics: clients don't collect statistics. Also don't create a
3994 useless (because empty) stats file in the stats/ directory. Fixes
3995 bug 4353; bugfix on 0.2.2.34.
3998 - Detect failure to initialize Libevent. This fix provides better
3999 detection for future instances of bug 4457.
4000 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
4001 function. This was eating up hideously large amounts of time on some
4002 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
4003 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4004 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4006 - Don't warn about unused log_mutex in log.c when building with
4007 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
4008 0.1.0.6-rc which introduced --disable-threads.
4009 - When configuring, starting, or stopping an NT service, stop
4010 immediately after the service configuration attempt has succeeded
4011 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
4012 - When sending a NETINFO cell, include the original address
4013 received for the other side, not its canonical address. Found
4014 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
4015 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
4016 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
4017 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
4018 occurred when a client tried to fetch a descriptor for a bridge
4019 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
4020 - Backport fixes for a pair of compilation warnings on Windows.
4021 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
4022 - If we had ever tried to call tor_addr_to_str on an address of
4023 unknown type, we would have done a strdup on an uninitialized
4024 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
4025 Reported by "troll_un".
4026 - Correctly detect and handle transient lookup failures from
4027 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
4028 Reported by "troll_un".
4029 - Fix null-pointer access that could occur if TLS allocation failed.
4030 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
4031 - Use tor_socket_t type for listener argument to accept(). Fixes bug
4032 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
4035 - Add two new config options for directory authorities:
4036 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
4037 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
4038 that is always sufficient to satisfy the bandwidth requirement for
4039 the Guard flag. Now it will be easier for researchers to simulate
4040 Tor networks with different values. Resolves ticket 4484.
4041 - When Tor ignores a hidden service specified in its configuration,
4042 include the hidden service's directory in the warning message.
4043 Previously, we would only tell the user that some hidden service
4044 was ignored. Bugfix on 0.0.6; fixes bug 4426.
4045 - Update to the December 6 2011 Maxmind GeoLite Country database.
4047 o Packaging changes:
4048 - Make it easier to automate expert package builds on Windows,
4049 by removing an absolute path from makensis.exe command.
4052 Changes in version 0.2.1.32 - 2011-12-16
4053 Tor 0.2.1.32 backports important security and privacy fixes for
4054 oldstable. This release is intended only for package maintainers and
4055 others who cannot use the 0.2.2 stable series. All others should be
4056 using Tor 0.2.2.x or newer.
4058 The Tor 0.2.1.x series will reach formal end-of-life some time in
4059 early 2012; we will stop releasing patches for it then.
4061 o Major bugfixes (also included in 0.2.2.x):
4062 - Correctly sanity-check that we don't underflow on a memory
4063 allocation (and then assert) for hidden service introduction
4064 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4065 bugfix on 0.2.1.5-alpha.
4066 - Fix a heap overflow bug that could occur when trying to pull
4067 data into the first chunk of a buffer, when that chunk had
4068 already had some data drained from it. Fixes CVE-2011-2778;
4069 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4072 - Update to the December 6 2011 Maxmind GeoLite Country database.
4075 Changes in version 0.2.3.9-alpha - 2011-12-08
4076 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
4077 a "DisableNetwork" security feature that bundles can use to avoid
4078 touching the network until bridges are configured, moves forward on
4079 the pluggable transport design, fixes a flaw in the hidden service
4080 design that unnecessarily prevented clients with wrong clocks from
4081 reaching hidden services, and fixes a wide variety of other issues.
4084 - Clients can now connect to private bridges over IPv6. Bridges
4085 still need at least one IPv4 address in order to connect to
4086 other relays. Note that we don't yet handle the case where the
4087 user has two bridge lines for the same bridge (one IPv4, one
4088 IPv6). Implements parts of proposal 186.
4089 - New "DisableNetwork" config option to prevent Tor from launching any
4090 connections or accepting any connections except on a control port.
4091 Bundles and controllers can set this option before letting Tor talk
4092 to the rest of the network, for example to prevent any connections
4093 to a non-bridge address. Packages like Orbot can also use this
4094 option to instruct Tor to save power when the network is off.
4095 - Clients and bridges can now be configured to use a separate
4096 "transport" proxy. This approach makes the censorship arms race
4097 easier by allowing bridges to use protocol obfuscation plugins. It
4098 implements the "managed proxy" part of proposal 180 (ticket 3472).
4099 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
4100 implementation. It makes AES_CTR about 7% faster than our old one
4101 (which was about 10% faster than the one OpenSSL used to provide).
4102 Resolves ticket 4526.
4103 - Add a "tor2web mode" for clients that want to connect to hidden
4104 services non-anonymously (and possibly more quickly). As a safety
4105 measure to try to keep users from turning this on without knowing
4106 what they are doing, tor2web mode must be explicitly enabled at
4107 compile time, and a copy of Tor compiled to run in tor2web mode
4108 cannot be used as a normal Tor client. Implements feature 2553.
4109 - Add experimental support for running on Windows with IOCP and no
4110 kernel-space socket buffers. This feature is controlled by a new
4111 "UserspaceIOCPBuffers" config option (off by default), which has
4112 no effect unless Tor has been built with support for bufferevents,
4113 is running on Windows, and has enabled IOCP. This may, in the long
4114 run, help solve or mitigate bug 98.
4115 - Use a more secure consensus parameter voting algorithm. Now at
4116 least three directory authorities or a majority of them must
4117 vote on a given parameter before it will be included in the
4118 consensus. Implements proposal 178.
4121 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
4122 They used to check that the timestamp was within 30 minutes
4123 of their system clock, so they could cap the size of their
4124 replay-detection cache, but that approach unnecessarily refused
4125 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
4126 the v3 intro-point protocol (the first one which sent a timestamp
4127 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
4128 - Only use the EVP interface when AES acceleration is enabled,
4129 to avoid a 5-7% performance regression. Resolves issue 4525;
4130 bugfix on 0.2.3.8-alpha.
4132 o Privacy/anonymity features (bridge detection):
4133 - Make bridge SSL certificates a bit more stealthy by using random
4134 serial numbers, in the same fashion as OpenSSL when generating
4135 self-signed certificates. Implements ticket 4584.
4136 - Introduce a new config option "DynamicDHGroups", enabled by
4137 default, which provides each bridge with a unique prime DH modulus
4138 to be used during SSL handshakes. This option attempts to help
4139 against censors who might use the Apache DH modulus as a static
4140 identifier for bridges. Addresses ticket 4548.
4142 o Minor features (new/different config options):
4143 - New configuration option "DisableDebuggerAttachment" (on by default)
4144 to prevent basic debugging attachment attempts by other processes.
4145 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
4146 - Allow MapAddress directives to specify matches against super-domains,
4147 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
4148 Implements issue 933.
4149 - Slightly change behavior of "list" options (that is, config
4150 options that can appear more than once) when they appear both in
4151 torrc and on the command line. Previously, the command-line options
4152 would be appended to the ones from torrc. Now, the command-line
4153 options override the torrc options entirely. This new behavior
4154 allows the user to override list options (like exit policies and
4155 ports to listen on) from the command line, rather than simply
4156 appending to the list.
4157 - You can get the old (appending) command-line behavior for "list"
4158 options by prefixing the option name with a "+".
4159 - You can remove all the values for a "list" option from the command
4160 line without adding any new ones by prefixing the option name
4162 - Add experimental support for a "defaults" torrc file to be parsed
4163 before the regular torrc. Torrc options override the defaults file's
4164 options in the same way that the command line overrides the torrc.
4165 The SAVECONF controller command saves only those options which
4166 differ between the current configuration and the defaults file. HUP
4167 reloads both files. (Note: This is an experimental feature; its
4168 behavior will probably be refined in future 0.2.3.x-alpha versions
4169 to better meet packagers' needs.) Implements task 4552.
4172 - Try to make the introductory warning message that Tor prints on
4173 startup more useful for actually finding help and information.
4174 Resolves ticket 2474.
4175 - Running "make version" now displays the version of Tor that
4176 we're about to build. Idea from katmagic; resolves issue 4400.
4177 - Expire old or over-used hidden service introduction points.
4178 Required by fix for bug 3460.
4179 - Move the replay-detection cache for the RSA-encrypted parts of
4180 INTRODUCE2 cells to the introduction point data structures.
4181 Previously, we would use one replay-detection cache per hidden
4182 service. Required by fix for bug 3460.
4183 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
4184 public key replay-detection cache from 60 minutes to 5 minutes. This
4185 replay-detection cache is now used only to detect multiple
4186 INTRODUCE2 cells specifying the same rendezvous point, so we can
4187 avoid launching multiple simultaneous attempts to connect to it.
4189 o Minor bugfixes (on Tor 0.2.2.x and earlier):
4190 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4191 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4193 - Fix a minor formatting issue in one of tor-gencert's error messages.
4195 - Prevent a false positive from the check-spaces script, by disabling
4196 the "whitespace between function name and (" check for functions
4198 - Fix a log message suggesting that people contact a non-existent
4199 email address. Fixes bug 3448.
4200 - Fix null-pointer access that could occur if TLS allocation failed.
4201 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
4202 - Report a real bootstrap problem to the controller on router
4203 identity mismatch. Previously we just said "foo", which probably
4204 made a lot of sense at the time. Fixes bug 4169; bugfix on
4206 - If we had ever tried to call tor_addr_to_str() on an address of
4207 unknown type, we would have done a strdup() on an uninitialized
4208 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
4209 Reported by "troll_un".
4210 - Correctly detect and handle transient lookup failures from
4211 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
4212 Reported by "troll_un".
4213 - Use tor_socket_t type for listener argument to accept(). Fixes bug
4214 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
4215 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
4216 bug 4532; found by "troll_un".
4218 o Minor bugfixes (on Tor 0.2.3.x):
4219 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
4221 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
4222 circuit for use as a hidden service client's rendezvous point.
4223 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
4224 with help from wanoskarnet.
4225 - Restore behavior of overriding SocksPort, ORPort, and similar
4226 options from the command line. Bugfix on 0.2.3.3-alpha.
4229 - Properly handle the case where the build-tree is not the same
4230 as the source tree when generating src/common/common_sha1.i,
4231 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
4232 bugfix on 0.2.0.1-alpha.
4234 o Code simplifications, cleanups, and refactorings:
4235 - Remove the pure attribute from all functions that used it
4236 previously. In many cases we assigned it incorrectly, because the
4237 functions might assert or call impure functions, and we don't have
4238 evidence that keeping the pure attribute is worthwhile. Implements
4239 changes suggested in ticket 4421.
4240 - Remove some dead code spotted by coverity. Fixes cid 432.
4241 Bugfix on 0.2.3.1-alpha, closes bug 4637.
4244 Changes in version 0.2.3.8-alpha - 2011-11-22
4245 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
4246 socketpair-related bug that has been bothering Windows users. It adds
4247 support to serve microdescriptors to controllers, so Vidalia's network
4248 map can resume listing relays (once Vidalia implements its side),
4249 and adds better support for hardware AES acceleration. Finally, it
4250 starts the process of adjusting the bandwidth cutoff for getting the
4251 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
4252 that tiny relays harm performance more than they help network capacity.
4255 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
4256 that it doesn't attempt to allocate a socketpair. This could cause
4257 some problems on Windows systems with overzealous firewalls. Fix for
4258 bug 4457; workaround for Libevent versions 2.0.1-alpha through
4260 - Correctly sanity-check that we don't underflow on a memory
4261 allocation (and then assert) for hidden service introduction
4262 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4263 bugfix on 0.2.1.5-alpha.
4264 - Remove the artificially low cutoff of 20KB to guarantee the Fast
4265 flag. In the past few years the average relay speed has picked
4266 up, and while the "top 7/8 of the network get the Fast flag" and
4267 "all relays with 20KB or more of capacity get the Fast flag" rules
4268 used to have the same result, now the top 7/8 of the network has
4269 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
4270 - Fix a rare assertion failure when checking whether a v0 hidden
4271 service descriptor has any usable introduction points left, and
4272 we don't have enough information to build a circuit to the first
4273 intro point named in the descriptor. The HS client code in
4274 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
4275 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
4276 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
4277 - Make bridge authorities not crash when they are asked for their own
4278 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
4279 - When running as a client, do not print a misleading (and plain
4280 wrong) log message that we're collecting "directory request"
4281 statistics: clients don't collect statistics. Also don't create a
4282 useless (because empty) stats file in the stats/ directory. Fixes
4283 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
4286 - Allow Tor controllers like Vidalia to obtain the microdescriptor
4287 for a relay by identity digest or nickname. Previously,
4288 microdescriptors were only available by their own digests, so a
4289 controller would have to ask for and parse the whole microdescriptor
4290 consensus in order to look up a single relay's microdesc. Fixes
4291 bug 3832; bugfix on 0.2.3.1-alpha.
4292 - Use OpenSSL's EVP interface for AES encryption, so that all AES
4293 operations can use hardware acceleration (if present). Resolves
4296 o Minor bugfixes (on 0.2.2.x and earlier):
4297 - Detect failure to initialize Libevent. This fix provides better
4298 detection for future instances of bug 4457.
4299 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
4300 function. This was eating up hideously large amounts of time on some
4301 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
4302 - Don't warn about unused log_mutex in log.c when building with
4303 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
4304 0.1.0.6-rc which introduced --disable-threads.
4305 - Allow manual 'authenticate' commands to the controller interface
4306 from netcat (nc) as well as telnet. We were rejecting them because
4307 they didn't come with the expected whitespace at the end of the
4308 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
4309 - Fix some (not actually triggerable) buffer size checks in usage of
4310 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
4312 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
4313 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
4314 - When configuring, starting, or stopping an NT service, stop
4315 immediately after the service configuration attempt has succeeded
4316 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
4317 - When sending a NETINFO cell, include the original address
4318 received for the other side, not its canonical address. Found
4319 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
4320 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
4321 can pick them up when the tests aren't disabled. Bugfix on
4322 0.2.2.4-alpha which introduced tinytest.
4323 - Fix a memory leak when we check whether a hidden service
4324 descriptor has any usable introduction points left. Fixes bug
4325 4424. Bugfix on 0.2.2.25-alpha.
4326 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
4327 occurred when a client tried to fetch a descriptor for a bridge
4328 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
4330 o Minor bugfixes (on 0.2.3.x):
4331 - Make util unit tests build correctly with MSVC. Bugfix on
4332 0.2.3.3-alpha. Patch by Gisle Vanem.
4333 - Successfully detect AUTH_CHALLENGE cells with no recognized
4334 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
4336 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
4337 it should still send a NETINFO cell to allow the connection to
4338 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
4340 - Log less loudly when we get an invalid authentication certificate
4341 from a source other than a directory authority: it's not unusual
4342 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
4344 - Tolerate servers with more clock skew in their authentication
4345 certificates than previously. Fixes bug 4371; bugfix on
4347 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
4348 on 0.2.3.4-alpha and 0.2.3.6-alpha.
4351 - Add two new config options for directory authorities:
4352 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
4353 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
4354 that is always sufficient to satisfy the bandwidth requirement for
4355 the Guard flag. Now it will be easier for researchers to simulate
4356 Tor networks with different values. Resolves ticket 4484.
4357 - When Tor ignores a hidden service specified in its configuration,
4358 include the hidden service's directory in the warning message.
4359 Previously, we would only tell the user that some hidden service
4360 was ignored. Bugfix on 0.0.6; fixes bug 4426.
4361 - When we fail to initialize Libevent, retry with IOCP disabled so we
4362 don't need to turn on multi-threading support in Libevent, which in
4363 turn requires a working socketpair(). This is a workaround for bug
4364 4457, which affects Libevent versions from 2.0.1-alpha through
4366 - Detect when we try to build on a platform that doesn't define
4367 AF_UNSPEC to 0. We don't work there, so refuse to compile.
4368 - Update to the November 1 2011 Maxmind GeoLite Country database.
4370 o Packaging changes:
4371 - Make it easier to automate expert package builds on Windows,
4372 by removing an absolute path from makensis.exe command.
4374 o Code simplifications and refactoring:
4375 - Remove some redundant #include directives throughout the code.
4376 Patch from Andrea Gelmini.
4377 - Unconditionally use OpenSSL's AES implementation instead of our
4378 old built-in one. OpenSSL's AES has been better for a while, and
4379 relatively few servers should still be on any version of OpenSSL
4380 that doesn't have good optimized assembly AES.
4381 - Use the name "CERTS" consistently to refer to the new cell type;
4382 we were calling it CERT in some places and CERTS in others.
4385 - Numerous new unit tests for functions in util.c and address.c by
4387 - The long-disabled benchmark tests are now split into their own
4388 ./src/test/bench binary.
4389 - The benchmark tests can now use more accurate timers than
4390 gettimeofday() when such timers are available.
4393 Changes in version 0.2.3.7-alpha - 2011-10-30
4394 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
4395 the new v3 handshake. It also resolves yet another bridge address
4399 - If we mark an OR connection for close based on a cell we process,
4400 don't process any further cells on it. We already avoid further
4401 reads on marked-for-close connections, but now we also discard the
4402 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
4403 which was the first version where we might mark a connection for
4404 close based on processing a cell on it.
4405 - Fix a double-free bug that would occur when we received an invalid
4406 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
4407 bugfix on 0.2.3.6-alpha.
4408 - Bridges no longer include their address in NETINFO cells on outgoing
4409 OR connections, to allow them to blend in better with clients.
4410 Removes another avenue for enumerating bridges. Reported by
4411 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
4412 cells were introduced.
4415 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
4416 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
4419 Changes in version 0.2.3.6-alpha - 2011-10-26
4420 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
4421 anonymity vulnerability where an attacker can deanonymize Tor
4422 users. Everybody should upgrade.
4424 This release also features support for a new v3 connection handshake
4425 protocol, and fixes to make hidden service connections more robust.
4428 - Implement a new handshake protocol (v3) for authenticating Tors to
4429 each other over TLS. It should be more resistant to fingerprinting
4430 than previous protocols, and should require less TLS hacking for
4431 future Tor implementations. Implements proposal 176.
4432 - Allow variable-length padding cells to disguise the length of
4433 Tor's TLS records. Implements part of proposal 184.
4435 o Privacy/anonymity fixes (clients):
4436 - Clients and bridges no longer send TLS certificate chains on
4437 outgoing OR connections. Previously, each client or bridge would
4438 use the same cert chain for all outgoing OR connections until
4439 its IP address changes, which allowed any relay that the client
4440 or bridge contacted to determine which entry guards it is using.
4441 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4442 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4443 no longer considers that connection as suitable for satisfying a
4444 circuit EXTEND request. Now relays can protect clients from the
4445 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4446 - Directory authorities no longer assign the Guard flag to relays
4447 that haven't upgraded to the above "refuse EXTEND requests
4448 to client connections" fix. Now directory authorities can
4449 protect clients from the CVE-2011-2768 issue even if neither
4450 the clients nor the relays have upgraded yet. There's a new
4451 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
4452 to let us transition smoothly, else tomorrow there would be no
4455 o Major bugfixes (hidden services):
4456 - Improve hidden service robustness: when an attempt to connect to
4457 a hidden service ends, be willing to refetch its hidden service
4458 descriptors from each of the HSDir relays responsible for them
4459 immediately. Previously, we would not consider refetching the
4460 service's descriptors from each HSDir for 15 minutes after the last
4461 fetch, which was inconvenient if the hidden service was not running
4462 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
4463 - When one of a hidden service's introduction points appears to be
4464 unreachable, stop trying it. Previously, we would keep trying
4465 to build circuits to the introduction point until we lost the
4466 descriptor, usually because the user gave up and restarted Tor.
4467 Partly fixes bug 3825.
4468 - Don't launch a useless circuit after failing to use one of a
4469 hidden service's introduction points. Previously, we would
4470 launch a new introduction circuit, but not set the hidden service
4471 which that circuit was intended to connect to, so it would never
4472 actually be used. A different piece of code would then create a
4473 new introduction circuit correctly. Bug reported by katmagic and
4474 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
4476 o Major bugfixes (other):
4477 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4478 that they initiated. Relays could distinguish incoming bridge
4479 connections from client connections, creating another avenue for
4480 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4481 Found by "frosty_un".
4482 - Don't update the AccountingSoftLimitHitAt state file entry whenever
4483 tor gets started. This prevents a wrong average bandwidth
4484 estimate, which would cause relays to always start a new accounting
4485 interval at the earliest possible moment. Fixes bug 2003; bugfix
4486 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
4487 immensely in tracking this bug down.
4488 - Fix a crash bug when changing node restrictions while a DNS lookup
4489 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
4492 o Minor bugfixes (on 0.2.2.x and earlier):
4493 - When a hidden service turns an extra service-side introduction
4494 circuit into a general-purpose circuit, free the rend_data and
4495 intro_key fields first, so we won't leak memory if the circuit
4496 is cannibalized for use as another service-side introduction
4497 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
4498 - Rephrase the log message emitted if the TestSocks check is
4499 successful. Patch from Fabian Keil; fixes bug 4094.
4500 - Bridges now skip DNS self-tests, to act a little more stealthily.
4501 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
4502 bridges. Patch by "warms0x".
4503 - Remove a confusing dollar sign from the example fingerprint in the
4504 man page, and also make the example fingerprint a valid one. Fixes
4505 bug 4309; bugfix on 0.2.1.3-alpha.
4506 - Fix internal bug-checking logic that was supposed to catch
4507 failures in digest generation so that it will fail more robustly
4508 if we ask for a nonexistent algorithm. Found by Coverity Scan.
4509 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
4510 - Report any failure in init_keys() calls launched because our
4511 IP address has changed. Spotted by Coverity Scan. Bugfix on
4512 0.1.1.4-alpha; fixes CID 484.
4514 o Minor bugfixes (on 0.2.3.x):
4515 - Fix a bug in configure.in that kept it from building a configure
4516 script with autoconf versions earlier than 2.61. Fixes bug 2430;
4517 bugfix on 0.2.3.1-alpha.
4518 - Don't warn users that they are exposing a client port to the
4519 Internet if they have specified an RFC1918 address. Previously,
4520 we would warn if the user had specified any non-loopback
4521 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
4522 - Fix memory leaks in the failing cases of the new SocksPort and
4523 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
4524 fixes coverity CIDs 485, 486, and 487.
4527 - When a hidden service's introduction point times out, consider
4528 trying it again during the next attempt to connect to the
4529 HS. Previously, we would not try it again unless a newly fetched
4530 descriptor contained it. Required by fixes for bugs 1297 and 3825.
4531 - The next version of Windows will be called Windows 8, and it has
4532 a major version of 6, minor version of 2. Correctly identify that
4533 version instead of calling it "Very recent version". Resolves
4534 ticket 4153; reported by funkstar.
4535 - The Bridge Authority now writes statistics on how many bridge
4536 descriptors it gave out in total, and how many unique descriptors
4537 it gave out. It also lists how often the most and least commonly
4538 fetched descriptors were given out, as well as the median and
4539 25th/75th percentile. Implements tickets 4200 and 4294.
4540 - Update to the October 4 2011 Maxmind GeoLite Country database.
4542 o Code simplifications and refactoring:
4543 - Remove some old code to remember statistics about which descriptors
4544 we've served as a directory mirror. The feature wasn't used and
4545 is outdated now that microdescriptors are around.
4546 - Rename Tor functions that turn strings into addresses, so that
4547 "parse" indicates that no hostname resolution occurs, and
4548 "lookup" indicates that hostname resolution may occur. This
4549 should help prevent mistakes in the future. Fixes bug 3512.
4552 Changes in version 0.2.2.34 - 2011-10-26
4553 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
4554 can deanonymize Tor users. Everybody should upgrade.
4556 The attack relies on four components: 1) Clients reuse their TLS cert
4557 when talking to different relays, so relays can recognize a user by
4558 the identity key in her cert. 2) An attacker who knows the client's
4559 identity key can probe each guard relay to see if that identity key
4560 is connected to that guard relay right now. 3) A variety of active
4561 attacks in the literature (starting from "Low-Cost Traffic Analysis
4562 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
4563 discover the guard relays that a Tor user visiting the website is using.
4564 4) Clients typically pick three guards at random, so the set of guards
4565 for a given user could well be a unique fingerprint for her. This
4566 release fixes components #1 and #2, which is enough to block the attack;
4567 the other two remain as open research problems. Special thanks to
4568 "frosty_un" for reporting the issue to us!
4570 Clients should upgrade so they are no longer recognizable by the TLS
4571 certs they present. Relays should upgrade so they no longer allow a
4572 remote attacker to probe them to test whether unpatched clients are
4573 currently connected to them.
4575 This release also fixes several vulnerabilities that allow an attacker
4576 to enumerate bridge relays. Some bridge enumeration attacks still
4577 remain; see for example proposal 188.
4579 o Privacy/anonymity fixes (clients):
4580 - Clients and bridges no longer send TLS certificate chains on
4581 outgoing OR connections. Previously, each client or bridge would
4582 use the same cert chain for all outgoing OR connections until
4583 its IP address changes, which allowed any relay that the client
4584 or bridge contacted to determine which entry guards it is using.
4585 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4586 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4587 no longer considers that connection as suitable for satisfying a
4588 circuit EXTEND request. Now relays can protect clients from the
4589 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4590 - Directory authorities no longer assign the Guard flag to relays
4591 that haven't upgraded to the above "refuse EXTEND requests
4592 to client connections" fix. Now directory authorities can
4593 protect clients from the CVE-2011-2768 issue even if neither
4594 the clients nor the relays have upgraded yet. There's a new
4595 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
4596 to let us transition smoothly, else tomorrow there would be no
4599 o Privacy/anonymity fixes (bridge enumeration):
4600 - Bridge relays now do their directory fetches inside Tor TLS
4601 connections, like all the other clients do, rather than connecting
4602 directly to the DirPort like public relays do. Removes another
4603 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4604 - Bridges relays now build circuits for themselves in a more similar
4605 way to how clients build them. Removes another avenue for
4606 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4607 when bridges were introduced.
4608 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4609 that they initiated. Relays could distinguish incoming bridge
4610 connections from client connections, creating another avenue for
4611 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4612 Found by "frosty_un".
4615 - Fix a crash bug when changing node restrictions while a DNS lookup
4616 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
4618 - Don't launch a useless circuit after failing to use one of a
4619 hidden service's introduction points. Previously, we would
4620 launch a new introduction circuit, but not set the hidden service
4621 which that circuit was intended to connect to, so it would never
4622 actually be used. A different piece of code would then create a
4623 new introduction circuit correctly. Bug reported by katmagic and
4624 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
4627 - Change an integer overflow check in the OpenBSD_Malloc code so
4628 that GCC is less likely to eliminate it as impossible. Patch
4629 from Mansour Moufid. Fixes bug 4059.
4630 - When a hidden service turns an extra service-side introduction
4631 circuit into a general-purpose circuit, free the rend_data and
4632 intro_key fields first, so we won't leak memory if the circuit
4633 is cannibalized for use as another service-side introduction
4634 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
4635 - Bridges now skip DNS self-tests, to act a little more stealthily.
4636 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
4637 bridges. Patch by "warms0x".
4638 - Fix internal bug-checking logic that was supposed to catch
4639 failures in digest generation so that it will fail more robustly
4640 if we ask for a nonexistent algorithm. Found by Coverity Scan.
4641 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
4642 - Report any failure in init_keys() calls launched because our
4643 IP address has changed. Spotted by Coverity Scan. Bugfix on
4644 0.1.1.4-alpha; fixes CID 484.
4646 o Minor bugfixes (log messages and documentation):
4647 - Remove a confusing dollar sign from the example fingerprint in the
4648 man page, and also make the example fingerprint a valid one. Fixes
4649 bug 4309; bugfix on 0.2.1.3-alpha.
4650 - The next version of Windows will be called Windows 8, and it has
4651 a major version of 6, minor version of 2. Correctly identify that
4652 version instead of calling it "Very recent version". Resolves
4653 ticket 4153; reported by funkstar.
4654 - Downgrade log messages about circuit timeout calibration from
4655 "notice" to "info": they don't require or suggest any human
4656 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4657 bugfix on 0.2.2.14-alpha.
4660 - Turn on directory request statistics by default and include them in
4661 extra-info descriptors. Don't break if we have no GeoIP database.
4662 Backported from 0.2.3.1-alpha; implements ticket 3951.
4663 - Update to the October 4 2011 Maxmind GeoLite Country database.
4666 Changes in version 0.2.1.31 - 2011-10-26
4667 Tor 0.2.1.31 backports important security and privacy fixes for
4668 oldstable. This release is intended only for package maintainers and
4669 others who cannot use the 0.2.2 stable series. All others should be
4670 using Tor 0.2.2.x or newer.
4672 o Security fixes (also included in 0.2.2.x):
4673 - Replace all potentially sensitive memory comparison operations
4674 with versions whose runtime does not depend on the data being
4675 compared. This will help resist a class of attacks where an
4676 adversary can use variations in timing information to learn
4677 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4678 implementation by Robert Ransom based partially on code by DJB.)
4679 - Fix an assert in parsing router descriptors containing IPv6
4680 addresses. This one took down the directory authorities when
4681 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4683 o Privacy/anonymity fixes (also included in 0.2.2.x):
4684 - Clients and bridges no longer send TLS certificate chains on
4685 outgoing OR connections. Previously, each client or bridge would
4686 use the same cert chain for all outgoing OR connections until
4687 its IP address changes, which allowed any relay that the client
4688 or bridge contacted to determine which entry guards it is using.
4689 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4690 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4691 no longer considers that connection as suitable for satisfying a
4692 circuit EXTEND request. Now relays can protect clients from the
4693 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4694 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4695 that they initiated. Relays could distinguish incoming bridge
4696 connections from client connections, creating another avenue for
4697 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4698 Found by "frosty_un".
4699 - When receiving a hidden service descriptor, check that it is for
4700 the hidden service we wanted. Previously, Tor would store any
4701 hidden service descriptors that a directory gave it, whether it
4702 wanted them or not. This wouldn't have let an attacker impersonate
4703 a hidden service, but it did let directories pre-seed a client
4704 with descriptors that it didn't want. Bugfix on 0.0.6.
4705 - Avoid linkability based on cached hidden service descriptors: forget
4706 all hidden service descriptors cached as a client when processing a
4707 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4708 - Make the bridge directory authority refuse to answer directory
4709 requests for "all" descriptors. It used to include bridge
4710 descriptors in its answer, which was a major information leak.
4711 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4712 - Don't attach new streams to old rendezvous circuits after SIGNAL
4713 NEWNYM. Previously, we would keep using an existing rendezvous
4714 circuit if it remained open (i.e. if it were kept open by a
4715 long-lived stream, or if a new stream were attached to it before
4716 Tor could notice that it was old and no longer in use). Bugfix on
4717 0.1.1.15-rc; fixes bug 3375.
4719 o Minor bugfixes (also included in 0.2.2.x):
4720 - When we restart our relay, we might get a successful connection
4721 from the outside before we've started our reachability tests,
4722 triggering a warning: "ORPort found reachable, but I have no
4723 routerinfo yet. Failing to inform controller of success." This
4724 bug was harmless unless Tor is running under a controller
4725 like Vidalia, in which case the controller would never get a
4726 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4728 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4729 enabled. Fixes bug 1526.
4730 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4731 anything since 0.2.1.16-rc.
4732 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4733 None of the cases where we did this before were wrong, but by making
4734 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4735 - Fix a rare crash bug that could occur when a client was configured
4736 with a large number of bridges. Fixes bug 2629; bugfix on
4737 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4738 - Correct the warning displayed when a rendezvous descriptor exceeds
4739 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4741 - Fix an uncommon assertion failure when running with DNSPort under
4742 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4743 - When warning about missing zlib development packages during compile,
4744 give the correct package names. Bugfix on 0.2.0.1-alpha.
4745 - Require that introduction point keys and onion keys have public
4746 exponent 65537. Bugfix on 0.2.0.10-alpha.
4747 - Do not crash when our configuration file becomes unreadable, for
4748 example due to a permissions change, between when we start up
4749 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4751 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4753 - Always NUL-terminate the sun_path field of a sockaddr_un before
4754 passing it to the kernel. (Not a security issue: kernels are
4755 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4756 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4757 - Don't stack-allocate the list of supplementary GIDs when we're
4758 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4759 could take up to 256K, which is way too much stack. Found by
4760 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4762 o Minor bugfixes (only in 0.2.1.x):
4763 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
4764 rely on them. Bugfix on 0.2.1.30.
4765 - Use git revisions instead of svn revisions when generating our
4766 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4768 o Minor features (also included in 0.2.2.x):
4769 - Adjust the expiration time on our SSL session certificates to
4770 better match SSL certs seen in the wild. Resolves ticket 4014.
4771 - Allow nameservers with IPv6 address. Resolves bug 2574.
4772 - Update to the October 4 2011 Maxmind GeoLite Country database.
4775 Changes in version 0.2.3.5-alpha - 2011-09-28
4776 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
4777 bridge relays; fixes an assertion error that many users started hitting
4778 today; and adds the ability to refill token buckets more often than
4779 once per second, allowing significant performance improvements.
4782 - Bridge relays now do their directory fetches inside Tor TLS
4783 connections, like all the other clients do, rather than connecting
4784 directly to the DirPort like public relays do. Removes another
4785 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4786 - Bridges relays now build circuits for themselves in a more similar
4787 way to how clients build them. Removes another avenue for
4788 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4789 when bridges were introduced.
4792 - Fix an "Assertion md->held_by_node == 1 failed" error that could
4793 occur when the same microdescriptor was referenced by two node_t
4794 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
4796 o Major features (networking):
4797 - Add a new TokenBucketRefillInterval option to refill token buckets
4798 more frequently than once per second. This should improve network
4799 performance, alleviate queueing problems, and make traffic less
4800 bursty. Implements proposal 183; closes ticket 3630. Design by
4801 Florian Tschorsch and Björn Scheuermann; implementation by
4805 - Change an integer overflow check in the OpenBSD_Malloc code so
4806 that GCC is less likely to eliminate it as impossible. Patch
4807 from Mansour Moufid. Fixes bug 4059.
4809 o Minor bugfixes (usability):
4810 - Downgrade log messages about circuit timeout calibration from
4811 "notice" to "info": they don't require or suggest any human
4812 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4813 bugfix on 0.2.2.14-alpha.
4815 o Minor features (diagnostics):
4816 - When the system call to create a listener socket fails, log the
4817 error message explaining why. This may help diagnose bug 4027.
4820 Changes in version 0.2.3.4-alpha - 2011-09-13
4821 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
4822 tweak to Tor's TLS handshake that makes relays and bridges that run
4823 this new version reachable from Iran again. It also fixes a few new
4824 bugs in 0.2.3.x, and teaches relays to recognize when they're not
4825 listed in the network consensus and republish.
4827 o Major bugfixes (also part of 0.2.2.33):
4828 - Avoid an assertion failure when reloading a configuration with
4829 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4830 3923; bugfix on 0.2.2.25-alpha.
4832 o Minor features (security, also part of 0.2.2.33):
4833 - Check for replays of the public-key encrypted portion of an
4834 INTRODUCE1 cell, in addition to the current check for replays of
4835 the g^x value. This prevents a possible class of active attacks
4836 by an attacker who controls both an introduction point and a
4837 rendezvous point, and who uses the malleability of AES-CTR to
4838 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4839 that these attacks are infeasible (requiring the attacker to send
4840 on the order of zettabytes of altered cells in a short interval),
4841 but we'd rather block them off in case there are any classes of
4842 this attack that we missed. Reported by Willem Pinckaers.
4844 o Minor features (also part of 0.2.2.33):
4845 - Adjust the expiration time on our SSL session certificates to
4846 better match SSL certs seen in the wild. Resolves ticket 4014.
4847 - Change the default required uptime for a relay to be accepted as
4848 a HSDir (hidden service directory) from 24 hours to 25 hours.
4849 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4850 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4851 authorities to abstain from voting on assignment of the HSDir
4852 consensus flag. Related to bug 2649.
4853 - Update to the September 6 2011 Maxmind GeoLite Country database.
4855 o Minor bugfixes (also part of 0.2.2.33):
4856 - Demote the 'replay detected' log message emitted when a hidden
4857 service receives the same Diffie-Hellman public key in two different
4858 INTRODUCE2 cells to info level. A normal Tor client can cause that
4859 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4860 fixes part of bug 2442.
4861 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4862 level. There is nothing that a hidden service's operator can do
4863 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4865 - Clarify a log message specifying the characters permitted in
4866 HiddenServiceAuthorizeClient client names. Previously, the log
4867 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4868 given the impression that every ASCII character between "+" and "_"
4869 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4871 o Build fixes (also part of 0.2.2.33):
4872 - Clean up some code issues that prevented Tor from building on older
4873 BSDs. Fixes bug 3894; reported by "grarpamp".
4874 - Search for a platform-specific version of "ar" when cross-compiling.
4875 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4878 - Fix a bug where the SocksPort option (for example) would get
4879 ignored and replaced by the default if a SocksListenAddress
4880 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
4884 - Relays now try regenerating and uploading their descriptor more
4885 frequently if they are not listed in the consensus, or if the
4886 version of their descriptor listed in the consensus is too
4887 old. This fix should prevent situations where a server declines
4888 to re-publish itself because it has done so too recently, even
4889 though the authorities decided not to list its recent-enough
4890 descriptor. Fix for bug 3327.
4893 - Relays now include a reason for regenerating their descriptors
4894 in an HTTP header when uploading to the authorities. This will
4895 make it easier to debug descriptor-upload issues in the future.
4896 - When starting as root and then changing our UID via the User
4897 control option, and we have a ControlSocket configured, make sure
4898 that the ControlSocket is owned by the same account that Tor will
4899 run under. Implements ticket 3421; fix by Jérémy Bobbio.
4902 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
4903 utility function used in the control-port code). This shouldn't
4904 ever happen unless Tor is completely out of memory, but if it did
4905 happen and Tor somehow recovered from it, Tor could have sent a log
4906 message to a control port in the middle of a reply to a controller
4907 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
4908 - Make 'FetchUselessDescriptors' cause all descriptor types and
4909 all consensus types (including microdescriptors) to get fetched.
4910 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
4913 - Make a new "entry connection" struct as an internal subtype of "edge
4914 connection", to simplify the code and make exit connections smaller.
4917 Changes in version 0.2.2.33 - 2011-09-13
4918 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
4919 TLS handshake that makes relays and bridges that run this new version
4920 reachable from Iran again.
4923 - Avoid an assertion failure when reloading a configuration with
4924 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4925 3923; bugfix on 0.2.2.25-alpha.
4927 o Minor features (security):
4928 - Check for replays of the public-key encrypted portion of an
4929 INTRODUCE1 cell, in addition to the current check for replays of
4930 the g^x value. This prevents a possible class of active attacks
4931 by an attacker who controls both an introduction point and a
4932 rendezvous point, and who uses the malleability of AES-CTR to
4933 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4934 that these attacks are infeasible (requiring the attacker to send
4935 on the order of zettabytes of altered cells in a short interval),
4936 but we'd rather block them off in case there are any classes of
4937 this attack that we missed. Reported by Willem Pinckaers.
4940 - Adjust the expiration time on our SSL session certificates to
4941 better match SSL certs seen in the wild. Resolves ticket 4014.
4942 - Change the default required uptime for a relay to be accepted as
4943 a HSDir (hidden service directory) from 24 hours to 25 hours.
4944 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4945 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4946 authorities to abstain from voting on assignment of the HSDir
4947 consensus flag. Related to bug 2649.
4948 - Update to the September 6 2011 Maxmind GeoLite Country database.
4950 o Minor bugfixes (documentation and log messages):
4951 - Correct the man page to explain that HashedControlPassword and
4952 CookieAuthentication can both be set, in which case either method
4953 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4954 when we decided to allow these config options to both be set. Issue
4956 - Demote the 'replay detected' log message emitted when a hidden
4957 service receives the same Diffie-Hellman public key in two different
4958 INTRODUCE2 cells to info level. A normal Tor client can cause that
4959 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4960 fixes part of bug 2442.
4961 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4962 level. There is nothing that a hidden service's operator can do
4963 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4965 - Clarify a log message specifying the characters permitted in
4966 HiddenServiceAuthorizeClient client names. Previously, the log
4967 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4968 given the impression that every ASCII character between "+" and "_"
4969 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4972 - Provide a substitute implementation of lround() for MSVC, which
4973 apparently lacks it. Patch from Gisle Vanem.
4974 - Clean up some code issues that prevented Tor from building on older
4975 BSDs. Fixes bug 3894; reported by "grarpamp".
4976 - Search for a platform-specific version of "ar" when cross-compiling.
4977 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4980 Changes in version 0.2.3.3-alpha - 2011-09-01
4981 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
4982 security, and provides client-side support for the microdescriptor
4983 and optimistic data features introduced earlier in the 0.2.3.x
4984 series. It also includes numerous critical bugfixes in the (optional)
4985 bufferevent-based networking backend.
4987 o Major features (stream isolation):
4988 - You can now configure Tor so that streams from different
4989 applications are isolated on different circuits, to prevent an
4990 attacker who sees your streams as they leave an exit node from
4991 linking your sessions to one another. To do this, choose some way
4992 to distinguish the applications: have them connect to different
4993 SocksPorts, or have one of them use SOCKS4 while the other uses
4994 SOCKS5, or have them pass different authentication strings to the
4995 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4996 degree of isolation you need. This implements Proposal 171.
4997 - There's a new syntax for specifying multiple client ports (such as
4998 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4999 multiple *Port entries with full addr:port syntax on each.
5000 The old *ListenAddress format is still supported, but you can't
5001 mix it with the new *Port syntax.
5003 o Major features (other):
5004 - Enable microdescriptor fetching by default for clients. This allows
5005 clients to download a much smaller amount of directory information.
5006 To disable it (and go back to the old-style consensus and
5007 descriptors), set "UseMicrodescriptors 0" in your torrc file.
5008 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
5009 "PortForwarding" config option), now supports Windows.
5010 - When using an exit relay running 0.2.3.x, clients can now
5011 "optimistically" send data before the exit relay reports that
5012 the stream has opened. This saves a round trip when starting
5013 connections where the client speaks first (such as web browsing).
5014 This behavior is controlled by a consensus parameter (currently
5015 disabled). To turn it on or off manually, use the "OptimisticData"
5016 torrc option. Implements proposal 181; code by Ian Goldberg.
5018 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
5019 - When using IOCP on Windows, we need to enable Libevent windows
5021 - The IOCP backend now works even when the user has not specified
5022 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
5023 Fixes part of bug 3752.
5024 - Correctly record the bytes we've read and written when using
5025 bufferevents, so that we can include them in our bandwidth history
5026 and advertised bandwidth. Fixes bug 3803.
5027 - Apply rate-limiting only at the bottom of a chain of filtering
5028 bufferevents. This prevents us from filling up internal read
5029 buffers and violating rate-limits when filtering bufferevents
5030 are enabled. Fixes part of bug 3804.
5031 - Add high-watermarks to the output buffers for filtered
5032 bufferevents. This prevents us from filling up internal write
5033 buffers and wasting CPU cycles when filtering bufferevents are
5034 enabled. Fixes part of bug 3804.
5035 - Correctly notice when data has been written from a bufferevent
5036 without flushing it completely. Fixes bug 3805.
5037 - Fix a bug where server-side tunneled bufferevent-based directory
5038 streams would get closed prematurely. Fixes bug 3814.
5039 - Fix a use-after-free error with per-connection rate-limiting
5040 buckets. Fixes bug 3888.
5042 o Major bugfixes (also part of 0.2.2.31-rc):
5043 - If we're configured to write our ControlPorts to disk, only write
5044 them after switching UID and creating the data directory. This way,
5045 we don't fail when starting up with a nonexistent DataDirectory
5046 and a ControlPortWriteToFile setting based on that directory. Fixes
5047 bug 3747; bugfix on Tor 0.2.2.26-beta.
5050 - Added a new CONF_CHANGED event so that controllers can be notified
5051 of any configuration changes made by other controllers, or by the
5052 user. Implements ticket 1692.
5053 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
5054 leak when using bufferevents, and lets Libevent worry about how to
5055 best copy data out of a buffer.
5056 - Replace files in stats/ rather than appending to them. Now that we
5057 include statistics in extra-info descriptors, it makes no sense to
5058 keep old statistics forever. Implements ticket 2930.
5060 o Minor features (build compatibility):
5061 - Limited, experimental support for building with nmake and MSVC.
5062 - Provide a substitute implementation of lround() for MSVC, which
5063 apparently lacks it. Patch from Gisle Vanem.
5065 o Minor features (also part of 0.2.2.31-rc):
5066 - Update to the August 2 2011 Maxmind GeoLite Country database.
5068 o Minor bugfixes (on 0.2.3.x-alpha):
5069 - Fix a spurious warning when parsing SOCKS requests with
5070 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
5071 - Get rid of a harmless warning that could happen on relays running
5072 with bufferevents. The warning was caused by someone doing an http
5073 request to a relay's orport. Also don't warn for a few related
5074 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
5076 o Minor bugfixes (on 2.2.x and earlier):
5077 - Correct the man page to explain that HashedControlPassword and
5078 CookieAuthentication can both be set, in which case either method
5079 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
5080 when we decided to allow these config options to both be set. Issue
5082 - The "--quiet" and "--hush" options now apply not only to Tor's
5083 behavior before logs are configured, but also to Tor's behavior in
5084 the absense of configured logs. Fixes bug 3550; bugfix on
5087 o Minor bugfixes (also part of 0.2.2.31-rc):
5088 - Write several files in text mode, on OSes that distinguish text
5089 mode from binary mode (namely, Windows). These files are:
5090 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
5091 that collect those statistics; 'client_keys' and 'hostname' for
5092 hidden services that use authentication; and (in the tor-gencert
5093 utility) newly generated identity and signing keys. Previously,
5094 we wouldn't specify text mode or binary mode, leading to an
5095 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
5096 the DirRecordUsageByCountry option which would have triggered
5097 the assertion failure was added), although this assertion failure
5098 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
5099 - Selectively disable deprecation warnings on OS X because Lion
5100 started deprecating the shipped copy of openssl. Fixes bug 3643.
5101 - Remove an extra pair of quotation marks around the error
5102 message in control-port STATUS_GENERAL BUG events. Bugfix on
5103 0.1.2.6-alpha; fixes bug 3732.
5104 - When unable to format an address as a string, report its value
5105 as "???" rather than reusing the last formatted address. Bugfix
5108 o Code simplifications and refactoring:
5109 - Rewrite the listener-selection logic so that parsing which ports
5110 we want to listen on is now separate from binding to the ports
5114 - Building Tor with bufferevent support now requires Libevent
5115 2.0.13-stable or later. Previous versions of Libevent had bugs in
5116 SSL-related bufferevents and related issues that would make Tor
5117 work badly with bufferevents. Requiring 2.0.13-stable also allows
5118 Tor with bufferevents to take advantage of Libevent APIs
5119 introduced after 2.0.8-rc.
5122 Changes in version 0.2.2.32 - 2011-08-27
5123 The Tor 0.2.2 release series is dedicated to the memory of Andreas
5124 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
5125 a founder of the PETS community, a leader in our field, a mentor,
5126 and a friend. He left us with these words: "I had the possibility
5127 to contribute to this world that is not as it should be. I hope I
5128 could help in some areas to make the world a better place, and that
5129 I could also encourage other people to be engaged in improving the
5130 world. Please, stay engaged. This world needs you, your love, your
5131 initiative -- now I cannot be part of that anymore."
5133 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
5134 ready. More than two years in the making, this release features improved
5135 client performance and hidden service reliability, better compatibility
5136 for Android, correct behavior for bridges that listen on more than
5137 one address, more extensible and flexible directory object handling,
5138 better reporting of network statistics, improved code security, and
5139 many many other features and bugfixes.
5142 Changes in version 0.2.2.31-rc - 2011-08-17
5143 Tor 0.2.2.31-rc is the second and hopefully final release candidate
5144 for the Tor 0.2.2.x series.
5147 - Remove an extra pair of quotation marks around the error
5148 message in control-port STATUS_GENERAL BUG events. Bugfix on
5149 0.1.2.6-alpha; fixes bug 3732.
5150 - If we're configured to write our ControlPorts to disk, only write
5151 them after switching UID and creating the data directory. This way,
5152 we don't fail when starting up with a nonexistent DataDirectory
5153 and a ControlPortWriteToFile setting based on that directory. Fixes
5154 bug 3747; bugfix on Tor 0.2.2.26-beta.
5157 - Update to the August 2 2011 Maxmind GeoLite Country database.
5160 - Allow GETINFO fingerprint to return a fingerprint even when
5161 we have not yet built a router descriptor. Fixes bug 3577;
5162 bugfix on 0.2.0.1-alpha.
5163 - Write several files in text mode, on OSes that distinguish text
5164 mode from binary mode (namely, Windows). These files are:
5165 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
5166 that collect those statistics; 'client_keys' and 'hostname' for
5167 hidden services that use authentication; and (in the tor-gencert
5168 utility) newly generated identity and signing keys. Previously,
5169 we wouldn't specify text mode or binary mode, leading to an
5170 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
5171 the DirRecordUsageByCountry option which would have triggered
5172 the assertion failure was added), although this assertion failure
5173 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
5174 - Selectively disable deprecation warnings on OS X because Lion
5175 started deprecating the shipped copy of openssl. Fixes bug 3643.
5176 - When unable to format an address as a string, report its value
5177 as "???" rather than reusing the last formatted address. Bugfix
5181 Changes in version 0.2.3.2-alpha - 2011-07-18
5182 Tor 0.2.3.2-alpha introduces two new experimental features:
5183 microdescriptors and pluggable transports. It also continues cleaning
5184 up a variety of recently introduced features.
5187 - Clients can now use microdescriptors instead of regular descriptors
5188 to build circuits. Microdescriptors are authority-generated
5189 summaries of regular descriptors' contents, designed to change
5190 very rarely (see proposal 158 for details). This feature is
5191 designed to save bandwidth, especially for clients on slow internet
5192 connections. It's off by default for now, since nearly no caches
5193 support it, but it will be on-by-default for clients in a future
5194 version. You can use the UseMicrodescriptors option to turn it on.
5195 - Tor clients using bridges can now be configured to use a separate
5196 'transport' proxy for each bridge. This approach helps to resist
5197 censorship by allowing bridges to use protocol obfuscation
5198 plugins. It implements part of proposal 180. Implements ticket 2841.
5199 - While we're trying to bootstrap, record how many TLS connections
5200 fail in each state, and report which states saw the most failures
5201 in response to any bootstrap failures. This feature may speed up
5202 diagnosis of censorship events. Implements ticket 3116.
5204 o Major bugfixes (on 0.2.3.1-alpha):
5205 - When configuring a large set of nodes in EntryNodes (as with
5206 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
5207 random subset to be guards, and choose them in random
5208 order. Fixes bug 2798.
5209 - Tor could crash when remembering a consensus in a non-used consensus
5210 flavor without having a current consensus set. Fixes bug 3361.
5211 - Comparing an unknown address to a microdescriptor's shortened exit
5212 policy would always give a "rejected" result. Fixes bug 3599.
5213 - Using microdescriptors as a client no longer prevents Tor from
5214 uploading and downloading hidden service descriptors. Fixes
5218 - Allow nameservers with IPv6 address. Resolves bug 2574.
5219 - Accept attempts to include a password authenticator in the
5220 handshake, as supported by SOCKS5. This handles SOCKS clients that
5221 don't know how to omit a password when authenticating. Resolves
5223 - When configuring a large set of nodes in EntryNodes, and there are
5224 enough of them listed as Guard so that we don't need to consider
5225 the non-guard entries, prefer the ones listed with the Guard flag.
5226 - Check for and recover from inconsistency in the microdescriptor
5227 cache. This will make it harder for us to accidentally free a
5228 microdescriptor without removing it from the appropriate data
5229 structures. Fixes issue 3135; issue noted by "wanoskarnet".
5230 - Log SSL state transitions at log level DEBUG, log domain
5231 HANDSHAKE. This can be useful for debugging censorship events.
5232 Implements ticket 3264.
5233 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
5234 implements ticket 3439.
5236 o Minor bugfixes (on 0.2.3.1-alpha):
5237 - Do not free all general-purpose regular descriptors just
5238 because microdescriptor use is enabled. Fixes bug 3113.
5239 - Correctly link libevent_openssl when --enable-static-libevent
5240 is passed to configure. Fixes bug 3118.
5241 - Bridges should not complain during their heartbeat log messages that
5242 they are unlisted in the consensus: that's more or less the point
5243 of being a bridge. Fixes bug 3183.
5244 - Report a SIGNAL event to controllers when acting on a delayed
5245 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
5246 event to the controller if we acted on a SIGNAL NEWNYM command
5247 immediately, and otherwise not report a SIGNAL event for the
5248 command at all. Fixes bug 3349.
5249 - Fix a crash when handling the SIGNAL controller command or
5250 reporting ERR-level status events with bufferevents enabled. Found
5251 by Robert Ransom. Fixes bug 3367.
5252 - Always ship the tor-fw-helper manpage in our release tarballs.
5253 Fixes bug 3389. Reported by Stephen Walker.
5254 - Fix a class of double-mark-for-close bugs when bufferevents
5255 are enabled. Fixes bug 3403.
5256 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
5257 - Add SIGNAL to the list returned by the 'GETINFO events/names'
5258 control-port command. Fixes part of bug 3465.
5259 - Prevent using negative indices during unit test runs when read_all()
5260 fails. Spotted by coverity.
5261 - Fix a rare memory leak when checking the nodelist without it being
5262 present. Found by coverity.
5263 - Only try to download a microdescriptor-flavored consensus from
5264 a directory cache that provides them.
5266 o Minor bugfixes (on 0.2.2.x and earlier):
5267 - Assert that hidden-service-related operations are not performed
5268 using single-hop circuits. Previously, Tor would assert that
5269 client-side streams are not attached to single-hop circuits,
5270 but not that other sensitive operations on the client and service
5271 side are not performed using single-hop circuits. Fixes bug 3332;
5273 - Don't publish a new relay descriptor when we reload our onion key,
5274 unless the onion key has actually changed. Fixes bug 3263 and
5275 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
5276 - Allow GETINFO fingerprint to return a fingerprint even when
5277 we have not yet built a router descriptor. Fixes bug 3577;
5278 bugfix on 0.2.0.1-alpha.
5279 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
5280 on 0.2.2.4-alpha; fixes bug 3427.
5282 o Code simplification and refactoring:
5283 - Use tor_sscanf() in place of scanf() in more places through the
5284 code. This makes us a little more locale-independent, and
5285 should help shut up code-analysis tools that can't tell
5286 a safe sscanf string from a dangerous one.
5287 - Use tt_assert(), not tor_assert(), for checking for test failures.
5288 This makes the unit tests more able to go on in the event that
5290 - Split connection_about_to_close() into separate functions for each
5294 - On Windows, we now define the _WIN32_WINNT macros only if they
5295 are not already defined. This lets the person building Tor decide,
5296 if they want, to require a later version of Windows.
5299 Changes in version 0.2.2.30-rc - 2011-07-07
5300 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
5301 series. It fixes a few smaller bugs, but generally appears stable.
5302 Please test it and let us know whether it is!
5305 - Send a SUCCEEDED stream event to the controller when a reverse
5306 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
5307 discovered by katmagic.
5308 - Always NUL-terminate the sun_path field of a sockaddr_un before
5309 passing it to the kernel. (Not a security issue: kernels are
5310 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5311 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5312 - Don't stack-allocate the list of supplementary GIDs when we're
5313 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
5314 could take up to 256K, which is way too much stack. Found by
5315 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
5316 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
5317 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
5318 fixes part of bug 3465.
5319 - Fix a memory leak when receiving a descriptor for a hidden
5320 service we didn't ask for. Found by Coverity; CID #30. Bugfix
5324 - Update to the July 1 2011 Maxmind GeoLite Country database.
5327 Changes in version 0.2.2.29-beta - 2011-06-20
5328 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
5329 have bridge lines in their torrc but don't want to use them; gets
5330 us closer to having the control socket feature working on Debian;
5331 and fixes a variety of smaller bugs.
5334 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
5335 When we changed the default behavior to "use bridges if any
5336 are listed in the torrc", we surprised users who had bridges
5337 in their torrc files but who didn't actually want to use them.
5338 Partial resolution for bug 3354.
5341 - Don't attach new streams to old rendezvous circuits after SIGNAL
5342 NEWNYM. Previously, we would keep using an existing rendezvous
5343 circuit if it remained open (i.e. if it were kept open by a
5344 long-lived stream, or if a new stream were attached to it before
5345 Tor could notice that it was old and no longer in use). Bugfix on
5346 0.1.1.15-rc; fixes bug 3375.
5349 - Fix a bug when using ControlSocketsGroupWritable with User. The
5350 directory's group would be checked against the current group, not
5351 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
5352 bugfix on 0.2.2.26-beta.
5353 - Make connection_printf_to_buf()'s behaviour sane. Its callers
5354 expect it to emit a CRLF iff the format string ends with CRLF;
5355 it actually emitted a CRLF iff (a) the format string ended with
5356 CRLF or (b) the resulting string was over 1023 characters long or
5357 (c) the format string did not end with CRLF *and* the resulting
5358 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
5359 fixes part of bug 3407.
5360 - Make send_control_event_impl()'s behaviour sane. Its callers
5361 expect it to always emit a CRLF at the end of the string; it
5362 might have emitted extra control characters as well. Bugfix on
5363 0.1.1.9-alpha; fixes another part of bug 3407.
5364 - Make crypto_rand_int() check the value of its input correctly.
5365 Previously, it accepted values up to UINT_MAX, but could return a
5366 negative number if given a value above INT_MAX+1. Found by George
5367 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
5368 - Avoid a segfault when reading a malformed circuit build state
5369 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
5371 - When asked about a DNS record type we don't support via a
5372 client DNSPort, reply with NOTIMPL rather than an empty
5373 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
5374 - Fix a rare memory leak during stats writing. Found by coverity.
5377 - Update to the June 1 2011 Maxmind GeoLite Country database.
5379 o Code simplifications and refactoring:
5380 - Remove some dead code as indicated by coverity.
5381 - Remove a few dead assignments during router parsing. Found by
5383 - Add some forgotten return value checks during unit tests. Found
5385 - Don't use 1-bit wide signed bit fields. Found by coverity.
5388 Changes in version 0.2.2.28-beta - 2011-06-04
5389 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
5390 fixed a big bug in whether relays stay in the consensus consistently,
5391 we moved closer to handling bridges and hidden services correctly,
5392 and we started the process of better handling the dreaded "my Vidalia
5393 died, and now my Tor demands a password when I try to reconnect to it"
5397 - Don't decide to make a new descriptor when receiving a HUP signal.
5398 This bug has caused a lot of 0.2.2.x relays to disappear from the
5399 consensus periodically. Fixes the most common case of triggering
5400 bug 1810; bugfix on 0.2.2.7-alpha.
5401 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
5402 - Don't try to build descriptors if "ORPort auto" is set and we
5403 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
5405 - Resolve a crash that occurred when setting BridgeRelay to 1 with
5406 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
5407 - Apply circuit timeouts to opened hidden-service-related circuits
5408 based on the correct start time. Previously, we would apply the
5409 circuit build timeout based on time since the circuit's creation;
5410 it was supposed to be applied based on time since the circuit
5411 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
5412 - Use the same circuit timeout for client-side introduction
5413 circuits as for other four-hop circuits, rather than the timeout
5414 for single-hop directory-fetch circuits; the shorter timeout may
5415 have been appropriate with the static circuit build timeout in
5416 0.2.1.x and earlier, but caused many hidden service access attempts
5417 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
5418 on 0.2.2.2-alpha; fixes another part of bug 1297.
5419 - In ticket 2511 we fixed a case where you could use an unconfigured
5420 bridge if you had configured it as a bridge the last time you ran
5421 Tor. Now fix another edge case: if you had configured it as a bridge
5422 but then switched to a different bridge via the controller, you
5423 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
5427 - Add an __OwningControllerProcess configuration option and a
5428 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
5429 that when it exits, Tor will shut down. Implements feature 3049.
5430 - If "UseBridges 1" is set and no bridges are configured, Tor will
5431 now refuse to build any circuits until some bridges are set.
5432 If "UseBridges auto" is set, Tor will use bridges if they are
5433 configured and we are not running as a server, but otherwise will
5434 make circuits as usual. The new default is "auto". Patch by anonym,
5435 so the Tails LiveCD can stop automatically revealing you as a Tor
5439 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5440 - Remove a trailing asterisk from "exit-policy/default" in the
5441 output of the control port command "GETINFO info/names". Bugfix
5443 - Use a wide type to hold sockets when built for 64-bit Windows builds.
5445 - Warn when the user configures two HiddenServiceDir lines that point
5446 to the same directory. Bugfix on 0.0.6 (the version introducing
5447 HiddenServiceDir); fixes bug 3289.
5448 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
5449 part of bug 2748; bugfix on 0.2.0.10-alpha.
5450 - Log malformed requests for rendezvous descriptors as protocol
5451 warnings, not warnings. Also, use a more informative log message
5452 in case someone sees it at log level warning without prior
5453 info-level messages. Fixes the other part of bug 2748; bugfix
5455 - Clear the table recording the time of the last request for each
5456 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
5457 Previously, we would clear our HS descriptor cache on SIGNAL
5458 NEWNYM, but if we had previously retrieved a descriptor (or tried
5459 to) from every directory responsible for it, we would refuse to
5460 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
5462 - Fix a log message that said "bits" while displaying a value in
5463 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
5465 - When checking for 1024-bit keys, check for 1024 bits, not 128
5466 bytes. This allows Tor to correctly discard keys of length 1017
5467 through 1023. Bugfix on 0.0.9pre5.
5470 - Relays now log the reason for publishing a new relay descriptor,
5471 so we have a better chance of hunting down instances of bug 1810.
5472 Resolves ticket 3252.
5473 - Revise most log messages that refer to nodes by nickname to
5474 instead use the "$key=nickname at address" format. This should be
5475 more useful, especially since nicknames are less and less likely
5476 to be unique. Resolves ticket 3045.
5477 - Log (at info level) when purging pieces of hidden-service-client
5478 state because of SIGNAL NEWNYM.
5481 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5482 anything since 0.2.1.16-rc.
5485 Changes in version 0.2.2.27-beta - 2011-05-18
5486 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
5487 release, and also adds a few more general bugfixes.
5490 - Fix a crash bug when changing bridges in a running Tor process.
5491 Fixes bug 3213; bugfix on 0.2.2.26-beta.
5492 - When the controller configures a new bridge, don't wait 10 to 60
5493 seconds before trying to fetch its descriptor. Bugfix on
5494 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
5497 - Require that onion keys have exponent 65537 in microdescriptors too.
5498 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
5499 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
5500 Changed the limit to 512 characters by removing base64 newlines.
5501 Fixes bug 2752. Fix by Michael Yakubovich.
5502 - When a client starts or stops using bridges, never use a circuit
5503 that was built before the configuration change. This behavior could
5504 put at risk a user who uses bridges to ensure that her traffic
5505 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
5509 Changes in version 0.2.2.26-beta - 2011-05-17
5510 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
5511 also introduces a new "socksport auto" approach that should make it
5512 easier to run multiple Tors on the same system, and does a lot of
5513 cleanup to get us closer to a release candidate.
5515 o Security/privacy fixes:
5516 - Replace all potentially sensitive memory comparison operations
5517 with versions whose runtime does not depend on the data being
5518 compared. This will help resist a class of attacks where an
5519 adversary can use variations in timing information to learn
5520 sensitive data. Fix for one case of bug 3122. (Safe memcmp
5521 implementation by Robert Ransom based partially on code by DJB.)
5522 - When receiving a hidden service descriptor, check that it is for
5523 the hidden service we wanted. Previously, Tor would store any
5524 hidden service descriptors that a directory gave it, whether it
5525 wanted them or not. This wouldn't have let an attacker impersonate
5526 a hidden service, but it did let directories pre-seed a client
5527 with descriptors that it didn't want. Bugfix on 0.0.6.
5528 - On SIGHUP, do not clear out all TrackHostExits mappings, client
5529 DNS cache entries, and virtual address mappings: that's what
5530 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
5533 - The options SocksPort, ControlPort, and so on now all accept a
5534 value "auto" that opens a socket on an OS-selected port. A
5535 new ControlPortWriteToFile option tells Tor to write its
5536 actual control port or ports to a chosen file. If the option
5537 ControlPortFileGroupReadable is set, the file is created as
5538 group-readable. Now users can run two Tor clients on the same
5539 system without needing to manually mess with parameters. Resolves
5540 part of ticket 3076.
5541 - Set SO_REUSEADDR on all sockets, not just listeners. This should
5542 help busy exit nodes avoid running out of useable ports just
5543 because all the ports have been used in the near past. Resolves
5547 - New "GETINFO net/listeners/(type)" controller command to return
5548 a list of addresses and ports that are bound for listeners for a
5549 given connection type. This is useful when the user has configured
5550 "SocksPort auto" and the controller needs to know which port got
5551 chosen. Resolves another part of ticket 3076.
5552 - Add a new ControlSocketsGroupWritable configuration option: when
5553 it is turned on, ControlSockets are group-writeable by the default
5554 group of the current user. Patch by Jérémy Bobbio; implements
5556 - Tor now refuses to create a ControlSocket in a directory that is
5557 world-readable (or group-readable if ControlSocketsGroupWritable
5558 is 0). This is necessary because some operating systems do not
5559 enforce permissions on an AF_UNIX sockets. Permissions on the
5560 directory holding the socket, however, seems to work everywhere.
5561 - Rate-limit a warning about failures to download v2 networkstatus
5562 documents. Resolves part of bug 1352.
5563 - Backport code from 0.2.3.x that allows directory authorities to
5564 clean their microdescriptor caches. Needed to resolve bug 2230.
5565 - When an HTTPS proxy reports "403 Forbidden", we now explain
5566 what it means rather than calling it an unexpected status code.
5567 Closes bug 2503. Patch from Michael Yakubovich.
5568 - Update to the May 1 2011 Maxmind GeoLite Country database.
5571 - Authorities now clean their microdesc cache periodically and when
5572 reading from disk initially, not only when adding new descriptors.
5573 This prevents a bug where we could lose microdescriptors. Bugfix
5574 on 0.2.2.6-alpha. Fixes bug 2230.
5575 - Do not crash when our configuration file becomes unreadable, for
5576 example due to a permissions change, between when we start up
5577 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5579 - Avoid a bug that would keep us from replacing a microdescriptor
5580 cache on Windows. (We would try to replace the file while still
5581 holding it open. That's fine on Unix, but Windows doesn't let us
5582 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
5583 - Add missing explanations for the authority-related torrc options
5584 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
5585 man page. Resolves issue 2379.
5586 - As an authority, do not upload our own vote or signature set to
5587 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
5588 it would get flagged as a duplicate. Resolves bug 3026.
5589 - Accept hidden service descriptors if we think we might be a hidden
5590 service directory, regardless of what our consensus says. This
5591 helps robustness, since clients and hidden services can sometimes
5592 have a more up-to-date view of the network consensus than we do,
5593 and if they think that the directory authorities list us a HSDir,
5594 we might actually be one. Related to bug 2732; bugfix on
5596 - When a controller changes TrackHostExits, remove mappings for
5597 hosts that should no longer have their exits tracked. Bugfix on
5599 - When a controller changes VirtualAddrNetwork, remove any mappings
5600 for hosts that were automapped to the old network. Bugfix on
5602 - When a controller changes one of the AutomapHosts* options, remove
5603 any mappings for hosts that should no longer be automapped. Bugfix
5605 - Do not reset the bridge descriptor download status every time we
5606 re-parse our configuration or get a configuration change. Fixes
5607 bug 3019; bugfix on 0.2.0.3-alpha.
5609 o Minor bugfixes (code cleanup):
5610 - When loading the microdesc journal, remember its current size.
5611 In 0.2.2, this helps prevent the microdesc journal from growing
5612 without limit on authorities (who are the only ones to use it in
5613 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5614 Fix posted by "cypherpunks."
5615 - The microdesc journal is supposed to get rebuilt only if it is
5616 at least _half_ the length of the store, not _twice_ the length
5617 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5618 - Fix a potential null-pointer dereference while computing a
5619 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
5621 - Avoid a possible null-pointer dereference when rebuilding the mdesc
5622 cache without actually having any descriptors to cache. Bugfix on
5623 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
5624 - If we fail to compute the identity digest of a v3 legacy keypair,
5625 warn, and don't use a buffer-full of junk instead. Bugfix on
5626 0.2.1.1-alpha; fixes bug 3106.
5627 - Resolve an untriggerable issue in smartlist_string_num_isin(),
5628 where if the function had ever in the future been used to check
5629 for the presence of a too-large number, it would have given an
5630 incorrect result. (Fortunately, we only used it for 16-bit
5631 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
5632 - Require that introduction point keys and onion handshake keys
5633 have a public exponent of 65537. Starts to fix bug 3207; bugfix
5637 - Caches no longer download and serve v2 networkstatus documents
5638 unless FetchV2Networkstatus flag is set: these documents haven't
5639 haven't been used by clients or relays since 0.2.0.x. Resolves
5643 Changes in version 0.2.3.1-alpha - 2011-05-05
5644 Tor 0.2.3.1-alpha adds some new experimental features, including support
5645 for an improved network IO backend, IOCP networking on Windows,
5646 microdescriptor caching, "fast-start" support for streams, and automatic
5647 home router configuration. There are also numerous internal improvements
5648 to try to make the code easier for developers to work with.
5650 This is the first alpha release in a new series, so expect there to be
5651 bugs. Users who would rather test out a more stable branch should
5652 stay with 0.2.2.x for now.
5655 - Tor can now optionally build with the "bufferevents" buffered IO
5656 backend provided by Libevent 2. To use this feature, make sure you
5657 have the latest possible version of Libevent, and pass the
5658 --enable-bufferevents flag to configure when building Tor from
5659 source. This feature will make our networking code more flexible,
5660 let us stack layers on each other, and let us use more efficient
5661 zero-copy transports where available.
5662 - As an experimental feature, Tor can use IOCP for networking on Windows.
5663 Once this code is tuned and optimized, it promises much better
5664 performance than the select-based backend we've used in the past. To
5665 try this feature, you must build Tor with Libevent 2, configure Tor
5666 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
5667 your torrc. There are known bugs here: only try this if you can help
5668 debug it as it breaks.
5669 - The EntryNodes option can now include country codes like {de} or IP
5670 addresses or network masks. Previously we had disallowed these options
5671 because we didn't have an efficient way to keep the list up to
5672 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
5673 - Exit nodes now accept and queue data on not-yet-connected streams.
5674 Previously, the client wasn't allowed to send data until the stream was
5675 connected, which slowed down all connections. This change will enable
5676 clients to perform a "fast-start" on streams and send data without
5677 having to wait for a confirmation that the stream has opened. (Patch
5678 from Ian Goldberg; implements the server side of Proposal 174.)
5679 - Tor now has initial support for automatic port mapping on the many
5680 home routers that support NAT-PMP or UPnP. (Not yet supported on
5681 Windows). To build the support code, you'll need to have libnatpnp
5682 library and/or the libminiupnpc library, and you'll need to enable the
5683 feature specifically by passing "--enable-upnp" and/or
5684 "--enable-natpnp" to configure. To turn it on, use the new
5685 PortForwarding option.
5686 - Caches now download, cache, and serve multiple "flavors" of the
5687 consensus, including a flavor that describes microdescriptors.
5688 - Caches now download, cache, and serve microdescriptors -- small
5689 summaries of router descriptors that are authenticated by all of the
5690 directory authorities. Once enough caches are running this code,
5691 clients will be able to save significant amounts of directory bandwidth
5692 by downloading microdescriptors instead of router descriptors.
5695 - Make logging resolution configurable with a new LogTimeGranularity
5696 option, and change the default from 1 millisecond to 1 second.
5697 Implements enhancement 1668.
5698 - We log which torrc file we're using on startup. Implements ticket
5700 - Ordinarily, Tor does not count traffic from private addresses (like
5701 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
5702 There is now a new option, CountPrivateBandwidth, to disable this
5703 behavior. Patch from Daniel Cagara.
5704 - New --enable-static-tor configure option for building Tor as
5705 statically as possible. Idea, general hackery and thoughts from
5706 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
5708 - If you set the NumCPUs option to 0, Tor will now try to detect how
5709 many CPUs you have. This is the new default behavior.
5710 - Turn on directory request statistics by default and include them in
5711 extra-info descriptors. Don't break if we have no GeoIP database.
5712 - Relays that set "ConnDirectionStatistics 1" write statistics on the
5713 bidirectional use of connections to disk every 24 hours.
5714 - Add a GeoIP file digest to the extra-info descriptor. Implements
5716 - The NodeFamily option -- which let you declare that you want to
5717 consider nodes to be part of a family whether they list themselves
5718 that way or not -- now allows IP address ranges and country codes.
5719 - Add a new 'Heartbeat' log message type to periodically log a message
5720 describing Tor's status at level Notice. This feature is meant for
5721 operators who log at notice, and want to make sure that their Tor
5722 server is still working. Implementation by George Kadianakis.
5724 o Minor bugfixes (on 0.2.2.25-alpha):
5725 - When loading the microdesc journal, remember its current size.
5726 In 0.2.2, this helps prevent the microdesc journal from growing
5727 without limit on authorities (who are the only ones to use it in
5728 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5729 Fix posted by "cypherpunks."
5730 - The microdesc journal is supposed to get rebuilt only if it is
5731 at least _half_ the length of the store, not _twice_ the length
5732 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5733 - If as an authority we fail to compute the identity digest of a v3
5734 legacy keypair, warn, and don't use a buffer-full of junk instead.
5735 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
5736 - Authorities now clean their microdesc cache periodically and when
5737 reading from disk initially, not only when adding new descriptors.
5738 This prevents a bug where we could lose microdescriptors. Bugfix
5741 o Minor features (controller):
5742 - Add a new SIGNAL event to the controller interface so that
5743 controllers can be notified when Tor handles a signal. Resolves
5744 issue 1955. Patch by John Brooks.
5745 - Add a new GETINFO option to get total bytes read and written. Patch
5746 from pipe, revised by atagar. Resolves ticket 2345.
5747 - Implement some GETINFO controller fields to provide information about
5748 the Tor process's pid, euid, username, and resource limits.
5751 - Our build system requires automake 1.6 or later to create the
5752 Makefile.in files. Previously, you could have used 1.4.
5753 This only affects developers and people building Tor from git;
5754 people who build Tor from the source distribution without changing
5755 the Makefile.am files should be fine.
5756 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
5757 so on. This is more robust against some of the failure modes
5758 associated with running the autotools pieces on their own.
5760 o Minor packaging issues:
5761 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
5762 already created. Patch from Andreas Stieger. Fixes bug 2573.
5764 o Code simplifications and refactoring:
5765 - A major revision to our internal node-selecting and listing logic.
5766 Tor already had at least two major ways to look at the question of
5767 "which Tor servers do we know about": a list of router descriptors,
5768 and a list of entries in the current consensus. With
5769 microdescriptors, we're adding a third. Having so many systems
5770 without an abstraction layer over them was hurting the codebase.
5771 Now, we have a new "node_t" abstraction that presents a consistent
5772 interface to a client's view of a Tor node, and holds (nearly) all
5773 of the mutable state formerly in routerinfo_t and routerstatus_t.
5774 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
5775 no longer link against Libevent: they never used it, but
5776 our library structure used to force them to link it.
5779 - Remove some old code to work around even older versions of Tor that
5780 used forked processes to handle DNS requests. Such versions of Tor
5781 are no longer in use as servers.
5783 o Documentation fixes:
5784 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
5785 - Add missing documentation for the authority-related torrc options
5786 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
5790 Changes in version 0.2.2.25-alpha - 2011-04-29
5791 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
5792 robust, routers no longer overreport their bandwidth, Win7 should crash
5793 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
5794 now prevents hidden service-related activity from being linkable. It
5795 provides more information to Vidalia so you can see if your bridge is
5796 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
5797 StrictNodes configuration options to make them more reliable, more
5798 understandable, and more regularly applied. If you use those options,
5799 please see the revised documentation for them in the manual page.
5802 - Relays were publishing grossly inflated bandwidth values because
5803 they were writing their state files wrong--now they write the
5804 correct value. Also, resume reading bandwidth history from the
5805 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
5806 - Improve hidden service robustness: When we find that we have
5807 extended a hidden service's introduction circuit to a relay not
5808 listed as an introduction point in the HS descriptor we currently
5809 have, retry with an introduction point from the current
5810 descriptor. Previously we would just give up. Fixes bugs 1024 and
5811 1930; bugfix on 0.2.0.10-alpha.
5812 - Clients now stop trying to use an exit node associated with a given
5813 destination by TrackHostExits if they fail to reach that exit node.
5814 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
5815 - Fix crash bug on platforms where gmtime and localtime can return
5816 NULL. Windows 7 users were running into this one. Fixes part of bug
5817 2077. Bugfix on all versions of Tor. Found by boboper.
5819 o Security and stability fixes:
5820 - Don't double-free a parsable, but invalid, microdescriptor, even if
5821 it is followed in the blob we're parsing by an unparsable
5822 microdescriptor. Fixes an issue reported in a comment on bug 2954.
5823 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
5824 - If the Nickname configuration option isn't given, Tor would pick a
5825 nickname based on the local hostname as the nickname for a relay.
5826 Because nicknames are not very important in today's Tor and the
5827 "Unnamed" nickname has been implemented, this is now problematic
5828 behavior: It leaks information about the hostname without being
5829 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
5830 introduced the Unnamed nickname. Reported by tagnaq.
5831 - Fix an uncommon assertion failure when running with DNSPort under
5832 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5833 - Avoid linkability based on cached hidden service descriptors: forget
5834 all hidden service descriptors cached as a client when processing a
5835 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5838 - Export GeoIP information on bridge usage to controllers even if we
5839 have not yet been running for 24 hours. Now Vidalia bridge operators
5840 can get more accurate and immediate feedback about their
5841 contributions to the network.
5843 o Major features and bugfixes (node selection):
5844 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
5845 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
5846 options. Previously, we had been ambiguous in describing what
5847 counted as an "exit" node, and what operations exactly "StrictNodes
5848 0" would permit. This created confusion when people saw nodes built
5849 through unexpected circuits, and made it hard to tell real bugs from
5850 surprises. Now the intended behavior is:
5851 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
5852 a node that delivers user traffic outside the Tor network.
5853 . "Entry", in the context of EntryNodes, means a node used as the
5854 first hop of a multihop circuit. It doesn't include direct
5855 connections to directory servers.
5856 . "ExcludeNodes" applies to all nodes.
5857 . "StrictNodes" changes the behavior of ExcludeNodes only. When
5858 StrictNodes is set, Tor should avoid all nodes listed in
5859 ExcludeNodes, even when it will make user requests fail. When
5860 StrictNodes is *not* set, then Tor should follow ExcludeNodes
5861 whenever it can, except when it must use an excluded node to
5862 perform self-tests, connect to a hidden service, provide a
5863 hidden service, fulfill a .exit request, upload directory
5864 information, or fetch directory information.
5865 Collectively, the changes to implement the behavior fix bug 1090.
5866 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
5867 a node is listed in both, it's treated as excluded.
5868 - ExcludeNodes now applies to directory nodes -- as a preference if
5869 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
5870 Don't exclude all the directory authorities and set StrictNodes to 1
5871 unless you really want your Tor to break.
5872 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
5873 - ExcludeExitNodes now overrides .exit requests.
5874 - We don't use bridges listed in ExcludeNodes.
5875 - When StrictNodes is 1:
5876 . We now apply ExcludeNodes to hidden service introduction points
5877 and to rendezvous points selected by hidden service users. This
5878 can make your hidden service less reliable: use it with caution!
5879 . If we have used ExcludeNodes on ourself, do not try relay
5880 reachability self-tests.
5881 . If we have excluded all the directory authorities, we will not
5882 even try to upload our descriptor if we're a relay.
5883 . Do not honor .exit requests to an excluded node.
5884 - Remove a misfeature that caused us to ignore the Fast/Stable flags
5885 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
5886 - When the set of permitted nodes changes, we now remove any mappings
5887 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
5889 - We never cannibalize a circuit that had excluded nodes on it, even
5890 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
5891 - Revert a change where we would be laxer about attaching streams to
5892 circuits than when building the circuits. This was meant to prevent
5893 a set of bugs where streams were never attachable, but our improved
5894 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
5895 - Keep track of how many times we launch a new circuit to handle a
5896 given stream. Too many launches could indicate an inconsistency
5897 between our "launch a circuit to handle this stream" logic and our
5898 "attach this stream to one of the available circuits" logic.
5899 - Improve log messages related to excluded nodes.
5902 - Fix a spurious warning when moving from a short month to a long
5903 month on relays with month-based BandwidthAccounting. Bugfix on
5904 0.2.2.17-alpha; fixes bug 3020.
5905 - When a client finds that an origin circuit has run out of 16-bit
5906 stream IDs, we now mark it as unusable for new streams. Previously,
5907 we would try to close the entire circuit. Bugfix on 0.0.6.
5908 - Add a forgotten cast that caused a compile warning on OS X 10.6.
5909 Bugfix on 0.2.2.24-alpha.
5910 - Be more careful about reporting the correct error from a failed
5911 connect() system call. Under some circumstances, it was possible to
5912 look at an incorrect value for errno when sending the end reason.
5913 Bugfix on 0.1.0.1-rc.
5914 - Correctly handle an "impossible" overflow cases in connection byte
5915 counting, where we write or read more than 4GB on an edge connection
5916 in a single second. Bugfix on 0.1.2.8-beta.
5917 - Correct the warning displayed when a rendezvous descriptor exceeds
5918 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5920 - Clients and hidden services now use HSDir-flagged relays for hidden
5921 service descriptor downloads and uploads even if the relays have no
5922 DirPort set and the client has disabled TunnelDirConns. This will
5923 eventually allow us to give the HSDir flag to relays with no
5924 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5925 - Downgrade "no current certificates known for authority" message from
5926 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5927 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
5928 2917. Bugfix on 0.1.1.1-alpha.
5929 - Only limit the lengths of single HS descriptors, even when multiple
5930 HS descriptors are published to an HSDir relay in a single POST
5931 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5932 - Write the current time into the LastWritten line in our state file,
5933 rather than the time from the previous write attempt. Also, stop
5934 trying to use a time of -1 in our log statements. Fixes bug 3039;
5935 bugfix on 0.2.2.14-alpha.
5936 - Be more consistent in our treatment of file system paths. "~" should
5937 get expanded to the user's home directory in the Log config option.
5938 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
5939 feature for the -f and --DataDirectory options.
5942 - Make sure every relay writes a state file at least every 12 hours.
5943 Previously, a relay could go for weeks without writing its state
5944 file, and on a crash could lose its bandwidth history, capacity
5945 estimates, client country statistics, and so on. Addresses bug 3012.
5946 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5947 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5948 clients are already deprecated because of security bugs.
5949 - Don't allow v0 hidden service authorities to act as clients.
5950 Required by fix for bug 3000.
5951 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5952 by fix for bug 3000.
5953 - Ensure that no empty [dirreq-](read|write)-history lines are added
5954 to an extrainfo document. Implements ticket 2497.
5956 o Code simplification and refactoring:
5957 - Remove workaround code to handle directory responses from servers
5958 that had bug 539 (they would send HTTP status 503 responses _and_
5959 send a body too). Since only server versions before
5960 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5961 keep the workaround in place.
5962 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5963 handling calculations where we have a known amount of clock skew and
5964 an allowed amount of unknown skew. But we only used it in three
5965 places, and we never adjusted the known/unknown skew values. This is
5966 still something we might want to do someday, but if we do, we'll
5967 want to do it differently.
5968 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5969 None of the cases where we did this before were wrong, but by making
5970 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5971 - Use GetTempDir to find the proper temporary directory location on
5972 Windows when generating temporary files for the unit tests. Patch by
5976 Changes in version 0.2.2.24-alpha - 2011-04-08
5977 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
5978 prevented Tor clients from effectively using "multihomed" bridges,
5979 that is, bridges that listen on multiple ports or IP addresses so users
5980 can continue to use some of their addresses even if others get blocked.
5983 - Fix a bug where bridge users who configure the non-canonical
5984 address of a bridge automatically switch to its canonical
5985 address. If a bridge listens at more than one address, it should be
5986 able to advertise those addresses independently and any non-blocked
5987 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
5989 - If you configured Tor to use bridge A, and then quit and
5990 configured Tor to use bridge B instead, it would happily continue
5991 to use bridge A if it's still reachable. While this behavior is
5992 a feature if your goal is connectivity, in some scenarios it's a
5993 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5994 - Directory authorities now use data collected from their own
5995 uptime observations when choosing whether to assign the HSDir flag
5996 to relays, instead of trusting the uptime value the relay reports in
5997 its descriptor. This change helps prevent an attack where a small
5998 set of nodes with frequently-changing identity keys can blackhole
5999 a hidden service. (Only authorities need upgrade; others will be
6000 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
6003 - When we restart our relay, we might get a successful connection
6004 from the outside before we've started our reachability tests,
6005 triggering a warning: "ORPort found reachable, but I have no
6006 routerinfo yet. Failing to inform controller of success." This
6007 bug was harmless unless Tor is running under a controller
6008 like Vidalia, in which case the controller would never get a
6009 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
6011 - Make directory authorities more accurate at recording when
6012 relays that have failed several reachability tests became
6013 unreachable, so we can provide more accuracy at assigning Stable,
6014 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
6015 - Fix an issue that prevented static linking of libevent on
6016 some platforms (notably Linux). Fixes bug 2698; bugfix on
6017 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
6018 the --with-static-libevent configure option).
6019 - We now ask the other side of a stream (the client or the exit)
6020 for more data on that stream when the amount of queued data on
6021 that stream dips low enough. Previously, we wouldn't ask the
6022 other side for more data until either it sent us more data (which
6023 it wasn't supposed to do if it had exhausted its window!) or we
6024 had completely flushed all our queued data. This flow control fix
6025 should improve throughput. Fixes bug 2756; bugfix on the earliest
6026 released versions of Tor (svn commit r152).
6027 - Avoid a double-mark-for-free warning when failing to attach a
6028 transparent proxy connection. (We thought we had fixed this in
6029 0.2.2.23-alpha, but it turns out our fix was checking the wrong
6030 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
6031 bug) and 0.2.2.23-alpha (the incorrect fix).
6032 - When warning about missing zlib development packages during compile,
6033 give the correct package names. Bugfix on 0.2.0.1-alpha.
6036 - Directory authorities now log the source of a rejected POSTed v3
6038 - Make compilation with clang possible when using
6039 --enable-gcc-warnings by removing two warning options that clang
6040 hasn't implemented yet and by fixing a few warnings. Implements
6042 - When expiring circuits, use microsecond timers rather than
6043 one-second timers. This can avoid an unpleasant situation where a
6044 circuit is launched near the end of one second and expired right
6045 near the beginning of the next, and prevent fluctuations in circuit
6047 - Use computed circuit-build timeouts to decide when to launch
6048 parallel introduction circuits for hidden services. (Previously,
6049 we would retry after 15 seconds.)
6050 - Update to the April 1 2011 Maxmind GeoLite Country database.
6053 - Create the /var/run/tor directory on startup on OpenSUSE if it is
6054 not already created. Patch from Andreas Stieger. Fixes bug 2573.
6056 o Documentation changes:
6057 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
6058 - Resolve all doxygen warnings except those for missing documentation.
6060 - Add doxygen documentation for more functions, fields, and types.
6063 Changes in version 0.2.2.23-alpha - 2011-03-08
6064 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
6065 they restart they don't lose their bandwidth capacity estimate. This
6066 release also fixes a diverse set of user-facing bugs, ranging from
6067 relays overrunning their rate limiting to clients falsely warning about
6068 clock skew to bridge descriptor leaks by our bridge directory authority.
6071 - Stop sending a CLOCK_SKEW controller status event whenever
6072 we fetch directory information from a relay that has a wrong clock.
6073 Instead, only inform the controller when it's a trusted authority
6074 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
6075 the rest of bug 1074.
6076 - Fix an assert in parsing router descriptors containing IPv6
6077 addresses. This one took down the directory authorities when
6078 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
6079 - Make the bridge directory authority refuse to answer directory
6080 requests for "all" descriptors. It used to include bridge
6081 descriptors in its answer, which was a major information leak.
6082 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
6083 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
6084 Tor would ignore their RelayBandwidthBurst setting,
6085 potentially using more bandwidth than expected. Bugfix on
6086 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
6087 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
6088 hidserv" in her torrc. The 'hidserv' argument never controlled
6089 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
6092 - Relays now save observed peak bandwidth throughput rates to their
6093 state file (along with total usage, which was already saved)
6094 so that they can determine their correct estimated bandwidth on
6095 restart. Resolves bug 1863, where Tor relays would reset their
6096 estimated bandwidth to 0 after restarting.
6097 - Directory authorities now take changes in router IP address and
6098 ORPort into account when determining router stability. Previously,
6099 if a router changed its IP or ORPort, the authorities would not
6100 treat it as having any downtime for the purposes of stability
6101 calculation, whereas clients would experience downtime since the
6102 change could take a while to propagate to them. Resolves issue 1035.
6103 - Enable Address Space Layout Randomization (ASLR) and Data Execution
6104 Prevention (DEP) by default on Windows to make it harder for
6105 attackers to exploit vulnerabilities. Patch from John Brooks.
6107 o Minor bugfixes (on 0.2.1.x and earlier):
6108 - Fix a rare crash bug that could occur when a client was configured
6109 with a large number of bridges. Fixes bug 2629; bugfix on
6110 0.2.1.2-alpha. Bugfix by trac user "shitlei".
6111 - Avoid a double mark-for-free warning when failing to attach a
6112 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
6114 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
6115 found by "cypherpunks". This bug was introduced before the first
6116 Tor release, in svn commit r110.
6117 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
6118 don't mention them in the manpage. Fixes bug 2450; issue
6119 spotted by keb and G-Lo.
6120 - Fix a bug in bandwidth history state parsing that could have been
6121 triggered if a future version of Tor ever changed the timing
6122 granularity at which bandwidth history is measured. Bugfix on
6124 - When a relay decides that its DNS is too broken for it to serve
6125 as an exit server, it advertised itself as a non-exit, but
6126 continued to act as an exit. This could create accidental
6127 partitioning opportunities for users. Instead, if a relay is
6128 going to advertise reject *:* as its exit policy, it should
6129 really act with exit policy "reject *:*". Fixes bug 2366.
6130 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
6131 - In the special case where you configure a public exit relay as your
6132 bridge, Tor would be willing to use that exit relay as the last
6133 hop in your circuit as well. Now we fail that circuit instead.
6134 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
6135 - Fix a bug with our locking implementation on Windows that couldn't
6136 correctly detect when a file was already locked. Fixes bug 2504,
6137 bugfix on 0.2.1.6-alpha.
6138 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
6139 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
6141 - Set target port in get_interface_address6() correctly. Bugfix
6142 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
6143 - Directory authorities are now more robust to hops back in time
6144 when calculating router stability. Previously, if a run of uptime
6145 or downtime appeared to be negative, the calculation could give
6146 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
6148 - Fix an assert that got triggered when using the TestingTorNetwork
6149 configuration option and then issuing a GETINFO config-text control
6150 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
6152 o Minor bugfixes (on 0.2.2.x):
6153 - Clients should not weight BadExit nodes as Exits in their node
6154 selection. Similarly, directory authorities should not count BadExit
6155 bandwidth as Exit bandwidth when computing bandwidth-weights.
6156 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
6157 - Correctly clear our dir_read/dir_write history when there is an
6158 error parsing any bw history value from the state file. Bugfix on
6160 - Resolve a bug in verifying signatures of directory objects
6161 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
6162 Fixes bug 2409. Found by "piebeer".
6163 - Bridge authorities no longer crash on SIGHUP when they try to
6164 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
6168 - Log less aggressively about circuit timeout changes, and improve
6169 some other circuit timeout messages. Resolves bug 2004.
6170 - Log a little more clearly about the times at which we're no longer
6171 accepting new connections. Resolves bug 2181.
6172 - Reject attempts at the client side to open connections to private
6173 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
6174 a randomly chosen exit node. Attempts to do so are always
6175 ill-defined, generally prevented by exit policies, and usually
6176 in error. This will also help to detect loops in transparent
6177 proxy configurations. You can disable this feature by setting
6178 "ClientRejectInternalAddresses 0" in your torrc.
6179 - Always treat failure to allocate an RSA key as an unrecoverable
6181 - Update to the March 1 2011 Maxmind GeoLite Country database.
6183 o Minor features (log subsystem):
6184 - Add documentation for configuring logging at different severities in
6185 different log domains. We've had this feature since 0.2.1.1-alpha,
6186 but for some reason it never made it into the manpage. Fixes
6188 - Make it simpler to specify "All log domains except for A and B".
6189 Previously you needed to say "[*,~A,~B]". Now you can just say
6191 - Add a "LogMessageDomains 1" option to include the domains of log
6192 messages along with the messages. Without this, there's no way
6193 to use log domains without reading the source or doing a lot
6196 o Packaging changes:
6197 - Stop shipping the Tor specs files and development proposal documents
6198 in the tarball. They are now in a separate git repository at
6199 git://git.torproject.org/torspec.git
6202 Changes in version 0.2.1.30 - 2011-02-23
6203 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
6204 change is a slight tweak to Tor's TLS handshake that makes relays
6205 and bridges that run this new version reachable from Iran again.
6206 We don't expect this tweak will win the arms race long-term, but it
6207 buys us time until we roll out a better solution.
6210 - Stop sending a CLOCK_SKEW controller status event whenever
6211 we fetch directory information from a relay that has a wrong clock.
6212 Instead, only inform the controller when it's a trusted authority
6213 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
6214 the rest of bug 1074.
6215 - Fix a bounds-checking error that could allow an attacker to
6216 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
6218 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
6219 Tor would ignore their RelayBandwidthBurst setting,
6220 potentially using more bandwidth than expected. Bugfix on
6221 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
6222 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
6223 hidserv" in her torrc. The 'hidserv' argument never controlled
6224 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
6227 - Adjust our TLS Diffie-Hellman parameters to match those used by
6229 - Update to the February 1 2011 Maxmind GeoLite Country database.
6232 - Check for and reject overly long directory certificates and
6233 directory tokens before they have a chance to hit any assertions.
6234 Bugfix on 0.2.1.28. Found by "doorss".
6235 - Bring the logic that gathers routerinfos and assesses the
6236 acceptability of circuits into line. This prevents a Tor OP from
6237 getting locked in a cycle of choosing its local OR as an exit for a
6238 path (due to a .exit request) and then rejecting the circuit because
6239 its OR is not listed yet. It also prevents Tor clients from using an
6240 OR running in the same instance as an exit (due to a .exit request)
6241 if the OR does not meet the same requirements expected of an OR
6242 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
6244 o Packaging changes:
6245 - Stop shipping the Tor specs files and development proposal documents
6246 in the tarball. They are now in a separate git repository at
6247 git://git.torproject.org/torspec.git
6248 - Do not include Git version tags as though they are SVN tags when
6249 generating a tarball from inside a repository that has switched
6250 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
6253 Changes in version 0.2.2.22-alpha - 2011-01-25
6254 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
6255 main other change is a slight tweak to Tor's TLS handshake that makes
6256 relays and bridges that run this new version reachable from Iran again.
6257 We don't expect this tweak will win the arms race long-term, but it
6258 will buy us a bit more time until we roll out a better solution.
6261 - Fix a bounds-checking error that could allow an attacker to
6262 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
6264 - Don't assert when changing from bridge to relay or vice versa
6265 via the controller. The assert happened because we didn't properly
6266 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
6267 bug 2433. Reported by bastik.
6270 - Adjust our TLS Diffie-Hellman parameters to match those used by
6272 - Provide a log message stating which geoip file we're parsing
6273 instead of just stating that we're parsing the geoip file.
6274 Implements ticket 2432.
6277 - Check for and reject overly long directory certificates and
6278 directory tokens before they have a chance to hit any assertions.
6279 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
6282 Changes in version 0.2.2.21-alpha - 2011-01-15
6283 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
6284 continues our recent code security audit work. The main fix resolves
6285 a remote heap overflow vulnerability that can allow remote code
6286 execution (CVE-2011-0427). Other fixes address a variety of assert
6287 and crash bugs, most of which we think are hard to exploit remotely.
6289 o Major bugfixes (security), also included in 0.2.1.29:
6290 - Fix a heap overflow bug where an adversary could cause heap
6291 corruption. This bug probably allows remote code execution
6292 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
6294 - Prevent a denial-of-service attack by disallowing any
6295 zlib-compressed data whose compression factor is implausibly
6296 high. Fixes part of bug 2324; reported by "doorss".
6297 - Zero out a few more keys in memory before freeing them. Fixes
6298 bug 2384 and part of bug 2385. These key instances found by
6299 "cypherpunks", based on Andrew Case's report about being able
6300 to find sensitive data in Tor's memory space if you have enough
6301 permissions. Bugfix on 0.0.2pre9.
6303 o Major bugfixes (crashes), also included in 0.2.1.29:
6304 - Prevent calls to Libevent from inside Libevent log handlers.
6305 This had potential to cause a nasty set of crashes, especially
6306 if running Libevent with debug logging enabled, and running
6307 Tor with a controller watching for low-severity log messages.
6308 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
6309 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
6310 underflow errors there too. Fixes the other part of bug 2324.
6311 - Fix a bug where we would assert if we ever had a
6312 cached-descriptors.new file (or another file read directly into
6313 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
6314 on 0.2.1.25. Found by doorss.
6315 - Fix some potential asserts and parsing issues with grossly
6316 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
6319 o Minor bugfixes (other), also included in 0.2.1.29:
6320 - Fix a bug with handling misformed replies to reverse DNS lookup
6321 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
6322 bug reported by doorss.
6323 - Fix compilation on mingw when a pthreads compatibility library
6324 has been installed. (We don't want to use it, so we shouldn't
6325 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
6326 - Fix a bug where we would declare that we had run out of virtual
6327 addresses when the address space was only half-exhausted. Bugfix
6329 - Correctly handle the case where AutomapHostsOnResolve is set but
6330 no virtual addresses are available. Fixes bug 2328; bugfix on
6331 0.1.2.1-alpha. Bug found by doorss.
6332 - Correctly handle wrapping around when we run out of virtual
6333 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
6335 o Minor features, also included in 0.2.1.29:
6336 - Update to the January 1 2011 Maxmind GeoLite Country database.
6337 - Introduce output size checks on all of our decryption functions.
6339 o Build changes, also included in 0.2.1.29:
6340 - Tor does not build packages correctly with Automake 1.6 and earlier;
6341 added a check to Makefile.am to make sure that we're building with
6342 Automake 1.7 or later.
6343 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
6344 because we built it with a too-old version of automake. Thus that
6345 release broke ./configure --enable-openbsd-malloc, which is popular
6346 among really fast exit relays on Linux.
6348 o Major bugfixes, new in 0.2.2.21-alpha:
6349 - Prevent crash/heap corruption when the cbtnummodes consensus
6350 parameter is set to 0 or large values. Fixes bug 2317; bugfix
6353 o Major features, new in 0.2.2.21-alpha:
6354 - Introduce minimum/maximum values that clients will believe
6355 from the consensus. Now we'll have a better chance to avoid crashes
6356 or worse when a consensus param has a weird value.
6358 o Minor features, new in 0.2.2.21-alpha:
6359 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
6360 used on bridges, and it makes bridge scanning somewhat easier.
6361 - If writing the state file to disk fails, wait up to an hour before
6362 retrying again, rather than trying again each second. Fixes bug
6363 2346; bugfix on Tor 0.1.1.3-alpha.
6364 - Make Libevent log messages get delivered to controllers later,
6365 and not from inside the Libevent log handler. This prevents unsafe
6366 reentrant Libevent calls while still letting the log messages
6368 - Detect platforms that brokenly use a signed size_t, and refuse to
6369 build there. Found and analyzed by doorss and rransom.
6370 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
6373 o Minor bugfixes, new in 0.2.2.21-alpha:
6374 - Handle SOCKS messages longer than 128 bytes long correctly, rather
6375 than waiting forever for them to finish. Fixes bug 2330; bugfix
6376 on 0.2.0.16-alpha. Found by doorss.
6377 - Add assertions to check for overflow in arguments to
6378 base32_encode() and base32_decode(); fix a signed-unsigned
6379 comparison there too. These bugs are not actually reachable in Tor,
6380 but it's good to prevent future errors too. Found by doorss.
6381 - Correctly detect failures to create DNS requests when using Libevent
6382 versions before v2. (Before Libevent 2, we used our own evdns
6383 implementation. Its return values for Libevent's evdns_resolve_*()
6384 functions are not consistent with those from Libevent.) Fixes bug
6385 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
6387 o Documentation, new in 0.2.2.21-alpha:
6388 - Document the default socks host and port (127.0.0.1:9050) for
6392 Changes in version 0.2.1.29 - 2011-01-15
6393 Tor 0.2.1.29 continues our recent code security audit work. The main
6394 fix resolves a remote heap overflow vulnerability that can allow remote
6395 code execution. Other fixes address a variety of assert and crash bugs,
6396 most of which we think are hard to exploit remotely.
6398 o Major bugfixes (security):
6399 - Fix a heap overflow bug where an adversary could cause heap
6400 corruption. This bug probably allows remote code execution
6401 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
6403 - Prevent a denial-of-service attack by disallowing any
6404 zlib-compressed data whose compression factor is implausibly
6405 high. Fixes part of bug 2324; reported by "doorss".
6406 - Zero out a few more keys in memory before freeing them. Fixes
6407 bug 2384 and part of bug 2385. These key instances found by
6408 "cypherpunks", based on Andrew Case's report about being able
6409 to find sensitive data in Tor's memory space if you have enough
6410 permissions. Bugfix on 0.0.2pre9.
6412 o Major bugfixes (crashes):
6413 - Prevent calls to Libevent from inside Libevent log handlers.
6414 This had potential to cause a nasty set of crashes, especially
6415 if running Libevent with debug logging enabled, and running
6416 Tor with a controller watching for low-severity log messages.
6417 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
6418 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
6419 underflow errors there too. Fixes the other part of bug 2324.
6420 - Fix a bug where we would assert if we ever had a
6421 cached-descriptors.new file (or another file read directly into
6422 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
6423 on 0.2.1.25. Found by doorss.
6424 - Fix some potential asserts and parsing issues with grossly
6425 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
6428 o Minor bugfixes (other):
6429 - Fix a bug with handling misformed replies to reverse DNS lookup
6430 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
6431 bug reported by doorss.
6432 - Fix compilation on mingw when a pthreads compatibility library
6433 has been installed. (We don't want to use it, so we shouldn't
6434 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
6435 - Fix a bug where we would declare that we had run out of virtual
6436 addresses when the address space was only half-exhausted. Bugfix
6438 - Correctly handle the case where AutomapHostsOnResolve is set but
6439 no virtual addresses are available. Fixes bug 2328; bugfix on
6440 0.1.2.1-alpha. Bug found by doorss.
6441 - Correctly handle wrapping around to when we run out of virtual
6442 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
6443 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
6444 because we built it with a too-old version of automake. Thus that
6445 release broke ./configure --enable-openbsd-malloc, which is popular
6446 among really fast exit relays on Linux.
6449 - Update to the January 1 2011 Maxmind GeoLite Country database.
6450 - Introduce output size checks on all of our decryption functions.
6453 - Tor does not build packages correctly with Automake 1.6 and earlier;
6454 added a check to Makefile.am to make sure that we're building with
6455 Automake 1.7 or later.
6458 Changes in version 0.2.2.20-alpha - 2010-12-17
6459 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
6460 exploitable bugs. We also fix a variety of other significant bugs,
6461 change the IP address for one of our directory authorities, and update
6462 the minimum version that Tor relays must run to join the network.
6465 - Fix a remotely exploitable bug that could be used to crash instances
6466 of Tor remotely by overflowing on the heap. Remote-code execution
6467 hasn't been confirmed, but can't be ruled out. Everyone should
6468 upgrade. Bugfix on the 0.1.1 series and later.
6469 - Fix a bug that could break accounting on 64-bit systems with large
6470 time_t values, making them hibernate for impossibly long intervals.
6471 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
6472 - Fix a logic error in directory_fetches_from_authorities() that
6473 would cause all _non_-exits refusing single-hop-like circuits
6474 to fetch from authorities, when we wanted to have _exits_ fetch
6475 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
6477 - Fix a stream fairness bug that would cause newer streams on a given
6478 circuit to get preference when reading bytes from the origin or
6479 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
6480 introduced before the first Tor release, in svn revision r152.
6482 o Directory authority changes:
6483 - Change IP address and ports for gabelmoo (v3 directory authority).
6486 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
6487 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
6488 - Fix an off-by-one error in calculating some controller command
6489 argument lengths. Fortunately, this mistake is harmless since
6490 the controller code does redundant NUL termination too. Found by
6491 boboper. Bugfix on 0.1.1.1-alpha.
6492 - Do not dereference NULL if a bridge fails to build its
6493 extra-info descriptor. Found by an anonymous commenter on
6494 Trac. Bugfix on 0.2.2.19-alpha.
6497 - Update to the December 1 2010 Maxmind GeoLite Country database.
6498 - Directory authorities now reject relays running any versions of
6499 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
6500 known bugs that keep RELAY_EARLY cells from working on rendezvous
6501 circuits. Followup to fix for bug 2081.
6502 - Directory authorities now reject relays running any version of Tor
6503 older than 0.2.0.26-rc. That version is the earliest that fetches
6504 current directory information correctly. Fixes bug 2156.
6505 - Report only the top 10 ports in exit-port stats in order not to
6506 exceed the maximum extra-info descriptor length of 50 KB. Implements
6510 Changes in version 0.2.1.28 - 2010-12-17
6511 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
6512 exploitable bugs. We also took this opportunity to change the IP address
6513 for one of our directory authorities, and to update the geoip database
6517 - Fix a remotely exploitable bug that could be used to crash instances
6518 of Tor remotely by overflowing on the heap. Remote-code execution
6519 hasn't been confirmed, but can't be ruled out. Everyone should
6520 upgrade. Bugfix on the 0.1.1 series and later.
6522 o Directory authority changes:
6523 - Change IP address and ports for gabelmoo (v3 directory authority).
6526 - Update to the December 1 2010 Maxmind GeoLite Country database.
6529 Changes in version 0.2.1.27 - 2010-11-23
6530 Yet another OpenSSL security patch broke its compatibility with Tor:
6531 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
6532 also took this opportunity to fix several crash bugs, integrate a new
6533 directory authority, and update the bundled GeoIP database.
6536 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
6537 No longer set the tlsext_host_name extension on server SSL objects;
6538 but continue to set it on client SSL objects. Our goal in setting
6539 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
6540 bugfix on 0.2.1.1-alpha.
6541 - Do not log messages to the controller while shrinking buffer
6542 freelists. Doing so would sometimes make the controller connection
6543 try to allocate a buffer chunk, which would mess up the internals
6544 of the freelist and cause an assertion failure. Fixes bug 1125;
6545 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
6546 - Learn our external IP address when we're a relay or bridge, even if
6547 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
6548 where we introduced bridge relays that don't need to publish to
6549 be useful. Fixes bug 2050.
6550 - Do even more to reject (and not just ignore) annotations on
6551 router descriptors received anywhere but from the cache. Previously
6552 we would ignore such annotations at first, but cache them to disk
6553 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
6554 - When you're using bridges and your network goes away and your
6555 bridges get marked as down, recover when you attempt a new socks
6556 connection (if the network is back), rather than waiting up to an
6557 hour to try fetching new descriptors for your bridges. Bugfix on
6558 0.2.0.3-alpha; fixes bug 1981.
6561 - Move to the November 2010 Maxmind GeoLite country db (rather
6562 than the June 2009 ip-to-country GeoIP db) for our statistics that
6563 count how many users relays are seeing from each country. Now we'll
6564 have more accurate data, especially for many African countries.
6566 o New directory authorities:
6567 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6571 - Fix an assertion failure that could occur in directory caches or
6572 bridge users when using a very short voting interval on a testing
6573 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
6575 - Enforce multiplicity rules when parsing annotations. Bugfix on
6576 0.2.0.8-alpha. Found by piebeer.
6577 - Allow handshaking OR connections to take a full KeepalivePeriod
6578 seconds to handshake. Previously, we would close them after
6579 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6580 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6582 - When building with --enable-gcc-warnings on OpenBSD, disable
6583 warnings in system headers. This makes --enable-gcc-warnings
6584 pass on OpenBSD 4.8.
6587 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6588 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6589 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6590 Servers can start sending this code when enough clients recognize
6591 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
6592 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6593 Patch from mingw-san.
6596 - Remove the old debian/ directory from the main Tor distribution.
6597 The official Tor-for-debian git repository lives at the URL
6598 https://git.torproject.org/debian/tor.git
6599 - Stop shipping the old doc/website/ directory in the tarball. We
6600 changed the website format in late 2010, and what we shipped in
6601 0.2.1.26 really wasn't that useful anyway.
6604 Changes in version 0.2.2.19-alpha - 2010-11-22
6605 Yet another OpenSSL security patch broke its compatibility with Tor:
6606 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
6609 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
6610 No longer set the tlsext_host_name extension on server SSL objects;
6611 but continue to set it on client SSL objects. Our goal in setting
6612 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
6613 bugfix on 0.2.1.1-alpha.
6616 - Try harder not to exceed the maximum length of 50 KB when writing
6617 statistics to extra-info descriptors. This bug was triggered by very
6618 fast relays reporting exit-port, entry, and dirreq statistics.
6619 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
6620 - Publish a router descriptor even if generating an extra-info
6621 descriptor fails. Previously we would not publish a router
6622 descriptor without an extra-info descriptor; this can cause fast
6623 exit relays collecting exit-port statistics to drop from the
6624 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
6627 Changes in version 0.2.2.18-alpha - 2010-11-16
6628 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
6629 us lately, makes unpublished bridge relays able to detect their IP
6630 address, and fixes a wide variety of other bugs to get us much closer
6631 to a stable release.
6634 - Do even more to reject (and not just ignore) annotations on
6635 router descriptors received anywhere but from the cache. Previously
6636 we would ignore such annotations at first, but cache them to disk
6637 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
6638 - Do not log messages to the controller while shrinking buffer
6639 freelists. Doing so would sometimes make the controller connection
6640 try to allocate a buffer chunk, which would mess up the internals
6641 of the freelist and cause an assertion failure. Fixes bug 1125;
6642 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
6643 - Learn our external IP address when we're a relay or bridge, even if
6644 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
6645 where we introduced bridge relays that don't need to publish to
6646 be useful. Fixes bug 2050.
6647 - Maintain separate TLS contexts and certificates for incoming and
6648 outgoing connections in bridge relays. Previously we would use the
6649 same TLS contexts and certs for incoming and outgoing connections.
6650 Bugfix on 0.2.0.3-alpha; addresses bug 988.
6651 - Maintain separate identity keys for incoming and outgoing TLS
6652 contexts in bridge relays. Previously we would use the same
6653 identity keys for incoming and outgoing TLS contexts. Bugfix on
6654 0.2.0.3-alpha; addresses the other half of bug 988.
6655 - Avoid an assertion failure when we as an authority receive a
6656 duplicate upload of a router descriptor that we already have,
6657 but which we previously considered an obsolete descriptor.
6658 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
6659 - Avoid a crash bug triggered by looking at a dangling pointer while
6660 setting the network status consensus. Found by Robert Ransom.
6661 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
6662 - Fix a logic error where servers that _didn't_ act as exits would
6663 try to keep their server lists more aggressively up to date than
6664 exits, when it was supposed to be the other way around. Bugfix
6667 o Minor bugfixes (on Tor 0.2.1.x and earlier):
6668 - When we're trying to guess whether we know our IP address as
6669 a relay, we would log various ways that we failed to guess
6670 our address, but never log that we ended up guessing it
6671 successfully. Now add a log line to help confused and anxious
6672 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
6673 - Bring the logic that gathers routerinfos and assesses the
6674 acceptability of circuits into line. This prevents a Tor OP from
6675 getting locked in a cycle of choosing its local OR as an exit for a
6676 path (due to a .exit request) and then rejecting the circuit because
6677 its OR is not listed yet. It also prevents Tor clients from using an
6678 OR running in the same instance as an exit (due to a .exit request)
6679 if the OR does not meet the same requirements expected of an OR
6680 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
6681 - Correctly describe errors that occur when generating a TLS object.
6682 Previously we would attribute them to a failure while generating a
6683 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
6685 - Enforce multiplicity rules when parsing annotations. Bugfix on
6686 0.2.0.8-alpha. Found by piebeer.
6687 - Fix warnings that newer versions of autoconf produced during
6688 ./autogen.sh. These warnings appear to be harmless in our case,
6689 but they were extremely verbose. Fixes bug 2020.
6691 o Minor bugfixes (on Tor 0.2.2.x):
6692 - Enable protection of small arrays whenever we build with gcc
6693 hardening features, not only when also building with warnings
6694 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
6697 - Make hidden services work better in private Tor networks by not
6698 requiring any uptime to join the hidden service descriptor
6699 DHT. Implements ticket 2088.
6700 - Rate-limit the "your application is giving Tor only an IP address"
6701 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
6702 - When AllowSingleHopExits is set, print a warning to explain to the
6703 relay operator why most clients are avoiding her relay.
6704 - Update to the November 1 2010 Maxmind GeoLite Country database.
6706 o Code simplifications and refactoring:
6707 - When we fixed bug 1038 we had to put in a restriction not to send
6708 RELAY_EARLY cells on rend circuits. This was necessary as long
6709 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
6710 active. Now remove this obsolete check. Resolves bug 2081.
6711 - Some options used different conventions for uppercasing of acronyms
6712 when comparing manpage and source. Fix those in favor of the
6713 manpage, as it makes sense to capitalize acronyms.
6714 - Remove the torrc.complete file. It hasn't been kept up to date
6715 and users will have better luck checking out the manpage.
6716 - Remove the obsolete "NoPublish" option; it has been flagged
6717 as obsolete and has produced a warning since 0.1.1.18-rc.
6718 - Remove everything related to building the expert bundle for OS X.
6719 It has confused many users, doesn't work right on OS X 10.6,
6720 and is hard to get rid of once installed. Resolves bug 1274.
6723 Changes in version 0.2.2.17-alpha - 2010-09-30
6724 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
6725 to use one-hop circuits (which can put the exit relays at higher risk,
6726 plus unbalance the network); fixes a big bug in bandwidth accounting
6727 for relays that want to limit their monthly bandwidth use; fixes a
6728 big pile of bugs in how clients tolerate temporary network failure;
6729 and makes our adaptive circuit build timeout feature (which improves
6730 client performance if your network is fast while not breaking things
6731 if your network is slow) better handle bad networks.
6734 - Exit relays now try harder to block exit attempts from unknown
6735 relays, to make it harder for people to use them as one-hop proxies
6736 a la tortunnel. Controlled by the refuseunknownexits consensus
6737 parameter (currently enabled), or you can override it on your
6738 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
6740 o Major bugfixes (0.2.1.x and earlier):
6741 - Fix a bug in bandwidth accounting that could make us use twice
6742 the intended bandwidth when our interval start changes due to
6743 daylight saving time. Now we tolerate skew in stored vs computed
6744 interval starts: if the start of the period changes by no more than
6745 50% of the period's duration, we remember bytes that we transferred
6746 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
6747 - Always search the Windows system directory for system DLLs, and
6748 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
6749 - When you're using bridges and your network goes away and your
6750 bridges get marked as down, recover when you attempt a new socks
6751 connection (if the network is back), rather than waiting up to an
6752 hour to try fetching new descriptors for your bridges. Bugfix on
6753 0.2.0.3-alpha; fixes bug 1981.
6755 o Major bugfixes (on 0.2.2.x):
6756 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
6758 - Fix a segfault that could happen when operating a bridge relay with
6759 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
6760 - The consensus bandwidth-weights (used by clients to choose fast
6761 relays) entered an unexpected edge case in September where
6762 Exits were much scarcer than Guards, resulting in bad weight
6763 recommendations. Now we compute them using new constraints that
6764 should succeed in all cases. Also alter directory authorities to
6765 not include the bandwidth-weights line if they fail to produce
6766 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
6767 - When weighting bridges during path selection, we used to trust
6768 the bandwidths they provided in their descriptor, only capping them
6769 at 10MB/s. This turned out to be problematic for two reasons:
6770 Bridges could claim to handle a lot more traffic then they
6771 actually would, thus making more clients pick them and have a
6772 pretty effective DoS attack. The other issue is that new bridges
6773 that might not have a good estimate for their bw capacity yet
6774 would not get used at all unless no other bridges are available
6775 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
6777 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
6778 - Ignore cannibalized circuits when recording circuit build times.
6779 This should provide for a minor performance improvement for hidden
6780 service users using 0.2.2.14-alpha, and should remove two spurious
6781 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
6782 - Simplify the logic that causes us to decide if the network is
6783 unavailable for purposes of recording circuit build times. If we
6784 receive no cells whatsoever for the entire duration of a circuit's
6785 full measured lifetime, the network is probably down. Also ignore
6786 one-hop directory fetching circuit timeouts when calculating our
6787 circuit build times. These changes should hopefully reduce the
6788 cases where we see ridiculous circuit build timeouts for people
6789 with spotty wireless connections. Fixes part of bug 1772; bugfix
6791 - Prevent the circuit build timeout from becoming larger than
6792 the maximum build time we have ever seen. Also, prevent the time
6793 period for measurement circuits from becoming larger than twice that
6794 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
6797 - When we run out of directory information such that we can't build
6798 circuits, but then get enough that we can build circuits, log when
6799 we actually construct a circuit, so the user has a better chance of
6800 knowing what's going on. Fixes bug 1362.
6801 - Be more generous with how much bandwidth we'd use up (with
6802 accounting enabled) before entering "soft hibernation". Previously,
6803 we'd refuse new connections and circuits once we'd used up 95% of
6804 our allotment. Now, we use up 95% of our allotment, AND make sure
6805 that we have no more than 500MB (or 3 hours of expected traffic,
6806 whichever is lower) remaining before we enter soft hibernation.
6807 - If we've configured EntryNodes and our network goes away and/or all
6808 our entrynodes get marked down, optimistically retry them all when
6809 a new socks application request appears. Fixes bug 1882.
6810 - Add some more defensive programming for architectures that can't
6811 handle unaligned integer accesses. We don't know of any actual bugs
6812 right now, but that's the best time to fix them. Fixes bug 1943.
6813 - Support line continuations in the torrc config file. If a line
6814 ends with a single backslash character, the newline is ignored, and
6815 the configuration value is treated as continuing on the next line.
6818 o Minor bugfixes (on 0.2.1.x and earlier):
6819 - For bandwidth accounting, calculate our expected bandwidth rate
6820 based on the time during which we were active and not in
6821 soft-hibernation during the last interval. Previously, we were
6822 also considering the time spent in soft-hibernation. If this
6823 was a long time, we would wind up underestimating our bandwidth
6824 by a lot, and skewing our wakeup time towards the start of the
6825 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
6827 o Minor bugfixes (on 0.2.2.x):
6828 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
6829 which were disabled by the circuit build timeout changes in
6830 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
6831 - Make sure we don't warn about missing bandwidth weights when
6832 choosing bridges or other relays not in the consensus. Bugfix on
6833 0.2.2.10-alpha; fixes bug 1805.
6834 - In our logs, do not double-report signatures from unrecognized
6835 authorities both as "from unknown authority" and "not
6836 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
6839 Changes in version 0.2.2.16-alpha - 2010-09-17
6840 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
6841 evident at exit relays), and also continues to resolve all the little
6842 bugs that have been filling up trac lately.
6844 o Major bugfixes (stream-level fairness):
6845 - When receiving a circuit-level SENDME for a blocked circuit, try
6846 to package cells fairly from all the streams that had previously
6847 been blocked on that circuit. Previously, we had started with the
6848 oldest stream, and allowed each stream to potentially exhaust
6849 the circuit's package window. This gave older streams on any
6850 given circuit priority over newer ones. Fixes bug 1937. Detected
6851 originally by Camilo Viecco. This bug was introduced before the
6852 first Tor release, in svn commit r152: it is the new winner of
6853 the longest-lived bug prize.
6854 - When the exit relay got a circuit-level sendme cell, it started
6855 reading on the exit streams, even if had 500 cells queued in the
6856 circuit queue already, so the circuit queue just grew and grew in
6857 some cases. We fix this by not re-enabling reading on receipt of a
6858 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
6859 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
6861 - Newly created streams were allowed to read cells onto circuits,
6862 even if the circuit's cell queue was blocked and waiting to drain.
6863 This created potential unfairness, as older streams would be
6864 blocked, but newer streams would gladly fill the queue completely.
6865 We add code to detect this situation and prevent any stream from
6866 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
6870 - Update to the September 1 2010 Maxmind GeoLite Country database.
6871 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
6872 not. This would lead to a cookie that is still not group readable.
6873 Closes bug 1843. Suggested by katmagic.
6874 - When logging a rate-limited warning, we now mention how many messages
6875 got suppressed since the last warning.
6876 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
6877 do individual connection-level rate limiting of clients. The torrc
6878 config options with the same names trump the consensus params, if
6879 both are present. Replaces the old "bwconnrate" and "bwconnburst"
6880 consensus params which were broken from 0.2.2.7-alpha through
6881 0.2.2.14-alpha. Closes bug 1947.
6882 - When a router changes IP address or port, authorities now launch
6883 a new reachability test for it. Implements ticket 1899.
6884 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
6885 2 no signature, 4 required" messages about consensus signatures
6886 easier to read, and make sure they get logged at the same severity
6887 as the messages explaining which keys are which. Fixes bug 1290.
6888 - Don't warn when we have a consensus that we can't verify because
6889 of missing certificates, unless those certificates are ones
6890 that we have been trying and failing to download. Fixes bug 1145.
6891 - If you configure your bridge with a known identity fingerprint,
6892 and the bridge authority is unreachable (as it is in at least
6893 one country now), fall back to directly requesting the descriptor
6894 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
6896 - When building with --enable-gcc-warnings on OpenBSD, disable
6897 warnings in system headers. This makes --enable-gcc-warnings
6898 pass on OpenBSD 4.8.
6900 o Minor bugfixes (on 0.2.1.x and earlier):
6901 - Authorities will now attempt to download consensuses if their
6902 own efforts to make a live consensus have failed. This change
6903 means authorities that restart will fetch a valid consensus, and
6904 it means authorities that didn't agree with the current consensus
6905 will still fetch and serve it if it has enough signatures. Bugfix
6906 on 0.2.0.9-alpha; fixes bug 1300.
6907 - Ensure DNS requests launched by "RESOLVE" commands from the
6908 controller respect the __LeaveStreamsUnattached setconf options. The
6909 same goes for requests launched via DNSPort or transparent
6910 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
6911 - Allow handshaking OR connections to take a full KeepalivePeriod
6912 seconds to handshake. Previously, we would close them after
6913 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6914 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6916 - Rate-limit "Failed to hand off onionskin" warnings.
6917 - Never relay a cell for a circuit we have already destroyed.
6918 Between marking a circuit as closeable and finally closing it,
6919 it may have been possible for a few queued cells to get relayed,
6920 even though they would have been immediately dropped by the next
6921 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6922 - Never queue a cell for a circuit that's already been marked
6924 - Never vote for a server as "Running" if we have a descriptor for
6925 it claiming to be hibernating, and that descriptor was published
6926 more recently than our last contact with the server. Bugfix on
6927 0.2.0.3-alpha; fixes bug 911.
6928 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6931 o Minor bugfixes (on 0.2.2.x):
6932 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
6933 down if a directory fetch fails and you've configured either
6934 bridges or EntryNodes. The intent was to mark the relay as down
6935 _unless_ you're using bridges or EntryNodes, since if you are
6936 then you could quickly run out of entry points.
6937 - Fix the Windows directory-listing code. A bug introduced in
6938 0.2.2.14-alpha could make Windows directory servers forget to load
6939 some of their cached v2 networkstatus files.
6940 - Really allow clients to use relays as bridges. Fixes bug 1776;
6941 bugfix on 0.2.2.15-alpha.
6942 - Demote a warn to info that happens when the CellStatistics option
6943 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
6944 Reported by Moritz Bartl.
6945 - On Windows, build correctly either with or without Unicode support.
6946 This is necessary so that Tor can support fringe platforms like
6947 Windows 98 (which has no Unicode), or Windows CE (which has no
6948 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
6951 - Add a unit test for cross-platform directory-listing code.
6954 Changes in version 0.2.2.15-alpha - 2010-08-18
6955 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
6956 fixes a variety of other bugs that were preventing performance
6957 experiments from moving forward, fixes several bothersome memory leaks,
6958 and generally closes a lot of smaller bugs that have been filling up
6962 - Stop assigning the HSDir flag to relays that disable their
6963 DirPort (and thus will refuse to answer directory requests). This
6964 fix should dramatically improve the reachability of hidden services:
6965 hidden services and hidden service clients pick six HSDir relays
6966 to store and retrieve the hidden service descriptor, and currently
6967 about half of the HSDir relays will refuse to work. Bugfix on
6968 0.2.0.10-alpha; fixes part of bug 1693.
6969 - The PerConnBWRate and Burst config options, along with the
6970 bwconnrate and bwconnburst consensus params, initialized each conn's
6971 token bucket values only when the connection is established. Now we
6972 update them if the config options change, and update them every time
6973 we get a new consensus. Otherwise we can encounter an ugly edge
6974 case where we initialize an OR conn to client-level bandwidth,
6975 but then later the relay joins the consensus and we leave it
6976 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
6977 - Fix a regression that caused Tor to rebind its ports if it receives
6978 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6981 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6982 should give us approximately 40-50% more Guard-flagged nodes,
6983 improving the anonymity the Tor network can provide and also
6984 decreasing the dropoff in throughput that relays experience when
6985 they first get the Guard flag.
6986 - Allow enabling or disabling the *Statistics config options while
6990 - Update to the August 1 2010 Maxmind GeoLite Country database.
6991 - Have the controller interface give a more useful message than
6992 "Internal Error" in response to failed GETINFO requests.
6993 - Warn when the same option is provided more than once in a torrc
6994 file, on the command line, or in a single SETCONF statement, and
6995 the option is one that only accepts a single line. Closes bug 1384.
6996 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6997 Patch from mingw-san.
6998 - Add support for the country code "{??}" in torrc options like
6999 ExcludeNodes, to indicate all routers of unknown country. Closes
7001 - Relays report the number of bytes spent on answering directory
7002 requests in extra-info descriptors similar to {read,write}-history.
7003 Implements enhancement 1790.
7005 o Minor bugfixes (on 0.2.1.x and earlier):
7006 - Complain if PublishServerDescriptor is given multiple arguments that
7007 include 0 or 1. This configuration will be rejected in the future.
7008 Bugfix on 0.2.0.1-alpha; closes bug 1107.
7009 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
7010 Bugfix on 0.2.0.13-alpha; closes bug 928.
7011 - Change "Application request when we're believed to be offline."
7012 notice to "Application request when we haven't used client
7013 functionality lately.", to clarify that it's not an error. Bugfix
7014 on 0.0.9.3; fixes bug 1222.
7015 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
7016 would return "551 Internal error" rather than "552 Unrecognized key
7017 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
7018 - Users can't configure a regular relay to be their bridge. It didn't
7019 work because when Tor fetched the bridge descriptor, it found
7020 that it already had it, and didn't realize that the purpose of the
7021 descriptor had changed. Now we replace routers with a purpose other
7022 than bridge with bridge descriptors when fetching them. Bugfix on
7023 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
7024 refetch the descriptor with router purpose 'general', disabling
7026 - Fix a rare bug in rend_fn unit tests: we would fail a test when
7027 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
7028 on 0.2.0.10-alpha; fixes bug 1808.
7029 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
7030 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
7031 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
7032 Servers can start sending this code when enough clients recognize
7033 it. Also update the spec to reflect this new reason. Bugfix on
7034 0.1.0.1-rc; fixes part of bug 1793.
7035 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
7036 when we switch from being a public relay to a bridge. Otherwise
7037 there will still be clients that see the relay in their consensus,
7038 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
7040 - Instead of giving an assertion failure on an internal mismatch
7041 on estimated freelist size, just log a BUG warning and try later.
7042 Mitigates but does not fix bug 1125.
7043 - Fix an assertion failure that could occur in caches or bridge users
7044 when using a very short voting interval on a testing network.
7045 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
7047 o Minor bugfixes (on 0.2.2.x):
7048 - Alter directory authorities to always consider Exit-flagged nodes
7049 as potential Guard nodes in their votes. The actual decision to
7050 use Exits as Guards is done in the consensus bandwidth weights.
7051 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
7052 - When the controller is reporting the purpose of circuits that
7053 didn't finish building before the circuit build timeout, it was
7054 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
7055 - Our libevent version parsing code couldn't handle versions like
7056 1.4.14b-stable and incorrectly warned the user about using an
7057 old and broken version of libevent. Treat 1.4.14b-stable like
7058 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
7060 - Don't use substitution references like $(VAR:MOD) when
7061 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
7062 '$(:x)' to 'x' rather than the empty string. This bites us in
7063 doc/ when configured with --disable-asciidoc. Bugfix on
7064 0.2.2.9-alpha; fixes bug 1773.
7065 - Remove a spurious hidden service server-side log notice about
7066 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
7068 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
7070 - Correctly report written bytes on linked connections. Found while
7071 implementing 1790. Bugfix on 0.2.2.4-alpha.
7072 - Fix three memory leaks: one in circuit_build_times_parse_state(),
7073 one in dirvote_add_signatures_to_pending_consensus(), and one every
7074 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
7075 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
7077 o Code simplifications and refactoring:
7078 - Take a first step towards making or.h smaller by splitting out
7079 function definitions for all source files in src/or/. Leave
7080 structures and defines in or.h for now.
7081 - Remove a bunch of unused function declarations as well as a block of
7082 #if 0'd code from the unit tests. Closes bug 1824.
7083 - New unit tests for exit-port history statistics; refactored exit
7084 statistics code to be more easily tested.
7085 - Remove the old debian/ directory from the main Tor distribution.
7086 The official Tor-for-debian git repository lives at the URL
7087 https://git.torproject.org/debian/tor.git
7090 Changes in version 0.2.2.14-alpha - 2010-07-12
7091 Tor 0.2.2.14-alpha greatly improves client-side handling of
7092 circuit build timeouts, which are used to estimate speed and improve
7093 performance. We also move to a much better GeoIP database, port Tor to
7094 Windows CE, introduce new compile flags that improve code security,
7095 add an eighth v3 directory authority, and address a lot of more
7099 - Tor directory authorities no longer crash when started with a
7100 cached-microdesc-consensus file in their data directory. Bugfix
7101 on 0.2.2.6-alpha; fixes bug 1532.
7102 - Treat an unset $HOME like an empty $HOME rather than triggering an
7103 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
7104 - Ignore negative and large circuit build timeout values that can
7105 happen during a suspend or hibernate. These values caused various
7106 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
7107 - Alter calculation of Pareto distribution parameter 'Xm' for
7108 Circuit Build Timeout learning to use the weighted average of the
7109 top N=3 modes (because we have three entry guards). Considering
7110 multiple modes should improve the timeout calculation in some cases,
7111 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
7113 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
7114 right censored distribution model. This approach improves over the
7115 synthetic timeout generation approach that was producing insanely
7116 high timeout values. Now we calculate build timeouts using truncated
7117 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
7118 - Do not close circuits that are under construction when they reach
7119 the circuit build timeout. Instead, leave them building (but do not
7120 use them) for up until the time corresponding to the 95th percentile
7121 on the Pareto CDF or 60 seconds, whichever is greater. This is done
7122 to provide better data for the new Pareto model. This percentile
7123 can be controlled by the consensus.
7126 - Move to the June 2010 Maxmind GeoLite country db (rather than the
7127 June 2009 ip-to-country GeoIP db) for our statistics that count
7128 how many users relays are seeing from each country. Now we have
7129 more accurate data for many African countries.
7130 - Port Tor to build and run correctly on Windows CE systems, using
7131 the wcecompat library. Contributed by Valerio Lupi.
7132 - New "--enable-gcc-hardening" ./configure flag (off by default)
7133 to turn on gcc compile time hardening options. It ensures
7134 that signed ints have defined behavior (-fwrapv), enables
7135 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
7136 with canaries (-fstack-protector-all), turns on ASLR protection if
7137 supported by the kernel (-fPIE, -pie), and adds additional security
7138 related warnings. Verified to work on Mac OS X and Debian Lenny.
7139 - New "--enable-linker-hardening" ./configure flag (off by default)
7140 to turn on ELF specific hardening features (relro, now). This does
7141 not work with Mac OS X or any other non-ELF binary format.
7143 o New directory authorities:
7144 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
7148 - New config option "WarnUnsafeSocks 0" disables the warning that
7149 occurs whenever Tor receives a socks handshake using a version of
7150 the socks protocol that can only provide an IP address (rather
7151 than a hostname). Setups that do DNS locally over Tor are fine,
7152 and we shouldn't spam the logs in that case.
7153 - Convert the HACKING file to asciidoc, and add a few new sections
7154 to it, explaining how we use Git, how we make changelogs, and
7155 what should go in a patch.
7156 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
7157 event, to give information on the current rate of circuit timeouts
7158 over our stored history.
7159 - Add ability to disable circuit build time learning via consensus
7160 parameter and via a LearnCircuitBuildTimeout config option. Also
7161 automatically disable circuit build time calculation if we are
7162 either a AuthoritativeDirectory, or if we fail to write our state
7163 file. Fixes bug 1296.
7164 - More gracefully handle corrupt state files, removing asserts
7165 in favor of saving a backup and resetting state.
7166 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
7170 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7172 - When a2x fails, mention that the user could disable manpages instead
7173 of trying to fix their asciidoc installation.
7174 - Where available, use Libevent 2.0's periodic timers so that our
7175 once-per-second cleanup code gets called even more closely to
7176 once per second than it would otherwise. Fixes bug 943.
7177 - If you run a bridge that listens on multiple IP addresses, and
7178 some user configures a bridge address that uses a different IP
7179 address than your bridge writes in its router descriptor, and the
7180 user doesn't specify an identity key, their Tor would discard the
7181 descriptor because "it isn't one of our configured bridges", and
7182 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
7183 Bugfix on 0.2.0.3-alpha.
7184 - If OpenSSL fails to make a duplicate of a private or public key, log
7185 an error message and try to exit cleanly. May help with debugging
7186 if bug 1209 ever remanifests.
7187 - Save a couple bytes in memory allocation every time we escape
7188 certain characters in a string. Patch from Florian Zumbiehl.
7189 - Make it explicit that we don't cannibalize one-hop circuits. This
7190 happens in the wild, but doesn't turn out to be a problem because
7191 we fortunately don't use those circuits. Many thanks to outofwords
7192 for the initial analysis and to swissknife who confirmed that
7193 two-hop circuits are actually created.
7194 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
7195 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
7196 - Eliminate a case where a circuit build time warning was displayed
7197 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
7200 Changes in version 0.2.1.26 - 2010-05-02
7201 Tor 0.2.1.26 addresses the recent connection and memory overload
7202 problems we've been seeing on relays, especially relays with their
7203 DirPort open. If your relay has been crashing, or you turned it off
7204 because it used too many resources, give this release a try.
7206 This release also fixes yet another instance of broken OpenSSL libraries
7207 that was causing some relays to drop out of the consensus.
7210 - Teach relays to defend themselves from connection overload. Relays
7211 now close idle circuits early if it looks like they were intended
7212 for directory fetches. Relays are also more aggressive about closing
7213 TLS connections that have no circuits on them. Such circuits are
7214 unlikely to be re-used, and tens of thousands of them were piling
7215 up at the fast relays, causing the relays to run out of sockets
7216 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
7217 their directory fetches over TLS).
7218 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
7219 that claim to be earlier than 0.9.8m, but which have in reality
7220 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
7221 behavior. Possible fix for some cases of bug 1346.
7222 - Directory mirrors were fetching relay descriptors only from v2
7223 directory authorities, rather than v3 authorities like they should.
7224 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
7225 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
7228 - Finally get rid of the deprecated and now harmful notion of "clique
7229 mode", where directory authorities maintain TLS connections to
7233 - In the util/threads test, no longer free the test_mutex before all
7234 worker threads have finished. Bugfix on 0.2.1.6-alpha.
7235 - The master thread could starve the worker threads quite badly on
7236 certain systems, causing them to run only partially in the allowed
7237 window. This resulted in test failures. Now the master thread sleeps
7238 occasionally for a few microseconds while the two worker-threads
7239 compete for the mutex. Bugfix on 0.2.0.1-alpha.
7242 Changes in version 0.2.2.13-alpha - 2010-04-24
7243 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
7244 problems we've been seeing on relays, especially relays with their
7245 DirPort open. If your relay has been crashing, or you turned it off
7246 because it used too many resources, give this release a try.
7249 - Teach relays to defend themselves from connection overload. Relays
7250 now close idle circuits early if it looks like they were intended
7251 for directory fetches. Relays are also more aggressive about closing
7252 TLS connections that have no circuits on them. Such circuits are
7253 unlikely to be re-used, and tens of thousands of them were piling
7254 up at the fast relays, causing the relays to run out of sockets
7255 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
7256 their directory fetches over TLS).
7259 - Finally get rid of the deprecated and now harmful notion of "clique
7260 mode", where directory authorities maintain TLS connections to
7262 - Directory authorities now do an immediate reachability check as soon
7263 as they hear about a new relay. This change should slightly reduce
7264 the time between setting up a relay and getting listed as running
7265 in the consensus. It should also improve the time between setting
7266 up a bridge and seeing use by bridge users.
7267 - Directory authorities no longer launch a TLS connection to every
7268 relay as they startup. Now that we have 2k+ descriptors cached,
7269 the resulting network hiccup is becoming a burden. Besides,
7270 authorities already avoid voting about Running for the first half
7271 hour of their uptime.
7274 Changes in version 0.2.2.12-alpha - 2010-04-20
7275 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
7276 handle and vote on descriptors. It was causing relays to drop out of
7280 - Many relays have been falling out of the consensus lately because
7281 not enough authorities know about their descriptor for them to get
7282 a majority of votes. When we deprecated the v2 directory protocol,
7283 we got rid of the only way that v3 authorities can hear from each
7284 other about other descriptors. Now authorities examine every v3
7285 vote for new descriptors, and fetch them from that authority. Bugfix
7287 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
7288 and a warning in or.h related to bandwidth_weight_rule_t that
7289 prevented clean compile on OS X. Fixes bug 1363; bugfix on
7291 - Fix a segfault on relays when DirReqStatistics is enabled
7292 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
7296 - Demote a confusing TLS warning that relay operators might get when
7297 someone tries to talk to their OrPort. It is neither the operator's
7298 fault nor can they do anything about it. Fixes bug 1364; bugfix
7302 Changes in version 0.2.2.11-alpha - 2010-04-15
7303 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
7304 libraries that was causing some relays to drop out of the consensus.
7307 - Directory mirrors were fetching relay descriptors only from v2
7308 directory authorities, rather than v3 authorities like they should.
7309 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
7310 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
7311 - Fix a parsing error that made every possible value of
7312 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
7313 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
7314 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
7315 about the option without breaking older ones.
7316 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
7317 that claim to be earlier than 0.9.8m, but which have in reality
7318 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
7319 behavior. Possible fix for some cases of bug 1346.
7322 - Experiment with a more aggressive approach to preventing clients
7323 from making one-hop exit streams. Exit relays who want to try it
7324 out can set "RefuseUnknownExits 1" in their torrc, and then look
7325 for "Attempt by %s to open a stream" log messages. Let us know
7327 - Add support for statically linking zlib by specifying
7328 --enable-static-zlib, to go with our support for statically linking
7329 openssl and libevent. Resolves bug 1358.
7332 - Fix a segfault that happens whenever a Tor client that is using
7333 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
7335 - When we cleaned up the contrib/tor-exit-notice.html file, we left
7336 out the first line. Fixes bug 1295.
7337 - When building the manpage from a tarball, we required asciidoc, but
7338 the asciidoc -> roff/html conversion was already done for the
7339 tarball. Make 'make' complain only when we need asciidoc (either
7340 because we're compiling directly from git, or because we altered
7341 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
7342 - When none of the directory authorities vote on any params, Tor
7343 segfaulted when trying to make the consensus from the votes. We
7344 didn't trigger the bug in practice, because authorities do include
7345 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
7348 - In the util/threads test, no longer free the test_mutex before all
7349 worker threads have finished. Bugfix on 0.2.1.6-alpha.
7350 - The master thread could starve the worker threads quite badly on
7351 certain systems, causing them to run only partially in the allowed
7352 window. This resulted in test failures. Now the master thread sleeps
7353 occasionally for a few microseconds while the two worker-threads
7354 compete for the mutex. Bugfix on 0.2.0.1-alpha.
7357 Changes in version 0.2.2.10-alpha - 2010-03-07
7358 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
7359 could prevent relays from guessing their IP address correctly. It also
7360 starts the groundwork for another client-side performance boost, since
7361 currently we're not making efficient use of relays that have both the
7362 Guard flag and the Exit flag.
7365 - Fix a regression from our patch for bug 1244 that caused relays
7366 to guess their IP address incorrectly if they didn't set Address
7367 in their torrc and/or their address fails to resolve. Bugfix on
7368 0.2.2.9-alpha; fixes bug 1269.
7370 o Major features (performance):
7371 - Directory authorities now compute consensus weightings that instruct
7372 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
7373 and no flag. Clients that use these weightings will distribute
7374 network load more evenly across these different relay types. The
7375 weightings are in the consensus so we can change them globally in
7376 the future. Extra thanks to "outofwords" for finding some nasty
7377 security bugs in the first implementation of this feature.
7379 o Minor features (performance):
7380 - Always perform router selections using weighted relay bandwidth,
7381 even if we don't need a high capacity circuit at the time. Non-fast
7382 circuits now only differ from fast ones in that they can use relays
7383 not marked with the Fast flag. This "feature" could turn out to
7384 be a horrible bug; we should investigate more before it goes into
7388 - Allow disabling building of the manpages. Skipping the manpage
7389 speeds up the build considerably.
7391 o Minor bugfixes (on 0.2.2.x):
7392 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
7393 Bugfix on 0.2.2.9-alpha.
7394 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
7395 config option. Bugfix on 0.2.2.7-alpha.
7396 - Ship the asciidoc-helper file in the tarball, so that people can
7397 build from source if they want to, and touching the .1.txt files
7398 doesn't break the build. Bugfix on 0.2.2.9-alpha.
7400 o Minor bugfixes (on 0.2.1.x or earlier):
7401 - Fix a dereference-then-NULL-check sequence when publishing
7402 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
7404 - Fix another dereference-then-NULL-check sequence. Bugfix on
7405 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
7406 - Make sure we treat potentially not NUL-terminated strings correctly.
7407 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
7409 o Code simplifications and refactoring:
7410 - Fix some urls in the exit notice file and make it XHTML1.1 strict
7411 compliant. Based on a patch from Christian Kujau.
7412 - Don't use sed in asciidoc-helper anymore.
7413 - Make the build process fail if asciidoc cannot be found and
7414 building with asciidoc isn't disabled.
7417 Changes in version 0.2.2.9-alpha - 2010-02-22
7418 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
7419 location of a directory authority, and cleans up a bunch of small bugs.
7421 o Directory authority changes:
7422 - Change IP address for dannenberg (v3 directory authority), and
7423 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
7424 service directory authority) from the list.
7427 - Make Tor work again on the latest OS X: when deciding whether to
7428 use strange flags to turn TLS renegotiation on, detect the OpenSSL
7429 version at run-time, not compile time. We need to do this because
7430 Apple doesn't update its dev-tools headers when it updates its
7431 libraries in a security patch.
7432 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
7433 that could happen on 32-bit platforms with 64-bit time_t. Also fix
7434 a memory leak when requesting a hidden service descriptor we've
7435 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
7437 - Authorities could be tricked into giving out the Exit flag to relays
7438 that didn't allow exiting to any ports. This bug could screw
7439 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
7440 1238. Bug discovered by Martin Kowalczyk.
7441 - When freeing a session key, zero it out completely. We only zeroed
7442 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
7443 patched by ekir. Fixes bug 1254.
7446 - Fix static compilation by listing the openssl libraries in the right
7447 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
7448 - Resume handling .exit hostnames in a special way: originally we
7449 stripped the .exit part and used the requested exit relay. In
7450 0.2.2.1-alpha we stopped treating them in any special way, meaning
7451 if you use a .exit address then Tor will pass it on to the exit
7452 relay. Now we reject the .exit stream outright, since that behavior
7453 might be more expected by the user. Found and diagnosed by Scott
7454 Bennett and Downie on or-talk.
7455 - Don't spam the controller with events when we have no file
7456 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
7457 for log messages was already solved from bug 748.)
7458 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
7460 - Make the DNSPort option work with libevent 2.x. Don't alter the
7461 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
7462 - Emit a GUARD DROPPED controller event for a case we missed.
7463 - Make more fields in the controller protocol case-insensitive, since
7464 control-spec.txt said they were.
7465 - Refactor resolve_my_address() to not use gethostbyname() anymore.
7466 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
7467 - Fix a spec conformance issue: the network-status-version token
7468 must be the first token in a v3 consensus or vote. Discovered by
7469 parakeep. Bugfix on 0.2.0.3-alpha.
7471 o Code simplifications and refactoring:
7472 - Generate our manpage and HTML documentation using Asciidoc. This
7473 change should make it easier to maintain the documentation, and
7475 - Remove the --enable-iphone option. According to reports from Marco
7476 Bonetti, Tor builds fine without any special tweaking on recent
7477 iPhone SDK versions.
7478 - Removed some unnecessary files from the source distribution. The
7479 AUTHORS file has now been merged into the people page on the
7480 website. The roadmaps and design doc can now be found in the
7481 projects directory in svn.
7482 - Enabled various circuit build timeout constants to be controlled
7483 by consensus parameters. Also set better defaults for these
7484 parameters based on experimentation on broadband and simulated
7488 - The 'EXTENDCIRCUIT' control port command can now be used with
7489 a circ id of 0 and no path. This feature will cause Tor to build
7490 a new 'fast' general purpose circuit using its own path selection
7492 - Added a BUILDTIMEOUT_SET controller event to describe changes
7493 to the circuit build timeout.
7494 - Future-proof the controller protocol a bit by ignoring keyword
7495 arguments we do not recognize.
7496 - Expand homedirs passed to tor-checkkey. This should silence a
7497 coverity complaint about passing a user-supplied string into
7498 open() without checking it.
7501 Changes in version 0.2.1.25 - 2010-03-16
7502 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
7503 prevent relays from guessing their IP address correctly. It also fixes
7504 several minor potential security bugs.
7507 - Fix a regression from our patch for bug 1244 that caused relays
7508 to guess their IP address incorrectly if they didn't set Address
7509 in their torrc and/or their address fails to resolve. Bugfix on
7510 0.2.1.23; fixes bug 1269.
7511 - When freeing a session key, zero it out completely. We only zeroed
7512 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
7513 patched by ekir. Fixes bug 1254.
7516 - Fix a dereference-then-NULL-check sequence when publishing
7517 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
7519 - Fix another dereference-then-NULL-check sequence. Bugfix on
7520 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
7521 - Make sure we treat potentially not NUL-terminated strings correctly.
7522 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
7526 Changes in version 0.2.1.24 - 2010-02-21
7527 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
7531 - Work correctly out-of-the-box with even more vendor-patched versions
7532 of OpenSSL. In particular, make it so Debian and OS X don't need
7533 customized patches to run/build.
7536 Changes in version 0.2.1.23 - 2010-02-13
7537 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
7538 again on the latest OS X, and updates the location of a directory
7541 o Major bugfixes (performance):
7542 - We were selecting our guards uniformly at random, and then weighting
7543 which of our guards we'd use uniformly at random. This imbalance
7544 meant that Tor clients were severely limited on throughput (and
7545 probably latency too) by the first hop in their circuit. Now we
7546 select guards weighted by currently advertised bandwidth. We also
7547 automatically discard guards picked using the old algorithm. Fixes
7548 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7551 - Make Tor work again on the latest OS X: when deciding whether to
7552 use strange flags to turn TLS renegotiation on, detect the OpenSSL
7553 version at run-time, not compile time. We need to do this because
7554 Apple doesn't update its dev-tools headers when it updates its
7555 libraries in a security patch.
7556 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
7557 that could happen on 32-bit platforms with 64-bit time_t. Also fix
7558 a memory leak when requesting a hidden service descriptor we've
7559 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
7562 o Directory authority changes:
7563 - Change IP address for dannenberg (v3 directory authority), and
7564 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
7565 service directory authority) from the list.
7568 - Refactor resolve_my_address() to not use gethostbyname() anymore.
7569 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
7572 - Avoid a mad rush at the beginning of each month when each client
7573 rotates half of its guards. Instead we spread the rotation out
7574 throughout the month, but we still avoid leaving a precise timestamp
7575 in the state file about when we first picked the guard. Improves
7576 over the behavior introduced in 0.1.2.17.
7579 Changes in version 0.2.2.8-alpha - 2010-01-26
7580 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
7581 causing bridge relays to disappear. If you're running a bridge,
7585 - Fix a memory corruption bug on bridges that occured during the
7586 inclusion of stats data in extra-info descriptors. Also fix the
7587 interface for geoip_get_bridge_stats* to prevent similar bugs in
7588 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
7589 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
7592 - Ignore OutboundBindAddress when connecting to localhost.
7593 Connections to localhost need to come _from_ localhost, or else
7594 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
7598 Changes in version 0.2.2.7-alpha - 2010-01-19
7599 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
7600 as laying the groundwork for further relay-side performance fixes. It
7601 also starts cleaning up client behavior with respect to the EntryNodes,
7602 ExitNodes, and StrictNodes config options.
7604 This release also rotates two directory authority keys, due to a
7605 security breach of some of the Torproject servers.
7607 o Directory authority changes:
7608 - Rotate keys (both v3 identity and relay identity) for moria1
7611 o Major features (performance):
7612 - We were selecting our guards uniformly at random, and then weighting
7613 which of our guards we'd use uniformly at random. This imbalance
7614 meant that Tor clients were severely limited on throughput (and
7615 probably latency too) by the first hop in their circuit. Now we
7616 select guards weighted by currently advertised bandwidth. We also
7617 automatically discard guards picked using the old algorithm. Fixes
7618 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7619 - When choosing which cells to relay first, relays can now favor
7620 circuits that have been quiet recently, to provide lower latency
7621 for low-volume circuits. By default, relays enable or disable this
7622 feature based on a setting in the consensus. You can override
7623 this default by using the new "CircuitPriorityHalflife" config
7624 option. Design and code by Ian Goldberg, Can Tang, and Chris
7626 - Add separate per-conn write limiting to go with the per-conn read
7627 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
7628 but never per-conn write limits.
7629 - New consensus params "bwconnrate" and "bwconnburst" to let us
7630 rate-limit client connections as they enter the network. It's
7631 controlled in the consensus so we can turn it on and off for
7632 experiments. It's starting out off. Based on proposal 163.
7634 o Major features (relay selection options):
7635 - Switch to a StrictNodes config option, rather than the previous
7636 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
7637 "StrictExcludeNodes" option.
7638 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
7639 change during a config reload, mark and discard all our origin
7640 circuits. This fix should address edge cases where we change the
7641 config options and but then choose a circuit that we created before
7643 - If EntryNodes or ExitNodes are set, be more willing to use an
7644 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
7646 - Make EntryNodes config option much more aggressive even when
7647 StrictNodes is not set. Before it would prepend your requested
7648 entrynodes to your list of guard nodes, but feel free to use others
7649 after that. Now it chooses only from your EntryNodes if any of
7650 those are available, and only falls back to others if a) they're
7651 all down and b) StrictNodes is not set.
7652 - Now we refresh your entry guards from EntryNodes at each consensus
7653 fetch -- rather than just at startup and then they slowly rot as
7654 the network changes.
7657 - Stop bridge directory authorities from answering dbg-stability.txt
7658 directory queries, which would let people fetch a list of all
7659 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7662 - Log a notice when we get a new control connection. Now it's easier
7663 for security-conscious users to recognize when a local application
7664 is knocking on their controller door. Suggested by bug 1196.
7665 - New config option "CircuitStreamTimeout" to override our internal
7666 timeout schedule for how many seconds until we detach a stream from
7667 a circuit and try a new circuit. If your network is particularly
7668 slow, you might want to set this to a number like 60.
7669 - New controller command "getinfo config-text". It returns the
7670 contents that Tor would write if you send it a SAVECONF command,
7671 so the controller can write the file to disk itself.
7672 - New options for SafeLogging to allow scrubbing only log messages
7673 generated while acting as a relay.
7674 - Ship the bridges spec file in the tarball too.
7675 - Avoid a mad rush at the beginning of each month when each client
7676 rotates half of its guards. Instead we spread the rotation out
7677 throughout the month, but we still avoid leaving a precise timestamp
7678 in the state file about when we first picked the guard. Improves
7679 over the behavior introduced in 0.1.2.17.
7681 o Minor bugfixes (compiling):
7682 - Fix compilation on OS X 10.3, which has a stub mlockall() but
7683 hides it. Bugfix on 0.2.2.6-alpha.
7684 - Fix compilation on Solaris by removing support for the
7685 DisableAllSwap config option. Solaris doesn't have an rlimit for
7686 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
7689 o Minor bugfixes (crashes):
7690 - Do not segfault when writing buffer stats when we haven't observed
7691 a single circuit to report about. Found by Fabian Lanze. Bugfix on
7693 - If we're in the pathological case where there's no exit bandwidth
7694 but there is non-exit bandwidth, or no guard bandwidth but there
7695 is non-guard bandwidth, don't crash during path selection. Bugfix
7697 - Fix an impossible-to-actually-trigger buffer overflow in relay
7698 descriptor generation. Bugfix on 0.1.0.15.
7700 o Minor bugfixes (privacy):
7701 - Fix an instance where a Tor directory mirror might accidentally
7702 log the IP address of a misbehaving Tor client. Bugfix on
7704 - Don't list Windows capabilities in relay descriptors. We never made
7705 use of them, and maybe it's a bad idea to publish them. Bugfix
7708 o Minor bugfixes (other):
7709 - Resolve an edge case in path weighting that could make us misweight
7710 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
7711 - Fix statistics on client numbers by country as seen by bridges that
7712 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
7713 intervals instead of variable 12-to-48-hour intervals.
7714 - After we free an internal connection structure, overwrite it
7715 with a different memory value than we use for overwriting a freed
7716 internal circuit structure. Should help with debugging. Suggested
7718 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
7722 - Remove the HSAuthorityRecordStats option that version 0 hidden
7723 service authorities could have used to track statistics of overall
7724 hidden service usage.
7727 Changes in version 0.2.1.22 - 2010-01-19
7728 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
7729 authorities -- it would tell you its whole history of bridge descriptors
7730 if you make the right directory request. This stable update also
7731 rotates two of the seven v3 directory authority keys and locations.
7733 o Directory authority changes:
7734 - Rotate keys (both v3 identity and relay identity) for moria1
7738 - Stop bridge directory authorities from answering dbg-stability.txt
7739 directory queries, which would let people fetch a list of all
7740 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7743 Changes in version 0.2.1.21 - 2009-12-21
7744 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
7745 library. If you use Tor on Linux / Unix and you're getting SSL
7746 renegotiation errors, upgrading should help. We also recommend an
7747 upgrade if you're an exit relay.
7750 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7751 handshake from working unless we explicitly tell OpenSSL that we
7752 are using SSL renegotiation safely. We are, of course, but OpenSSL
7753 0.9.8l won't work unless we say we are.
7754 - Avoid crashing if the client is trying to upload many bytes and the
7755 circuit gets torn down at the same time, or if the flip side
7756 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
7759 - Do not refuse to learn about authority certs and v2 networkstatus
7760 documents that are older than the latest consensus. This bug might
7761 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7762 Spotted and fixed by xmux.
7763 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
7764 trigger platform-specific option misparsing case found by Coverity
7766 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
7767 trigger assert. Fixes bug 1173.
7770 Changes in version 0.2.2.6-alpha - 2009-11-19
7771 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
7772 support for the new lower-footprint "microdescriptor" directory design,
7773 future-proofing our consensus format against new hash functions or
7774 other changes, and an Android port. It also makes Tor compatible with
7775 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
7778 - Directory authorities can now create, vote on, and serve multiple
7779 parallel formats of directory data as part of their voting process.
7780 Partially implements Proposal 162: "Publish the consensus in
7782 - Directory authorities can now agree on and publish small summaries
7783 of router information that clients can use in place of regular
7784 server descriptors. This transition will eventually allow clients
7785 to use far less bandwidth for downloading information about the
7786 network. Begins the implementation of Proposal 158: "Clients
7787 download consensus + microdescriptors".
7788 - The directory voting system is now extensible to use multiple hash
7789 algorithms for signatures and resource selection. Newer formats
7790 are signed with SHA256, with a possibility for moving to a better
7791 hash algorithm in the future.
7792 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
7793 current and future memory pages via mlockall(). On supported
7794 platforms (modern Linux and probably BSD but not Windows or OS X),
7795 this should effectively disable any and all attempts to page out
7796 memory. This option requires that you start your Tor as root --
7797 if you use DisableAllSwap, please consider using the User option
7798 to properly reduce the privileges of your Tor.
7799 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
7800 to help Tor build correctly for Android phones.
7803 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7804 handshake from working unless we explicitly tell OpenSSL that we
7805 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
7806 won't work unless we say we are.
7809 - Fix a crash bug when trying to initialize the evdns module in
7810 Libevent 2. Bugfix on 0.2.1.16-rc.
7811 - Stop logging at severity 'warn' when some other Tor client tries
7812 to establish a circuit with us using weak DH keys. It's a protocol
7813 violation, but that doesn't mean ordinary users need to hear about
7814 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
7815 - Do not refuse to learn about authority certs and v2 networkstatus
7816 documents that are older than the latest consensus. This bug might
7817 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7818 Spotted and fixed by xmux.
7819 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
7820 - If all authorities restart at once right before a consensus vote,
7821 nobody will vote about "Running", and clients will get a consensus
7822 with no usable relays. Instead, authorities refuse to build a
7823 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
7824 - If your relay can't keep up with the number of incoming create
7825 cells, it would log one warning per failure into your logs. Limit
7826 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
7827 - Bridges now use "reject *:*" as their default exit policy. Bugfix
7828 on 0.2.0.3-alpha; fixes bug 1113.
7829 - Fix a memory leak on directory authorities during voting that was
7830 introduced in 0.2.2.1-alpha. Found via valgrind.
7833 Changes in version 0.2.1.20 - 2009-10-15
7834 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
7835 services at once, prepares for more performance improvements, and
7836 fixes a bunch of smaller bugs.
7838 The Windows and OS X bundles also include a more recent Vidalia,
7839 and switch from Privoxy to Polipo.
7841 The OS X installers are now drag and drop. It's best to un-install
7842 Tor/Vidalia and then install this new bundle, rather than upgrade. If
7843 you want to upgrade, you'll need to update the paths for Tor and Polipo
7844 in the Vidalia Settings window.
7847 - Send circuit or stream sendme cells when our window has decreased
7848 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7849 by Karsten when testing the "reduce circuit window" performance
7850 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7851 before the release of Tor 0.0.0. This is the new winner of the
7853 - Fix a remotely triggerable memory leak when a consensus document
7854 contains more than one signature from the same voter. Bugfix on
7856 - Avoid segfault in rare cases when finishing an introduction circuit
7857 as a client and finding out that we don't have an introduction key
7858 for it. Fixes bug 1073. Reported by Aaron Swartz.
7861 - Tor now reads the "circwindow" parameter out of the consensus,
7862 and uses that value for its circuit package window rather than the
7863 default of 1000 cells. Begins the implementation of proposal 168.
7865 o New directory authorities:
7866 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7868 - Move moria1 and tonga to alternate IP addresses.
7871 - Fix a signed/unsigned compile warning in 0.2.1.19.
7872 - Fix possible segmentation fault on directory authorities. Bugfix on
7874 - Fix an extremely rare infinite recursion bug that could occur if
7875 we tried to log a message after shutting down the log subsystem.
7876 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7877 - Fix an obscure bug where hidden services on 64-bit big-endian
7878 systems might mis-read the timestamp in v3 introduce cells, and
7879 refuse to connect back to the client. Discovered by "rotor".
7880 Bugfix on 0.2.1.6-alpha.
7881 - We were triggering a CLOCK_SKEW controller status event whenever
7882 we connect via the v2 connection protocol to any relay that has
7883 a wrong clock. Instead, we should only inform the controller when
7884 it's a trusted authority that claims our clock is wrong. Bugfix
7885 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7886 - We were telling the controller about CHECKING_REACHABILITY and
7887 REACHABILITY_FAILED status events whenever we launch a testing
7888 circuit or notice that one has failed. Instead, only tell the
7889 controller when we want to inform the user of overall success or
7890 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7892 - Don't warn when we're using a circuit that ends with a node
7893 excluded in ExcludeExitNodes, but the circuit is not used to access
7894 the outside world. This should help fix bug 1090. Bugfix on
7896 - Work around a small memory leak in some versions of OpenSSL that
7897 stopped the memory used by the hostname TLS extension from being
7901 - Add a "getinfo status/accepted-server-descriptor" controller
7902 command, which is the recommended way for controllers to learn
7903 whether our server descriptor has been successfully received by at
7904 least on directory authority. Un-recommend good-server-descriptor
7905 getinfo and status events until we have a better design for them.
7908 Changes in version 0.2.2.5-alpha - 2009-10-11
7909 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
7912 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
7914 o Directory authorities:
7915 - Temporarily (just for this release) move dizum to an alternate
7919 Changes in version 0.2.2.4-alpha - 2009-10-10
7920 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
7921 introduces a new unit test framework, shifts directry authority
7922 addresses around to reduce the impact from recent blocking events,
7923 and fixes a few smaller bugs.
7926 - Fix several more asserts in the circuit_build_times code, for
7927 example one that causes Tor to fail to start once we have
7928 accumulated 5000 build times in the state file. Bugfixes on
7929 0.2.2.2-alpha; fixes bug 1108.
7931 o New directory authorities:
7932 - Move moria1 and Tonga to alternate IP addresses.
7935 - Log SSL state transitions at debug level during handshake, and
7936 include SSL states in error messages. This may help debug future
7937 SSL handshake issues.
7938 - Add a new "Handshake" log domain for activities that happen
7939 during the TLS handshake.
7940 - Revert to the "June 3 2009" ip-to-country file. The September one
7941 seems to have removed most US IP addresses.
7942 - Directory authorities now reject Tor relays with versions less than
7943 0.1.2.14. This step cuts out four relays from the current network,
7944 none of which are very big.
7947 - Fix a couple of smaller issues with gathering statistics. Bugfixes
7949 - Fix two memory leaks in the error case of
7950 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
7951 - Don't count one-hop circuits when we're estimating how long it
7952 takes circuits to build on average. Otherwise we'll set our circuit
7953 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
7954 - Directory authorities no longer change their opinion of, or vote on,
7955 whether a router is Running, unless they have themselves been
7956 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
7959 o Code simplifications and refactoring:
7960 - Revise our unit tests to use the "tinytest" framework, so we
7961 can run tests in their own processes, have smarter setup/teardown
7962 code, and so on. The unit test code has moved to its own
7963 subdirectory, and has been split into multiple modules.
7966 Changes in version 0.2.2.3-alpha - 2009-09-23
7967 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
7970 - Fix an overzealous assert in our new circuit build timeout code.
7971 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
7974 - If the networkstatus consensus tells us that we should use a
7975 negative circuit package window, ignore it. Otherwise we'll
7976 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
7979 Changes in version 0.2.2.2-alpha - 2009-09-21
7980 Tor 0.2.2.2-alpha introduces our latest performance improvement for
7981 clients: Tor tracks the average time it takes to build a circuit, and
7982 avoids using circuits that take too long to build. For fast connections,
7983 this feature can cut your expected latency in half. For slow or flaky
7984 connections, it could ruin your Tor experience. Let us know if it does!
7987 - Tor now tracks how long it takes to build client-side circuits
7988 over time, and adapts its timeout to local network performance.
7989 Since a circuit that takes a long time to build will also provide
7990 bad performance, we get significant latency improvements by
7991 discarding the slowest 20% of circuits. Specifically, Tor creates
7992 circuits more aggressively than usual until it has enough data
7993 points for a good timeout estimate. Implements proposal 151.
7994 We are especially looking for reports (good and bad) from users with
7995 both EDGE and broadband connections that can move from broadband
7996 to EDGE and find out if the build-time data in the .tor/state gets
7997 reset without loss of Tor usability. You should also see a notice
7998 log message telling you that Tor has reset its timeout.
7999 - Directory authorities can now vote on arbitary integer values as
8000 part of the consensus process. This is designed to help set
8001 network-wide parameters. Implements proposal 167.
8002 - Tor now reads the "circwindow" parameter out of the consensus,
8003 and uses that value for its circuit package window rather than the
8004 default of 1000 cells. Begins the implementation of proposal 168.
8007 - Fix a remotely triggerable memory leak when a consensus document
8008 contains more than one signature from the same voter. Bugfix on
8012 - Fix an extremely rare infinite recursion bug that could occur if
8013 we tried to log a message after shutting down the log subsystem.
8014 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
8015 - Fix parsing for memory or time units given without a space between
8016 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
8017 - A networkstatus vote must contain exactly one signature. Spec
8018 conformance issue. Bugfix on 0.2.0.3-alpha.
8019 - Fix an obscure bug where hidden services on 64-bit big-endian
8020 systems might mis-read the timestamp in v3 introduce cells, and
8021 refuse to connect back to the client. Discovered by "rotor".
8022 Bugfix on 0.2.1.6-alpha.
8023 - We were triggering a CLOCK_SKEW controller status event whenever
8024 we connect via the v2 connection protocol to any relay that has
8025 a wrong clock. Instead, we should only inform the controller when
8026 it's a trusted authority that claims our clock is wrong. Bugfix
8027 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
8028 - We were telling the controller about CHECKING_REACHABILITY and
8029 REACHABILITY_FAILED status events whenever we launch a testing
8030 circuit or notice that one has failed. Instead, only tell the
8031 controller when we want to inform the user of overall success or
8032 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
8034 - Don't warn when we're using a circuit that ends with a node
8035 excluded in ExcludeExitNodes, but the circuit is not used to access
8036 the outside world. This should help fix bug 1090, but more problems
8037 remain. Bugfix on 0.2.1.6-alpha.
8038 - Work around a small memory leak in some versions of OpenSSL that
8039 stopped the memory used by the hostname TLS extension from being
8041 - Make our 'torify' script more portable; if we have only one of
8042 'torsocks' or 'tsocks' installed, don't complain to the user;
8043 and explain our warning about tsocks better.
8046 - Add a "getinfo status/accepted-server-descriptor" controller
8047 command, which is the recommended way for controllers to learn
8048 whether our server descriptor has been successfully received by at
8049 least on directory authority. Un-recommend good-server-descriptor
8050 getinfo and status events until we have a better design for them.
8051 - Update to the "September 4 2009" ip-to-country file.
8054 Changes in version 0.2.2.1-alpha - 2009-08-26
8055 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
8056 Tor clients to bootstrap on networks where only port 80 is reachable,
8057 makes it more straightforward to support hardware crypto accelerators,
8058 and starts the groundwork for gathering stats safely at relays.
8061 - Start the process of disabling ".exit" address notation, since it
8062 can be used for a variety of esoteric application-level attacks
8063 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
8066 o New directory authorities:
8067 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
8071 - New AccelName and AccelDir options add support for dynamic OpenSSL
8072 hardware crypto acceleration engines.
8073 - Tor now supports tunneling all of its outgoing connections over
8074 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
8075 configuration options. Code by Christopher Davis.
8078 - Send circuit or stream sendme cells when our window has decreased
8079 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
8080 by Karsten when testing the "reduce circuit window" performance
8081 patch. Bugfix on the 54th commit on Tor -- from July 2002,
8082 before the release of Tor 0.0.0. This is the new winner of the
8085 o New options for gathering stats safely:
8086 - Directory mirrors that set "DirReqStatistics 1" write statistics
8087 about directory requests to disk every 24 hours. As compared to the
8088 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
8089 1) stats are written to disk exactly every 24 hours; 2) estimated
8090 shares of v2 and v3 requests are determined as mean values, not at
8091 the end of a measurement period; 3) unresolved requests are listed
8092 with country code '??'; 4) directories also measure download times.
8093 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
8094 number of exit streams and transferred bytes per port to disk every
8096 - Relays that set "CellStatistics 1" write statistics on how long
8097 cells spend in their circuit queues to disk every 24 hours.
8098 - Entry nodes that set "EntryStatistics 1" write statistics on the
8099 rough number and origins of connecting clients to disk every 24
8101 - Relays that write any of the above statistics to disk and set
8102 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
8103 their extra-info documents.
8106 - New --digests command-line switch to output the digests of the
8107 source files Tor was built with.
8108 - The "torify" script now uses torsocks where available.
8109 - The memarea code now uses a sentinel value at the end of each area
8110 to make sure nothing writes beyond the end of an area. This might
8111 help debug some conceivable causes of bug 930.
8112 - Time and memory units in the configuration file can now be set to
8113 fractional units. For example, "2.5 GB" is now a valid value for
8115 - Certain Tor clients (such as those behind check.torproject.org) may
8116 want to fetch the consensus in an extra early manner. To enable this
8117 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
8118 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
8119 as only certain clients who must have this information sooner should
8121 - Instead of adding the svn revision to the Tor version string, report
8122 the git commit (when we're building from a git checkout).
8125 - If any of the v3 certs we download are unparseable, we should
8126 actually notice the failure so we don't retry indefinitely. Bugfix
8127 on 0.2.0.x; reported by "rotator".
8128 - If the cached cert file is unparseable, warn but don't exit.
8129 - Fix possible segmentation fault on directory authorities. Bugfix on
8131 - When Tor fails to parse a descriptor of any kind, dump it to disk.
8132 Might help diagnosing bug 1051.
8134 o Deprecated and removed features:
8135 - The controller no longer accepts the old obsolete "addr-mappings/"
8136 or "unregistered-servers-" GETINFO values.
8137 - Hidden services no longer publish version 0 descriptors, and clients
8138 do not request or use version 0 descriptors. However, the old hidden
8139 service authorities still accept and serve version 0 descriptors
8140 when contacted by older hidden services/clients.
8141 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
8142 always on; using them is necessary for correct forward-compatible
8144 - Remove support for .noconnect style addresses. Nobody was using
8145 them, and they provided another avenue for detecting Tor users
8146 via application-level web tricks.
8148 o Packaging changes:
8149 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
8150 installer bundles. See
8151 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
8152 for details of what's new in Vidalia 0.2.3.
8153 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
8154 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
8155 configuration file, rather than the old Privoxy.
8156 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
8157 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
8158 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
8159 better compatibility with OS X 10.6, aka Snow Leopard.
8160 - OS X Vidalia Bundle: The multi-package installer is now replaced
8161 by a simple drag and drop to the /Applications folder. This change
8162 occurred with the upgrade to Vidalia 0.2.3.
8165 Changes in version 0.2.1.19 - 2009-07-28
8166 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
8167 services on Tor 0.2.1.3-alpha through 0.2.1.18.
8170 - Make accessing hidden services on 0.2.1.x work right again.
8171 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
8172 part of patch provided by "optimist".
8175 - When a relay/bridge is writing out its identity key fingerprint to
8176 the "fingerprint" file and to its logs, write it without spaces. Now
8177 it will look like the fingerprints in our bridges documentation,
8178 and confuse fewer users.
8181 - Relays no longer publish a new server descriptor if they change
8182 their MaxAdvertisedBandwidth config option but it doesn't end up
8183 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
8184 fixes bug 1026. Patch from Sebastian.
8185 - Avoid leaking memory every time we get a create cell but we have
8186 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
8187 fixes bug 1034. Reported by BarkerJr.
8190 Changes in version 0.2.1.18 - 2009-07-24
8191 Tor 0.2.1.18 lays the foundations for performance improvements,
8192 adds status events to help users diagnose bootstrap problems, adds
8193 optional authentication/authorization for hidden services, fixes a
8194 variety of potential anonymity problems, and includes a huge pile of
8195 other features and bug fixes.
8198 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
8201 Changes in version 0.2.1.17-rc - 2009-07-07
8202 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
8203 candidate for the 0.2.1.x series. It lays the groundwork for further
8204 client performance improvements, and also fixes a big bug with directory
8205 authorities that were causing them to assign Guard and Stable flags
8208 The Windows bundles also finally include the geoip database that we
8209 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
8210 should actually install Torbutton rather than giving you a cryptic
8211 failure message (oops).
8214 - Clients now use the bandwidth values in the consensus, rather than
8215 the bandwidth values in each relay descriptor. This approach opens
8216 the door to more accurate bandwidth estimates once the directory
8217 authorities start doing active measurements. Implements more of
8221 - When Tor clients restart after 1-5 days, they discard all their
8222 cached descriptors as too old, but they still use the cached
8223 consensus document. This approach is good for robustness, but
8224 bad for performance: since they don't know any bandwidths, they
8225 end up choosing at random rather than weighting their choice by
8226 speed. Fixed by the above feature of putting bandwidths in the
8227 consensus. Bugfix on 0.2.0.x.
8228 - Directory authorities were neglecting to mark relays down in their
8229 internal histories if the relays fall off the routerlist without
8230 ever being found unreachable. So there were relays in the histories
8231 that haven't been seen for eight months, and are listed as being
8232 up for eight months. This wreaked havoc on the "median wfu"
8233 and "median mtbf" calculations, in turn making Guard and Stable
8234 flags very wrong, hurting network performance. Fixes bugs 696 and
8235 969. Bugfix on 0.2.0.6-alpha.
8238 - Serve the DirPortFrontPage page even when we have been approaching
8239 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
8240 - The control port would close the connection before flushing long
8241 replies, such as the network consensus, if a QUIT command was issued
8242 before the reply had completed. Now, the control port flushes all
8243 pending replies before closing the connection. Also fixed a spurious
8244 warning when a QUIT command is issued after a malformed or rejected
8245 AUTHENTICATE command, but before the connection was closed. Patch
8246 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
8247 - When we can't find an intro key for a v2 hidden service descriptor,
8248 fall back to the v0 hidden service descriptor and log a bug message.
8249 Workaround for bug 1024.
8250 - Fix a log message that did not respect the SafeLogging option.
8254 - If we're a relay and we change our IP address, be more verbose
8255 about the reason that made us change. Should help track down
8256 further bugs for relays on dynamic IP addresses.
8259 Changes in version 0.2.0.35 - 2009-06-24
8261 - Avoid crashing in the presence of certain malformed descriptors.
8262 Found by lark, and by automated fuzzing.
8263 - Fix an edge case where a malicious exit relay could convince a
8264 controller that the client's DNS question resolves to an internal IP
8265 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
8268 - Finally fix the bug where dynamic-IP relays disappear when their
8269 IP address changes: directory mirrors were mistakenly telling
8270 them their old address if they asked via begin_dir, so they
8271 never got an accurate answer about their new address, so they
8272 just vanished after a day. For belt-and-suspenders, relays that
8273 don't set Address in their config now avoid using begin_dir for
8274 all direct connections. Should fix bugs 827, 883, and 900.
8275 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
8276 that would occur on some exit nodes when DNS failures and timeouts
8277 occurred in certain patterns. Fix for bug 957.
8280 - When starting with a cache over a few days old, do not leak
8281 memory for the obsolete router descriptors in it. Bugfix on
8282 0.2.0.33; fixes bug 672.
8283 - Hidden service clients didn't use a cached service descriptor that
8284 was older than 15 minutes, but wouldn't fetch a new one either,
8285 because there was already one in the cache. Now, fetch a v2
8286 descriptor unless the same descriptor was added to the cache within
8287 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
8290 Changes in version 0.2.1.16-rc - 2009-06-20
8291 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
8292 a bunch of minor bugs.
8295 - Fix an edge case where a malicious exit relay could convince a
8296 controller that the client's DNS question resolves to an internal IP
8297 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
8299 o Major performance improvements (on 0.2.0.x):
8300 - Disable and refactor some debugging checks that forced a linear scan
8301 over the whole server-side DNS cache. These accounted for over 50%
8302 of CPU time on a relatively busy exit node's gprof profile. Found
8304 - Disable some debugging checks that appeared in exit node profile
8308 - Update to the "June 3 2009" ip-to-country file.
8309 - Do not have tor-resolve automatically refuse all .onion addresses;
8310 if AutomapHostsOnResolve is set in your torrc, this will work fine.
8312 o Minor bugfixes (on 0.2.0.x):
8313 - Log correct error messages for DNS-related network errors on
8315 - Fix a race condition that could cause crashes or memory corruption
8316 when running as a server with a controller listening for log
8318 - Avoid crashing when we have a policy specified in a DirPolicy or
8319 SocksPolicy or ReachableAddresses option with ports set on it,
8320 and we re-load the policy. May fix bug 996.
8321 - Hidden service clients didn't use a cached service descriptor that
8322 was older than 15 minutes, but wouldn't fetch a new one either,
8323 because there was already one in the cache. Now, fetch a v2
8324 descriptor unless the same descriptor was added to the cache within
8325 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
8327 o Minor bugfixes (on 0.2.1.x):
8328 - Don't warn users about low port and hibernation mix when they
8329 provide a *ListenAddress directive to fix that. Bugfix on
8331 - When switching back and forth between bridge mode, do not start
8332 gathering GeoIP data until two hours have passed.
8333 - Do not complain that the user has requested an excluded node as
8334 an exit when the node is not really an exit. This could happen
8335 because the circuit was for testing, or an introduction point.
8339 Changes in version 0.2.1.15-rc - 2009-05-25
8340 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
8341 series. It fixes a major bug on fast exit relays, as well as a variety
8344 o Major bugfixes (on 0.2.0.x):
8345 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
8346 that would occur on some exit nodes when DNS failures and timeouts
8347 occurred in certain patterns. Fix for bug 957.
8349 o Minor bugfixes (on 0.2.0.x):
8350 - Actually return -1 in the error case for read_bandwidth_usage().
8351 Harmless bug, since we currently don't care about the return value
8352 anywhere. Bugfix on 0.2.0.9-alpha.
8353 - Provide a more useful log message if bug 977 (related to buffer
8354 freelists) ever reappears, and do not crash right away.
8355 - Fix an assertion failure on 64-bit platforms when we allocated
8356 memory right up to the end of a memarea, then realigned the memory
8357 one step beyond the end. Fixes a possible cause of bug 930.
8358 - Protect the count of open sockets with a mutex, so we can't
8359 corrupt it when two threads are closing or opening sockets at once.
8360 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
8361 - Don't allow a bridge to publish its router descriptor to a
8362 non-bridge directory authority. Fixes part of bug 932.
8363 - When we change to or from being a bridge, reset our counts of
8364 client usage by country. Fixes bug 932.
8365 - Fix a bug that made stream bandwidth get misreported to the
8367 - Stop using malloc_usable_size() to use more area than we had
8368 actually allocated: it was safe, but made valgrind really unhappy.
8369 - Fix a memory leak when v3 directory authorities load their keys
8370 and cert from disk. Bugfix on 0.2.0.1-alpha.
8372 o Minor bugfixes (on 0.2.1.x):
8373 - Fix use of freed memory when deciding to mark a non-addable
8374 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
8377 Changes in version 0.2.1.14-rc - 2009-04-12
8378 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
8379 series. It begins fixing some major performance problems, and also
8380 finally addresses the bug that was causing relays on dynamic IP
8381 addresses to fall out of the directory.
8384 - Clients replace entry guards that were chosen more than a few months
8385 ago. This change should significantly improve client performance,
8386 especially once more people upgrade, since relays that have been
8387 a guard for a long time are currently overloaded.
8389 o Major bugfixes (on 0.2.0):
8390 - Finally fix the bug where dynamic-IP relays disappear when their
8391 IP address changes: directory mirrors were mistakenly telling
8392 them their old address if they asked via begin_dir, so they
8393 never got an accurate answer about their new address, so they
8394 just vanished after a day. For belt-and-suspenders, relays that
8395 don't set Address in their config now avoid using begin_dir for
8396 all direct connections. Should fix bugs 827, 883, and 900.
8397 - Relays were falling out of the networkstatus consensus for
8398 part of a day if they changed their local config but the
8399 authorities discarded their new descriptor as "not sufficiently
8400 different". Now directory authorities accept a descriptor as changed
8401 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
8403 - Avoid crashing in the presence of certain malformed descriptors.
8404 Found by lark, and by automated fuzzing.
8407 - When generating circuit events with verbose nicknames for
8408 controllers, try harder to look up nicknames for routers on a
8409 circuit. (Previously, we would look in the router descriptors we had
8410 for nicknames, but not in the consensus.) Partial fix for bug 941.
8411 - If the bridge config line doesn't specify a port, assume 443.
8412 This makes bridge lines a bit smaller and easier for users to
8414 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
8415 bytes (aka 20KB/s), to match our documentation. Also update
8416 directory authorities so they always assign the Fast flag to relays
8417 with 20KB/s of capacity. Now people running relays won't suddenly
8418 find themselves not seeing any use, if the network gets faster
8420 - Update to the "April 3 2009" ip-to-country file.
8423 - Avoid trying to print raw memory to the logs when we decide to
8424 give up on downloading a given relay descriptor. Bugfix on
8426 - In tor-resolve, when the Tor client to use is specified by
8427 <hostname>:<port>, actually use the specified port rather than
8428 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
8429 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
8430 - When starting with a cache over a few days old, do not leak
8431 memory for the obsolete router descriptors in it. Bugfix on
8433 - Avoid double-free on list of successfully uploaded hidden
8434 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
8435 - Change memarea_strndup() implementation to work even when
8436 duplicating a string at the end of a page. This bug was
8437 harmless for now, but could have meant crashes later. Fix by
8438 lark. Bugfix on 0.2.1.1-alpha.
8439 - Limit uploaded directory documents to be 16M rather than 500K.
8440 The directory authorities were refusing v3 consensus votes from
8441 other authorities, since the votes are now 504K. Fixes bug 959;
8442 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
8443 - Directory authorities should never send a 503 "busy" response to
8444 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
8448 Changes in version 0.2.1.13-alpha - 2009-03-09
8449 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
8450 cleanups. We're finally getting close to a release candidate.
8453 - Correctly update the list of which countries we exclude as
8454 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
8455 lark. Bugfix on 0.2.1.6-alpha.
8457 o Minor bugfixes (on 0.2.0.x and earlier):
8458 - Automatically detect MacOSX versions earlier than 10.4.0, and
8459 disable kqueue from inside Tor when running with these versions.
8460 We previously did this from the startup script, but that was no
8461 help to people who didn't use the startup script. Resolves bug 863.
8462 - When we had picked an exit node for a connection, but marked it as
8463 "optional", and it turned out we had no onion key for the exit,
8464 stop wanting that exit and try again. This situation may not
8465 be possible now, but will probably become feasible with proposal
8466 158. Spotted by rovv. Fixes another case of bug 752.
8467 - Clients no longer cache certificates for authorities they do not
8468 recognize. Bugfix on 0.2.0.9-alpha.
8469 - When we can't transmit a DNS request due to a network error, retry
8470 it after a while, and eventually transmit a failing response to
8471 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
8472 - If the controller claimed responsibility for a stream, but that
8473 stream never finished making its connection, it would live
8474 forever in circuit_wait state. Now we close it after SocksTimeout
8475 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
8476 - Drop begin cells to a hidden service if they come from the middle
8477 of a circuit. Patch from lark.
8478 - When we erroneously receive two EXTEND cells for the same circuit
8479 ID on the same connection, drop the second. Patch from lark.
8480 - Fix a crash that occurs on exit nodes when a nameserver request
8481 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
8482 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
8484 - Do not assume that a stack-allocated character array will be
8485 64-bit aligned on platforms that demand that uint64_t access is
8486 aligned. Possible fix for bug 604.
8487 - Parse dates and IPv4 addresses in a locale- and libc-independent
8488 manner, to avoid platform-dependent behavior on malformed input.
8489 - Build correctly when configured to build outside the main source
8490 path. Patch from Michael Gold.
8491 - We were already rejecting relay begin cells with destination port
8492 of 0. Now also reject extend cells with destination port or address
8493 of 0. Suggested by lark.
8495 o Minor bugfixes (on 0.2.1.x):
8496 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
8497 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
8498 - If we're an exit node, scrub the IP address to which we are exiting
8499 in the logs. Bugfix on 0.2.1.8-alpha.
8502 - On Linux, use the prctl call to re-enable core dumps when the user
8504 - New controller event NEWCONSENSUS that lists the networkstatus
8505 lines for every recommended relay. Now controllers like Torflow
8506 can keep up-to-date on which relays they should be using.
8507 - Update to the "February 26 2009" ip-to-country file.
8510 Changes in version 0.2.0.34 - 2009-02-08
8511 Tor 0.2.0.34 features several more security-related fixes. You should
8512 upgrade, especially if you run an exit relay (remote crash) or a
8513 directory authority (remote infinite loop), or you're on an older
8514 (pre-XP) or not-recently-patched Windows (remote exploit).
8516 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
8517 have many known flaws, and nobody should be using them. You should
8518 upgrade. If you're using a Linux or BSD and its packages are obsolete,
8519 stop using those packages and upgrade anyway.
8522 - Fix an infinite-loop bug on handling corrupt votes under certain
8523 circumstances. Bugfix on 0.2.0.8-alpha.
8524 - Fix a temporary DoS vulnerability that could be performed by
8525 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
8526 - Avoid a potential crash on exit nodes when processing malformed
8527 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
8528 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8529 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8532 - Fix compilation on systems where time_t is a 64-bit integer.
8533 Patch from Matthias Drochner.
8534 - Don't consider expiring already-closed client connections. Fixes
8535 bug 893. Bugfix on 0.0.2pre20.
8538 Changes in version 0.2.1.12-alpha - 2009-02-08
8539 Tor 0.2.1.12-alpha features several more security-related fixes. You
8540 should upgrade, especially if you run an exit relay (remote crash) or
8541 a directory authority (remote infinite loop), or you're on an older
8542 (pre-XP) or not-recently-patched Windows (remote exploit). It also
8543 includes a big pile of minor bugfixes and cleanups.
8546 - Fix an infinite-loop bug on handling corrupt votes under certain
8547 circumstances. Bugfix on 0.2.0.8-alpha.
8548 - Fix a temporary DoS vulnerability that could be performed by
8549 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
8550 - Avoid a potential crash on exit nodes when processing malformed
8551 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
8554 - Let controllers actually ask for the "clients_seen" event for
8555 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
8556 reported by Matt Edman.
8557 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
8559 - Fix a bug in address parsing that was preventing bridges or hidden
8560 service targets from being at IPv6 addresses.
8561 - Solve a bug that kept hardware crypto acceleration from getting
8562 enabled when accounting was turned on. Fixes bug 907. Bugfix on
8564 - Remove a bash-ism from configure.in to build properly on non-Linux
8565 platforms. Bugfix on 0.2.1.1-alpha.
8566 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
8567 headers. Bugfix on 0.2.0.10-alpha.
8568 - Don't consider expiring already-closed client connections. Fixes
8569 bug 893. Bugfix on 0.0.2pre20.
8570 - Fix another interesting corner-case of bug 891 spotted by rovv:
8571 Previously, if two hosts had different amounts of clock drift, and
8572 one of them created a new connection with just the wrong timing,
8573 the other might decide to deprecate the new connection erroneously.
8574 Bugfix on 0.1.1.13-alpha.
8575 - Resolve a very rare crash bug that could occur when the user forced
8576 a nameserver reconfiguration during the middle of a nameserver
8577 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
8578 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
8579 Bugfix on 0.2.1.7-alpha.
8580 - If we're using bridges and our network goes away, be more willing
8581 to forgive our bridges and try again when we get an application
8582 request. Bugfix on 0.2.0.x.
8585 - Support platforms where time_t is 64 bits long. (Congratulations,
8586 NetBSD!) Patch from Matthias Drochner.
8587 - Add a 'getinfo status/clients-seen' controller command, in case
8588 controllers want to hear clients_seen events but connect late.
8591 - Disable GCC's strict alias optimization by default, to avoid the
8592 likelihood of its introducing subtle bugs whenever our code violates
8593 the letter of C99's alias rules.
8596 Changes in version 0.2.0.33 - 2009-01-21
8597 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
8598 useful to users. It also finally fixes a bug where a relay or client
8599 that's been off for many days would take a long time to bootstrap.
8601 This update also fixes an important security-related bug reported by
8602 Ilja van Sprundel. You should upgrade. (We'll send out more details
8603 about the bug once people have had some time to upgrade.)
8606 - Fix a heap-corruption bug that may be remotely triggerable on
8607 some platforms. Reported by Ilja van Sprundel.
8610 - When a stream at an exit relay is in state "resolving" or
8611 "connecting" and it receives an "end" relay cell, the exit relay
8612 would silently ignore the end cell and not close the stream. If
8613 the client never closes the circuit, then the exit relay never
8614 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
8616 - When sending CREATED cells back for a given circuit, use a 64-bit
8617 connection ID to find the right connection, rather than an addr:port
8618 combination. Now that we can have multiple OR connections between
8619 the same ORs, it is no longer possible to use addr:port to uniquely
8620 identify a connection.
8621 - Bridge relays that had DirPort set to 0 would stop fetching
8622 descriptors shortly after startup, and then briefly resume
8623 after a new bandwidth test and/or after publishing a new bridge
8624 descriptor. Bridge users that try to bootstrap from them would
8625 get a recent networkstatus but would get descriptors from up to
8626 18 hours earlier, meaning most of the descriptors were obsolete
8627 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8628 - Prevent bridge relays from serving their 'extrainfo' document
8629 to anybody who asks, now that extrainfo docs include potentially
8630 sensitive aggregated client geoip summaries. Bugfix on
8632 - If the cached networkstatus consensus is more than five days old,
8633 discard it rather than trying to use it. In theory it could be
8634 useful because it lists alternate directory mirrors, but in practice
8635 it just means we spend many minutes trying directory mirrors that
8636 are long gone from the network. Also discard router descriptors as
8637 we load them if they are more than five days old, since the onion
8638 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
8641 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8642 could make gcc generate non-functional binary search code. Bugfix
8644 - Build correctly on platforms without socklen_t.
8645 - Compile without warnings on solaris.
8646 - Avoid potential crash on internal error during signature collection.
8647 Fixes bug 864. Patch from rovv.
8648 - Correct handling of possible malformed authority signing key
8649 certificates with internal signature types. Fixes bug 880.
8650 Bugfix on 0.2.0.3-alpha.
8651 - Fix a hard-to-trigger resource leak when logging credential status.
8653 - When we can't initialize DNS because the network is down, do not
8654 automatically stop Tor from starting. Instead, we retry failed
8655 dns_init() every 10 minutes, and change the exit policy to reject
8656 *:* until one succeeds. Fixes bug 691.
8657 - Use 64 bits instead of 32 bits for connection identifiers used with
8658 the controller protocol, to greatly reduce risk of identifier reuse.
8659 - When we're choosing an exit node for a circuit, and we have
8660 no pending streams, choose a good general exit rather than one that
8661 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8662 - Fix another case of assuming, when a specific exit is requested,
8663 that we know more than the user about what hosts it allows.
8664 Fixes one case of bug 752. Patch from rovv.
8665 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8666 seconds. Warn the user if lower values are given in the
8667 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8668 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8669 user if lower values are given in the configuration. Bugfix on
8670 0.1.1.17-rc. Patch by Sebastian.
8671 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
8672 the cache because we already had a v0 descriptor with the same ID.
8673 Bugfix on 0.2.0.18-alpha.
8674 - Fix a race condition when freeing keys shared between main thread
8675 and CPU workers that could result in a memory leak. Bugfix on
8676 0.1.0.1-rc. Fixes bug 889.
8677 - Send a valid END cell back when a client tries to connect to a
8678 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8679 840. Patch from rovv.
8680 - Check which hops rendezvous stream cells are associated with to
8681 prevent possible guess-the-streamid injection attacks from
8682 intermediate hops. Fixes another case of bug 446. Based on patch
8684 - If a broken client asks a non-exit router to connect somewhere,
8685 do not even do the DNS lookup before rejecting the connection.
8686 Fixes another case of bug 619. Patch from rovv.
8687 - When a relay gets a create cell it can't decrypt (e.g. because it's
8688 using the wrong onion key), we were dropping it and letting the
8689 client time out. Now actually answer with a destroy cell. Fixes
8690 bug 904. Bugfix on 0.0.2pre8.
8692 o Minor bugfixes (hidden services):
8693 - Do not throw away existing introduction points on SIGHUP. Bugfix on
8694 0.0.6pre1. Patch by Karsten. Fixes bug 874.
8697 - Report the case where all signatures in a detached set are rejected
8698 differently than the case where there is an error handling the
8700 - When we realize that another process has modified our cached
8701 descriptors, print out a more useful error message rather than
8702 triggering an assertion. Fixes bug 885. Patch from Karsten.
8703 - Implement the 0x20 hack to better resist DNS poisoning: set the
8704 case on outgoing DNS requests randomly, and reject responses that do
8705 not match the case correctly. This logic can be disabled with the
8706 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
8707 of servers that do not reliably preserve case in replies. See
8708 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8710 - Check DNS replies for more matching fields to better resist DNS
8712 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8713 compress cells, which are basically all encrypted, compressed, or
8717 Changes in version 0.2.1.11-alpha - 2009-01-20
8718 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
8719 week it will take a long time to bootstrap again" bug. It also fixes
8720 an important security-related bug reported by Ilja van Sprundel. You
8721 should upgrade. (We'll send out more details about the bug once people
8722 have had some time to upgrade.)
8725 - Fix a heap-corruption bug that may be remotely triggerable on
8726 some platforms. Reported by Ilja van Sprundel.
8729 - Discard router descriptors as we load them if they are more than
8730 five days old. Otherwise if Tor is off for a long time and then
8731 starts with cached descriptors, it will try to use the onion
8732 keys in those obsolete descriptors when building circuits. Bugfix
8733 on 0.2.0.x. Fixes bug 887.
8736 - Try to make sure that the version of Libevent we're running with
8737 is binary-compatible with the one we built with. May address bug
8739 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
8740 for bug 905. Bugfix on 0.2.1.7-alpha.
8741 - Add a new --enable-local-appdata configuration switch to change
8742 the default location of the datadir on win32 from APPDATA to
8743 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
8744 entirely. Patch from coderman.
8747 - Make outbound DNS packets respect the OutboundBindAddress setting.
8748 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
8749 - When our circuit fails at the first hop (e.g. we get a destroy
8750 cell back), avoid using that OR connection anymore, and also
8751 tell all the one-hop directory requests waiting for it that they
8752 should fail. Bugfix on 0.2.1.3-alpha.
8753 - In the torify(1) manpage, mention that tsocks will leak your
8757 Changes in version 0.2.1.10-alpha - 2009-01-06
8758 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
8759 would make the bridge relay not so useful if it had DirPort set to 0,
8760 and one that could let an attacker learn a little bit of information
8761 about the bridge's users), and a bug that would cause your Tor relay
8762 to ignore a circuit create request it can't decrypt (rather than reply
8763 with an error). It also fixes a wide variety of other bugs.
8766 - If the cached networkstatus consensus is more than five days old,
8767 discard it rather than trying to use it. In theory it could
8768 be useful because it lists alternate directory mirrors, but in
8769 practice it just means we spend many minutes trying directory
8770 mirrors that are long gone from the network. Helps bug 887 a bit;
8772 - Bridge relays that had DirPort set to 0 would stop fetching
8773 descriptors shortly after startup, and then briefly resume
8774 after a new bandwidth test and/or after publishing a new bridge
8775 descriptor. Bridge users that try to bootstrap from them would
8776 get a recent networkstatus but would get descriptors from up to
8777 18 hours earlier, meaning most of the descriptors were obsolete
8778 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8779 - Prevent bridge relays from serving their 'extrainfo' document
8780 to anybody who asks, now that extrainfo docs include potentially
8781 sensitive aggregated client geoip summaries. Bugfix on
8785 - New controller event "clients_seen" to report a geoip-based summary
8786 of which countries we've seen clients from recently. Now controllers
8787 like Vidalia can show bridge operators that they're actually making
8789 - Build correctly against versions of OpenSSL 0.9.8 or later built
8790 without support for deprecated functions.
8791 - Update to the "December 19 2008" ip-to-country file.
8793 o Minor bugfixes (on 0.2.0.x):
8794 - Authorities now vote for the Stable flag for any router whose
8795 weighted MTBF is at least 5 days, regardless of the mean MTBF.
8796 - Do not remove routers as too old if we do not have any consensus
8797 document. Bugfix on 0.2.0.7-alpha.
8798 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8799 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8800 - When an exit relay resolves a stream address to a local IP address,
8801 do not just keep retrying that same exit relay over and
8802 over. Instead, just close the stream. Addresses bug 872. Bugfix
8803 on 0.2.0.32. Patch from rovv.
8804 - If a hidden service sends us an END cell, do not consider
8805 retrying the connection; just close it. Patch from rovv.
8806 - When we made bridge authorities stop serving bridge descriptors over
8807 unencrypted links, we also broke DirPort reachability testing for
8808 bridges. So bridges with a non-zero DirPort were printing spurious
8809 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
8810 - When a relay gets a create cell it can't decrypt (e.g. because it's
8811 using the wrong onion key), we were dropping it and letting the
8812 client time out. Now actually answer with a destroy cell. Fixes
8813 bug 904. Bugfix on 0.0.2pre8.
8814 - Squeeze 2-5% out of client performance (according to oprofile) by
8815 improving the implementation of some policy-manipulation functions.
8817 o Minor bugfixes (on 0.2.1.x):
8818 - Make get_interface_address() function work properly again; stop
8819 guessing the wrong parts of our address as our address.
8820 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
8821 send on that circuit. Otherwise we might violate the proposal-110
8822 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
8824 - When we're sending non-EXTEND cells to the first hop in a circuit,
8825 for example to use an encrypted directory connection, we don't need
8826 to use RELAY_EARLY cells: the first hop knows what kind of cell
8827 it is, and nobody else can even see the cell type. Conserving
8828 RELAY_EARLY cells makes it easier to cannibalize circuits like
8830 - Stop logging nameserver addresses in reverse order.
8831 - If we are retrying a directory download slowly over and over, do
8832 not automatically give up after the 254th failure. Bugfix on
8834 - Resume reporting accurate "stream end" reasons to the local control
8835 port. They were lost in the changes for Proposal 148. Bugfix on
8838 o Deprecated and removed features:
8839 - The old "tor --version --version" command, which would print out
8840 the subversion "Id" of most of the source files, is now removed. It
8841 turned out to be less useful than we'd expected, and harder to
8844 o Code simplifications and refactoring:
8845 - Change our header file guard macros to be less likely to conflict
8846 with system headers. Adam Langley noticed that we were conflicting
8847 with log.h on Android.
8848 - Tool-assisted documentation cleanup. Nearly every function or
8849 static variable in Tor should have its own documentation now.
8852 Changes in version 0.2.1.9-alpha - 2008-12-25
8853 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
8855 o New directory authorities:
8856 - gabelmoo (the authority run by Karsten Loesing) now has a new
8860 - Never use a connection with a mismatched address to extend a
8861 circuit, unless that connection is canonical. A canonical
8862 connection is one whose address is authenticated by the router's
8863 identity key, either in a NETINFO cell or in a router descriptor.
8864 - Avoid a possible memory corruption bug when receiving hidden service
8865 descriptors. Bugfix on 0.2.1.6-alpha.
8868 - Fix a logic error that would automatically reject all but the first
8869 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
8870 part of bug 813/868. Bug spotted by coderman.
8871 - When a stream at an exit relay is in state "resolving" or
8872 "connecting" and it receives an "end" relay cell, the exit relay
8873 would silently ignore the end cell and not close the stream. If
8874 the client never closes the circuit, then the exit relay never
8875 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
8877 - When we can't initialize DNS because the network is down, do not
8878 automatically stop Tor from starting. Instead, retry failed
8879 dns_init() every 10 minutes, and change the exit policy to reject
8880 *:* until one succeeds. Fixes bug 691.
8883 - Give a better error message when an overzealous init script says
8884 "sudo -u username tor --user username". Makes Bug 882 easier for
8886 - When a directory authority gives us a new guess for our IP address,
8887 log which authority we used. Hopefully this will help us debug
8888 the recent complaints about bad IP address guesses.
8889 - Detect svn revision properly when we're using git-svn.
8890 - Try not to open more than one descriptor-downloading connection
8891 to an authority at once. This should reduce load on directory
8892 authorities. Fixes bug 366.
8893 - Add cross-certification to newly generated certificates, so that
8894 a signing key is enough information to look up a certificate.
8895 Partial implementation of proposal 157.
8896 - Start serving certificates by <identity digest, signing key digest>
8897 pairs. Partial implementation of proposal 157.
8898 - Clients now never report any stream end reason except 'MISC'.
8899 Implements proposal 148.
8900 - On platforms with a maximum syslog string length, truncate syslog
8901 messages to that length ourselves, rather than relying on the
8902 system to do it for us.
8903 - Optimize out calls to time(NULL) that occur for every IO operation,
8904 or for every cell. On systems where time() is a slow syscall,
8905 this fix will be slightly helpful.
8906 - Exit servers can now answer resolve requests for ip6.arpa addresses.
8907 - When we download a descriptor that we then immediately (as
8908 a directory authority) reject, do not retry downloading it right
8909 away. Should save some bandwidth on authorities. Fix for bug
8910 888. Patch by Sebastian Hahn.
8911 - When a download gets us zero good descriptors, do not notify
8912 Tor that new directory information has arrived.
8913 - Avoid some nasty corner cases in the logic for marking connections
8914 as too old or obsolete or noncanonical for circuits. Partial
8917 o Minor features (controller):
8918 - New CONSENSUS_ARRIVED event to note when a new consensus has
8919 been fetched and validated.
8920 - When we realize that another process has modified our cached
8921 descriptors file, print out a more useful error message rather
8922 than triggering an assertion. Fixes bug 885. Patch from Karsten.
8923 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8924 controllers to prevent SIGHUP from reloading the
8925 configuration. Fixes bug 856.
8928 - Resume using the correct "REASON=" stream when telling the
8929 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
8930 - When a canonical connection appears later in our internal list
8931 than a noncanonical one for a given OR ID, always use the
8932 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8934 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8935 seconds. Warn the user if lower values are given in the
8936 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8937 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8938 user if lower values are given in the configuration. Bugfix on
8939 0.1.1.17-rc. Patch by Sebastian.
8940 - Fix a race condition when freeing keys shared between main thread
8941 and CPU workers that could result in a memory leak. Bugfix on
8942 0.1.0.1-rc. Fixes bug 889.
8944 o Minor bugfixes (hidden services):
8945 - Do not throw away existing introduction points on SIGHUP (bugfix on
8946 0.0.6pre1); also, do not stall hidden services because we're
8947 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
8948 by John Brooks. Patch by Karsten. Fixes bug 874.
8949 - Fix a memory leak when we decline to add a v2 rendezvous
8950 descriptor to the cache because we already had a v0 descriptor
8951 with the same ID. Bugfix on 0.2.0.18-alpha.
8953 o Deprecated and removed features:
8954 - RedirectExits has been removed. It was deprecated since
8956 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8957 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8958 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8960 o Code simplifications and refactoring:
8961 - Rename the confusing or_is_obsolete field to the more appropriate
8962 is_bad_for_new_circs, and move it to or_connection_t where it
8964 - Move edge-only flags from connection_t to edge_connection_t: not
8965 only is this better coding, but on machines of plausible alignment,
8966 it should save 4-8 bytes per connection_t. "Every little bit helps."
8967 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8968 for consistency; keep old option working for backward compatibility.
8969 - Simplify the code for finding connections to use for a circuit.
8972 Changes in version 0.2.1.8-alpha - 2008-12-08
8973 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
8974 builds better on unusual platforms like Solaris and old OS X, and
8975 fixes a variety of other issues.
8978 - New DirPortFrontPage option that takes an html file and publishes
8979 it as "/" on the DirPort. Now relay operators can provide a
8980 disclaimer without needing to set up a separate webserver. There's
8981 a sample disclaimer in contrib/tor-exit-notice.html.
8984 - When the client is choosing entry guards, now it selects at most
8985 one guard from a given relay family. Otherwise we could end up with
8986 all of our entry points into the network run by the same operator.
8987 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
8990 - Fix a DOS opportunity during the voting signature collection process
8991 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8992 - Fix a possible segfault when establishing an exit connection. Bugfix
8996 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
8998 - Made Tor a little less aggressive about deleting expired
8999 certificates. Partial fix for bug 854.
9000 - Stop doing unaligned memory access that generated bus errors on
9001 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
9002 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
9003 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
9004 - Make USR2 log-level switch take effect immediately. Bugfix on
9006 - If one win32 nameserver fails to get added, continue adding the
9007 rest, and don't automatically fail.
9008 - Use fcntl() for locking when flock() is not available. Should fix
9009 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
9010 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
9011 could make gcc generate non-functional binary search code. Bugfix
9013 - Build correctly on platforms without socklen_t.
9014 - Avoid potential crash on internal error during signature collection.
9015 Fixes bug 864. Patch from rovv.
9016 - Do not use C's stdio library for writing to log files. This will
9017 improve logging performance by a minute amount, and will stop
9018 leaking fds when our disk is full. Fixes bug 861.
9019 - Stop erroneous use of O_APPEND in cases where we did not in fact
9020 want to re-seek to the end of a file before every last write().
9021 - Correct handling of possible malformed authority signing key
9022 certificates with internal signature types. Fixes bug 880. Bugfix
9024 - Fix a hard-to-trigger resource leak when logging credential status.
9028 - Directory mirrors no longer fetch the v1 directory or
9029 running-routers files. They are obsolete, and nobody asks for them
9030 anymore. This is the first step to making v1 authorities obsolete.
9032 o Minor features (controller):
9033 - Return circuit purposes in response to GETINFO circuit-status. Fixes
9037 Changes in version 0.2.0.32 - 2008-11-20
9038 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
9039 packages (and maybe other packages) noticed by Theo de Raadt, fixes
9040 a smaller security flaw that might allow an attacker to access local
9041 services, further improves hidden service performance, and fixes a
9042 variety of other issues.
9045 - The "User" and "Group" config options did not clear the
9046 supplementary group entries for the Tor process. The "User" option
9047 is now more robust, and we now set the groups to the specified
9048 user's primary group. The "Group" option is now ignored. For more
9049 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
9050 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
9051 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
9052 - The "ClientDNSRejectInternalAddresses" config option wasn't being
9053 consistently obeyed: if an exit relay refuses a stream because its
9054 exit policy doesn't allow it, we would remember what IP address
9055 the relay said the destination address resolves to, even if it's
9056 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
9059 - Fix a DOS opportunity during the voting signature collection process
9060 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
9062 o Major bugfixes (hidden services):
9063 - When fetching v0 and v2 rendezvous service descriptors in parallel,
9064 we were failing the whole hidden service request when the v0
9065 descriptor fetch fails, even if the v2 fetch is still pending and
9066 might succeed. Similarly, if the last v2 fetch fails, we were
9067 failing the whole hidden service request even if a v0 fetch is
9068 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
9069 - When extending a circuit to a hidden service directory to upload a
9070 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
9071 requests failed, because the router descriptor has not been
9072 downloaded yet. In these cases, do not attempt to upload the
9073 rendezvous descriptor, but wait until the router descriptor is
9074 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
9075 descriptor from a hidden service directory for which the router
9076 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
9080 - Fix several infrequent memory leaks spotted by Coverity.
9081 - When testing for libevent functions, set the LDFLAGS variable
9082 correctly. Found by Riastradh.
9083 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
9084 bootstrapping with tunneled directory connections. Bugfix on
9085 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
9086 - When asked to connect to A.B.exit:80, if we don't know the IP for A
9087 and we know that server B rejects most-but-not all connections to
9088 port 80, we would previously reject the connection. Now, we assume
9089 the user knows what they were asking for. Fixes bug 752. Bugfix
9090 on 0.0.9rc5. Diagnosed by BarkerJr.
9091 - If we overrun our per-second write limits a little, count this as
9092 having used up our write allocation for the second, and choke
9093 outgoing directory writes. Previously, we had only counted this when
9094 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
9095 Bugfix on 0.2.0.x (??).
9096 - Remove the old v2 directory authority 'lefkada' from the default
9097 list. It has been gone for many months.
9098 - Stop doing unaligned memory access that generated bus errors on
9099 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
9100 - Make USR2 log-level switch take effect immediately. Bugfix on
9103 o Minor bugfixes (controller):
9104 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
9105 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
9108 Changes in version 0.2.1.7-alpha - 2008-11-08
9109 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
9110 packages (and maybe other packages) noticed by Theo de Raadt, fixes
9111 a smaller security flaw that might allow an attacker to access local
9112 services, adds better defense against DNS poisoning attacks on exit
9113 relays, further improves hidden service performance, and fixes a
9114 variety of other issues.
9117 - The "ClientDNSRejectInternalAddresses" config option wasn't being
9118 consistently obeyed: if an exit relay refuses a stream because its
9119 exit policy doesn't allow it, we would remember what IP address
9120 the relay said the destination address resolves to, even if it's
9121 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
9122 - The "User" and "Group" config options did not clear the
9123 supplementary group entries for the Tor process. The "User" option
9124 is now more robust, and we now set the groups to the specified
9125 user's primary group. The "Group" option is now ignored. For more
9126 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
9127 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
9128 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
9129 - Do not use or believe expired v3 authority certificates. Patch
9130 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
9133 - Now NodeFamily and MyFamily config options allow spaces in
9134 identity fingerprints, so it's easier to paste them in.
9135 Suggested by Lucky Green.
9136 - Implement the 0x20 hack to better resist DNS poisoning: set the
9137 case on outgoing DNS requests randomly, and reject responses that do
9138 not match the case correctly. This logic can be disabled with the
9139 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
9140 of servers that do not reliably preserve case in replies. See
9141 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
9143 - Preserve case in replies to DNSPort requests in order to support
9144 the 0x20 hack for resisting DNS poisoning attacks.
9146 o Hidden service performance improvements:
9147 - When the client launches an introduction circuit, retry with a
9148 new circuit after 30 seconds rather than 60 seconds.
9149 - Launch a second client-side introduction circuit in parallel
9150 after a delay of 15 seconds (based on work by Christian Wilms).
9151 - Hidden services start out building five intro circuits rather
9152 than three, and when the first three finish they publish a service
9153 descriptor using those. Now we publish our service descriptor much
9154 faster after restart.
9157 - Minor fix in the warning messages when you're having problems
9158 bootstrapping; also, be more forgiving of bootstrap problems when
9159 we're still making incremental progress on a given bootstrap phase.
9160 - When we're choosing an exit node for a circuit, and we have
9161 no pending streams, choose a good general exit rather than one that
9162 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
9163 - Send a valid END cell back when a client tries to connect to a
9164 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
9165 840. Patch from rovv.
9166 - If a broken client asks a non-exit router to connect somewhere,
9167 do not even do the DNS lookup before rejecting the connection.
9168 Fixes another case of bug 619. Patch from rovv.
9169 - Fix another case of assuming, when a specific exit is requested,
9170 that we know more than the user about what hosts it allows.
9171 Fixes another case of bug 752. Patch from rovv.
9172 - Check which hops rendezvous stream cells are associated with to
9173 prevent possible guess-the-streamid injection attacks from
9174 intermediate hops. Fixes another case of bug 446. Based on patch
9176 - Avoid using a negative right-shift when comparing 32-bit
9177 addresses. Possible fix for bug 845 and bug 811.
9178 - Make the assert_circuit_ok() function work correctly on circuits that
9179 have already been marked for close.
9180 - Fix read-off-the-end-of-string error in unit tests when decoding
9181 introduction points.
9182 - Fix uninitialized size field for memory area allocation: may improve
9183 memory performance during directory parsing.
9184 - Treat duplicate certificate fetches as failures, so that we do
9185 not try to re-fetch an expired certificate over and over and over.
9186 - Do not say we're fetching a certificate when we'll in fact skip it
9187 because of a pending download.
9190 Changes in version 0.2.1.6-alpha - 2008-09-30
9191 Tor 0.2.1.6-alpha further improves performance and robustness of
9192 hidden services, starts work on supporting per-country relay selection,
9193 and fixes a variety of smaller issues.
9196 - Implement proposal 121: make it possible to build hidden services
9197 that only certain clients are allowed to connect to. This is
9198 enforced at several points, so that unauthorized clients are unable
9199 to send INTRODUCE cells to the service, or even (depending on the
9200 type of authentication) to learn introduction points. This feature
9201 raises the bar for certain kinds of active attacks against hidden
9202 services. Code by Karsten Loesing.
9203 - Relays now store and serve v2 hidden service descriptors by default,
9204 i.e., the new default value for HidServDirectoryV2 is 1. This is
9205 the last step in proposal 114, which aims to make hidden service
9206 lookups more reliable.
9207 - Start work to allow node restrictions to include country codes. The
9208 syntax to exclude nodes in a country with country code XX is
9209 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
9210 refinement to decide what config options should take priority if
9211 you ask to both use a particular node and exclude it.
9212 - Allow ExitNodes list to include IP ranges and country codes, just
9213 like the Exclude*Nodes lists. Patch from Robert Hogan.
9216 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
9217 Tor to fail to start if you had it configured to use a bridge
9218 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
9219 - When extending a circuit to a hidden service directory to upload a
9220 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
9221 requests failed, because the router descriptor had not been
9222 downloaded yet. In these cases, we now wait until the router
9223 descriptor is downloaded, and then retry. Likewise, clients
9224 now skip over a hidden service directory if they don't yet have
9225 its router descriptor, rather than futilely requesting it and
9226 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
9228 - When fetching v0 and v2 rendezvous service descriptors in parallel,
9229 we were failing the whole hidden service request when the v0
9230 descriptor fetch fails, even if the v2 fetch is still pending and
9231 might succeed. Similarly, if the last v2 fetch fails, we were
9232 failing the whole hidden service request even if a v0 fetch is
9233 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
9234 - DNS replies need to have names matching their requests, but
9235 these names should be in the questions section, not necessarily
9236 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
9239 - Update to the "September 1 2008" ip-to-country file.
9240 - Allow ports 465 and 587 in the default exit policy again. We had
9241 rejected them in 0.1.0.15, because back in 2005 they were commonly
9242 misconfigured and ended up as spam targets. We hear they are better
9243 locked down these days.
9244 - Use a lockfile to make sure that two Tor processes are not
9245 simultaneously running with the same datadir.
9246 - Serve the latest v3 networkstatus consensus via the control
9247 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
9248 - Better logging about stability/reliability calculations on directory
9250 - Drop the requirement to have an open dir port for storing and
9251 serving v2 hidden service descriptors.
9252 - Directory authorities now serve a /tor/dbg-stability.txt URL to
9253 help debug WFU and MTBF calculations.
9254 - Implement most of Proposal 152: allow specialized servers to permit
9255 single-hop circuits, and clients to use those servers to build
9256 single-hop circuits when using a specialized controller. Patch
9257 from Josh Albrecht. Resolves feature request 768.
9258 - Add a -p option to tor-resolve for specifying the SOCKS port: some
9259 people find host:port too confusing.
9260 - Make TrackHostExit mappings expire a while after their last use, not
9261 after their creation. Patch from Robert Hogan.
9262 - Provide circuit purposes along with circuit events to the controller.
9265 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
9267 - Fixed some memory leaks -- some quite frequent, some almost
9268 impossible to trigger -- based on results from Coverity.
9269 - When testing for libevent functions, set the LDFLAGS variable
9270 correctly. Found by Riastradh.
9271 - Fix an assertion bug in parsing policy-related options; possible fix
9273 - Catch and report a few more bootstrapping failure cases when Tor
9274 fails to establish a TCP connection. Cleanup on 0.2.1.x.
9275 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
9276 bootstrapping with tunneled directory connections. Bugfix on
9277 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
9278 - When asked to connect to A.B.exit:80, if we don't know the IP for A
9279 and we know that server B rejects most-but-not all connections to
9280 port 80, we would previously reject the connection. Now, we assume
9281 the user knows what they were asking for. Fixes bug 752. Bugfix
9282 on 0.0.9rc5. Diagnosed by BarkerJr.
9283 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
9284 service directories if they have no advertised dir port. Bugfix
9286 - If we overrun our per-second write limits a little, count this as
9287 having used up our write allocation for the second, and choke
9288 outgoing directory writes. Previously, we had only counted this when
9289 we had met our limits precisely. Fixes bug 824. Patch by rovv.
9290 Bugfix on 0.2.0.x (??).
9291 - Avoid a "0 divided by 0" calculation when calculating router uptime
9292 at directory authorities. Bugfix on 0.2.0.8-alpha.
9293 - Make DNS resolved controller events into "CLOSED", not
9294 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
9296 - Fix a bug where an unreachable relay would establish enough
9297 reachability testing circuits to do a bandwidth test -- if
9298 we already have a connection to the middle hop of the testing
9299 circuit, then it could establish the last hop by using the existing
9300 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
9301 circuits no longer use entry guards in 0.2.1.3-alpha.
9302 - If we have correct permissions on $datadir, we complain to stdout
9303 and fail to start. But dangerous permissions on
9304 $datadir/cached-status/ would cause us to open a log and complain
9305 there. Now complain to stdout and fail to start in both cases. Fixes
9306 bug 820, reported by seeess.
9307 - Remove the old v2 directory authority 'lefkada' from the default
9308 list. It has been gone for many months.
9310 o Code simplifications and refactoring:
9311 - Revise the connection_new functions so that a more typesafe variant
9312 exists. This will work better with Coverity, and let us find any
9313 actual mistakes we're making here.
9314 - Refactor unit testing logic so that dmalloc can be used sensibly
9315 with unit tests to check for memory leaks.
9316 - Move all hidden-service related fields from connection and circuit
9317 structure to substructures: this way they won't eat so much memory.
9320 Changes in version 0.2.0.31 - 2008-09-03
9321 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
9322 a big bug we're seeing where in rare cases traffic from one Tor stream
9323 gets mixed into another stream, and fixes a variety of smaller issues.
9326 - Make sure that two circuits can never exist on the same connection
9327 with the same circuit ID, even if one is marked for close. This
9328 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
9329 - Relays now reject risky extend cells: if the extend cell includes
9330 a digest of all zeroes, or asks to extend back to the relay that
9331 sent the extend cell, tear down the circuit. Ideas suggested
9333 - If not enough of our entry guards are available so we add a new
9334 one, we might use the new one even if it overlapped with the
9335 current circuit's exit relay (or its family). Anonymity bugfix
9336 pointed out by rovv.
9339 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
9340 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
9341 - Correctly detect the presence of the linux/netfilter_ipv4.h header
9342 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
9343 - Pick size of default geoip filename string correctly on windows.
9344 Fixes bug 806. Bugfix on 0.2.0.30.
9345 - Make the autoconf script accept the obsolete --with-ssl-dir
9346 option as an alias for the actually-working --with-openssl-dir
9347 option. Fix the help documentation to recommend --with-openssl-dir.
9348 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
9349 - When using the TransPort option on OpenBSD, and using the User
9350 option to change UID and drop privileges, make sure to open
9351 /dev/pf before dropping privileges. Fixes bug 782. Patch from
9352 Christopher Davis. Bugfix on 0.1.2.1-alpha.
9353 - Try to attach connections immediately upon receiving a RENDEZVOUS2
9354 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
9355 on the client side when connecting to a hidden service. Bugfix
9356 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
9357 - When closing an application-side connection because its circuit is
9358 getting torn down, generate the stream event correctly. Bugfix on
9359 0.1.2.x. Anonymous patch.
9362 Changes in version 0.2.1.5-alpha - 2008-08-31
9363 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
9364 in a lot of the infrastructure for adding authorization to hidden
9365 services, lays the groundwork for having clients read their load
9366 balancing information out of the networkstatus consensus rather than
9367 the individual router descriptors, addresses two potential anonymity
9368 issues, and fixes a variety of smaller issues.
9371 - Convert many internal address representations to optionally hold
9373 - Generate and accept IPv6 addresses in many protocol elements.
9374 - Make resolver code handle nameservers located at ipv6 addresses.
9375 - Begin implementation of proposal 121 ("Client authorization for
9376 hidden services"): configure hidden services with client
9377 authorization, publish descriptors for them, and configure
9378 authorization data for hidden services at clients. The next
9379 step is to actually access hidden services that perform client
9381 - More progress toward proposal 141: Network status consensus
9382 documents and votes now contain bandwidth information for each
9383 router and a summary of that router's exit policy. Eventually this
9384 will be used by clients so that they do not have to download every
9385 known descriptor before building circuits.
9387 o Major bugfixes (on 0.2.0.x and before):
9388 - When sending CREATED cells back for a given circuit, use a 64-bit
9389 connection ID to find the right connection, rather than an addr:port
9390 combination. Now that we can have multiple OR connections between
9391 the same ORs, it is no longer possible to use addr:port to uniquely
9392 identify a connection.
9393 - Relays now reject risky extend cells: if the extend cell includes
9394 a digest of all zeroes, or asks to extend back to the relay that
9395 sent the extend cell, tear down the circuit. Ideas suggested
9397 - If not enough of our entry guards are available so we add a new
9398 one, we might use the new one even if it overlapped with the
9399 current circuit's exit relay (or its family). Anonymity bugfix
9400 pointed out by rovv.
9403 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
9404 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
9405 - When using the TransPort option on OpenBSD, and using the User
9406 option to change UID and drop privileges, make sure to open /dev/pf
9407 before dropping privileges. Fixes bug 782. Patch from Christopher
9408 Davis. Bugfix on 0.1.2.1-alpha.
9409 - Correctly detect the presence of the linux/netfilter_ipv4.h header
9410 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
9411 - Add a missing safe_str() call for a debug log message.
9412 - Use 64 bits instead of 32 bits for connection identifiers used with
9413 the controller protocol, to greatly reduce risk of identifier reuse.
9414 - Make the autoconf script accept the obsolete --with-ssl-dir
9415 option as an alias for the actually-working --with-openssl-dir
9416 option. Fix the help documentation to recommend --with-openssl-dir.
9417 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
9420 - Rate-limit too-many-sockets messages: when they happen, they happen
9421 a lot. Resolves bug 748.
9422 - Resist DNS poisoning a little better by making sure that names in
9423 answer sections match.
9424 - Print the SOCKS5 error message string as well as the error code
9425 when a tor-resolve request fails. Patch from Jacob.
9428 Changes in version 0.2.1.4-alpha - 2008-08-04
9429 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
9432 - The address part of exit policies was not correctly written
9433 to router descriptors. This generated router descriptors that failed
9434 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
9436 - Tor triggered a false assert when extending a circuit to a relay
9437 but we already have a connection open to that relay. Noticed by
9438 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
9441 - Fix a hidden service logging bug: in some edge cases, the router
9442 descriptor of a previously picked introduction point becomes
9443 obsolete and we need to give up on it rather than continually
9444 complaining that it has become obsolete. Observed by xiando. Bugfix
9448 - Take out the TestVia config option, since it was a workaround for
9449 a bug that was fixed in Tor 0.1.1.21.
9452 Changes in version 0.2.1.3-alpha - 2008-08-03
9453 Tor 0.2.1.3-alpha implements most of the pieces to prevent
9454 infinite-length circuit attacks (see proposal 110); fixes a bug that
9455 might cause exit relays to corrupt streams they send back; allows
9456 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
9457 ExcludeExitNodes config options; and fixes a big pile of bugs.
9459 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
9460 - Send a bootstrap problem "warn" event on the first problem if the
9461 reason is NO_ROUTE (that is, our network is down).
9464 - Implement most of proposal 110: The first K cells to be sent
9465 along a circuit are marked as special "early" cells; only K "early"
9466 cells will be allowed. Once this code is universal, we can block
9467 certain kinds of DOS attack by requiring that EXTEND commands must
9468 be sent using an "early" cell.
9471 - Try to attach connections immediately upon receiving a RENDEZVOUS2
9472 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
9473 on the client side when connecting to a hidden service. Bugfix
9474 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
9475 - Ensure that two circuits can never exist on the same connection
9476 with the same circuit ID, even if one is marked for close. This
9477 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
9480 - When relays do their initial bandwidth measurement, don't limit
9481 to just our entry guards for the test circuits. Otherwise we tend
9482 to have multiple test circuits going through a single entry guard,
9483 which makes our bandwidth test less accurate. Fixes part of bug 654;
9484 patch contributed by Josh Albrecht.
9485 - Add an ExcludeExitNodes option so users can list a set of nodes
9486 that should be be excluded from the exit node position, but
9487 allowed elsewhere. Implements proposal 151.
9488 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
9489 ExcludeNodes and ExcludeExitNodes lists.
9490 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
9491 be more efficient. Formerly it was quadratic in the number of
9492 servers; now it should be linear. Fixes bug 509.
9493 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
9494 and n_conn_id_digest fields into a separate structure that's
9495 only needed when the circuit has not yet attached to an n_conn.
9498 - Change the contrib/tor.logrotate script so it makes the new
9499 logs as "_tor:_tor" rather than the default, which is generally
9500 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
9501 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
9502 warnings (occasionally), but it can also cause the compiler to
9503 eliminate error-checking code. Suggested by Peter Gutmann.
9504 - When a hidden service is giving up on an introduction point candidate
9505 that was not included in the last published rendezvous descriptor,
9506 don't reschedule publication of the next descriptor. Fixes bug 763.
9508 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
9509 HiddenServiceExcludeNodes as obsolete: they never worked properly,
9510 and nobody claims to be using them. Fixes bug 754. Bugfix on
9511 0.1.0.1-rc. Patch from Christian Wilms.
9512 - Fix a small alignment and memory-wasting bug on buffer chunks.
9515 o Minor bugfixes (controller):
9516 - When closing an application-side connection because its circuit
9517 is getting torn down, generate the stream event correctly.
9518 Bugfix on 0.1.2.x. Anonymous patch.
9521 - Remove all backward-compatibility code to support relays running
9522 versions of Tor so old that they no longer work at all on the
9526 Changes in version 0.2.0.30 - 2008-07-15
9528 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
9529 warnings (occasionally), but it can also cause the compiler to
9530 eliminate error-checking code. Suggested by Peter Gutmann.
9533 Changes in version 0.2.0.29-rc - 2008-07-08
9534 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
9535 hidden-service performance bugs, and fixes a bunch of smaller bugs.
9538 - If you have more than one bridge but don't know their keys,
9539 you would only launch a request for the descriptor of the first one
9540 on your list. (Tor considered launching requests for the others, but
9541 found that it already had a connection on the way for $0000...0000
9542 so it didn't open another.) Bugfix on 0.2.0.x.
9543 - If you have more than one bridge but don't know their keys, and the
9544 connection to one of the bridges failed, you would cancel all
9545 pending bridge connections. (After all, they all have the same
9546 digest.) Bugfix on 0.2.0.x.
9547 - When a hidden service was trying to establish an introduction point,
9548 and Tor had built circuits preemptively for such purposes, we
9549 were ignoring all the preemptive circuits and launching a new one
9550 instead. Bugfix on 0.2.0.14-alpha.
9551 - When a hidden service was trying to establish an introduction point,
9552 and Tor *did* manage to reuse one of the preemptively built
9553 circuits, it didn't correctly remember which one it used,
9554 so it asked for another one soon after, until there were no
9555 more preemptive circuits, at which point it launched one from
9556 scratch. Bugfix on 0.0.9.x.
9557 - Make directory servers include the X-Your-Address-Is: http header in
9558 their responses even for begin_dir conns. Now clients who only
9559 ever use begin_dir connections still have a way to learn their IP
9560 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
9563 - Fix a macro/CPP interaction that was confusing some compilers:
9564 some GCCs don't like #if/#endif pairs inside macro arguments.
9566 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
9567 Fixes bug 704; fix from Steven Murdoch.
9568 - When opening /dev/null in finish_daemonize(), do not pass the
9569 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
9570 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
9571 - Correctly detect transparent proxy support on Linux hosts that
9572 require in.h to be included before netfilter_ipv4.h. Patch
9574 - Disallow session resumption attempts during the renegotiation
9575 stage of the v2 handshake protocol. Clients should never be trying
9576 session resumption at this point, but apparently some did, in
9577 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
9578 found by Geoff Goodell.
9581 Changes in version 0.2.1.2-alpha - 2008-06-20
9582 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
9583 make it easier to set up your own private Tor network; fixes several
9584 big bugs with using more than one bridge relay; fixes a big bug with
9585 offering hidden services quickly after Tor starts; and uses a better
9586 API for reporting potential bootstrapping problems to the controller.
9589 - New TestingTorNetwork config option to allow adjustment of
9590 previously constant values that, while reasonable, could slow
9591 bootstrapping. Implements proposal 135. Patch from Karsten.
9594 - If you have more than one bridge but don't know their digests,
9595 you would only learn a request for the descriptor of the first one
9596 on your list. (Tor considered launching requests for the others, but
9597 found that it already had a connection on the way for $0000...0000
9598 so it didn't open another.) Bugfix on 0.2.0.x.
9599 - If you have more than one bridge but don't know their digests,
9600 and the connection to one of the bridges failed, you would cancel
9601 all pending bridge connections. (After all, they all have the
9602 same digest.) Bugfix on 0.2.0.x.
9603 - When establishing a hidden service, introduction points that
9604 originate from cannibalized circuits are completely ignored and not
9605 included in rendezvous service descriptors. This might be another
9606 reason for delay in making a hidden service available. Bugfix
9607 from long ago (0.0.9.x?)
9610 - Allow OpenSSL to use dynamic locks if it wants.
9611 - When building a consensus, do not include routers that are down.
9612 This will cut down 30% to 40% on consensus size. Implements
9614 - In directory authorities' approved-routers files, allow
9615 fingerprints with or without space.
9616 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
9617 controller can query our current bootstrap state in case it attaches
9618 partway through and wants to catch up.
9619 - Send an initial "Starting" bootstrap status event, so we have a
9620 state to start out in.
9623 - Asking for a conditional consensus at .../consensus/<fingerprints>
9624 would crash a dirserver if it did not already have a
9625 consensus. Bugfix on 0.2.1.1-alpha.
9626 - Clean up some macro/CPP interactions: some GCC versions don't like
9627 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
9630 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
9631 - Directory authorities shouldn't complain about bootstrapping
9632 problems just because they do a lot of reachability testing and
9633 some of the connection attempts fail.
9634 - Start sending "count" and "recommendation" key/value pairs in
9635 bootstrap problem status events, so the controller can hear about
9636 problems even before Tor decides they're worth reporting for sure.
9637 - If you're using bridges, generate "bootstrap problem" warnings
9638 as soon as you run out of working bridges, rather than waiting
9639 for ten failures -- which will never happen if you have less than
9641 - If we close our OR connection because there's been a circuit
9642 pending on it for too long, we were telling our bootstrap status
9643 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
9646 Changes in version 0.2.1.1-alpha - 2008-06-13
9647 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
9648 were making the Tor process bloat especially on Linux; makes our TLS
9649 handshake blend in better; sends "bootstrap phase" status events to
9650 the controller, so it can keep the user informed of progress (and
9651 problems) fetching directory information and establishing circuits;
9652 and adds a variety of smaller features.
9655 - More work on making our TLS handshake blend in: modify the list
9656 of ciphers advertised by OpenSSL in client mode to even more
9657 closely resemble a common web browser. We cheat a little so that
9658 we can advertise ciphers that the locally installed OpenSSL doesn't
9660 - Start sending "bootstrap phase" status events to the controller,
9661 so it can keep the user informed of progress fetching directory
9662 information and establishing circuits. Also inform the controller
9663 if we think we're stuck at a particular bootstrap phase. Implements
9665 - Resume using OpenSSL's RAND_poll() for better (and more portable)
9666 cross-platform entropy collection again. We used to use it, then
9667 stopped using it because of a bug that could crash systems that
9668 called RAND_poll when they had a lot of fds open. It looks like the
9669 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
9670 at startup, and to call RAND_poll() when we reseed later only if
9671 we have a non-buggy OpenSSL version.
9674 - When we choose to abandon a new entry guard because we think our
9675 older ones might be better, close any circuits pending on that
9676 new entry guard connection. This fix should make us recover much
9677 faster when our network is down and then comes back. Bugfix on
9678 0.1.2.8-beta; found by lodger.
9680 o Memory fixes and improvements:
9681 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
9682 to avoid unused RAM in buffer chunks and memory pools.
9683 - Speed up parsing and cut down on memory fragmentation by using
9684 stack-style allocations for parsing directory objects. Previously,
9685 this accounted for over 40% of allocations from within Tor's code
9686 on a typical directory cache.
9687 - Use a Bloom filter rather than a digest-based set to track which
9688 descriptors we need to keep around when we're cleaning out old
9689 router descriptors. This speeds up the computation significantly,
9690 and may reduce fragmentation.
9691 - Reduce the default smartlist size from 32 to 16; it turns out that
9692 most smartlists hold around 8-12 elements tops.
9693 - Make dumpstats() log the fullness and size of openssl-internal
9695 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
9696 patch to their OpenSSL, turn it on to save memory on servers. This
9697 patch will (with any luck) get included in a mainline distribution
9699 - Never use OpenSSL compression: it wastes RAM and CPU trying to
9700 compress cells, which are basically all encrypted, compressed,
9704 - Stop reloading the router list from disk for no reason when we
9705 run out of reachable directory mirrors. Once upon a time reloading
9706 it would set the 'is_running' flag back to 1 for them. It hasn't
9707 done that for a long time.
9708 - In very rare situations new hidden service descriptors were
9709 published earlier than 30 seconds after the last change to the
9710 service. (We currently think that a hidden service descriptor
9711 that's been stable for 30 seconds is worth publishing.)
9714 - Allow separate log levels to be configured for different logging
9715 domains. For example, this allows one to log all notices, warnings,
9716 or errors, plus all memory management messages of level debug or
9717 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
9718 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
9719 and stop using a warning that had become unfixably verbose under
9721 - New --hush command-line option similar to --quiet. While --quiet
9722 disables all logging to the console on startup, --hush limits the
9723 output to messages of warning and error severity.
9724 - Servers support a new URL scheme for consensus downloads that
9725 allows the client to specify which authorities are trusted.
9726 The server then only sends the consensus if the client will trust
9727 it. Otherwise a 404 error is sent back. Clients use this
9728 new scheme when the server supports it (meaning it's running
9729 0.2.1.1-alpha or later). Implements proposal 134.
9730 - New configure/torrc options (--enable-geoip-stats,
9731 DirRecordUsageByCountry) to record how many IPs we've served
9732 directory info to in each country code, how many status documents
9733 total we've sent to each country code, and what share of the total
9734 directory requests we should expect to see.
9735 - Use the TLS1 hostname extension to more closely resemble browser
9737 - Lots of new unit tests.
9738 - Add a macro to implement the common pattern of iterating through
9739 two parallel lists in lockstep.
9742 Changes in version 0.2.0.28-rc - 2008-06-13
9743 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
9744 performance bug, and fixes a bunch of smaller bugs.
9747 - Fix a bug where, when we were choosing the 'end stream reason' to
9748 put in our relay end cell that we send to the exit relay, Tor
9749 clients on Windows were sometimes sending the wrong 'reason'. The
9750 anonymity problem is that exit relays may be able to guess whether
9751 the client is running Windows, thus helping partition the anonymity
9752 set. Down the road we should stop sending reasons to exit relays,
9753 or otherwise prevent future versions of this bug.
9756 - While setting up a hidden service, some valid introduction circuits
9757 were overlooked and abandoned. This might be the reason for
9758 the long delay in making a hidden service available. Bugfix on
9762 - Update to the "June 9 2008" ip-to-country file.
9763 - Run 'make test' as part of 'make dist', so we stop releasing so
9764 many development snapshots that fail their unit tests.
9767 - When we're checking if we have enough dir info for each relay
9768 to begin establishing circuits, make sure that we actually have
9769 the descriptor listed in the consensus, not just any descriptor.
9771 - Bridge relays no longer print "xx=0" in their extrainfo document
9772 for every single country code in the geoip db. Bugfix on
9774 - Only warn when we fail to load the geoip file if we were planning to
9775 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
9776 - If we change our MaxAdvertisedBandwidth and then reload torrc,
9777 Tor won't realize it should publish a new relay descriptor. Fixes
9778 bug 688, reported by mfr. Bugfix on 0.1.2.x.
9779 - When we haven't had any application requests lately, don't bother
9780 logging that we have expired a bunch of descriptors. Bugfix
9782 - Make relay cells written on a connection count as non-padding when
9783 tracking how long a connection has been in use. Bugfix on
9784 0.2.0.1-alpha. Spotted by lodger.
9785 - Fix unit tests in 0.2.0.27-rc.
9786 - Fix compile on Windows.
9789 Changes in version 0.2.0.27-rc - 2008-06-03
9790 Tor 0.2.0.27-rc adds a few features we left out of the earlier
9791 release candidates. In particular, we now include an IP-to-country
9792 GeoIP database, so controllers can easily look up what country a
9793 given relay is in, and so bridge relays can give us some sanitized
9794 summaries about which countries are making use of bridges. (See proposal
9795 126-geoip-fetching.txt for details.)
9798 - Include an IP-to-country GeoIP file in the tarball, so bridge
9799 relays can report sanitized summaries of the usage they're seeing.
9802 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
9803 Robert Hogan. Fixes the first part of bug 681.
9804 - Make bridge authorities never serve extrainfo docs.
9805 - Add support to detect Libevent versions in the 1.4.x series
9807 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
9808 - Include a new contrib/tor-exit-notice.html file that exit relay
9809 operators can put on their website to help reduce abuse queries.
9812 - When tunneling an encrypted directory connection, and its first
9813 circuit fails, do not leave it unattached and ask the controller
9814 to deal. Fixes the second part of bug 681.
9815 - Make bridge authorities correctly expire old extrainfo documents
9819 Changes in version 0.2.0.26-rc - 2008-05-13
9820 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
9821 in Debian's OpenSSL packages. All users running any 0.2.0.x version
9822 should upgrade, whether they're running Debian or not.
9824 o Major security fixes:
9825 - Use new V3 directory authority keys on the tor26, gabelmoo, and
9826 moria1 V3 directory authorities. The old keys were generated with
9827 a vulnerable version of Debian's OpenSSL package, and must be
9828 considered compromised. Other authorities' keys were not generated
9829 with an affected version of OpenSSL.
9832 - List authority signatures as "unrecognized" based on DirServer
9833 lines, not on cert cache. Bugfix on 0.2.0.x.
9836 - Add a new V3AuthUseLegacyKey option to make it easier for
9837 authorities to change their identity keys if they have to.
9840 Changes in version 0.2.0.25-rc - 2008-04-23
9841 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
9844 - Remember to initialize threading before initializing logging.
9845 Otherwise, many BSD-family implementations will crash hard on
9846 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
9849 - Authorities correctly free policies on bad servers on
9850 exit. Fixes bug 672. Bugfix on 0.2.0.x.
9853 Changes in version 0.2.0.24-rc - 2008-04-22
9854 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
9855 v3 directory authority, makes relays with dynamic IP addresses and no
9856 DirPort notice more quickly when their IP address changes, fixes a few
9857 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
9859 o New directory authorities:
9860 - Take lefkada out of the list of v3 directory authorities, since
9861 it has been down for months.
9862 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
9866 - Detect address changes more quickly on non-directory mirror
9867 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
9869 o Minor features (security):
9870 - Reject requests for reverse-dns lookup of names that are in
9871 a private address space. Patch from lodger.
9872 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
9875 o Minor bugfixes (crashes):
9876 - Avoid a rare assert that can trigger when Tor doesn't have much
9877 directory information yet and it tries to fetch a v2 hidden
9878 service descriptor. Fixes bug 651, reported by nwf.
9879 - Initialize log mutex before initializing dmalloc. Otherwise,
9880 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
9881 - Use recursive pthread mutexes in order to avoid deadlock when
9882 logging debug-level messages to a controller. Bug spotted by nwf,
9883 bugfix on 0.2.0.16-alpha.
9885 o Minor bugfixes (resource management):
9886 - Keep address policies from leaking memory: start their refcount
9887 at 1, not 2. Bugfix on 0.2.0.16-alpha.
9888 - Free authority certificates on exit, so they don't look like memory
9889 leaks. Bugfix on 0.2.0.19-alpha.
9890 - Free static hashtables for policy maps and for TLS connections on
9891 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
9892 - Avoid allocating extra space when computing consensuses on 64-bit
9893 platforms. Bug spotted by aakova.
9895 o Minor bugfixes (misc):
9896 - Do not read the configuration file when we've only been told to
9897 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
9898 based on patch from Sebastian Hahn.
9899 - Exit relays that are used as a client can now reach themselves
9900 using the .exit notation, rather than just launching an infinite
9901 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
9902 - When attempting to open a logfile fails, tell us why.
9903 - Fix a dumb bug that was preventing us from knowing that we should
9904 preemptively build circuits to handle expected directory requests.
9905 Fixes bug 660. Bugfix on 0.1.2.x.
9906 - Warn less verbosely about clock skew from netinfo cells from
9907 untrusted sources. Fixes bug 663.
9908 - Make controller stream events for DNS requests more consistent,
9909 by adding "new stream" events for DNS requests, and removing
9910 spurious "stream closed" events" for cached reverse resolves.
9911 Patch from mwenge. Fixes bug 646.
9912 - Correctly notify one-hop connections when a circuit build has
9913 failed. Possible fix for bug 669. Found by lodger.
9916 Changes in version 0.2.0.23-rc - 2008-03-24
9917 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
9918 makes bootstrapping faster if the first directory mirror you contact
9919 is down. The bundles also include the new Vidalia 0.1.2 release.
9922 - When a tunneled directory request is made to a directory server
9923 that's down, notice after 30 seconds rather than 120 seconds. Also,
9924 fail any begindir streams that are pending on it, so they can
9925 retry elsewhere. This was causing multi-minute delays on bootstrap.
9928 Changes in version 0.2.0.22-rc - 2008-03-18
9929 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
9930 enables encrypted directory connections by default for non-relays, fixes
9931 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
9932 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
9935 - Enable encrypted directory connections by default for non-relays,
9936 so censor tools that block Tor directory connections based on their
9937 plaintext patterns will no longer work. This means Tor works in
9938 certain censored countries by default again.
9941 - Make sure servers always request certificates from clients during
9942 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
9943 - Do not enter a CPU-eating loop when a connection is closed in
9944 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
9945 diagnosed by lodger; bugfix on 0.2.0.20-rc.
9946 - Fix assertion failure that could occur when a blocked circuit
9947 became unblocked, and it had pending client DNS requests. Bugfix
9948 on 0.2.0.1-alpha. Fixes bug 632.
9950 o Minor bugfixes (on 0.1.2.x):
9951 - Generate "STATUS_SERVER" events rather than misspelled
9952 "STATUS_SEVER" events. Caught by mwenge.
9953 - When counting the number of bytes written on a TLS connection,
9954 look at the BIO actually used for writing to the network, not
9955 at the BIO used (sometimes) to buffer data for the network.
9956 Looking at different BIOs could result in write counts on the
9957 order of ULONG_MAX. Fixes bug 614.
9958 - On Windows, correctly detect errors when listing the contents of
9959 a directory. Fix from lodger.
9961 o Minor bugfixes (on 0.2.0.x):
9962 - Downgrade "sslv3 alert handshake failure" message to INFO.
9963 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
9964 left BandwidthRate and BandwidthBurst at the default, we would be
9965 silently limited by those defaults. Now raise them to match the
9966 RelayBandwidth* values.
9967 - Fix the SVK version detection logic to work correctly on a branch.
9968 - Make --enable-openbsd-malloc work correctly on Linux with alpha
9969 CPUs. Fixes bug 625.
9970 - Logging functions now check that the passed severity is sane.
9971 - Use proper log levels in the testsuite call of
9972 get_interface_address6().
9973 - When using a nonstandard malloc, do not use the platform values for
9974 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
9975 - Make the openbsd malloc code use 8k pages on alpha CPUs and
9977 - Detect mismatched page sizes when using --enable-openbsd-malloc.
9978 - Avoid double-marked-for-close warning when certain kinds of invalid
9979 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
9980 for bug 617. Bugfix on 0.2.0.1-alpha.
9981 - Make sure that the "NULL-means-reject *:*" convention is followed by
9982 all the policy manipulation functions, avoiding some possible crash
9983 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
9984 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
9985 actually works, and doesn't warn about every single reverse lookup.
9986 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
9989 - Only log guard node status when guard node status has changed.
9990 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9991 make "INFO" 75% less verbose.
9994 Changes in version 0.2.0.21-rc - 2008-03-02
9995 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
9996 makes Tor work well with Vidalia again, fixes a rare assert bug,
9997 and fixes a pair of more minor bugs. The bundles also include Vidalia
9998 0.1.0 and Torbutton 1.1.16.
10001 - The control port should declare that it requires password auth
10002 when HashedControlSessionPassword is set too. Patch from Matt Edman;
10003 bugfix on 0.2.0.20-rc. Fixes bug 615.
10004 - Downgrade assert in connection_buckets_decrement() to a log message.
10005 This may help us solve bug 614, and in any case will make its
10006 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
10007 - We were sometimes miscounting the number of bytes read from the
10008 network, causing our rate limiting to not be followed exactly.
10009 Bugfix on 0.2.0.16-alpha. Reported by lodger.
10012 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
10013 OpenSSL versions should have been working fine. Diagnosis and patch
10014 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
10015 Bugfix on 0.2.0.20-rc.
10018 Changes in version 0.2.0.20-rc - 2008-02-24
10019 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
10020 makes more progress towards normalizing Tor's TLS handshake, makes
10021 hidden services work better again, helps relays bootstrap if they don't
10022 know their IP address, adds optional support for linking in openbsd's
10023 allocator or tcmalloc, allows really fast relays to scale past 15000
10024 sockets, and fixes a bunch of minor bugs reported by Veracode.
10027 - Enable the revised TLS handshake based on the one designed by
10028 Steven Murdoch in proposal 124, as revised in proposal 130. It
10029 includes version negotiation for OR connections as described in
10030 proposal 105. The new handshake is meant to be harder for censors
10031 to fingerprint, and it adds the ability to detect certain kinds of
10032 man-in-the-middle traffic analysis attacks. The version negotiation
10033 feature will allow us to improve Tor's link protocol more safely
10035 - Choose which bridge to use proportional to its advertised bandwidth,
10036 rather than uniformly at random. This should speed up Tor for
10037 bridge users. Also do this for people who set StrictEntryNodes.
10038 - When a TrackHostExits-chosen exit fails too many times in a row,
10039 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
10042 - Resolved problems with (re-)fetching hidden service descriptors.
10043 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
10044 and 0.2.0.19-alpha.
10045 - If we only ever used Tor for hidden service lookups or posts, we
10046 would stop building circuits and start refusing connections after
10047 24 hours, since we falsely believed that Tor was dormant. Reported
10048 by nwf; bugfix on 0.1.2.x.
10049 - Servers that don't know their own IP address should go to the
10050 authorities for their first directory fetch, even if their DirPort
10051 is off or if they don't know they're reachable yet. This will help
10052 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
10053 - When counting the number of open sockets, count not only the number
10054 of sockets we have received from the socket() call, but also
10055 the number we've gotten from accept() and socketpair(). This bug
10056 made us fail to count all sockets that we were using for incoming
10057 connections. Bugfix on 0.2.0.x.
10058 - Fix code used to find strings within buffers, when those strings
10059 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
10060 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
10061 - Add a new __HashedControlSessionPassword option for controllers
10062 to use for one-off session password hashes that shouldn't get
10063 saved to disk by SAVECONF --- Vidalia users were accumulating a
10064 pile of HashedControlPassword lines in their torrc files, one for
10065 each time they had restarted Tor and then clicked Save. Make Tor
10066 automatically convert "HashedControlPassword" to this new option but
10067 only when it's given on the command line. Partial fix for bug 586.
10069 o Minor features (performance):
10070 - Tune parameters for cell pool allocation to minimize amount of
10072 - Add OpenBSD malloc code from phk as an optional malloc
10073 replacement on Linux: some glibc libraries do very poorly
10074 with Tor's memory allocation patterns. Pass
10075 --enable-openbsd-malloc to get the replacement malloc code.
10076 - Add a --with-tcmalloc option to the configure script to link
10077 against tcmalloc (if present). Does not yet search for
10078 non-system include paths.
10079 - Stop imposing an arbitrary maximum on the number of file descriptors
10080 used for busy servers. Bug reported by Olaf Selke; patch from
10083 o Minor features (other):
10084 - When SafeLogging is disabled, log addresses along with all TLS
10086 - When building with --enable-gcc-warnings, check for whether Apple's
10087 warning "-Wshorten-64-to-32" is available.
10088 - Add a --passphrase-fd argument to the tor-gencert command for
10091 o Minor bugfixes (memory leaks and code problems):
10092 - We were leaking a file descriptor if Tor started with a zero-length
10093 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
10094 - Detect size overflow in zlib code. Reported by Justin Ferguson and
10096 - We were comparing the raw BridgePassword entry with a base64'ed
10097 version of it, when handling a "/tor/networkstatus-bridges"
10098 directory request. Now compare correctly. Noticed by Veracode.
10099 - Recover from bad tracked-since value in MTBF-history file.
10100 Should fix bug 537.
10101 - Alter the code that tries to recover from unhandled write
10102 errors, to not try to flush onto a socket that's given us
10103 unhandled errors. Bugfix on 0.1.2.x.
10104 - Make Unix controlsockets work correctly on OpenBSD. Patch from
10105 tup. Bugfix on 0.2.0.3-alpha.
10107 o Minor bugfixes (other):
10108 - If we have an extra-info document for our server, always make
10109 it available on the control port, even if we haven't gotten
10110 a copy of it from an authority yet. Patch from mwenge.
10111 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
10112 - Directory mirrors no longer include a guess at the client's IP
10113 address if the connection appears to be coming from the same /24
10114 network; it was producing too many wrong guesses.
10115 - Make the new hidden service code respect the SafeLogging setting.
10116 Bugfix on 0.2.0.x. Patch from Karsten.
10117 - When starting as an authority, do not overwrite all certificates
10118 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
10119 - If we're trying to flush the last bytes on a connection (for
10120 example, when answering a directory request), reset the
10121 time-to-give-up timeout every time we manage to write something
10122 on the socket. Bugfix on 0.1.2.x.
10123 - Change the behavior of "getinfo status/good-server-descriptor"
10124 so it doesn't return failure when any authority disappears.
10125 - Even though the man page said that "TrackHostExits ." should
10126 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
10127 - Report TLS "zero return" case as a "clean close" and "IO error"
10128 as a "close". Stop calling closes "unexpected closes": existing
10129 Tors don't use SSL_close(), so having a connection close without
10130 the TLS shutdown handshake is hardly unexpected.
10131 - Send NAMESERVER_STATUS messages for a single failed nameserver
10134 o Code simplifications and refactoring:
10135 - Remove the tor_strpartition function: its logic was confused,
10136 and it was only used for one thing that could be implemented far
10140 Changes in version 0.2.0.19-alpha - 2008-02-09
10141 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
10142 handshake, makes path selection for relays more secure and IP address
10143 guessing more robust, and generally fixes a lot of bugs in preparation
10144 for calling the 0.2.0 branch stable.
10147 - Do not include recognizeable strings in the commonname part of
10148 Tor's x509 certificates.
10151 - If we're a relay, avoid picking ourselves as an introduction point,
10152 a rendezvous point, or as the final hop for internal circuits. Bug
10153 reported by taranis and lodger. Bugfix on 0.1.2.x.
10154 - Patch from "Andrew S. Lists" to catch when we contact a directory
10155 mirror at IP address X and he says we look like we're coming from
10156 IP address X. Bugfix on 0.1.2.x.
10158 o Minor features (security):
10159 - Be more paranoid about overwriting sensitive memory on free(),
10160 as a defensive programming tactic to ensure forward secrecy.
10162 o Minor features (directory authority):
10163 - Actually validate the options passed to AuthDirReject,
10164 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
10165 - Reject router descriptors with out-of-range bandwidthcapacity or
10166 bandwidthburst values.
10168 o Minor features (controller):
10169 - Reject controller commands over 1MB in length. This keeps rogue
10170 processes from running us out of memory.
10172 o Minor features (misc):
10173 - Give more descriptive well-formedness errors for out-of-range
10174 hidden service descriptor/protocol versions.
10175 - Make memory debugging information describe more about history
10176 of cell allocation, so we can help reduce our memory use.
10178 o Deprecated features (controller):
10179 - The status/version/num-versioning and status/version/num-concurring
10180 GETINFO options are no longer useful in the v3 directory protocol:
10181 treat them as deprecated, and warn when they're used.
10184 - When our consensus networkstatus has been expired for a while, stop
10185 being willing to build circuits using it. Fixes bug 401. Bugfix
10187 - Directory caches now fetch certificates from all authorities
10188 listed in a networkstatus consensus, even when they do not
10189 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
10190 - When connecting to a bridge without specifying its key, insert
10191 the connection into the identity-to-connection map as soon as
10192 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
10193 - Detect versions of OS X where malloc_good_size() is present in the
10194 library but never actually declared. Resolves bug 587. Bugfix
10196 - Stop incorrectly truncating zlib responses to directory authority
10197 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
10198 - Stop recommending that every server operator send mail to tor-ops.
10199 Resolves bug 597. Bugfix on 0.1.2.x.
10200 - Don't trigger an assert if we start a directory authority with a
10201 private IP address (like 127.0.0.1).
10202 - Avoid possible failures when generating a directory with routers
10203 with over-long versions strings, or too many flags set. Bugfix
10205 - If an attempt to launch a DNS resolve request over the control
10206 port fails because we have overrun the limit on the number of
10207 connections, tell the controller that the request has failed.
10208 - Avoid using too little bandwidth when our clock skips a few
10209 seconds. Bugfix on 0.1.2.x.
10210 - Fix shell error when warning about missing packages in configure
10211 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
10212 - Do not become confused when receiving a spurious VERSIONS-like
10213 cell from a confused v1 client. Bugfix on 0.2.0.x.
10214 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
10215 introduction points for a hidden service have failed. Patch from
10216 Karsten Loesing. Bugfix on 0.2.0.x.
10218 o Code simplifications and refactoring:
10219 - Remove some needless generality from cpuworker code, for improved
10221 - Stop overloading the circuit_t.onionskin field for both "onionskin
10222 from a CREATE cell that we are waiting for a cpuworker to be
10223 assigned" and "onionskin from an EXTEND cell that we are going to
10224 send to an OR as soon as we are connected". Might help with bug 600.
10225 - Add an in-place version of aes_crypt() so that we can avoid doing a
10226 needless memcpy() call on each cell payload.
10229 Changes in version 0.2.0.18-alpha - 2008-01-25
10230 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
10231 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
10232 that can warn or reject connections to ports generally associated with
10233 vulnerable-plaintext protocols.
10235 o New directory authorities:
10236 - Set up dannenberg (run by CCC) as the sixth v3 directory
10240 - Fix a major memory leak when attempting to use the v2 TLS
10241 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
10242 - We accidentally enabled the under-development v2 TLS handshake
10243 code, which was causing log entries like "TLS error while
10244 renegotiating handshake". Disable it again. Resolves bug 590.
10245 - We were computing the wrong Content-Length: header for directory
10246 responses that need to be compressed on the fly, causing clients
10247 asking for those items to always fail. Bugfix on 0.2.0.x; partially
10251 - Avoid going directly to the directory authorities even if you're a
10252 relay, if you haven't found yourself reachable yet or if you've
10253 decided not to advertise your dirport yet. Addresses bug 556.
10254 - If we've gone 12 hours since our last bandwidth check, and we
10255 estimate we have less than 50KB bandwidth capacity but we could
10256 handle more, do another bandwidth test.
10257 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
10258 Tor can warn and/or refuse connections to ports commonly used with
10259 vulnerable-plaintext protocols. Currently we warn on ports 23,
10260 109, 110, and 143, but we don't reject any.
10263 - When we setconf ClientOnly to 1, close any current OR and Dir
10264 listeners. Reported by mwenge.
10265 - When we get a consensus that's been signed by more people than
10266 we expect, don't log about it; it's not a big deal. Reported
10270 - Don't answer "/tor/networkstatus-bridges" directory requests if
10271 the request isn't encrypted.
10272 - Make "ClientOnly 1" config option disable directory ports too.
10273 - Patches from Karsten Loesing to make v2 hidden services more
10274 robust: work even when there aren't enough HSDir relays available;
10275 retry when a v2 rend desc fetch fails; but don't retry if we
10276 already have a usable v0 rend desc.
10279 Changes in version 0.2.0.17-alpha - 2008-01-17
10280 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
10283 - Make the tor-gencert man page get included correctly in the tarball.
10286 Changes in version 0.2.0.16-alpha - 2008-01-17
10287 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
10288 Loesing, and generally cleans up a lot of features and minor bugs.
10290 o New directory authorities:
10291 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
10294 o Major performance improvements:
10295 - Switch our old ring buffer implementation for one more like that
10296 used by free Unix kernels. The wasted space in a buffer with 1mb
10297 of data will now be more like 8k than 1mb. The new implementation
10298 also avoids realloc();realloc(); patterns that can contribute to
10299 memory fragmentation.
10302 - Configuration files now accept C-style strings as values. This
10303 helps encode characters not allowed in the current configuration
10304 file format, such as newline or #. Addresses bug 557.
10305 - Although we fixed bug 539 (where servers would send HTTP status 503
10306 responses _and_ send a body too), there are still servers out
10307 there that haven't upgraded. Therefore, make clients parse such
10308 bodies when they receive them.
10309 - When we're not serving v2 directory information, there is no reason
10310 to actually keep any around. Remove the obsolete files and directory
10311 on startup if they are very old and we aren't going to serve them.
10313 o Minor performance improvements:
10314 - Reference-count and share copies of address policy entries; only 5%
10315 of them were actually distinct.
10316 - Never walk through the list of logs if we know that no log is
10317 interested in a given message.
10320 - When an authority has not signed a consensus, do not try to
10321 download a nonexistent "certificate with key 00000000". Bugfix
10322 on 0.2.0.x. Fixes bug 569.
10323 - Fix a rare assert error when we're closing one of our threads:
10324 use a mutex to protect the list of logs, so we never write to the
10325 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
10326 bug 575, which is kind of the revenge of bug 222.
10327 - Patch from Karsten Loesing to complain less at both the client
10328 and the relay when a relay used to have the HSDir flag but doesn't
10329 anymore, and we try to upload a hidden service descriptor.
10330 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
10332 - Do not try to download missing certificates until we have tried
10333 to check our fallback consensus. Fixes bug 583.
10334 - Make bridges round reported GeoIP stats info up to the nearest
10335 estimate, not down. Now we can distinguish between "0 people from
10336 this country" and "1 person from this country".
10337 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
10338 - Avoid possible segfault if key generation fails in
10339 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
10340 - Avoid segfault in the case where a badly behaved v2 versioning
10341 directory sends a signed networkstatus with missing client-versions.
10343 - Avoid segfaults on certain complex invocations of
10344 router_get_by_hexdigest(). Bugfix on 0.1.2.
10345 - Correct bad index on array access in parse_http_time(). Bugfix
10347 - Fix possible bug in vote generation when server versions are present
10348 but client versions are not.
10349 - Fix rare bug on REDIRECTSTREAM control command when called with no
10350 port set: it could erroneously report an error when none had
10352 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
10353 compressing large objects and find ourselves with more than 4k
10354 left over. Bugfix on 0.2.0.
10355 - Fix a small memory leak when setting up a hidden service.
10356 - Fix a few memory leaks that could in theory happen under bizarre
10358 - Fix an assert if we post a general-purpose descriptor via the
10359 control port but that descriptor isn't mentioned in our current
10360 network consensus. Bug reported by Jon McLachlan; bugfix on
10363 o Minor features (controller):
10364 - Get NS events working again. Patch from tup.
10365 - The GETCONF command now escapes and quotes configuration values
10366 that don't otherwise fit into the torrc file.
10367 - The SETCONF command now handles quoted values correctly.
10369 o Minor features (directory authorities):
10370 - New configuration options to override default maximum number of
10371 servers allowed on a single IP address. This is important for
10372 running a test network on a single host.
10373 - Actually implement the -s option to tor-gencert.
10374 - Add a manual page for tor-gencert.
10376 o Minor features (bridges):
10377 - Bridge authorities no longer serve bridge descriptors over
10378 unencrypted connections.
10380 o Minor features (other):
10381 - Add hidden services and DNSPorts to the list of things that make
10382 Tor accept that it has running ports. Change starting Tor with no
10383 ports from a fatal error to a warning; we might change it back if
10384 this turns out to confuse anybody. Fixes bug 579.
10387 Changes in version 0.1.2.19 - 2008-01-17
10388 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
10389 exit policy a little bit more conservative so it's safer to run an
10390 exit relay on a home system, and fixes a variety of smaller issues.
10393 - Exit policies now reject connections that are addressed to a
10394 relay's public (external) IP address too, unless
10395 ExitPolicyRejectPrivate is turned off. We do this because too
10396 many relays are running nearby to services that trust them based
10397 on network address.
10400 - When the clock jumps forward a lot, do not allow the bandwidth
10401 buckets to become negative. Fixes bug 544.
10402 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
10403 on every successful resolve. Reported by Mike Perry.
10404 - Purge old entries from the "rephist" database and the hidden
10405 service descriptor database even when DirPort is zero.
10406 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
10407 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
10408 crashing or mis-answering these requests.
10409 - When we decide to send a 503 response to a request for servers, do
10410 not then also send the server descriptors: this defeats the whole
10411 purpose. Fixes bug 539.
10414 - Changing the ExitPolicyRejectPrivate setting should cause us to
10415 rebuild our server descriptor.
10416 - Fix handling of hex nicknames when answering controller requests for
10417 networkstatus by name, or when deciding whether to warn about
10418 unknown routers in a config option. (Patch from mwenge.)
10419 - Fix a couple of hard-to-trigger autoconf problems that could result
10420 in really weird results on platforms whose sys/types.h files define
10421 nonstandard integer types.
10422 - Don't try to create the datadir when running --verify-config or
10423 --hash-password. Resolves bug 540.
10424 - If we were having problems getting a particular descriptor from the
10425 directory caches, and then we learned about a new descriptor for
10426 that router, we weren't resetting our failure count. Reported
10428 - Although we fixed bug 539 (where servers would send HTTP status 503
10429 responses _and_ send a body too), there are still servers out there
10430 that haven't upgraded. Therefore, make clients parse such bodies
10431 when they receive them.
10432 - Run correctly on systems where rlim_t is larger than unsigned long.
10433 This includes some 64-bit systems.
10434 - Run correctly on platforms (like some versions of OS X 10.5) where
10435 the real limit for number of open files is OPEN_FILES, not rlim_max
10436 from getrlimit(RLIMIT_NOFILES).
10437 - Avoid a spurious free on base64 failure.
10438 - Avoid segfaults on certain complex invocations of
10439 router_get_by_hexdigest().
10440 - Fix rare bug on REDIRECTSTREAM control command when called with no
10441 port set: it could erroneously report an error when none had
10445 Changes in version 0.2.0.15-alpha - 2007-12-25
10446 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
10447 features added in 0.2.0.13-alpha.
10450 - Fix several remotely triggerable asserts based on DirPort requests
10451 for a v2 or v3 networkstatus object before we were prepared. This
10452 was particularly bad for 0.2.0.13 and later bridge relays, who
10453 would never have a v2 networkstatus and would thus always crash
10454 when used. Bugfixes on 0.2.0.x.
10455 - Estimate the v3 networkstatus size more accurately, rather than
10456 estimating it at zero bytes and giving it artificially high priority
10457 compared to other directory requests. Bugfix on 0.2.0.x.
10460 - Fix configure.in logic for cross-compilation.
10461 - When we load a bridge descriptor from the cache, and it was
10462 previously unreachable, mark it as retriable so we won't just
10463 ignore it. Also, try fetching a new copy immediately. Bugfixes
10465 - The bridge GeoIP stats were counting other relays, for example
10466 self-reachability and authority-reachability tests.
10469 - Support compilation to target iPhone; patch from cjacker huang.
10470 To build for iPhone, pass the --enable-iphone option to configure.
10473 Changes in version 0.2.0.14-alpha - 2007-12-23
10475 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
10476 without a datadirectory from a previous Tor install. Reported
10478 - Fix a crash when we fetch a descriptor that turns out to be
10479 unexpected (it used to be in our networkstatus when we started
10480 fetching it, but it isn't in our current networkstatus), and we
10481 aren't using bridges. Bugfix on 0.2.0.x.
10482 - Fix a crash when accessing hidden services: it would work the first
10483 time you use a given introduction point for your service, but
10484 on subsequent requests we'd be using garbage memory. Fixed by
10485 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
10486 - Fix a crash when we load a bridge descriptor from disk but we don't
10487 currently have a Bridge line for it in our torrc. Bugfix on
10491 - If bridge authorities set BridgePassword, they will serve a
10492 snapshot of known bridge routerstatuses from their DirPort to
10493 anybody who knows that password. Unset by default.
10496 - Make the unit tests build again.
10497 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
10498 - Make PublishServerDescriptor default to 1, so the default doesn't
10499 have to change as we invent new directory protocol versions.
10500 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
10501 be included unless sys/time.h is already included. Fixes
10502 bug 553. Bugfix on 0.2.0.x.
10503 - If we receive a general-purpose descriptor and then receive an
10504 identical bridge-purpose descriptor soon after, don't discard
10505 the next one as a duplicate.
10508 - If BridgeRelay is set to 1, then the default for
10509 PublishServerDescriptor is now "bridge" rather than "v2,v3".
10510 - If the user sets RelayBandwidthRate but doesn't set
10511 RelayBandwidthBurst, then make them equal rather than erroring out.
10514 Changes in version 0.2.0.13-alpha - 2007-12-21
10515 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
10516 Goodell, fixes many more bugs, and adds a lot of infrastructure for
10519 o New directory authorities:
10520 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
10524 - Only update guard status (usable / not usable) once we have
10525 enough directory information. This was causing us to always pick
10526 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
10527 causing us to discard all our guards on startup if we hadn't been
10528 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
10529 - Purge old entries from the "rephist" database and the hidden
10530 service descriptor databases even when DirPort is zero. Bugfix
10532 - We were ignoring our RelayBandwidthRate for the first 30 seconds
10533 after opening a circuit -- even a relayed circuit. Bugfix on
10535 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
10536 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
10537 crashing or mis-answering these types of requests.
10538 - Relays were publishing their server descriptor to v1 and v2
10539 directory authorities, but they didn't try publishing to v3-only
10540 authorities. Fix this; and also stop publishing to v1 authorities.
10542 - When we were reading router descriptors from cache, we were ignoring
10543 the annotations -- so for example we were reading in bridge-purpose
10544 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
10545 - When we decided to send a 503 response to a request for servers, we
10546 were then also sending the server descriptors: this defeats the
10547 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
10550 - Bridge relays now behave like clients with respect to time
10551 intervals for downloading new consensus documents -- otherwise they
10552 stand out. Bridge users now wait until the end of the interval,
10553 so their bridge relay will be sure to have a new consensus document.
10554 - Three new config options (AlternateDirAuthority,
10555 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
10556 user selectively replace the default directory authorities by type,
10557 rather than the all-or-nothing replacement that DirServer offers.
10558 - Tor can now be configured to read a GeoIP file from disk in one
10559 of two formats. This can be used by controllers to map IP addresses
10560 to countries. Eventually, it may support exit-by-country.
10561 - When possible, bridge relays remember which countries users
10562 are coming from, and report aggregate information in their
10563 extra-info documents, so that the bridge authorities can learn
10564 where Tor is blocked.
10565 - Bridge directory authorities now do reachability testing on the
10566 bridges they know. They provide router status summaries to the
10567 controller via "getinfo ns/purpose/bridge", and also dump summaries
10568 to a file periodically.
10569 - Stop fetching directory info so aggressively if your DirPort is
10570 on but your ORPort is off; stop fetching v2 dir info entirely.
10571 You can override these choices with the new FetchDirInfoEarly
10575 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
10576 consensus documents when there are too many relays at a single
10577 IP address. Now clear it in v2 network status documents too, and
10578 also clear it in routerinfo_t when the relay is no longer listed
10579 in the relevant networkstatus document.
10580 - Don't crash if we get an unexpected value for the
10581 PublishServerDescriptor config option. Reported by Matt Edman;
10582 bugfix on 0.2.0.9-alpha.
10583 - Our new v2 hidden service descriptor format allows descriptors
10584 that have no introduction points. But Tor crashed when we tried
10585 to build a descriptor with no intro points (and it would have
10586 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
10587 by Karsten Loesing.
10588 - Fix building with dmalloc 5.5.2 with glibc.
10589 - Reject uploaded descriptors and extrainfo documents if they're
10590 huge. Otherwise we'll cache them all over the network and it'll
10591 clog everything up. Reported by Aljosha Judmayer.
10592 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
10593 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
10594 - When the DANGEROUS_VERSION controller status event told us we're
10595 running an obsolete version, it used the string "OLD" to describe
10596 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
10597 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
10598 - If we can't expand our list of entry guards (e.g. because we're
10599 using bridges or we have StrictEntryNodes set), don't mark relays
10600 down when they fail a directory request. Otherwise we're too quick
10601 to mark all our entry points down. Bugfix on 0.1.2.x.
10602 - Fix handling of hex nicknames when answering controller requests for
10603 networkstatus by name, or when deciding whether to warn about unknown
10604 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
10605 - Fix a couple of hard-to-trigger autoconf problems that could result
10606 in really weird results on platforms whose sys/types.h files define
10607 nonstandard integer types. Bugfix on 0.1.2.x.
10608 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
10609 - Don't crash on name lookup when we have no current consensus. Fixes
10610 bug 538; bugfix on 0.2.0.x.
10611 - Only Tors that want to mirror the v2 directory info should
10612 create the "cached-status" directory in their datadir. (All Tors
10613 used to create it.) Bugfix on 0.2.0.9-alpha.
10614 - Directory authorities should only automatically download Extra Info
10615 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
10618 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
10619 consumers. (We already do this on HUP.)
10620 - Authorities and caches fetch the v2 networkstatus documents
10621 less often, now that v3 is encouraged.
10622 - Add a new config option BridgeRelay that specifies you want to
10623 be a bridge relay. Right now the only difference is that it makes
10624 you answer begin_dir requests, and it makes you cache dir info,
10625 even if your DirPort isn't on.
10626 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
10627 ask about source, timestamp of arrival, purpose, etc. We need
10628 something like this to help Vidalia not do GeoIP lookups on bridge
10630 - Allow multiple HashedControlPassword config lines, to support
10631 multiple controller passwords.
10632 - Authorities now decide whether they're authoritative for a given
10633 router based on the router's purpose.
10634 - New config options AuthDirBadDir and AuthDirListBadDirs for
10635 authorities to mark certain relays as "bad directories" in the
10636 networkstatus documents. Also supports the "!baddir" directive in
10637 the approved-routers file.
10640 Changes in version 0.2.0.12-alpha - 2007-11-16
10641 This twelfth development snapshot fixes some more build problems as
10642 well as a few minor bugs.
10645 - Make it build on OpenBSD again. Patch from tup.
10646 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
10647 package-building for Red Hat, OS X, etc.
10649 o Minor bugfixes (on 0.1.2.x):
10650 - Changing the ExitPolicyRejectPrivate setting should cause us to
10651 rebuild our server descriptor.
10653 o Minor bugfixes (on 0.2.0.x):
10654 - When we're lacking a consensus, don't try to perform rendezvous
10655 operations. Reported by Karsten Loesing.
10656 - Fix a small memory leak whenever we decide against using a
10657 newly picked entry guard. Reported by Mike Perry.
10658 - When authorities detected more than two relays running on the same
10659 IP address, they were clearing all the status flags but forgetting
10660 to clear the "hsdir" flag. So clients were being told that a
10661 given relay was the right choice for a v2 hsdir lookup, yet they
10662 never had its descriptor because it was marked as 'not running'
10664 - If we're trying to fetch a bridge descriptor and there's no way
10665 the bridge authority could help us (for example, we don't know
10666 a digest, or there is no bridge authority), don't be so eager to
10667 fall back to asking the bridge authority.
10668 - If we're using bridges or have strictentrynodes set, and our
10669 chosen exit is in the same family as all our bridges/entry guards,
10670 then be flexible about families.
10673 - When we negotiate a v2 link-layer connection (not yet implemented),
10674 accept RELAY_EARLY cells and turn them into RELAY cells if we've
10675 negotiated a v1 connection for their next step. Initial code for
10679 Changes in version 0.2.0.11-alpha - 2007-11-12
10680 This eleventh development snapshot fixes some build problems with
10681 the previous snapshot. It also includes a more secure-by-default exit
10682 policy for relays, fixes an enormous memory leak for exit relays, and
10683 fixes another bug where servers were falling out of the directory list.
10686 - Exit policies now reject connections that are addressed to a
10687 relay's public (external) IP address too, unless
10688 ExitPolicyRejectPrivate is turned off. We do this because too
10689 many relays are running nearby to services that trust them based
10690 on network address. Bugfix on 0.1.2.x.
10693 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
10694 on every successful resolve. Reported by Mike Perry; bugfix
10696 - On authorities, never downgrade to old router descriptors simply
10697 because they're listed in the consensus. This created a catch-22
10698 where we wouldn't list a new descriptor because there was an
10699 old one in the consensus, and we couldn't get the new one in the
10700 consensus because we wouldn't list it. Possible fix for bug 548.
10701 Also, this might cause bug 543 to appear on authorities; if so,
10702 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
10704 o Packaging fixes on 0.2.0.10-alpha:
10705 - We were including instructions about what to do with the
10706 src/config/fallback-consensus file, but we weren't actually
10707 including it in the tarball. Disable all of that for now.
10710 - Allow people to say PreferTunnelledDirConns rather than
10711 PreferTunneledDirConns, for those alternate-spellers out there.
10714 - Don't reevaluate all the information from our consensus document
10715 just because we've downloaded a v2 networkstatus that we intend
10716 to cache. Fixes bug 545; bugfix on 0.2.0.x.
10719 Changes in version 0.2.0.10-alpha - 2007-11-10
10720 This tenth development snapshot adds a third v3 directory authority
10721 run by Mike Perry, adds most of Karsten Loesing's new hidden service
10722 descriptor format, fixes a bad crash bug and new bridge bugs introduced
10723 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
10724 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
10725 addresses many more minor issues.
10727 o New directory authorities:
10728 - Set up ides (run by Mike Perry) as the third v3 directory authority.
10731 - Allow tunnelled directory connections to ask for an encrypted
10732 "begin_dir" connection or an anonymized "uses a full Tor circuit"
10733 connection independently. Now we can make anonymized begin_dir
10734 connections for (e.g.) more secure hidden service posting and
10736 - More progress on proposal 114: code from Karsten Loesing to
10737 implement new hidden service descriptor format.
10738 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
10739 accommodate the growing number of servers that use the default
10740 and are reaching it.
10741 - Directory authorities use a new formula for selecting which nodes
10742 to advertise as Guards: they must be in the top 7/8 in terms of
10743 how long we have known about them, and above the median of those
10744 nodes in terms of weighted fractional uptime.
10745 - Make "not enough dir info yet" warnings describe *why* Tor feels
10746 it doesn't have enough directory info yet.
10749 - Stop servers from crashing if they set a Family option (or
10750 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
10752 - Make bridge users work again -- the move to v3 directories in
10753 0.2.0.9-alpha had introduced a number of bugs that made bridges
10754 no longer work for clients.
10755 - When the clock jumps forward a lot, do not allow the bandwidth
10756 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
10758 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
10759 - When the consensus lists a router descriptor that we previously were
10760 mirroring, but that we considered non-canonical, reload the
10761 descriptor as canonical. This fixes bug 543 where Tor servers
10762 would start complaining after a few days that they don't have
10763 enough directory information to build a circuit.
10764 - Consider replacing the current consensus when certificates arrive
10765 that make the pending consensus valid. Previously, we were only
10766 considering replacement when the new certs _didn't_ help.
10767 - Fix an assert error on startup if we didn't already have the
10768 consensus and certs cached in our datadirectory: we were caching
10769 the consensus in consensus_waiting_for_certs but then free'ing it
10771 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
10772 Request) if we need more v3 certs but we've already got pending
10773 requests for all of them.
10774 - Correctly back off from failing certificate downloads. Fixes
10776 - Authorities don't vote on the Running flag if they have been running
10777 for less than 30 minutes themselves. Fixes bug 547, where a newly
10778 started authority would vote that everyone was down.
10780 o New requirements:
10781 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
10782 it, it had no AES, and it hasn't seen any security patches since
10786 - Clients now hold circuitless TLS connections open for 1.5 times
10787 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
10788 rebuild a new circuit over them within that timeframe. Previously,
10789 they held them open only for KeepalivePeriod (5 minutes).
10790 - Use "If-Modified-Since" to avoid retrieving consensus
10791 networkstatuses that we already have.
10792 - When we have no consensus, check FallbackNetworkstatusFile (defaults
10793 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
10794 we start knowing some directory caches.
10795 - When we receive a consensus from the future, warn about skew.
10796 - Improve skew reporting: try to give the user a better log message
10797 about how skewed they are, and how much this matters.
10798 - When we have a certificate for an authority, believe that
10799 certificate's claims about the authority's IP address.
10800 - New --quiet command-line option to suppress the default console log.
10801 Good in combination with --hash-password.
10802 - Authorities send back an X-Descriptor-Not-New header in response to
10803 an accepted-but-discarded descriptor upload. Partially implements
10805 - Make the log message for "tls error. breaking." more useful.
10806 - Better log messages about certificate downloads, to attempt to
10807 track down the second incarnation of bug 546.
10809 o Minor features (bridges):
10810 - If bridge users set UpdateBridgesFromAuthority, but the digest
10811 they ask for is a 404 from the bridge authority, they now fall
10812 back to trying the bridge directly.
10813 - Bridges now use begin_dir to publish their server descriptor to
10814 the bridge authority, even when they haven't set TunnelDirConns.
10816 o Minor features (controller):
10817 - When reporting clock skew, and we know that the clock is _at least
10818 as skewed_ as some value, but we don't know the actual value,
10819 report the value as a "minimum skew."
10822 - Update linux-tor-prio.sh script to allow QoS based on the uid of
10823 the Tor process. Patch from Marco Bonetti with tweaks from Mike
10827 - Refuse to start if both ORPort and UseBridges are set. Bugfix
10828 on 0.2.0.x, suggested by Matt Edman.
10829 - Don't stop fetching descriptors when FetchUselessDescriptors is
10830 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
10831 reported by tup and ioerror.
10832 - Better log message on vote from unknown authority.
10833 - Don't log "Launching 0 request for 0 router" message.
10835 o Minor bugfixes (memory leaks):
10836 - Stop leaking memory every time we parse a v3 certificate. Bugfix
10838 - Stop leaking memory every time we load a v3 certificate. Bugfix
10839 on 0.2.0.1-alpha. Fixes bug 536.
10840 - Stop leaking a cached networkstatus on exit. Bugfix on
10842 - Stop leaking voter information every time we free a consensus.
10843 Bugfix on 0.2.0.3-alpha.
10844 - Stop leaking signed data every time we check a voter signature.
10845 Bugfix on 0.2.0.3-alpha.
10846 - Stop leaking a signature every time we fail to parse a consensus or
10847 a vote. Bugfix on 0.2.0.3-alpha.
10848 - Stop leaking v2_download_status_map on shutdown. Bugfix on
10850 - Stop leaking conn->nickname every time we make a connection to a
10851 Tor relay without knowing its expected identity digest (e.g. when
10852 using bridges). Bugfix on 0.2.0.3-alpha.
10854 - Minor bugfixes (portability):
10855 - Run correctly on platforms where rlim_t is larger than unsigned
10856 long, and/or where the real limit for number of open files is
10857 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
10858 particular, these may be needed for OS X 10.5.
10861 Changes in version 0.1.2.18 - 2007-10-28
10862 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
10863 hidden service introduction that were causing huge delays, and a big
10864 bug that was causing some servers to disappear from the network status
10865 lists for a few hours each day.
10867 o Major bugfixes (crashes):
10868 - If a connection is shut down abruptly because of something that
10869 happened inside connection_flushed_some(), do not call
10870 connection_finished_flushing(). Should fix bug 451:
10871 "connection_stop_writing: Assertion conn->write_event failed"
10872 Bugfix on 0.1.2.7-alpha.
10873 - Fix possible segfaults in functions called from
10874 rend_process_relay_cell().
10876 o Major bugfixes (hidden services):
10877 - Hidden services were choosing introduction points uniquely by
10878 hexdigest, but when constructing the hidden service descriptor
10879 they merely wrote the (potentially ambiguous) nickname.
10880 - Clients now use the v2 intro format for hidden service
10881 connections: they specify their chosen rendezvous point by identity
10882 digest rather than by (potentially ambiguous) nickname. These
10883 changes could speed up hidden service connections dramatically.
10885 o Major bugfixes (other):
10886 - Stop publishing a new server descriptor just because we get a
10887 HUP signal. This led (in a roundabout way) to some servers getting
10888 dropped from the networkstatus lists for a few hours each day.
10889 - When looking for a circuit to cannibalize, consider family as well
10890 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10891 circuit cannibalization).
10892 - When a router wasn't listed in a new networkstatus, we were leaving
10893 the flags for that router alone -- meaning it remained Named,
10894 Running, etc -- even though absence from the networkstatus means
10895 that it shouldn't be considered to exist at all anymore. Now we
10896 clear all the flags for routers that fall out of the networkstatus
10897 consensus. Fixes bug 529.
10900 - Don't try to access (or alter) the state file when running
10901 --list-fingerprint or --verify-config or --hash-password. Resolves
10903 - When generating information telling us how to extend to a given
10904 router, do not try to include the nickname if it is
10905 absent. Resolves bug 467.
10906 - Fix a user-triggerable segfault in expand_filename(). (There isn't
10907 a way to trigger this remotely.)
10908 - When sending a status event to the controller telling it that an
10909 OR address is reachable, set the port correctly. (Previously we
10910 were reporting the dir port.)
10911 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10912 command. Bugfix on 0.1.2.17.
10913 - When loading bandwidth history, do not believe any information in
10914 the future. Fixes bug 434.
10915 - When loading entry guard information, do not believe any information
10917 - When we have our clock set far in the future and generate an
10918 onion key, then re-set our clock to be correct, we should not stop
10919 the onion key from getting rotated.
10920 - On some platforms, accept() can return a broken address. Detect
10921 this more quietly, and deal accordingly. Fixes bug 483.
10922 - It's not actually an error to find a non-pending entry in the DNS
10923 cache when canceling a pending resolve. Don't log unless stuff
10924 is fishy. Resolves bug 463.
10925 - Don't reset trusted dir server list when we set a configuration
10926 option. Patch from Robert Hogan.
10927 - Don't try to create the datadir when running --verify-config or
10928 --hash-password. Resolves bug 540.
10931 Changes in version 0.2.0.9-alpha - 2007-10-24
10932 This ninth development snapshot switches clients to the new v3 directory
10933 system; allows servers to be listed in the network status even when they
10934 have the same nickname as a registered server; and fixes many other
10935 bugs including a big one that was causing some servers to disappear
10936 from the network status lists for a few hours each day.
10938 o Major features (directory system):
10939 - Clients now download v3 consensus networkstatus documents instead
10940 of v2 networkstatus documents. Clients and caches now base their
10941 opinions about routers on these consensus documents. Clients only
10942 download router descriptors listed in the consensus.
10943 - Authorities now list servers who have the same nickname as
10944 a different named server, but list them with a new flag,
10945 "Unnamed". Now we can list servers that happen to pick the same
10946 nickname as a server that registered two years ago and then
10947 disappeared. Partially implements proposal 122.
10948 - If the consensus lists a router as "Unnamed", the name is assigned
10949 to a different router: do not identify the router by that name.
10950 Partially implements proposal 122.
10951 - Authorities can now come to a consensus on which method to use to
10952 compute the consensus. This gives us forward compatibility.
10955 - Stop publishing a new server descriptor just because we HUP or
10956 when we find our DirPort to be reachable but won't actually publish
10957 it. New descriptors without any real changes are dropped by the
10958 authorities, and can screw up our "publish every 18 hours" schedule.
10960 - When a router wasn't listed in a new networkstatus, we were leaving
10961 the flags for that router alone -- meaning it remained Named,
10962 Running, etc -- even though absence from the networkstatus means
10963 that it shouldn't be considered to exist at all anymore. Now we
10964 clear all the flags for routers that fall out of the networkstatus
10965 consensus. Fixes bug 529; bugfix on 0.1.2.x.
10966 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
10967 extrainfo documents and then discard them immediately for not
10968 matching the latest router. Bugfix on 0.2.0.1-alpha.
10970 o Minor features (v3 directory protocol):
10971 - Allow tor-gencert to generate a new certificate without replacing
10973 - Allow certificates to include an address.
10974 - When we change our directory-cache settings, reschedule all voting
10975 and download operations.
10976 - Reattempt certificate downloads immediately on failure, as long as
10977 we haven't failed a threshold number of times yet.
10978 - Delay retrying consensus downloads while we're downloading
10979 certificates to verify the one we just got. Also, count getting a
10980 consensus that we already have (or one that isn't valid) as a failure,
10981 and count failing to get the certificates after 20 minutes as a
10983 - Build circuits and download descriptors even if our consensus is a
10984 little expired. (This feature will go away once authorities are
10987 o Minor features (router descriptor cache):
10988 - If we find a cached-routers file that's been sitting around for more
10989 than 28 days unmodified, then most likely it's a leftover from
10990 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10992 - When we (as a cache) download a descriptor because it was listed
10993 in a consensus, remember when the consensus was supposed to expire,
10994 and don't expire the descriptor until then.
10996 o Minor features (performance):
10997 - Call routerlist_remove_old_routers() much less often. This should
10998 speed startup, especially on directory caches.
10999 - Don't try to launch new descriptor downloads quite so often when we
11000 already have enough directory information to build circuits.
11001 - Base64 decoding was actually showing up on our profile when parsing
11002 the initial descriptor file; switch to an in-process all-at-once
11003 implementation that's about 3.5x times faster than calling out to
11006 o Minor features (compilation):
11007 - Detect non-ASCII platforms (if any still exist) and refuse to
11008 build there: some of our code assumes that 'A' is 65 and so on.
11010 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
11011 - Make the "next period" votes into "current period" votes immediately
11012 after publishing the consensus; avoid a heisenbug that made them
11013 stick around indefinitely.
11014 - When we discard a vote as a duplicate, do not report this as
11016 - Treat missing v3 keys or certificates as an error when running as a
11017 v3 directory authority.
11018 - When we're configured to be a v3 authority, but we're only listed
11019 as a non-v3 authority in our DirServer line for ourself, correct
11021 - If an authority doesn't have a qualified hostname, just put
11022 its address in the vote. This fixes the problem where we referred to
11023 "moria on moria:9031."
11024 - Distinguish between detached signatures for the wrong period, and
11025 detached signatures for a divergent vote.
11026 - Fix a small memory leak when computing a consensus.
11027 - When there's no concensus, we were forming a vote every 30
11028 minutes, but writing the "valid-after" line in our vote based
11029 on our configured V3AuthVotingInterval: so unless the intervals
11030 matched up, we immediately rejected our own vote because it didn't
11031 start at the voting interval that caused us to construct a vote.
11033 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
11034 - Delete unverified-consensus when the real consensus is set.
11035 - Consider retrying a consensus networkstatus fetch immediately
11036 after one fails: don't wait 60 seconds to notice.
11037 - When fetching a consensus as a cache, wait until a newer consensus
11038 should exist before trying to replace the current one.
11039 - Use a more forgiving schedule for retrying failed consensus
11040 downloads than for other types.
11042 o Minor bugfixes (other directory issues):
11043 - Correct the implementation of "download votes by digest." Bugfix on
11045 - Authorities no longer send back "400 you're unreachable please fix
11046 it" errors to Tor servers that aren't online all the time. We're
11047 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
11049 o Minor bugfixes (controller):
11050 - Don't reset trusted dir server list when we set a configuration
11051 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
11052 - Respond to INT and TERM SIGNAL commands before we execute the
11053 signal, in case the signal shuts us down. We had a patch in
11054 0.1.2.1-alpha that tried to do this by queueing the response on
11055 the connection's buffer before shutting down, but that really
11056 isn't the same thing at all. Bug located by Matt Edman.
11058 o Minor bugfixes (misc):
11059 - Correctly check for bad options to the "PublishServerDescriptor"
11060 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
11061 - Stop leaking memory on failing case of base32_decode, and make
11062 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
11063 - Don't try to download extrainfo documents when we're trying to
11064 fetch enough directory info to build a circuit: having enough
11065 info should get priority. Bugfix on 0.2.0.x.
11066 - Don't complain that "your server has not managed to confirm that its
11067 ports are reachable" if we haven't been able to build any circuits
11068 yet. Bug found by spending four hours without a v3 consensus. Bugfix
11070 - Detect the reason for failing to mmap a descriptor file we just
11071 wrote, and give a more useful log message. Fixes bug 533. Bugfix
11074 o Code simplifications and refactoring:
11075 - Remove support for the old bw_accounting file: we've been storing
11076 bandwidth accounting information in the state file since
11077 0.1.2.5-alpha. This may result in bandwidth accounting errors
11078 if you try to upgrade from 0.1.1.x or earlier, or if you try to
11079 downgrade to 0.1.1.x or earlier.
11080 - New convenience code to locate a file within the DataDirectory.
11081 - Move non-authority functionality out of dirvote.c.
11082 - Refactor the arguments for router_pick_{directory_|trusteddir}server
11083 so that they all take the same named flags.
11086 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
11087 Unix users an easy way to script their Tor process (e.g. by
11088 adjusting bandwidth based on the time of the day).
11091 Changes in version 0.2.0.8-alpha - 2007-10-12
11092 This eighth development snapshot fixes a crash bug that's been bothering
11093 us since February 2007, lets bridge authorities store a list of bridge
11094 descriptors they've seen, gets v3 directory voting closer to working,
11095 starts caching v3 directory consensus documents on directory mirrors,
11096 and fixes a variety of smaller issues including some minor memory leaks.
11098 o Major features (router descriptor cache):
11099 - Store routers in a file called cached-descriptors instead of in
11100 cached-routers. Initialize cached-descriptors from cached-routers
11101 if the old format is around. The new format allows us to store
11102 annotations along with descriptors.
11103 - Use annotations to record the time we received each descriptor, its
11104 source, and its purpose.
11105 - Disable the SETROUTERPURPOSE controller command: it is now
11107 - Controllers should now specify cache=no or cache=yes when using
11108 the +POSTDESCRIPTOR command.
11109 - Bridge authorities now write bridge descriptors to disk, meaning
11110 we can export them to other programs and begin distributing them
11113 o Major features (directory authorities):
11114 - When a v3 authority is missing votes or signatures, it now tries
11116 - Directory authorities track weighted fractional uptime as well as
11117 weighted mean-time-between failures. WFU is suitable for deciding
11118 whether a node is "usually up", while MTBF is suitable for deciding
11119 whether a node is "likely to stay up." We need both, because
11120 "usually up" is a good requirement for guards, while "likely to
11121 stay up" is a good requirement for long-lived connections.
11123 o Major features (v3 directory system):
11124 - Caches now download v3 network status documents as needed,
11125 and download the descriptors listed in them.
11126 - All hosts now attempt to download and keep fresh v3 authority
11127 certificates, and re-attempt after failures.
11128 - More internal-consistency checks for vote parsing.
11130 o Major bugfixes (crashes):
11131 - If a connection is shut down abruptly because of something that
11132 happened inside connection_flushed_some(), do not call
11133 connection_finished_flushing(). Should fix bug 451. Bugfix on
11136 o Major bugfixes (performance):
11137 - Fix really bad O(n^2) performance when parsing a long list of
11138 routers: Instead of searching the entire list for an "extra-info "
11139 string which usually wasn't there, once for every routerinfo
11140 we read, just scan lines forward until we find one we like.
11142 - When we add data to a write buffer in response to the data on that
11143 write buffer getting low because of a flush, do not consider the
11144 newly added data as a candidate for immediate flushing, but rather
11145 make it wait until the next round of writing. Otherwise, we flush
11146 and refill recursively, and a single greedy TLS connection can
11147 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
11149 o Minor features (v3 authority system):
11150 - Add more ways for tools to download the votes that lead to the
11152 - Send a 503 when low on bandwidth and a vote, consensus, or
11153 certificate is requested.
11154 - If-modified-since is now implemented properly for all kinds of
11155 certificate requests.
11157 o Minor bugfixes (network statuses):
11158 - Tweak the implementation of proposal 109 slightly: allow at most
11159 two Tor servers on the same IP address, except if it's the location
11160 of a directory authority, in which case allow five. Bugfix on
11163 o Minor bugfixes (controller):
11164 - When sending a status event to the controller telling it that an
11165 OR address is reachable, set the port correctly. (Previously we
11166 were reporting the dir port.) Bugfix on 0.1.2.x.
11168 o Minor bugfixes (v3 directory system):
11169 - Fix logic to look up a cert by its signing key digest. Bugfix on
11171 - Only change the reply to a vote to "OK" if it's not already
11172 set. This gets rid of annoying "400 OK" log messages, which may
11173 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
11174 - When we get a valid consensus, recompute the voting schedule.
11175 - Base the valid-after time of a vote on the consensus voting
11176 schedule, not on our preferred schedule.
11177 - Make the return values and messages from signature uploads and
11178 downloads more sensible.
11179 - Fix a memory leak when serving votes and consensus documents, and
11180 another when serving certificates.
11182 o Minor bugfixes (performance):
11183 - Use a slightly simpler string hashing algorithm (copying Python's
11184 instead of Java's) and optimize our digest hashing algorithm to take
11185 advantage of 64-bit platforms and to remove some possibly-costly
11187 - Fix a minor memory leak whenever we parse guards from our state
11188 file. Bugfix on 0.2.0.7-alpha.
11189 - Fix a minor memory leak whenever we write out a file. Bugfix on
11191 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11192 command. Bugfix on 0.2.0.5-alpha.
11194 o Minor bugfixes (portability):
11195 - On some platforms, accept() can return a broken address. Detect
11196 this more quietly, and deal accordingly. Fixes bug 483.
11197 - Stop calling tor_strlower() on uninitialized memory in some cases.
11198 Bugfix in 0.2.0.7-alpha.
11200 o Minor bugfixes (usability):
11201 - Treat some 403 responses from directory servers as INFO rather than
11202 WARN-severity events.
11203 - It's not actually an error to find a non-pending entry in the DNS
11204 cache when canceling a pending resolve. Don't log unless stuff is
11205 fishy. Resolves bug 463.
11207 o Minor bugfixes (anonymity):
11208 - Never report that we've used more bandwidth than we're willing to
11209 relay: it leaks how much non-relay traffic we're using. Resolves
11211 - When looking for a circuit to cannibalize, consider family as well
11212 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
11213 circuit cannibalization).
11215 o Code simplifications and refactoring:
11216 - Make a bunch of functions static. Remove some dead code.
11217 - Pull out about a third of the really big routerlist.c; put it in a
11218 new module, networkstatus.c.
11219 - Merge the extra fields in local_routerstatus_t back into
11220 routerstatus_t: we used to need one routerstatus_t for each
11221 authority's opinion, plus a local_routerstatus_t for the locally
11222 computed consensus opinion. To save space, we put the locally
11223 modified fields into local_routerstatus_t, and only the common
11224 stuff into routerstatus_t. But once v3 directories are in use,
11225 clients and caches will no longer need to hold authority opinions;
11226 thus, the rationale for keeping the types separate is now gone.
11227 - Make the code used to reschedule and reattempt downloads more
11229 - Turn all 'Are we a directory server/mirror?' logic into a call to
11231 - Remove the code to generate the oldest (v1) directory format.
11232 The code has been disabled since 0.2.0.5-alpha.
11235 Changes in version 0.2.0.7-alpha - 2007-09-21
11236 This seventh development snapshot makes bridges work again, makes bridge
11237 authorities work for the first time, fixes two huge performance flaws
11238 in hidden services, and fixes a variety of minor issues.
11240 o New directory authorities:
11241 - Set up moria1 and tor26 as the first v3 directory authorities. See
11242 doc/spec/dir-spec.txt for details on the new directory design.
11244 o Major bugfixes (crashes):
11245 - Fix possible segfaults in functions called from
11246 rend_process_relay_cell(). Bugfix on 0.1.2.x.
11248 o Major bugfixes (bridges):
11249 - Fix a bug that made servers send a "404 Not found" in response to
11250 attempts to fetch their server descriptor. This caused Tor servers
11251 to take many minutes to establish reachability for their DirPort,
11252 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
11253 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
11254 users configure that and specify a bridge with an identity
11255 fingerprint, now they will lookup the bridge descriptor at the
11256 default bridge authority via a one-hop tunnel, but once circuits
11257 are established they will switch to a three-hop tunnel for later
11258 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
11260 o Major bugfixes (hidden services):
11261 - Hidden services were choosing introduction points uniquely by
11262 hexdigest, but when constructing the hidden service descriptor
11263 they merely wrote the (potentially ambiguous) nickname.
11264 - Clients now use the v2 intro format for hidden service
11265 connections: they specify their chosen rendezvous point by identity
11266 digest rather than by (potentially ambiguous) nickname. Both
11267 are bugfixes on 0.1.2.x, and they could speed up hidden service
11268 connections dramatically. Thanks to Karsten Loesing.
11270 o Minor features (security):
11271 - As a client, do not believe any server that tells us that an
11272 address maps to an internal address space.
11273 - Make it possible to enable HashedControlPassword and
11274 CookieAuthentication at the same time.
11276 o Minor features (guard nodes):
11277 - Tag every guard node in our state file with the version that
11278 we believe added it, or with our own version if we add it. This way,
11279 if a user temporarily runs an old version of Tor and then switches
11280 back to a new one, she doesn't automatically lose her guards.
11282 o Minor features (speed):
11283 - When implementing AES counter mode, update only the portions of the
11284 counter buffer that need to change, and don't keep separate
11285 network-order and host-order counters when they are the same (i.e.,
11286 on big-endian hosts.)
11288 o Minor features (controller):
11289 - Accept LF instead of CRLF on controller, since some software has a
11290 hard time generating real Internet newlines.
11291 - Add GETINFO values for the server status events
11292 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
11295 o Removed features:
11296 - Routers no longer include bandwidth-history lines in their
11297 descriptors; this information is already available in extra-info
11298 documents, and including it in router descriptors took up 60%
11299 (!) of compressed router descriptor downloads. Completes
11300 implementation of proposal 104.
11301 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
11302 and TorControl.py, as they use the old v0 controller protocol,
11303 and are obsoleted by TorFlow anyway.
11304 - Drop support for v1 rendezvous descriptors, since we never used
11305 them anyway, and the code has probably rotted by now. Based on
11306 patch from Karsten Loesing.
11307 - On OSX, stop warning the user that kqueue support in libevent is
11308 "experimental", since it seems to have worked fine for ages.
11311 - When generating information telling us how to extend to a given
11312 router, do not try to include the nickname if it is absent. Fixes
11313 bug 467. Bugfix on 0.2.0.3-alpha.
11314 - Fix a user-triggerable (but not remotely-triggerable) segfault
11315 in expand_filename(). Bugfix on 0.1.2.x.
11316 - Fix a memory leak when freeing incomplete requests from DNSPort.
11317 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
11318 - Don't try to access (or alter) the state file when running
11319 --list-fingerprint or --verify-config or --hash-password. (Resolves
11320 bug 499.) Bugfix on 0.1.2.x.
11321 - Servers used to decline to publish their DirPort if their
11322 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
11323 were below a threshold. Now they only look at BandwidthRate and
11324 RelayBandwidthRate. Bugfix on 0.1.2.x.
11325 - Remove an optimization in the AES counter-mode code that assumed
11326 that the counter never exceeded 2^68. When the counter can be set
11327 arbitrarily as an IV (as it is by Karsten's new hidden services
11328 code), this assumption no longer holds. Bugfix on 0.1.2.x.
11329 - Resume listing "AUTHORITY" flag for authorities in network status.
11330 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
11332 o Code simplifications and refactoring:
11333 - Revamp file-writing logic so we don't need to have the entire
11334 contents of a file in memory at once before we write to disk. Tor,
11336 - Turn "descriptor store" into a full-fledged type.
11337 - Move all NT services code into a separate source file.
11338 - Unify all code that computes medians, percentile elements, etc.
11339 - Get rid of a needless malloc when parsing address policies.
11342 Changes in version 0.1.2.17 - 2007-08-30
11343 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
11344 X bundles. Vidalia 0.0.14 makes authentication required for the
11345 ControlPort in the default configuration, which addresses important
11346 security risks. Everybody who uses Vidalia (or another controller)
11349 In addition, this Tor update fixes major load balancing problems with
11350 path selection, which should speed things up a lot once many people
11353 o Major bugfixes (security):
11354 - We removed support for the old (v0) control protocol. It has been
11355 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
11356 become more of a headache than it's worth.
11358 o Major bugfixes (load balancing):
11359 - When choosing nodes for non-guard positions, weight guards
11360 proportionally less, since they already have enough load. Patch
11362 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
11363 will allow fast Tor servers to get more attention.
11364 - When we're upgrading from an old Tor version, forget our current
11365 guards and pick new ones according to the new weightings. These
11366 three load balancing patches could raise effective network capacity
11367 by a factor of four. Thanks to Mike Perry for measurements.
11369 o Major bugfixes (stream expiration):
11370 - Expire not-yet-successful application streams in all cases if
11371 they've been around longer than SocksTimeout. Right now there are
11372 some cases where the stream will live forever, demanding a new
11373 circuit every 15 seconds. Fixes bug 454; reported by lodger.
11375 o Minor features (controller):
11376 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
11377 is valid before any authentication has been received. It tells
11378 a controller what kind of authentication is expected, and what
11379 protocol is spoken. Implements proposal 119.
11381 o Minor bugfixes (performance):
11382 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
11383 greatly speeding up loading cached-routers from disk on startup.
11384 - Disable sentinel-based debugging for buffer code: we squashed all
11385 the bugs that this was supposed to detect a long time ago, and now
11386 its only effect is to change our buffer sizes from nice powers of
11387 two (which platform mallocs tend to like) to values slightly over
11388 powers of two (which make some platform mallocs sad).
11390 o Minor bugfixes (misc):
11391 - If exit bandwidth ever exceeds one third of total bandwidth, then
11392 use the correct formula to weight exit nodes when choosing paths.
11393 Based on patch from Mike Perry.
11394 - Choose perfectly fairly among routers when choosing by bandwidth and
11395 weighting by fraction of bandwidth provided by exits. Previously, we
11396 would choose with only approximate fairness, and correct ourselves
11397 if we ran off the end of the list.
11398 - If we require CookieAuthentication but we fail to write the
11399 cookie file, we would warn but not exit, and end up in a state
11400 where no controller could authenticate. Now we exit.
11401 - If we require CookieAuthentication, stop generating a new cookie
11402 every time we change any piece of our config.
11403 - Refuse to start with certain directory authority keys, and
11404 encourage people using them to stop.
11405 - Terminate multi-line control events properly. Original patch
11407 - Fix a minor memory leak when we fail to find enough suitable
11408 servers to choose a circuit.
11409 - Stop leaking part of the descriptor when we run into a particularly
11410 unparseable piece of it.
11413 Changes in version 0.2.0.6-alpha - 2007-08-26
11414 This sixth development snapshot features a new Vidalia version in the
11415 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
11416 the ControlPort in the default configuration, which addresses important
11419 In addition, this snapshot fixes major load balancing problems
11420 with path selection, which should speed things up a lot once many
11421 people have upgraded. The directory authorities also use a new
11422 mean-time-between-failure approach to tracking which servers are stable,
11423 rather than just looking at the most recent uptime.
11425 o New directory authorities:
11426 - Set up Tonga as the default bridge directory authority.
11429 - Directory authorities now track servers by weighted
11430 mean-times-between-failures. When we have 4 or more days of data,
11431 use measured MTBF rather than declared uptime to decide whether
11432 to call a router Stable. Implements proposal 108.
11434 o Major bugfixes (load balancing):
11435 - When choosing nodes for non-guard positions, weight guards
11436 proportionally less, since they already have enough load. Patch
11438 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
11439 will allow fast Tor servers to get more attention.
11440 - When we're upgrading from an old Tor version, forget our current
11441 guards and pick new ones according to the new weightings. These
11442 three load balancing patches could raise effective network capacity
11443 by a factor of four. Thanks to Mike Perry for measurements.
11445 o Major bugfixes (descriptor parsing):
11446 - Handle unexpected whitespace better in malformed descriptors. Bug
11447 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
11450 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
11451 GETINFO for Torstat to use until it can switch to using extrainfos.
11452 - Optionally (if built with -DEXPORTMALLINFO) export the output
11453 of mallinfo via http, as tor/mallinfo.txt. Only accessible
11457 - Do not intermix bridge routers with controller-added
11458 routers. (Bugfix on 0.2.0.x)
11459 - Do not fail with an assert when accept() returns an unexpected
11460 address family. Addresses but does not wholly fix bug 483. (Bugfix
11462 - Let directory authorities startup even when they can't generate
11463 a descriptor immediately, e.g. because they don't know their
11465 - Stop putting the authentication cookie in a file called "0"
11466 in your working directory if you don't specify anything for the
11467 new CookieAuthFile option. Reported by Matt Edman.
11468 - Make it possible to read the PROTOCOLINFO response in a way that
11469 conforms to our control-spec. Reported by Matt Edman.
11470 - Fix a minor memory leak when we fail to find enough suitable
11471 servers to choose a circuit. Bugfix on 0.1.2.x.
11472 - Stop leaking part of the descriptor when we run into a particularly
11473 unparseable piece of it. Bugfix on 0.1.2.x.
11474 - Unmap the extrainfo cache file on exit.
11477 Changes in version 0.2.0.5-alpha - 2007-08-19
11478 This fifth development snapshot fixes compilation on Windows again;
11479 fixes an obnoxious client-side bug that slowed things down and put
11480 extra load on the network; gets us closer to using the v3 directory
11481 voting scheme; makes it easier for Tor controllers to use cookie-based
11482 authentication; and fixes a variety of other bugs.
11484 o Removed features:
11485 - Version 1 directories are no longer generated in full. Instead,
11486 authorities generate and serve "stub" v1 directories that list
11487 no servers. This will stop Tor versions 0.1.0.x and earlier from
11488 working, but (for security reasons) nobody should be running those
11491 o Major bugfixes (compilation, 0.2.0.x):
11492 - Try to fix Win32 compilation again: improve checking for IPv6 types.
11493 - Try to fix MSVC compilation: build correctly on platforms that do
11494 not define s6_addr16 or s6_addr32.
11495 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
11498 o Major bugfixes (stream expiration):
11499 - Expire not-yet-successful application streams in all cases if
11500 they've been around longer than SocksTimeout. Right now there are
11501 some cases where the stream will live forever, demanding a new
11502 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
11503 reported by lodger.
11505 o Minor features (directory servers):
11506 - When somebody requests a list of statuses or servers, and we have
11507 none of those, return a 404 rather than an empty 200.
11509 o Minor features (directory voting):
11510 - Store v3 consensus status consensuses on disk, and reload them
11513 o Minor features (security):
11514 - Warn about unsafe ControlPort configurations.
11515 - Refuse to start with certain directory authority keys, and
11516 encourage people using them to stop.
11518 o Minor features (controller):
11519 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
11520 is valid before any authentication has been received. It tells
11521 a controller what kind of authentication is expected, and what
11522 protocol is spoken. Implements proposal 119.
11523 - New config option CookieAuthFile to choose a new location for the
11524 cookie authentication file, and config option
11525 CookieAuthFileGroupReadable to make it group-readable.
11527 o Minor features (unit testing):
11528 - Add command-line arguments to unit-test executable so that we can
11529 invoke any chosen test from the command line rather than having
11530 to run the whole test suite at once; and so that we can turn on
11531 logging for the unit tests.
11533 o Minor bugfixes (on 0.1.2.x):
11534 - If we require CookieAuthentication but we fail to write the
11535 cookie file, we would warn but not exit, and end up in a state
11536 where no controller could authenticate. Now we exit.
11537 - If we require CookieAuthentication, stop generating a new cookie
11538 every time we change any piece of our config.
11539 - When loading bandwidth history, do not believe any information in
11540 the future. Fixes bug 434.
11541 - When loading entry guard information, do not believe any information
11543 - When we have our clock set far in the future and generate an
11544 onion key, then re-set our clock to be correct, we should not stop
11545 the onion key from getting rotated.
11546 - Clean up torrc sample config file.
11547 - Do not automatically run configure from autogen.sh. This
11548 non-standard behavior tended to annoy people who have built other
11551 o Minor bugfixes (on 0.2.0.x):
11552 - Fix a bug with AutomapHostsOnResolve that would always cause
11553 the second request to fail. Bug reported by Kate. Bugfix on
11555 - Fix a bug in ADDRMAP controller replies that would sometimes
11556 try to print a NULL. Patch from tup.
11557 - Read v3 directory authority keys from the right location.
11558 - Numerous bugfixes to directory voting code.
11561 Changes in version 0.1.2.16 - 2007-08-01
11562 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
11563 remote attacker in certain situations to rewrite the user's torrc
11564 configuration file. This can completely compromise anonymity of users
11565 in most configurations, including those running the Vidalia bundles,
11566 TorK, etc. Or worse.
11568 o Major security fixes:
11569 - Close immediately after missing authentication on control port;
11570 do not allow multiple authentication attempts.
11573 Changes in version 0.2.0.4-alpha - 2007-08-01
11574 This fourth development snapshot fixes a critical security vulnerability
11575 for most users, specifically those running Vidalia, TorK, etc. Everybody
11576 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
11578 o Major security fixes:
11579 - Close immediately after missing authentication on control port;
11580 do not allow multiple authentication attempts.
11582 o Major bugfixes (compilation):
11583 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
11586 o Minor features (performance):
11587 - Be even more aggressive about releasing RAM from small
11588 empty buffers. Thanks to our free-list code, this shouldn't be too
11589 performance-intensive.
11590 - Disable sentinel-based debugging for buffer code: we squashed all
11591 the bugs that this was supposed to detect a long time ago, and
11592 now its only effect is to change our buffer sizes from nice
11593 powers of two (which platform mallocs tend to like) to values
11594 slightly over powers of two (which make some platform mallocs sad).
11595 - Log malloc statistics from mallinfo() on platforms where it
11599 Changes in version 0.2.0.3-alpha - 2007-07-29
11600 This third development snapshot introduces new experimental
11601 blocking-resistance features and a preliminary version of the v3
11602 directory voting design, and includes many other smaller features
11606 - The first pieces of our "bridge" design for blocking-resistance
11607 are implemented. People can run bridge directory authorities;
11608 people can run bridges; and people can configure their Tor clients
11609 with a set of bridges to use as the first hop into the Tor network.
11610 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
11612 - Create listener connections before we setuid to the configured
11613 User and Group. Now non-Windows users can choose port values
11614 under 1024, start Tor as root, and have Tor bind those ports
11615 before it changes to another UID. (Windows users could already
11617 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
11618 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
11619 on "vserver" accounts. (Patch from coderman.)
11620 - Be even more aggressive about separating local traffic from relayed
11621 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
11623 o Major features (experimental):
11624 - First cut of code for "v3 dir voting": directory authorities will
11625 vote on a common network status document rather than each publishing
11626 their own opinion. This code needs more testing and more corner-case
11627 handling before it's ready for use.
11630 - Directory authorities now call routers Fast if their bandwidth is
11631 at least 100KB/s, and consider their bandwidth adequate to be a
11632 Guard if it is at least 250KB/s, no matter the medians. This fix
11633 complements proposal 107. [Bugfix on 0.1.2.x]
11634 - Directory authorities now never mark more than 3 servers per IP as
11635 Valid and Running. (Implements proposal 109, by Kevin Bauer and
11637 - Minor change to organizationName and commonName generation
11638 procedures in TLS certificates during Tor handshakes, to invalidate
11639 some earlier censorware approaches. This is not a long-term
11640 solution, but applying it will give us a bit of time to look into
11641 the epidemiology of countermeasures as they spread.
11643 o Major bugfixes (directory):
11644 - Rewrite directory tokenization code to never run off the end of
11645 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
11647 o Minor features (controller):
11648 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
11649 match requests to applications. (Patch from Robert Hogan.)
11650 - Report address and port correctly on connections to DNSPort. (Patch
11651 from Robert Hogan.)
11652 - Add a RESOLVE command to launch hostname lookups. (Original patch
11653 from Robert Hogan.)
11654 - Add GETINFO status/enough-dir-info to let controllers tell whether
11655 Tor has downloaded sufficient directory information. (Patch
11657 - You can now use the ControlSocket option to tell Tor to listen for
11658 controller connections on Unix domain sockets on systems that
11659 support them. (Patch from Peter Palfrader.)
11660 - STREAM NEW events are generated for DNSPort requests and for
11661 tunneled directory connections. (Patch from Robert Hogan.)
11662 - New "GETINFO address-mappings/*" command to get address mappings
11663 with expiry information. "addr-mappings/*" is now deprecated.
11666 o Minor features (misc):
11667 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
11669 - The tor-gencert tool for v3 directory authorities now creates all
11670 files as readable to the file creator only, and write-protects
11671 the authority identity key.
11672 - When dumping memory usage, list bytes used in buffer memory
11674 - When running with dmalloc, dump more stats on hup and on exit.
11675 - Directory authorities now fail quickly and (relatively) harmlessly
11676 if they generate a network status document that is somehow
11679 o Traffic load balancing improvements:
11680 - If exit bandwidth ever exceeds one third of total bandwidth, then
11681 use the correct formula to weight exit nodes when choosing paths.
11682 (Based on patch from Mike Perry.)
11683 - Choose perfectly fairly among routers when choosing by bandwidth and
11684 weighting by fraction of bandwidth provided by exits. Previously, we
11685 would choose with only approximate fairness, and correct ourselves
11686 if we ran off the end of the list. [Bugfix on 0.1.2.x]
11688 o Performance improvements:
11689 - Be more aggressive with freeing buffer RAM or putting it on the
11691 - Use Critical Sections rather than Mutexes for synchronizing threads
11692 on win32; Mutexes are heavier-weight, and designed for synchronizing
11695 o Deprecated and removed features:
11696 - RedirectExits is now deprecated.
11697 - Stop allowing address masks that do not correspond to bit prefixes.
11698 We have warned about these for a really long time; now it's time
11699 to reject them. (Patch from croup.)
11701 o Minor bugfixes (directory):
11702 - Fix another crash bug related to extra-info caching. (Bug found by
11703 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
11704 - Directories no longer return a "304 not modified" when they don't
11705 have the networkstatus the client asked for. Also fix a memory
11706 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
11707 - We had accidentally labelled 0.1.2.x directory servers as not
11708 suitable for begin_dir requests, and had labelled no directory
11709 servers as suitable for uploading extra-info documents. [Bugfix
11712 o Minor bugfixes (dns):
11713 - Fix a crash when DNSPort is set more than once. (Patch from Robert
11714 Hogan.) [Bugfix on 0.2.0.2-alpha]
11715 - Add DNSPort connections to the global connection list, so that we
11716 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
11718 - Fix a dangling reference that could lead to a crash when DNSPort is
11719 changed or closed (Patch from Robert Hogan.) [Bugfix on
11722 o Minor bugfixes (controller):
11723 - Provide DNS expiry times in GMT, not in local time. For backward
11724 compatibility, ADDRMAP events only provide GMT expiry in an extended
11725 field. "GETINFO address-mappings" always does the right thing.
11726 - Use CRLF line endings properly in NS events.
11727 - Terminate multi-line control events properly. (Original patch
11728 from tup.) [Bugfix on 0.1.2.x-alpha]
11729 - Do not include spaces in SOURCE_ADDR fields in STREAM
11730 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
11733 Changes in version 0.1.2.15 - 2007-07-17
11734 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
11735 problems, fixes compilation on BSD, and fixes a variety of other
11736 bugs. Everybody should upgrade.
11738 o Major bugfixes (compilation):
11739 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
11741 o Major bugfixes (crashes):
11742 - Try even harder not to dereference the first character after
11743 an mmap(). Reported by lodger.
11744 - Fix a crash bug in directory authorities when we re-number the
11745 routerlist while inserting a new router.
11746 - When the cached-routers file is an even multiple of the page size,
11747 don't run off the end and crash. (Fixes bug 455; based on idea
11749 - Fix eventdns.c behavior on Solaris: It is critical to include
11750 orconfig.h _before_ sys/types.h, so that we can get the expected
11751 definition of _FILE_OFFSET_BITS.
11753 o Major bugfixes (security):
11754 - Fix a possible buffer overrun when using BSD natd support. Bug
11756 - When sending destroy cells from a circuit's origin, don't include
11757 the reason for tearing down the circuit. The spec says we didn't,
11758 and now we actually don't. Reported by lodger.
11759 - Keep streamids from different exits on a circuit separate. This
11760 bug may have allowed other routers on a given circuit to inject
11761 cells into streams. Reported by lodger; fixes bug 446.
11762 - If there's a never-before-connected-to guard node in our list,
11763 never choose any guards past it. This way we don't expand our
11764 guard list unless we need to.
11766 o Minor bugfixes (guard nodes):
11767 - Weight guard selection by bandwidth, so that low-bandwidth nodes
11768 don't get overused as guards.
11770 o Minor bugfixes (directory):
11771 - Correctly count the number of authorities that recommend each
11772 version. Previously, we were under-counting by 1.
11773 - Fix a potential crash bug when we load many server descriptors at
11774 once and some of them make others of them obsolete. Fixes bug 458.
11776 o Minor bugfixes (hidden services):
11777 - Stop tearing down the whole circuit when the user asks for a
11778 connection to a port that the hidden service didn't configure.
11781 o Minor bugfixes (misc):
11782 - On Windows, we were preventing other processes from reading
11783 cached-routers while Tor was running. Reported by janbar.
11784 - Fix a possible (but very unlikely) bug in picking routers by
11785 bandwidth. Add a log message to confirm that it is in fact
11786 unlikely. Patch from lodger.
11787 - Backport a couple of memory leak fixes.
11788 - Backport miscellaneous cosmetic bugfixes.
11791 Changes in version 0.2.0.2-alpha - 2007-06-02
11792 o Major bugfixes on 0.2.0.1-alpha:
11793 - Fix an assertion failure related to servers without extra-info digests.
11794 Resolves bugs 441 and 442.
11796 o Minor features (directory):
11797 - Support "If-Modified-Since" when answering HTTP requests for
11798 directories, running-routers documents, and network-status documents.
11799 (There's no need to support it for router descriptors, since those
11800 are downloaded by descriptor digest.)
11802 o Minor build issues:
11803 - Clear up some MIPSPro compiler warnings.
11804 - When building from a tarball on a machine that happens to have SVK
11805 installed, report the micro-revision as whatever version existed
11806 in the tarball, not as "x".
11809 Changes in version 0.2.0.1-alpha - 2007-06-01
11810 This early development snapshot provides new features for people running
11811 Tor as both a client and a server (check out the new RelayBandwidth
11812 config options); lets Tor run as a DNS proxy; and generally moves us
11813 forward on a lot of fronts.
11815 o Major features, server usability:
11816 - New config options RelayBandwidthRate and RelayBandwidthBurst:
11817 a separate set of token buckets for relayed traffic. Right now
11818 relayed traffic is defined as answers to directory requests, and
11819 OR connections that don't have any local circuits on them.
11821 o Major features, client usability:
11822 - A client-side DNS proxy feature to replace the need for
11823 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
11824 for DNS requests on port 9999, use the Tor network to resolve them
11825 anonymously, and send the reply back like a regular DNS server.
11826 The code still only implements a subset of DNS.
11827 - Make PreferTunneledDirConns and TunnelDirConns work even when
11828 we have no cached directory info. This means Tor clients can now
11829 do all of their connections protected by TLS.
11831 o Major features, performance and efficiency:
11832 - Directory authorities accept and serve "extra info" documents for
11833 routers. These documents contain fields from router descriptors
11834 that aren't usually needed, and that use a lot of excess
11835 bandwidth. Once these fields are removed from router descriptors,
11836 the bandwidth savings should be about 60%. [Partially implements
11838 - Servers upload extra-info documents to any authority that accepts
11839 them. Authorities (and caches that have been configured to download
11840 extra-info documents) download them as needed. [Partially implements
11842 - Change the way that Tor buffers data that it is waiting to write.
11843 Instead of queueing data cells in an enormous ring buffer for each
11844 client->OR or OR->OR connection, we now queue cells on a separate
11845 queue for each circuit. This lets us use less slack memory, and
11846 will eventually let us be smarter about prioritizing different kinds
11848 - Use memory pools to allocate cells with better speed and memory
11849 efficiency, especially on platforms where malloc() is inefficient.
11850 - Stop reading on edge connections when their corresponding circuit
11851 buffers are full; start again as the circuits empty out.
11853 o Major features, other:
11854 - Add an HSAuthorityRecordStats option that hidden service authorities
11855 can use to track statistics of overall hidden service usage without
11856 logging information that would be very useful to an attacker.
11857 - Start work implementing multi-level keys for directory authorities:
11858 Add a standalone tool to generate key certificates. (Proposal 103.)
11861 - Directory authorities now call routers Stable if they have an
11862 uptime of at least 30 days, even if that's not the median uptime
11863 in the network. Implements proposal 107, suggested by Kevin Bauer
11866 o Minor fixes (resource management):
11867 - Count the number of open sockets separately from the number
11868 of active connection_t objects. This will let us avoid underusing
11869 our allocated connection limit.
11870 - We no longer use socket pairs to link an edge connection to an
11871 anonymous directory connection or a DirPort test connection.
11872 Instead, we track the link internally and transfer the data
11873 in-process. This saves two sockets per "linked" connection (at the
11874 client and at the server), and avoids the nasty Windows socketpair()
11876 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
11877 for every single inactive connection_t. Free items from the
11878 4k/16k-buffer free lists when they haven't been used for a while.
11880 o Minor features (build):
11881 - Make autoconf search for libevent, openssl, and zlib consistently.
11882 - Update deprecated macros in configure.in.
11883 - When warning about missing headers, tell the user to let us
11884 know if the compile succeeds anyway, so we can downgrade the
11886 - Include the current subversion revision as part of the version
11887 string: either fetch it directly if we're in an SVN checkout, do
11888 some magic to guess it if we're in an SVK checkout, or use
11889 the last-detected version if we're building from a .tar.gz.
11890 Use this version consistently in log messages.
11892 o Minor features (logging):
11893 - Always prepend "Bug: " to any log message about a bug.
11894 - Put a platform string (e.g. "Linux i686") in the startup log
11895 message, so when people paste just their logs, we know if it's
11896 OpenBSD or Windows or what.
11897 - When logging memory usage, break down memory used in buffers by
11900 o Minor features (directory system):
11901 - New config option V2AuthoritativeDirectory that all directory
11902 authorities should set. This will let future authorities choose
11903 not to serve V2 directory information.
11904 - Directory authorities allow multiple router descriptors and/or extra
11905 info documents to be uploaded in a single go. This will make
11906 implementing proposal 104 simpler.
11908 o Minor features (controller):
11909 - Add a new config option __DisablePredictedCircuits designed for
11910 use by the controller, when we don't want Tor to build any circuits
11912 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
11913 so we can exit from the middle of the circuit.
11914 - Implement "getinfo status/circuit-established".
11915 - Implement "getinfo status/version/..." so a controller can tell
11916 whether the current version is recommended, and whether any versions
11917 are good, and how many authorities agree. (Patch from shibz.)
11919 o Minor features (hidden services):
11920 - Allow multiple HiddenServicePort directives with the same virtual
11921 port; when they occur, the user is sent round-robin to one
11922 of the target ports chosen at random. Partially fixes bug 393 by
11923 adding limited ad-hoc round-robining.
11925 o Minor features (other):
11927 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11928 resolve request for hosts matching a given pattern causes Tor to
11929 generate an internal virtual address mapping for that host. This
11930 allows DNSPort to work sensibly with hidden service users. By
11931 default, .exit and .onion addresses are remapped; the list of
11932 patterns can be reconfigured with AutomapHostsSuffixes.
11933 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11934 address. Thanks to the AutomapHostsOnResolve option, this is no
11935 longer a completely silly thing to do.
11936 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11937 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11938 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11939 minus 1 byte: the actual maximum declared bandwidth.
11941 o Removed features:
11942 - Removed support for the old binary "version 0" controller protocol.
11943 This has been deprecated since 0.1.1, and warnings have been issued
11944 since 0.1.2. When we encounter a v0 control message, we now send
11945 back an error and close the connection.
11946 - Remove the old "dns worker" server DNS code: it hasn't been default
11947 since 0.1.2.2-alpha, and all the servers seem to be using the new
11950 o Minor bugfixes (portability):
11951 - Even though Windows is equally happy with / and \ as path separators,
11952 try to use \ consistently on Windows and / consistently on Unix: it
11953 makes the log messages nicer.
11954 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11955 - Read resolv.conf files correctly on platforms where read() returns
11956 partial results on small file reads.
11958 o Minor bugfixes (directory):
11959 - Correctly enforce that elements of directory objects do not appear
11960 more often than they are allowed to appear.
11961 - When we are reporting the DirServer line we just parsed, we were
11962 logging the second stanza of the key fingerprint, not the first.
11964 o Minor bugfixes (logging):
11965 - When we hit an EOF on a log (probably because we're shutting down),
11966 don't try to remove the log from the list: just mark it as
11967 unusable. (Bulletproofs against bug 222.)
11969 o Minor bugfixes (other):
11970 - In the exitlist script, only consider the most recently published
11971 server descriptor for each server. Also, when the user requests
11972 a list of servers that _reject_ connections to a given address,
11973 explicitly exclude the IPs that also have servers that accept
11974 connections to that address. (Resolves bug 405.)
11975 - Stop allowing hibernating servers to be "stable" or "fast".
11976 - On Windows, we were preventing other processes from reading
11977 cached-routers while Tor was running. (Reported by janbar)
11978 - Make the NodeFamilies config option work. (Reported by
11979 lodger -- it has never actually worked, even though we added it
11981 - Check return values from pthread_mutex functions.
11982 - Don't save non-general-purpose router descriptors to the disk cache,
11983 because we have no way of remembering what their purpose was when
11985 - Add even more asserts to hunt down bug 417.
11986 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
11987 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
11988 Add a log message to confirm that it is in fact unlikely.
11990 o Minor bugfixes (controller):
11991 - Make 'getinfo fingerprint' return a 551 error if we're not a
11992 server, so we match what the control spec claims we do. Reported
11994 - Fix a typo in an error message when extendcircuit fails that
11995 caused us to not follow the \r\n-based delimiter protocol. Reported
11998 o Code simplifications and refactoring:
11999 - Stop passing around circuit_t and crypt_path_t pointers that are
12000 implicit in other procedure arguments.
12001 - Drop the old code to choke directory connections when the
12002 corresponding OR connections got full: thanks to the cell queue
12003 feature, OR conns don't get full any more.
12004 - Make dns_resolve() handle attaching connections to circuits
12005 properly, so the caller doesn't have to.
12006 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
12007 - Keep the connection array as a dynamic smartlist_t, rather than as
12008 a fixed-sized array. This is important, as the number of connections
12009 is becoming increasingly decoupled from the number of sockets.
12012 Changes in version 0.1.2.14 - 2007-05-25
12013 Tor 0.1.2.14 changes the addresses of two directory authorities (this
12014 change especially affects those who serve or use hidden services),
12015 and fixes several other crash- and security-related bugs.
12017 o Directory authority changes:
12018 - Two directory authorities (moria1 and moria2) just moved to new
12019 IP addresses. This change will particularly affect those who serve
12020 or use hidden services.
12022 o Major bugfixes (crashes):
12023 - If a directory server runs out of space in the connection table
12024 as it's processing a begin_dir request, it will free the exit stream
12025 but leave it attached to the circuit, leading to unpredictable
12026 behavior. (Reported by seeess, fixes bug 425.)
12027 - Fix a bug in dirserv_remove_invalid() that would cause authorities
12028 to corrupt memory under some really unlikely scenarios.
12029 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
12030 - Avoid segfaults when reading from mmaped descriptor file. (Reported
12033 o Major bugfixes (security):
12034 - When choosing an entry guard for a circuit, avoid using guards
12035 that are in the same family as the chosen exit -- not just guards
12036 that are exactly the chosen exit. (Reported by lodger.)
12038 o Major bugfixes (resource management):
12039 - If a directory authority is down, skip it when deciding where to get
12040 networkstatus objects or descriptors. Otherwise we keep asking
12041 every 10 seconds forever. Fixes bug 384.
12042 - Count it as a failure if we fetch a valid network-status but we
12043 don't want to keep it. Otherwise we'll keep fetching it and keep
12044 not wanting to keep it. Fixes part of bug 422.
12045 - If all of our dirservers have given us bad or no networkstatuses
12046 lately, then stop hammering them once per minute even when we
12047 think they're failed. Fixes another part of bug 422.
12050 - Actually set the purpose correctly for descriptors inserted with
12051 purpose=controller.
12052 - When we have k non-v2 authorities in our DirServer config,
12053 we ignored the last k authorities in the list when updating our
12055 - Correctly back-off from requesting router descriptors that we are
12056 having a hard time downloading.
12057 - Read resolv.conf files correctly on platforms where read() returns
12058 partial results on small file reads.
12059 - Don't rebuild the entire router store every time we get 32K of
12060 routers: rebuild it when the journal gets very large, or when
12061 the gaps in the store get very large.
12064 - When routers publish SVN revisions in their router descriptors,
12065 authorities now include those versions correctly in networkstatus
12067 - Warn when using a version of libevent before 1.3b to run a server on
12068 OSX or BSD: these versions interact badly with userspace threads.
12071 Changes in version 0.1.2.13 - 2007-04-24
12072 This release features some major anonymity fixes, such as safer path
12073 selection; better client performance; faster bootstrapping, better
12074 address detection, and better DNS support for servers; write limiting as
12075 well as read limiting to make servers easier to run; and a huge pile of
12076 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
12078 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
12079 of the Freenode IRC network, remembering his patience and vision for
12080 free speech on the Internet.
12083 - Fix a memory leak when we ask for "all" networkstatuses and we
12084 get one we don't recognize.
12085 - Add more asserts to hunt down bug 417.
12086 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
12089 Changes in version 0.1.2.12-rc - 2007-03-16
12091 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
12092 directory information requested inside Tor connections (i.e. via
12093 begin_dir cells). It only triggered when the same connection was
12094 serving other data at the same time. Reported by seeess.
12097 - When creating a circuit via the controller, send a 'launched'
12098 event when we're done, so we follow the spec better.
12101 Changes in version 0.1.2.11-rc - 2007-03-15
12102 o Minor bugfixes (controller), reported by daejees:
12103 - Correct the control spec to match how the code actually responds
12104 to 'getinfo addr-mappings/*'.
12105 - The control spec described a GUARDS event, but the code
12106 implemented a GUARD event. Standardize on GUARD, but let people
12107 ask for GUARDS too.
12110 Changes in version 0.1.2.10-rc - 2007-03-07
12111 o Major bugfixes (Windows):
12112 - Do not load the NT services library functions (which may not exist)
12113 just to detect if we're a service trying to shut down. Now we run
12114 on Win98 and friends again.
12116 o Minor bugfixes (other):
12117 - Clarify a couple of log messages.
12118 - Fix a misleading socks5 error number.
12121 Changes in version 0.1.2.9-rc - 2007-03-02
12122 o Major bugfixes (Windows):
12123 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
12124 of the usual GCC "%llu". This prevents a bug when saving 64-bit
12125 int configuration values: the high-order 32 bits would get
12126 truncated. In particular, we were being bitten by the default
12127 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
12128 and maybe also bug 397.)
12130 o Minor bugfixes (performance):
12131 - Use OpenSSL's AES implementation on platforms where it's faster.
12132 This could save us as much as 10% CPU usage.
12134 o Minor bugfixes (server):
12135 - Do not rotate onion key immediately after setting it for the first
12138 o Minor bugfixes (directory authorities):
12139 - Stop calling servers that have been hibernating for a long time
12140 "stable". Also, stop letting hibernating or obsolete servers affect
12141 uptime and bandwidth cutoffs.
12142 - Stop listing hibernating servers in the v1 directory.
12144 o Minor bugfixes (hidden services):
12145 - Upload hidden service descriptors slightly less often, to reduce
12146 load on authorities.
12148 o Minor bugfixes (other):
12149 - Fix an assert that could trigger if a controller quickly set then
12150 cleared EntryNodes. Bug found by Udo van den Heuvel.
12151 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
12153 - Fix a potential race condition in the rpm installer. Found by
12155 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
12156 of 2 as indicating that the server is completely bad; it sometimes
12157 means that the server is just bad for the request in question. (may fix
12158 the last of bug 326.)
12159 - Disable encrypted directory connections when we don't have a server
12160 descriptor for the destination. We'll get this working again in
12164 Changes in version 0.1.2.8-beta - 2007-02-26
12165 o Major bugfixes (crashes):
12166 - Stop crashing when the controller asks us to resetconf more than
12167 one config option at once. (Vidalia 0.0.11 does this.)
12168 - Fix a crash that happened on Win98 when we're given command-line
12169 arguments: don't try to load NT service functions from advapi32.dll
12170 except when we need them. (Bug introduced in 0.1.2.7-alpha;
12172 - Fix a longstanding obscure crash bug that could occur when
12173 we run out of DNS worker processes. (Resolves bug 390.)
12175 o Major bugfixes (hidden services):
12176 - Correctly detect whether hidden service descriptor downloads are
12177 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
12179 o Major bugfixes (accounting):
12180 - When we start during an accounting interval before it's time to wake
12181 up, remember to wake up at the correct time. (May fix bug 342.)
12183 o Minor bugfixes (controller):
12184 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
12185 clear the corresponding on_circuit variable, and remember later
12186 that we don't need to send a redundant CLOSED event. Resolves part
12188 - Report events where a resolve succeeded or where we got a socks
12189 protocol error correctly, rather than calling both of them
12191 - Change reported stream target addresses to IP consistently when
12192 we finally get the IP from an exit node.
12193 - Send log messages to the controller even if they happen to be very
12196 o Minor bugfixes (other):
12197 - Display correct results when reporting which versions are
12198 recommended, and how recommended they are. (Resolves bug 383.)
12199 - Improve our estimates for directory bandwidth to be less random:
12200 guess that an unrecognized directory will have the average bandwidth
12201 from all known directories, not that it will have the average
12202 bandwidth from those directories earlier than it on the list.
12203 - If we start a server with ClientOnly 1, then set ClientOnly to 0
12204 and hup, stop triggering an assert based on an empty onion_key.
12205 - On platforms with no working mmap() equivalent, don't warn the
12206 user when cached-routers doesn't exist.
12207 - Warn the user when mmap() [or its equivalent] fails for some reason
12208 other than file-not-found.
12209 - Don't warn the user when cached-routers.new doesn't exist: that's
12210 perfectly fine when starting up for the first time.
12211 - When EntryNodes are configured, rebuild the guard list to contain,
12212 in order: the EntryNodes that were guards before; the rest of the
12213 EntryNodes; the nodes that were guards before.
12214 - Mask out all signals in sub-threads; only the libevent signal
12215 handler should be processing them. This should prevent some crashes
12216 on some machines using pthreads. (Patch from coderman.)
12217 - Fix switched arguments on memset in the implementation of
12218 tor_munmap() for systems with no mmap() call.
12219 - When Tor receives a router descriptor that it asked for, but
12220 no longer wants (because it has received fresh networkstatuses
12221 in the meantime), do not warn the user. Cache the descriptor if
12222 we're a cache; drop it if we aren't.
12223 - Make earlier entry guards _really_ get retried when the network
12225 - On a malformed DNS reply, always give an error to the corresponding
12227 - Build with recent libevents on platforms that do not define the
12228 nonstandard types "u_int8_t" and friends.
12230 o Minor features (controller):
12231 - Warn the user when an application uses the obsolete binary v0
12232 control protocol. We're planning to remove support for it during
12233 the next development series, so it's good to give people some
12235 - Add STREAM_BW events to report per-entry-stream bandwidth
12236 use. (Patch from Robert Hogan.)
12237 - Rate-limit SIGNEWNYM signals in response to controllers that
12238 impolitely generate them for every single stream. (Patch from
12239 mwenge; closes bug 394.)
12240 - Make REMAP stream events have a SOURCE (cache or exit), and
12241 make them generated in every case where we get a successful
12242 connected or resolved cell.
12244 o Minor bugfixes (performance):
12245 - Call router_have_min_dir_info half as often. (This is showing up in
12246 some profiles, but not others.)
12247 - When using GCC, make log_debug never get called at all, and its
12248 arguments never get evaluated, when no debug logs are configured.
12249 (This is showing up in some profiles, but not others.)
12252 - Remove some never-implemented options. Mark PathlenCoinWeight as
12254 - Implement proposal 106: Stop requiring clients to have well-formed
12255 certificates; stop checking nicknames in certificates. (Clients
12256 have certificates so that they can look like Tor servers, but in
12257 the future we might want to allow them to look like regular TLS
12258 clients instead. Nicknames in certificates serve no purpose other
12259 than making our protocol easier to recognize on the wire.)
12260 - Revise messages on handshake failure again to be even more clear about
12261 which are incoming connections and which are outgoing.
12262 - Discard any v1 directory info that's over 1 month old (for
12263 directories) or over 1 week old (for running-routers lists).
12264 - Do not warn when individual nodes in the configuration's EntryNodes,
12265 ExitNodes, etc are down: warn only when all possible nodes
12266 are down. (Fixes bug 348.)
12267 - Always remove expired routers and networkstatus docs before checking
12268 whether we have enough information to build circuits. (Fixes
12270 - Put a lower-bound on MaxAdvertisedBandwidth.
12273 Changes in version 0.1.2.7-alpha - 2007-02-06
12274 o Major bugfixes (rate limiting):
12275 - Servers decline directory requests much more aggressively when
12276 they're low on bandwidth. Otherwise they end up queueing more and
12277 more directory responses, which can't be good for latency.
12278 - But never refuse directory requests from local addresses.
12279 - Fix a memory leak when sending a 503 response for a networkstatus
12281 - Be willing to read or write on local connections (e.g. controller
12282 connections) even when the global rate limiting buckets are empty.
12283 - If our system clock jumps back in time, don't publish a negative
12284 uptime in the descriptor. Also, don't let the global rate limiting
12285 buckets go absurdly negative.
12286 - Flush local controller connection buffers periodically as we're
12287 writing to them, so we avoid queueing 4+ megabytes of data before
12290 o Major bugfixes (NT services):
12291 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
12292 command-line flag so that admins can override the default by saying
12293 "tor --service install --user "SomeUser"". This will not affect
12294 existing installed services. Also, warn the user that the service
12295 will look for its configuration file in the service user's
12296 %appdata% directory. (We can't do the 'hardwire the user's appdata
12297 directory' trick any more, since we may not have read access to that
12300 o Major bugfixes (other):
12301 - Previously, we would cache up to 16 old networkstatus documents
12302 indefinitely, if they came from nontrusted authorities. Now we
12303 discard them if they are more than 10 days old.
12304 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
12306 - Detect and reject malformed DNS responses containing circular
12308 - If exits are rare enough that we're not marking exits as guards,
12309 ignore exit bandwidth when we're deciding the required bandwidth
12311 - When we're handling a directory connection tunneled over Tor,
12312 don't fill up internal memory buffers with all the data we want
12313 to tunnel; instead, only add it if the OR connection that will
12314 eventually receive it has some room for it. (This can lead to
12315 slowdowns in tunneled dir connections; a better solution will have
12316 to wait for 0.2.0.)
12318 o Minor bugfixes (dns):
12319 - Add some defensive programming to eventdns.c in an attempt to catch
12320 possible memory-stomping bugs.
12321 - Detect and reject DNS replies containing IPv4 or IPv6 records with
12322 an incorrect number of bytes. (Previously, we would ignore the
12324 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
12325 in the correct order, and doesn't crash.
12326 - Free memory held in recently-completed DNS lookup attempts on exit.
12327 This was not a memory leak, but may have been hiding memory leaks.
12328 - Handle TTL values correctly on reverse DNS lookups.
12329 - Treat failure to parse resolv.conf as an error.
12331 o Minor bugfixes (other):
12332 - Fix crash with "tor --list-fingerprint" (reported by seeess).
12333 - When computing clock skew from directory HTTP headers, consider what
12334 time it was when we finished asking for the directory, not what
12336 - Expire socks connections if they spend too long waiting for the
12337 handshake to finish. Previously we would let them sit around for
12338 days, if the connecting application didn't close them either.
12339 - And if the socks handshake hasn't started, don't send a
12340 "DNS resolve socks failed" handshake reply; just close it.
12341 - Stop using C functions that OpenBSD's linker doesn't like.
12342 - Don't launch requests for descriptors unless we have networkstatuses
12343 from at least half of the authorities. This delays the first
12344 download slightly under pathological circumstances, but can prevent
12345 us from downloading a bunch of descriptors we don't need.
12346 - Do not log IPs with TLS failures for incoming TLS
12347 connections. (Fixes bug 382.)
12348 - If the user asks to use invalid exit nodes, be willing to use
12350 - Stop using the reserved ac_cv namespace in our configure script.
12351 - Call stat() slightly less often; use fstat() when possible.
12352 - Refactor the way we handle pending circuits when an OR connection
12353 completes or fails, in an attempt to fix a rare crash bug.
12354 - Only rewrite a conn's address based on X-Forwarded-For: headers
12355 if it's a parseable public IP address; and stop adding extra quotes
12356 to the resulting address.
12359 - Weight directory requests by advertised bandwidth. Now we can
12360 let servers enable write limiting but still allow most clients to
12361 succeed at their directory requests. (We still ignore weights when
12362 choosing a directory authority; I hope this is a feature.)
12365 - Create a new file ReleaseNotes which was the old ChangeLog. The
12366 new ChangeLog file now includes the summaries for all development
12368 - Check for addresses with invalid characters at the exit as well
12369 as at the client, and warn less verbosely when they fail. You can
12370 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
12371 - Adapt a patch from goodell to let the contrib/exitlist script
12372 take arguments rather than require direct editing.
12373 - Inform the server operator when we decide not to advertise a
12374 DirPort due to AccountingMax enabled or a low BandwidthRate. It
12375 was confusing Zax, so now we're hopefully more helpful.
12376 - Bring us one step closer to being able to establish an encrypted
12377 directory tunnel without knowing a descriptor first. Still not
12378 ready yet. As part of the change, now assume we can use a
12379 create_fast cell if we don't know anything about a router.
12380 - Allow exit nodes to use nameservers running on ports other than 53.
12381 - Servers now cache reverse DNS replies.
12382 - Add an --ignore-missing-torrc command-line option so that we can
12383 get the "use sensible defaults if the configuration file doesn't
12384 exist" behavior even when specifying a torrc location on the command
12387 o Minor features (controller):
12388 - Track reasons for OR connection failure; make these reasons
12389 available via the controller interface. (Patch from Mike Perry.)
12390 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
12391 can learn when clients are sending malformed hostnames to Tor.
12392 - Clean up documentation for controller status events.
12393 - Add a REMAP status to stream events to note that a stream's
12394 address has changed because of a cached address or a MapAddress
12398 Changes in version 0.1.2.6-alpha - 2007-01-09
12400 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
12401 connection handles more than 4 gigs in either direction, we crash.
12402 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
12403 advertised exit node, somebody might try to exit from us when
12404 we're bootstrapping and before we've built our descriptor yet.
12405 Refuse the connection rather than crashing.
12408 - Warn if we (as a server) find that we've resolved an address that we
12409 weren't planning to resolve.
12410 - Warn that using select() on any libevent version before 1.1 will be
12411 unnecessarily slow (even for select()).
12412 - Flush ERR-level controller status events just like we currently
12413 flush ERR-level log events, so that a Tor shutdown doesn't prevent
12414 the controller from learning about current events.
12416 o Minor features (more controller status events):
12417 - Implement EXTERNAL_ADDRESS server status event so controllers can
12418 learn when our address changes.
12419 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
12420 can learn when directories reject our descriptor.
12421 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
12422 can learn when a client application is speaking a non-socks protocol
12424 - Implement DANGEROUS_SOCKS client status event so controllers
12425 can learn when a client application is leaking DNS addresses.
12426 - Implement BUG general status event so controllers can learn when
12427 Tor is unhappy about its internal invariants.
12428 - Implement CLOCK_SKEW general status event so controllers can learn
12429 when Tor thinks the system clock is set incorrectly.
12430 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
12431 server status events so controllers can learn when their descriptors
12432 are accepted by a directory.
12433 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
12434 server status events so controllers can learn about Tor's progress in
12435 deciding whether it's reachable from the outside.
12436 - Implement BAD_LIBEVENT general status event so controllers can learn
12437 when we have a version/method combination in libevent that needs to
12439 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
12440 and DNS_USELESS server status events so controllers can learn
12441 about changes to DNS server status.
12443 o Minor features (directory):
12444 - Authorities no longer recommend exits as guards if this would shift
12445 too much load to the exit nodes.
12448 Changes in version 0.1.2.5-alpha - 2007-01-06
12450 - Enable write limiting as well as read limiting. Now we sacrifice
12451 capacity if we're pushing out lots of directory traffic, rather
12452 than overrunning the user's intended bandwidth limits.
12453 - Include TLS overhead when counting bandwidth usage; previously, we
12454 would count only the bytes sent over TLS, but not the bytes used
12456 - Support running the Tor service with a torrc not in the same
12457 directory as tor.exe and default to using the torrc located in
12458 the %appdata%\Tor\ of the user who installed the service. Patch
12460 - Servers now check for the case when common DNS requests are going to
12461 wildcarded addresses (i.e. all getting the same answer), and change
12462 their exit policy to reject *:* if it's happening.
12463 - Implement BEGIN_DIR cells, so we can connect to the directory
12464 server via TLS to do encrypted directory requests rather than
12465 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
12466 config options if you like.
12468 o Minor features (config and docs):
12469 - Start using the state file to store bandwidth accounting data:
12470 the bw_accounting file is now obsolete. We'll keep generating it
12471 for a while for people who are still using 0.1.2.4-alpha.
12472 - Try to batch changes to the state file so that we do as few
12473 disk writes as possible while still storing important things in
12475 - The state file and the bw_accounting file get saved less often when
12476 the AvoidDiskWrites config option is set.
12477 - Make PIDFile work on Windows (untested).
12478 - Add internal descriptions for a bunch of configuration options:
12479 accessible via controller interface and in comments in saved
12481 - Reject *:563 (NNTPS) in the default exit policy. We already reject
12482 NNTP by default, so this seems like a sensible addition.
12483 - Clients now reject hostnames with invalid characters. This should
12484 avoid some inadvertent info leaks. Add an option
12485 AllowNonRFC953Hostnames to disable this behavior, in case somebody
12486 is running a private network with hosts called @, !, and #.
12487 - Add a maintainer script to tell us which options are missing
12488 documentation: "make check-docs".
12489 - Add a new address-spec.txt document to describe our special-case
12490 addresses: .exit, .onion, and .noconnnect.
12492 o Minor features (DNS):
12493 - Ongoing work on eventdns infrastructure: now it has dns server
12494 and ipv6 support. One day Tor will make use of it.
12495 - Add client-side caching for reverse DNS lookups.
12496 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
12497 - When we change nameservers or IP addresses, reset and re-launch
12498 our tests for DNS hijacking.
12500 o Minor features (directory):
12501 - Authorities now specify server versions in networkstatus. This adds
12502 about 2% to the size of compressed networkstatus docs, and allows
12503 clients to tell which servers support BEGIN_DIR and which don't.
12504 The implementation is forward-compatible with a proposed future
12505 protocol version scheme not tied to Tor versions.
12506 - DirServer configuration lines now have an orport= option so
12507 clients can open encrypted tunnels to the authorities without
12508 having downloaded their descriptors yet. Enabled for moria1,
12509 moria2, tor26, and lefkada now in the default configuration.
12510 - Directory servers are more willing to send a 503 "busy" if they
12511 are near their write limit, especially for v1 directory requests.
12512 Now they can use their limited bandwidth for actual Tor traffic.
12513 - Clients track responses with status 503 from dirservers. After a
12514 dirserver has given us a 503, we try not to use it until an hour has
12515 gone by, or until we have no dirservers that haven't given us a 503.
12516 - When we get a 503 from a directory, and we're not a server, we don't
12517 count the failure against the total number of failures allowed
12518 for the thing we're trying to download.
12519 - Report X-Your-Address-Is correctly from tunneled directory
12520 connections; don't report X-Your-Address-Is when it's an internal
12521 address; and never believe reported remote addresses when they're
12523 - Protect against an unlikely DoS attack on directory servers.
12524 - Add a BadDirectory flag to network status docs so that authorities
12525 can (eventually) tell clients about caches they believe to be
12528 o Minor features (controller):
12529 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
12530 - Reimplement GETINFO so that info/names stays in sync with the
12532 - Implement "GETINFO fingerprint".
12533 - Implement "SETEVENTS GUARD" so controllers can get updates on
12534 entry guard status as it changes.
12536 o Minor features (clean up obsolete pieces):
12537 - Remove some options that have been deprecated since at least
12538 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
12539 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
12540 to set log options.
12541 - We no longer look for identity and onion keys in "identity.key" and
12542 "onion.key" -- these were replaced by secret_id_key and
12543 secret_onion_key in 0.0.8pre1.
12544 - We no longer require unrecognized directory entries to be
12547 o Major bugfixes (security):
12548 - Stop sending the HttpProxyAuthenticator string to directory
12549 servers when directory connections are tunnelled through Tor.
12550 - Clients no longer store bandwidth history in the state file.
12551 - Do not log introduction points for hidden services if SafeLogging
12553 - When generating bandwidth history, round down to the nearest
12554 1k. When storing accounting data, round up to the nearest 1k.
12555 - When we're running as a server, remember when we last rotated onion
12556 keys, so that we will rotate keys once they're a week old even if
12557 we never stay up for a week ourselves.
12559 o Major bugfixes (other):
12560 - Fix a longstanding bug in eventdns that prevented the count of
12561 timed-out resolves from ever being reset. This bug caused us to
12562 give up on a nameserver the third time it timed out, and try it
12563 10 seconds later... and to give up on it every time it timed out
12565 - Take out the '5 second' timeout from the connection retry
12566 schedule. Now the first connect attempt will wait a full 10
12567 seconds before switching to a new circuit. Perhaps this will help
12568 a lot. Based on observations from Mike Perry.
12569 - Fix a bug on the Windows implementation of tor_mmap_file() that
12570 would prevent the cached-routers file from ever loading. Reported
12574 - Fix an assert failure when a directory authority sets
12575 AuthDirRejectUnlisted and then receives a descriptor from an
12576 unlisted router. Reported by seeess.
12577 - Avoid a double-free when parsing malformed DirServer lines.
12578 - Fix a bug when a BSD-style PF socket is first used. Patch from
12580 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
12581 to resolve an address at a given exit node even when they ask for
12583 - Servers no longer ever list themselves in their "family" line,
12584 even if configured to do so. This makes it easier to configure
12585 family lists conveniently.
12586 - When running as a server, don't fall back to 127.0.0.1 when no
12587 nameservers are configured in /etc/resolv.conf; instead, make the
12588 user fix resolv.conf or specify nameservers explicitly. (Resolves
12590 - Stop accepting certain malformed ports in configured exit policies.
12591 - Don't re-write the fingerprint file every restart, unless it has
12593 - Stop warning when a single nameserver fails: only warn when _all_ of
12594 our nameservers have failed. Also, when we only have one nameserver,
12595 raise the threshold for deciding that the nameserver is dead.
12596 - Directory authorities now only decide that routers are reachable
12597 if their identity keys are as expected.
12598 - When the user uses bad syntax in the Log config line, stop
12599 suggesting other bad syntax as a replacement.
12600 - Correctly detect ipv6 DNS capability on OpenBSD.
12602 o Minor bugfixes (controller):
12603 - Report the circuit number correctly in STREAM CLOSED events. Bug
12604 reported by Mike Perry.
12605 - Do not report bizarre values for results of accounting GETINFOs
12606 when the last second's write or read exceeds the allotted bandwidth.
12607 - Report "unrecognized key" rather than an empty string when the
12608 controller tries to fetch a networkstatus that doesn't exist.
12611 Changes in version 0.1.1.26 - 2006-12-14
12612 o Security bugfixes:
12613 - Stop sending the HttpProxyAuthenticator string to directory
12614 servers when directory connections are tunnelled through Tor.
12615 - Clients no longer store bandwidth history in the state file.
12616 - Do not log introduction points for hidden services if SafeLogging
12620 - Fix an assert failure when a directory authority sets
12621 AuthDirRejectUnlisted and then receives a descriptor from an
12622 unlisted router (reported by seeess).
12625 Changes in version 0.1.2.4-alpha - 2006-12-03
12627 - Add support for using natd; this allows FreeBSDs earlier than
12628 5.1.2 to have ipfw send connections through Tor without using
12629 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
12632 - Make all connections to addresses of the form ".noconnect"
12633 immediately get closed. This lets application/controller combos
12634 successfully test whether they're talking to the same Tor by
12635 watching for STREAM events.
12636 - Make cross.sh cross-compilation script work even when autogen.sh
12637 hasn't been run. (Patch from Michael Mohr.)
12638 - Statistics dumped by -USR2 now include a breakdown of public key
12639 operations, for profiling.
12642 - Fix a major leak when directory authorities parse their
12643 approved-routers list, a minor memory leak when we fail to pick
12644 an exit node, and a few rare leaks on errors.
12645 - Handle TransPort connections even when the server sends data before
12646 the client sends data. Previously, the connection would just hang
12647 until the client sent data. (Patch from tup based on patch from
12649 - Avoid assert failure when our cached-routers file is empty on
12653 - Don't log spurious warnings when we see a circuit close reason we
12654 don't recognize; it's probably just from a newer version of Tor.
12655 - Have directory authorities allow larger amounts of drift in uptime
12656 without replacing the server descriptor: previously, a server that
12657 restarted every 30 minutes could have 48 "interesting" descriptors
12659 - Start linking to the Tor specification and Tor reference manual
12660 correctly in the Windows installer.
12661 - Add Vidalia to the OS X uninstaller script, so when we uninstall
12662 Tor/Privoxy we also uninstall Vidalia.
12663 - Resume building on Irix64, and fix a lot of warnings from its
12664 MIPSpro C compiler.
12665 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
12666 when we're running as a client.
12669 Changes in version 0.1.1.25 - 2006-11-04
12671 - When a client asks us to resolve (rather than connect to)
12672 an address, and we have a cached answer, give them the cached
12673 answer. Previously, we would give them no answer at all.
12674 - We were building exactly the wrong circuits when we predict
12675 hidden service requirements, meaning Tor would have to build all
12676 its circuits on demand.
12677 - If none of our live entry guards have a high uptime, but we
12678 require a guard with a high uptime, try adding a new guard before
12679 we give up on the requirement. This patch should make long-lived
12680 connections more stable on average.
12681 - When testing reachability of our DirPort, don't launch new
12682 tests when there's already one in progress -- unreachable
12683 servers were stacking up dozens of testing streams.
12685 o Security bugfixes:
12686 - When the user sends a NEWNYM signal, clear the client-side DNS
12687 cache too. Otherwise we continue to act on previous information.
12690 - Avoid a memory corruption bug when creating a hash table for
12692 - Avoid possibility of controller-triggered crash when misusing
12693 certain commands from a v0 controller on platforms that do not
12694 handle printf("%s",NULL) gracefully.
12695 - Avoid infinite loop on unexpected controller input.
12696 - Don't log spurious warnings when we see a circuit close reason we
12697 don't recognize; it's probably just from a newer version of Tor.
12698 - Add Vidalia to the OS X uninstaller script, so when we uninstall
12699 Tor/Privoxy we also uninstall Vidalia.
12702 Changes in version 0.1.2.3-alpha - 2006-10-29
12704 - Prepare for servers to publish descriptors less often: never
12705 discard a descriptor simply for being too old until either it is
12706 recommended by no authorities, or until we get a better one for
12707 the same router. Make caches consider retaining old recommended
12708 routers for even longer.
12709 - If most authorities set a BadExit flag for a server, clients
12710 don't think of it as a general-purpose exit. Clients only consider
12711 authorities that advertise themselves as listing bad exits.
12712 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
12713 headers for content, so that we can work better in the presence of
12714 caching HTTP proxies.
12715 - Allow authorities to list nodes as bad exits by fingerprint or by
12718 o Minor features, controller:
12719 - Add a REASON field to CIRC events; for backward compatibility, this
12720 field is sent only to controllers that have enabled the extended
12721 event format. Also, add additional reason codes to explain why
12722 a given circuit has been destroyed or truncated. (Patches from
12724 - Add a REMOTE_REASON field to extended CIRC events to tell the
12725 controller about why a remote OR told us to close a circuit.
12726 - Stream events also now have REASON and REMOTE_REASON fields,
12727 working much like those for circuit events.
12728 - There's now a GETINFO ns/... field so that controllers can ask Tor
12729 about the current status of a router.
12730 - A new event type "NS" to inform a controller when our opinion of
12731 a router's status has changed.
12732 - Add a GETINFO events/names and GETINFO features/names so controllers
12733 can tell which events and features are supported.
12734 - A new CLEARDNSCACHE signal to allow controllers to clear the
12735 client-side DNS cache without expiring circuits.
12737 o Security bugfixes:
12738 - When the user sends a NEWNYM signal, clear the client-side DNS
12739 cache too. Otherwise we continue to act on previous information.
12742 - Avoid sending junk to controllers or segfaulting when a controller
12743 uses EVENT_NEW_DESC with verbose nicknames.
12744 - Stop triggering asserts if the controller tries to extend hidden
12745 service circuits (reported by mwenge).
12746 - Avoid infinite loop on unexpected controller input.
12747 - When the controller does a "GETINFO network-status", tell it
12748 about even those routers whose descriptors are very old, and use
12749 long nicknames where appropriate.
12750 - Change NT service functions to be loaded on demand. This lets us
12751 build with MinGW without breaking Tor for Windows 98 users.
12752 - Do DirPort reachability tests less often, since a single test
12753 chews through many circuits before giving up.
12754 - In the hidden service example in torrc.sample, stop recommending
12755 esoteric and discouraged hidden service options.
12756 - When stopping an NT service, wait up to 10 sec for it to actually
12757 stop. Patch from Matt Edman; resolves bug 295.
12758 - Fix handling of verbose nicknames with ORCONN controller events:
12759 make them show up exactly when requested, rather than exactly when
12761 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
12762 printing a duplicate "$" in the keys we send (reported by mwenge).
12763 - Correctly set maximum connection limit on Cygwin. (This time
12765 - Try to detect Windows correctly when cross-compiling.
12766 - Detect the size of the routers file correctly even if it is
12767 corrupted (on systems without mmap) or not page-aligned (on systems
12768 with mmap). This bug was harmless.
12769 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
12770 to open a stream fails; now we do in more cases. This should
12771 make clients able to find a good exit faster in some cases, since
12772 unhandleable requests will now get an error rather than timing out.
12773 - Resolve two memory leaks when rebuilding the on-disk router cache
12774 (reported by fookoowa).
12775 - Clean up minor code warnings suggested by the MIPSpro C compiler,
12776 and reported by some Centos users.
12777 - Controller signals now work on non-Unix platforms that don't define
12778 SIGUSR1 and SIGUSR2 the way we expect.
12779 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
12780 values before failing, and always enables eventdns.
12781 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
12782 Try to fix this in configure.in by checking for most functions
12783 before we check for libevent.
12786 Changes in version 0.1.2.2-alpha - 2006-10-07
12788 - Make our async eventdns library on-by-default for Tor servers,
12789 and plan to deprecate the separate dnsworker threads.
12790 - Add server-side support for "reverse" DNS lookups (using PTR
12791 records so clients can determine the canonical hostname for a given
12792 IPv4 address). Only supported by servers using eventdns; servers
12793 now announce in their descriptors whether they support eventdns.
12794 - Specify and implement client-side SOCKS5 interface for reverse DNS
12795 lookups (see doc/socks-extensions.txt).
12796 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
12797 connect to directory servers through Tor. Previously, clients needed
12798 to find Tor exits to make private connections to directory servers.
12799 - Avoid choosing Exit nodes for entry or middle hops when the
12800 total bandwidth available from non-Exit nodes is much higher than
12801 the total bandwidth available from Exit nodes.
12802 - Workaround for name servers (like Earthlink's) that hijack failing
12803 DNS requests and replace the no-such-server answer with a "helpful"
12804 redirect to an advertising-driven search portal. Also work around
12805 DNS hijackers who "helpfully" decline to hijack known-invalid
12806 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
12807 lets you turn it off.
12808 - Send out a burst of long-range padding cells once we've established
12809 that we're reachable. Spread them over 4 circuits, so hopefully
12810 a few will be fast. This exercises our bandwidth and bootstraps
12811 us into the directory more quickly.
12813 o New/improved config options:
12814 - Add new config option "ResolvConf" to let the server operator
12815 choose an alternate resolve.conf file when using eventdns.
12816 - Add an "EnforceDistinctSubnets" option to control our "exclude
12817 servers on the same /16" behavior. It's still on by default; this
12818 is mostly for people who want to operate private test networks with
12819 all the machines on the same subnet.
12820 - If one of our entry guards is on the ExcludeNodes list, or the
12821 directory authorities don't think it's a good guard, treat it as
12822 if it were unlisted: stop using it as a guard, and throw it off
12823 the guards list if it stays that way for a long time.
12824 - Allow directory authorities to be marked separately as authorities
12825 for the v1 directory protocol, the v2 directory protocol, and
12826 as hidden service directories, to make it easier to retire old
12827 authorities. V1 authorities should set "HSAuthoritativeDir 1"
12828 to continue being hidden service authorities too.
12829 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
12831 o Minor features, controller:
12832 - Fix CIRC controller events so that controllers can learn the
12833 identity digests of non-Named servers used in circuit paths.
12834 - Let controllers ask for more useful identifiers for servers. Instead
12835 of learning identity digests for un-Named servers and nicknames
12836 for Named servers, the new identifiers include digest, nickname,
12837 and indication of Named status. Off by default; see control-spec.txt
12838 for more information.
12839 - Add a "getinfo address" controller command so it can display Tor's
12840 best guess to the user.
12841 - New controller event to alert the controller when our server
12842 descriptor has changed.
12843 - Give more meaningful errors on controller authentication failure.
12845 o Minor features, other:
12846 - When asked to resolve a hostname, don't use non-exit servers unless
12847 requested to do so. This allows servers with broken DNS to be
12848 useful to the network.
12849 - Divide eventdns log messages into warn and info messages.
12850 - Reserve the nickname "Unnamed" for routers that can't pick
12851 a hostname: any router can call itself Unnamed; directory
12852 authorities will never allocate Unnamed to any particular router;
12853 clients won't believe that any router is the canonical Unnamed.
12854 - Only include function names in log messages for info/debug messages.
12855 For notice/warn/err, the content of the message should be clear on
12856 its own, and printing the function name only confuses users.
12857 - Avoid some false positives during reachability testing: don't try
12858 to test via a server that's on the same /24 as us.
12859 - If we fail to build a circuit to an intended enclave, and it's
12860 not mandatory that we use that enclave, stop wanting it.
12861 - When eventdns is enabled, allow multithreaded builds on NetBSD and
12862 OpenBSD. (We had previously disabled threads on these platforms
12863 because they didn't have working thread-safe resolver functions.)
12865 o Major bugfixes, anonymity/security:
12866 - If a client asked for a server by name, and there's a named server
12867 in our network-status but we don't have its descriptor yet, we
12868 could return an unnamed server instead.
12869 - Fix NetBSD bug that could allow someone to force uninitialized RAM
12870 to be sent to a server's DNS resolver. This only affects NetBSD
12871 and other platforms that do not bounds-check tolower().
12872 - Reject (most) attempts to use Tor circuits with length one. (If
12873 many people start using Tor as a one-hop proxy, exit nodes become
12874 a more attractive target for compromise.)
12875 - Just because your DirPort is open doesn't mean people should be
12876 able to remotely teach you about hidden service descriptors. Now
12877 only accept rendezvous posts if you've got HSAuthoritativeDir set.
12879 o Major bugfixes, other:
12880 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
12881 - When a client asks the server to resolve (not connect to)
12882 an address, and it has a cached answer, give them the cached answer.
12883 Previously, the server would give them no answer at all.
12884 - Allow really slow clients to not hang up five minutes into their
12885 directory downloads (suggested by Adam J. Richter).
12886 - We were building exactly the wrong circuits when we anticipated
12887 hidden service requirements, meaning Tor would have to build all
12888 its circuits on demand.
12889 - Avoid crashing when we mmap a router cache file of size 0.
12890 - When testing reachability of our DirPort, don't launch new
12891 tests when there's already one in progress -- unreachable
12892 servers were stacking up dozens of testing streams.
12894 o Minor bugfixes, correctness:
12895 - If we're a directory mirror and we ask for "all" network status
12896 documents, we would discard status documents from authorities
12897 we don't recognize.
12898 - Avoid a memory corruption bug when creating a hash table for
12900 - Avoid controller-triggered crash when misusing certain commands
12901 from a v0 controller on platforms that do not handle
12902 printf("%s",NULL) gracefully.
12903 - Don't crash when a controller sends a third argument to an
12904 "extendcircuit" request.
12905 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12906 response; fix error code when "getinfo dir/status/" fails.
12907 - Avoid crash when telling controller stream-status and a stream
12909 - Patch from Adam Langley to fix assert() in eventdns.c.
12910 - Fix a debug log message in eventdns to say "X resolved to Y"
12911 instead of "X resolved to X".
12912 - Make eventdns give strings for DNS errors, not just error numbers.
12913 - Track unreachable entry guards correctly: don't conflate
12914 'unreachable by us right now' with 'listed as down by the directory
12915 authorities'. With the old code, if a guard was unreachable by
12916 us but listed as running, it would clog our guard list forever.
12917 - Behave correctly in case we ever have a network with more than
12918 2GB/s total advertised capacity.
12919 - Make TrackExitHosts case-insensitive, and fix the behavior of
12920 ".suffix" TrackExitHosts items to avoid matching in the middle of
12922 - Finally fix the openssl warnings from newer gccs that believe that
12923 ignoring a return value is okay, but casting a return value and
12924 then ignoring it is a sign of madness.
12925 - Prevent the contrib/exitlist script from printing the same
12926 result more than once.
12927 - Patch from Steve Hildrey: Generate network status correctly on
12928 non-versioning dirservers.
12929 - Don't listen to the X-Your-Address-Is hint if you did the lookup
12930 via Tor; otherwise you'll think you're the exit node's IP address.
12932 o Minor bugfixes, performance:
12933 - Two small performance improvements on parsing descriptors.
12934 - Major performance improvement on inserting descriptors: change
12935 algorithm from O(n^2) to O(n).
12936 - Make the common memory allocation path faster on machines where
12937 malloc(0) returns a pointer.
12938 - Start remembering X-Your-Address-Is directory hints even if you're
12939 a client, so you can become a server more smoothly.
12940 - Avoid duplicate entries on MyFamily line in server descriptor.
12942 o Packaging, features:
12943 - Remove architecture from OS X builds. The official builds are
12944 now universal binaries.
12945 - The Debian package now uses --verify-config when (re)starting,
12946 to distinguish configuration errors from other errors.
12947 - Update RPMs to require libevent 1.1b.
12949 o Packaging, bugfixes:
12950 - Patches so Tor builds with MinGW on Windows.
12951 - Patches so Tor might run on Cygwin again.
12952 - Resume building on non-gcc compilers and ancient gcc. Resume
12953 building with the -O0 compile flag. Resume building cleanly on
12955 - Run correctly on OS X platforms with case-sensitive filesystems.
12956 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
12957 - Add autoconf checks so Tor can build on Solaris x86 again.
12960 - Documented (and renamed) ServerDNSSearchDomains and
12961 ServerDNSResolvConfFile options.
12962 - Be clearer that the *ListenAddress directives can be repeated
12966 Changes in version 0.1.1.24 - 2006-09-29
12968 - Allow really slow clients to not hang up five minutes into their
12969 directory downloads (suggested by Adam J. Richter).
12970 - Fix major performance regression from 0.1.0.x: instead of checking
12971 whether we have enough directory information every time we want to
12972 do something, only check when the directory information has changed.
12973 This should improve client CPU usage by 25-50%.
12974 - Don't crash if, after a server has been running for a while,
12975 it can't resolve its hostname.
12978 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12979 - Don't crash when the controller receives a third argument to an
12980 "extendcircuit" request.
12981 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12982 response; fix error code when "getinfo dir/status/" fails.
12983 - Fix configure.in to not produce broken configure files with
12984 more recent versions of autoconf. Thanks to Clint for his auto*
12986 - Fix security bug on NetBSD that could allow someone to force
12987 uninitialized RAM to be sent to a server's DNS resolver. This
12988 only affects NetBSD and other platforms that do not bounds-check
12990 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12991 methods: these are known to be buggy.
12992 - If we're a directory mirror and we ask for "all" network status
12993 documents, we would discard status documents from authorities
12994 we don't recognize.
12997 Changes in version 0.1.2.1-alpha - 2006-08-27
12999 - Add "eventdns" async dns library from Adam Langley, tweaked to
13000 build on OSX and Windows. Only enabled if you pass the
13001 --enable-eventdns argument to configure.
13002 - Allow servers with no hostname or IP address to learn their
13003 IP address by asking the directory authorities. This code only
13004 kicks in when you would normally have exited with a "no address"
13005 error. Nothing's authenticated, so use with care.
13006 - Rather than waiting a fixed amount of time between retrying
13007 application connections, we wait only 5 seconds for the first,
13008 10 seconds for the second, and 15 seconds for each retry after
13009 that. Hopefully this will improve the expected user experience.
13010 - Patch from Tup to add support for transparent AP connections:
13011 this basically bundles the functionality of trans-proxy-tor
13012 into the Tor mainline. Now hosts with compliant pf/netfilter
13013 implementations can redirect TCP connections straight to Tor
13014 without diverting through SOCKS. Needs docs.
13015 - Busy directory servers save lots of memory by spooling server
13016 descriptors, v1 directories, and v2 networkstatus docs to buffers
13017 as needed rather than en masse. Also mmap the cached-routers
13018 files, so we don't need to keep the whole thing in memory too.
13019 - Automatically avoid picking more than one node from the same
13020 /16 network when constructing a circuit.
13021 - Revise and clean up the torrc.sample that we ship with; add
13022 a section for BandwidthRate and BandwidthBurst.
13025 - Split circuit_t into origin_circuit_t and or_circuit_t, and
13026 split connection_t into edge, or, dir, control, and base structs.
13027 These will save quite a bit of memory on busy servers, and they'll
13028 also help us track down bugs in the code and bugs in the spec.
13029 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
13030 or later. Log when we are doing this, so we can diagnose it when
13031 it fails. (Also, recommend libevent 1.1b for kqueue and
13032 win32 methods; deprecate libevent 1.0b harder; make libevent
13033 recommendation system saner.)
13034 - Start being able to build universal binaries on OS X (thanks
13036 - Export the default exit policy via the control port, so controllers
13037 don't need to guess what it is / will be later.
13038 - Add a man page entry for ProtocolWarnings.
13039 - Add TestVia config option to the man page.
13040 - Remove even more protocol-related warnings from Tor server logs,
13041 such as bad TLS handshakes and malformed begin cells.
13042 - Stop fetching descriptors if you're not a dir mirror and you
13043 haven't tried to establish any circuits lately. [This currently
13044 causes some dangerous behavior, because when you start up again
13045 you'll use your ancient server descriptors.]
13046 - New DirPort behavior: if you have your dirport set, you download
13047 descriptors aggressively like a directory mirror, whether or not
13048 your ORPort is set.
13049 - Get rid of the router_retry_connections notion. Now routers
13050 no longer try to rebuild long-term connections to directory
13051 authorities, and directory authorities no longer try to rebuild
13052 long-term connections to all servers. We still don't hang up
13053 connections in these two cases though -- we need to look at it
13054 more carefully to avoid flapping, and we likely need to wait til
13055 0.1.1.x is obsolete.
13056 - Drop compatibility with obsolete Tors that permit create cells
13057 to have the wrong circ_id_type.
13058 - Re-enable per-connection rate limiting. Get rid of the "OP
13059 bandwidth" concept. Lay groundwork for "bandwidth classes" --
13060 separate global buckets that apply depending on what sort of conn
13062 - Start publishing one minute or so after we find our ORPort
13063 to be reachable. This will help reduce the number of descriptors
13064 we have for ourselves floating around, since it's quite likely
13065 other things (e.g. DirPort) will change during that minute too.
13066 - Fork the v1 directory protocol into its own spec document,
13067 and mark dir-spec.txt as the currently correct (v2) spec.
13070 - When we find our DirPort to be reachable, publish a new descriptor
13071 so we'll tell the world (reported by pnx).
13072 - Publish a new descriptor after we hup/reload. This is important
13073 if our config has changed such that we'll want to start advertising
13074 our DirPort now, etc.
13075 - Allow Tor to start when RunAsDaemon is set but no logs are set.
13076 - When we have a state file we cannot parse, tell the user and
13077 move it aside. Now we avoid situations where the user starts
13078 Tor in 1904, Tor writes a state file with that timestamp in it,
13079 the user fixes her clock, and Tor refuses to start.
13080 - Fix configure.in to not produce broken configure files with
13081 more recent versions of autoconf. Thanks to Clint for his auto*
13083 - "tor --verify-config" now exits with -1(255) or 0 depending on
13084 whether the config options are bad or good.
13085 - Resolve bug 321 when using dnsworkers: append a period to every
13086 address we resolve at the exit node, so that we do not accidentally
13087 pick up local addresses, and so that failing searches are retried
13088 in the resolver search domains. (This is already solved for
13089 eventdns.) (This breaks Blossom servers for now.)
13090 - If we are using an exit enclave and we can't connect, e.g. because
13091 its webserver is misconfigured to not listen on localhost, then
13092 back off and try connecting from somewhere else before we fail.
13095 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
13096 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
13097 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
13098 when the IP address is mapped through MapAddress to a hostname.
13099 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
13100 useless IPv6 DNS resolves.
13101 - Patch suggested by Karsten Loesing: respond to SIGNAL command
13102 before we execute the signal, in case the signal shuts us down.
13103 - Clean up AllowInvalidNodes man page entry.
13104 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
13105 - Add more asserts to track down an assert error on a windows Tor
13106 server with connection_add being called with socket == -1.
13107 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
13108 - Fix misleading log messages: an entry guard that is "unlisted",
13109 as well as not known to be "down" (because we've never heard
13110 of it), is not therefore "up".
13111 - Remove code to special-case "-cvs" ending, since it has not
13112 actually mattered since 0.0.9.
13113 - Make our socks5 handling more robust to broken socks clients:
13114 throw out everything waiting on the buffer in between socks
13115 handshake phases, since they can't possibly (so the theory
13116 goes) have predicted what we plan to respond to them.
13119 Changes in version 0.1.1.23 - 2006-07-30
13121 - Fast Tor servers, especially exit nodes, were triggering asserts
13122 due to a bug in handling the list of pending DNS resolves. Some
13123 bugs still remain here; we're hunting them.
13124 - Entry guards could crash clients by sending unexpected input.
13125 - More fixes on reachability testing: if you find yourself reachable,
13126 then don't ever make any client requests (so you stop predicting
13127 circuits), then hup or have your clock jump, then later your IP
13128 changes, you won't think circuits are working, so you won't try to
13129 test reachability, so you won't publish.
13132 - Avoid a crash if the controller does a resetconf firewallports
13133 and then a setconf fascistfirewall=1.
13134 - Avoid an integer underflow when the dir authority decides whether
13135 a router is stable: we might wrongly label it stable, and compute
13136 a slightly wrong median stability, when a descriptor is published
13138 - Fix a place where we might trigger an assert if we can't build our
13139 own server descriptor yet.
13142 Changes in version 0.1.1.22 - 2006-07-05
13144 - Fix a big bug that was causing servers to not find themselves
13145 reachable if they changed IP addresses. Since only 0.1.1.22+
13146 servers can do reachability testing correctly, now we automatically
13147 make sure to test via one of these.
13148 - Fix to allow clients and mirrors to learn directory info from
13149 descriptor downloads that get cut off partway through.
13150 - Directory authorities had a bug in deciding if a newly published
13151 descriptor was novel enough to make everybody want a copy -- a few
13152 servers seem to be publishing new descriptors many times a minute.
13154 - Fix a rare bug that was causing some servers to complain about
13155 "closing wedged cpuworkers" and skip some circuit create requests.
13156 - Make the Exit flag in directory status documents actually work.
13159 Changes in version 0.1.1.21 - 2006-06-10
13160 o Crash and assert fixes from 0.1.1.20:
13161 - Fix a rare crash on Tor servers that have enabled hibernation.
13162 - Fix a seg fault on startup for Tor networks that use only one
13163 directory authority.
13164 - Fix an assert from a race condition that occurs on Tor servers
13165 while exiting, where various threads are trying to log that they're
13166 exiting, and delete the logs, at the same time.
13167 - Make our unit tests pass again on certain obscure platforms.
13170 - Add support for building SUSE RPM packages.
13171 - Speed up initial bootstrapping for clients: if we are making our
13172 first ever connection to any entry guard, then don't mark it down
13174 - When only one Tor server in the network is labelled as a guard,
13175 and we've already picked him, we would cycle endlessly picking him
13176 again, being unhappy about it, etc. Now we specifically exclude
13177 current guards when picking a new guard.
13178 - Servers send create cells more reliably after the TLS connection
13179 is established: we were sometimes forgetting to send half of them
13180 when we had more than one pending.
13181 - If we get a create cell that asks us to extend somewhere, but the
13182 Tor server there doesn't match the expected digest, we now send
13183 a destroy cell back, rather than silently doing nothing.
13184 - Make options->RedirectExit work again.
13185 - Make cookie authentication for the controller work again.
13186 - Stop being picky about unusual characters in the arguments to
13187 mapaddress. It's none of our business.
13188 - Add a new config option "TestVia" that lets you specify preferred
13189 middle hops to use for test circuits. Perhaps this will let me
13190 debug the reachability problems better.
13192 o Log / documentation fixes:
13193 - If we're a server and some peer has a broken TLS certificate, don't
13194 log about it unless ProtocolWarnings is set, i.e., we want to hear
13195 about protocol violations by others.
13196 - Fix spelling of VirtualAddrNetwork in man page.
13197 - Add a better explanation at the top of the autogenerated torrc file
13198 about what happened to our old torrc.
13201 Changes in version 0.1.1.20 - 2006-05-23
13203 - Downgrade a log severity where servers complain that they're
13205 - Avoid a compile warning on FreeBSD.
13206 - Remove string size limit on NEWDESC messages; solve bug 291.
13207 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
13208 more thoroughly when we're running on windows.
13211 Changes in version 0.1.1.19-rc - 2006-05-03
13213 - Regenerate our local descriptor if it's dirty and we try to use
13214 it locally (e.g. if it changes during reachability detection).
13215 - If we setconf our ORPort to 0, we continued to listen on the
13216 old ORPort and receive connections.
13217 - Avoid a second warning about machine/limits.h on Debian
13219 - Be willing to add our own routerinfo into the routerlist.
13220 Now authorities will include themselves in their directories
13221 and network-statuses.
13222 - Stop trying to upload rendezvous descriptors to every
13223 directory authority: only try the v1 authorities.
13224 - Servers no longer complain when they think they're not
13225 registered with the directory authorities. There were too many
13227 - Backport dist-rpm changes so rpms can be built without errors.
13230 - Implement an option, VirtualAddrMask, to set which addresses
13231 get handed out in response to mapaddress requests. This works
13232 around a bug in tsocks where 127.0.0.0/8 is never socksified.
13235 Changes in version 0.1.1.18-rc - 2006-04-10
13237 - Work harder to download live network-statuses from all the
13238 directory authorities we know about. Improve the threshold
13239 decision logic so we're more robust to edge cases.
13240 - When fetching rendezvous descriptors, we were willing to ask
13241 v2 authorities too, which would always return 404.
13244 - Stop listing down or invalid nodes in the v1 directory. This will
13245 reduce its bulk by about 1/3, and reduce load on directory
13247 - When deciding whether a router is Fast or Guard-worthy, consider
13248 his advertised BandwidthRate and not just the BandwidthCapacity.
13249 - No longer ship INSTALL and README files -- they are useless now.
13250 - Force rpmbuild to behave and honor target_cpu.
13251 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
13252 - Start to include translated versions of the tor-doc-*.html
13253 files, along with the screenshots. Still needs more work.
13254 - Start sending back 512 and 451 errors if mapaddress fails,
13255 rather than not sending anything back at all.
13256 - When we fail to bind or listen on an incoming or outgoing
13257 socket, we should close it before failing. otherwise we just
13258 leak it. (thanks to weasel for finding.)
13259 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
13260 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
13261 - Make NoPublish (even though deprecated) work again.
13262 - Fix a minor security flaw where a versioning auth dirserver
13263 could list a recommended version many times in a row to make
13264 clients more convinced that it's recommended.
13265 - Fix crash bug if there are two unregistered servers running
13266 with the same nickname, one of them is down, and you ask for
13267 them by nickname in your EntryNodes or ExitNodes. Also, try
13268 to pick the one that's running rather than an arbitrary one.
13269 - Fix an infinite loop we could hit if we go offline for too long.
13270 - Complain when we hit WSAENOBUFS on recv() or write() too.
13271 Perhaps this will help us hunt the bug.
13272 - If you're not a versioning dirserver, don't put the string
13273 "client-versions \nserver-versions \n" in your network-status.
13274 - Lower the minimum required number of file descriptors to 1000,
13275 so we can have some overhead for Valgrind on Linux, where the
13276 default ulimit -n is 1024.
13279 - Add tor.dizum.com as the fifth authoritative directory server.
13280 - Add a new config option FetchUselessDescriptors, off by default,
13281 for when you plan to run "exitlist" on your client and you want
13282 to know about even the non-running descriptors.
13285 Changes in version 0.1.1.17-rc - 2006-03-28
13287 - Clients and servers since 0.1.1.10-alpha have been expiring
13288 connections whenever they are idle for 5 minutes and they *do*
13289 have circuits on them. Oops. With this new version, clients will
13290 discard their previous entry guard choices and avoid choosing
13291 entry guards running these flawed versions.
13292 - Fix memory leak when uncompressing concatenated zlib streams. This
13293 was causing substantial leaks over time on Tor servers.
13294 - The v1 directory was including servers as much as 48 hours old,
13295 because that's how the new routerlist->routers works. Now only
13296 include them if they're 20 hours old or less.
13299 - Resume building on irix64, netbsd 2.0, etc.
13300 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
13302 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
13303 and it is confusing some users.
13304 - Mirrors stop caching the v1 directory so often.
13305 - Make the max number of old descriptors that a cache will hold
13306 rise with the number of directory authorities, so we can scale.
13307 - Change our win32 uname() hack to be more forgiving about what
13308 win32 versions it thinks it's found.
13311 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
13313 - When the controller's *setconf commands fail, collect an error
13314 message in a string and hand it back to the controller.
13315 - Make the v2 dir's "Fast" flag based on relative capacity, just
13316 like "Stable" is based on median uptime. Name everything in the
13317 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
13318 - Log server fingerprint on startup, so new server operators don't
13319 have to go hunting around their filesystem for it.
13320 - Return a robots.txt on our dirport to discourage google indexing.
13321 - Let the controller ask for GETINFO dir/status/foo so it can ask
13322 directly rather than connecting to the dir port. Only works when
13323 dirport is set for now.
13325 o New config options rather than constants in the code:
13326 - SocksTimeout: How long do we let a socks connection wait
13327 unattached before we fail it?
13328 - CircuitBuildTimeout: Cull non-open circuits that were born
13329 at least this many seconds ago.
13330 - CircuitIdleTimeout: Cull open clean circuits that were born
13331 at least this many seconds ago.
13334 Changes in version 0.1.1.16-rc - 2006-03-18
13335 o Bugfixes on 0.1.1.15-rc:
13336 - Fix assert when the controller asks to attachstream a connect-wait
13337 or resolve-wait stream.
13338 - Now do address rewriting when the controller asks us to attach
13339 to a particular circuit too. This will let Blossom specify
13340 "moria2.exit" without having to learn what moria2's IP address is.
13341 - Make the "tor --verify-config" command-line work again, so people
13342 can automatically check if their torrc will parse.
13343 - Authoritative dirservers no longer require an open connection from
13344 a server to consider him "reachable". We need this change because
13345 when we add new auth dirservers, old servers won't know not to
13347 - Let Tor build on Sun CC again.
13348 - Fix an off-by-one buffer size in dirserv.c that magically never
13349 hit our three authorities but broke sjmurdoch's own tor network.
13350 - If we as a directory mirror don't know of any v1 directory
13351 authorities, then don't try to cache any v1 directories.
13352 - Stop warning about unknown servers in our family when they are
13353 given as hex digests.
13354 - Stop complaining as quickly to the server operator that he
13355 hasn't registered his nickname/key binding.
13356 - Various cleanups so we can add new V2 Auth Dirservers.
13357 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
13358 reflect the updated flags in our v2 dir protocol.
13359 - Resume allowing non-printable characters for exit streams (both
13360 for connecting and for resolving). Now we tolerate applications
13361 that don't follow the RFCs. But continue to block malformed names
13364 o Bugfixes on 0.1.0.x:
13365 - Fix assert bug in close_logs(): when we close and delete logs,
13366 remove them all from the global "logfiles" list.
13367 - Fix minor integer overflow in calculating when we expect to use up
13368 our bandwidth allocation before hibernating.
13369 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
13370 there are multiple SSLs installed with different versions.
13371 - When we try to be a server and Address is not explicitly set and
13372 our hostname resolves to a private IP address, try to use an
13373 interface address if it has a public address. Now Windows machines
13374 that think of themselves as localhost can work by default.
13377 - Let the controller ask for GETINFO dir/server/foo so it can ask
13378 directly rather than connecting to the dir port.
13379 - Let the controller tell us about certain router descriptors
13380 that it doesn't want Tor to use in circuits. Implement
13381 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
13382 - New config option SafeSocks to reject all application connections
13383 using unsafe socks protocols. Defaults to off.
13386 Changes in version 0.1.1.15-rc - 2006-03-11
13387 o Bugfixes and cleanups:
13388 - When we're printing strings from the network, don't try to print
13389 non-printable characters. This protects us against shell escape
13390 sequence exploits, and also against attacks to fool humans into
13391 misreading their logs.
13392 - Fix a bug where Tor would fail to establish any connections if you
13393 left it off for 24 hours and then started it: we were happy with
13394 the obsolete network statuses, but they all referred to router
13395 descriptors that were too old to fetch, so we ended up with no
13396 valid router descriptors.
13397 - Fix a seg fault in the controller's "getinfo orconn-status"
13398 command while listing status on incoming handshaking connections.
13399 Introduce a status name "NEW" for these connections.
13400 - If we get a linelist or linelist_s config option from the torrc
13401 (e.g. ExitPolicy) and it has no value, warn and skip rather than
13402 silently resetting it to its default.
13403 - Don't abandon entry guards until they've been down or gone for
13405 - Cleaner and quieter log messages.
13408 - New controller signal NEWNYM that makes new application requests
13409 use clean circuits.
13410 - Add a new circuit purpose 'controller' to let the controller ask
13411 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
13412 controller command to let you specify the purpose if you're
13413 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
13414 command to let you change a circuit's purpose after it's been
13416 - Accept "private:*" in routerdesc exit policies; not generated yet
13417 because older Tors do not understand it.
13418 - Add BSD-style contributed startup script "rc.subr" from Peter
13422 Changes in version 0.1.1.14-alpha - 2006-02-20
13423 o Bugfixes on 0.1.1.x:
13424 - Don't die if we ask for a stdout or stderr log (even implicitly)
13425 and we're set to RunAsDaemon -- just warn.
13426 - We still had a few bugs in the OR connection rotation code that
13427 caused directory servers to slowly aggregate connections to other
13428 fast Tor servers. This time for sure!
13429 - Make log entries on Win32 include the name of the function again.
13430 - We were treating a pair of exit policies if they were equal even
13431 if one said accept and the other said reject -- causing us to
13432 not always publish a new descriptor since we thought nothing
13434 - Retry pending server downloads as well as pending networkstatus
13435 downloads when we unexpectedly get a socks request.
13436 - We were ignoring the IS_FAST flag in the directory status,
13437 meaning we were willing to pick trivial-bandwidth nodes for "fast"
13439 - If the controller's SAVECONF command fails (e.g. due to file
13440 permissions), let the controller know that it failed.
13443 - If we're trying to be a Tor server and running Windows 95/98/ME
13444 as a server, explain that we'll likely crash.
13445 - When we're a server, a client asks for an old-style directory,
13446 and our write bucket is empty, don't give it to him. This way
13447 small servers can continue to serve the directory *sometimes*,
13448 without getting overloaded.
13449 - Compress exit policies even more -- look for duplicate lines
13451 - Clients now honor the "guard" flag in the router status when
13452 picking entry guards, rather than looking at is_fast or is_stable.
13453 - Retain unrecognized lines in $DATADIR/state file, so that we can
13454 be forward-compatible.
13455 - Generate 18.0.0.0/8 address policy format in descs when we can;
13456 warn when the mask is not reducible to a bit-prefix.
13457 - Let the user set ControlListenAddress in the torrc. This can be
13458 dangerous, but there are some cases (like a secured LAN) where it
13460 - Split ReachableAddresses into ReachableDirAddresses and
13461 ReachableORAddresses, so we can restrict Dir conns to port 80
13462 and OR conns to port 443.
13463 - Now we can target arch and OS in rpm builds (contributed by
13464 Phobos). Also make the resulting dist-rpm filename match the
13466 - New config options to help controllers: FetchServerDescriptors
13467 and FetchHidServDescriptors for whether to fetch server
13468 info and hidserv info or let the controller do it, and
13469 PublishServerDescriptor and PublishHidServDescriptors.
13470 - Also let the controller set the __AllDirActionsPrivate config
13471 option if you want all directory fetches/publishes to happen via
13472 Tor (it assumes your controller bootstraps your circuits).
13475 Changes in version 0.1.0.17 - 2006-02-17
13476 o Crash bugfixes on 0.1.0.x:
13477 - When servers with a non-zero DirPort came out of hibernation,
13478 sometimes they would trigger an assert.
13480 o Other important bugfixes:
13481 - On platforms that don't have getrlimit (like Windows), we were
13482 artificially constraining ourselves to a max of 1024
13483 connections. Now just assume that we can handle as many as 15000
13484 connections. Hopefully this won't cause other problems.
13486 o Backported features:
13487 - When we're a server, a client asks for an old-style directory,
13488 and our write bucket is empty, don't give it to him. This way
13489 small servers can continue to serve the directory *sometimes*,
13490 without getting overloaded.
13491 - Whenever you get a 503 in response to a directory fetch, try
13492 once more. This will become important once servers start sending
13493 503's whenever they feel busy.
13494 - Fetch a new directory every 120 minutes, not every 40 minutes.
13495 Now that we have hundreds of thousands of users running the old
13496 directory algorithm, it's starting to hurt a lot.
13497 - Bump up the period for forcing a hidden service descriptor upload
13498 from 20 minutes to 1 hour.
13501 Changes in version 0.1.1.13-alpha - 2006-02-09
13502 o Crashes in 0.1.1.x:
13503 - When you tried to setconf ORPort via the controller, Tor would
13504 crash. So people using TorCP to become a server were sad.
13505 - Solve (I hope) the stack-smashing bug that we were seeing on fast
13506 servers. The problem appears to be something do with OpenSSL's
13507 random number generation, or how we call it, or something. Let me
13508 know if the crashes continue.
13509 - Turn crypto hardware acceleration off by default, until we find
13510 somebody smart who can test it for us. (It appears to produce
13511 seg faults in at least some cases.)
13512 - Fix a rare assert error when we've tried all intro points for
13513 a hidden service and we try fetching the service descriptor again:
13514 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
13517 - Fix a major load balance bug: we were round-robining in 16 KB
13518 chunks, and servers with bandwidthrate of 20 KB, while downloading
13519 a 600 KB directory, would starve their other connections. Now we
13520 try to be a bit more fair.
13521 - Dir authorities and mirrors were never expiring the newest
13522 descriptor for each server, causing memory and directory bloat.
13523 - Fix memory-bloating and connection-bloating bug on servers: We
13524 were never closing any connection that had ever had a circuit on
13525 it, because we were checking conn->n_circuits == 0, yet we had a
13526 bug that let it go negative.
13527 - Make Tor work using squid as your http proxy again -- squid
13528 returns an error if you ask for a URL that's too long, and it uses
13529 a really generic error message. Plus, many people are behind a
13530 transparent squid so they don't even realize it.
13531 - On platforms that don't have getrlimit (like Windows), we were
13532 artificially constraining ourselves to a max of 1024
13533 connections. Now just assume that we can handle as many as 15000
13534 connections. Hopefully this won't cause other problems.
13535 - Add a new config option ExitPolicyRejectPrivate which defaults to
13536 1. This means all exit policies will begin with rejecting private
13537 addresses, unless the server operator explicitly turns it off.
13540 - Clients no longer download descriptors for non-running
13542 - Before we add new directory authorities, we should make it
13543 clear that only v1 authorities should receive/publish hidden
13544 service descriptors.
13547 - As soon as we've fetched some more directory info, immediately
13548 try to download more server descriptors. This way we don't have
13549 a 10 second pause during initial bootstrapping.
13550 - Remove even more loud log messages that the server operator can't
13552 - When we're running an obsolete or un-recommended version, make
13553 the log message more clear about what the problem is and what
13554 versions *are* still recommended.
13555 - Provide a more useful warn message when our onion queue gets full:
13556 the CPU is too slow or the exit policy is too liberal.
13557 - Don't warn when we receive a 503 from a dirserver/cache -- this
13558 will pave the way for them being able to refuse if they're busy.
13559 - When we fail to bind a listener, try to provide a more useful
13560 log message: e.g., "Is Tor already running?"
13561 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
13562 Goldberg can prove things about our handshake protocol more
13564 - MaxConn has been obsolete for a while now. Document the ConnLimit
13565 config option, which is a *minimum* number of file descriptors
13566 that must be available else Tor refuses to start.
13567 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
13568 if you log to syslog and want something other than LOG_DAEMON.
13569 - Make dirservers generate a separate "guard" flag to mean,
13570 "would make a good entry guard". Make clients parse it and vote
13571 on it. Not used by clients yet.
13572 - Implement --with-libevent-dir option to ./configure. Also, improve
13573 search techniques to find libevent, and use those for openssl too.
13574 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
13575 - Only start testing reachability once we've established a
13576 circuit. This will make startup on dirservers less noisy.
13577 - Don't try to upload hidden service descriptors until we have
13578 established a circuit.
13579 - Fix the controller's "attachstream 0" command to treat conn like
13580 it just connected, doing address remapping, handling .exit and
13581 .onion idioms, and so on. Now we're more uniform in making sure
13582 that the controller hears about new and closing connections.
13585 Changes in version 0.1.1.12-alpha - 2006-01-11
13586 o Bugfixes on 0.1.1.x:
13587 - The fix to close duplicate server connections was closing all
13588 Tor client connections if they didn't establish a circuit
13589 quickly enough. Oops.
13590 - Fix minor memory issue (double-free) that happened on exit.
13592 o Bugfixes on 0.1.0.x:
13593 - Tor didn't warn when it failed to open a log file.
13596 Changes in version 0.1.1.11-alpha - 2006-01-10
13597 o Crashes in 0.1.1.x:
13598 - Include all the assert/crash fixes from 0.1.0.16.
13599 - If you start Tor and then quit very quickly, there were some
13600 races that tried to free things that weren't allocated yet.
13601 - Fix a rare memory stomp if you're running hidden services.
13602 - Fix segfault when specifying DirServer in config without nickname.
13603 - Fix a seg fault when you finish connecting to a server but at
13604 that moment you dump his server descriptor.
13605 - Extendcircuit and Attachstream controller commands would
13606 assert/crash if you don't give them enough arguments.
13607 - Fix an assert error when we're out of space in the connection_list
13608 and we try to post a hidden service descriptor (reported by weasel).
13609 - If you specify a relative torrc path and you set RunAsDaemon in
13610 your torrc, then it chdir()'s to the new directory. If you HUP,
13611 it tries to load the new torrc location, fails, and exits.
13612 The fix: no longer allow a relative path to torrc using -f.
13615 - Implement "entry guards": automatically choose a handful of entry
13616 nodes and stick with them for all circuits. Only pick new guards
13617 when the ones you have are unsuitable, and if the old guards
13618 become suitable again, switch back. This will increase security
13619 dramatically against certain end-point attacks. The EntryNodes
13620 config option now provides some hints about which entry guards you
13621 want to use most; and StrictEntryNodes means to only use those.
13622 - New directory logic: download by descriptor digest, not by
13623 fingerprint. Caches try to download all listed digests from
13624 authorities; clients try to download "best" digests from caches.
13625 This avoids partitioning and isolating attacks better.
13626 - Make the "stable" router flag in network-status be the median of
13627 the uptimes of running valid servers, and make clients pay
13628 attention to the network-status flags. Thus the cutoff adapts
13629 to the stability of the network as a whole, making IRC, IM, etc
13630 connections more reliable.
13633 - Tor servers with dynamic IP addresses were needing to wait 18
13634 hours before they could start doing reachability testing using
13635 the new IP address and ports. This is because they were using
13636 the internal descriptor to learn what to test, yet they were only
13637 rebuilding the descriptor once they decided they were reachable.
13638 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
13639 to download certain server descriptors, throw them away, and then
13640 fetch them again after 30 minutes. Now mirrors throw away these
13641 server descriptors so clients can't get them.
13642 - We were leaving duplicate connections to other ORs open for a week,
13643 rather than closing them once we detect a duplicate. This only
13644 really affected authdirservers, but it affected them a lot.
13645 - Spread the authdirservers' reachability testing over the entire
13646 testing interval, so we don't try to do 500 TLS's at once every
13650 - If the network is down, and we try to connect to a conn because
13651 we have a circuit in mind, and we timeout (30 seconds) because the
13652 network never answers, we were expiring the circuit, but we weren't
13653 obsoleting the connection or telling the entry_guards functions.
13654 - Some Tor servers process billions of cells per day. These statistics
13655 need to be uint64_t's.
13656 - Check for integer overflows in more places, when adding elements
13657 to smartlists. This could possibly prevent a buffer overflow
13658 on malicious huge inputs. I don't see any, but I haven't looked
13660 - ReachableAddresses kept growing new "reject *:*" lines on every
13662 - When you "setconf log" via the controller, it should remove all
13663 logs. We were automatically adding back in a "log notice stdout".
13664 - Newly bootstrapped Tor networks couldn't establish hidden service
13665 circuits until they had nodes with high uptime. Be more tolerant.
13666 - We were marking servers down when they could not answer every piece
13667 of the directory request we sent them. This was far too harsh.
13668 - Fix the torify (tsocks) config file to not use Tor for localhost
13670 - Directory authorities now go to the proper authority when asking for
13671 a networkstatus, even when they want a compressed one.
13672 - Fix a harmless bug that was causing Tor servers to log
13673 "Got an end because of misc error, but we're not an AP. Closing."
13674 - Authorities were treating their own descriptor changes as cosmetic,
13675 meaning the descriptor available in the network-status and the
13676 descriptor that clients downloaded were different.
13677 - The OS X installer was adding a symlink for tor_resolve but
13678 the binary was called tor-resolve (reported by Thomas Hardly).
13679 - Workaround a problem with some http proxies where they refuse GET
13680 requests that specify "Content-Length: 0" (reported by Adrian).
13681 - Fix wrong log message when you add a "HiddenServiceNodes" config
13682 line without any HiddenServiceDir line (reported by Chris Thomas).
13685 - Write the TorVersion into the state file so we have a prayer of
13686 keeping forward and backward compatibility.
13687 - Revive the FascistFirewall config option rather than eliminating it:
13688 now it's a synonym for ReachableAddresses *:80,*:443.
13689 - Clients choose directory servers from the network status lists,
13690 not from their internal list of router descriptors. Now they can
13691 go to caches directly rather than needing to go to authorities
13693 - Directory authorities ignore router descriptors that have only
13694 cosmetic differences: do this for 0.1.0.x servers now too.
13695 - Add a new flag to network-status indicating whether the server
13696 can answer v2 directory requests too.
13697 - Authdirs now stop whining so loudly about bad descriptors that
13698 they fetch from other dirservers. So when there's a log complaint,
13699 it's for sure from a freshly uploaded descriptor.
13700 - Reduce memory requirements in our structs by changing the order
13702 - There used to be two ways to specify your listening ports in a
13703 server descriptor: on the "router" line and with a separate "ports"
13704 line. Remove support for the "ports" line.
13705 - New config option "AuthDirRejectUnlisted" for auth dirservers as
13706 a panic button: if we get flooded with unusable servers we can
13707 revert to only listing servers in the approved-routers file.
13708 - Auth dir servers can now mark a fingerprint as "!reject" or
13709 "!invalid" in the approved-routers file (as its nickname), to
13710 refuse descriptors outright or include them but marked as invalid.
13711 - Servers store bandwidth history across restarts/crashes.
13712 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
13713 get a better idea of why their circuits failed. Not used yet.
13714 - Directory mirrors now cache up to 16 unrecognized network-status
13715 docs. Now we can add new authdirservers and they'll be cached too.
13716 - When picking a random directory, prefer non-authorities if any
13718 - New controller option "getinfo desc/all-recent" to fetch the
13719 latest server descriptor for every router that Tor knows about.
13722 Changes in version 0.1.0.16 - 2006-01-02
13723 o Crash bugfixes on 0.1.0.x:
13724 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13725 corrupting the heap, losing FDs, or crashing when we need to resize
13726 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13727 - It turns out sparc64 platforms crash on unaligned memory access
13728 too -- so detect and avoid this.
13729 - Handle truncated compressed data correctly (by detecting it and
13731 - Fix possible-but-unlikely free(NULL) in control.c.
13732 - When we were closing connections, there was a rare case that
13733 stomped on memory, triggering seg faults and asserts.
13734 - Avoid potential infinite recursion when building a descriptor. (We
13735 don't know that it ever happened, but better to fix it anyway.)
13736 - We were neglecting to unlink marked circuits from soon-to-close OR
13737 connections, which caused some rare scribbling on freed memory.
13738 - Fix a memory stomping race bug when closing the joining point of two
13739 rendezvous circuits.
13740 - Fix an assert in time parsing found by Steven Murdoch.
13742 o Other bugfixes on 0.1.0.x:
13743 - When we're doing reachability testing, provide more useful log
13744 messages so the operator knows what to expect.
13745 - Do not check whether DirPort is reachable when we are suppressing
13746 advertising it because of hibernation.
13747 - When building with -static or on Solaris, we sometimes needed -ldl.
13748 - When we're deciding whether a stream has enough circuits around
13749 that can handle it, count the freshly dirty ones and not the ones
13750 that are so dirty they won't be able to handle it.
13751 - When we're expiring old circuits, we had a logic error that caused
13752 us to close new rendezvous circuits rather than old ones.
13753 - Give a more helpful log message when you try to change ORPort via
13754 the controller: you should upgrade Tor if you want that to work.
13755 - We were failing to parse Tor versions that start with "Tor ".
13756 - Tolerate faulty streams better: when a stream fails for reason
13757 exitpolicy, stop assuming that the router is lying about his exit
13758 policy. When a stream fails for reason misc, allow it to retry just
13759 as if it was resolvefailed. When a stream has failed three times,
13760 reset its failure count so we can try again and get all three tries.
13763 Changes in version 0.1.1.10-alpha - 2005-12-11
13764 o Correctness bugfixes on 0.1.0.x:
13765 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13766 corrupting the heap, losing FDs, or crashing when we need to resize
13767 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13768 - Stop doing the complex voodoo overkill checking for insecure
13769 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
13770 - When we were closing connections, there was a rare case that
13771 stomped on memory, triggering seg faults and asserts.
13772 - We were neglecting to unlink marked circuits from soon-to-close OR
13773 connections, which caused some rare scribbling on freed memory.
13774 - When we're deciding whether a stream has enough circuits around
13775 that can handle it, count the freshly dirty ones and not the ones
13776 that are so dirty they won't be able to handle it.
13777 - Recover better from TCP connections to Tor servers that are
13778 broken but don't tell you (it happens!); and rotate TLS
13779 connections once a week.
13780 - When we're expiring old circuits, we had a logic error that caused
13781 us to close new rendezvous circuits rather than old ones.
13782 - Fix a scary-looking but apparently harmless bug where circuits
13783 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
13784 servers, and never switch to state CIRCUIT_STATE_OPEN.
13785 - When building with -static or on Solaris, we sometimes needed to
13787 - Give a useful message when people run Tor as the wrong user,
13788 rather than telling them to start chowning random directories.
13789 - We were failing to inform the controller about new .onion streams.
13791 o Security bugfixes on 0.1.0.x:
13792 - Refuse server descriptors if the fingerprint line doesn't match
13793 the included identity key. Tor doesn't care, but other apps (and
13794 humans) might actually be trusting the fingerprint line.
13795 - We used to kill the circuit when we receive a relay command we
13796 don't recognize. Now we just drop it.
13797 - Start obeying our firewall options more rigorously:
13798 . If we can't get to a dirserver directly, try going via Tor.
13799 . Don't ever try to connect (as a client) to a place our
13800 firewall options forbid.
13801 . If we specify a proxy and also firewall options, obey the
13802 firewall options even when we're using the proxy: some proxies
13803 can only proxy to certain destinations.
13804 - Fix a bug found by Lasse Overlier: when we were making internal
13805 circuits (intended to be cannibalized later for rendezvous and
13806 introduction circuits), we were picking them so that they had
13807 useful exit nodes. There was no need for this, and it actually
13808 aids some statistical attacks.
13809 - Start treating internal circuits and exit circuits separately.
13810 It's important to keep them separate because internal circuits
13811 have their last hops picked like middle hops, rather than like
13812 exit hops. So exiting on them will break the user's expectations.
13814 o Bugfixes on 0.1.1.x:
13815 - Take out the mis-feature where we tried to detect IP address
13816 flapping for people with DynDNS, and chose not to upload a new
13817 server descriptor sometimes.
13818 - Try to be compatible with OpenSSL 0.9.6 again.
13819 - Log fix: when the controller is logging about .onion addresses,
13820 sometimes it didn't include the ".onion" part of the address.
13821 - Don't try to modify options->DirServers internally -- if the
13822 user didn't specify any, just add the default ones directly to
13823 the trusted dirserver list. This fixes a bug where people running
13824 controllers would use SETCONF on some totally unrelated config
13825 option, and Tor would start yelling at them about changing their
13827 - Let the controller's redirectstream command specify a port, in
13828 case the controller wants to change that too.
13829 - When we requested a pile of server descriptors, we sometimes
13830 accidentally launched a duplicate request for the first one.
13831 - Bugfix for trackhostexits: write down the fingerprint of the
13832 chosen exit, not its nickname, because the chosen exit might not
13834 - When parsing foo.exit, if foo is unknown, and we are leaving
13835 circuits unattached, set the chosen_exit field and leave the
13836 address empty. This matters because controllers got confused
13838 - Directory authorities no longer try to download server
13839 descriptors that they know they will reject.
13841 o Features and updates:
13842 - Replace balanced trees with hash tables: this should make stuff
13843 significantly faster.
13844 - Resume using the AES counter-mode implementation that we ship,
13845 rather than OpenSSL's. Ours is significantly faster.
13846 - Many other CPU and memory improvements.
13847 - Add a new config option FastFirstHopPK (on by default) so clients
13848 do a trivial crypto handshake for their first hop, since TLS has
13849 already taken care of confidentiality and authentication.
13850 - Add a new config option TestSocks so people can see if their
13851 applications are using socks4, socks4a, socks5-with-ip, or
13852 socks5-with-hostname. This way they don't have to keep mucking
13853 with tcpdump and wondering if something got cached somewhere.
13854 - Warn when listening on a public address for socks. I suspect a
13855 lot of people are setting themselves up as open socks proxies,
13856 and they have no idea that jerks on the Internet are using them,
13857 since they simply proxy the traffic into the Tor network.
13858 - Add "private:*" as an alias in configuration for policies. Now
13859 you can simplify your exit policy rather than needing to list
13860 every single internal or nonroutable network space.
13861 - Add a new controller event type that allows controllers to get
13862 all server descriptors that were uploaded to a router in its role
13863 as authoritative dirserver.
13864 - Start shipping socks-extensions.txt, tor-doc-unix.html,
13865 tor-doc-server.html, and stylesheet.css in the tarball.
13866 - Stop shipping tor-doc.html in the tarball.
13869 Changes in version 0.1.1.9-alpha - 2005-11-15
13870 o Usability improvements:
13871 - Start calling it FooListenAddress rather than FooBindAddress,
13872 since few of our users know what it means to bind an address
13874 - Reduce clutter in server logs. We're going to try to make
13875 them actually usable now. New config option ProtocolWarnings that
13876 lets you hear about how _other Tors_ are breaking the protocol. Off
13878 - Divide log messages into logging domains. Once we put some sort
13879 of interface on this, it will let people looking at more verbose
13880 log levels specify the topics they want to hear more about.
13881 - Make directory servers return better http 404 error messages
13882 instead of a generic "Servers unavailable".
13883 - Check for even more Windows version flags when writing the platform
13884 string in server descriptors, and note any we don't recognize.
13885 - Clean up more of the OpenSSL memory when exiting, so we can detect
13886 memory leaks better.
13887 - Make directory authorities be non-versioning, non-naming by
13888 default. Now we can add new directory servers without requiring
13889 their operators to pay close attention.
13890 - When logging via syslog, include the pid whenever we provide
13891 a log entry. Suggested by Todd Fries.
13893 o Performance improvements:
13894 - Directory servers now silently throw away new descriptors that
13895 haven't changed much if the timestamps are similar. We do this to
13896 tolerate older Tor servers that upload a new descriptor every 15
13897 minutes. (It seemed like a good idea at the time.)
13898 - Inline bottleneck smartlist functions; use fast versions by default.
13899 - Add a "Map from digest to void*" abstraction digestmap_t so we
13900 can do less hex encoding/decoding. Use it in router_get_by_digest()
13901 to resolve a performance bottleneck.
13902 - Allow tor_gzip_uncompress to extract as much as possible from
13903 truncated compressed data. Try to extract as many
13904 descriptors as possible from truncated http responses (when
13905 DIR_PURPOSE_FETCH_ROUTERDESC).
13906 - Make circ->onionskin a pointer, not a static array. moria2 was using
13907 125000 circuit_t's after it had been up for a few weeks, which
13908 translates to 20+ megs of wasted space.
13909 - The private half of our EDH handshake keys are now chosen out
13910 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
13912 o Security improvements:
13913 - Start making directory caches retain old routerinfos, so soon
13914 clients can start asking by digest of descriptor rather than by
13915 fingerprint of server.
13916 - Add half our entropy from RAND_poll in OpenSSL. This knows how
13917 to use egd (if present), openbsd weirdness (if present), vms/os2
13918 weirdness (if we ever port there), and more in the future.
13920 o Bugfixes on 0.1.0.x:
13921 - Do round-robin writes of at most 16 kB per write. This might be
13922 more fair on loaded Tor servers, and it might resolve our Windows
13923 crash bug. It might also slow things down.
13924 - Our TLS handshakes were generating a single public/private
13925 keypair for the TLS context, rather than making a new one for
13926 each new connections. Oops. (But we were still rotating them
13927 periodically, so it's not so bad.)
13928 - When we were cannibalizing a circuit with a particular exit
13929 node in mind, we weren't checking to see if that exit node was
13930 already present earlier in the circuit. Oops.
13931 - When a Tor server's IP changes (e.g. from a dyndns address),
13932 upload a new descriptor so clients will learn too.
13933 - Really busy servers were keeping enough circuits open on stable
13934 connections that they were wrapping around the circuit_id
13935 space. (It's only two bytes.) This exposed a bug where we would
13936 feel free to reuse a circuit_id even if it still exists but has
13937 been marked for close. Try to fix this bug. Some bug remains.
13938 - If we would close a stream early (e.g. it asks for a .exit that
13939 we know would refuse it) but the LeaveStreamsUnattached config
13940 option is set by the controller, then don't close it.
13942 o Bugfixes on 0.1.1.8-alpha:
13943 - Fix a big pile of memory leaks, some of them serious.
13944 - Do not try to download a routerdesc if we would immediately reject
13946 - Resume inserting a newline between all router descriptors when
13947 generating (old style) signed directories, since our spec says
13949 - When providing content-type application/octet-stream for
13950 server descriptors using .z, we were leaving out the
13951 content-encoding header. Oops. (Everything tolerated this just
13952 fine, but that doesn't mean we need to be part of the problem.)
13953 - Fix a potential seg fault in getconf and getinfo using version 1
13954 of the controller protocol.
13955 - Avoid crash: do not check whether DirPort is reachable when we
13956 are suppressing it because of hibernation.
13957 - Make --hash-password not crash on exit.
13960 Changes in version 0.1.1.8-alpha - 2005-10-07
13961 o New features (major):
13962 - Clients don't download or use the directory anymore. Now they
13963 download and use network-statuses from the trusted dirservers,
13964 and fetch individual server descriptors as needed from mirrors.
13965 See dir-spec.txt for all the gory details.
13966 - Be more conservative about whether to advertise our DirPort.
13967 The main change is to not advertise if we're running at capacity
13968 and either a) we could hibernate or b) our capacity is low and
13969 we're using a default DirPort.
13970 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
13972 o New features (minor):
13973 - Try to be smart about when to retry network-status and
13974 server-descriptor fetches. Still needs some tuning.
13975 - Stop parsing, storing, or using running-routers output (but
13976 mirrors still cache and serve it).
13977 - Consider a threshold of versioning dirservers (dirservers who have
13978 an opinion about which Tor versions are still recommended) before
13979 deciding whether to warn the user that he's obsolete.
13980 - Dirservers can now reject/invalidate by key and IP, with the
13981 config options "AuthDirInvalid" and "AuthDirReject". This is
13982 useful since currently we automatically list servers as running
13983 and usable even if we know they're jerks.
13984 - Provide dire warnings to any users who set DirServer; move it out
13985 of torrc.sample and into torrc.complete.
13986 - Add MyFamily to torrc.sample in the server section.
13987 - Add nicknames to the DirServer line, so we can refer to them
13988 without requiring all our users to memorize their IP addresses.
13989 - When we get an EOF or a timeout on a directory connection, note
13990 how many bytes of serverdesc we are dropping. This will help
13991 us determine whether it is smart to parse incomplete serverdesc
13993 - Add a new function to "change pseudonyms" -- that is, to stop
13994 using any currently-dirty circuits for new streams, so we don't
13995 link new actions to old actions. Currently it's only called on
13996 HUP (or SIGNAL RELOAD).
13997 - On sighup, if UseHelperNodes changed to 1, use new circuits.
13998 - Start using RAND_bytes rather than RAND_pseudo_bytes from
13999 OpenSSL. Also, reseed our entropy every hour, not just at
14000 startup. And entropy in 512-bit chunks, not 160-bit chunks.
14002 o Fixes on 0.1.1.7-alpha:
14003 - Nobody ever implemented EVENT_ADDRMAP for control protocol
14004 version 0, so don't let version 0 controllers ask for it.
14005 - If you requested something with too many newlines via the
14006 v1 controller protocol, you could crash tor.
14007 - Fix a number of memory leaks, including some pretty serious ones.
14008 - Re-enable DirPort testing again, so Tor servers will be willing
14009 to advertise their DirPort if it's reachable.
14010 - On TLS handshake, only check the other router's nickname against
14011 its expected nickname if is_named is set.
14013 o Fixes forward-ported from 0.1.0.15:
14014 - Don't crash when we don't have any spare file descriptors and we
14015 try to spawn a dns or cpu worker.
14016 - Make the numbers in read-history and write-history into uint64s,
14017 so they don't overflow and publish negatives in the descriptor.
14019 o Fixes on 0.1.0.x:
14020 - For the OS X package's modified privoxy config file, comment
14021 out the "logfile" line so we don't log everything passed
14023 - We were whining about using socks4 or socks5-with-local-lookup
14024 even when it's an IP in the "virtual" range we designed exactly
14026 - We were leaking some memory every time the client changes IPs.
14027 - Never call free() on tor_malloc()d memory. This will help us
14028 use dmalloc to detect memory leaks.
14029 - Check for named servers when looking them up by nickname;
14030 warn when we'recalling a non-named server by its nickname;
14031 don't warn twice about the same name.
14032 - Try to list MyFamily elements by key, not by nickname, and warn
14033 if we've not heard of the server.
14034 - Make windows platform detection (uname equivalent) smarter.
14035 - It turns out sparc64 doesn't like unaligned access either.
14038 Changes in version 0.1.0.15 - 2005-09-23
14039 o Bugfixes on 0.1.0.x:
14040 - Reject ports 465 and 587 (spam targets) in default exit policy.
14041 - Don't crash when we don't have any spare file descriptors and we
14042 try to spawn a dns or cpu worker.
14043 - Get rid of IgnoreVersion undocumented config option, and make us
14044 only warn, never exit, when we're running an obsolete version.
14045 - Don't try to print a null string when your server finds itself to
14046 be unreachable and the Address config option is empty.
14047 - Make the numbers in read-history and write-history into uint64s,
14048 so they don't overflow and publish negatives in the descriptor.
14049 - Fix a minor memory leak in smartlist_string_remove().
14050 - We were only allowing ourselves to upload a server descriptor at
14051 most every 20 minutes, even if it changed earlier than that.
14052 - Clean up log entries that pointed to old URLs.
14055 Changes in version 0.1.1.7-alpha - 2005-09-14
14056 o Fixes on 0.1.1.6-alpha:
14057 - Exit servers were crashing when people asked them to make a
14058 connection to an address not in their exit policy.
14059 - Looking up a non-existent stream for a v1 control connection would
14061 - Fix a seg fault if we ask a dirserver for a descriptor by
14062 fingerprint but he doesn't know about him.
14063 - SETCONF was appending items to linelists, not clearing them.
14064 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
14065 out and refuse the setconf if it would fail.
14066 - Downgrade the dirserver log messages when whining about
14070 - Add Peter Palfrader's check-tor script to tor/contrib/
14071 It lets you easily check whether a given server (referenced by
14072 nickname) is reachable by you.
14073 - Numerous changes to move towards client-side v2 directories. Not
14076 o Fixes on 0.1.0.x:
14077 - If the user gave tor an odd number of command-line arguments,
14078 we were silently ignoring the last one. Now we complain and fail.
14079 [This wins the oldest-bug prize -- this bug has been present since
14080 November 2002, as released in Tor 0.0.0.]
14081 - Do not use unaligned memory access on alpha, mips, or mipsel.
14082 It *works*, but is very slow, so we treat them as if it doesn't.
14083 - Retry directory requests if we fail to get an answer we like
14084 from a given dirserver (we were retrying before, but only if
14085 we fail to connect).
14086 - When writing the RecommendedVersions line, sort them first.
14087 - When the client asked for a rendezvous port that the hidden
14088 service didn't want to provide, we were sending an IP address
14089 back along with the end cell. Fortunately, it was zero. But stop
14091 - Correct "your server is reachable" log entries to indicate that
14092 it was self-testing that told us so.
14095 Changes in version 0.1.1.6-alpha - 2005-09-09
14096 o Fixes on 0.1.1.5-alpha:
14097 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
14098 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
14099 - Fix bug with tor_memmem finding a match at the end of the string.
14100 - Make unit tests run without segfaulting.
14101 - Resolve some solaris x86 compile warnings.
14102 - Handle duplicate lines in approved-routers files without warning.
14103 - Fix bug where as soon as a server refused any requests due to his
14104 exit policy (e.g. when we ask for localhost and he tells us that's
14105 127.0.0.1 and he won't do it), we decided he wasn't obeying his
14106 exit policy using him for any exits.
14107 - Only do openssl hardware accelerator stuff if openssl version is
14110 o New controller features/fixes:
14111 - Add a "RESETCONF" command so you can set config options like
14112 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
14113 a config option in the torrc with no value, then it clears it
14114 entirely (rather than setting it to its default).
14115 - Add a "GETINFO config-file" to tell us where torrc is.
14116 - Avoid sending blank lines when GETINFO replies should be empty.
14117 - Add a QUIT command for the controller (for using it manually).
14118 - Fix a bug in SAVECONF that was adding default dirservers and
14119 other redundant entries to the torrc file.
14121 o Start on the new directory design:
14122 - Generate, publish, cache, serve new network-status format.
14123 - Publish individual descriptors (by fingerprint, by "all", and by
14125 - Publish client and server recommended versions separately.
14126 - Allow tor_gzip_uncompress() to handle multiple concatenated
14127 compressed strings. Serve compressed groups of router
14128 descriptors. The compression logic here could be more
14130 - Distinguish v1 authorities (all currently trusted directories)
14131 from v2 authorities (all trusted directories).
14132 - Change DirServers config line to note which dirs are v1 authorities.
14133 - Add configuration option "V1AuthoritativeDirectory 1" which
14134 moria1, moria2, and tor26 should set.
14135 - Remove option when getting directory cache to see whether they
14136 support running-routers; they all do now. Replace it with one
14137 to see whether caches support v2 stuff.
14140 - Dirservers now do their own external reachability testing of each
14141 Tor server, and only list them as running if they've been found to
14142 be reachable. We also send back warnings to the server's logs if
14143 it uploads a descriptor that we already believe is unreachable.
14144 - Implement exit enclaves: if we know an IP address for the
14145 destination, and there's a running Tor server at that address
14146 which allows exit to the destination, then extend the circuit to
14147 that exit first. This provides end-to-end encryption and end-to-end
14148 authentication. Also, if the user wants a .exit address or enclave,
14149 use 4 hops rather than 3, and cannibalize a general circ for it
14151 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
14152 controller. Also, rotate dns and cpu workers if the controller
14153 changes options that will affect them; and initialize the dns
14154 worker cache tree whether or not we start out as a server.
14155 - Only upload a new server descriptor when options change, 18
14156 hours have passed, uptime is reset, or bandwidth changes a lot.
14157 - Check [X-]Forwarded-For headers in HTTP requests when generating
14158 log messages. This lets people run dirservers (and caches) behind
14159 Apache but still know which IP addresses are causing warnings.
14161 o Config option changes:
14162 - Replace (Fascist)Firewall* config options with a new
14163 ReachableAddresses option that understands address policies.
14164 For example, "ReachableAddresses *:80,*:443"
14165 - Get rid of IgnoreVersion undocumented config option, and make us
14166 only warn, never exit, when we're running an obsolete version.
14167 - Make MonthlyAccountingStart config option truly obsolete now.
14169 o Fixes on 0.1.0.x:
14170 - Reject ports 465 and 587 in the default exit policy, since
14171 people have started using them for spam too.
14172 - It turns out we couldn't bootstrap a network since we added
14173 reachability detection in 0.1.0.1-rc. Good thing the Tor network
14174 has never gone down. Add an AssumeReachable config option to let
14175 servers and dirservers bootstrap. When we're trying to build a
14176 high-uptime or high-bandwidth circuit but there aren't enough
14177 suitable servers, try being less picky rather than simply failing.
14178 - Our logic to decide if the OR we connected to was the right guy
14179 was brittle and maybe open to a mitm for unverified routers.
14180 - We weren't cannibalizing circuits correctly for
14181 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
14182 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
14183 build those from scratch. This should make hidden services faster.
14184 - Predict required circuits better, with an eye toward making hidden
14185 services faster on the service end.
14186 - Retry streams if the exit node sends back a 'misc' failure. This
14187 should result in fewer random failures. Also, after failing
14188 from resolve failed or misc, reset the num failures, so we give
14189 it a fair shake next time we try.
14190 - Clean up the rendezvous warn log msgs, and downgrade some to info.
14191 - Reduce severity on logs about dns worker spawning and culling.
14192 - When we're shutting down and we do something like try to post a
14193 server descriptor or rendezvous descriptor, don't complain that
14194 we seem to be unreachable. Of course we are, we're shutting down.
14195 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
14196 We don't use them yet, but maybe one day our DNS resolver will be
14197 able to discover them.
14198 - Make ContactInfo mandatory for authoritative directory servers.
14199 - Require server descriptors to list IPv4 addresses -- hostnames
14200 are no longer allowed. This also fixes some potential security
14201 problems with people providing hostnames as their address and then
14202 preferentially resolving them to partition users.
14203 - Change log line for unreachability to explicitly suggest /etc/hosts
14204 as the culprit. Also make it clearer what IP address and ports we're
14205 testing for reachability.
14206 - Put quotes around user-supplied strings when logging so users are
14207 more likely to realize if they add bad characters (like quotes)
14209 - Let auth dir servers start without specifying an Address config
14211 - Make unit tests (and other invocations that aren't the real Tor)
14212 run without launching listeners, creating subdirectories, and so on.
14215 Changes in version 0.1.1.5-alpha - 2005-08-08
14216 o Bugfixes included in 0.1.0.14.
14218 o Bugfixes on 0.1.0.x:
14219 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
14220 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
14221 it would silently using ignore the 6668.
14224 Changes in version 0.1.0.14 - 2005-08-08
14225 o Bugfixes on 0.1.0.x:
14226 - Fix the other half of the bug with crypto handshakes
14228 - Fix an assert trigger if you send a 'signal term' via the
14229 controller when it's listening for 'event info' messages.
14232 Changes in version 0.1.1.4-alpha - 2005-08-04
14233 o Bugfixes included in 0.1.0.13.
14236 - Improve tor_gettimeofday() granularity on windows.
14237 - Make clients regenerate their keys when their IP address changes.
14238 - Implement some more GETINFO goodness: expose helper nodes, config
14239 options, getinfo keys.
14242 Changes in version 0.1.0.13 - 2005-08-04
14243 o Bugfixes on 0.1.0.x:
14244 - Fix a critical bug in the security of our crypto handshakes.
14245 - Fix a size_t underflow in smartlist_join_strings2() that made
14246 it do bad things when you hand it an empty smartlist.
14247 - Fix Windows installer to ship Tor license (thanks to Aphex for
14248 pointing out this oversight) and put a link to the doc directory
14250 - Explicitly set no-unaligned-access for sparc: it turns out the
14251 new gcc's let you compile broken code, but that doesn't make it
14255 Changes in version 0.1.1.3-alpha - 2005-07-23
14256 o Bugfixes on 0.1.1.2-alpha:
14257 - Fix a bug in handling the controller's "post descriptor"
14259 - Fix several bugs in handling the controller's "extend circuit"
14261 - Fix a bug in handling the controller's "stream status" event.
14262 - Fix an assert failure if we have a controller listening for
14263 circuit events and we go offline.
14264 - Re-allow hidden service descriptors to publish 0 intro points.
14265 - Fix a crash when generating your hidden service descriptor if
14266 you don't have enough intro points already.
14268 o New features on 0.1.1.2-alpha:
14269 - New controller function "getinfo accounting", to ask how
14270 many bytes we've used in this time period.
14271 - Experimental support for helper nodes: a lot of the risk from
14272 a small static adversary comes because users pick new random
14273 nodes every time they rebuild a circuit. Now users will try to
14274 stick to the same small set of entry nodes if they can. Not
14275 enabled by default yet.
14277 o Bugfixes on 0.1.0.12:
14278 - If you're an auth dir server, always publish your dirport,
14279 even if you haven't yet found yourself to be reachable.
14280 - Fix a size_t underflow in smartlist_join_strings2() that made
14281 it do bad things when you hand it an empty smartlist.
14284 Changes in version 0.1.0.12 - 2005-07-18
14285 o New directory servers:
14286 - tor26 has changed IP address.
14288 o Bugfixes on 0.1.0.x:
14289 - Fix a possible double-free in tor_gzip_uncompress().
14290 - When --disable-threads is set, do not search for or link against
14291 pthreads libraries.
14292 - Don't trigger an assert if an authoritative directory server
14293 claims its dirport is 0.
14294 - Fix bug with removing Tor as an NT service: some people were
14295 getting "The service did not return an error." Thanks to Matt
14299 Changes in version 0.1.1.2-alpha - 2005-07-15
14300 o New directory servers:
14301 - tor26 has changed IP address.
14303 o Bugfixes on 0.1.0.x, crashes/leaks:
14304 - Port the servers-not-obeying-their-exit-policies fix from
14306 - Fix an fd leak in start_daemon().
14307 - On Windows, you can't always reopen a port right after you've
14308 closed it. So change retry_listeners() to only close and re-open
14309 ports that have changed.
14310 - Fix a possible double-free in tor_gzip_uncompress().
14312 o Bugfixes on 0.1.0.x, usability:
14313 - When tor_socketpair() fails in Windows, give a reasonable
14314 Windows-style errno back.
14315 - Let people type "tor --install" as well as "tor -install" when
14317 want to make it an NT service.
14318 - NT service patch from Matt Edman to improve error messages.
14319 - When the controller asks for a config option with an abbreviated
14320 name, give the full name in our response.
14321 - Correct the man page entry on TrackHostExitsExpire.
14322 - Looks like we were never delivering deflated (i.e. compressed)
14323 running-routers lists, even when asked. Oops.
14324 - When --disable-threads is set, do not search for or link against
14325 pthreads libraries.
14327 o Bugfixes on 0.1.1.x:
14328 - Fix a seg fault with autodetecting which controller version is
14332 - New hidden service descriptor format: put a version in it, and
14333 let people specify introduction/rendezvous points that aren't
14334 in "the directory" (which is subjective anyway).
14335 - Allow the DEBUG controller event to work again. Mark certain log
14336 entries as "don't tell this to controllers", so we avoid cycles.
14339 Changes in version 0.1.0.11 - 2005-06-30
14340 o Bugfixes on 0.1.0.x:
14341 - Fix major security bug: servers were disregarding their
14342 exit policies if clients behaved unexpectedly.
14343 - Make OS X init script check for missing argument, so we don't
14344 confuse users who invoke it incorrectly.
14345 - Fix a seg fault in "tor --hash-password foo".
14346 - The MAPADDRESS control command was broken.
14349 Changes in version 0.1.1.1-alpha - 2005-06-29
14351 - Make OS X init script check for missing argument, so we don't
14352 confuse users who invoke it incorrectly.
14353 - Fix a seg fault in "tor --hash-password foo".
14354 - Fix a possible way to DoS dirservers.
14355 - When we complain that your exit policy implicitly allows local or
14356 private address spaces, name them explicitly so operators can
14358 - Make the log message less scary when all the dirservers are
14359 temporarily unreachable.
14360 - We were printing the number of idle dns workers incorrectly when
14364 - Revised controller protocol (version 1) that uses ascii rather
14365 than binary. Add supporting libraries in python and java so you
14366 can use the controller from your applications without caring how
14367 our protocol works.
14368 - Spiffy new support for crypto hardware accelerators. Can somebody
14372 Changes in version 0.0.9.10 - 2005-06-16
14373 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
14374 - Refuse relay cells that claim to have a length larger than the
14375 maximum allowed. This prevents a potential attack that could read
14376 arbitrary memory (e.g. keys) from an exit server's process
14380 Changes in version 0.1.0.10 - 2005-06-14
14381 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
14382 libevent before 1.1a.
14385 Changes in version 0.1.0.9-rc - 2005-06-09
14387 - Reset buf->highwater every time buf_shrink() is called, not just on
14388 a successful shrink. This was causing significant memory bloat.
14389 - Fix buffer overflow when checking hashed passwords.
14390 - Security fix: if seeding the RNG on Win32 fails, quit.
14391 - Allow seeding the RNG on Win32 even when you're not running as
14393 - Disable threading on Solaris too. Something is wonky with it,
14394 cpuworkers, and reentrant libs.
14395 - Reenable the part of the code that tries to flush as soon as an
14396 OR outbuf has a full TLS record available. Perhaps this will make
14397 OR outbufs not grow as huge except in rare cases, thus saving lots
14398 of CPU time plus memory.
14399 - Reject malformed .onion addresses rather then passing them on as
14400 normal web requests.
14401 - Adapt patch from Adam Langley: fix possible memory leak in
14402 tor_lookup_hostname().
14403 - Initialize libevent later in the startup process, so the logs are
14404 already established by the time we start logging libevent warns.
14405 - Use correct errno on win32 if libevent fails.
14406 - Check and warn about known-bad/slow libevent versions.
14407 - Pay more attention to the ClientOnly config option.
14408 - Have torctl.in/tor.sh.in check for location of su binary (needed
14410 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
14411 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
14412 HttpProxyAuthenticator
14413 - Stop warning about sigpipes in the logs. We're going to
14414 pretend that getting these occassionally is normal and fine.
14415 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
14417 installer screens; and don't put stuff into StartupItems unless
14418 the user asks you to.
14419 - Require servers that use the default dirservers to have public IP
14420 addresses. We have too many servers that are configured with private
14421 IPs and their admins never notice the log entries complaining that
14422 their descriptors are being rejected.
14423 - Add OSX uninstall instructions. An actual uninstall script will
14427 Changes in version 0.1.0.8-rc - 2005-05-23
14429 - It turns out that kqueue on OS X 10.3.9 was causing kernel
14430 panics. Disable kqueue on all OS X Tors.
14431 - Fix RPM: remove duplicate line accidentally added to the rpm
14433 - Disable threads on openbsd too, since its gethostaddr is not
14435 - Tolerate libevent 0.8 since it still works, even though it's
14437 - Enable building on Red Hat 9.0 again.
14438 - Allow the middle hop of the testing circuit to be running any
14439 version, now that most of them have the bugfix to let them connect
14440 to unknown servers. This will allow reachability testing to work
14441 even when 0.0.9.7-0.0.9.9 become obsolete.
14442 - Handle relay cells with rh.length too large. This prevents
14443 a potential attack that could read arbitrary memory (maybe even
14444 keys) from the exit server's process.
14445 - We screwed up the dirport reachability testing when we don't yet
14446 have a cached version of the directory. Hopefully now fixed.
14447 - Clean up router_load_single_router() (used by the controller),
14448 so it doesn't seg fault on error.
14449 - Fix a minor memory leak when somebody establishes an introduction
14450 point at your Tor server.
14451 - If a socks connection ends because read fails, don't warn that
14452 you're not sending a socks reply back.
14455 - Add HttpProxyAuthenticator config option too, that works like
14456 the HttpsProxyAuthenticator config option.
14457 - Encode hashed controller passwords in hex instead of base64,
14458 to make it easier to write controllers.
14461 Changes in version 0.1.0.7-rc - 2005-05-17
14463 - Fix a bug in the OS X package installer that prevented it from
14464 installing on Tiger.
14465 - Fix a script bug in the OS X package installer that made it
14466 complain during installation.
14467 - Find libevent even if it's hiding in /usr/local/ and your
14468 CFLAGS and LDFLAGS don't tell you to look there.
14469 - Be able to link with libevent as a shared library (the default
14470 after 1.0d), even if it's hiding in /usr/local/lib and even
14471 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
14472 assuming you're running gcc. Otherwise fail and give a useful
14474 - Fix a bug in the RPM packager: set home directory for _tor to
14475 something more reasonable when first installing.
14476 - Free a minor amount of memory that is still reachable on exit.
14479 Changes in version 0.1.0.6-rc - 2005-05-14
14481 - Implement --disable-threads configure option. Disable threads on
14482 netbsd by default, because it appears to have no reentrant resolver
14484 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
14485 release (1.1) detects and disables kqueue if it's broken.
14486 - Append default exit policy before checking for implicit internal
14487 addresses. Now we don't log a bunch of complaints on startup
14488 when using the default exit policy.
14489 - Some people were putting "Address " in their torrc, and they had
14490 a buggy resolver that resolved " " to 0.0.0.0. Oops.
14491 - If DataDir is ~/.tor, and that expands to /.tor, then default to
14492 LOCALSTATEDIR/tor instead.
14493 - Fix fragmented-message bug in TorControl.py.
14494 - Resolve a minor bug which would prevent unreachable dirports
14495 from getting suppressed in the published descriptor.
14496 - When the controller gave us a new descriptor, we weren't resolving
14497 it immediately, so Tor would think its address was 0.0.0.0 until
14498 we fetched a new directory.
14499 - Fix an uppercase/lowercase case error in suppressing a bogus
14500 libevent warning on some Linuxes.
14503 - Begin scrubbing sensitive strings from logs by default. Turn off
14504 the config option SafeLogging if you need to do debugging.
14505 - Switch to a new buffer management algorithm, which tries to avoid
14506 reallocing and copying quite as much. In first tests it looks like
14507 it uses *more* memory on average, but less cpu.
14508 - First cut at support for "create-fast" cells. Clients can use
14509 these when extending to their first hop, since the TLS already
14510 provides forward secrecy and authentication. Not enabled on
14512 - When dirservers refuse a router descriptor, we now log its
14513 contactinfo, platform, and the poster's IP address.
14514 - Call tor_free_all instead of connections_free_all after forking, to
14515 save memory on systems that need to fork.
14516 - Whine at you if you're a server and you don't set your contactinfo.
14517 - Implement --verify-config command-line option to check if your torrc
14518 is valid without actually launching Tor.
14519 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
14520 rather than just rejecting it.
14523 Changes in version 0.1.0.5-rc - 2005-04-27
14525 - Stop trying to print a null pointer if an OR conn fails because
14526 we didn't like its cert.
14528 - Switch our internal buffers implementation to use a ring buffer,
14529 to hopefully improve performance for fast servers a lot.
14530 - Add HttpsProxyAuthenticator support (basic auth only), based
14531 on patch from Adam Langley.
14532 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
14533 the fast servers that have been joining lately.
14534 - Give hidden service accesses extra time on the first attempt,
14535 since 60 seconds is often only barely enough. This might improve
14537 - Improve performance for dirservers: stop re-parsing the whole
14538 directory every time you regenerate it.
14539 - Add more debugging info to help us find the weird dns freebsd
14540 pthreads bug; cleaner debug messages to help track future issues.
14543 Changes in version 0.0.9.9 - 2005-04-23
14544 o Bugfixes on 0.0.9.x:
14545 - If unofficial Tor clients connect and send weird TLS certs, our
14546 Tor server triggers an assert. This release contains a minimal
14547 backport from the broader fix that we put into 0.1.0.4-rc.
14550 Changes in version 0.1.0.4-rc - 2005-04-23
14552 - If unofficial Tor clients connect and send weird TLS certs, our
14553 Tor server triggers an assert. Stop asserting, and start handling
14554 TLS errors better in other situations too.
14555 - When the controller asks us to tell it about all the debug-level
14556 logs, it turns out we were generating debug-level logs while
14557 telling it about them, which turns into a bad loop. Now keep
14558 track of whether you're sending a debug log to the controller,
14559 and don't log when you are.
14560 - Fix the "postdescriptor" feature of the controller interface: on
14561 non-complete success, only say "done" once.
14563 - Clients are now willing to load balance over up to 2mB, not 1mB,
14564 of advertised bandwidth capacity.
14565 - Add a NoPublish config option, so you can be a server (e.g. for
14566 testing running Tor servers in other Tor networks) without
14567 publishing your descriptor to the primary dirservers.
14570 Changes in version 0.1.0.3-rc - 2005-04-08
14571 o Improvements on 0.1.0.2-rc:
14572 - Client now retries when streams end early for 'hibernating' or
14573 'resource limit' reasons, rather than failing them.
14574 - More automated handling for dirserver operators:
14575 - Automatically approve nodes running 0.1.0.2-rc or later,
14576 now that the the reachability detection stuff is working.
14577 - Now we allow two unverified servers with the same nickname
14578 but different keys. But if a nickname is verified, only that
14579 nickname+key are allowed.
14580 - If you're an authdirserver connecting to an address:port,
14581 and it's not the OR you were expecting, forget about that
14582 descriptor. If he *was* the one you were expecting, then forget
14583 about all other descriptors for that address:port.
14584 - Allow servers to publish descriptors from 12 hours in the future.
14585 Corollary: only whine about clock skew from the dirserver if
14586 he's a trusted dirserver (since now even verified servers could
14587 have quite wrong clocks).
14588 - Adjust maximum skew and age for rendezvous descriptors: let skew
14589 be 48 hours rather than 90 minutes.
14590 - Efficiency improvements:
14591 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
14592 it much faster to look up a circuit for each relay cell.
14593 - Remove most calls to assert_all_pending_dns_resolves_ok(),
14594 since they're eating our cpu on exit nodes.
14595 - Stop wasting time doing a case insensitive comparison for every
14596 dns name every time we do any lookup. Canonicalize the names to
14597 lowercase and be done with it.
14598 - Start sending 'truncated' cells back rather than destroy cells,
14599 if the circuit closes in front of you. This means we won't have
14600 to abandon partially built circuits.
14601 - Only warn once per nickname from add_nickname_list_to_smartlist
14602 per failure, so an entrynode or exitnode choice that's down won't
14604 - Put a note in the torrc about abuse potential with the default
14606 - Revise control spec and implementation to allow all log messages to
14607 be sent to controller with their severities intact (suggested by
14608 Matt Edman). Update TorControl to handle new log event types.
14609 - Provide better explanation messages when controller's POSTDESCRIPTOR
14611 - Stop putting nodename in the Platform string in server descriptors.
14612 It doesn't actually help, and it is confusing/upsetting some people.
14614 o Bugfixes on 0.1.0.2-rc:
14615 - We were printing the host mask wrong in exit policies in server
14616 descriptors. This isn't a critical bug though, since we were still
14617 obeying the exit policy internally.
14618 - Fix Tor when compiled with libevent but without pthreads: move
14619 connection_unregister() from _connection_free() to
14621 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
14622 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
14623 when we look through the connection array, we'll find any of the
14624 cpu/dnsworkers. This is no good.
14626 o Bugfixes on 0.0.9.8:
14627 - Fix possible bug on threading platforms (e.g. win32) which was
14628 leaking a file descriptor whenever a cpuworker or dnsworker died.
14629 - When using preferred entry or exit nodes, ignore whether the
14630 circuit wants uptime or capacity. They asked for the nodes, they
14632 - chdir() to your datadirectory at the *end* of the daemonize process,
14633 not the beginning. This was a problem because the first time you
14634 run tor, if your datadir isn't there, and you have runasdaemon set
14635 to 1, it will try to chdir to it before it tries to create it. Oops.
14636 - Handle changed router status correctly when dirserver reloads
14637 fingerprint file. We used to be dropping all unverified descriptors
14638 right then. The bug was hidden because we would immediately
14639 fetch a directory from another dirserver, which would include the
14640 descriptors we just dropped.
14641 - When we're connecting to an OR and he's got a different nickname/key
14642 than we were expecting, only complain loudly if we're an OP or a
14643 dirserver. Complaining loudly to the OR admins just confuses them.
14644 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
14645 artificially capped at 500kB.
14648 Changes in version 0.0.9.8 - 2005-04-07
14649 o Bugfixes on 0.0.9.x:
14650 - We have a bug that I haven't found yet. Sometimes, very rarely,
14651 cpuworkers get stuck in the 'busy' state, even though the cpuworker
14652 thinks of itself as idle. This meant that no new circuits ever got
14653 established. Here's a workaround to kill any cpuworker that's been
14654 busy for more than 100 seconds.
14657 Changes in version 0.1.0.2-rc - 2005-04-01
14658 o Bugfixes on 0.1.0.1-rc:
14659 - Fixes on reachability detection:
14660 - Don't check for reachability while hibernating.
14661 - If ORPort is reachable but DirPort isn't, still publish the
14662 descriptor, but zero out DirPort until it's found reachable.
14663 - When building testing circs for ORPort testing, use only
14664 high-bandwidth nodes, so fewer circuits fail.
14665 - Complain about unreachable ORPort separately from unreachable
14666 DirPort, so the user knows what's going on.
14667 - Make sure we only conclude ORPort reachability if we didn't
14668 initiate the conn. Otherwise we could falsely conclude that
14669 we're reachable just because we connected to the guy earlier
14670 and he used that same pipe to extend to us.
14671 - Authdirservers shouldn't do ORPort reachability detection,
14672 since they're in clique mode, so it will be rare to find a
14673 server not already connected to them.
14674 - When building testing circuits, always pick middle hops running
14675 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
14676 bug. (This is a kludge; it will go away when 0.0.9.x becomes
14678 - When we decide we're reachable, actually publish our descriptor
14680 - Fix bug in redirectstream in the controller.
14681 - Fix the state descriptor strings so logs don't claim edge streams
14682 are in a different state than they actually are.
14683 - Use recent libevent features when possible (this only really affects
14684 win32 and osx right now, because the new libevent with these
14685 features hasn't been released yet). Add code to suppress spurious
14687 - Prevent possible segfault in connection_close_unattached_ap().
14688 - Fix newlines on torrc in win32.
14689 - Improve error msgs when tor-resolve fails.
14691 o Improvements on 0.0.9.x:
14692 - New experimental script tor/contrib/ExerciseServer.py (needs more
14693 work) that uses the controller interface to build circuits and
14694 fetch pages over them. This will help us bootstrap servers that
14695 have lots of capacity but haven't noticed it yet.
14696 - New experimental script tor/contrib/PathDemo.py (needs more work)
14697 that uses the controller interface to let you choose whole paths
14699 "<hostname>.<path,separated by dots>.<length of path>.path"
14700 - When we've connected to an OR and handshaked but didn't like
14701 the result, we were closing the conn without sending destroy
14702 cells back for pending circuits. Now send those destroys.
14705 Changes in version 0.0.9.7 - 2005-04-01
14706 o Bugfixes on 0.0.9.x:
14707 - Fix another race crash bug (thanks to Glenn Fink for reporting).
14708 - Compare identity to identity, not to nickname, when extending to
14709 a router not already in the directory. This was preventing us from
14710 extending to unknown routers. Oops.
14711 - Make sure to create OS X Tor user in <500 range, so we aren't
14712 creating actual system users.
14713 - Note where connection-that-hasn't-sent-end was marked, and fix
14714 a few really loud instances of this harmless bug (it's fixed more
14718 Changes in version 0.1.0.1-rc - 2005-03-28
14720 - Add reachability testing. Your Tor server will automatically try
14721 to see if its ORPort and DirPort are reachable from the outside,
14722 and it won't upload its descriptor until it decides they are.
14723 - Handle unavailable hidden services better. Handle slow or busy
14724 hidden services better.
14725 - Add support for CONNECTing through https proxies, with "HttpsProxy"
14727 - New exit policy: accept most low-numbered ports, rather than
14728 rejecting most low-numbered ports.
14729 - More Tor controller support (still experimental). See
14730 http://tor.eff.org/doc/control-spec.txt for all the new features,
14731 including signals to emulate unix signals from any platform;
14732 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
14733 closestream; closecircuit; etc.
14734 - Make nt services work and start on startup on win32 (based on
14735 patch by Matt Edman).
14736 - Add a new AddressMap config directive to rewrite incoming socks
14737 addresses. This lets you, for example, declare an implicit
14738 required exit node for certain sites.
14739 - Add a new TrackHostExits config directive to trigger addressmaps
14740 for certain incoming socks addresses -- for sites that break when
14741 your exit keeps changing (based on patch by Mike Perry).
14742 - Redo the client-side dns cache so it's just an addressmap too.
14743 - Notice when our IP changes, and reset stats/uptime/reachability.
14744 - When an application is using socks5, give him the whole variety of
14745 potential socks5 responses (connect refused, host unreachable, etc),
14746 rather than just "success" or "failure".
14747 - A more sane version numbering system. See
14748 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
14749 - New contributed script "exitlist": a simple python script to
14750 parse directories and find Tor nodes that exit to listed
14752 - New contributed script "privoxy-tor-toggle" to toggle whether
14753 Privoxy uses Tor. Seems to be configured for Debian by default.
14754 - Report HTTP reasons to client when getting a response from directory
14755 servers -- so you can actually know what went wrong.
14756 - New config option MaxAdvertisedBandwidth which lets you advertise
14757 a low bandwidthrate (to not attract as many circuits) while still
14758 allowing a higher bandwidthrate in reality.
14760 o Robustness/stability fixes:
14761 - Make Tor use Niels Provos's libevent instead of its current
14762 poll-but-sometimes-select mess. This will let us use faster async
14763 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
14765 - pthread support now too. This was forced because when we forked,
14766 we ended up wasting a lot of duplicate ram over time. Also switch
14767 to foo_r versions of some library calls to allow reentry and
14769 - Better handling for heterogeneous / unreliable nodes:
14770 - Annotate circuits w/ whether they aim to contain high uptime nodes
14771 and/or high capacity nodes. When building circuits, choose
14773 - This means that every single node in an intro rend circuit,
14774 not just the last one, will have a minimum uptime.
14775 - New config option LongLivedPorts to indicate application streams
14776 that will want high uptime circuits.
14777 - Servers reset uptime when a dir fetch entirely fails. This
14778 hopefully reflects stability of the server's network connectivity.
14779 - If somebody starts his tor server in Jan 2004 and then fixes his
14780 clock, don't make his published uptime be a year.
14781 - Reset published uptime when you wake up from hibernation.
14782 - Introduce a notion of 'internal' circs, which are chosen without
14783 regard to the exit policy of the last hop. Intro and rendezvous
14784 circs must be internal circs, to avoid leaking information. Resolve
14785 and connect streams can use internal circs if they want.
14786 - New circuit pooling algorithm: make sure to have enough circs around
14787 to satisfy any predicted ports, and also make sure to have 2 internal
14788 circs around if we've required internal circs lately (and with high
14789 uptime if we've seen that lately too).
14790 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
14791 which describes how often we retry making new circuits if current
14792 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
14793 how long we're willing to make use of an already-dirty circuit.
14794 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
14795 circ as necessary, if there are any completed ones lying around
14796 when we try to launch one.
14797 - Make hidden services try to establish a rendezvous for 30 seconds,
14798 rather than for n (where n=3) attempts to build a circuit.
14799 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
14800 "ShutdownWaitLength".
14801 - Try to be more zealous about calling connection_edge_end when
14802 things go bad with edge conns in connection.c.
14803 - Revise tor-spec to add more/better stream end reasons.
14804 - Revise all calls to connection_edge_end to avoid sending "misc",
14805 and to take errno into account where possible.
14808 - Fix a race condition that can trigger an assert, when we have a
14809 pending create cell and an OR connection fails right then.
14810 - Fix several double-mark-for-close bugs, e.g. where we were finding
14811 a conn for a cell even if that conn is already marked for close.
14812 - Make sequence of log messages when starting on win32 with no config
14813 file more reasonable.
14814 - When choosing an exit node for a new non-internal circ, don't take
14815 into account whether it'll be useful for any pending x.onion
14816 addresses -- it won't.
14817 - Turn addr_policy_compare from a tristate to a quadstate; this should
14818 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
14819 for google.com" problem.
14820 - Make "platform" string in descriptor more accurate for Win32 servers,
14821 so it's not just "unknown platform".
14822 - Fix an edge case in parsing config options (thanks weasel).
14823 If they say "--" on the commandline, it's not an option.
14824 - Reject odd-looking addresses at the client (e.g. addresses that
14825 contain a colon), rather than having the server drop them because
14827 - tor-resolve requests were ignoring .exit if there was a working circuit
14828 they could use instead.
14829 - REUSEADDR on normal platforms means you can rebind to the port
14830 right after somebody else has let it go. But REUSEADDR on win32
14831 means to let you bind to the port _even when somebody else
14832 already has it bound_! So, don't do that on Win32.
14833 - Change version parsing logic: a version is "obsolete" if it is not
14834 recommended and (1) there is a newer recommended version in the
14835 same series, or (2) there are no recommended versions in the same
14836 series, but there are some recommended versions in a newer series.
14837 A version is "new" if it is newer than any recommended version in
14839 - Stop most cases of hanging up on a socks connection without sending
14843 - Require BandwidthRate to be at least 20kB/s for servers.
14844 - When a dirserver causes you to give a warn, mention which dirserver
14846 - New config option DirAllowPrivateAddresses for authdirservers.
14847 Now by default they refuse router descriptors that have non-IP or
14848 private-IP addresses.
14849 - Stop publishing socksport in the directory, since it's not
14850 actually meant to be public. For compatibility, publish a 0 there
14852 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
14853 smart" value, that is low for servers and high for clients.
14854 - If our clock jumps forward by 100 seconds or more, assume something
14855 has gone wrong with our network and abandon all not-yet-used circs.
14856 - Warn when exit policy implicitly allows local addresses.
14857 - If we get an incredibly skewed timestamp from a dirserver mirror
14858 that isn't a verified OR, don't warn -- it's probably him that's
14860 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
14861 cookies to disk and doesn't log each web request to disk. (Thanks
14862 to Brett Carrington for pointing this out.)
14863 - When a client asks us for a dir mirror and we don't have one,
14864 launch an attempt to get a fresh one.
14865 - If we're hibernating and we get a SIGINT, exit immediately.
14866 - Add --with-dmalloc ./configure option, to track memory leaks.
14867 - And try to free all memory on closing, so we can detect what
14869 - Cache local dns resolves correctly even when they're .exit
14871 - Give a better warning when some other server advertises an
14872 ORPort that is actually an apache running ssl.
14873 - Add "opt hibernating 1" to server descriptor to make it clearer
14874 whether the server is hibernating.
14877 Changes in version 0.0.9.6 - 2005-03-24
14878 o Bugfixes on 0.0.9.x (crashes and asserts):
14879 - Add new end stream reasons to maintainance branch. Fix bug where
14880 reason (8) could trigger an assert. Prevent bug from recurring.
14881 - Apparently win32 stat wants paths to not end with a slash.
14882 - Fix assert triggers in assert_cpath_layer_ok(), where we were
14883 blowing away the circuit that conn->cpath_layer points to, then
14884 checking to see if the circ is well-formed. Backport check to make
14885 sure we dont use the cpath on a closed connection.
14886 - Prevent circuit_resume_edge_reading_helper() from trying to package
14887 inbufs for marked-for-close streams.
14888 - Don't crash on hup if your options->address has become unresolvable.
14889 - Some systems (like OS X) sometimes accept() a connection and tell
14890 you the remote host is 0.0.0.0:0. If this happens, due to some
14891 other mis-features, we get confused; so refuse the conn for now.
14893 o Bugfixes on 0.0.9.x (other):
14894 - Fix harmless but scary "Unrecognized content encoding" warn message.
14895 - Add new stream error reason: TORPROTOCOL reason means "you are not
14896 speaking a version of Tor I understand; say bye-bye to your stream."
14897 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
14898 into the future, now that we are more tolerant of skew. This
14899 resolves a bug where a Tor server would refuse to cache a directory
14900 because all the directories it gets are too far in the future;
14901 yet the Tor server never logs any complaints about clock skew.
14902 - Mac packaging magic: make man pages useable, and do not overwrite
14903 existing torrc files.
14904 - Make OS X log happily to /var/log/tor/tor.log
14907 Changes in version 0.0.9.5 - 2005-02-22
14908 o Bugfixes on 0.0.9.x:
14909 - Fix an assert race at exit nodes when resolve requests fail.
14910 - Stop picking unverified dir mirrors--it only leads to misery.
14911 - Patch from Matt Edman to make NT services work better. Service
14912 support is still not compiled into the executable by default.
14913 - Patch from Dmitri Bely so the Tor service runs better under
14914 the win32 SYSTEM account.
14915 - Make tor-resolve actually work (?) on Win32.
14916 - Fix a sign bug when getrlimit claims to have 4+ billion
14917 file descriptors available.
14918 - Stop refusing to start when bandwidthburst == bandwidthrate.
14919 - When create cells have been on the onion queue more than five
14920 seconds, just send back a destroy and take them off the list.
14923 Changes in version 0.0.9.4 - 2005-02-03
14924 o Bugfixes on 0.0.9:
14925 - Fix an assert bug that took down most of our servers: when
14926 a server claims to have 1 GB of bandwidthburst, don't
14928 - Don't crash as badly if we have spawned the max allowed number
14929 of dnsworkers, or we're out of file descriptors.
14930 - Block more file-sharing ports in the default exit policy.
14931 - MaxConn is now automatically set to the hard limit of max
14932 file descriptors we're allowed (ulimit -n), minus a few for
14934 - Give a clearer message when servers need to raise their
14935 ulimit -n when they start running out of file descriptors.
14936 - SGI Compatibility patches from Jan Schaumann.
14937 - Tolerate a corrupt cached directory better.
14938 - When a dirserver hasn't approved your server, list which one.
14939 - Go into soft hibernation after 95% of the bandwidth is used,
14940 not 99%. This is especially important for daily hibernators who
14941 have a small accounting max. Hopefully it will result in fewer
14942 cut connections when the hard hibernation starts.
14943 - Load-balance better when using servers that claim more than
14944 800kB/s of capacity.
14945 - Make NT services work (experimental, only used if compiled in).
14948 Changes in version 0.0.9.3 - 2005-01-21
14949 o Bugfixes on 0.0.9:
14950 - Backport the cpu use fixes from main branch, so busy servers won't
14951 need as much processor time.
14952 - Work better when we go offline and then come back, or when we
14953 run Tor at boot before the network is up. We do this by
14954 optimistically trying to fetch a new directory whenever an
14955 application request comes in and we think we're offline -- the
14956 human is hopefully a good measure of when the network is back.
14957 - Backport some minimal hidserv bugfixes: keep rend circuits open as
14958 long as you keep using them; actually publish hidserv descriptors
14959 shortly after they change, rather than waiting 20-40 minutes.
14960 - Enable Mac startup script by default.
14961 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
14962 - When you update AllowUnverifiedNodes or FirewallPorts via the
14963 controller's setconf feature, we were always appending, never
14965 - When you update HiddenServiceDir via setconf, it was screwing up
14966 the order of reading the lines, making it fail.
14967 - Do not rewrite a cached directory back to the cache; otherwise we
14968 will think it is recent and not fetch a newer one on startup.
14969 - Workaround for webservers that lie about Content-Encoding: Tor
14970 now tries to autodetect compressed directories and compression
14971 itself. This lets us Proxypass dir fetches through apache.
14974 Changes in version 0.0.9.2 - 2005-01-04
14975 o Bugfixes on 0.0.9 (crashes and asserts):
14976 - Fix an assert on startup when the disk is full and you're logging
14978 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
14979 style address, then we'd crash.
14980 - Fix an assert trigger when the running-routers string we get from
14981 a dirserver is broken.
14982 - Make worker threads start and run on win32. Now win32 servers
14984 - Bandaid (not actually fix, but now it doesn't crash) an assert
14985 where the dns worker dies mysteriously and the main Tor process
14986 doesn't remember anything about the address it was resolving.
14988 o Bugfixes on 0.0.9 (Win32):
14989 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
14990 name out of the warning/assert messages.
14991 - Fix a superficial "unhandled error on read" bug on win32.
14992 - The win32 installer no longer requires a click-through for our
14993 license, since our Free Software license grants rights but does not
14995 - Win32: When connecting to a dirserver fails, try another one
14996 immediately. (This was already working for non-win32 Tors.)
14997 - Stop trying to parse $HOME on win32 when hunting for default
14999 - Make tor-resolve.c work on win32 by calling network_init().
15001 o Bugfixes on 0.0.9 (other):
15002 - Make 0.0.9.x build on Solaris again.
15003 - Due to a fencepost error, we were blowing away the \n when reporting
15004 confvalue items in the controller. So asking for multiple config
15005 values at once couldn't work.
15006 - When listing circuits that are pending on an opening OR connection,
15007 if we're an OR we were listing circuits that *end* at us as
15008 being pending on every listener, dns/cpu worker, etc. Stop that.
15009 - Dirservers were failing to create 'running-routers' or 'directory'
15010 strings if we had more than some threshold of routers. Fix them so
15011 they can handle any number of routers.
15012 - Fix a superficial "Duplicate mark for close" bug.
15013 - Stop checking for clock skew for OR connections, even for servers.
15014 - Fix a fencepost error that was chopping off the last letter of any
15015 nickname that is the maximum allowed nickname length.
15016 - Update URLs in log messages so they point to the new website.
15017 - Fix a potential problem in mangling server private keys while
15018 writing to disk (not triggered yet, as far as we know).
15019 - Include the licenses for other free software we include in Tor,
15020 now that we're shipping binary distributions more regularly.
15023 Changes in version 0.0.9.1 - 2004-12-15
15024 o Bugfixes on 0.0.9:
15025 - Make hibernation actually work.
15026 - Make HashedControlPassword config option work.
15027 - When we're reporting event circuit status to a controller,
15028 don't use the stream status code.
15031 Changes in version 0.0.9 - 2004-12-12
15033 - Clean up manpage and torrc.sample file.
15034 - Clean up severities and text of log warnings.
15036 - Make servers trigger an assert when they enter hibernation.
15039 Changes in version 0.0.9rc7 - 2004-12-08
15040 o Bugfixes on 0.0.9rc:
15041 - Fix a stack-trashing crash when an exit node begins hibernating.
15042 - Avoid looking at unallocated memory while considering which
15043 ports we need to build circuits to cover.
15044 - Stop a sigpipe: when an 'end' cell races with eof from the app,
15045 we shouldn't hold-open-until-flush if the eof arrived first.
15046 - Fix a bug with init_cookie_authentication() in the controller.
15047 - When recommending new-format log lines, if the upper bound is
15048 LOG_ERR, leave it implicit.
15050 o Bugfixes on 0.0.8.1:
15051 - Fix a whole slew of memory leaks.
15052 - Fix isspace() and friends so they still make Solaris happy
15053 but also so they don't trigger asserts on win32.
15054 - Fix parse_iso_time on platforms without strptime (eg win32).
15055 - win32: tolerate extra "readable" events better.
15056 - win32: when being multithreaded, leave parent fdarray open.
15057 - Make unit tests work on win32.
15060 Changes in version 0.0.9rc6 - 2004-12-06
15061 o Bugfixes on 0.0.9pre:
15062 - Clean up some more integer underflow opportunities (not exploitable
15064 - While hibernating, hup should not regrow our listeners.
15065 - Send an end to the streams we close when we hibernate, rather
15066 than just chopping them off.
15067 - React to eof immediately on non-open edge connections.
15069 o Bugfixes on 0.0.8.1:
15070 - Calculate timeout for waiting for a connected cell from the time
15071 we sent the begin cell, not from the time the stream started. If
15072 it took a long time to establish the circuit, we would time out
15073 right after sending the begin cell.
15074 - Fix router_compare_addr_to_addr_policy: it was not treating a port
15075 of * as always matching, so we were picking reject *:* nodes as
15076 exit nodes too. Oops.
15079 - New circuit building strategy: keep a list of ports that we've
15080 used in the past 6 hours, and always try to have 2 circuits open
15081 or on the way that will handle each such port. Seed us with port
15082 80 so web users won't complain that Tor is "slow to start up".
15083 - Make kill -USR1 dump more useful stats about circuits.
15084 - When warning about retrying or giving up, print the address, so
15085 the user knows which one it's talking about.
15086 - If you haven't used a clean circuit in an hour, throw it away,
15087 just to be on the safe side. (This means after 6 hours a totally
15088 unused Tor client will have no circuits open.)
15091 Changes in version 0.0.9rc5 - 2004-12-01
15092 o Bugfixes on 0.0.8.1:
15093 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
15094 - Let resolve conns retry/expire also, rather than sticking around
15096 - If we are using select, make sure we stay within FD_SETSIZE.
15098 o Bugfixes on 0.0.9pre:
15099 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
15100 but doesn't seem to be currently; thanks to Ilja van Sprundel for
15102 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
15103 instead. Impose minima and maxima for all *Period options; impose
15104 even tighter maxima for fetching if we are a caching dirserver.
15105 Clip rather than rejecting.
15106 - Fetch cached running-routers from servers that serve it (that is,
15107 authdirservers and servers running 0.0.9rc5-cvs or later.)
15110 - Accept *:706 (silc) in default exit policy.
15111 - Implement new versioning format for post 0.1.
15112 - Support "foo.nickname.exit" addresses, to let Alice request the
15113 address "foo" as viewed by exit node "nickname". Based on a patch
15115 - Make tor --version --version dump the cvs Id of every file.
15118 Changes in version 0.0.9rc4 - 2004-11-28
15119 o Bugfixes on 0.0.8.1:
15120 - Make windows sockets actually non-blocking (oops), and handle
15121 win32 socket errors better.
15123 o Bugfixes on 0.0.9rc1:
15124 - Actually catch the -USR2 signal.
15127 Changes in version 0.0.9rc3 - 2004-11-25
15128 o Bugfixes on 0.0.8.1:
15129 - Flush the log file descriptor after we print "Tor opening log file",
15130 so we don't see those messages days later.
15132 o Bugfixes on 0.0.9rc1:
15133 - Make tor-resolve work again.
15134 - Avoid infinite loop in tor-resolve if tor hangs up on it.
15135 - Fix an assert trigger for clients/servers handling resolves.
15138 Changes in version 0.0.9rc2 - 2004-11-24
15139 o Bugfixes on 0.0.9rc1:
15140 - I broke socks5 support while fixing the eof bug.
15141 - Allow unitless bandwidths and intervals; they default to bytes
15143 - New servers don't start out hibernating; they are active until
15144 they run out of bytes, so they have a better estimate of how
15145 long it takes, and so their operators can know they're working.
15148 Changes in version 0.0.9rc1 - 2004-11-23
15149 o Bugfixes on 0.0.8.1:
15150 - Finally fix a bug that's been plaguing us for a year:
15151 With high load, circuit package window was reaching 0. Whenever
15152 we got a circuit-level sendme, we were reading a lot on each
15153 socket, but only writing out a bit. So we would eventually reach
15154 eof. This would be noticed and acted on even when there were still
15155 bytes sitting in the inbuf.
15156 - When poll() is interrupted, we shouldn't believe the revents values.
15158 o Bugfixes on 0.0.9pre6:
15159 - Fix hibernate bug that caused pre6 to be broken.
15160 - Don't keep rephist info for routers that haven't had activity for
15161 24 hours. (This matters now that clients have keys, since we track
15163 - Never call close_temp_logs while validating log options.
15164 - Fix backslash-escaping on tor.sh.in and torctl.in.
15167 - Implement weekly/monthly/daily accounting: now you specify your
15168 hibernation properties by
15169 AccountingMax N bytes|KB|MB|GB|TB
15170 AccountingStart day|week|month [day] HH:MM
15171 Defaults to "month 1 0:00".
15172 - Let bandwidth and interval config options be specified as 5 bytes,
15173 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
15174 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
15175 get back to normal.)
15176 - If your requested entry or exit node has advertised bandwidth 0,
15178 - Be more greedy about filling up relay cells -- we try reading again
15179 once we've processed the stuff we read, in case enough has arrived
15180 to fill the last cell completely.
15181 - Apply NT service patch from Osamu Fujino. Still needs more work.
15184 Changes in version 0.0.9pre6 - 2004-11-15
15185 o Bugfixes on 0.0.8.1:
15186 - Fix assert failure on malformed socks4a requests.
15187 - Use identity comparison, not nickname comparison, to choose which
15188 half of circuit-ID-space each side gets to use. This is needed
15189 because sometimes we think of a router as a nickname, and sometimes
15190 as a hex ID, and we can't predict what the other side will do.
15191 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
15192 write() call will fail and we handle it there.
15193 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
15194 and smartlist_len, which are two major profiling offenders.
15196 o Bugfixes on 0.0.9pre5:
15197 - Fix a bug in read_all that was corrupting config files on windows.
15198 - When we're raising the max number of open file descriptors to
15199 'unlimited', don't log that we just raised it to '-1'.
15200 - Include event code with events, as required by control-spec.txt.
15201 - Don't give a fingerprint when clients do --list-fingerprint:
15202 it's misleading, because it will never be the same again.
15203 - Stop using strlcpy in tor_strndup, since it was slowing us
15205 - Remove warn on startup about missing cached-directory file.
15206 - Make kill -USR1 work again.
15207 - Hibernate if we start tor during the "wait for wakeup-time" phase
15208 of an accounting interval. Log our hibernation plans better.
15209 - Authoritative dirservers now also cache their directory, so they
15210 have it on start-up.
15213 - Fetch running-routers; cache running-routers; compress
15214 running-routers; serve compressed running-routers.z
15215 - Add NSI installer script contributed by J Doe.
15216 - Commit VC6 and VC7 workspace/project files.
15217 - Commit a tor.spec for making RPM files, with help from jbash.
15218 - Add contrib/torctl.in contributed by Glenn Fink.
15219 - Implement the control-spec's SAVECONF command, to write your
15220 configuration to torrc.
15221 - Get cookie authentication for the controller closer to working.
15222 - Include control-spec.txt in the tarball.
15223 - When set_conf changes our server descriptor, upload a new copy.
15224 But don't upload it too often if there are frequent changes.
15225 - Document authentication config in man page, and document signals
15227 - Clean up confusing parts of man page and torrc.sample.
15228 - Make expand_filename handle ~ and ~username.
15229 - Use autoconf to enable largefile support where necessary. Use
15230 ftello where available, since ftell can fail at 2GB.
15231 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
15232 log more informatively.
15233 - Give a slightly more useful output for "tor -h".
15234 - Refuse application socks connections to port 0.
15235 - Check clock skew for verified servers, but allow unverified
15236 servers and clients to have any clock skew.
15237 - Break DirFetchPostPeriod into:
15238 - DirFetchPeriod for fetching full directory,
15239 - StatusFetchPeriod for fetching running-routers,
15240 - DirPostPeriod for posting server descriptor,
15241 - RendPostPeriod for posting hidden service descriptors.
15242 - Make sure the hidden service descriptors are at a random offset
15243 from each other, to hinder linkability.
15246 Changes in version 0.0.9pre5 - 2004-11-09
15247 o Bugfixes on 0.0.9pre4:
15248 - Fix a seg fault in unit tests (doesn't affect main program).
15249 - Fix an assert bug where a hidden service provider would fail if
15250 the first hop of his rendezvous circuit was down.
15251 - Hidden service operators now correctly handle version 1 style
15252 INTRODUCE1 cells (nobody generates them still, so not a critical
15254 - If do_hup fails, actually notice.
15255 - Handle more errnos from accept() without closing the listener.
15256 Some OpenBSD machines were closing their listeners because
15257 they ran out of file descriptors.
15258 - Send resolve cells to exit routers that are running a new
15259 enough version of the resolve code to work right.
15260 - Better handling of winsock includes on non-MSV win32 compilers.
15261 - Some people had wrapped their tor client/server in a script
15262 that would restart it whenever it died. This did not play well
15263 with our "shut down if your version is obsolete" code. Now people
15264 don't fetch a new directory if their local cached version is
15266 - Make our autogen.sh work on ksh as well as bash.
15269 - Hibernation: New config option "AccountingMaxKB" lets you
15270 set how many KBytes per month you want to allow your server to
15271 consume. Rather than spreading those bytes out evenly over the
15272 month, we instead hibernate for some of the month and pop up
15273 at a deterministic time, work until the bytes are consumed, then
15274 hibernate again. Config option "MonthlyAccountingStart" lets you
15275 specify which day of the month your billing cycle starts on.
15276 - Control interface: a separate program can now talk to your
15277 client/server over a socket, and get/set config options, receive
15278 notifications of circuits and streams starting/finishing/dying,
15279 bandwidth used, etc. The next step is to get some GUIs working.
15280 Let us know if you want to help out. See doc/control-spec.txt .
15281 - Ship a contrib/tor-control.py as an example script to interact
15282 with the control port.
15283 - "tor --hash-password zzyxz" will output a salted password for
15284 use in authenticating to the control interface.
15285 - New log format in config:
15286 "Log minsev[-maxsev] stdout|stderr|syslog" or
15287 "Log minsev[-maxsev] file /var/foo"
15290 - DirPolicy config option, to let people reject incoming addresses
15291 from their dirserver.
15292 - "tor --list-fingerprint" will list your identity key fingerprint
15294 - Add "pass" target for RedirectExit, to make it easier to break
15295 out of a sequence of RedirectExit rules.
15296 - Clients now generate a TLS cert too, in preparation for having
15297 them act more like real nodes.
15298 - Ship src/win32/ in the tarball, so people can use it to build.
15299 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
15301 - New "router-status" line in directory, to better bind each verified
15302 nickname to its identity key.
15303 - Deprecate unofficial config option abbreviations, and abbreviations
15304 not on the command line.
15305 - Add a pure-C tor-resolve implementation.
15306 - Use getrlimit and friends to ensure we can reach MaxConn (currently
15307 1024) file descriptors.
15309 o Code security improvements, inspired by Ilja:
15310 - Replace sprintf with snprintf. (I think they were all safe, but
15312 - Replace strcpy/strncpy with strlcpy in more places.
15313 - Avoid strcat; use snprintf or strlcat instead.
15314 - snprintf wrapper with consistent (though not C99) overflow behavior.
15317 Changes in version 0.0.9pre4 - 2004-10-17
15318 o Bugfixes on 0.0.9pre3:
15319 - If the server doesn't specify an exit policy, use the real default
15320 exit policy, not reject *:*.
15321 - Ignore fascistfirewall when uploading/downloading hidden service
15322 descriptors, since we go through Tor for those; and when using
15323 an HttpProxy, since we assume it can reach them all.
15324 - When looking for an authoritative dirserver, use only the ones
15325 configured at boot. Don't bother looking in the directory.
15326 - The rest of the fix for get_default_conf_file() on older win32.
15327 - Make 'Routerfile' config option obsolete.
15330 - New 'MyFamily nick1,...' config option for a server to
15331 specify other servers that shouldn't be used in the same circuit
15332 with it. Only believed if nick1 also specifies us.
15333 - New 'NodeFamily nick1,nick2,...' config option for a client to
15334 specify nodes that it doesn't want to use in the same circuit.
15335 - New 'Redirectexit pattern address:port' config option for a
15336 server to redirect exit connections, e.g. to a local squid.
15339 Changes in version 0.0.9pre3 - 2004-10-13
15340 o Bugfixes on 0.0.8.1:
15341 - Better torrc example lines for dirbindaddress and orbindaddress.
15342 - Improved bounds checking on parsed ints (e.g. config options and
15343 the ones we find in directories.)
15344 - Better handling of size_t vs int, so we're more robust on 64
15346 - Fix the rest of the bug where a newly started OR would appear
15347 as unverified even after we've added his fingerprint and hupped
15349 - Fix a bug from 0.0.7: when read() failed on a stream, we would
15350 close it without sending back an end. So 'connection refused'
15351 would simply be ignored and the user would get no response.
15353 o Bugfixes on 0.0.9pre2:
15354 - Serving the cached-on-disk directory to people is bad. We now
15355 provide no directory until we've fetched a fresh one.
15356 - Workaround for bug on windows where cached-directories get crlf
15358 - Make get_default_conf_file() work on older windows too.
15359 - If we write a *:* exit policy line in the descriptor, don't write
15360 any more exit policy lines.
15363 - Use only 0.0.9pre1 and later servers for resolve cells.
15364 - Make the dirservers file obsolete.
15365 - Include a dir-signing-key token in directories to tell the
15366 parsing entity which key is being used to sign.
15367 - Remove the built-in bulky default dirservers string.
15368 - New config option "Dirserver %s:%d [fingerprint]", which can be
15369 repeated as many times as needed. If no dirservers specified,
15370 default to moria1,moria2,tor26.
15371 - Make moria2 advertise a dirport of 80, so people behind firewalls
15372 will be able to get a directory.
15373 - Http proxy support
15374 - Dirservers translate requests for http://%s:%d/x to /x
15375 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
15376 be routed through this host.
15377 - Clients ask for /tor/x rather than /x for new enough dirservers.
15378 This way we can one day coexist peacefully with apache.
15379 - Clients specify a "Host: %s%d" http header, to be compatible
15380 with more proxies, and so running squid on an exit node can work.
15383 Changes in version 0.0.8.1 - 2004-10-13
15385 - Fix a seg fault that can be triggered remotely for Tor
15386 clients/servers with an open dirport.
15387 - Fix a rare assert trigger, where routerinfos for entries in
15388 our cpath would expire while we're building the path.
15389 - Fix a bug in OutboundBindAddress so it (hopefully) works.
15390 - Fix a rare seg fault for people running hidden services on
15391 intermittent connections.
15392 - Fix a bug in parsing opt keywords with objects.
15393 - Fix a stale pointer assert bug when a stream detaches and
15395 - Fix a string format vulnerability (probably not exploitable)
15396 in reporting stats locally.
15397 - Fix an assert trigger: sometimes launching circuits can fail
15398 immediately, e.g. because too many circuits have failed recently.
15399 - Fix a compile warning on 64 bit platforms.
15402 Changes in version 0.0.9pre2 - 2004-10-03
15404 - Make fetching a cached directory work for 64-bit platforms too.
15405 - Make zlib.h a required header, not an optional header.
15408 Changes in version 0.0.9pre1 - 2004-10-01
15410 - Stop using separate defaults for no-config-file and
15411 empty-config-file. Now you have to explicitly turn off SocksPort,
15412 if you don't want it open.
15413 - Fix a bug in OutboundBindAddress so it (hopefully) works.
15414 - Improve man page to mention more of the 0.0.8 features.
15415 - Fix a rare seg fault for people running hidden services on
15416 intermittent connections.
15417 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
15419 - Fix more dns related bugs: send back resolve_failed and end cells
15420 more reliably when the resolve fails, rather than closing the
15421 circuit and then trying to send the cell. Also attach dummy resolve
15422 connections to a circuit *before* calling dns_resolve(), to fix
15423 a bug where cached answers would never be sent in RESOLVED cells.
15424 - When we run out of disk space, or other log writing error, don't
15425 crash. Just stop logging to that log and continue.
15426 - We were starting to daemonize before we opened our logs, so if
15427 there were any problems opening logs, we would complain to stderr,
15428 which wouldn't work, and then mysteriously exit.
15429 - Fix a rare bug where sometimes a verified OR would connect to us
15430 before he'd uploaded his descriptor, which would cause us to
15431 assign conn->nickname as though he's unverified. Now we look through
15432 the fingerprint list to see if he's there.
15433 - Fix a rare assert trigger, where routerinfos for entries in
15434 our cpath would expire while we're building the path.
15437 - Clients can ask dirservers for /dir.z to get a compressed version
15438 of the directory. Only works for servers running 0.0.9, of course.
15439 - Make clients cache directories and use them to seed their router
15440 lists at startup. This means clients have a datadir again.
15441 - Configuration infrastructure support for warning on obsolete
15443 - Respond to content-encoding headers by trying to uncompress as
15445 - Reply with a deflated directory when a client asks for "dir.z".
15446 We could use allow-encodings instead, but allow-encodings isn't
15447 specified in HTTP 1.0.
15448 - Raise the max dns workers from 50 to 100.
15449 - Discourage people from setting their dirfetchpostperiod more often
15450 than once per minute.
15451 - Protect dirservers from overzealous descriptor uploading -- wait
15452 10 seconds after directory gets dirty, before regenerating.
15455 Changes in version 0.0.8 - 2004-08-25
15456 o Port it to SunOS 5.9 / Athena
15459 Changes in version 0.0.8rc2 - 2004-08-20
15460 o Make it compile on cygwin again.
15461 o When picking unverified routers, skip those with low uptime and/or
15462 low bandwidth, depending on what properties you care about.
15465 Changes in version 0.0.8rc1 - 2004-08-18
15466 o Changes from 0.0.7.3:
15468 - Fix assert triggers: if the other side returns an address 0.0.0.0,
15469 don't put it into the client dns cache.
15470 - If a begin failed due to exit policy, but we believe the IP address
15471 should have been allowed, switch that router to exitpolicy reject *:*
15472 until we get our next directory.
15474 - Clients choose nodes proportional to advertised bandwidth.
15475 - Avoid using nodes with low uptime as introduction points.
15476 - Handle servers with dynamic IP addresses: don't replace
15477 options->Address with the resolved one at startup, and
15478 detect our address right before we make a routerinfo each time.
15479 - 'FascistFirewall' option to pick dirservers and ORs on specific
15480 ports; plus 'FirewallPorts' config option to tell FascistFirewall
15481 which ports are open. (Defaults to 80,443)
15482 - Be more aggressive about trying to make circuits when the network
15483 has changed (e.g. when you unsuspend your laptop).
15484 - Check for time skew on http headers; report date in response to
15486 - If the entrynode config line has only one node, don't pick it as
15488 - Add strict{entry|exit}nodes config options. If set to 1, then
15489 we refuse to build circuits that don't include the specified entry
15491 - OutboundBindAddress config option, to bind to a specific
15492 IP address for outgoing connect()s.
15493 - End truncated log entries (e.g. directories) with "[truncated]".
15495 o Patches to 0.0.8preX:
15497 - Patches to compile and run on win32 again (maybe)?
15498 - Fix crash when looking for ~/.torrc with no $HOME set.
15499 - Fix a race bug in the unit tests.
15500 - Handle verified/unverified name collisions better when new
15501 routerinfo's arrive in a directory.
15502 - Sometimes routers were getting entered into the stats before
15503 we'd assigned their identity_digest. Oops.
15504 - Only pick and establish intro points after we've gotten a
15507 - AllowUnverifiedNodes config option to let circuits choose no-name
15508 routers in entry,middle,exit,introduction,rendezvous positions.
15509 Allow middle and rendezvous positions by default.
15510 - Add a man page for tor-resolve.
15513 Changes in version 0.0.7.3 - 2004-08-12
15514 o Stop dnsworkers from triggering an assert failure when you
15515 ask them to resolve the host "".
15518 Changes in version 0.0.8pre3 - 2004-08-09
15519 o Changes from 0.0.7.2:
15520 - Allow multiple ORs with same nickname in routerlist -- now when
15521 people give us one identity key for a nickname, then later
15522 another, we don't constantly complain until the first expires.
15523 - Remember used bandwidth (both in and out), and publish 15-minute
15524 snapshots for the past day into our descriptor.
15525 - You can now fetch $DIRURL/running-routers to get just the
15526 running-routers line, not the whole descriptor list. (But
15527 clients don't use this yet.)
15528 - When people mistakenly use Tor as an http proxy, point them
15529 at the tor-doc.html rather than the INSTALL.
15530 - Remove our mostly unused -- and broken -- hex_encode()
15531 function. Use base16_encode() instead. (Thanks to Timo Lindfors
15532 for pointing out this bug.)
15533 - Rotate onion keys every 12 hours, not every 2 hours, so we have
15534 fewer problems with people using the wrong key.
15535 - Change the default exit policy to reject the default edonkey,
15536 kazaa, gnutella ports.
15537 - Add replace_file() to util.[ch] to handle win32's rename().
15539 o Changes from 0.0.8preX:
15540 - Fix two bugs in saving onion keys to disk when rotating, so
15541 hopefully we'll get fewer people using old onion keys.
15542 - Fix an assert error that was making SocksPolicy not work.
15543 - Be willing to expire routers that have an open dirport -- it's
15544 just the authoritative dirservers we want to not forget.
15545 - Reject tor-resolve requests for .onion addresses early, so we
15546 don't build a whole rendezvous circuit and then fail.
15547 - When you're warning a server that he's unverified, don't cry
15548 wolf unpredictably.
15549 - Fix a race condition: don't try to extend onto a connection
15550 that's still handshaking.
15551 - For servers in clique mode, require the conn to be open before
15552 you'll choose it for your path.
15553 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
15554 end relay cell, etc.
15555 - Measure bandwidth capacity over the last 24 hours, not just 12
15556 - Bugfix: authoritative dirservers were making and signing a new
15557 directory for each client, rather than reusing the cached one.
15560 Changes in version 0.0.8pre2 - 2004-08-04
15561 o Changes from 0.0.7.2:
15563 - Check directory signature _before_ you decide whether you're
15564 you're running an obsolete version and should exit.
15565 - Check directory signature _before_ you parse the running-routers
15566 list to decide who's running or verified.
15567 - Bugfixes and features:
15568 - Check return value of fclose while writing to disk, so we don't
15569 end up with broken files when servers run out of disk space.
15570 - Log a warning if the user uses an unsafe socks variant, so people
15571 are more likely to learn about privoxy or socat.
15572 - Dirservers now include RFC1123-style dates in the HTTP headers,
15573 which one day we will use to better detect clock skew.
15575 o Changes from 0.0.8pre1:
15576 - Make it compile without warnings again on win32.
15577 - Log a warning if you're running an unverified server, to let you
15578 know you might want to get it verified.
15579 - Only pick a default nickname if you plan to be a server.
15582 Changes in version 0.0.8pre1 - 2004-07-23
15584 - Made our unit tests compile again on OpenBSD 3.5, and tor
15585 itself compile again on OpenBSD on a sparc64.
15586 - We were neglecting milliseconds when logging on win32, so
15587 everything appeared to happen at the beginning of each second.
15589 o Protocol changes:
15590 - 'Extend' relay cell payloads now include the digest of the
15591 intended next hop's identity key. Now we can verify that we're
15592 extending to the right router, and also extend to routers we
15593 hadn't heard of before.
15596 - Tor nodes can now act as relays (with an advertised ORPort)
15597 without being manually verified by the dirserver operators.
15598 - Uploaded descriptors of unverified routers are now accepted
15599 by the dirservers, and included in the directory.
15600 - Verified routers are listed by nickname in the running-routers
15601 list; unverified routers are listed as "$<fingerprint>".
15602 - We now use hash-of-identity-key in most places rather than
15603 nickname or addr:port, for improved security/flexibility.
15604 - To avoid Sybil attacks, paths still use only verified servers.
15605 But now we have a chance to play around with hybrid approaches.
15606 - Nodes track bandwidth usage to estimate capacity (not used yet).
15607 - ClientOnly option for nodes that never want to become servers.
15608 - Directory caching.
15609 - "AuthoritativeDir 1" option for the official dirservers.
15610 - Now other nodes (clients and servers) will cache the latest
15611 directory they've pulled down.
15612 - They can enable their DirPort to serve it to others.
15613 - Clients will pull down a directory from any node with an open
15614 DirPort, and check the signature/timestamp correctly.
15615 - Authoritative dirservers now fetch directories from other
15616 authdirservers, to stay better synced.
15617 - Running-routers list tells who's down also, along with noting
15618 if they're verified (listed by nickname) or unverified (listed
15620 - Allow dirservers to serve running-router list separately.
15621 This isn't used yet.
15622 - ORs connect-on-demand to other ORs
15623 - If you get an extend cell to an OR you're not connected to,
15624 connect, handshake, and forward the create cell.
15625 - The authoritative dirservers stay connected to everybody,
15626 and everybody stays connected to 0.0.7 servers, but otherwise
15627 clients/servers expire unused connections after 5 minutes.
15628 - When servers get a sigint, they delay 30 seconds (refusing new
15629 connections) then exit. A second sigint causes immediate exit.
15630 - File and name management:
15631 - Look for .torrc if no CONFDIR "torrc" is found.
15632 - If no datadir is defined, then choose, make, and secure ~/.tor
15634 - If torrc not found, exitpolicy reject *:*.
15635 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
15636 - If no nickname is defined, derive default from hostname.
15637 - Rename secret key files, e.g. identity.key -> secret_id_key,
15638 to discourage people from mailing their identity key to tor-ops.
15639 - Refuse to build a circuit before the directory has arrived --
15640 it won't work anyway, since you won't know the right onion keys
15642 - Try other dirservers immediately if the one you try is down. This
15643 should tolerate down dirservers better now.
15644 - Parse tor version numbers so we can do an is-newer-than check
15645 rather than an is-in-the-list check.
15646 - New socks command 'resolve', to let us shim gethostbyname()
15648 - A 'tor_resolve' script to access the socks resolve functionality.
15649 - A new socks-extensions.txt doc file to describe our
15650 interpretation and extensions to the socks protocols.
15651 - Add a ContactInfo option, which gets published in descriptor.
15652 - Publish OR uptime in descriptor (and thus in directory) too.
15653 - Write tor version at the top of each log file
15654 - New docs in the tarball:
15656 - Document that you should proxy your SSL traffic too.
15659 Changes in version 0.0.7.2 - 2004-07-07
15660 o A better fix for the 0.0.0.0 problem, that will hopefully
15661 eliminate the remaining related assertion failures.
15664 Changes in version 0.0.7.1 - 2004-07-04
15665 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
15666 since internally we use 0.0.0.0 to signify "not yet resolved".
15669 Changes in version 0.0.7 - 2004-06-07
15670 o Updated the man page to reflect the new features.
15673 Changes in version 0.0.7rc2 - 2004-06-06
15674 o Changes from 0.0.7rc1:
15675 - Make it build on Win32 again.
15676 o Changes from 0.0.6.2:
15677 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
15681 Changes in version 0.0.7rc1 - 2004-06-02
15683 - On sighup, we were adding another log without removing the first
15684 one. So log messages would get duplicated n times for n sighups.
15685 - Several cases of using a connection after we'd freed it. The
15686 problem was that connections that are pending resolve are in both
15687 the pending_resolve tree, and also the circuit's resolving_streams
15688 list. When you want to remove one, you must remove it from both.
15689 - Fix a double-mark-for-close where an end cell arrived for a
15690 resolving stream, and then the resolve failed.
15691 - Check directory signatures based on name of signer, not on whom
15692 we got the directory from. This will let us cache directories more
15695 - Crank up some of our constants to handle more users.
15698 Changes in version 0.0.7pre1 - 2004-06-02
15699 o Fixes for crashes and other obnoxious bugs:
15700 - Fix an epipe bug: sometimes when directory connections failed
15701 to connect, we would give them a chance to flush before closing
15703 - When we detached from a circuit because of resolvefailed, we
15704 would immediately try the same circuit twice more, and then
15705 give up on the resolve thinking we'd tried three different
15707 - Limit the number of intro circuits we'll attempt to build for a
15708 hidden service per 15-minute period.
15709 - Check recommended-software string *early*, before actually parsing
15710 the directory. Thus we can detect an obsolete version and exit,
15711 even if the new directory format doesn't parse.
15712 o Fixes for security bugs:
15713 - Remember which nodes are dirservers when you startup, and if a
15714 random OR enables his dirport, don't automatically assume he's
15715 a trusted dirserver.
15717 - Directory connections were asking the wrong poll socket to
15718 start writing, and not asking themselves to start writing.
15719 - When we detached from a circuit because we sent a begin but
15720 didn't get a connected, we would use it again the first time;
15721 but after that we would correctly switch to a different one.
15722 - Stop warning when the first onion decrypt attempt fails; they
15723 will sometimes legitimately fail now that we rotate keys.
15724 - Override unaligned-access-ok check when $host_cpu is ia64 or
15725 arm. Apparently they allow it but the kernel whines.
15726 - Dirservers try to reconnect periodically too, in case connections
15728 - Fix some memory leaks in directory servers.
15729 - Allow backslash in Win32 filenames.
15730 - Made Tor build complain-free on FreeBSD, hopefully without
15731 breaking other BSD builds. We'll see.
15733 - Doxygen markup on all functions and global variables.
15734 - Make directory functions update routerlist, not replace it. So
15735 now directory disagreements are not so critical a problem.
15736 - Remove the upper limit on number of descriptors in a dirserver's
15737 directory (not that we were anywhere close).
15738 - Allow multiple logfiles at different severity ranges.
15739 - Allow *BindAddress to specify ":port" rather than setting *Port
15740 separately. Allow multiple instances of each BindAddress config
15741 option, so you can bind to multiple interfaces if you want.
15742 - Allow multiple exit policy lines, which are processed in order.
15743 Now we don't need that huge line with all the commas in it.
15744 - Enable accept/reject policies on SOCKS connections, so you can bind
15745 to 0.0.0.0 but still control who can use your OP.
15748 Changes in version 0.0.6.2 - 2004-05-16
15749 o Our integrity-checking digest was checking only the most recent cell,
15750 not the previous cells like we'd thought.
15751 Thanks to Stefan Mark for finding the flaw!
15754 Changes in version 0.0.6.1 - 2004-05-06
15755 o Fix two bugs in our AES counter-mode implementation (this affected
15756 onion-level stream encryption, but not TLS-level). It turns
15757 out we were doing something much more akin to a 16-character
15758 polyalphabetic cipher. Oops.
15759 Thanks to Stefan Mark for finding the flaw!
15760 o Retire moria3 as a directory server, and add tor26 as a directory
15764 Changes in version 0.0.6 - 2004-05-02
15765 [version bump only]
15768 Changes in version 0.0.6rc4 - 2004-05-01
15769 o Update the built-in dirservers list to use the new directory format
15770 o Fix a rare seg fault: if a node offering a hidden service attempts
15771 to build a circuit to Alice's rendezvous point and fails before it
15772 reaches the last hop, it retries with a different circuit, but
15774 o Handle windows socket errors correctly.
15777 Changes in version 0.0.6rc3 - 2004-04-28
15778 o Don't expire non-general excess circuits (if we had enough
15779 circuits open, we were expiring rendezvous circuits -- even
15780 when they had a stream attached. oops.)
15781 o Fetch randomness from /dev/urandom better (not via fopen/fread)
15782 o Better debugging for tls errors
15783 o Some versions of openssl have an SSL_pending function that erroneously
15784 returns bytes when there is a non-application record pending.
15785 o Set Content-Type on the directory and hidserv descriptor.
15786 o Remove IVs from cipher code, since AES-ctr has none.
15787 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
15788 o We were using an array of length zero in a few places.
15789 o win32's gethostbyname can't resolve an IP to an IP.
15790 o win32's close can't close a socket.
15793 Changes in version 0.0.6rc2 - 2004-04-26
15794 o Fix a bug where we were closing tls connections intermittently.
15795 It turns out openssl keeps its errors around -- so if an error
15796 happens, and you don't ask about it, and then another openssl
15797 operation happens and succeeds, and you ask if there was an error,
15798 it tells you about the first error. Fun fun.
15799 o Fix a bug that's been lurking since 27 may 03 (!)
15800 When passing back a destroy cell, we would use the wrong circ id.
15801 'Mostly harmless', but still worth fixing.
15802 o Since we don't support truncateds much, don't bother sending them;
15803 just close the circ.
15804 o check for <machine/limits.h> so we build on NetBSD again (I hope).
15805 o don't crash if a conn that sent a begin has suddenly lost its circuit
15806 (this was quite rare).
15809 Changes in version 0.0.6rc1 - 2004-04-25
15810 o We now rotate link (tls context) keys and onion keys.
15811 o CREATE cells now include oaep padding, so you can tell
15812 if you decrypted them correctly.
15813 o Add bandwidthburst to server descriptor.
15814 o Directories now say which dirserver signed them.
15815 o Use a tor_assert macro that logs failed assertions too.
15818 Changes in version 0.0.6pre5 - 2004-04-18
15819 o changes from 0.0.6pre4:
15820 - make tor build on broken freebsd 5.2 installs
15821 - fix a failed assert when you try an intro point, get a nack, and try
15822 a second one and it works.
15823 - when alice uses a port that the hidden service doesn't accept,
15824 it now sends back an end cell (denied by exit policy). otherwise
15825 alice would just have to wait to time out.
15826 - fix another rare bug: when we had tried all the intro
15827 points for a hidden service, we fetched the descriptor
15828 again, but we left our introcirc thinking it had already
15829 sent an intro, so it kept waiting for a response...
15830 - bugfix: when you sleep your hidden-service laptop, as soon
15831 as it wakes up it tries to upload a service descriptor, but
15832 socketpair fails for some reason (localhost not up yet?).
15833 now we simply give up on that upload, and we'll try again later.
15834 i'd still like to find the bug though.
15835 - if an intro circ waiting for an ack dies before getting one, then
15837 - we were reusing stale service descriptors and refetching usable
15841 Changes in version 0.0.6pre4 - 2004-04-14
15842 o changes from 0.0.6pre3:
15843 - when bob fails to connect to the rendezvous point, and his
15844 circ didn't fail because of the rendezvous point itself, then
15845 he retries a couple of times
15846 - we expire introduction and rendezvous circs more thoroughly
15847 (sometimes they were hanging around forever)
15848 - we expire unattached rendezvous streams that have been around
15849 too long (they were sticking around forever).
15850 - fix a measly fencepost error that was crashing everybody with
15854 Changes in version 0.0.6pre3 - 2004-04-14
15855 o changes from 0.0.6pre2:
15856 - make hup work again
15857 - fix some memory leaks for dirservers
15858 - allow more skew in rendezvous descriptor timestamps, to help
15859 handle people like blanu who don't know what time it is
15860 - normal circs are 3 hops, but some rend/intro circs are 4, if
15861 the initiator doesn't get to choose the last hop
15862 - send acks for introductions, so alice can know whether to try
15864 - bob publishes intro points more correctly
15865 o changes from 0.0.5:
15866 - fix an assert trigger that's been plaguing us since the days
15867 of 0.0.2prexx (thanks weasel!)
15868 - retry stream correctly when we fail to connect because of
15869 exit-policy-reject (should try another) or can't-resolve-address
15870 (also should try another, because dns on random internet servers
15872 - when we hup a dirserver and we've *removed* a server from the
15873 approved-routers list, now we remove that server from the
15874 in-memory directories too
15877 Changes in version 0.0.6pre2 - 2004-04-08
15878 o We fixed our base32 implementation. Now it works on all architectures.
15881 Changes in version 0.0.6pre1 - 2004-04-08
15883 - Hidden services and rendezvous points are implemented. Go to
15884 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
15885 hidden services. (This only works via a socks4a proxy such as
15886 Privoxy, and currently it's quite slow.)
15889 Changes in version 0.0.5 - 2004-03-30
15890 [version bump only]
15893 Changes in version 0.0.5rc3 - 2004-03-29
15894 o Install torrc as torrc.sample -- we no longer clobber your
15896 o Re-enable recommendedversion checking (we broke it in rc2, oops)
15897 o Add in a 'notice' log level for things the operator should hear
15898 but that aren't warnings
15901 Changes in version 0.0.5rc2 - 2004-03-29
15902 o Hold socks connection open until reply is flushed (if possible)
15903 o Make exit nodes resolve IPs to IPs immediately, rather than asking
15904 the dns farm to do it.
15905 o Fix c99 aliasing warnings in rephist.c
15906 o Don't include server descriptors that are older than 24 hours in the
15908 o Give socks 'reject' replies their whole 15s to attempt to flush,
15909 rather than seeing the 60s timeout and assuming the flush had failed.
15910 o Clean automake droppings from the cvs repository
15913 Changes in version 0.0.5rc1 - 2004-03-28
15914 o Fix mangled-state bug in directory fetching (was causing sigpipes).
15915 o Only build circuits after we've fetched the directory: clients were
15916 using only the directory servers before they'd fetched a directory.
15917 This also means longer startup time; so it goes.
15918 o Fix an assert trigger where an OP would fail to handshake, and we'd
15919 expect it to have a nickname.
15920 o Work around a tsocks bug: do a socks reject when AP connection dies
15921 early, else tsocks goes into an infinite loop.
15924 Changes in version 0.0.4 - 2004-03-26
15925 o When connecting to a dirserver or OR and the network is down,
15929 Changes in version 0.0.3 - 2004-03-26
15930 o Warn and fail if server chose a nickname with illegal characters
15931 o Port to Solaris and Sparc:
15932 - include missing header fcntl.h
15933 - have autoconf find -lsocket -lnsl automatically
15934 - deal with hardware word alignment
15935 - make uname() work (solaris has a different return convention)
15936 - switch from using signal() to sigaction()
15937 o Preliminary work on reputation system:
15938 - Keep statistics on success/fail of connect attempts; they're published
15939 by kill -USR1 currently.
15940 - Add a RunTesting option to try to learn link state by creating test
15941 circuits, even when SocksPort is off.
15942 - Remove unused open circuits when there are too many.
15945 Changes in version 0.0.2 - 2004-03-19
15946 - Include strlcpy and strlcat for safer string ops
15947 - define INADDR_NONE so we compile (but still not run) on solaris
15950 Changes in version 0.0.2pre27 - 2004-03-14
15952 - Allow internal tor networks (we were rejecting internal IPs,
15953 now we allow them if they're set explicitly).
15954 - And fix a few endian issues.
15957 Changes in version 0.0.2pre26 - 2004-03-14
15959 - If a stream times out after 15s without a connected cell, don't
15960 try that circuit again: try a new one.
15961 - Retry streams at most 4 times. Then give up.
15962 - When a dirserver gets a descriptor from an unknown router, it
15963 logs its fingerprint (so the dirserver operator can choose to
15964 accept it even without mail from the server operator).
15965 - Inform unapproved servers when we reject their descriptors.
15966 - Make tor build on Windows again. It works as a client, who knows
15968 - Clearer instructions in the torrc for how to set up a server.
15969 - Be more efficient about reading fd's when our global token bucket
15970 (used for rate limiting) becomes empty.
15972 - Stop asserting that computers always go forward in time. It's
15974 - When we sent a cell (e.g. destroy) and then marked an OR connection
15975 expired, we might close it before finishing a flush if the other
15976 side isn't reading right then.
15977 - Don't allow dirservers to start if they haven't defined
15978 RecommendedVersions
15979 - We were caching transient dns failures. Oops.
15980 - Prevent servers from publishing an internal IP as their address.
15981 - Address a strcat vulnerability in circuit.c
15984 Changes in version 0.0.2pre25 - 2004-03-04
15986 - Put the OR's IP in its router descriptor, not its fqdn. That way
15987 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15990 - If the user typed in an address that didn't resolve, the server
15994 Changes in version 0.0.2pre24 - 2004-03-03
15996 - Fix an assertion failure in dns.c, where we were trying to dequeue
15997 a pending dns resolve even if it wasn't pending
15998 - Fix a spurious socks5 warning about still trying to write after the
15999 connection is finished.
16000 - Hold certain marked_for_close connections open until they're finished
16001 flushing, rather than losing bytes by closing them too early.
16002 - Correctly report the reason for ending a stream
16003 - Remove some duplicate calls to connection_mark_for_close
16004 - Put switch_id and start_daemon earlier in the boot sequence, so it
16005 will actually try to chdir() to options.DataDirectory
16006 - Make 'make test' exit(1) if a test fails; fix some unit tests
16007 - Make tor fail when you use a config option it doesn't know about,
16008 rather than warn and continue.
16009 - Make --version work
16010 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
16013 Changes in version 0.0.2pre23 - 2004-02-29
16015 - Print a statement when the first circ is finished, so the user
16016 knows it's working.
16017 - If a relay cell is unrecognized at the end of the circuit,
16018 send back a destroy. (So attacks to mutate cells are more
16020 - New config option 'excludenodes' to avoid certain nodes for circuits.
16021 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
16022 so you can collect coredumps there.
16024 - Fix a bug in tls flushing where sometimes data got wedged and
16025 didn't flush until more data got sent. Hopefully this bug was
16026 a big factor in the random delays we were seeing.
16027 - Make 'connected' cells include the resolved IP, so the client
16028 dns cache actually gets populated.
16029 - Disallow changing from ORPort=0 to ORPort>0 on hup.
16030 - When we time-out on a stream and detach from the circuit, send an
16031 end cell down it first.
16032 - Only warn about an unknown router (in exitnodes, entrynodes,
16033 excludenodes) after we've fetched a directory.
16036 Changes in version 0.0.2pre22 - 2004-02-26
16038 - Servers publish less revealing uname information in descriptors.
16039 - More memory tracking and assertions, to crash more usefully when
16041 - If the default torrc isn't there, just use some default defaults.
16042 Plus provide an internal dirservers file if they don't have one.
16043 - When the user tries to use Tor as an http proxy, give them an http
16044 501 failure explaining that we're a socks proxy.
16045 - Dump a new router.desc on hup, to help confused people who change
16046 their exit policies and then wonder why router.desc doesn't reflect
16048 - Clean up the generic tor.sh init script that we ship with.
16050 - If the exit stream is pending on the resolve, and a destroy arrives,
16051 then the stream wasn't getting removed from the pending list. I
16052 think this was the one causing recent server crashes.
16053 - Use a more robust poll on OSX 10.3, since their poll is flaky.
16054 - When it couldn't resolve any dirservers, it was useless from then on.
16055 Now it reloads the RouterFile (or default dirservers) if it has no
16057 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
16058 many users don't even *have* a /usr/local/sbin/.
16061 Changes in version 0.0.2pre21 - 2004-02-18
16063 - There's a ChangeLog file that actually reflects the changelog.
16064 - There's a 'torify' wrapper script, with an accompanying
16065 tor-tsocks.conf, that simplifies the process of using tsocks for
16066 tor. It even has a man page.
16067 - The tor binary gets installed to sbin rather than bin now.
16068 - Retry streams where the connected cell hasn't arrived in 15 seconds
16069 - Clean up exit policy handling -- get the default out of the torrc,
16070 so we can update it without forcing each server operator to fix
16072 - Allow imaps and pop3s in default exit policy
16074 - Prevent picking middleman nodes as the last node in the circuit
16077 Changes in version 0.0.2pre20 - 2004-01-30
16079 - We now have a deb package, and it's in debian unstable. Go to
16080 it, apt-getters. :)
16081 - I've split the TotalBandwidth option into BandwidthRate (how many
16082 bytes per second you want to allow, long-term) and
16083 BandwidthBurst (how many bytes you will allow at once before the cap
16084 kicks in). This better token bucket approach lets you, say, set
16085 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
16086 performance while not exceeding your monthly bandwidth quota.
16087 - Push out a tls record's worth of data once you've got it, rather
16088 than waiting until you've read everything waiting to be read. This
16089 may improve performance by pipelining better. We'll see.
16090 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
16091 from failed circuits (if they haven't been connected yet) and attach
16093 - Expire old streams that haven't managed to connect. Some day we'll
16094 have them reattach to new circuits instead.
16097 - Fix several memory leaks that were causing servers to become bloated
16099 - Fix a few very rare assert triggers. A few more remain.
16100 - Setuid to User _before_ complaining about running as root.
16103 Changes in version 0.0.2pre19 - 2004-01-07
16105 - Fix deadlock condition in dns farm. We were telling a child to die by
16106 closing the parent's file descriptor to him. But newer children were
16107 inheriting the open file descriptor from the parent, and since they
16108 weren't closing it, the socket never closed, so the child never read
16109 eof, so he never knew to exit. Similarly, dns workers were holding
16110 open other sockets, leading to all sorts of chaos.
16111 - New cleaner daemon() code for forking and backgrounding.
16112 - If you log to a file, it now prints an entry at the top of the
16113 logfile so you know it's working.
16114 - The onionskin challenge length was 30 bytes longer than necessary.
16115 - Started to patch up the spec so it's not quite so out of date.
16118 Changes in version 0.0.2pre18 - 2004-01-02
16120 - Fix endian issues with the 'integrity' field in the relay header.
16121 - Fix a potential bug where connections in state
16122 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
16125 Changes in version 0.0.2pre17 - 2003-12-30
16127 - Made --debuglogfile (or any second log file, actually) work.
16128 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
16129 adversary could force us into an infinite loop.
16132 - Each onionskin handshake now includes a hash of the computed key,
16133 to prove the server's identity and help perfect forward secrecy.
16134 - Changed cell size from 256 to 512 bytes (working toward compatibility
16136 - Changed cell length to 2 bytes, and moved it to the relay header.
16137 - Implemented end-to-end integrity checking for the payloads of
16139 - Separated streamid from 'recognized' (otherwise circuits will get
16140 messed up when we try to have streams exit from the middle). We
16141 use the integrity-checking to confirm that a cell is addressed to
16143 - Randomize the initial circid and streamid values, so an adversary who
16144 breaks into a node can't learn how many circuits or streams have
16148 Changes in version 0.0.2pre16 - 2003-12-14
16150 - Fixed a bug that made HUP trigger an assert
16151 - Fixed a bug where a circuit that immediately failed wasn't being
16152 counted as a failed circuit in counting retries.
16155 - Now we close the circuit when we get a truncated cell: otherwise we're
16156 open to an anonymity attack where a bad node in the path truncates
16157 the circuit and then we open streams at him.
16158 - Add port ranges to exit policies
16159 - Add a conservative default exit policy
16160 - Warn if you're running tor as root
16161 - on HUP, retry OR connections and close/rebind listeners
16162 - options.EntryNodes: try these nodes first when picking the first node
16163 - options.ExitNodes: if your best choices happen to include any of
16164 your preferred exit nodes, you choose among just those preferred
16166 - options.ExcludedNodes: nodes that are never picked in path building
16169 Changes in version 0.0.2pre15 - 2003-12-03
16170 o Robustness and bugfixes:
16171 - Sometimes clients would cache incorrect DNS resolves, which would
16172 really screw things up.
16173 - An OP that goes offline would slowly leak all its sockets and stop
16175 - A wide variety of bugfixes in exit node selection, exit policy
16176 handling, and processing pending streams when a new circuit is
16178 - Pick nodes for a path only from those the directory says are up
16179 - Choose randomly from all running dirservers, not always the first one
16180 - Increase allowed http header size for directory fetch.
16181 - Stop writing to stderr (if we're daemonized it will be closed).
16182 - Enable -g always, so cores will be more useful to me.
16183 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
16186 - Wrote a man page. It lists commonly used options.
16189 - Change default loglevel to warn.
16190 - Make PidFile default to null rather than littering in your CWD.
16191 - OnionRouter config option is now obsolete. Instead it just checks
16193 - Moved to a single unified torrc file for both clients and servers.
16196 Changes in version 0.0.2pre14 - 2003-11-29
16197 o Robustness and bugfixes:
16198 - Force the admin to make the DataDirectory himself
16199 - to get ownership/permissions right
16200 - so clients no longer make a DataDirectory and then never use it
16201 - fix bug where a client who was offline for 45 minutes would never
16202 pull down a directory again
16203 - fix (or at least hide really well) the dns assert bug that was
16204 causing server crashes
16205 - warnings and improved robustness wrt clockskew for certs
16206 - use the native daemon(3) to daemonize, when available
16207 - exit if bind() fails
16208 - exit if neither socksport nor orport is defined
16209 - include our own tor_timegm (Win32 doesn't have its own)
16210 - bugfix for win32 with lots of connections
16211 - fix minor bias in PRNG
16212 - make dirserver more robust to corrupt cached directory
16215 - Wrote the design document (woo)
16217 o Circuit building and exit policies:
16218 - Circuits no longer try to use nodes that the directory has told them
16220 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
16221 bitcounts (18.0.0.0/8).
16222 - Make AP connections standby for a circuit if no suitable circuit
16223 exists, rather than failing
16224 - Circuits choose exit node based on addr/port, exit policies, and
16225 which AP connections are standing by
16226 - Bump min pathlen from 2 to 3
16227 - Relay end cells have a payload to describe why the stream ended.
16228 - If the stream failed because of exit policy, try again with a new
16230 - Clients have a dns cache to remember resolved addresses.
16231 - Notice more quickly when we have no working circuits
16234 - APPort is now called SocksPort
16235 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
16237 - RecommendedVersions is now a config variable rather than
16238 hardcoded (for dirservers)
16239 - Reloads config on HUP
16240 - Usage info on -h or --help
16241 - If you set User and Group config vars, it'll setu/gid to them.
16244 Changes in version 0.0.2pre13 - 2003-10-19
16245 o General stability:
16246 - SSL_write no longer fails when it returns WANTWRITE and the number
16247 of bytes in the buf has changed by the next SSL_write call.
16248 - Fix segfault fetching directory when network is down
16249 - Fix a variety of minor memory leaks
16250 - Dirservers reload the fingerprints file on HUP, so I don't have
16251 to take down the network when I approve a new router
16252 - Default server config file has explicit Address line to specify fqdn
16255 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
16256 - Make listener connections not ever alloc bufs
16258 o Autoconf improvements:
16259 - don't clobber an external CFLAGS in ./configure
16260 - Make install now works
16261 - create var/lib/tor on make install
16262 - autocreate a tor.sh initscript to help distribs
16263 - autocreate the torrc and sample-server-torrc with correct paths
16265 o Log files and Daemonizing now work:
16266 - If --DebugLogFile is specified, log to it at -l debug
16267 - If --LogFile is specified, use it instead of commandline
16268 - If --RunAsDaemon is set, tor forks and backgrounds on startup