1 Changes in version 0.3.2.9 - 2018-01-09
2 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
6 Per our stable release policy, we plan to support each stable release
7 series for at least the next nine months, or for three months after
8 the first stable release of the next series: whichever is longer. If
9 you need a release with long-term support, we recommend that you stay
10 with the 0.2.9 series.
12 Below is a list of the changes since 0.3.2.8-rc. For a list of all
13 changes since 0.3.1, see the ReleaseNotes file.
15 o Minor features (fallback directory mirrors):
16 - The fallback directory list has been re-generated based on the
17 current status of the network. Tor uses fallback directories to
18 bootstrap when it doesn't yet have up-to-date directory
19 information. Closes ticket 24801.
20 - Make the default DirAuthorityFallbackRate 0.1, so that clients
21 prefer to bootstrap from fallback directory mirrors. This is a
22 follow-up to 24679, which removed weights from the default
23 fallbacks. Implements ticket 24681.
25 o Minor features (geoip):
26 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
29 o Minor bugfixes (address selection):
30 - When the fascist_firewall_choose_address_ functions don't find a
31 reachable address, set the returned address to the null address
32 and port. This is a precautionary measure, because some callers do
33 not check the return value. Fixes bug 24736; bugfix
36 o Minor bugfixes (compilation):
37 - Resolve a few shadowed-variable warnings in the onion service
38 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
40 o Minor bugfixes (portability, msvc):
41 - Fix a bug in the bit-counting parts of our timing-wheel code on
42 MSVC. (Note that MSVC is still not a supported build platform, due
43 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
47 Changes in version 0.3.2.8-rc - 2017-12-21
48 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
49 schedulers that had led servers under heavy load to overload their
50 outgoing connections. All relay operators running earlier 0.3.2.x
51 versions should upgrade. This version also includes a mitigation for
52 over-full DESTROY queues leading to out-of-memory conditions: if it
53 works, we will soon backport it to earlier release series.
55 This is the second release candidate in the 0.3.2 series. If we find
56 no new bugs or regression here, then the first stable 0.3.2 release
57 will be nearly identical to this.
59 o Major bugfixes (KIST, scheduler):
60 - The KIST scheduler did not correctly account for data already
61 enqueued in each connection's send socket buffer, particularly in
62 cases when the TCP/IP congestion window was reduced between
63 scheduler calls. This situation lead to excessive per-connection
64 buffering in the kernel, and a potential memory DoS. Fixes bug
65 24665; bugfix on 0.3.2.1-alpha.
67 o Minor features (geoip):
68 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
71 o Minor bugfixes (hidden service v3):
72 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
73 the probability of reaching a service for a client missing
74 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
76 o Minor bugfixes (memory usage):
77 - When queuing DESTROY cells on a channel, only queue the circuit-id
78 and reason fields: not the entire 514-byte cell. This fix should
79 help mitigate any bugs or attacks that fill up these queues, and
80 free more RAM for other uses. Fixes bug 24666; bugfix
83 o Minor bugfixes (scheduler, KIST):
84 - Use a sane write limit for KISTLite when writing onto a connection
85 buffer instead of using INT_MAX and shoving as much as it can.
86 Because the OOM handler cleans up circuit queues, we are better
87 off at keeping them in that queue instead of the connection's
88 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
91 Changes in version 0.3.2.7-rc - 2017-12-14
92 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
93 including some that could affect reliability or correctness.
95 This is the first release candidate in the 0.3.2 series. If we find no
96 new bugs or regression here, then the first stable 0.3.2. release will
97 be nearly identical to this.
99 o Major bugfixes (circuit prediction):
100 - Fix circuit prediction logic so that a client doesn't treat a port
101 as being "handled" by a circuit if that circuit already has
102 isolation settings on it. This change should make Tor clients more
103 responsive by improving their chances of having a pre-created
104 circuit ready for use when a request arrives. Fixes bug 18859;
105 bugfix on 0.2.3.3-alpha.
107 o Minor features (logging):
108 - Provide better warnings when the getrandom() syscall fails. Closes
111 o Minor features (portability):
112 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
113 (It doesn't yet work with the sandbox enabled.) Closes
116 o Minor bugfixes (bridge clients, bootstrap):
117 - Retry directory downloads when we get our first bridge descriptor
118 during bootstrap or while reconnecting to the network. Keep
119 retrying every time we get a bridge descriptor, until we have a
120 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
121 - Stop delaying bridge descriptor fetches when we have cached bridge
122 descriptors. Instead, only delay bridge descriptor fetches when we
123 have at least one reachable bridge. Fixes part of bug 24367;
124 bugfix on 0.2.0.3-alpha.
125 - Stop delaying directory fetches when we have cached bridge
126 descriptors. Instead, only delay bridge descriptor fetches when
127 all our bridges are definitely unreachable. Fixes part of bug
128 24367; bugfix on 0.2.0.3-alpha.
130 o Minor bugfixes (compilation):
131 - Fix a signed/unsigned comparison warning introduced by our fix to
132 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
134 o Minor bugfixes (correctness):
135 - Fix several places in our codebase where a C compiler would be
136 likely to eliminate a check, based on assuming that undefined
137 behavior had not happened elsewhere in the code. These cases are
138 usually a sign of redundant checking or dubious arithmetic. Found
139 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
140 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
143 o Minor bugfixes (onion service v3):
144 - Fix a race where an onion service would launch a new intro circuit
145 after closing an old one, but fail to register it before freeing
146 the previously closed circuit. This bug was making the service
147 unable to find the established intro circuit and thus not upload
148 its descriptor, thus making a service unavailable for up to 24
149 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
151 o Minor bugfixes (scheduler, KIST):
152 - Properly set the scheduler state of an unopened channel in the
153 KIST scheduler main loop. This prevents a harmless but annoying
154 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
155 - Avoid a possible integer overflow when computing the available
156 space on the TCP buffer of a channel. This had no security
157 implications; but could make KIST allow too many cells on a
158 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
159 - Downgrade to "info" a harmless warning about the monotonic time
160 moving backwards: This can happen on platform not supporting
161 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
164 Changes in version 0.3.2.6-alpha - 2017-12-01
165 This version of Tor is the latest in the 0.3.2 alpha series. It
166 includes fixes for several important security issues. All Tor users
167 should upgrade to this release, or to one of the other releases coming
170 o Major bugfixes (security):
171 - Fix a denial of service bug where an attacker could use a
172 malformed directory object to cause a Tor instance to pause while
173 OpenSSL would try to read a passphrase from the terminal. (Tor
174 instances run without a terminal, which is the case for most Tor
175 packages, are not impacted.) Fixes bug 24246; bugfix on every
176 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
177 Found by OSS-Fuzz as testcase 6360145429790720.
178 - Fix a denial of service issue where an attacker could crash a
179 directory authority using a malformed router descriptor. Fixes bug
180 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
182 - When checking for replays in the INTRODUCE1 cell data for a
183 (legacy) onion service, correctly detect replays in the RSA-
184 encrypted part of the cell. We were previously checking for
185 replays on the entire cell, but those can be circumvented due to
186 the malleability of Tor's legacy hybrid encryption. This fix helps
187 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
188 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
191 o Major bugfixes (security, onion service v2):
192 - Fix a use-after-free error that could crash v2 Tor onion services
193 when they failed to open circuits while expiring introduction
194 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
195 also tracked as TROVE-2017-013 and CVE-2017-8823.
197 o Major bugfixes (security, relay):
198 - When running as a relay, make sure that we never build a path
199 through ourselves, even in the case where we have somehow lost the
200 version of our descriptor appearing in the consensus. Fixes part
201 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
202 as TROVE-2017-012 and CVE-2017-8822.
203 - When running as a relay, make sure that we never choose ourselves
204 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
205 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
207 o Minor feature (relay statistics):
208 - Change relay bandwidth reporting stats interval from 4 hours to 24
209 hours in order to reduce the efficiency of guard discovery
210 attacks. Fixes ticket 23856.
212 o Minor features (directory authority):
213 - Add an IPv6 address for the "bastet" directory authority. Closes
216 o Minor bugfixes (client):
217 - By default, do not enable storage of client-side DNS values. These
218 values were unused by default previously, but they should not have
219 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
222 Changes in version 0.3.2.5-alpha - 2017-11-22
223 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
224 fixes several stability and reliability bugs, including a fix for
225 intermittent bootstrapping failures that some people have been seeing
226 since the 0.3.0.x series.
228 Please test this alpha out -- many of these fixes will soon be
229 backported to stable Tor versions if no additional bugs are found
232 o Major bugfixes (bootstrapping):
233 - Fetch descriptors aggressively whenever we lack enough to build
234 circuits, regardless of how many descriptors we are missing.
235 Previously, we would delay launching the fetch when we had fewer
236 than 15 missing descriptors, even if some of those descriptors
237 were blocking circuits from building. Fixes bug 23985; bugfix on
238 0.1.1.11-alpha. The effects of this bug became worse in
239 0.3.0.3-alpha, when we began treating missing descriptors from our
240 primary guards as a reason to delay circuits.
241 - Don't try fetching microdescriptors from relays that have failed
242 to deliver them in the past. Fixes bug 23817; bugfix
245 o Minor features (directory authority):
246 - Make the "Exit" flag assignment only depend on whether the exit
247 policy allows connections to ports 80 and 443. Previously relays
248 would get the Exit flag if they allowed connections to one of
249 these ports and also port 6667. Resolves ticket 23637.
251 o Minor features (geoip):
252 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
255 o Minor features (linux seccomp2 sandbox):
256 - Update the sandbox rules so that they should now work correctly
257 with Glibc 2.26. Closes ticket 24315.
259 o Minor features (logging):
260 - Downgrade a pair of log messages that could occur when an exit's
261 resolver gave us an unusual (but not forbidden) response. Closes
263 - Improve the message we log when re-enabling circuit build timeouts
264 after having received a consensus. Closes ticket 20963.
266 o Minor bugfixes (compilation):
267 - Fix a memory leak warning in one of the libevent-related
268 configuration tests that could occur when manually specifying
269 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
270 Found and patched by Alex Xu.
271 - When detecting OpenSSL on Windows from our configure script, make
272 sure to try linking with the ws2_32 library. Fixes bug 23783;
273 bugfix on 0.3.2.2-alpha.
275 o Minor bugfixes (control port, linux seccomp2 sandbox):
276 - Avoid a crash when attempting to use the seccomp2 sandbox together
277 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
280 o Minor bugfixes (control port, onion services):
281 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
282 HS_DESC event when a service is not able to upload a descriptor.
283 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
285 o Minor bugfixes (directory cache):
286 - Recover better from empty or corrupt files in the consensus cache
287 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
288 - When a consensus diff calculation is only partially successful,
289 only record the successful parts as having succeeded. Partial
290 success can happen if (for example) one compression method fails
291 but the others succeed. Previously we misrecorded all the
292 calculations as having succeeded, which would later cause a
293 nonfatal assertion failure. Fixes bug 24086; bugfix
296 o Minor bugfixes (logging):
297 - Only log once if we notice that KIST support is gone. Fixes bug
298 24158; bugfix on 0.3.2.1-alpha.
299 - Suppress a log notice when relay descriptors arrive. We already
300 have a bootstrap progress for this so no need to log notice
301 everytime tor receives relay descriptors. Microdescriptors behave
302 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
304 o Minor bugfixes (network layer):
305 - When closing a connection via close_connection_immediately(), we
306 mark it as "not blocked on bandwidth", to prevent later calls from
307 trying to unblock it, and give it permission to read. This fixes a
308 backtrace warning that can happen on relays under various
309 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
311 o Minor bugfixes (onion services):
312 - The introduction circuit was being timed out too quickly while
313 waiting for the rendezvous circuit to complete. Keep the intro
314 circuit around longer instead of timing out and reopening new ones
315 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
316 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
317 so it matches dir-spec.txt. Fixes bug 24262; bugfix
319 - Silence a warning about failed v3 onion descriptor uploads that
320 can happen naturally under certain edge cases. Fixes part of bug
321 23662; bugfix on 0.3.2.1-alpha.
323 o Minor bugfixes (tests):
324 - Fix a memory leak in one of the bridge-distribution test cases.
325 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
326 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
327 to correctly handle cases where a caller gives it an RSA key of
328 under 160 bits. (This is not actually a bug in Tor itself, but
329 rather in our fuzzing code.) Fixes bug 24247; bugfix on
330 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
333 - Add notes in man page regarding OS support for the various
334 scheduler types. Attempt to use less jargon in the scheduler
335 section. Closes ticket 24254.
338 Changes in version 0.3.2.4-alpha - 2017-11-08
339 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
340 It fixes several stability and reliability bugs, especially including
341 a major reliability issue that has been plaguing fast exit relays in
344 o Major bugfixes (exit relays, DNS):
345 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
346 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
347 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
348 identifying and finding a workaround to this bug and to Moritz,
349 Arthur Edelstein, and Roger for helping to track it down and
352 o Major bugfixes (scheduler, channel):
353 - Stop processing scheduled channels if they closed while flushing
354 cells. This can happen if the write on the connection fails
355 leading to the channel being closed while in the scheduler loop.
356 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
358 o Minor features (logging, scheduler):
359 - Introduce a SCHED_BUG() function to log extra information about
360 the scheduler state if we ever catch a bug in the scheduler.
363 o Minor features (removed deprecations):
364 - The ClientDNSRejectInternalAddresses flag can once again be set in
365 non-testing Tor networks, so long as they do not use the default
366 directory authorities. This change also removes the deprecation of
367 this flag from 0.2.9.2-alpha. Closes ticket 21031.
369 o Minor features (testing):
370 - Our fuzzing tests now test the encrypted portions of v3 onion
371 service descriptors. Implements more of 21509.
373 o Minor bugfixes (directory client):
374 - On failure to download directory information, delay retry attempts
375 by a random amount based on the "decorrelated jitter" algorithm.
376 Our previous delay algorithm tended to produce extra-long delays
377 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
379 o Minor bugfixes (IPv6, v3 single onion services):
380 - Remove buggy code for IPv6-only v3 single onion services, and
381 reject attempts to configure them. This release supports IPv4,
382 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
383 stack v3 single onion services. Fixes bug 23820; bugfix
386 o Minor bugfixes (logging, relay):
387 - Give only a protocol warning when the ed25519 key is not
388 consistent between the descriptor and microdescriptor of a relay.
389 This can happen, for instance, if the relay has been flagged
390 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
392 o Minor bugfixes (manpage, onion service):
393 - Document that the HiddenServiceNumIntroductionPoints option is
394 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
395 bugfix on 0.3.2.1-alpha.
397 o Minor bugfixes (memory leaks):
398 - Fix a minor memory leak at exit in the KIST scheduler. This bug
399 should have no user-visible impact. Fixes bug 23774; bugfix
401 - Fix a memory leak when decrypting a badly formatted v3 onion
402 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
403 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
405 o Minor bugfixes (onion services):
406 - Cache some needed onion service client information instead of
407 constantly computing it over and over again. Fixes bug 23623;
408 bugfix on 0.3.2.1-alpha.
409 - Properly retry HSv3 descriptor fetches when missing required
410 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
412 o Minor bugfixes (path selection):
413 - When selecting relays by bandwidth, avoid a rounding error that
414 could sometimes cause load to be imbalanced incorrectly.
415 Previously, we would always round upwards; now, we round towards
416 the nearest integer. This had the biggest effect when a relay's
417 weight adjustments should have given it weight 0, but it got
418 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
419 - When calculating the fraction of nodes that have descriptors, and
420 all nodes in the network have zero bandwidths, count the number of
421 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
422 - Actually log the total bandwidth in compute_weighted_bandwidths().
423 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
425 o Minor bugfixes (relay, crash):
426 - Avoid a crash when transitioning from client mode to bridge mode.
427 Previously, we would launch the worker threads whenever our
428 "public server" mode changed, but not when our "server" mode
429 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
431 o Minor bugfixes (testing):
432 - Fix a spurious fuzzing-only use of an uninitialized value. Found
433 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
434 - Test that IPv6-only clients can use microdescriptors when running
435 "make test-network-all". Requires chutney master 61c28b9 or later.
439 Changes in version 0.3.2.3-alpha - 2017-10-27
440 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
441 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
442 directory authority, Bastet.
444 o Directory authority changes:
445 - Add "Bastet" as a ninth directory authority to the default list.
447 - The directory authority "Longclaw" has changed its IP address.
450 o Minor features (bridge):
451 - Bridge relays can now set the BridgeDistribution config option to
452 add a "bridge-distribution-request" line to their bridge
453 descriptor, which tells BridgeDB how they'd like their bridge
454 address to be given out. (Note that as of Oct 2017, BridgeDB does
455 not yet implement this feature.) As a side benefit, this feature
456 provides a way to distinguish bridge descriptors from non-bridge
457 descriptors. Implements tickets 18329.
459 o Minor features (client, entry guards):
460 - Improve log messages when missing descriptors for primary guards.
461 Resolves ticket 23670.
463 o Minor features (geoip):
464 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
467 o Minor bugfixes (bridge):
468 - Overwrite the bridge address earlier in the process of retrieving
469 its descriptor, to make sure we reach it on the configured
470 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
472 o Minor bugfixes (documentation):
473 - Document better how to read gcov, and what our gcov postprocessing
474 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
476 o Minor bugfixes (entry guards):
477 - Tor now updates its guard state when it reads a consensus
478 regardless of whether it's missing descriptors. That makes tor use
479 its primary guards to fetch descriptors in some edge cases where
480 it would previously have used fallback directories. Fixes bug
481 23862; bugfix on 0.3.0.1-alpha.
483 o Minor bugfixes (hidden service client):
484 - When handling multiple SOCKS request for the same .onion address,
485 only fetch the service descriptor once.
486 - When a descriptor fetch fails with a non-recoverable error, close
487 all pending SOCKS requests for that .onion. Fixes bug 23653;
488 bugfix on 0.3.2.1-alpha.
490 o Minor bugfixes (hidden service):
491 - Always regenerate missing hidden service public key files. Prior
492 to this, if the public key was deleted from disk, it wouldn't get
493 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
495 - Make sure that we have a usable ed25519 key when the intro point
496 relay supports ed25519 link authentication. Fixes bug 24002;
497 bugfix on 0.3.2.1-alpha.
499 o Minor bugfixes (hidden service, v2):
500 - When reloading configured hidden services, copy all information
501 from the old service object. Previously, some data was omitted,
502 causing delays in descriptor upload, and other bugs. Fixes bug
503 23790; bugfix on 0.2.1.9-alpha.
505 o Minor bugfixes (memory safety, defensive programming):
506 - Clear the target address when node_get_prim_orport() returns
507 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
509 o Minor bugfixes (relay):
510 - Avoid a BUG warning when receiving a dubious CREATE cell while an
511 option transition is in progress. Fixes bug 23952; bugfix
514 o Minor bugfixes (testing):
515 - Adjust the GitLab CI configuration to more closely match that of
516 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
517 - Prevent scripts/test/coverage from attempting to move gcov output
518 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
519 - When running unit tests as root, skip a test that would fail
520 because it expects a permissions error. This affects some
521 continuous integration setups. Fixes bug 23758; bugfix
523 - Stop unconditionally mirroring the tor repository in GitLab CI.
524 This prevented developers from enabling GitLab CI on master. Fixes
525 bug 23755; bugfix on 0.3.2.2-alpha.
526 - Fix the hidden service v3 descriptor decoding fuzzing to use the
527 latest decoding API correctly. Fixes bug 21509; bugfix
530 o Minor bugfixes (warnings):
531 - When we get an HTTP request on a SOCKS port, tell the user about
532 the new HTTPTunnelPort option. Previously, we would give a "Tor is
533 not an HTTP Proxy" message, which stopped being true when
534 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
538 Changes in version 0.3.2.2-alpha - 2017-09-29
539 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
540 release fixes several minor bugs in the new scheduler and next-
541 generation onion services; both features were newly added in the 0.3.2
542 series. Other fixes in this alpha include several fixes for non-fatal
543 tracebacks which would appear in logs.
545 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
546 alpha does not contain any substantial new features. Minor features
547 include better testing and logging.
549 The following comprises the complete list of changes included
550 in tor-0.3.2.2-alpha:
552 o Major bugfixes (relay, crash, assertion failure):
553 - Fix a timing-based assertion failure that could occur when the
554 circuit out-of-memory handler freed a connection's output buffer.
555 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
557 o Major bugfixes (scheduler):
558 - If a channel is put into the scheduler's pending list, then it
559 starts closing, and then if the scheduler runs before it finishes
560 closing, the scheduler will get stuck trying to flush its cells
561 while the lower layers refuse to cooperate. Fix that race
562 condition by giving the scheduler an escape method. Fixes bug
563 23676; bugfix on 0.3.2.1-alpha.
565 o Minor features (build, compilation):
566 - The "check-changes" feature is now part of the "make check" tests;
567 we'll use it to try to prevent misformed changes files from
568 accumulating. Closes ticket 23564.
569 - Tor builds should now fail if there are any mismatches between the
570 C type representing a configuration variable and the C type the
571 data-driven parser uses to store a value there. Previously, we
572 needed to check these by hand, which sometimes led to mistakes.
575 o Minor features (directory authorities):
576 - Remove longclaw's IPv6 address, as it will soon change. Authority
577 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
578 3/8 directory authorities with IPv6 addresses, but there are also
579 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
581 o Minor features (hidden service, circuit, logging):
582 - Improve logging of many callsite in the circuit subsystem to print
583 the circuit identifier(s).
584 - Log when we cleanup an intro point from a service so we know when
585 and for what reason it happened. Closes ticket 23604.
587 o Minor features (logging):
588 - Log more circuit information whenever we are about to try to
589 package a relay cell on a circuit with a nonexistent n_chan.
590 Attempt to diagnose ticket 8185.
591 - Improve info-level log identification of particular circuits, to
592 help with debugging. Closes ticket 23645.
594 o Minor features (relay):
595 - When choosing which circuits can be expired as unused, consider
596 circuits from clients even if those clients used regular CREATE
597 cells to make them; and do not consider circuits from relays even
598 if they were made with CREATE_FAST. Part of ticket 22805.
600 o Minor features (robustness):
601 - Change several fatal assertions when flushing buffers into non-
602 fatal assertions, to prevent any recurrence of 23690.
604 o Minor features (spec conformance, bridge, diagnostic):
605 - When handling the USERADDR command on an ExtOrPort, warn when the
606 transports provides a USERADDR with no port. In a future version,
607 USERADDR commands of this format may be rejected. Detects problems
608 related to ticket 23080.
610 o Minor features (testing):
611 - Add a unit test to make sure that our own generated platform
612 string will be accepted by directory authorities. Closes
615 o Minor bugfixes (bootstrapping):
616 - When warning about state file clock skew, report the correct
617 direction for the detected skew. Fixes bug 23606; bugfix
619 - Avoid an assertion failure when logging a state file clock skew
620 very early in bootstrapping. Fixes bug 23607; bugfix
623 o Minor bugfixes (build, compilation):
624 - Fix a compilation warning when building with zstd support on
625 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
626 and fixed by Andreas Stieger.
627 - When searching for OpenSSL, don't accept any OpenSSL library that
628 lacks TLSv1_1_method(): Tor doesn't build with those versions.
629 Additionally, look in /usr/local/opt/openssl, if it's present.
630 These changes together repair the default build on OSX systems
631 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
633 o Minor bugfixes (compression):
634 - Handle a pathological case when decompressing Zstandard data when
635 the output buffer size is zero. Fixes bug 23551; bugfix
638 o Minor bugfixes (documentation):
639 - Fix manpage to not refer to the obsolete (and misspelled)
640 UseEntryGuardsAsDirectoryGuards parameter in the description of
641 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
643 o Minor bugfixes (hidden service v3):
644 - Don't log an assertion failure when we can't find the right
645 information to extend to an introduction point. In rare cases,
646 this could happen, causing a warning, even though tor would
647 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
648 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
649 much bigger so the rendezvous point can't distinguish which hidden
650 service protocol is being used. Fixes bug 23420; bugfix
653 o Minor bugfixes (hidden service, relay):
654 - Avoid a possible double close of a circuit by the intro point on
655 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
656 bugfix on 0.3.0.1-alpha.
658 o Minor bugfixes (logging, relay shutdown, annoyance):
659 - When a circuit is marked for close, do not attempt to package any
660 cells for channels on that circuit. Previously, we would detect
661 this condition lower in the call stack, when we noticed that the
662 circuit had no attached channel, and log an annoying message.
663 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
665 o Minor bugfixes (scheduler):
666 - When switching schedulers due to a consensus change, we didn't
667 give the new scheduler a chance to react to the consensus. Fix
668 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
669 - Make the KISTSchedRunInterval option a non negative value. With
670 this, the way to disable KIST through the consensus is to set it
671 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
672 - Only notice log the selected scheduler when we switch scheduler
673 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
674 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
675 by a different tv_usec data type. Fixes bug 23575; bugfix
677 - Make a hard exit if tor is unable to pick a scheduler which can
678 happen if the user specifies a scheduler type that is not
679 supported and not other types in Schedulers. Fixes bug 23581;
680 bugfix on 0.3.2.1-alpha.
681 - Properly initialize the scheduler last run time counter so it is
682 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
684 o Minor bugfixes (testing):
685 - Capture and detect several "Result does not fit" warnings in unit
686 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
688 - Fix additional channelpadding unit test failures by using mocked
689 time instead of actual time for all tests. Fixes bug 23608; bugfix
691 - The removal of some old scheduler options caused some tests to
692 fail on BSD systems. Assume current behavior is correct and make
693 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
695 o Code simplification and refactoring:
696 - Remove various ways of testing circuits and connections for
697 "clientness"; instead, favor channel_is_client(). Part of
700 o Deprecated features:
701 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
702 now deprecated; they do not apply to relays, and they have had no
703 effect on clients since 0.2.8.x. Closes ticket 19704.
706 - HiddenServiceVersion man page entry wasn't mentioning the now
707 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
708 - Clarify that the Address option is entirely about setting an
709 advertised IPv4 address. Closes ticket 18891.
710 - Clarify the manpage's use of the term "address" to clarify what
711 kind of address is intended. Closes ticket 21405.
712 - Document that onion service subdomains are allowed, and ignored.
716 Changes in version 0.3.2.1-alpha - 2017-09-18
717 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
718 includes support for our next-generation ("v3") onion service
719 protocol, and adds a new circuit scheduler for more responsive
720 forwarding decisions from relays. There are also numerous other small
721 features and bugfixes here.
723 Below are the changes since Tor 0.3.1.7.
725 o Major feature (scheduler, channel):
726 - Tor now uses new schedulers to decide which circuits should
727 deliver cells first, in order to improve congestion at relays. The
728 first type is called "KIST" ("Kernel Informed Socket Transport"),
729 and is only available on Linux-like systems: it uses feedback from
730 the kernel to prevent the kernel's TCP buffers from growing too
731 full. The second new scheduler type is called "KISTLite": it
732 behaves the same as KIST, but runs on systems without kernel
733 support for inspecting TCP implementation details. The old
734 scheduler is still available, under the name "Vanilla". To change
735 the default scheduler preference order, use the new "Schedulers"
736 option. (The default preference order is "KIST,KISTLite,Vanilla".)
738 Matt Traudt implemented KIST, based on research by Rob Jansen,
739 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
740 more information, see the design paper at
741 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
742 followup implementation paper at https://arxiv.org/abs/1709.01044.
745 o Major features (next-generation onion services):
746 - Tor now supports the next-generation onion services protocol for
747 clients and services! As part of this release, the core of
748 proposal 224 has been implemented and is available for
749 experimentation and testing by our users. This newer version of
750 onion services ("v3") features many improvements over the legacy
753 a) Better crypto (replaced SHA1/DH/RSA1024
754 with SHA3/ed25519/curve25519)
756 b) Improved directory protocol, leaking much less information to
759 c) Improved directory protocol, with smaller surface for
762 d) Better onion address security against impersonation.
764 e) More extensible introduction/rendezvous protocol.
766 f) A cleaner and more modular codebase.
768 You can identify a next-generation onion address by its length:
769 they are 56 characters long, as in
770 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
772 In the future, we will release more options and features for v3
773 onion services, but we first need a testing period, so that the
774 current codebase matures and becomes more robust. Planned features
775 include: offline keys, advanced client authorization, improved
776 guard algorithms, and statistics. For full details, see
779 Legacy ("v2") onion services will still work for the foreseeable
780 future, and will remain the default until this new codebase gets
781 tested and hardened. Service operators who want to experiment with
782 the new system can use the 'HiddenServiceVersion 3' torrc
783 directive along with the regular onion service configuration
784 options. We will publish a blog post about this new feature
787 o Major bugfixes (usability, control port):
788 - Report trusted clock skew indications as bootstrap errors, so
789 controllers can more easily alert users when their clocks are
790 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
792 o Minor features (bug detection):
793 - Log a warning message with a stack trace for any attempt to call
794 get_options() during option validation. This pattern has caused
795 subtle bugs in the past. Closes ticket 22281.
797 o Minor features (client):
798 - You can now use Tor as a tunneled HTTP proxy: use the new
799 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
800 requests. Closes ticket 22407.
801 - Add an extra check to make sure that we always use the newer guard
802 selection code for picking our guards. Closes ticket 22779.
803 - When downloading (micro)descriptors, don't split the list into
804 multiple requests unless we want at least 32 descriptors.
805 Previously, we split at 4, not 32, which led to significant
806 overhead in HTTP request size and degradation in compression
807 performance. Closes ticket 23220.
809 o Minor features (command line):
810 - Add a new commandline option, --key-expiration, which prints when
811 the current signing key is going to expire. Implements ticket
812 17639; patch by Isis Lovecruft.
814 o Minor features (control port):
815 - If an application tries to use the control port as an HTTP proxy,
816 respond with a meaningful "This is the Tor control port" message,
817 and log the event. Closes ticket 1667. Patch from Ravi
819 - Provide better error message for GETINFO desc/(id|name) when not
820 fetching router descriptors. Closes ticket 5847. Patch by
822 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
823 whether Tor will try to download router descriptors and
824 microdescriptors respectively. Closes ticket 22684.
825 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
826 so controllers can tell whether the geoip databases are loaded.
828 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
829 events. Closes ticket 19254. Patch by "DonnchaC".
831 o Minor features (development support):
832 - Developers can now generate a call-graph for Tor using the
833 "calltool" python program, which post-processes object dumps. It
834 should work okay on many Linux and OSX platforms, and might work
835 elsewhere too. To run it, install calltool from
836 https://gitweb.torproject.org/user/nickm/calltool.git and run
837 "make callgraph". Closes ticket 19307.
839 o Minor features (ed25519):
840 - Add validation function to checks for torsion components in
841 ed25519 public keys, used by prop224 client-side code. Closes
842 ticket 22006. Math help by Ian Goldberg.
844 o Minor features (exit relay, DNS):
845 - Improve the clarity and safety of the log message from evdns when
846 receiving an apparently spoofed DNS reply. Closes ticket 3056.
848 o Minor features (integration, hardening):
849 - Add a new NoExec option to prevent Tor from running other
850 programs. When this option is set to 1, Tor will never try to run
851 another program, regardless of the settings of
852 PortForwardingHelper, ClientTransportPlugin, or
853 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
854 without restarting Tor. Closes ticket 22976.
856 o Minor features (logging):
857 - Improve the warning message for specifying a relay by nickname.
858 The previous message implied that nickname registration was still
859 part of the Tor network design, which it isn't. Closes
861 - If the sandbox filter fails to load, suggest to the user that
862 their kernel might not support seccomp2. Closes ticket 23090.
864 o Minor features (portability):
865 - Check at configure time whether uint8_t is the same type as
866 unsigned char. Lots of existing code already makes this
867 assumption, and there could be strict aliasing issues if the
868 assumption is violated. Closes ticket 22410.
870 o Minor features (relay, configuration):
871 - Reject attempts to use relative file paths when RunAsDaemon is
872 set. Previously, Tor would accept these, but the directory-
873 changing step of RunAsDaemon would give strange and/or confusing
874 results. Closes ticket 22731.
876 o Minor features (startup, safety):
877 - When configured to write a PID file, Tor now exits if it is unable
878 to do so. Previously, it would warn and continue. Closes
881 o Minor features (static analysis):
882 - The BUG() macro has been changed slightly so that Coverity no
883 longer complains about dead code if the bug is impossible. Closes
886 o Minor features (testing):
887 - The default chutney network tests now include tests for the v3
888 hidden service design. Make sure you have the latest version of
889 chutney if you want to run these. Closes ticket 22437.
890 - Add a unit test to verify that we can parse a hardcoded v2 hidden
891 service descriptor. Closes ticket 15554.
893 o Minor bugfixes (certificate handling):
894 - Fix a time handling bug in Tor certificates set to expire after
895 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
896 Coverity as CID 1415728.
898 o Minor bugfixes (client, usability):
899 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
900 SOCKS4a requests that contain IP address strings, even when
901 SafeSocks in enabled, as this prevents user from connecting to
902 known IP addresses without relying on DNS for resolving. SafeSocks
903 still rejects SOCKS connections that connect to IP addresses when
904 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
905 bugfix on Tor 0.2.6.2-alpha.
907 o Minor bugfixes (code correctness):
908 - Call htons() in extend_cell_format() for encoding a 16-bit value.
909 Previously we used ntohs(), which happens to behave the same on
910 all the platforms we support, but which isn't really correct.
911 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
912 - For defense-in-depth, make the controller's write_escaped_data()
913 function robust to extremely long inputs. Fixes bug 19281; bugfix
914 on 0.1.1.1-alpha. Reported by Guido Vranken.
916 o Minor bugfixes (compilation):
917 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
918 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
920 o Minor bugfixes (consensus expiry):
921 - Check for adequate directory information correctly. Previously, Tor
922 would reconsider whether it had sufficient directory information
923 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
925 o Minor bugfixes (directory protocol):
926 - Directory servers now include a "Date:" http header for response
927 codes other than 200. Clients starting with a skewed clock and a
928 recent consensus were getting "304 Not modified" responses from
929 directory authorities, so without the Date header, the client
930 would never hear about a wrong clock. Fixes bug 23499; bugfix
932 - Make clients wait for 6 seconds before trying to download a
933 consensus from an authority. Fixes bug 17750; bugfix
936 o Minor bugfixes (DoS-resistance):
937 - If future code asks if there are any running bridges, without
938 checking if bridges are enabled, log a BUG warning rather than
939 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
941 o Minor bugfixes (format strictness):
942 - Restrict several data formats to decimal. Previously, the
943 BuildTimeHistogram entries in the state file, the "bw=" entries in
944 the bandwidth authority file, and the process IDs passed to the
945 __OwningControllerProcess option could all be specified in hex or
946 octal as well as in decimal. This was not an intentional feature.
947 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
950 o Minor bugfixes (heartbeat):
951 - If we fail to write a heartbeat message, schedule a retry for the
952 minimum heartbeat interval number of seconds in the future. Fixes
953 bug 19476; bugfix on 0.2.3.1-alpha.
955 o Minor bugfixes (linux seccomp2 sandbox, logging):
956 - Fix some messages on unexpected errors from the seccomp2 library.
957 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
959 o Minor bugfixes (logging):
960 - Remove duplicate log messages regarding opening non-local
961 SocksPorts upon parsing config and opening listeners at startup.
962 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
963 - Use a more comprehensible log message when telling the user
964 they've excluded every running exit node. Fixes bug 7890; bugfix
966 - When logging the number of descriptors we intend to download per
967 directory request, do not log a number higher than then the number
968 of descriptors we're fetching in total. Fixes bug 19648; bugfix
970 - When warning about a directory owned by the wrong user, log the
971 actual name of the user owning the directory. Previously, we'd log
972 the name of the process owner twice. Fixes bug 23487; bugfix
974 - The tor specification says hop counts are 1-based, so fix two log
975 messages that mistakenly logged 0-based hop counts. Fixes bug
976 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
977 Credit to Xiaofan Li for reporting this issue.
979 o Minor bugfixes (portability):
980 - Stop using the PATH_MAX variable, which is not defined on GNU
981 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
983 o Minor bugfixes (relay):
984 - When uploading our descriptor for the first time after startup,
985 report the reason for uploading as "Tor just started" rather than
986 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
987 - Avoid unnecessary calls to directory_fetches_from_authorities() on
988 relays, to prevent spurious address resolutions and descriptor
989 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
990 bugfix on in 0.2.8.1-alpha.
992 o Minor bugfixes (tests):
993 - Fix a broken unit test for the OutboundAddress option: the parsing
994 function was never returning an error on failure. Fixes bug 23366;
995 bugfix on 0.3.0.3-alpha.
996 - Fix a signed-integer overflow in the unit tests for
997 dir/download_status_random_backoff, which was untriggered until we
998 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
1000 o Minor bugfixes (usability, control port):
1001 - Stop making an unnecessary routerlist check in NETINFO clock skew
1002 detection; this was preventing clients from reporting NETINFO clock
1003 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
1005 o Code simplification and refactoring:
1006 - Extract the code for handling newly-open channels into a separate
1007 function from the general code to handle channel state
1008 transitions. This change simplifies our callgraph, reducing the
1009 size of the largest strongly connected component by roughly a
1010 factor of two. Closes ticket 22608.
1011 - Remove dead code for largely unused statistics on the number of
1012 times we've attempted various public key operations. Fixes bug
1013 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
1014 - Remove several now-obsolete functions for asking about old
1015 variants directory authority status. Closes ticket 22311; patch
1017 - Remove some of the code that once supported "Named" and "Unnamed"
1018 routers. Authorities no longer vote for these flags. Closes
1020 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
1021 and old hidden services, to indicate that they aren't suitable for
1022 new protocols or formats. Closes ticket 23026.
1023 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
1024 22521. Patch from Neel Chauhan.
1025 - Split the enormous circuit_send_next_onion_skin() function into
1026 multiple subfunctions. Closes ticket 22804.
1027 - Split the portions of the buffer.c module that handle particular
1028 protocols into separate modules. Part of ticket 23149.
1029 - Use our test macros more consistently, to produce more useful
1030 error messages when our unit tests fail. Add coccinelle patches to
1031 allow us to re-check for test macro uses. Closes ticket 22497.
1033 o Deprecated features:
1034 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
1035 only applies to direct unencrypted HTTP connections to your
1036 directory server, which your Tor probably isn't using. Closes
1040 - Clarify in the manual that "Sandbox 1" is only supported on Linux
1041 kernels. Closes ticket 22677.
1042 - Document all values of PublishServerDescriptor in the manpage.
1043 Closes ticket 15645.
1044 - Improve the documentation for the directory port part of the
1045 DirAuthority line. Closes ticket 20152.
1046 - Restore documentation for the authorities' "approved-routers"
1047 file. Closes ticket 21148.
1050 - The AllowDotExit option has been removed as unsafe. It has been
1051 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
1052 - The ClientDNSRejectInternalAddresses flag can no longer be set on
1053 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
1054 Closes ticket 21031.
1055 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
1056 nobody was using it any longer. Closes ticket 22377.
1059 Changes in version 0.2.8.15 - 2017-09-18
1060 Tor 0.2.8.15 backports a collection of bugfixes from later
1063 Most significantly, it includes a fix for TROVE-2017-008, a
1064 security bug that affects hidden services running with the
1065 SafeLogging option disabled. For more information, see
1066 https://trac.torproject.org/projects/tor/ticket/23490
1068 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
1069 2018. We suggest that you upgrade to the latest stable release if
1070 possible. If you can't, we recommend that you upgrade at least to
1071 0.2.9, which will be supported until 2020.
1073 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1074 - Avoid an assertion failure bug affecting our implementation of
1075 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1076 handling of "0xx" differs from what we had expected. Fixes bug
1077 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1080 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1083 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1084 - Backport a fix for an "unused variable" warning that appeared
1085 in some versions of mingw. Fixes bug 22838; bugfix on
1088 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1089 - Fix a memset() off the end of an array when packing cells. This
1090 bug should be harmless in practice, since the corrupted bytes are
1091 still in the same structure, and are always padding bytes,
1092 ignored, or immediately overwritten, depending on compiler
1093 behavior. Nevertheless, because the memset()'s purpose is to make
1094 sure that any other cell-handling bugs can't expose bytes to the
1095 network, we need to fix it. Fixes bug 22737; bugfix on
1096 0.2.4.11-alpha. Fixes CID 1401591.
1098 o Build features (backport from 0.3.1.5-alpha):
1099 - Tor's repository now includes a Travis Continuous Integration (CI)
1100 configuration file (.travis.yml). This is meant to help new
1101 developers and contributors who fork Tor to a Github repository be
1102 better able to test their changes, and understand what we expect
1103 to pass. To use this new build feature, you must fork Tor to your
1104 Github account, then go into the "Integrations" menu in the
1105 repository settings for your fork and enable Travis, then push
1106 your changes. Closes ticket 22636.
1109 Changes in version 0.2.9.12 - 2017-09-18
1110 Tor 0.2.9.12 backports a collection of bugfixes from later
1113 Most significantly, it includes a fix for TROVE-2017-008, a
1114 security bug that affects hidden services running with the
1115 SafeLogging option disabled. For more information, see
1116 https://trac.torproject.org/projects/tor/ticket/23490
1118 o Major features (security, backport from 0.3.0.2-alpha):
1119 - Change the algorithm used to decide DNS TTLs on client and server
1120 side, to better resist DNS-based correlation attacks like the
1121 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
1122 Feamster. Now relays only return one of two possible DNS TTL
1123 values, and clients are willing to believe DNS TTL values up to 3
1124 hours long. Closes ticket 19769.
1126 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
1127 - Fix a rare crash when sending a begin cell on a circuit whose
1128 linked directory connection had already been closed. Fixes bug
1129 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
1131 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
1132 - Fix a bug that prevented exit nodes from caching DNS records for
1133 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
1135 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
1136 - Fix a typo that had prevented TPROXY-based transparent proxying
1137 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
1138 Patch from "d4fq0fQAgoJ".
1140 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1141 - Avoid an assertion failure bug affecting our implementation of
1142 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1143 handling of "0xx" differs from what we had expected. Fixes bug
1144 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1146 o Minor features (code style, backport from 0.3.1.3-alpha):
1147 - Add "Falls through" comments to our codebase, in order to silence
1148 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1149 Stieger. Closes ticket 22446.
1151 o Minor features (geoip):
1152 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1155 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
1156 - Roll over monthly accounting at the configured hour and minute,
1157 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
1158 Found by Andrey Karpov with PVS-Studio.
1160 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
1161 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
1162 bugfix on 0.2.8.1-alpha.
1163 - Fix warnings when building with libscrypt and openssl scrypt support
1164 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
1165 - When building with certain versions the mingw C header files, avoid
1166 float-conversion warnings when calling the C functions isfinite(),
1167 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
1169 o Minor bugfixes (compilation, backport from 0.3.1.7):
1170 - Avoid compiler warnings in the unit tests for running tor_sscanf()
1171 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1173 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1174 - Backport a fix for an "unused variable" warning that appeared
1175 in some versions of mingw. Fixes bug 22838; bugfix on
1178 o Minor bugfixes (controller, backport from 0.3.1.7):
1179 - Do not crash when receiving a HSPOST command with an empty body.
1180 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1181 - Do not crash when receiving a POSTDESCRIPTOR command with an
1182 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1184 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
1185 - Avoid Coverity build warnings related to our BUG() macro. By
1186 default, Coverity treats BUG() as the Linux kernel does: an
1187 instant abort(). We need to override that so our BUG() macro
1188 doesn't prevent Coverity from analyzing functions that use it.
1189 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
1191 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1192 - Fix a memset() off the end of an array when packing cells. This
1193 bug should be harmless in practice, since the corrupted bytes are
1194 still in the same structure, and are always padding bytes,
1195 ignored, or immediately overwritten, depending on compiler
1196 behavior. Nevertheless, because the memset()'s purpose is to make
1197 sure that any other cell-handling bugs can't expose bytes to the
1198 network, we need to fix it. Fixes bug 22737; bugfix on
1199 0.2.4.11-alpha. Fixes CID 1401591.
1201 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
1202 - When setting the maximum number of connections allowed by the OS,
1203 always allow some extra file descriptors for other files. Fixes
1204 bug 22797; bugfix on 0.2.0.10-alpha.
1206 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
1207 - Avoid a sandbox failure when trying to re-bind to a socket and
1208 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
1210 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
1211 - Permit the fchmod system call, to avoid crashing on startup when
1212 starting with the seccomp2 sandbox and an unexpected set of
1213 permissions on the data directory or its contents. Fixes bug
1214 22516; bugfix on 0.2.5.4-alpha.
1216 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
1217 - Avoid a double-marked-circuit warning that could happen when we
1218 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
1221 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
1222 - Reject version numbers with non-numeric prefixes (such as +, -, or
1223 whitespace). Disallowing whitespace prevents differential version
1224 parsing between POSIX-based and Windows platforms. Fixes bug 21507
1225 and part of 21508; bugfix on 0.0.8pre1.
1227 o Build features (backport from 0.3.1.5-alpha):
1228 - Tor's repository now includes a Travis Continuous Integration (CI)
1229 configuration file (.travis.yml). This is meant to help new
1230 developers and contributors who fork Tor to a Github repository be
1231 better able to test their changes, and understand what we expect
1232 to pass. To use this new build feature, you must fork Tor to your
1233 Github account, then go into the "Integrations" menu in the
1234 repository settings for your fork and enable Travis, then push
1235 your changes. Closes ticket 22636.
1238 Changes in version 0.3.0.11 - 2017-09-18
1239 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
1242 Most significantly, it includes a fix for TROVE-2017-008, a
1243 security bug that affects hidden services running with the
1244 SafeLogging option disabled. For more information, see
1245 https://trac.torproject.org/projects/tor/ticket/23490
1247 o Minor features (code style, backport from 0.3.1.7):
1248 - Add "Falls through" comments to our codebase, in order to silence
1249 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1250 Stieger. Closes ticket 22446.
1253 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1256 o Minor bugfixes (compilation, backport from 0.3.1.7):
1257 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
1258 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1260 o Minor bugfixes (controller, backport from 0.3.1.7):
1261 - Do not crash when receiving a HSPOST command with an empty body.
1262 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1263 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
1264 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1266 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
1267 - When setting the maximum number of connections allowed by the OS,
1268 always allow some extra file descriptors for other files. Fixes
1269 bug 22797; bugfix on 0.2.0.10-alpha.
1271 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
1272 - Remove a forgotten debugging message when an introduction point
1273 successfully establishes a hidden service prop224 circuit with
1275 - Change three other log_warn() for an introduction point to
1276 protocol warnings, because they can be failure from the network
1277 and are not relevant to the operator. Fixes bug 23078; bugfix on
1278 0.3.0.1-alpha and 0.3.0.2-alpha.
1281 Changes in version 0.3.1.7 - 2017-09-18
1282 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
1284 With the 0.3.1 series, Tor now serves and downloads directory
1285 information in more compact formats, to save on bandwidth overhead. It
1286 also contains a new padding system to resist netflow-based traffic
1287 analysis, and experimental support for building parts of Tor in Rust
1288 (though no parts of Tor are in Rust yet). There are also numerous
1289 small features, bugfixes on earlier release series, and groundwork for
1290 the hidden services revamp of 0.3.2.
1292 This release also includes a fix for TROVE-2017-008, a security bug
1293 that affects hidden services running with the SafeLogging option
1294 disabled. For more information, see
1295 https://trac.torproject.org/projects/tor/ticket/23490
1297 Per our stable release policy, we plan to support each stable release
1298 series for at least the next nine months, or for three months after
1299 the first stable release of the next series: whichever is longer. If
1300 you need a release with long-term support, we recommend that you stay
1301 with the 0.2.9 series.
1303 Below is a list of the changes since 0.3.1.6-rc. For a list of all
1304 changes since 0.3.0, see the ReleaseNotes file.
1306 o Major bugfixes (security, hidden services, loggging):
1307 - Fix a bug where we could log uninitialized stack when a certain
1308 hidden service error occurred while SafeLogging was disabled.
1309 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
1310 TROVE-2017-008 and CVE-2017-0380.
1312 o Minor features (defensive programming):
1313 - Create a pair of consensus parameters, nf_pad_tor2web and
1314 nf_pad_single_onion, to disable netflow padding in the consensus
1315 for non-anonymous connections in case the overhead is high. Closes
1318 o Minor features (diagnostic):
1319 - Add a stack trace to the bug warnings that can be logged when
1320 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
1321 attempt for bug 23105.
1323 o Minor features (geoip):
1324 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1327 o Minor bugfixes (compilation):
1328 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
1329 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1331 o Minor bugfixes (controller):
1332 - Do not crash when receiving a HSPOST command with an empty body.
1333 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1334 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
1335 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1337 o Minor bugfixes (relay):
1338 - Inform the geoip and rephist modules about all requests, even on
1339 relays that are only fetching microdescriptors. Fixes a bug
1340 related to 21585; bugfix on 0.3.0.1-alpha.
1342 o Minor bugfixes (unit tests):
1343 - Fix a channelpadding unit test failure on slow systems by using
1344 mocked time instead of actual time. Fixes bug 23077; bugfix
1348 Changes in version 0.3.1.6-rc - 2017-09-05
1349 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
1350 release series, including a bug that produced weird behavior on
1351 Windows directory caches.
1353 This is the first release candidate in the Tor 0.3.1 series. If we
1354 find no new bugs or regressions here, the first stable 0.3.1 release
1355 will be nearly identical to it.
1357 o Major bugfixes (windows, directory cache):
1358 - On Windows, do not try to delete cached consensus documents and
1359 diffs before they are unmapped from memory--Windows won't allow
1360 that. Instead, allow the consensus cache directory to grow larger,
1361 to hold files that might need to stay around longer. Fixes bug
1362 22752; bugfix on 0.3.1.1-alpha.
1364 o Minor features (directory authority):
1365 - Improve the message that authorities report to relays that present
1366 RSA/Ed25519 keypairs that conflict with previously pinned keys.
1367 Closes ticket 22348.
1369 o Minor features (geoip):
1370 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
1373 o Minor features (testing):
1374 - Add more tests for compression backend initialization. Closes
1377 o Minor bugfixes (directory cache):
1378 - Fix a memory leak when recovering space in the consensus cache.
1379 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
1381 o Minor bugfixes (hidden service):
1382 - Increase the number of circuits that a service is allowed to
1383 open over a specific period of time. The value was lower than it
1384 should be (8 vs 12) in the normal case of 3 introduction points.
1385 Fixes bug 22159; bugfix on 0.3.0.5-rc.
1386 - Fix a BUG warning during HSv3 descriptor decoding that could be
1387 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
1388 on 0.3.0.1-alpha. Bug found by "haxxpop".
1389 - Rate-limit the log messages if we exceed the maximum number of
1390 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
1392 o Minor bugfixes (logging, relay):
1393 - Remove a forgotten debugging message when an introduction point
1394 successfully establishes a hidden service prop224 circuit with
1396 - Change three other log_warn() for an introduction point to
1397 protocol warnings, because they can be failure from the network
1398 and are not relevant to the operator. Fixes bug 23078; bugfix on
1399 0.3.0.1-alpha and 0.3.0.2-alpha.
1401 o Minor bugfixes (relay):
1402 - When a relay is not running as a directory cache, it will no
1403 longer generate compressed consensuses and consensus diff
1404 information. Previously, this was a waste of disk and CPU. Fixes
1405 bug 23275; bugfix on 0.3.1.1-alpha.
1407 o Minor bugfixes (robustness, error handling):
1408 - Improve our handling of the cases where OpenSSL encounters a
1409 memory error while encoding keys and certificates. We haven't
1410 observed these errors in the wild, but if they do happen, we now
1411 detect and respond better. Fixes bug 19418; bugfix on all versions
1412 of Tor. Reported by Guido Vranken.
1414 o Minor bugfixes (stability):
1415 - Avoid crashing on a double-free when unable to load or process an
1416 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
1417 with the clang static analyzer.
1419 o Minor bugfixes (testing):
1420 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1421 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1422 - Port the hs_ntor handshake test to work correctly with recent
1423 versions of the pysha3 module. Fixes bug 23071; bugfix
1426 o Minor bugfixes (Windows service):
1427 - When running as a Windows service, set the ID of the main thread
1428 correctly. Failure to do so made us fail to send log messages to
1429 the controller in 0.2.1.16-rc, slowed down controller event
1430 delivery in 0.2.7.3-rc and later, and crash with an assertion
1431 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1432 Patch and diagnosis from "Vort".
1435 Changes in version 0.3.0.10 - 2017-08-02
1436 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
1437 from the current Tor alpha series. OpenBSD users and TPROXY users
1438 should upgrade; others are probably okay sticking with 0.3.0.9.
1440 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
1441 - Tor's repository now includes a Travis Continuous Integration (CI)
1442 configuration file (.travis.yml). This is meant to help new
1443 developers and contributors who fork Tor to a Github repository be
1444 better able to test their changes, and understand what we expect
1445 to pass. To use this new build feature, you must fork Tor to your
1446 Github account, then go into the "Integrations" menu in the
1447 repository settings for your fork and enable Travis, then push
1448 your changes. Closes ticket 22636.
1450 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
1451 - Fix a typo that had prevented TPROXY-based transparent proxying
1452 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
1453 Patch from "d4fq0fQAgoJ".
1455 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1456 - Avoid an assertion failure bug affecting our implementation of
1457 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1458 handling of "0xbar" differs from what we had expected. Fixes bug
1459 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1461 o Minor features (backport from 0.3.1.5-alpha):
1462 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
1465 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
1466 - Roll over monthly accounting at the configured hour and minute,
1467 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
1468 Found by Andrey Karpov with PVS-Studio.
1470 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
1471 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
1472 bugfix on 0.2.8.1-alpha.
1473 - Fix warnings when building with libscrypt and openssl scrypt
1474 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
1475 - When building with certain versions of the mingw C header files,
1476 avoid float-conversion warnings when calling the C functions
1477 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
1480 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1481 - Backport a fix for an "unused variable" warning that appeared
1482 in some versions of mingw. Fixes bug 22838; bugfix on
1485 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
1486 - Avoid Coverity build warnings related to our BUG() macro. By
1487 default, Coverity treats BUG() as the Linux kernel does: an
1488 instant abort(). We need to override that so our BUG() macro
1489 doesn't prevent Coverity from analyzing functions that use it.
1490 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
1492 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
1493 - When rejecting a router descriptor for running an obsolete version
1494 of Tor without ntor support, warn about the obsolete tor version,
1495 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
1497 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
1498 - Avoid a sandbox failure when trying to re-bind to a socket and
1499 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
1501 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
1502 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
1503 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
1506 Changes in version 0.3.1.5-alpha - 2017-08-01
1507 Tor 0.3.1.5-alpha improves the performance of consensus diff
1508 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
1509 several other bugs. If no serious bugs are found in this version, the
1510 next version will be a release candidate.
1512 This release also marks the end of support for the Tor 0.2.4.x,
1513 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
1514 further bug or security fixes. Anyone still running or distributing
1515 one of those versions should upgrade.
1517 o Major features (build system, continuous integration):
1518 - Tor's repository now includes a Travis Continuous Integration (CI)
1519 configuration file (.travis.yml). This is meant to help new
1520 developers and contributors who fork Tor to a Github repository be
1521 better able to test their changes, and understand what we expect
1522 to pass. To use this new build feature, you must fork Tor to your
1523 Github account, then go into the "Integrations" menu in the
1524 repository settings for your fork and enable Travis, then push
1525 your changes. Closes ticket 22636.
1527 o Major bugfixes (openbsd, denial-of-service):
1528 - Avoid an assertion failure bug affecting our implementation of
1529 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1530 handling of "0xbar" differs from what we had expected. Fixes bug
1531 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1533 o Major bugfixes (relay, performance):
1534 - Perform circuit handshake operations at a higher priority than we
1535 use for consensus diff creation and compression. This should
1536 prevent circuits from starving when a relay or bridge receives a
1537 new consensus, especially on lower-powered machines. Fixes bug
1538 22883; bugfix on 0.3.1.1-alpha.
1540 o Minor features (bridge authority):
1541 - Add "fingerprint" lines to the networkstatus-bridges file produced
1542 by bridge authorities. Closes ticket 22207.
1544 o Minor features (directory cache, consensus diff):
1545 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
1546 operators with low-resource environments to adjust the number of
1547 consensuses they'll store and generate diffs from. Most cache
1548 operators should leave it unchanged. Helps to work around
1551 o Minor features (geoip):
1552 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
1555 o Minor features (relay, performance):
1556 - Always start relays with at least two worker threads, to prevent
1557 priority inversion on slow tasks. Part of the fix for bug 22883.
1558 - Allow background work to be queued with different priorities, so
1559 that a big pile of slow low-priority jobs will not starve out
1560 higher priority jobs. This lays the groundwork for a fix for
1563 o Minor bugfixes (build system, rust):
1564 - Fix a problem where Rust toolchains were not being found when
1565 building without --enable-cargo-online-mode, due to setting the
1566 $HOME environment variable instead of $CARGO_HOME. Fixes bug
1567 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
1569 o Minor bugfixes (compatibility, zstd):
1570 - Write zstd epilogues correctly when the epilogue requires
1571 reallocation of the output buffer, even with zstd 1.3.0.
1572 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
1573 22927; bugfix on 0.3.1.1-alpha.
1575 o Minor bugfixes (compilation warnings):
1576 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
1577 22915; bugfix on 0.2.8.1-alpha.
1578 - Fix warnings when building with libscrypt and openssl scrypt
1579 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
1580 - Compile correctly when both openssl 1.1.0 and libscrypt are
1581 detected. Previously this would cause an error. Fixes bug 22892;
1582 bugfix on 0.3.1.1-alpha.
1583 - When building with certain versions of the mingw C header files,
1584 avoid float-conversion warnings when calling the C functions
1585 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
1588 o Minor bugfixes (coverity build support):
1589 - Avoid Coverity build warnings related to our BUG() macro. By
1590 default, Coverity treats BUG() as the Linux kernel does: an
1591 instant abort(). We need to override that so our BUG() macro
1592 doesn't prevent Coverity from analyzing functions that use it.
1593 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
1595 o Minor bugfixes (directory authority):
1596 - When a directory authority rejects a descriptor or extrainfo with
1597 a given digest, mark that digest as undownloadable, so that we do
1598 not attempt to download it again over and over. We previously
1599 tried to avoid downloading such descriptors by other means, but we
1600 didn't notice if we accidentally downloaded one anyway. This
1601 behavior became problematic in 0.2.7.2-alpha, when authorities
1602 began pinning Ed25519 keys. Fixes bug 22349; bugfix
1605 o Minor bugfixes (error reporting, windows):
1606 - When formatting Windows error messages, use the English format to
1607 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
1610 o Minor bugfixes (file limits, osx):
1611 - When setting the maximum number of connections allowed by the OS,
1612 always allow some extra file descriptors for other files. Fixes
1613 bug 22797; bugfix on 0.2.0.10-alpha.
1615 o Minor bugfixes (linux seccomp2 sandbox):
1616 - Avoid a sandbox failure when trying to re-bind to a socket and
1617 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
1619 o Minor bugfixes (memory leaks):
1620 - Fix a small memory leak when validating a configuration that uses
1621 two or more AF_UNIX sockets for the same port type. Fixes bug
1622 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
1624 o Minor bugfixes (unit tests):
1625 - test_consdiff_base64cmp would fail on OS X because while OS X
1626 follows the standard of (less than zero/zero/greater than zero),
1627 it doesn't follow the convention of (-1/0/+1). Make the test
1628 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
1629 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
1630 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
1633 Changes in version 0.3.1.4-alpha - 2017-06-29
1634 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
1635 to use a guard that was in the same network family as a chosen exit
1636 relay. This is a security regression; all clients running earlier
1637 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
1640 This release also fixes several other bugs introduced in 0.3.0.x
1641 and 0.3.1.x, including others that can affect bandwidth usage
1645 - To build with zstd and lzma support, Tor now requires the
1646 pkg-config tool at build time. (This requirement was new in
1647 0.3.1.1-alpha, but was not noted at the time. Noting it here to
1648 close ticket 22623.)
1650 o Major bugfixes (path selection, security):
1651 - When choosing which guard to use for a circuit, avoid the exit's
1652 family along with the exit itself. Previously, the new guard
1653 selection logic avoided the exit, but did not consider its family.
1654 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
1655 006 and CVE-2017-0377.
1657 o Major bugfixes (compression, zstd):
1658 - Correctly detect a full buffer when decompressing a large zstd-
1659 compressed input. Previously, we would sometimes treat a full
1660 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
1662 o Major bugfixes (directory protocol):
1663 - Ensure that we send "304 Not modified" as HTTP status code when a
1664 client is attempting to fetch a consensus or consensus diff, and
1665 the best one we can send them is one they already have. Fixes bug
1666 22702; bugfix on 0.3.1.1-alpha.
1668 o Major bugfixes (entry guards):
1669 - When starting with an old consensus, do not add new entry guards
1670 unless the consensus is "reasonably live" (under 1 day old). Fixes
1671 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
1673 o Minor features (bug mitigation, diagnostics, logging):
1674 - Avoid an assertion failure, and log a better error message, when
1675 unable to remove a file from the consensus cache on Windows.
1676 Attempts to mitigate and diagnose bug 22752.
1678 o Minor features (geoip):
1679 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
1682 o Minor bugfixes (compression):
1683 - When compressing or decompressing a buffer, check for a failure to
1684 create a compression object. Fixes bug 22626; bugfix
1686 - When decompressing a buffer, check for extra data after the end of
1687 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
1688 - When decompressing an object received over an anonymous directory
1689 connection, if we have already decompressed it using an acceptable
1690 compression method, do not reject it for looking like an
1691 unacceptable compression method. Fixes part of bug 22670; bugfix
1693 - When serving directory votes compressed with zlib, do not claim to
1694 have compressed them with zstd. Fixes bug 22669; bugfix
1696 - When spooling compressed data to an output buffer, don't try to
1697 spool more data when there is no more data to spool and we are not
1698 trying to flush the input. Previously, we would sometimes launch
1699 compression requests with nothing to do, which interferes with our
1700 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
1702 o Minor bugfixes (defensive programming):
1703 - Detect and break out of infinite loops in our compression code. We
1704 don't think that any such loops exist now, but it's best to be
1705 safe. Closes ticket 22672.
1706 - Fix a memset() off the end of an array when packing cells. This
1707 bug should be harmless in practice, since the corrupted bytes are
1708 still in the same structure, and are always padding bytes,
1709 ignored, or immediately overwritten, depending on compiler
1710 behavior. Nevertheless, because the memset()'s purpose is to make
1711 sure that any other cell-handling bugs can't expose bytes to the
1712 network, we need to fix it. Fixes bug 22737; bugfix on
1713 0.2.4.11-alpha. Fixes CID 1401591.
1715 o Minor bugfixes (linux seccomp2 sandbox):
1716 - Permit the fchmod system call, to avoid crashing on startup when
1717 starting with the seccomp2 sandbox and an unexpected set of
1718 permissions on the data directory or its contents. Fixes bug
1719 22516; bugfix on 0.2.5.4-alpha.
1720 - Fix a crash in the LZMA module, when the sandbox was enabled, and
1721 liblzma would allocate more than 16 MB of memory. We solve this by
1722 bumping the mprotect() limit in the sandbox module from 16 MB to
1723 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
1725 o Minor bugfixes (logging):
1726 - When decompressing, do not warn if we fail to decompress using a
1727 compression method that we merely guessed. Fixes part of bug
1728 22670; bugfix on 0.1.1.14-alpha.
1729 - When decompressing, treat mismatch between content-encoding and
1730 actual compression type as a protocol warning. Fixes part of bug
1731 22670; bugfix on 0.1.1.9-alpha.
1732 - Downgrade "assigned_to_cpuworker failed" message to info-level
1733 severity. In every case that can reach it, either a better warning
1734 has already been logged, or no warning is warranted. Fixes bug
1735 22356; bugfix on 0.2.6.3-alpha.
1736 - Demote a warn that was caused by libevent delays to info if
1737 netflow padding is less than 4.5 seconds late, or to notice
1738 if it is more (4.5 seconds is the amount of time that a netflow
1739 record might be emitted after, if we chose the maximum timeout).
1740 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
1742 o Minor bugfixes (process behavior):
1743 - When exiting because of an error, always exit with a nonzero exit
1744 status. Previously, we would fail to report an error in our exit
1745 status in cases related to __OwningControllerProcess failure,
1746 lockfile contention, and Ed25519 key initialization. Fixes bug
1747 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
1748 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
1752 - Add a manpage description for the key-pinning-journal file. Closes
1754 - Correctly note that bandwidth accounting values are stored in the
1755 state file, and the bw_accounting file is now obsolete. Closes
1757 - Document more of the files in the Tor data directory, including
1758 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
1759 approved-routers, sr-random, and diff-cache. Found while fixing
1763 Changes in version 0.3.0.9 - 2017-06-29
1764 Tor 0.3.0.9 fixes a path selection bug that would allow a client
1765 to use a guard that was in the same network family as a chosen exit
1766 relay. This is a security regression; all clients running earlier
1767 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
1770 This release also backports several other bugfixes from the 0.3.1.x
1773 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
1774 - When choosing which guard to use for a circuit, avoid the exit's
1775 family along with the exit itself. Previously, the new guard
1776 selection logic avoided the exit, but did not consider its family.
1777 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
1778 006 and CVE-2017-0377.
1780 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
1781 - Don't block bootstrapping when a primary bridge is offline and we
1782 can't get its descriptor. Fixes bug 22325; fixes one case of bug
1783 21969; bugfix on 0.3.0.3-alpha.
1785 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
1786 - When starting with an old consensus, do not add new entry guards
1787 unless the consensus is "reasonably live" (under 1 day old). Fixes
1788 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
1790 o Minor features (geoip):
1791 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
1794 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
1795 - Reject version numbers with non-numeric prefixes (such as +, -, or
1796 whitespace). Disallowing whitespace prevents differential version
1797 parsing between POSIX-based and Windows platforms. Fixes bug 21507
1798 and part of 21508; bugfix on 0.0.8pre1.
1800 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
1801 - Permit the fchmod system call, to avoid crashing on startup when
1802 starting with the seccomp2 sandbox and an unexpected set of
1803 permissions on the data directory or its contents. Fixes bug
1804 22516; bugfix on 0.2.5.4-alpha.
1806 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
1807 - Fix a memset() off the end of an array when packing cells. This
1808 bug should be harmless in practice, since the corrupted bytes are
1809 still in the same structure, and are always padding bytes,
1810 ignored, or immediately overwritten, depending on compiler
1811 behavior. Nevertheless, because the memset()'s purpose is to make
1812 sure that any other cell-handling bugs can't expose bytes to the
1813 network, we need to fix it. Fixes bug 22737; bugfix on
1814 0.2.4.11-alpha. Fixes CID 1401591.
1817 Changes in version 0.3.1.3-alpha - 2017-06-08
1818 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
1819 remotely crash a hidden service with an assertion failure. Anyone
1820 running a hidden service should upgrade to this version, or to some
1821 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
1823 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
1824 that sometimes made relays unreliable, as well as several other
1825 bugfixes described below.
1827 o Major bugfixes (hidden service, relay, security):
1828 - Fix a remotely triggerable assertion failure when a hidden service
1829 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
1830 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
1831 - Fix a remotely triggerable assertion failure caused by receiving a
1832 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1833 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1836 o Major bugfixes (relay, link handshake):
1837 - When performing the v3 link handshake on a TLS connection, report
1838 that we have the x509 certificate that we actually used on that
1839 connection, even if we have changed certificates since that
1840 connection was first opened. Previously, we would claim to have
1841 used our most recent x509 link certificate, which would sometimes
1842 make the link handshake fail. Fixes one case of bug 22460; bugfix
1845 o Major bugfixes (relays, key management):
1846 - Regenerate link and authentication certificates whenever the key
1847 that signs them changes; also, regenerate link certificates
1848 whenever the signed key changes. Previously, these processes were
1849 only weakly coupled, and we relays could (for minutes to hours)
1850 wind up with an inconsistent set of keys and certificates, which
1851 other relays would not accept. Fixes two cases of bug 22460;
1852 bugfix on 0.3.0.1-alpha.
1853 - When sending an Ed25519 signing->link certificate in a CERTS cell,
1854 send the certificate that matches the x509 certificate that we
1855 used on the TLS connection. Previously, there was a race condition
1856 if the TLS context rotated after we began the TLS handshake but
1857 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
1860 o Major bugfixes (torrc, crash):
1861 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
1862 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
1864 o Minor features (code style):
1865 - Add "Falls through" comments to our codebase, in order to silence
1866 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1867 Stieger. Closes ticket 22446.
1869 o Minor features (diagnostic):
1870 - Add logging messages to try to diagnose a rare bug that seems to
1871 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
1872 think this is happening because of incorrect system clocks, but
1873 we'd like to know for certain. Diagnostic for bug 22466.
1875 o Minor bugfixes (correctness):
1876 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1877 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1879 o Minor bugfixes (directory protocol):
1880 - Check for libzstd >= 1.1, because older versions lack the
1881 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
1883 o Minor bugfixes (link handshake):
1884 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
1885 months, and regenerate it when it is within one month of expiring.
1886 Previously, we had generated this certificate at startup with a
1887 ten-year lifetime, but that could lead to weird behavior when Tor
1888 was started with a grossly inaccurate clock. Mitigates bug 22466;
1889 mitigation on 0.3.0.1-alpha.
1891 o Minor bugfixes (storage directories):
1892 - Always check for underflows in the cached storage directory usage.
1893 If the usage does underflow, re-calculate it. Also, avoid a
1894 separate underflow when the usage is not known. Fixes bug 22424;
1895 bugfix on 0.3.1.1-alpha.
1897 o Minor bugfixes (unit tests):
1898 - The unit tests now pass on systems where localhost is misconfigured
1899 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
1903 - Clarify the manpage for the (deprecated) torify script. Closes
1906 Changes in version 0.3.0.8 - 2017-06-08
1907 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
1908 remotely crash a hidden service with an assertion failure. Anyone
1909 running a hidden service should upgrade to this version, or to some
1910 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
1912 Tor 0.3.0.8 also includes fixes for several key management bugs
1913 that sometimes made relays unreliable, as well as several other
1914 bugfixes described below.
1916 o Major bugfixes (hidden service, relay, security, backport
1917 from 0.3.1.3-alpha):
1918 - Fix a remotely triggerable assertion failure when a hidden service
1919 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
1920 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
1921 - Fix a remotely triggerable assertion failure caused by receiving a
1922 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1923 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1926 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
1927 - When performing the v3 link handshake on a TLS connection, report
1928 that we have the x509 certificate that we actually used on that
1929 connection, even if we have changed certificates since that
1930 connection was first opened. Previously, we would claim to have
1931 used our most recent x509 link certificate, which would sometimes
1932 make the link handshake fail. Fixes one case of bug 22460; bugfix
1935 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
1936 - Regenerate link and authentication certificates whenever the key
1937 that signs them changes; also, regenerate link certificates
1938 whenever the signed key changes. Previously, these processes were
1939 only weakly coupled, and we relays could (for minutes to hours)
1940 wind up with an inconsistent set of keys and certificates, which
1941 other relays would not accept. Fixes two cases of bug 22460;
1942 bugfix on 0.3.0.1-alpha.
1943 - When sending an Ed25519 signing->link certificate in a CERTS cell,
1944 send the certificate that matches the x509 certificate that we
1945 used on the TLS connection. Previously, there was a race condition
1946 if the TLS context rotated after we began the TLS handshake but
1947 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
1950 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
1951 - Stop rejecting v3 hidden service descriptors because their size
1952 did not match an old padding rule. Fixes bug 22447; bugfix on
1955 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
1956 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
1957 December 2016 (of which ~126 were still functional) with a list of
1958 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
1959 2017. Resolves ticket 21564.
1961 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
1962 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
1963 bug 22252; bugfix on 0.2.9.3-alpha.
1965 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
1966 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1967 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1969 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
1970 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
1971 months, and regenerate it when it is within one month of expiring.
1972 Previously, we had generated this certificate at startup with a
1973 ten-year lifetime, but that could lead to weird behavior when Tor
1974 was started with a grossly inaccurate clock. Mitigates bug 22466;
1975 mitigation on 0.3.0.1-alpha.
1977 o Minor bugfixes (memory leak, directory authority, backport from
1979 - When directory authorities reject a router descriptor due to
1980 keypinning, free the router descriptor rather than leaking the
1981 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
1984 Changes in version 0.2.9.11 - 2017-06-08
1985 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
1986 remotely crash a hidden service with an assertion failure. Anyone
1987 running a hidden service should upgrade to this version, or to some
1988 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
1989 are not affected by TROVE-2017-004.)
1991 Tor 0.2.9.11 also backports fixes for several key management bugs
1992 that sometimes made relays unreliable, as well as several other
1993 bugfixes described below.
1995 o Major bugfixes (hidden service, relay, security, backport
1996 from 0.3.1.3-alpha):
1997 - Fix a remotely triggerable assertion failure caused by receiving a
1998 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1999 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2002 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
2003 - When performing the v3 link handshake on a TLS connection, report
2004 that we have the x509 certificate that we actually used on that
2005 connection, even if we have changed certificates since that
2006 connection was first opened. Previously, we would claim to have
2007 used our most recent x509 link certificate, which would sometimes
2008 make the link handshake fail. Fixes one case of bug 22460; bugfix
2011 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2012 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2013 December 2016 (of which ~126 were still functional) with a list of
2014 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2015 2017. Resolves ticket 21564.
2017 o Minor features (future-proofing, backport from 0.3.0.7):
2018 - Tor no longer refuses to download microdescriptors or descriptors if
2019 they are listed as "published in the future". This change will
2020 eventually allow us to stop listing meaningful "published" dates
2021 in microdescriptor consensuses, and thereby allow us to reduce the
2022 resources required to download consensus diffs by over 50%.
2023 Implements part of ticket 21642; implements part of proposal 275.
2025 o Minor features (directory authorities, backport from 0.3.0.4-rc)
2026 - Directory authorities now reject relays running versions
2027 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
2028 suffer from bug 20499 and don't keep their consensus cache
2029 up-to-date. Resolves ticket 20509.
2031 o Minor features (geoip):
2032 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2035 o Minor bugfixes (control port, backport from 0.3.0.6):
2036 - The GETINFO extra-info/digest/<digest> command was broken because
2037 of a wrong base16 decode return value check, introduced when
2038 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
2040 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
2041 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2042 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2044 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
2045 - The getpid() system call is now permitted under the Linux seccomp2
2046 sandbox, to avoid crashing with versions of OpenSSL (and other
2047 libraries) that attempt to learn the process's PID by using the
2048 syscall rather than the VDSO code. Fixes bug 21943; bugfix
2051 o Minor bugfixes (memory leak, directory authority, backport
2052 from 0.3.1.2-alpha):
2053 - When directory authorities reject a router descriptor due to
2054 keypinning, free the router descriptor rather than leaking the
2055 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2057 Changes in version 0.2.8.14 - 2017-06-08
2058 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
2059 remotely crash a hidden service with an assertion failure. Anyone
2060 running a hidden service should upgrade to this version, or to some
2061 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2062 are not affected by TROVE-2017-004.)
2064 o Major bugfixes (hidden service, relay, security):
2065 - Fix a remotely triggerable assertion failure caused by receiving a
2066 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2067 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2070 o Minor features (geoip):
2071 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2074 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2075 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2076 December 2016 (of which ~126 were still functional) with a list of
2077 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2078 2017. Resolves ticket 21564.
2080 o Minor bugfixes (correctness):
2081 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2082 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2084 Changes in version 0.2.7.8 - 2017-06-08
2085 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
2086 remotely crash a hidden service with an assertion failure. Anyone
2087 running a hidden service should upgrade to this version, or to some
2088 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2089 are not affected by TROVE-2017-004.)
2091 o Major bugfixes (hidden service, relay, security):
2092 - Fix a remotely triggerable assertion failure caused by receiving a
2093 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2094 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2097 o Minor features (geoip):
2098 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2101 o Minor bugfixes (correctness):
2102 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2103 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2106 Changes in version 0.2.6.12 - 2017-06-08
2107 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
2108 remotely crash a hidden service with an assertion failure. Anyone
2109 running a hidden service should upgrade to this version, or to some
2110 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2111 are not affected by TROVE-2017-004.)
2113 o Major bugfixes (hidden service, relay, security):
2114 - Fix a remotely triggerable assertion failure caused by receiving a
2115 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2116 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2119 o Minor features (geoip):
2120 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2123 o Minor bugfixes (correctness):
2124 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2125 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2127 Changes in version 0.2.5.14 - 2017-06-08
2128 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
2129 remotely crash a hidden service with an assertion failure. Anyone
2130 running a hidden service should upgrade to this version, or to some
2131 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2132 are not affected by TROVE-2017-004.)
2134 o Major bugfixes (hidden service, relay, security):
2135 - Fix a remotely triggerable assertion failure caused by receiving a
2136 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2137 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2140 o Minor features (geoip):
2141 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2144 o Minor bugfixes (correctness):
2145 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2146 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2148 Changes in version 0.2.4.29 - 2017-06-08
2149 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
2150 remotely crash a hidden service with an assertion failure. Anyone
2151 running a hidden service should upgrade to this version, or to some
2152 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2153 are not affected by TROVE-2017-004.)
2155 o Major bugfixes (hidden service, relay, security):
2156 - Fix a remotely triggerable assertion failure caused by receiving a
2157 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2158 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2161 o Minor features (geoip):
2162 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2165 o Minor bugfixes (correctness):
2166 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2167 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2170 Changes in version 0.3.1.2-alpha - 2017-05-26
2171 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
2172 fixes a few bugs found while testing 0.3.1.1-alpha, including a
2173 memory corruption bug that affected relay stability.
2175 o Major bugfixes (crash, relay):
2176 - Fix a memory-corruption bug in relays that set MyFamily.
2177 Previously, they would double-free MyFamily elements when making
2178 the next descriptor or when changing their configuration. Fixes
2179 bug 22368; bugfix on 0.3.1.1-alpha.
2181 o Minor bugfixes (logging):
2182 - Log a better message when a directory authority replies to an
2183 upload with an unexpected status code. Fixes bug 11121; bugfix
2186 o Minor bugfixes (memory leak, directory authority):
2187 - When directory authorities reject a router descriptor due to
2188 keypinning, free the router descriptor rather than leaking the
2189 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2192 Changes in version 0.3.1.1-alpha - 2017-05-22
2193 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
2194 reduces the bandwidth usage for Tor's directory protocol, adds some
2195 basic padding to resist netflow-based traffic analysis and to serve as
2196 the basis of other padding in the future, and adds rust support to the
2199 It also contains numerous other small features and improvements to
2200 security, correctness, and performance.
2202 Below are the changes since 0.3.0.7.
2204 o Major features (directory protocol):
2205 - Tor relays and authorities can now serve clients an abbreviated
2206 version of the consensus document, containing only the changes
2207 since an older consensus document that the client holds. Clients
2208 now request these documents when available. When both client and
2209 server use this new protocol, they will use far less bandwidth (up
2210 to 94% less) to keep the client's consensus up-to-date. Implements
2211 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
2212 - Tor can now compress directory traffic with lzma or with zstd
2213 compression algorithms, which can deliver better bandwidth
2214 performance. Because lzma is computationally expensive, it's only
2215 used for documents that can be compressed once and served many
2216 times. Support for these algorithms requires that tor is built
2217 with the libzstd and/or liblzma libraries available. Implements
2218 proposal 278; closes ticket 21662.
2219 - Relays now perform the more expensive compression operations, and
2220 consensus diff generation, in worker threads. This separation
2221 avoids delaying the main thread when a new consensus arrives.
2223 o Major features (experimental):
2224 - Tor can now build modules written in Rust. To turn this on, pass
2225 the "--enable-rust" flag to the configure script. It's not time to
2226 get excited yet: currently, there is no actual Rust functionality
2227 beyond some simple glue code, and a notice at startup to tell you
2228 that Rust is running. Still, we hope that programmers and
2229 packagers will try building Tor with Rust support, so that we can
2230 find issues and solve portability problems. Closes ticket 22106.
2232 o Major features (traffic analysis resistance):
2233 - Connections between clients and relays now send a padding cell in
2234 each direction every 1.5 to 9.5 seconds (tunable via consensus
2235 parameters). This padding will not resist specialized
2236 eavesdroppers, but it should be enough to make many ISPs' routine
2237 network flow logging less useful in traffic analysis against
2240 Padding is negotiated using Tor's link protocol, so both relays
2241 and clients must upgrade for this to take effect. Clients may
2242 still send padding despite the relay's version by setting
2243 ConnectionPadding 1 in torrc, and may disable padding by setting
2244 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
2245 users with the torrc option ReducedConnectionPadding. Implements
2246 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
2247 - Relays will publish 24 hour totals of padding and non-padding cell
2248 counts to their extra-info descriptors, unless PaddingStatistics 0
2249 is set in torrc. These 24 hour totals are also rounded to
2252 o Major bugfixes (connection usage):
2253 - We use NETINFO cells to try to determine if both relays involved
2254 in a connection will agree on the canonical status of that
2255 connection. We prefer the connections where this is the case for
2256 extend cells, and try to close connections where relays disagree
2257 on their canonical status early. Also, we now prefer the oldest
2258 valid connection for extend cells. These two changes should reduce
2259 the number of long-term connections that are kept open between
2260 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
2261 - Relays now log hourly statistics (look for
2262 "channel_check_for_duplicates" lines) on the total number of
2263 connections to other relays. If the number of connections per
2264 relay is unexpectedly large, this log message is at notice level.
2265 Otherwise it is at info.
2267 o Major bugfixes (entry guards):
2268 - Don't block bootstrapping when a primary bridge is offline and we
2269 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2270 21969; bugfix on 0.3.0.3-alpha.
2272 o Major bugfixes (linux TPROXY support):
2273 - Fix a typo that had prevented TPROXY-based transparent proxying
2274 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2275 Patch from "d4fq0fQAgoJ".
2277 o Minor features (security, windows):
2278 - Enable a couple of pieces of Windows hardening: one
2279 (HeapEnableTerminationOnCorruption) that has been on-by-default
2280 since Windows 8, and unavailable before Windows 7; and one
2281 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2282 affect us, but shouldn't do any harm. Closes ticket 21953.
2284 o Minor features (config options):
2285 - Allow "%include" directives in torrc configuration files. These
2286 directives import the settings from other files, or from all the
2287 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
2288 - Make SAVECONF return an error when overwriting a torrc that has
2289 includes. Using SAVECONF with the FORCE option will allow it to
2290 overwrite torrc even if includes are used. Related to ticket 1922.
2291 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
2292 will work without the FORCE option. Related to ticket 1922.
2294 o Minor features (controller):
2295 - Warn the first time that a controller requests data in the long-
2296 deprecated 'GETINFO network-status' format. Closes ticket 21703.
2298 o Minor features (defaults):
2299 - The default value for UseCreateFast is now 0: clients which
2300 haven't yet received a consensus document will now use a proper
2301 ntor handshake to talk to their directory servers whenever they
2302 can. Closes ticket 21407.
2303 - Onion key rotation and expiry intervals are now defined as a
2304 network consensus parameter, per proposal 274. The default
2305 lifetime of an onion key is increased from 7 to 28 days. Old onion
2306 keys will expire after 7 days by default. This change will make
2307 consensus diffs much smaller, and save significant bandwidth.
2308 Closes ticket 21641.
2310 o Minor features (fallback directory list):
2311 - Update the fallback directory mirror whitelist and blacklist based
2312 on operator emails. Closes task 21121.
2313 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2314 December 2016 (of which ~126 were still functional) with a list of
2315 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2316 2017. Resolves ticket 21564.
2318 o Minor features (hidden services, logging):
2319 - Log a message when a hidden service descriptor has fewer
2320 introduction points than specified in
2321 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
2322 - Log a message when a hidden service reaches its introduction point
2323 circuit limit, and when that limit is reset. Follow up to ticket
2324 21594; closes ticket 21622.
2325 - Warn user if multiple entries in EntryNodes and at least one
2326 HiddenService are used together. Pinning EntryNodes along with a
2327 hidden service can be possibly harmful; for instance see ticket
2328 14917 or 21155. Closes ticket 21155.
2330 o Minor features (linux seccomp2 sandbox):
2331 - We now have a document storage backend compatible with the Linux
2332 seccomp2 sandbox. This backend is used for consensus documents and
2333 diffs between them; in the long term, we'd like to use it for
2334 unparseable directory material too. Closes ticket 21645
2335 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
2336 from 1MB to 16MB. This was necessary with the glibc allocator in
2337 order to allow worker threads to allocate more memory -- which in
2338 turn is necessary because of our new use of worker threads for
2339 compression. Closes ticket 22096.
2341 o Minor features (logging):
2342 - Log files are no longer created world-readable by default.
2343 (Previously, most distributors would store the logs in a non-
2344 world-readable location to prevent inappropriate access. This
2345 change is an extra precaution.) Closes ticket 21729; patch
2348 o Minor features (performance):
2349 - Our Keccak (SHA-3) implementation now accesses memory more
2350 efficiently, especially on little-endian systems. Closes
2352 - Add an O(1) implementation of channel_find_by_global_id(), to
2353 speed some controller functions.
2355 o Minor features (relay, configuration):
2356 - The MyFamily option may now be repeated as many times as desired,
2357 for relays that want to configure large families. Closes ticket
2358 4998; patch by Daniel Pinto.
2360 o Minor features (safety):
2361 - Add an explicit check to extrainfo_parse_entry_from_string() for
2362 NULL inputs. We don't believe this can actually happen, but it may
2363 help silence a warning from the Clang analyzer. Closes
2366 o Minor features (testing):
2367 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
2368 When Tor is compiled with this option, we disable a number of
2369 redundant memory-safety failsafes that are intended to stop bugs
2370 from becoming security issues. This makes it easier to hunt for
2371 bugs that would be security issues without the failsafes turned
2372 on. Closes ticket 21439.
2373 - Add a general event-tracing instrumentation support to Tor. This
2374 subsystem will enable developers and researchers to add fine-
2375 grained instrumentation to their Tor instances, for use when
2376 examining Tor network performance issues. There are no trace
2377 events yet, and event-tracing is off by default unless enabled at
2378 compile time. Implements ticket 13802.
2379 - Improve our version parsing tests: add tests for typical version
2380 components, add tests for invalid versions, including numeric
2381 range and non-numeric prefixes. Unit tests 21278, 21450, and
2382 21507. Partially implements 21470.
2384 o Minor bugfixes (bandwidth accounting):
2385 - Roll over monthly accounting at the configured hour and minute,
2386 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2387 Found by Andrey Karpov with PVS-Studio.
2389 o Minor bugfixes (code correctness):
2390 - Accurately identify client connections by their lack of peer
2391 authentication. This means that we bail out earlier if asked to
2392 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
2395 o Minor bugfixes (configuration):
2396 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
2397 bug 22252; bugfix on 0.2.9.3-alpha.
2399 o Minor bugfixes (connection lifespan):
2400 - Allow more control over how long TLS connections are kept open:
2401 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
2402 single option called CircuitsAvailableTimeout. Also, allow the
2403 consensus to control the default values for both this preference
2404 and the lifespan of relay-to-relay connections. Fixes bug 17592;
2405 bugfix on 0.2.5.5-alpha.
2406 - Increase the initial circuit build timeout testing frequency, to
2407 help ensure that ReducedConnectionPadding clients finish learning
2408 a timeout before their orconn would expire. The initial testing
2409 rate was set back in the days of TAP and before the Tor Browser
2410 updater, when we had to be much more careful about new clients
2411 making lots of circuits. With this change, a circuit build timeout
2412 is learned in about 15-20 minutes, instead of 100-120 minutes.
2414 o Minor bugfixes (controller):
2415 - GETINFO onions/current and onions/detached no longer respond with
2416 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
2417 - Trigger HS descriptor events on the control port when the client
2418 fails to pick a hidden service directory for a hidden service.
2419 This can happen if all the hidden service directories are in
2420 ExcludeNodes, or they have all been queried within the last 15
2421 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
2423 o Minor bugfixes (directory authority):
2424 - When rejecting a router descriptor for running an obsolete version
2425 of Tor without ntor support, warn about the obsolete tor version,
2426 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2427 - Prevent the shared randomness subsystem from asserting when
2428 initialized by a bridge authority with an incomplete configuration
2429 file. Fixes bug 21586; bugfix on 0.2.9.8.
2431 o Minor bugfixes (exit-side DNS):
2432 - Fix an untriggerable assertion that checked the output of a
2433 libevent DNS error, so that the assertion actually behaves as
2434 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
2435 Karpov using PVS-Studio.
2437 o Minor bugfixes (fallback directories):
2438 - Make the usage example in updateFallbackDirs.py actually work, and
2439 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
2440 - Decrease the guard flag average required to be a fallback. This
2441 allows us to keep relays that have their guard flag removed when
2442 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2443 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
2444 bugfix on 0.2.8.1-alpha.
2445 - Make sure fallback directory mirrors have the same address, port,
2446 and relay identity key for at least 30 days before they are
2447 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2449 o Minor bugfixes (hidden services):
2450 - Stop printing a cryptic warning when a hidden service gets a
2451 request to connect to a virtual port that it hasn't configured.
2452 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
2453 - Simplify hidden service descriptor creation by using an existing
2454 flag to check if an introduction point is established. Fixes bug
2455 21599; bugfix on 0.2.7.2-alpha.
2457 o Minor bugfixes (memory leak):
2458 - Fix a small memory leak at exit from the backtrace handler code.
2459 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
2461 o Minor bugfixes (protocol, logging):
2462 - Downgrade a log statement about unexpected relay cells from "bug"
2463 to "protocol warning", because there is at least one use case
2464 where it can be triggered by a buggy tor implementation. Fixes bug
2465 21293; bugfix on 0.1.1.14-alpha.
2467 o Minor bugfixes (testing):
2468 - Use unbuffered I/O for utility functions around the
2469 process_handle_t type. This fixes unit test failures reported on
2470 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
2471 - Make display of captured unit test log messages consistent. Fixes
2472 bug 21510; bugfix on 0.2.9.3-alpha.
2473 - Make test-network.sh always call chutney's test-network.sh.
2474 Previously, this only worked on systems which had bash installed,
2475 due to some bash-specific code in the script. Fixes bug 19699;
2476 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
2478 o Minor bugfixes (voting consistency):
2479 - Reject version numbers with non-numeric prefixes (such as +, -, or
2480 whitespace). Disallowing whitespace prevents differential version
2481 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2482 and part of 21508; bugfix on 0.0.8pre1.
2484 o Minor bugfixes (windows, relay):
2485 - Resolve "Failure from drain_fd: No error" warnings on Windows
2486 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
2488 o Code simplification and refactoring:
2489 - Break up the 630-line function connection_dir_client_reached_eof()
2490 into a dozen smaller functions. This change should help
2491 maintainability and readability of the client directory code.
2492 - Isolate our use of the openssl headers so that they are only
2493 included from our crypto wrapper modules, and from tests that
2494 examine those modules' internals. Closes ticket 21841.
2495 - Simplify our API to launch directory requests, making it more
2496 extensible and less error-prone. Now it's easier to add extra
2497 headers to directory requests. Closes ticket 21646.
2498 - Our base64 decoding functions no longer overestimate the output
2499 space that they need when parsing unpadded inputs. Closes
2501 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
2502 Resolves ticket 22213.
2503 - The logic that directory caches use to spool request to clients,
2504 serving them one part at a time so as not to allocate too much
2505 memory, has been refactored for consistency. Previously there was
2506 a separate spooling implementation per type of spoolable data. Now
2507 there is one common spooling implementation, with extensible data
2508 types. Closes ticket 21651.
2509 - Tor's compression module now supports multiple backends. Part of
2510 the implementation for proposal 278; closes ticket 21663.
2513 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
2514 Closes ticket 21873.
2515 - Correct documentation about the default DataDirectory value.
2516 Closes ticket 21151.
2517 - Document the default behavior of NumEntryGuards and
2518 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
2520 - Document key=value pluggable transport arguments for Bridge lines
2521 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
2522 - Note that bandwidth-limiting options don't affect TCP headers or
2523 DNS. Closes ticket 17170.
2525 o Removed features (configuration options, all in ticket 22060):
2526 - These configuration options are now marked Obsolete, and no longer
2527 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
2528 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
2529 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
2530 in 0.2.9.2-alpha and have now been removed. The previous default
2531 behavior is now always chosen; the previous (less secure) non-
2532 default behavior is now unavailable.
2533 - CloseHSClientCircuitsImmediatelyOnTimeout and
2534 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
2535 0.2.9.2-alpha and now have been removed. HS circuits never close
2536 on circuit build timeout; they have a longer timeout period.
2537 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
2538 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
2539 (and others) to configure listen-only and advertise-only addresses.
2541 o Removed features (tools):
2542 - We've removed the tor-checkkey tool from src/tools. Long ago, we
2543 used it to help people detect RSA keys that were generated by
2544 versions of Debian affected by CVE-2008-0166. But those keys have
2545 been out of circulation for ages, and this tool is no longer
2546 required. Closes ticket 21842.
2549 Changes in version 0.3.0.7 - 2017-05-15
2550 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
2551 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
2552 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
2553 clients are not affected.
2555 o Major bugfixes (hidden service directory, security):
2556 - Fix an assertion failure in the hidden service directory code, which
2557 could be used by an attacker to remotely cause a Tor relay process to
2558 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
2559 should upgrade. This security issue is tracked as TROVE-2017-002.
2560 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
2563 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2566 o Minor features (future-proofing):
2567 - Tor no longer refuses to download microdescriptors or descriptors
2568 if they are listed as "published in the future". This change will
2569 eventually allow us to stop listing meaningful "published" dates
2570 in microdescriptor consensuses, and thereby allow us to reduce the
2571 resources required to download consensus diffs by over 50%.
2572 Implements part of ticket 21642; implements part of proposal 275.
2574 o Minor bugfixes (Linux seccomp2 sandbox):
2575 - The getpid() system call is now permitted under the Linux seccomp2
2576 sandbox, to avoid crashing with versions of OpenSSL (and other
2577 libraries) that attempt to learn the process's PID by using the
2578 syscall rather than the VDSO code. Fixes bug 21943; bugfix
2582 Changes in version 0.3.0.6 - 2017-04-26
2583 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
2585 With the 0.3.0 series, clients and relays now use Ed25519 keys to
2586 authenticate their link connections to relays, rather than the old
2587 RSA1024 keys that they used before. (Circuit crypto has been
2588 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
2589 the guard selection and replacement algorithm to behave more robustly
2590 in the presence of unreliable networks, and to resist guard-
2593 This series also includes numerous other small features and bugfixes,
2594 along with more groundwork for the upcoming hidden-services revamp.
2596 Per our stable release policy, we plan to support the Tor 0.3.0
2597 release series for at least the next nine months, or for three months
2598 after the first stable release of the 0.3.1 series: whichever is
2599 longer. If you need a release with long-term support, we recommend
2600 that you stay with the 0.2.9 series.
2602 Below are the changes since 0.3.0.5-rc. For a list of all changes
2603 since 0.2.9, see the ReleaseNotes file.
2605 o Minor features (geoip):
2606 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
2609 o Minor bugfixes (control port):
2610 - The GETINFO extra-info/digest/<digest> command was broken because
2611 of a wrong base16 decode return value check, introduced when
2612 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
2614 o Minor bugfixes (crash prevention):
2615 - Fix a (currently untriggerable, but potentially dangerous) crash
2616 bug when base32-encoding inputs whose sizes are not a multiple of
2617 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
2620 Changes in version 0.3.0.5-rc - 2017-04-05
2621 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
2622 0.3.0 release series.
2624 This is the second release candidate in the Tor 0.3.0 series, and has
2625 much fewer changes than the first. If we find no new bugs or
2626 regressions here, the first stable 0.3.0 release will be nearly
2629 o Major bugfixes (crash, directory connections):
2630 - Fix a rare crash when sending a begin cell on a circuit whose
2631 linked directory connection had already been closed. Fixes bug
2632 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
2634 o Major bugfixes (guard selection):
2635 - Fix a guard selection bug where Tor would refuse to bootstrap in
2636 some cases if the user swapped a bridge for another bridge in
2637 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
2638 Reported by "torvlnt33r".
2640 o Minor features (geoip):
2641 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
2644 o Minor bugfix (compilation):
2645 - Fix a warning when compiling hs_service.c. Previously, it had no
2646 exported symbols when compiled for libor.a, resulting in a
2647 compilation warning from clang. Fixes bug 21825; bugfix
2650 o Minor bugfixes (hidden services):
2651 - Make hidden services check for failed intro point connections,
2652 even when they have exceeded their intro point creation limit.
2653 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
2654 - Make hidden services with 8 to 10 introduction points check for
2655 failed circuits immediately after startup. Previously, they would
2656 wait for 5 minutes before performing their first checks. Fixes bug
2657 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
2659 o Minor bugfixes (memory leaks):
2660 - Fix a memory leak when using GETCONF on a port option. Fixes bug
2661 21682; bugfix on 0.3.0.3-alpha.
2663 o Minor bugfixes (relay):
2664 - Avoid a double-marked-circuit warning that could happen when we
2665 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
2668 o Minor bugfixes (tests):
2669 - Run the entry_guard_parse_from_state_full() test with the time set
2670 to a specific date. (The guard state that this test was parsing
2671 contained guards that had expired since the test was first
2672 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
2675 - Update the description of the directory server options in the
2676 manual page, to clarify that a relay no longer needs to set
2677 DirPort in order to be a directory cache. Closes ticket 21720.
2681 Changes in version 0.2.8.13 - 2017-03-03
2682 Tor 0.2.8.13 backports a security fix from later Tor
2683 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
2684 this release, if for some reason they cannot upgrade to a later
2685 release series, and if they build Tor with the --enable-expensive-hardening
2688 Note that support for Tor 0.2.8.x is ending next year: we will not issue
2689 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
2690 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
2692 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
2693 - Fix an integer underflow bug when comparing malformed Tor
2694 versions. This bug could crash Tor when built with
2695 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2696 0.2.9.8, which were built with -ftrapv by default. In other cases
2697 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2698 on 0.0.8pre1. Found by OSS-Fuzz.
2700 o Minor features (geoip):
2701 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2705 Changes in version 0.2.7.7 - 2017-03-03
2706 Tor 0.2.7.7 backports a number of security fixes from later Tor
2707 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
2708 this release, if for some reason they cannot upgrade to a later
2711 Note that support for Tor 0.2.7.x is ending this year: we will not issue
2712 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
2713 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
2715 o Directory authority changes (backport from 0.2.8.5-rc):
2716 - Urras is no longer a directory authority. Closes ticket 19271.
2718 o Directory authority changes (backport from 0.2.9.2-alpha):
2719 - The "Tonga" bridge authority has been retired; the new bridge
2720 authority is "Bifroest". Closes tickets 19728 and 19690.
2722 o Directory authority key updates (backport from 0.2.8.1-alpha):
2723 - Update the V3 identity key for the dannenberg directory authority:
2724 it was changed on 18 November 2015. Closes task 17906. Patch
2727 o Major bugfixes (parsing, security, backport from 0.2.9.8):
2728 - Fix a bug in parsing that could cause clients to read a single
2729 byte past the end of an allocated region. This bug could be used
2730 to cause hardened clients (built with --enable-expensive-hardening)
2731 to crash if they tried to visit a hostile hidden service. Non-
2732 hardened clients are only affected depending on the details of
2733 their platform's memory allocator. Fixes bug 21018; bugfix on
2734 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2735 2016-12-002 and as CVE-2016-1254.
2737 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
2738 - Stop a crash that could occur when a client running with DNSPort
2739 received a query with multiple address types, and the first
2740 address type was not supported. Found and fixed by Scott Dial.
2741 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
2742 - Prevent a class of security bugs caused by treating the contents
2743 of a buffer chunk as if they were a NUL-terminated string. At
2744 least one such bug seems to be present in all currently used
2745 versions of Tor, and would allow an attacker to remotely crash
2746 most Tor instances, especially those compiled with extra compiler
2747 hardening. With this defense in place, such bugs can't crash Tor,
2748 though we should still fix them as they occur. Closes ticket
2749 20384 (TROVE-2016-10-001).
2751 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
2752 - Avoid a difficult-to-trigger heap corruption attack when extending
2753 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
2754 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
2755 Reported by Guido Vranken.
2757 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
2758 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
2759 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
2761 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
2762 - If OpenSSL fails to generate an RSA key, do not retain a dangling
2763 pointer to the previous (uninitialized) key value. The impact here
2764 should be limited to a difficult-to-trigger crash, if OpenSSL is
2765 running an engine that makes key generation failures possible, or
2766 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
2767 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
2770 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
2771 - Fix an integer underflow bug when comparing malformed Tor
2772 versions. This bug could crash Tor when built with
2773 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2774 0.2.9.8, which were built with -ftrapv by default. In other cases
2775 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2776 on 0.0.8pre1. Found by OSS-Fuzz.
2778 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
2779 - Make memwipe() do nothing when passed a NULL pointer or buffer of
2780 zero size. Check size argument to memwipe() for underflow. Fixes
2781 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
2784 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
2785 - Make Tor survive errors involving connections without a
2786 corresponding event object. Previously we'd fail with an
2787 assertion; now we produce a log message. Related to bug 16248.
2789 o Minor features (geoip):
2790 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2794 Changes in version 0.2.6.11 - 2017-03-03
2795 Tor 0.2.6.11 backports a number of security fixes from later Tor
2796 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
2797 this release, if for some reason they cannot upgrade to a later
2800 Note that support for Tor 0.2.6.x is ending this year: we will not issue
2801 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
2802 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
2804 o Directory authority changes (backport from 0.2.8.5-rc):
2805 - Urras is no longer a directory authority. Closes ticket 19271.
2807 o Directory authority changes (backport from 0.2.9.2-alpha):
2808 - The "Tonga" bridge authority has been retired; the new bridge
2809 authority is "Bifroest". Closes tickets 19728 and 19690.
2811 o Directory authority key updates (backport from 0.2.8.1-alpha):
2812 - Update the V3 identity key for the dannenberg directory authority:
2813 it was changed on 18 November 2015. Closes task 17906. Patch
2816 o Major features (security fixes, backport from 0.2.9.4-alpha):
2817 - Prevent a class of security bugs caused by treating the contents
2818 of a buffer chunk as if they were a NUL-terminated string. At
2819 least one such bug seems to be present in all currently used
2820 versions of Tor, and would allow an attacker to remotely crash
2821 most Tor instances, especially those compiled with extra compiler
2822 hardening. With this defense in place, such bugs can't crash Tor,
2823 though we should still fix them as they occur. Closes ticket
2824 20384 (TROVE-2016-10-001).
2826 o Major bugfixes (parsing, security, backport from 0.2.9.8):
2827 - Fix a bug in parsing that could cause clients to read a single
2828 byte past the end of an allocated region. This bug could be used
2829 to cause hardened clients (built with --enable-expensive-hardening)
2830 to crash if they tried to visit a hostile hidden service. Non-
2831 hardened clients are only affected depending on the details of
2832 their platform's memory allocator. Fixes bug 21018; bugfix on
2833 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2834 2016-12-002 and as CVE-2016-1254.
2836 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
2837 - Stop a crash that could occur when a client running with DNSPort
2838 received a query with multiple address types, and the first
2839 address type was not supported. Found and fixed by Scott Dial.
2840 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
2842 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
2843 - Fix an error that could cause us to read 4 bytes before the
2844 beginning of an openssl string. This bug could be used to cause
2845 Tor to crash on systems with unusual malloc implementations, or
2846 systems with unusual hardening installed. Fixes bug 17404; bugfix
2849 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
2850 - Avoid a difficult-to-trigger heap corruption attack when extending
2851 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
2852 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
2853 Reported by Guido Vranken.
2855 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
2856 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
2857 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
2859 o Major bugfixes (guard selection, backport from 0.2.7.6):
2860 - Actually look at the Guard flag when selecting a new directory
2861 guard. When we implemented the directory guard design, we
2862 accidentally started treating all relays as if they have the Guard
2863 flag during guard selection, leading to weaker anonymity and worse
2864 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
2867 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
2868 - If OpenSSL fails to generate an RSA key, do not retain a dangling
2869 pointer to the previous (uninitialized) key value. The impact here
2870 should be limited to a difficult-to-trigger crash, if OpenSSL is
2871 running an engine that makes key generation failures possible, or
2872 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
2873 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
2876 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
2877 - Fix an integer underflow bug when comparing malformed Tor
2878 versions. This bug could crash Tor when built with
2879 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2880 0.2.9.8, which were built with -ftrapv by default. In other cases
2881 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2882 on 0.0.8pre1. Found by OSS-Fuzz.
2884 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
2885 - Make memwipe() do nothing when passed a NULL pointer or buffer of
2886 zero size. Check size argument to memwipe() for underflow. Fixes
2887 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
2890 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
2891 - Make Tor survive errors involving connections without a
2892 corresponding event object. Previously we'd fail with an
2893 assertion; now we produce a log message. Related to bug 16248.
2895 o Minor features (geoip):
2896 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2899 o Minor bugfixes (compilation, backport from 0.2.7.6):
2900 - Fix a compilation warning with Clang 3.6: Do not check the
2901 presence of an address which can never be NULL. Fixes bug 17781.
2904 Changes in version 0.2.5.13 - 2017-03-03
2905 Tor 0.2.5.13 backports a number of security fixes from later Tor
2906 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
2907 this release, if for some reason they cannot upgrade to a later
2910 Note that support for Tor 0.2.5.x is ending next year: we will not issue
2911 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
2912 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
2914 o Directory authority changes (backport from 0.2.8.5-rc):
2915 - Urras is no longer a directory authority. Closes ticket 19271.
2917 o Directory authority changes (backport from 0.2.9.2-alpha):
2918 - The "Tonga" bridge authority has been retired; the new bridge
2919 authority is "Bifroest". Closes tickets 19728 and 19690.
2921 o Directory authority key updates (backport from 0.2.8.1-alpha):
2922 - Update the V3 identity key for the dannenberg directory authority:
2923 it was changed on 18 November 2015. Closes task 17906. Patch
2926 o Major features (security fixes, backport from 0.2.9.4-alpha):
2927 - Prevent a class of security bugs caused by treating the contents
2928 of a buffer chunk as if they were a NUL-terminated string. At
2929 least one such bug seems to be present in all currently used
2930 versions of Tor, and would allow an attacker to remotely crash
2931 most Tor instances, especially those compiled with extra compiler
2932 hardening. With this defense in place, such bugs can't crash Tor,
2933 though we should still fix them as they occur. Closes ticket
2934 20384 (TROVE-2016-10-001).
2936 o Major bugfixes (parsing, security, backport from 0.2.9.8):
2937 - Fix a bug in parsing that could cause clients to read a single
2938 byte past the end of an allocated region. This bug could be used
2939 to cause hardened clients (built with --enable-expensive-hardening)
2940 to crash if they tried to visit a hostile hidden service. Non-
2941 hardened clients are only affected depending on the details of
2942 their platform's memory allocator. Fixes bug 21018; bugfix on
2943 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2944 2016-12-002 and as CVE-2016-1254.
2946 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
2947 - Stop a crash that could occur when a client running with DNSPort
2948 received a query with multiple address types, and the first
2949 address type was not supported. Found and fixed by Scott Dial.
2950 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
2952 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
2953 - Fix an error that could cause us to read 4 bytes before the
2954 beginning of an openssl string. This bug could be used to cause
2955 Tor to crash on systems with unusual malloc implementations, or
2956 systems with unusual hardening installed. Fixes bug 17404; bugfix
2959 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
2960 - Avoid a difficult-to-trigger heap corruption attack when extending
2961 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
2962 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
2963 Reported by Guido Vranken.
2965 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
2966 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
2967 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
2969 o Major bugfixes (guard selection, backport from 0.2.7.6):
2970 - Actually look at the Guard flag when selecting a new directory
2971 guard. When we implemented the directory guard design, we
2972 accidentally started treating all relays as if they have the Guard
2973 flag during guard selection, leading to weaker anonymity and worse
2974 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
2977 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
2978 - If OpenSSL fails to generate an RSA key, do not retain a dangling
2979 pointer to the previous (uninitialized) key value. The impact here
2980 should be limited to a difficult-to-trigger crash, if OpenSSL is
2981 running an engine that makes key generation failures possible, or
2982 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
2983 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
2986 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
2987 - Fix an integer underflow bug when comparing malformed Tor
2988 versions. This bug could crash Tor when built with
2989 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2990 0.2.9.8, which were built with -ftrapv by default. In other cases
2991 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2992 on 0.0.8pre1. Found by OSS-Fuzz.
2994 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
2995 - Make memwipe() do nothing when passed a NULL pointer or buffer of
2996 zero size. Check size argument to memwipe() for underflow. Fixes
2997 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3000 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3001 - Make Tor survive errors involving connections without a
3002 corresponding event object. Previously we'd fail with an
3003 assertion; now we produce a log message. Related to bug 16248.
3005 o Minor features (geoip):
3006 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3009 o Minor bugfixes (compilation, backport from 0.2.7.6):
3010 - Fix a compilation warning with Clang 3.6: Do not check the
3011 presence of an address which can never be NULL. Fixes bug 17781.
3013 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
3014 - Check for failures from crypto_early_init, and refuse to continue.
3015 A previous typo meant that we could keep going with an
3016 uninitialized crypto library, and would have OpenSSL initialize
3017 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
3018 when implementing ticket 4900. Patch by "teor".
3020 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3021 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3022 a client authorized hidden service. Fixes bug 15823; bugfix
3026 Changes in version 0.2.4.28 - 2017-03-03
3027 Tor 0.2.4.28 backports a number of security fixes from later Tor
3028 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
3029 this release, if for some reason they cannot upgrade to a later
3032 Note that support for Tor 0.2.4.x is ending soon: we will not issue
3033 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
3034 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
3036 o Directory authority changes (backport from 0.2.8.5-rc):
3037 - Urras is no longer a directory authority. Closes ticket 19271.
3039 o Directory authority changes (backport from 0.2.9.2-alpha):
3040 - The "Tonga" bridge authority has been retired; the new bridge
3041 authority is "Bifroest". Closes tickets 19728 and 19690.
3043 o Directory authority key updates (backport from 0.2.8.1-alpha):
3044 - Update the V3 identity key for the dannenberg directory authority:
3045 it was changed on 18 November 2015. Closes task 17906. Patch
3048 o Major features (security fixes, backport from 0.2.9.4-alpha):
3049 - Prevent a class of security bugs caused by treating the contents
3050 of a buffer chunk as if they were a NUL-terminated string. At
3051 least one such bug seems to be present in all currently used
3052 versions of Tor, and would allow an attacker to remotely crash
3053 most Tor instances, especially those compiled with extra compiler
3054 hardening. With this defense in place, such bugs can't crash Tor,
3055 though we should still fix them as they occur. Closes ticket
3056 20384 (TROVE-2016-10-001).
3058 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3059 - Fix a bug in parsing that could cause clients to read a single
3060 byte past the end of an allocated region. This bug could be used
3061 to cause hardened clients (built with --enable-expensive-hardening)
3062 to crash if they tried to visit a hostile hidden service. Non-
3063 hardened clients are only affected depending on the details of
3064 their platform's memory allocator. Fixes bug 21018; bugfix on
3065 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3066 2016-12-002 and as CVE-2016-1254.
3068 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3069 - Fix an error that could cause us to read 4 bytes before the
3070 beginning of an openssl string. This bug could be used to cause
3071 Tor to crash on systems with unusual malloc implementations, or
3072 systems with unusual hardening installed. Fixes bug 17404; bugfix
3075 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3076 - Avoid a difficult-to-trigger heap corruption attack when extending
3077 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3078 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3079 Reported by Guido Vranken.
3081 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3082 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3083 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3085 o Major bugfixes (guard selection, backport from 0.2.7.6):
3086 - Actually look at the Guard flag when selecting a new directory
3087 guard. When we implemented the directory guard design, we
3088 accidentally started treating all relays as if they have the Guard
3089 flag during guard selection, leading to weaker anonymity and worse
3090 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3093 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3094 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3095 pointer to the previous (uninitialized) key value. The impact here
3096 should be limited to a difficult-to-trigger crash, if OpenSSL is
3097 running an engine that makes key generation failures possible, or
3098 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3099 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3102 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3103 - Fix an integer underflow bug when comparing malformed Tor
3104 versions. This bug could crash Tor when built with
3105 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3106 0.2.9.8, which were built with -ftrapv by default. In other cases
3107 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3108 on 0.0.8pre1. Found by OSS-Fuzz.
3110 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3111 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3112 zero size. Check size argument to memwipe() for underflow. Fixes
3113 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3116 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3117 - Make Tor survive errors involving connections without a
3118 corresponding event object. Previously we'd fail with an
3119 assertion; now we produce a log message. Related to bug 16248.
3121 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
3122 - Make it harder for attackers to overload hidden services with
3123 introductions, by blocking multiple introduction requests on the
3124 same circuit. Resolves ticket 15515.
3126 o Minor features (geoip):
3127 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3130 o Minor bugfixes (compilation, backport from 0.2.7.6):
3131 - Fix a compilation warning with Clang 3.6: Do not check the
3132 presence of an address which can never be NULL. Fixes bug 17781.
3134 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3135 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3136 a client authorized hidden service. Fixes bug 15823; bugfix
3140 Changes in version 0.3.0.4-rc - 2017-03-01
3141 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
3142 0.3.0 release series, and introduces a few reliability features to
3143 keep them from coming back.
3145 This is the first release candidate in the Tor 0.3.0 series. If we
3146 find no new bugs or regressions here, the first stable 0.3.0 release
3147 will be nearly identical to it.
3149 o Major bugfixes (bridges):
3150 - When the same bridge is configured multiple times with the same
3151 identity, but at different address:port combinations, treat those
3152 bridge instances as separate guards. This fix restores the ability
3153 of clients to configure the same bridge with multiple pluggable
3154 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
3156 o Major bugfixes (hidden service directory v3):
3157 - Stop crashing on a failed v3 hidden service descriptor lookup
3158 failure. Fixes bug 21471; bugfixes on tor-0.3.0.1-alpha.
3160 o Major bugfixes (parsing):
3161 - When parsing a malformed content-length field from an HTTP
3162 message, do not read off the end of the buffer. This bug was a
3163 potential remote denial-of-service attack against Tor clients and
3164 relays. A workaround was released in October 2016, to prevent this
3165 bug from crashing Tor. This is a fix for the underlying issue,
3166 which should no longer matter (if you applied the earlier patch).
3167 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
3168 using AFL (http://lcamtuf.coredump.cx/afl/).
3169 - Fix an integer underflow bug when comparing malformed Tor
3170 versions. This bug could crash Tor when built with
3171 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3172 0.2.9.8, which were built with -ftrapv by default. In other cases
3173 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3174 on 0.0.8pre1. Found by OSS-Fuzz.
3176 o Minor feature (protocol versioning):
3177 - Add new protocol version for proposal 224. HSIntro now advertises
3178 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
3180 o Minor features (directory authorities):
3181 - Directory authorities now reject descriptors that claim to be
3182 malformed versions of Tor. Helps prevent exploitation of
3184 - Reject version numbers with components that exceed INT32_MAX.
3185 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3186 Fixes bug 21450; bugfix on 0.0.8pre1.
3187 - Directory authorities now reject relays running versions
3188 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
3189 suffer from bug 20499 and don't keep their consensus cache
3190 up-to-date. Resolves ticket 20509.
3192 o Minor features (geoip):
3193 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3196 o Minor features (reliability, crash):
3197 - Try better to detect problems in buffers where they might grow (or
3198 think they have grown) over 2 GB in size. Diagnostic for
3201 o Minor features (testing):
3202 - During 'make test-network-all', if tor logs any warnings, ask
3203 chutney to output them. Requires a recent version of chutney with
3204 the 21572 patch. Implements 21570.
3206 o Minor bugfixes (certificate expiration time):
3207 - Avoid using link certificates that don't become valid till some
3208 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
3210 o Minor bugfixes (code correctness):
3211 - Repair a couple of (unreachable or harmless) cases of the risky
3212 comparison-by-subtraction pattern that caused bug 21278.
3213 - Remove a redundant check for the UseEntryGuards option from the
3214 options_transition_affects_guards() function. Fixes bug 21492;
3215 bugfix on 0.3.0.1-alpha.
3217 o Minor bugfixes (directory mirrors):
3218 - Allow relays to use directory mirrors without a DirPort: these
3219 relays need to be contacted over their ORPorts using a begindir
3220 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
3221 - Clarify the message logged when a remote relay is unexpectedly
3222 missing an ORPort or DirPort: users were confusing this with a
3223 local port. Fixes another case of bug 20711; bugfix
3226 o Minor bugfixes (guards):
3227 - Don't warn about a missing guard state on timeout-measurement
3228 circuits: they aren't supposed to be using guards. Fixes an
3229 instance of bug 21007; bugfix on 0.3.0.1-alpha.
3230 - Silence a BUG() warning when attempting to use a guard whose
3231 descriptor we don't know, and make this scenario less likely to
3232 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
3234 o Minor bugfixes (hidden service):
3235 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
3236 cells. Previously, we were using sizeof() on a pointer, instead of
3237 the real destination buffer. Fortunately, that value was only used
3238 to double-check that there was enough room--which was already
3239 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
3241 o Minor bugfixes (testing):
3242 - Fix Raspbian build issues related to missing socket errno in
3243 test_util.c. Fixes bug 21116; bugfix on tor-0.2.8.2. Patch
3245 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
3246 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
3247 - Use bash in src/test/test-network.sh. This ensures we reliably
3248 call chutney's newer tools/test-network.sh when available. Fixes
3249 bug 21562; bugfix on 0.2.9.1-alpha.
3252 - Small fixes to the fuzzing documentation. Closes ticket 21472.
3255 Changes in version 0.2.9.10 - 2017-03-01
3256 Tor 0.2.9.10 backports a security fix from later Tor release. It also
3257 includes fixes for some major issues affecting directory authorities,
3258 LibreSSL compatibility, and IPv6 correctness.
3260 The Tor 0.2.9.x release series is now marked as a long-term-support
3261 series. We intend to backport security fixes to 0.2.9.x until at
3262 least January of 2020.
3264 o Major bugfixes (directory authority, 0.3.0.3-alpha):
3265 - During voting, when marking a relay as a probable sybil, do not
3266 clear its BadExit flag: sybils can still be bad in other ways
3267 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3270 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
3271 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3272 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3273 exit policy rejects that port on more than an IPv6 /16 of
3274 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3275 which rejected a relay's own IPv6 address by default. Fixes bug
3276 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3278 o Major bugfixes (parsing, also in 0.3.0.4-rc):
3279 - Fix an integer underflow bug when comparing malformed Tor
3280 versions. This bug could crash Tor when built with
3281 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3282 0.2.9.8, which were built with -ftrapv by default. In other cases
3283 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3284 on 0.0.8pre1. Found by OSS-Fuzz.
3286 o Minor features (directory authorities, also in 0.3.0.4-rc):
3287 - Directory authorities now reject descriptors that claim to be
3288 malformed versions of Tor. Helps prevent exploitation of
3290 - Reject version numbers with components that exceed INT32_MAX.
3291 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3292 Fixes bug 21450; bugfix on 0.0.8pre1.
3294 o Minor features (geoip):
3295 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3298 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
3299 - Autoconf now checks to determine if OpenSSL structures are opaque,
3300 instead of explicitly checking for OpenSSL version numbers. Part
3302 - Support building with recent LibreSSL code that uses opaque
3303 structures. Closes ticket 21359.
3305 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
3306 - Repair a couple of (unreachable or harmless) cases of the risky
3307 comparison-by-subtraction pattern that caused bug 21278.
3309 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
3310 - The tor-resolve command line tool now rejects hostnames over 255
3311 characters in length. Previously, it would silently truncate them,
3312 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
3313 Patch by "junglefowl".
3316 Changes in version 0.3.0.3-alpha - 2017-02-03
3317 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
3318 0.3.0.x development series, including some that could cause
3319 authorities to behave badly. There is also a fix for a longstanding
3320 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
3321 includes some smaller features and bugfixes.
3323 The Tor 0.3.0.x release series is now in patch-freeze: no additional
3324 features will be considered for inclusion in 0.3.0.x. We suspect that
3325 some bugs will probably remain, however, and we encourage people to
3328 o Major bugfixes (directory authority):
3329 - During voting, when marking a relay as a probable sybil, do not
3330 clear its BadExit flag: sybils can still be bad in other ways
3331 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3333 - When deciding whether we have just found a router to be reachable,
3334 do not penalize it for not having performed an Ed25519 link
3335 handshake if it does not claim to support an Ed25519 handshake.
3336 Previously, we would treat such relays as non-running. Fixes bug
3337 21107; bugfix on 0.3.0.1-alpha.
3339 o Major bugfixes (entry guards):
3340 - Stop trying to build circuits through entry guards for which we
3341 have no descriptor. Also, stop crashing in the case that we *do*
3342 accidentally try to build a circuit in such a state. Fixes bug
3343 21242; bugfix on 0.3.0.1-alpha.
3345 o Major bugfixes (IPv6 Exits):
3346 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3347 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3348 exit policy rejects that port on more than an IPv6 /16 of
3349 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3350 which rejected a relay's own IPv6 address by default. Fixes bug
3351 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3353 o Minor feature (client):
3354 - Enable IPv6 traffic on the SocksPort by default. To disable this,
3355 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
3357 o Minor feature (fallback scripts):
3358 - Add a check_existing mode to updateFallbackDirs.py, which checks
3359 if fallbacks in the hard-coded list are working. Closes ticket
3360 20174. Patch by haxxpop.
3362 o Minor features (ciphersuite selection):
3363 - Clients now advertise a list of ciphersuites closer to the ones
3364 preferred by Firefox. Closes part of ticket 15426.
3365 - Allow relays to accept a wider range of ciphersuites, including
3366 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
3368 o Minor features (controller, configuration):
3369 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
3370 and so on, now comes with a __*Port variant that will not be saved
3371 to the torrc file by the controller's SAVECONF command. This
3372 change allows TorBrowser to set up a single-use domain socket for
3373 each time it launches Tor. Closes ticket 20956.
3374 - The GETCONF command can now query options that may only be
3375 meaningful in context-sensitive lists. This allows the controller
3376 to query the mixed SocksPort/__SocksPort style options introduced
3377 in feature 20956. Implements ticket 21300.
3379 o Minor features (portability, compilation):
3380 - Autoconf now checks to determine if OpenSSL structures are opaque,
3381 instead of explicitly checking for OpenSSL version numbers. Part
3383 - Support building with recent LibreSSL code that uses opaque
3384 structures. Closes ticket 21359.
3386 o Minor features (relay):
3387 - We now allow separation of exit and relay traffic to different
3388 source IP addresses, using the OutboundBindAddressExit and
3389 OutboundBindAddressOR options respectively. Closes ticket 17975.
3390 Written by Michael Sonntag.
3392 o Minor bugfix (logging):
3393 - Don't recommend the use of Tor2web in non-anonymous mode.
3394 Recommending Tor2web is a bad idea because the client loses all
3395 anonymity. Tor2web should only be used in specific cases by users
3396 who *know* and understand the issues. Fixes bug 21294; bugfix
3399 o Minor bugfixes (client):
3400 - Always recover from failures in extend_info_from_node(), in an
3401 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
3402 bugfix on 0.2.3.1-alpha.
3404 o Minor bugfixes (client, entry guards):
3405 - Fix a bug warning (with backtrace) when we fail a channel that
3406 circuits to fallback directories on it. Fixes bug 21128; bugfix
3408 - Fix a spurious bug warning (with backtrace) when removing an
3409 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
3410 - Fix a bug of the new guard algorithm where tor could stall for up
3411 to 10 minutes before retrying a guard after a long period of no
3412 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
3413 - Do not try to build circuits until we have descriptors for our
3414 primary entry guards. Related to fix for bug 21242.
3416 o Minor bugfixes (configure, autoconf):
3417 - Rename the configure option --enable-expensive-hardening to
3418 --enable-fragile-hardening. Expensive hardening makes the tor
3419 daemon abort when some kinds of issues are detected. Thus, it
3420 makes tor more at risk of remote crashes but safer against RCE or
3421 heartbleed bug category. We now try to explain this issue in a
3422 message from the configure script. Fixes bug 21290; bugfix
3425 o Minor bugfixes (controller):
3426 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
3427 20824; bugfix on 0.3.0.1-alpha.
3429 o Minor bugfixes (hidden service):
3430 - Clean up the code for expiring intro points with no associated
3431 circuits. It was causing, rarely, a service with some expiring
3432 introduction points to not open enough additional introduction
3433 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
3434 - Stop setting the torrc option HiddenServiceStatistics to "0" just
3435 because we're not a bridge or relay. Instead, we preserve whatever
3436 value the user set (or didn't set). Fixes bug 21150; bugfix
3438 - Resolve two possible underflows which could lead to creating and
3439 closing a lot of introduction point circuits in a non-stop loop.
3440 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
3442 o Minor bugfixes (portability):
3443 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
3444 It is supported by OpenBSD itself, and also by most OpenBSD
3445 variants (such as Bitrig). Fixes bug 20980; bugfix
3447 - When mapping a file of length greater than SIZE_MAX, do not
3448 silently truncate its contents. This issue could occur on 32 bit
3449 systems with large file support and files which are larger than 4
3450 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
3452 o Minor bugfixes (tor-resolve):
3453 - The tor-resolve command line tool now rejects hostnames over 255
3454 characters in length. Previously, it would silently truncate them,
3455 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
3456 Patch by "junglefowl".
3458 o Minor bugfixes (Windows services):
3459 - Be sure to initialize the monotonic time subsystem before using
3460 it, even when running as an NT service. Fixes bug 21356; bugfix
3464 Changes in version 0.3.0.2-alpha - 2017-01-23
3465 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
3466 cause relays and clients to crash, even if they were not built with
3467 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
3468 versions, and also affects 0.3.0.1-alpha: all relays running an affected
3469 version should upgrade.
3471 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
3472 time-to-live values, makes directory authorities enforce the 1-to-1
3473 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
3474 client-side onion service reachability bug, does better at selecting
3475 the set of fallback directories, and more.
3477 o Major bugfixes (security, also in 0.2.9.9):
3478 - Downgrade the "-ftrapv" option from "always on" to "only on when
3479 --enable-expensive-hardening is provided." This hardening option, like
3480 others, can turn survivable bugs into crashes--and having it on by
3481 default made a (relatively harmless) integer overflow bug into a
3482 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
3485 o Major features (security):
3486 - Change the algorithm used to decide DNS TTLs on client and server
3487 side, to better resist DNS-based correlation attacks like the
3488 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
3489 Feamster. Now relays only return one of two possible DNS TTL
3490 values, and clients are willing to believe DNS TTL values up to 3
3491 hours long. Closes ticket 19769.
3493 o Major features (directory authority, security):
3494 - The default for AuthDirPinKeys is now 1: directory authorities
3495 will reject relays where the RSA identity key matches a previously
3496 seen value, but the Ed25519 key has changed. Closes ticket 18319.
3498 o Major bugfixes (client, guard, crash):
3499 - In circuit_get_global_origin_list(), return the actual list of
3500 origin circuits. The previous version of this code returned the
3501 list of all the circuits, and could have caused strange bugs,
3502 including possible crashes. Fixes bug 21118; bugfix
3505 o Major bugfixes (client, onion service, also in 0.2.9.9):
3506 - Fix a client-side onion service reachability bug, where multiple
3507 socks requests to an onion service (or a single slow request)
3508 could cause us to mistakenly mark some of the service's
3509 introduction points as failed, and we cache that failure so
3510 eventually we run out and can't reach the service. Also resolves a
3511 mysterious "Remote server sent bogus reason code 65021" log
3512 warning. The bug was introduced in ticket 17218, where we tried to
3513 remember the circuit end reason as a uint16_t, which mangled
3514 negative values. Partially fixes bug 21056 and fixes bug 20307;
3515 bugfix on 0.2.8.1-alpha.
3517 o Major bugfixes (DNS):
3518 - Fix a bug that prevented exit nodes from caching DNS records for
3519 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
3521 o Minor features (controller):
3522 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
3523 shared-random values to the controller. Closes ticket 19925.
3525 o Minor features (entry guards):
3526 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
3527 break regression tests.
3528 - Require UseEntryGuards when UseBridges is set, in order to make
3529 sure bridges aren't bypassed. Resolves ticket 20502.
3531 o Minor features (fallback directories):
3532 - Select 200 fallback directories for each release. Closes
3534 - Allow 3 fallback relays per operator, which is safe now that we
3535 are choosing 200 fallback relays. Closes ticket 20912.
3536 - Exclude relays affected by bug 20499 from the fallback list.
3537 Exclude relays from the fallback list if they are running versions
3538 known to be affected by bug 20499, or if in our tests they deliver
3539 a stale consensus (i.e. one that expired more than 24 hours ago).
3540 Closes ticket 20539.
3541 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
3543 - Require fallback directories to have the same address and port for
3544 7 days (now that we have enough relays with this stability).
3545 Relays whose OnionOO stability timer is reset on restart by bug
3546 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
3547 this issue. Closes ticket 20880; maintains short-term fix
3549 - Require fallbacks to have flags for 90% of the time (weighted
3550 decaying average), rather than 95%. This allows at least 73% of
3551 clients to bootstrap in the first 5 seconds without contacting an
3552 authority. Part of ticket 18828.
3553 - Annotate updateFallbackDirs.py with the bandwidth and consensus
3554 weight for each candidate fallback. Closes ticket 20878.
3555 - Make it easier to change the output sort order of fallbacks.
3556 Closes ticket 20822.
3557 - Display the relay fingerprint when downloading consensuses from
3558 fallbacks. Closes ticket 20908.
3560 o Minor features (geoip, also in 0.2.9.9):
3561 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
3564 o Minor features (next-gen onion service directories):
3565 - Remove the "EnableOnionServicesV3" consensus parameter that we
3566 introduced in 0.3.0.1-alpha: relays are now always willing to act
3567 as v3 onion service directories. Resolves ticket 19899.
3569 o Minor features (linting):
3570 - Enhance the changes file linter to warn on Tor versions that are
3571 prefixed with "tor-". Closes ticket 21096.
3573 o Minor features (logging):
3574 - In several places, describe unset ed25519 keys as "<unset>",
3575 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
3577 o Minor bugfix (control protocol):
3578 - The reply to a "GETINFO config/names" request via the control
3579 protocol now spells the type "Dependent" correctly. This is a
3580 breaking change in the control protocol. (The field seems to be
3581 ignored by the most common known controllers.) Fixes bug 18146;
3582 bugfix on 0.1.1.4-alpha.
3584 o Minor bugfixes (bug resilience):
3585 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
3586 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
3587 Hans Jerry Illikainen.
3589 o Minor bugfixes (build):
3590 - Replace obsolete Autoconf macros with their modern equivalent and
3591 prevent similar issues in the future. Fixes bug 20990; bugfix
3594 o Minor bugfixes (client, guards):
3595 - Fix bug where Tor would think that there are circuits waiting for
3596 better guards even though those circuits have been freed. Fixes
3597 bug 21142; bugfix on 0.3.0.1-alpha.
3599 o Minor bugfixes (config):
3600 - Don't assert on startup when trying to get the options list and
3601 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
3602 options so of course they aren't ready yet. Fixes bug 21062;
3603 bugfix on 0.2.9.3-alpha.
3605 o Minor bugfixes (controller):
3606 - Make the GETINFO interface for inquiring about entry guards
3607 support the new guards backend. Fixes bug 20823; bugfix
3610 o Minor bugfixes (dead code):
3611 - Remove a redundant check for PidFile changes at runtime in
3612 options_transition_allowed(): this check is already performed
3613 regardless of whether the sandbox is active. Fixes bug 21123;
3614 bugfix on 0.2.5.4-alpha.
3616 o Minor bugfixes (documentation):
3617 - Update the tor manual page to document every option that can not
3618 be changed while tor is running. Fixes bug 21122.
3620 o Minor bugfixes (fallback directories):
3621 - Stop failing when a relay has no uptime data in
3622 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
3623 - Avoid checking fallback candidates' DirPorts if they are down in
3624 OnionOO. When a relay operator has multiple relays, this
3625 prioritizes relays that are up over relays that are down. Fixes
3626 bug 20926; bugfix on 0.2.8.3-alpha.
3627 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
3628 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
3630 o Minor bugfixes (guards, bootstrapping):
3631 - When connecting to a directory guard during bootstrap, do not mark
3632 the guard as successful until we receive a good-looking directory
3633 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
3635 o Minor bugfixes (onion services):
3636 - Fix the config reload pruning of old vs new services so it
3637 actually works when both ephemeral and non-ephemeral services are
3638 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
3639 - Allow the number of introduction points to be as low as 0, rather
3640 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
3642 o Minor bugfixes (IPv6):
3643 - Make IPv6-using clients try harder to find an IPv6 directory
3644 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
3645 - When IPv6 addresses have not been downloaded yet (microdesc
3646 consensus documents don't list relay IPv6 addresses), use hard-
3647 coded addresses for authorities, fallbacks, and configured
3648 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
3649 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
3651 o Minor bugfixes (memory leaks):
3652 - Fix a memory leak when configuring hidden services. Fixes bug
3653 20987; bugfix on 0.3.0.1-alpha.
3655 o Minor bugfixes (portability, also in 0.2.9.9):
3656 - Avoid crashing when Tor is built using headers that contain
3657 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
3658 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
3660 - Fix Libevent detection on platforms without Libevent 1 headers
3661 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
3663 o Minor bugfixes (relay):
3664 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
3665 initializing the keys would reset the DataDirectory to 0700
3666 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
3667 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
3669 o Minor bugfixes (testing):
3670 - Remove undefined behavior from the backtrace generator by removing
3671 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
3673 o Minor bugfixes (unit tests):
3674 - Allow the unit tests to pass even when DNS lookups of bogus
3675 addresses do not fail as expected. Fixes bug 20862 and 20863;
3676 bugfix on unit tests introduced in 0.2.8.1-alpha
3677 through 0.2.9.4-alpha.
3679 o Code simplification and refactoring:
3680 - Refactor code to manipulate global_origin_circuit_list into
3681 separate functions. Closes ticket 20921.
3683 o Documentation (formatting):
3684 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
3685 blocks were incorrectly appearing. Closes ticket 20885.
3687 o Documentation (man page):
3688 - Clarify many options in tor.1 and add some min/max values for
3689 HiddenService options. Closes ticket 21058.
3692 Changes in version 0.2.9.9 - 2017-01-23
3693 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
3694 cause relays and clients to crash, even if they were not built with
3695 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
3696 versions, and also affects 0.3.0.1-alpha: all relays running an affected
3697 version should upgrade.
3699 This release also resolves a client-side onion service reachability
3700 bug, and resolves a pair of small portability issues.
3702 o Major bugfixes (security):
3703 - Downgrade the "-ftrapv" option from "always on" to "only on when
3704 --enable-expensive-hardening is provided." This hardening option,
3705 like others, can turn survivable bugs into crashes -- and having
3706 it on by default made a (relatively harmless) integer overflow bug
3707 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
3708 bugfix on 0.2.9.1-alpha.
3710 o Major bugfixes (client, onion service):
3711 - Fix a client-side onion service reachability bug, where multiple
3712 socks requests to an onion service (or a single slow request)
3713 could cause us to mistakenly mark some of the service's
3714 introduction points as failed, and we cache that failure so
3715 eventually we run out and can't reach the service. Also resolves a
3716 mysterious "Remote server sent bogus reason code 65021" log
3717 warning. The bug was introduced in ticket 17218, where we tried to
3718 remember the circuit end reason as a uint16_t, which mangled
3719 negative values. Partially fixes bug 21056 and fixes bug 20307;
3720 bugfix on 0.2.8.1-alpha.
3722 o Minor features (geoip):
3723 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
3726 o Minor bugfixes (portability):
3727 - Avoid crashing when Tor is built using headers that contain
3728 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
3729 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
3731 - Fix Libevent detection on platforms without Libevent 1 headers
3732 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
3735 Changes in version 0.3.0.1-alpha - 2016-12-19
3736 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
3737 series. It strengthens Tor's link and circuit handshakes by
3738 identifying relays by their Ed25519 keys, improves the algorithm that
3739 clients use to choose and maintain their list of guards, and includes
3740 additional backend support for the next-generation hidden service
3741 design. It also contains numerous other small features and
3742 improvements to security, correctness, and performance.
3744 Below are the changes since 0.2.9.8.
3746 o Major features (guard selection algorithm):
3747 - Tor's guard selection algorithm has been redesigned from the
3748 ground up, to better support unreliable networks and restrictive
3749 sets of entry nodes, and to better resist guard-capture attacks by
3750 hostile local networks. Implements proposal 271; closes
3753 o Major features (next-generation hidden services):
3754 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
3755 prop224 aka "Next Generation Hidden Services". Service and clients
3756 don't use this functionality yet. Closes ticket 19043. Based on
3757 initial code by Alec Heifetz.
3758 - Relays now support the HSDir version 3 protocol, so that they can
3759 can store and serve v3 descriptors. This is part of the next-
3760 generation onion service work detailled in proposal 224. Closes
3763 o Major features (protocol, ed25519 identity keys):
3764 - Relays now use Ed25519 to prove their Ed25519 identities and to
3765 one another, and to clients. This algorithm is faster and more
3766 secure than the RSA-based handshake we've been doing until now.
3767 Implements the second big part of proposal 220; Closes
3769 - Clients now support including Ed25519 identity keys in the EXTEND2
3770 cells they generate. By default, this is controlled by a consensus
3771 parameter, currently disabled. You can turn this feature on for
3772 testing by setting ExtendByEd25519ID in your configuration. This
3773 might make your traffic appear different than the traffic
3774 generated by other users, however. Implements part of ticket
3775 15056; part of proposal 220.
3776 - Relays now understand requests to extend to other relays by their
3777 Ed25519 identity keys. When an Ed25519 identity key is included in
3778 an EXTEND2 cell, the relay will only extend the circuit if the
3779 other relay can prove ownership of that identity. Implements part
3780 of ticket 15056; part of proposal 220.
3782 o Major bugfixes (scheduler):
3783 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
3784 caused the channel scheduler to behave more or less randomly,
3785 rather than preferring channels with higher-priority circuits.
3786 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
3788 o Minor features (controller):
3789 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
3790 rather than "unrecognized." Closes ticket 20389; patch from
3793 o Minor features (diagnostic, directory client):
3794 - Warn when we find an unexpected inconsistency in directory
3795 download status objects. Prevents some negative consequences of
3798 o Minor features (directory authority):
3799 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
3800 default) to control whether authorities should try to probe relays
3801 by their Ed25519 link keys. This option will go away in a few
3802 releases--unless we encounter major trouble in our ed25519 link
3803 protocol rollout, in which case it will serve as a safety option.
3805 o Minor features (directory cache):
3806 - Relays and bridges will now refuse to serve the consensus they
3807 have if they know it is too old for a client to use. Closes
3810 o Minor features (ed25519 link handshake):
3811 - Advertise support for the ed25519 link handshake using the
3812 subprotocol-versions mechanism, so that clients can tell which
3813 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
3815 o Minor features (fingerprinting resistance, authentication):
3816 - Extend the length of RSA keys used for TLS link authentication to
3817 2048 bits. (These weren't used for forward secrecy; for forward
3818 secrecy, we used P256.) Closes ticket 13752.
3820 o Minor features (infrastructure):
3821 - Implement smartlist_add_strdup() function. Replaces the use of
3822 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
3824 o Minor bugfixes (client):
3825 - When clients that use bridges start up with a cached consensus on
3826 disk, they were ignoring it and downloading a new one. Now they
3827 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
3829 o Minor bugfixes (configuration):
3830 - Accept non-space whitespace characters after the severity level in
3831 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
3832 - Support "TByte" and "TBytes" units in options given in bytes.
3833 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
3834 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
3836 o Minor bugfixes (consensus weight):
3837 - Add new consensus method that initializes bw weights to 1 instead
3838 of 0. This prevents a zero weight from making it all the way to
3839 the end (happens in small testing networks) and causing an error.
3840 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
3842 o Minor bugfixes (descriptors):
3843 - Correctly recognise downloaded full descriptors as valid, even
3844 when using microdescriptors as circuits. This affects clients with
3845 FetchUselessDescriptors set, and may affect directory authorities.
3846 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
3848 o Minor bugfixes (directory system):
3849 - Download all consensus flavors, descriptors, and authority
3850 certificates when FetchUselessDescriptors is set, regardless of
3851 whether tor is a directory cache or not. Fixes bug 20667; bugfix
3852 on all recent tor versions.
3853 - Bridges and relays now use microdescriptors (like clients do)
3854 rather than old-style router descriptors. Now bridges will blend
3855 in with clients in terms of the circuits they build. Fixes bug
3856 6769; bugfix on 0.2.3.2-alpha.
3858 o Minor bugfixes (ed25519 certificates):
3859 - Correctly interpret ed25519 certificates that would expire some
3860 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
3862 o Minor bugfixes (hidden services):
3863 - Stop ignoring misconfigured hidden services. Instead, refuse to
3864 start tor until the misconfigurations have been corrected. Fixes
3865 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
3868 o Minor bugfixes (memory leak at exit):
3869 - Fix a small harmless memory leak at exit of the previously unused
3870 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
3873 o Minor bugfixes (util):
3874 - When finishing writing a file to disk, if we were about to replace
3875 the file with the temporary file created before and we fail to
3876 replace it, remove the temporary file so it doesn't stay on disk.
3877 Fixes bug 20646; bugfix on tor-0.2.0.7-alpha. Patch by fk.
3879 o Minor bugfixes (Windows):
3880 - Check for getpagesize before using it to mmap files. This fixes
3881 compilation in some MinGW environments. Fixes bug 20530; bugfix on
3882 0.1.2.1-alpha. Reported by "ice".
3884 o Code simplification and refactoring:
3885 - Abolish all global guard context in entrynodes.c; replace with new
3886 guard_selection_t structure as preparation for proposal 271.
3887 Closes ticket 19858.
3888 - Introduce rend_service_is_ephemeral() that tells if given onion
3889 service is ephemeral. Replace unclear NULL-checkings for service
3890 directory with this function. Closes ticket 20526.
3891 - Extract magic numbers in circuituse.c into defined variables.
3892 - Refactor circuit_is_available_for_use to remove unnecessary check.
3893 - Refactor circuit_predict_and_launch_new for readability and
3894 testability. Closes ticket 18873.
3895 - Refactor large if statement in purpose_needs_anonymity to use
3896 switch statement instead. Closes part of ticket 20077.
3897 - Refactor the hashing API to return negative values for errors, as
3898 is done as throughout the codebase. Closes ticket 20717.
3899 - Remove data structures that were used to index or_connection
3900 objects by their RSA identity digests. These structures are fully
3901 redundant with the similar structures used in the
3902 channel abstraction.
3903 - Remove duplicate code in the channel_write_*cell() functions.
3904 Closes ticket 13827; patch from Pingl.
3905 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
3906 use only purpose_needs_anonymity. Closes part of ticket 20077.
3907 - The code to generate and parse EXTEND and EXTEND2 cells has been
3908 replaced with code automatically generated by the
3912 - Include the "TBits" unit in Tor's man page. Fixes part of bug
3913 20622; bugfix on tor-0.2.5.1-alpha.
3914 - Change '1' to 'weight_scale' in consensus bw weights calculation
3915 comments, as that is reality. Closes ticket 20273. Patch
3917 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
3918 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
3919 on tor-0.2.5.6-alpha.
3920 - Stop the man page from incorrectly stating that HiddenServiceDir
3921 must already exist. Fixes 20486.
3922 - Clarify that when ClientRejectInternalAddresses is enabled (which
3923 is the default), multicast DNS hostnames for machines on the local
3924 network (of the form *.local) are also rejected. Closes
3928 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
3929 limit for relays running on a single IP applies to authority IP
3930 addresses as well as to non-authority IP addresses. Closes
3932 - The UseDirectoryGuards torrc option no longer exists: all users
3933 that use entry guards will also use directory guards. Related to
3934 proposal 271; implements part of ticket 20831.
3937 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
3938 from "overcaffeinated".
3939 - Perform the coding style checks when running the tests and fail
3940 when coding style violations are found. Closes ticket 5500.
3941 - Add tests for networkstatus_compute_bw_weights_v10.
3942 - Add unit tests circuit_predict_and_launch_new.
3943 - Extract dummy_origin_circuit_new so it can be used by other
3947 Changes in version 0.2.8.12 - 2016-12-19
3948 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
3949 below) where Tor clients could crash when attempting to visit a
3950 hostile hidden service. Clients are recommended to upgrade as packages
3951 become available for their systems.
3953 It also includes an updated list of fallback directories, backported
3956 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
3957 backported to 0.2.8 in the future.
3959 o Major bugfixes (parsing, security, backported from 0.2.9.8):
3960 - Fix a bug in parsing that could cause clients to read a single
3961 byte past the end of an allocated region. This bug could be used
3962 to cause hardened clients (built with --enable-expensive-hardening)
3963 to crash if they tried to visit a hostile hidden service. Non-
3964 hardened clients are only affected depending on the details of
3965 their platform's memory allocator. Fixes bug 21018; bugfix on
3966 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3967 2016-12-002 and as CVE-2016-1254.
3969 o Minor features (fallback directory list, backported from 0.2.9.8):
3970 - Replace the 81 remaining fallbacks of the 100 originally
3971 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
3972 fallbacks (123 new, 54 existing, 27 removed) generated in December
3973 2016. Resolves ticket 20170.
3975 o Minor features (geoip, backported from 0.2.9.7-rc):
3976 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
3980 Changes in version 0.2.9.8 - 2016-12-19
3981 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
3983 The Tor 0.2.9 series makes mandatory a number of security features
3984 that were formerly optional. It includes support for a new shared-
3985 randomness protocol that will form the basis for next generation
3986 hidden services, includes a single-hop hidden service mode for
3987 optimizing .onion services that don't actually want to be hidden,
3988 tries harder not to overload the directory authorities with excessive
3989 downloads, and supports a better protocol versioning scheme for
3990 improved compatibility with other implementations of the Tor protocol.
3992 And of course, there are numerous other bugfixes and improvements.
3994 This release also includes a fix for a medium-severity issue (bug
3995 21018 below) where Tor clients could crash when attempting to visit a
3996 hostile hidden service. Clients are recommended to upgrade as packages
3997 become available for their systems.
3999 Below are the changes since 0.2.9.7-rc. For a list of all changes
4000 since 0.2.8, see the ReleaseNotes file.
4002 o Major bugfixes (parsing, security):
4003 - Fix a bug in parsing that could cause clients to read a single
4004 byte past the end of an allocated region. This bug could be used
4005 to cause hardened clients (built with --enable-expensive-hardening)
4006 to crash if they tried to visit a hostile hidden service. Non-
4007 hardened clients are only affected depending on the details of
4008 their platform's memory allocator. Fixes bug 21018; bugfix on
4009 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4010 2016-12-002 and as CVE-2016-1254.
4012 o Minor features (fallback directory list):
4013 - Replace the 81 remaining fallbacks of the 100 originally
4014 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4015 fallbacks (123 new, 54 existing, 27 removed) generated in December
4016 2016. Resolves ticket 20170.
4019 Changes in version 0.2.9.7-rc - 2016-12-12
4020 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
4021 including a few that had prevented tests from passing on
4024 o Minor features (geoip):
4025 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
4028 o Minor bugfix (build):
4029 - The current Git revision when building from a local repository is
4030 now detected correctly when using git worktrees. Fixes bug 20492;
4031 bugfix on 0.2.3.9-alpha.
4033 o Minor bugfixes (directory authority):
4034 - When computing old Tor protocol line version in protover, we were
4035 looking at 0.2.7.5 twice instead of a specific case for
4036 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
4038 o Minor bugfixes (download scheduling):
4039 - Resolve a "bug" warning when considering a download schedule whose
4040 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
4042 o Minor bugfixes (logging):
4043 - Downgrade a harmless log message about the
4044 pending_entry_connections list from "warn" to "info". Mitigates
4047 o Minor bugfixes (memory leak):
4048 - Fix a small memory leak when receiving AF_UNIX connections on a
4049 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
4050 - When moving a signed descriptor object from a source to an
4051 existing destination, free the allocated memory inside that
4052 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
4054 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
4055 - Fix a memory leak and use-after-free error when removing entries
4056 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
4057 0.2.5.5-alpha. Patch from "cypherpunks".
4059 o Minor bugfixes (portability):
4060 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
4061 Fixes bug 20935; bugfix on 0.2.9.6-rc.
4063 o Minor bugfixes (unit tests):
4064 - Stop expecting NetBSD unit tests to report success for ipfw. Part
4065 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
4066 - Fix tolerances in unit tests for monotonic time comparisons
4067 between nanoseconds and microseconds. Previously, we accepted a 10
4068 us difference only, which is not realistic on every platform's
4069 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
4070 - Remove a double-free in the single onion service unit test. Stop
4071 ignoring a return value. Make future changes less error-prone.
4072 Fixes bug 20864; bugfix on 0.2.9.6-rc.
4075 Changes in version 0.2.8.11 - 2016-12-08
4076 Tor 0.2.8.11 backports fixes for additional portability issues that
4077 could prevent Tor from building correctly on OSX Sierra, or with
4078 OpenSSL 1.1. Affected users should upgrade; others can safely stay
4081 o Minor bugfixes (portability):
4082 - Avoid compilation errors when building on OSX Sierra. Sierra began
4083 to support the getentropy() and clock_gettime() APIs, but created
4084 a few problems in doing so. Tor 0.2.9 has a more thorough set of
4085 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
4086 monotonic time interfaces. Fixes bug 20865. Bugfix
4089 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
4090 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
4091 architectures. Closes ticket 20588.
4094 Changes in version 0.2.8.10 - 2016-12-02
4095 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
4096 unusable after they left standby mode. It also backports fixes for
4097 a few portability issues and a small but problematic memory leak.
4099 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
4100 - When Tor leaves standby because of a new application request, open
4101 circuits as needed to serve that request. Previously, we would
4102 potentially wait a very long time. Fixes part of bug 19969; bugfix
4105 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
4106 - Clients now respond to new application stream requests immediately
4107 when they arrive, rather than waiting up to one second before
4108 starting to handle them. Fixes part of bug 19969; bugfix
4111 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
4112 - Work around a bug in the OSX 10.12 SDK that would prevent us from
4113 successfully targeting earlier versions of OSX. Resolves
4116 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
4117 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
4118 20551; bugfix on 0.2.1.1-alpha.
4120 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
4121 - Work around a memory leak in OpenSSL 1.1 when encoding public
4122 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
4124 o Minor features (geoip):
4125 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
4128 Changes in version 0.2.9.6-rc - 2016-12-02
4129 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
4130 version. We hope that it will be ready to become stable soon, and we
4131 encourage everyone to test this release. If no showstopper bugs are
4132 found here, the next 0.2.9 release will be stable.
4134 o Major bugfixes (relay, resolver, logging):
4135 - For relays that don't know their own address, avoid attempting a
4136 local hostname resolve for each descriptor we download. This
4137 will cut down on the number of "Success: chose address 'x.x.x.x'"
4138 log lines, and also avoid confusing clock jumps if the resolver
4139 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
4141 o Minor bugfixes (client, fascistfirewall):
4142 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
4143 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
4145 o Minor bugfixes (hidden services):
4146 - Stop ignoring the anonymity status of saved keys for hidden
4147 services and single onion services when first starting tor.
4148 Instead, refuse to start tor if any hidden service key has been
4149 used in a different hidden service anonymity mode. Fixes bug
4150 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
4152 o Minor bugfixes (portability):
4153 - Work around a bug in the OSX 10.12 SDK that would prevent us from
4154 successfully targeting earlier versions of OSX. Resolves
4156 - Run correctly when built on Windows build environments that
4157 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
4159 o Minor bugfixes (single onion services, Tor2web):
4160 - Stop complaining about long-term one-hop circuits deliberately
4161 created by single onion services and Tor2web. These log messages
4162 are intended to diagnose issue 8387, which relates to circuits
4163 hanging around forever for no reason. Fixes bug 20613; bugfix on
4164 0.2.9.1-alpha. Reported by "pastly".
4166 o Minor bugfixes (unit tests):
4167 - Stop spurious failures in the local interface address discovery
4168 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
4172 - Correct the minimum bandwidth value in torrc.sample, and queue a
4173 corresponding change for torrc.minimal. Closes ticket 20085.
4176 Changes in version 0.2.9.5-alpha - 2016-11-08
4177 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
4178 version. We believe one or two probably remain, and we encourage
4179 everyone to test this release.
4181 o Major bugfixes (client performance):
4182 - Clients now respond to new application stream requests immediately
4183 when they arrive, rather than waiting up to one second before
4184 starting to handle them. Fixes part of bug 19969; bugfix
4187 o Major bugfixes (client reliability):
4188 - When Tor leaves standby because of a new application request, open
4189 circuits as needed to serve that request. Previously, we would
4190 potentially wait a very long time. Fixes part of bug 19969; bugfix
4193 o Major bugfixes (download scheduling):
4194 - When using an exponential backoff schedule, do not give up on
4195 downloading just because we have failed a bunch of times. Since
4196 each delay is longer than the last, retrying indefinitely won't
4197 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
4198 - If a consensus expires while we are waiting for certificates to
4199 download, stop waiting for certificates.
4200 - If we stop waiting for certificates less than a minute after we
4201 started downloading them, do not consider the certificate download
4202 failure a separate failure. Fixes bug 20533; bugfix
4204 - Remove the maximum delay on exponential-backoff scheduling. Since
4205 we now allow an infinite number of failures (see ticket 20536), we
4206 must now allow the time to grow longer on each failure. Fixes part
4207 of bug 20534; bugfix on 0.2.9.1-alpha.
4208 - Make our initial download delays closer to those from 0.2.8. Fixes
4209 another part of bug 20534; bugfix on 0.2.9.1-alpha.
4210 - When determining when to download a directory object, handle times
4211 after 2038 if the operating system supports them. (Someday this
4212 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
4213 - When using exponential backoff in test networks, use a lower
4214 exponent, so the delays do not vary as much. This helps test
4215 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
4217 o Minor features (geoip):
4218 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
4221 o Minor bugfixes (client directory scheduling):
4222 - Treat "relay too busy to answer request" as a failed request and a
4223 reason to back off on our retry frequency. This is safe now that
4224 exponential backoffs retry indefinitely, and avoids a bug where we
4225 would reset our download schedule erroneously. Fixes bug 20593;
4226 bugfix on 0.2.9.1-alpha.
4228 o Minor bugfixes (client, logging):
4229 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
4230 assume all nodes support EXTEND2. Use ntor whenever a key is
4231 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
4232 - On DNSPort, stop logging a BUG warning on a failed hostname
4233 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
4235 o Minor bugfixes (hidden services):
4236 - When configuring hidden services, check every hidden service
4237 directory's permissions. Previously, we only checked the last
4238 hidden service. Fixes bug 20529; bugfix the work to fix 13942
4241 o Minor bugfixes (portability):
4242 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
4243 architectures. Closes ticket 20588.
4244 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
4245 removed the ECDH ciphers which caused the tests to fail on
4246 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
4247 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
4248 20551; bugfix on 0.2.1.1-alpha.
4250 o Minor bugfixes (relay bootstrap):
4251 - Ensure relays don't make multiple connections during bootstrap.
4252 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
4254 o Minor bugfixes (relay):
4255 - Work around a memory leak in OpenSSL 1.1 when encoding public
4256 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
4257 - Avoid a small memory leak when informing worker threads about
4258 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
4259 - Do not try to parallelize workers more than 16x without the user
4260 explicitly configuring us to do so, even if we do detect more than
4261 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4263 o Minor bugfixes (single onion services):
4264 - Start correctly when creating a single onion service in a
4265 directory that did not previously exist. Fixes bug 20484; bugfix
4268 o Minor bugfixes (testing):
4269 - Avoid a unit test failure on systems with over 16 detectable CPU
4270 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4273 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
4274 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
4275 - Module-level documentation for several more modules. Closes
4276 tickets 19287 and 19290.
4279 Changes in version 0.2.8.9 - 2016-10-17
4280 Tor 0.2.8.9 backports a fix for a security hole in previous versions
4281 of Tor that would allow a remote attacker to crash a Tor client,
4282 hidden service, relay, or authority. All Tor users should upgrade to
4283 this version, or to 0.2.9.4-alpha. Patches will be released for older
4286 o Major features (security fixes, also in 0.2.9.4-alpha):
4287 - Prevent a class of security bugs caused by treating the contents
4288 of a buffer chunk as if they were a NUL-terminated string. At
4289 least one such bug seems to be present in all currently used
4290 versions of Tor, and would allow an attacker to remotely crash
4291 most Tor instances, especially those compiled with extra compiler
4292 hardening. With this defense in place, such bugs can't crash Tor,
4293 though we should still fix them as they occur. Closes ticket
4294 20384 (TROVE-2016-10-001).
4296 o Minor features (geoip):
4297 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
4301 Changes in version 0.2.9.4-alpha - 2016-10-17
4302 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
4303 that would allow a remote attacker to crash a Tor client, hidden
4304 service, relay, or authority. All Tor users should upgrade to this
4305 version, or to 0.2.8.9. Patches will be released for older versions
4308 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
4309 previous versions of Tor, including the implementation of a feature to
4310 future- proof the Tor ecosystem against protocol changes, some bug
4311 fixes necessary for Tor Browser to use unix domain sockets correctly,
4312 and several portability improvements. We anticipate that this will be
4313 the last alpha in the Tor 0.2.9 series, and that the next release will
4314 be a release candidate.
4316 o Major features (security fixes):
4317 - Prevent a class of security bugs caused by treating the contents
4318 of a buffer chunk as if they were a NUL-terminated string. At
4319 least one such bug seems to be present in all currently used
4320 versions of Tor, and would allow an attacker to remotely crash
4321 most Tor instances, especially those compiled with extra compiler
4322 hardening. With this defense in place, such bugs can't crash Tor,
4323 though we should still fix them as they occur. Closes ticket
4324 20384 (TROVE-2016-10-001).
4326 o Major features (subprotocol versions):
4327 - Tor directory authorities now vote on a set of recommended
4328 subprotocol versions, and on a set of required subprotocol
4329 versions. Clients and relays that lack support for a _required_
4330 subprotocol version will not start; those that lack support for a
4331 _recommended_ subprotocol version will warn the user to upgrade.
4332 Closes ticket 19958; implements part of proposal 264.
4333 - Tor now uses "subprotocol versions" to indicate compatibility.
4334 Previously, versions of Tor looked at the declared Tor version of
4335 a relay to tell whether they could use a given feature. Now, they
4336 should be able to rely on its declared subprotocol versions. This
4337 change allows compatible implementations of the Tor protocol(s) to
4338 exist without pretending to be 100% bug-compatible with particular
4339 releases of Tor itself. Closes ticket 19958; implements part of
4342 o Minor feature (fallback directories):
4343 - Remove broken fallbacks from the hard-coded fallback directory
4344 list. Closes ticket 20190; patch by teor.
4346 o Minor features (client, directory):
4347 - Since authorities now omit all routers that lack the Running and
4348 Valid flags, we assume that any relay listed in the consensus must
4349 have those flags. Closes ticket 20001; implements part of
4352 o Minor features (compilation, portability):
4353 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
4356 o Minor features (development tools, etags):
4357 - Teach the "make tags" Makefile target how to correctly find
4358 "MOCK_IMPL" function definitions. Patch from nherring; closes
4361 o Minor features (geoip):
4362 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
4365 o Minor features (unix domain sockets):
4366 - When configuring a unix domain socket for a SocksPort,
4367 ControlPort, or Hidden service, you can now wrap the address in
4368 quotes, using C-style escapes inside the quotes. This allows unix
4369 domain socket paths to contain spaces.
4371 o Minor features (virtual addresses):
4372 - Increase the maximum number of bits for the IPv6 virtual network
4373 prefix from 16 to 104. In this way, the condition for address
4374 allocation is less restrictive. Closes ticket 20151; feature
4377 o Minor bugfixes (address discovery):
4378 - Stop reordering IP addresses returned by the OS. This makes it
4379 more likely that Tor will guess the same relay IP address every
4380 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
4381 Reported by René Mayrhofer, patch by "cypherpunks".
4383 o Minor bugfixes (client, unix domain sockets):
4384 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
4385 the client address is meaningless. Fixes bug 20261; bugfix
4388 o Minor bugfixes (compilation, OpenBSD):
4389 - Detect Libevent2 functions correctly on systems that provide
4390 libevent2, but where libevent1 is linked with -levent. Fixes bug
4391 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
4393 o Minor bugfixes (configuration):
4394 - When parsing quoted configuration values from the torrc file,
4395 handle windows line endings correctly. Fixes bug 19167; bugfix on
4396 0.2.0.16-alpha. Patch from "Pingl".
4398 o Minor bugfixes (getpass):
4399 - Defensively fix a non-triggerable heap corruption at do_getpass()
4400 to protect ourselves from mistakes in the future. Fixes bug
4401 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
4404 o Minor bugfixes (hidden service):
4405 - Allow hidden services to run on IPv6 addresses even when the
4406 IPv6Exit option is not set. Fixes bug 18357; bugfix
4410 - Add module-level internal documentation for 36 C files that
4411 previously didn't have a high-level overview. Closes ticket #20385.
4413 o Required libraries:
4414 - When building with OpenSSL, Tor now requires version 1.0.1 or
4415 later. OpenSSL 1.0.0 and earlier are no longer supported by the
4416 OpenSSL team, and should not be used. Closes ticket 20303.
4419 Changes in version 0.2.9.3-alpha - 2016-09-23
4420 Tor 0.2.9.3-alpha adds improved support for entities that want to make
4421 high-performance services available through the Tor .onion mechanism
4422 without themselves receiving anonymity as they host those services. It
4423 also tries harder to ensure that all steps on a circuit are using the
4424 strongest crypto possible, strengthens some TLS properties, and
4425 resolves several bugs -- including a pair of crash bugs from the 0.2.8
4426 series. Anybody running an earlier version of 0.2.9.x should upgrade.
4428 o Major bugfixes (crash, also in 0.2.8.8):
4429 - Fix a complicated crash bug that could affect Tor clients
4430 configured to use bridges when replacing a networkstatus consensus
4431 in which one of their bridges was mentioned. OpenBSD users saw
4432 more crashes here, but all platforms were potentially affected.
4433 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
4435 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
4436 - Fix a timing-dependent assertion failure that could occur when we
4437 tried to flush from a circuit after having freed its cells because
4438 of an out-of-memory condition. Fixes bug 20203; bugfix on
4439 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
4442 o Major features (circuit building, security):
4443 - Authorities, relays and clients now require ntor keys in all
4444 descriptors, for all hops (except for rare hidden service protocol
4445 cases), for all circuits, and for all other roles. Part of
4447 - Tor authorities, relays, and clients only use ntor, except for
4448 rare cases in the hidden service protocol. Part of ticket 19163.
4450 o Major features (single-hop "hidden" services):
4451 - Add experimental HiddenServiceSingleHopMode and
4452 HiddenServiceNonAnonymousMode options. When both are set to 1,
4453 every hidden service on a Tor instance becomes a non-anonymous
4454 Single Onion Service. Single Onions make one-hop (direct)
4455 connections to their introduction and renzedvous points. One-hop
4456 circuits make Single Onion servers easily locatable, but clients
4457 remain location-anonymous. This is compatible with the existing
4458 hidden service implementation, and works on the current tor
4459 network without any changes to older relays or clients. Implements
4460 proposal 260, completes ticket 17178. Patch by teor and asn.
4462 o Major features (resource management):
4463 - Tor can now notice it is about to run out of sockets, and
4464 preemptively close connections of lower priority. (This feature is
4465 off by default for now, since the current prioritizing method is
4466 yet not mature enough. You can enable it by setting
4467 "DisableOOSCheck 0", but watch out: it might close some sockets
4468 you would rather have it keep.) Closes ticket 18640.
4470 o Major bugfixes (circuit building):
4471 - Hidden service client-to-intro-point and service-to-rendezvous-
4472 point circuits use the TAP key supplied by the protocol, to avoid
4473 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
4475 o Major bugfixes (compilation, OpenBSD):
4476 - Fix a Libevent-detection bug in our autoconf script that would
4477 prevent Tor from linking successfully on OpenBSD. Patch from
4478 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
4480 o Major bugfixes (hidden services):
4481 - Clients now require hidden services to include the TAP keys for
4482 their intro points in the hidden service descriptor. This prevents
4483 an inadvertent upgrade to ntor, which a malicious hidden service
4484 could use to distinguish clients by consensus version. Fixes bug
4485 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
4487 o Minor features (security, TLS):
4488 - Servers no longer support clients that without AES ciphersuites.
4489 (3DES is no longer considered an acceptable cipher.) We believe
4490 that no such Tor clients currently exist, since Tor has required
4491 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
4493 o Minor feature (fallback directories):
4494 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
4495 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
4496 2016. Closes ticket 20190; patch by teor.
4498 o Minor features (geoip, also in 0.2.8.8):
4499 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
4502 o Minor feature (port flags):
4503 - Add new flags to the *Port options to finer control over which
4504 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
4505 and the synthetic flag OnionTrafficOnly, which is equivalent to
4506 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
4507 18693; patch by "teor".
4509 o Minor features (directory authority):
4510 - After voting, if the authorities decide that a relay is not
4511 "Valid", they no longer include it in the consensus at all. Closes
4512 ticket 20002; implements part of proposal 272.
4514 o Minor features (testing):
4515 - Disable memory protections on OpenBSD when performing our unit
4516 tests for memwipe(). The test deliberately invokes undefined
4517 behavior, and the OpenBSD protections interfere with this. Patch
4518 from "rubiate". Closes ticket 20066.
4520 o Minor features (testing, ipv6):
4521 - Add the single-onion and single-onion-ipv6 chutney targets to
4522 "make test-network-all". This requires a recent chutney version
4523 with the single onion network flavours (git c72a652 or later).
4524 Closes ticket 20072; patch by teor.
4525 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
4526 tests. Remove bridges+hs, as it's somewhat redundant. This
4527 requires a recent chutney version that supports IPv6 clients,
4528 relays, and authorities. Closes ticket 20069; patch by teor.
4530 o Minor features (Tor2web):
4531 - Make Tor2web clients respect ReachableAddresses. This feature was
4532 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
4533 0.2.8.7. Implements feature 20034. Patch by teor.
4535 o Minor features (unit tests):
4536 - We've done significant work to make the unit tests run faster.
4537 - Our link-handshake unit tests now check that when invalid
4538 handshakes fail, they fail with the error messages we expected.
4539 - Our unit testing code that captures log messages no longer
4540 prevents them from being written out if the user asked for them
4541 (by passing --debug or --info or or --notice --warn to the "test"
4542 binary). This change prevents us from missing unexpected log
4543 messages simply because we were looking for others. Related to
4545 - The unit tests now log all warning messages with the "BUG" flag.
4546 Previously, they only logged errors by default. This change will
4547 help us make our testing code more correct, and make sure that we
4548 only hit this code when we mean to. In the meantime, however,
4549 there will be more warnings in the unit test logs than before.
4550 This is preparatory work for ticket 19999.
4551 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
4552 assertion as a test failure.
4554 o Minor bug fixes (circuits):
4555 - Use the CircuitBuildTimeout option whenever
4556 LearnCircuitBuildTimeout is disabled. Previously, we would respect
4557 the option when a user disabled it, but not when it was disabled
4558 because some other option was set. Fixes bug 20073; bugfix on
4559 0.2.4.12-alpha. Patch by teor.
4561 o Minor bugfixes (allocation):
4562 - Change how we allocate memory for large chunks on buffers, to
4563 avoid a (currently impossible) integer overflow, and to waste less
4564 space when allocating unusually large chunks. Fixes bug 20081;
4565 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
4566 - Always include orconfig.h before including any other C headers.
4567 Sometimes, it includes macros that affect the behavior of the
4568 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
4569 first version to use AC_USE_SYSTEM_EXTENSIONS).
4570 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
4571 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
4572 Patch from Gisle Vanem.
4573 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
4574 They apparently require a set of annotations that we aren't
4575 currently using, and they create false positives in our pthreads
4576 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
4578 o Minor bugfixes (directory authority):
4579 - Die with a more useful error when the operator forgets to place
4580 the authority_signing_key file into the keys directory. This
4581 avoids an uninformative assert & traceback about having an invalid
4582 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
4583 - When allowing private addresses, mark Exits that only exit to
4584 private locations as such. Fixes bug 20064; bugfix
4587 o Minor bugfixes (documentation):
4588 - Document the default PathsNeededToBuildCircuits value that's used
4589 by clients when the directory authorities don't set
4590 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
4591 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
4592 - Fix manual for the User option: it takes a username, not a UID.
4593 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
4596 o Minor bugfixes (hidden services):
4597 - Stop logging intro point details to the client log on certain
4598 error conditions. Fixed as part of bug 20012; bugfix on
4599 0.2.4.8-alpha. Patch by teor.
4601 o Minor bugfixes (IPv6, testing):
4602 - Check for IPv6 correctly on Linux when running test networks.
4603 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
4605 o Minor bugfixes (Linux seccomp2 sandbox):
4606 - Add permission to run the sched_yield() and sigaltstack() system
4607 calls, in order to support versions of Tor compiled with asan or
4608 ubsan code that use these calls. Now "sandbox 1" and
4609 "--enable-expensive-hardening" should be compatible on more
4610 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
4612 o Minor bugfixes (logging):
4613 - When logging a message from the BUG() macro, be explicit about
4614 what we were asserting. Previously we were confusing what we were
4615 asserting with what the bug was. Fixes bug 20093; bugfix
4617 - When we are unable to remove the bw_accounting file, do not warn
4618 if the reason we couldn't remove it was that it didn't exist.
4619 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
4621 o Minor bugfixes (option parsing):
4622 - Count unix sockets when counting client listeners (SOCKS, Trans,
4623 NATD, and DNS). This has no user-visible behaviour changes: these
4624 options are set once, and never read. Required for correct
4625 behaviour in ticket 17178. Fixes bug 19677; bugfix on
4626 0.2.6.3-alpha. Patch by teor.
4628 o Minor bugfixes (options):
4629 - Check the consistency of UseEntryGuards and EntryNodes more
4630 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
4632 - Stop changing the configured value of UseEntryGuards on
4633 authorities and Tor2web clients. Fixes bug 20074; bugfix on
4634 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
4637 o Minor bugfixes (Tor2web):
4638 - Prevent Tor2web clients running hidden services, these services
4639 are not anonymous due to the one-hop client paths. Fixes bug
4640 19678. Patch by teor.
4642 o Minor bugfixes (unit tests):
4643 - Fix a shared-random unit test that was failing on big endian
4644 architectures due to internal representation of a integer copied
4645 to a buffer. The test is changed to take a full 32 bytes of data
4646 and use the output of a python script that make the COMMIT and
4647 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
4649 - The tor_tls_server_info_callback unit test no longer crashes when
4650 debug-level logging is turned on. Fixes bug 20041; bugfix
4654 Changes in version 0.2.8.8 - 2016-09-23
4655 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
4656 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
4657 who select public relays as their bridges.
4659 o Major bugfixes (crash):
4660 - Fix a complicated crash bug that could affect Tor clients
4661 configured to use bridges when replacing a networkstatus consensus
4662 in which one of their bridges was mentioned. OpenBSD users saw
4663 more crashes here, but all platforms were potentially affected.
4664 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
4666 o Major bugfixes (relay, OOM handler):
4667 - Fix a timing-dependent assertion failure that could occur when we
4668 tried to flush from a circuit after having freed its cells because
4669 of an out-of-memory condition. Fixes bug 20203; bugfix on
4670 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
4673 o Minor feature (fallback directories):
4674 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
4675 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
4676 2016. Closes ticket 20190; patch by teor.
4678 o Minor features (geoip):
4679 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
4683 Changes in version 0.2.9.2-alpha - 2016-08-24
4684 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
4685 several new features and bugfixes. It also includes an important
4686 authority update and an important bugfix from 0.2.8.7. Everyone who
4687 sets the ReachableAddresses option, and all bridges, are strongly
4688 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
4690 o Directory authority changes (also in 0.2.8.7):
4691 - The "Tonga" bridge authority has been retired; the new bridge
4692 authority is "Bifroest". Closes tickets 19728 and 19690.
4694 o Major bugfixes (client, security, also in 0.2.8.7):
4695 - Only use the ReachableAddresses option to restrict the first hop
4696 in a path. In earlier versions of 0.2.8.x, it would apply to
4697 every hop in the path, with a possible degradation in anonymity
4698 for anyone using an uncommon ReachableAddress setting. Fixes bug
4699 19973; bugfix on 0.2.8.2-alpha.
4701 o Major features (user interface):
4702 - Tor now supports the ability to declare options deprecated, so
4703 that we can recommend that people stop using them. Previously,
4704 this was done in an ad-hoc way. Closes ticket 19820.
4706 o Major bugfixes (directory downloads):
4707 - Avoid resetting download status for consensuses hourly, since we
4708 already have another, smarter retry mechanism. Fixes bug 8625;
4709 bugfix on 0.2.0.9-alpha.
4711 o Minor features (config):
4712 - Warn users when descriptor and port addresses are inconsistent.
4713 Mitigates bug 13953; patch by teor.
4715 o Minor features (geoip):
4716 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
4719 o Minor features (user interface):
4720 - There is a new --list-deprecated-options command-line option to
4721 list all of the deprecated options. Implemented as part of
4724 o Minor bugfixes (code style):
4725 - Fix an integer signedness conversion issue in the case conversion
4726 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
4728 o Minor bugfixes (compilation):
4729 - Build correctly on versions of libevent2 without support for
4730 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
4732 - Fix a compilation warning on GCC versions before 4.6. Our
4733 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
4734 when it is also required as an argument to the compiler pragma.
4735 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
4737 o Minor bugfixes (compilation, also in 0.2.8.7):
4738 - Remove an inappropriate "inline" in tortls.c that was causing
4739 warnings on older versions of GCC. Fixes bug 19903; bugfix
4742 o Minor bugfixes (fallback directories, also in 0.2.8.7):
4743 - Avoid logging a NULL string pointer when loading fallback
4744 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
4745 and 0.2.8.1-alpha. Report and patch by "rubiate".
4747 o Minor bugfixes (logging):
4748 - Log a more accurate message when we fail to dump a microdescriptor.
4749 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
4751 o Minor bugfixes (memory leak):
4752 - Fix a series of slow memory leaks related to parsing torrc files
4753 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
4755 o Deprecated features:
4756 - A number of DNS-cache-related sub-options for client ports are now
4757 deprecated for security reasons, and may be removed in a future
4758 version of Tor. (We believe that client-side DNS cacheing is a bad
4759 idea for anonymity, and you should not turn it on.) The options
4760 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
4761 UseIPv4Cache, and UseIPv6Cache.
4762 - A number of options are deprecated for security reasons, and may
4763 be removed in a future version of Tor. The options are:
4764 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
4765 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
4766 CloseHSClientCircuitsImmediatelyOnTimeout,
4767 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
4768 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
4769 UseNTorHandshake, and WarnUnsafeSocks.
4770 - The *ListenAddress options are now deprecated as unnecessary: the
4771 corresponding *Port options should be used instead. These options
4772 may someday be removed. The affected options are:
4773 ControlListenAddress, DNSListenAddress, DirListenAddress,
4774 NATDListenAddress, ORListenAddress, SocksListenAddress,
4775 and TransListenAddress.
4778 - Correct the IPv6 syntax in our documentation for the
4779 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
4782 - We no longer include the (dead, deprecated) bufferevent code in
4783 Tor. Closes ticket 19450. Based on a patch from U+039b.
4786 Changes in version 0.2.8.7 - 2016-08-24
4787 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
4788 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
4789 who sets the ReachableAddresses option, and all bridges, are strongly
4790 encouraged to upgrade.
4792 o Directory authority changes:
4793 - The "Tonga" bridge authority has been retired; the new bridge
4794 authority is "Bifroest". Closes tickets 19728 and 19690.
4796 o Major bugfixes (client, security):
4797 - Only use the ReachableAddresses option to restrict the first hop
4798 in a path. In earlier versions of 0.2.8.x, it would apply to
4799 every hop in the path, with a possible degradation in anonymity
4800 for anyone using an uncommon ReachableAddress setting. Fixes bug
4801 19973; bugfix on 0.2.8.2-alpha.
4803 o Minor features (geoip):
4804 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
4807 o Minor bugfixes (compilation):
4808 - Remove an inappropriate "inline" in tortls.c that was causing
4809 warnings on older versions of GCC. Fixes bug 19903; bugfix
4812 o Minor bugfixes (fallback directories):
4813 - Avoid logging a NULL string pointer when loading fallback
4814 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
4815 and 0.2.8.1-alpha. Report and patch by "rubiate".
4818 Changes in version 0.2.9.1-alpha - 2016-08-08
4819 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
4820 series. It improves our support for hardened builds and compiler
4821 warnings, deploys some critical infrastructure for improvements to
4822 hidden services, includes a new timing backend that we hope to use for
4823 better support for traffic padding, makes it easier for programmers to
4824 log unexpected events, and contains other small improvements to
4825 security, correctness, and performance.
4827 Below are the changes since 0.2.8.6.
4829 o New system requirements:
4830 - Tor now requires Libevent version 2.0.10-stable or later. Older
4831 versions of Libevent have less efficient backends for several
4832 platforms, and lack the DNS code that we use for our server-side
4833 DNS support. This implements ticket 19554.
4834 - Tor now requires zlib version 1.2 or later, for security,
4835 efficiency, and (eventually) gzip support. (Back when we started,
4836 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
4837 released in 2003. We recommend the latest version.)
4839 o Major features (build, hardening):
4840 - Tor now builds with -ftrapv by default on compilers that support
4841 it. This option detects signed integer overflow (which C forbids),
4842 and turns it into a hard-failure. We do not apply this option to
4843 code that needs to run in constant time to avoid side-channels;
4844 instead, we use -fwrapv in that code. Closes ticket 17983.
4845 - When --enable-expensive-hardening is selected, stop applying the
4846 clang/gcc sanitizers to code that needs to run in constant time.
4847 Although we are aware of no introduced side-channels, we are not
4848 able to prove that there are none. Related to ticket 17983.
4850 o Major features (compilation):
4851 - Our big list of extra GCC warnings is now enabled by default when
4852 building with GCC (or with anything like Clang that claims to be
4853 GCC-compatible). To make all warnings into fatal compilation
4854 errors, pass --enable-fatal-warnings to configure. Closes
4856 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
4857 turn on C and POSIX extensions. (Previously, we attempted to do
4858 this on an ad hoc basis.) Closes ticket 19139.
4860 o Major features (directory authorities, hidden services):
4861 - Directory authorities can now perform the shared randomness
4862 protocol specified by proposal 250. Using this protocol, directory
4863 authorities generate a global fresh random value every day. In the
4864 future, this value will be used by hidden services to select
4865 HSDirs. This release implements the directory authority feature;
4866 the hidden service side will be implemented in the future as part
4867 of proposal 224. Resolves ticket 16943; implements proposal 250.
4869 o Major features (downloading, random exponential backoff):
4870 - When we fail to download an object from a directory service, wait
4871 for an (exponentially increasing) randomized amount of time before
4872 retrying, rather than a fixed interval as we did before. This
4873 prevents a group of Tor instances from becoming too synchronized,
4874 or a single Tor instance from becoming too predictable, in its
4875 download schedule. Closes ticket 15942.
4877 o Major bugfixes (exit policies):
4878 - Avoid disclosing exit outbound bind addresses, configured port
4879 bind addresses, and local interface addresses in relay descriptors
4880 by default under ExitPolicyRejectPrivate. Instead, only reject
4881 these (otherwise unlisted) addresses if
4882 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
4883 0.2.7.2-alpha. Patch by teor.
4885 o Major bugfixes (hidden service client):
4886 - Allow Tor clients with appropriate controllers to work with
4887 FetchHidServDescriptors set to 0. Previously, this option also
4888 disabled descriptor cache lookup, thus breaking hidden services
4889 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
4891 o Minor features (build, hardening):
4892 - Detect and work around a libclang_rt problem that would prevent
4893 clang from finding __mulodi4() on some 32-bit platforms, and thus
4894 keep -ftrapv from linking on those systems. Closes ticket 19079.
4895 - When building on a system without runtime support for the runtime
4896 hardening options, try to log a useful warning at configuration
4897 time, rather than an incomprehensible warning at link time. If
4898 expensive hardening was requested, this warning becomes an error.
4899 Closes ticket 18895.
4901 o Minor features (code safety):
4902 - In our integer-parsing functions, ensure that maxiumum value we
4903 give is no smaller than the minimum value. Closes ticket 19063;
4906 o Minor features (controller):
4907 - Implement new GETINFO queries for all downloads that use
4908 download_status_t to schedule retries. This allows controllers to
4909 examine the schedule for pending downloads. Closes ticket 19323.
4910 - Allow controllers to configure basic client authorization on
4911 hidden services when they create them with the ADD_ONION control
4912 command. Implements ticket 15588. Patch by "special".
4913 - Fire a STATUS_SERVER controller event whenever the hibernation
4914 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
4916 o Minor features (directory authority):
4917 - Directory authorities now only give the Guard flag to a relay if
4918 they are also giving it the Stable flag. This change allows us to
4919 simplify path selection for clients. It should have minimal effect
4920 in practice, since >99% of Guards already have the Stable flag.
4921 Implements ticket 18624.
4922 - Directory authorities now write their v3-status-votes file out to
4923 disk earlier in the consensus process, so we have a record of the
4924 votes even if we abort the consensus process. Resolves
4927 o Minor features (hidden service):
4928 - Stop being so strict about the payload length of "rendezvous1"
4929 cells. We used to be locked in to the "TAP" handshake length, and
4930 now we can handle better handshakes like "ntor". Resolves
4933 o Minor features (infrastructure, time):
4934 - Tor now uses the operating system's monotonic timers (where
4935 available) for internal fine-grained timing. Previously we would
4936 look at the system clock, and then attempt to compensate for the
4937 clock running backwards. Closes ticket 18908.
4938 - Tor now includes an improved timer backend, so that we can
4939 efficiently support tens or hundreds of thousands of concurrent
4940 timers, as will be needed for some of our planned anti-traffic-
4941 analysis work. This code is based on William Ahern's "timeout.c"
4942 project, which implements a "tickless hierarchical timing wheel".
4943 Closes ticket 18365.
4945 o Minor features (logging):
4946 - Provide a more useful warning message when configured with an
4947 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
4948 - When dumping unparseable router descriptors, optionally store them
4949 in separate files, named by digest, up to a configurable size
4950 limit. You can change the size limit by setting the
4951 MaxUnparseableDescSizeToLog option, and disable this feature by
4952 setting that option to 0. Closes ticket 18322.
4953 - Add a set of macros to check nonfatal assertions, for internal
4954 use. Migrating more of our checks to these should help us avoid
4955 needless crash bugs. Closes ticket 18613.
4957 o Minor features (performance):
4958 - Changer the "optimistic data" extension from "off by default" to
4959 "on by default". The default was ordinarily overridden by a
4960 consensus option, but when clients were bootstrapping for the
4961 first time, they would not have a consensus to get the option
4962 from. Changing this default When fetching a consensus for the
4963 first time, use optimistic data. This saves a round-trip during
4964 startup. Closes ticket 18815.
4966 o Minor features (relay, usability):
4967 - When the directory authorities refuse a bad relay's descriptor,
4968 encourage the relay operator to contact us. Many relay operators
4969 won't notice this line in their logs, but it's a win if even a few
4970 learn why we don't like what their relay was doing. Resolves
4973 o Minor features (testing):
4974 - Let backtrace tests work correctly under AddressSanitizer. Fixes
4975 part of bug 18934; bugfix on 0.2.5.2-alpha.
4976 - Move the test-network.sh script to chutney, and modify tor's test-
4977 network.sh to call the (newer) chutney version when available.
4978 Resolves ticket 19116. Patch by teor.
4979 - Use the lcov convention for marking lines as unreachable, so that
4980 we don't count them when we're generating test coverage data.
4981 Update our coverage tools to understand this convention. Closes
4984 o Minor bugfixes (bootstrap):
4985 - Remember the directory we fetched the consensus or previous
4986 certificates from, and use it to fetch future authority
4987 certificates. This change improves bootstrapping performance.
4988 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
4990 o Minor bugfixes (build):
4991 - The test-stem and test-network makefile targets now depend only on
4992 the tor binary that they are testing. Previously, they depended on
4993 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
4994 patch from "cypherpunks".
4996 o Minor bugfixes (circuits):
4997 - Make sure extend_info_from_router() is only called on servers.
4998 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
5000 o Minor bugfixes (compilation):
5001 - When building with Clang, use a full set of GCC warnings.
5002 (Previously, we included only a subset, because of the way we
5003 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
5005 o Minor bugfixes (directory authority):
5006 - Authorities now sort the "package" lines in their votes, for ease
5007 of debugging. (They are already sorted in consensus documents.)
5008 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
5009 - When parsing a detached signature, make sure we use the length of
5010 the digest algorithm instead of an hardcoded DIGEST256_LEN in
5011 order to avoid comparing bytes out-of-bounds with a smaller digest
5012 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
5014 o Minor bugfixes (documentation):
5015 - Document the --passphrase-fd option in the tor manpage. Fixes bug
5016 19504; bugfix on 0.2.7.3-rc.
5017 - Fix the description of the --passphrase-fd option in the
5018 tor-gencert manpage. The option is used to pass the number of a
5019 file descriptor to read the passphrase from, not to read the file
5020 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
5022 o Minor bugfixes (ephemeral hidden service):
5023 - When deleting an ephemeral hidden service, close its intro points
5024 even if they are not completely open. Fixes bug 18604; bugfix
5027 o Minor bugfixes (guard selection):
5028 - Use a single entry guard even if the NumEntryGuards consensus
5029 parameter is not provided. Fixes bug 17688; bugfix
5031 - Don't mark guards as unreachable if connection_connect() fails.
5032 That function fails for local reasons, so it shouldn't reveal
5033 anything about the status of the guard. Fixes bug 14334; bugfix
5036 o Minor bugfixes (hidden service client):
5037 - Increase the minimum number of internal circuits we preemptively
5038 build from 2 to 3, so a circuit is available when a client
5039 connects to another onion service. Fixes bug 13239; bugfix
5042 o Minor bugfixes (logging):
5043 - When logging a directory ownership mismatch, log the owning
5044 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
5046 o Minor bugfixes (memory leaks):
5047 - Fix a small, uncommon memory leak that could occur when reading a
5048 truncated ed25519 key file. Fixes bug 18956; bugfix
5051 o Minor bugfixes (testing):
5052 - Allow clients to retry HSDirs much faster in test networks. Fixes
5053 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
5054 - Disable ASAN's detection of segmentation faults while running
5055 test_bt.sh, so that we can make sure that our own backtrace
5056 generation code works. Fixes another aspect of bug 18934; bugfix
5057 on 0.2.5.2-alpha. Patch from "cypherpunks".
5058 - Fix the test-network-all target on out-of-tree builds by using the
5059 correct path to the test driver script. Fixes bug 19421; bugfix
5062 o Minor bugfixes (time):
5063 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
5064 bugfix on all released tor versions.
5065 - When computing the difference between two times in milliseconds,
5066 we now round to the nearest millisecond correctly. Previously, we
5067 could sometimes round in the wrong direction. Fixes bug 19428;
5068 bugfix on 0.2.2.2-alpha.
5070 o Minor bugfixes (user interface):
5071 - Display a more accurate number of suppressed messages in the log
5072 rate-limiter. Previously, there was a potential integer overflow
5073 in the counter. Now, if the number of messages hits a maximum, the
5074 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
5076 - Fix a typo in the passphrase prompt for the ed25519 identity key.
5077 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
5079 o Code simplification and refactoring:
5080 - Remove redundant declarations of the MIN macro. Closes
5082 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
5083 Closes ticket 18462; patch from "icanhasaccount".
5084 - Split the 600-line directory_handle_command_get function into
5085 separate functions for different URL types. Closes ticket 16698.
5088 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
5089 ticket 19153. Patch from "U+039b".
5092 - Remove support for "GET /tor/bytes.txt" DirPort request, and
5093 "GETINFO dir-usage" controller request, which were only available
5094 via a compile-time option in Tor anyway. Feature was added in
5095 0.2.2.1-alpha. Resolves ticket 19035.
5096 - There is no longer a compile-time option to disable support for
5097 TransPort. (If you don't want TransPort; just don't use it.) Patch
5098 from "U+039b". Closes ticket 19449.
5101 - Run more workqueue tests as part of "make check". These had
5102 previously been implemented, but you needed to know special
5103 command-line options to enable them.
5104 - We now have unit tests for our code to reject zlib "compression
5105 bombs". (Fortunately, the code works fine.)
5108 Changes in version 0.2.8.6 - 2016-08-02
5110 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
5112 The Tor 0.2.8 series improves client bootstrapping performance,
5113 completes the authority-side implementation of improved identity
5114 keys for relays, and includes numerous bugfixes and performance
5115 improvements throughout the program. This release continues to
5116 improve the coverage of Tor's test suite. For a full list of
5117 changes since Tor 0.2.7, see the ReleaseNotes file.
5119 Changes since 0.2.8.5-rc:
5121 o Minor features (geoip):
5122 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
5125 o Minor bugfixes (compilation):
5126 - Fix a compilation warning in the unit tests on systems where char
5127 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
5129 o Minor bugfixes (fallback directories):
5130 - Remove 1 fallback that was on the hardcoded list, then opted-out,
5131 leaving 89 of the 100 fallbacks originally introduced in Tor
5132 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
5134 o Minor bugfixes (Linux seccomp2 sandbox):
5135 - Allow more syscalls when running with "Sandbox 1" enabled:
5136 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
5137 some systems, these are required for Tor to start. Fixes bug
5138 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
5139 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
5140 so that get_interface_address6_via_udp_socket_hack() can work.
5141 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
5144 Changes in version 0.2.8.5-rc - 2016-07-07
5145 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
5146 series. If we find no new bugs or regressions here, the first stable
5147 0.2.8 release will be identical to it. It has a few small bugfixes
5148 against previous versions.
5150 o Directory authority changes:
5151 - Urras is no longer a directory authority. Closes ticket 19271.
5153 o Major bugfixes (heartbeat):
5154 - Fix a regression that would crash Tor when the periodic
5155 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
5156 0.2.8.1-alpha. Reported by "kubaku".
5158 o Minor features (build):
5159 - Tor now again builds with the recent OpenSSL 1.1 development
5160 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
5161 - When building manual pages, set the timezone to "UTC", so that the
5162 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
5163 Patch from intrigeri.
5165 o Minor bugfixes (fallback directory selection):
5166 - Avoid errors during fallback selection if there are no eligible
5167 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
5170 o Minor bugfixes (IPv6, microdescriptors):
5171 - Don't check node addresses when we only have a routerstatus. This
5172 allows IPv6-only clients to bootstrap by fetching microdescriptors
5173 from fallback directory mirrors. (The microdescriptor consensus
5174 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
5177 o Minor bugfixes (logging):
5178 - Reduce pointlessly verbose log messages when directory servers
5179 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
5180 0.2.8.1-alpha. Patch by teor.
5181 - When a fallback directory changes its fingerprint from the hard-
5182 coded fingerprint, log a less severe, more explanatory log
5183 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
5185 o Minor bugfixes (Linux seccomp2 sandboxing):
5186 - Allow statistics to be written to disk when "Sandbox 1" is
5187 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
5188 0.2.6.1-alpha respectively.
5190 o Minor bugfixes (user interface):
5191 - Remove a warning message "Service [scrubbed] not found after
5192 descriptor upload". This message appears when one uses HSPOST
5193 control command to upload a service descriptor. Since there is
5194 only a descriptor and no service, showing this message is
5195 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
5197 o Fallback directory list:
5198 - Add a comment to the generated fallback directory list that
5199 explains how to comment out unsuitable fallbacks in a way that's
5200 compatible with the stem fallback parser.
5201 - Update fallback whitelist and blacklist based on relay operator
5202 emails. Blacklist unsuitable (non-working, over-volatile)
5203 fallbacks. Resolves ticket 19071. Patch by teor.
5204 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
5205 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
5206 ticket 19071; patch by teor.
5209 Changes in version 0.2.8.4-rc - 2016-06-15
5210 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
5211 If we find no new bugs or regressions here, the first stable 0.2.8
5212 release will be identical to it. It has a few small bugfixes against
5215 o Major bugfixes (user interface):
5216 - Correctly give a warning in the cases where a relay is specified
5217 by nickname, and one such relay is found, but it is not officially
5218 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
5220 o Minor features (build):
5221 - Tor now builds once again with the recent OpenSSL 1.1 development
5222 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
5224 o Minor features (geoip):
5225 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
5228 o Minor bugfixes (compilation):
5229 - Cause the unit tests to compile correctly on mingw64 versions that
5230 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
5232 o Minor bugfixes (downloading):
5233 - Predict more correctly whether we'll be downloading over HTTP when
5234 we determine the maximum length of a URL. This should avoid a
5235 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
5239 Changes in version 0.2.8.3-alpha - 2016-05-26
5240 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
5241 the course of the 0.2.8 development cycle. It improves the behavior of
5242 directory clients, fixes several crash bugs, fixes a gap in compiler
5243 hardening, and allows the full integration test suite to run on
5246 o Major bugfixes (security, client, DNS proxy):
5247 - Stop a crash that could occur when a client running with DNSPort
5248 received a query with multiple address types, and the first
5249 address type was not supported. Found and fixed by Scott Dial.
5250 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5252 o Major bugfixes (security, compilation):
5253 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
5254 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
5255 cause a compiler warning, thereby making other checks fail, and
5256 needlessly disabling compiler-hardening support. Fixes one case of
5257 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
5259 o Major bugfixes (security, directory authorities):
5260 - Fix a crash and out-of-bounds write during authority voting, when
5261 the list of relays includes duplicate ed25519 identity keys. Fixes
5262 bug 19032; bugfix on 0.2.8.2-alpha.
5264 o Major bugfixes (client, bootstrapping):
5265 - Check if bootstrap consensus downloads are still needed when the
5266 linked connection attaches. This prevents tor making unnecessary
5267 begindir-style connections, which are the only directory
5268 connections tor clients make since the fix for 18483 was merged.
5269 - Fix some edge cases where consensus download connections may not
5270 have been closed, even though they were not needed. Related to fix
5272 - Make relays retry consensus downloads the correct number of times,
5273 rather than the more aggressive client retry count. Fixes part of
5275 - Stop downloading consensuses when we have a consensus, even if we
5276 don't have all the certificates for it yet. Fixes bug 18809;
5277 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
5279 o Major bugfixes (directory mirrors):
5280 - Decide whether to advertise begindir support in the the same way
5281 we decide whether to advertise our DirPort. Allowing these
5282 decisions to become out-of-sync led to surprising behavior like
5283 advertising begindir support when hibernation made us not
5284 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
5287 o Major bugfixes (IPv6 bridges, client):
5288 - Actually use IPv6 addresses when selecting directory addresses for
5289 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
5292 o Major bugfixes (key management):
5293 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5294 pointer to the previous (uninitialized) key value. The impact here
5295 should be limited to a difficult-to-trigger crash, if OpenSSL is
5296 running an engine that makes key generation failures possible, or
5297 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5298 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5301 o Major bugfixes (testing):
5302 - Fix a bug that would block 'make test-network-all' on systems where
5303 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
5304 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
5305 bugfix on 0.2.8.1-alpha.
5307 o Minor features (clients):
5308 - Make clients, onion services, and bridge relays always use an
5309 encrypted begindir connection for directory requests. Resolves
5310 ticket 18483. Patch by "teor".
5312 o Minor features (fallback directory mirrors):
5313 - Give each fallback the same weight for client selection; restrict
5314 fallbacks to one per operator; report fallback directory detail
5315 changes when rebuilding list; add new fallback directory mirrors
5316 to the whitelist; and many other minor simplifications and fixes.
5317 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
5318 0.2.8.1-alpha; patch by "teor".
5319 - Replace the 21 fallbacks generated in January 2016 and included in
5320 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
5321 2016. Closes task 17158; patch by "teor".
5323 o Minor features (geoip):
5324 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
5327 o Minor bugfixes (assert, portability):
5328 - Fix an assertion failure in memarea.c on systems where "long" is
5329 shorter than the size of a pointer. Fixes bug 18716; bugfix
5332 o Minor bugfixes (bootstrap):
5333 - Consistently use the consensus download schedule for authority
5334 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
5336 o Minor bugfixes (build):
5337 - Remove a pair of redundant AM_CONDITIONAL declarations from
5338 configure.ac. Fixes one final case of bug 17744; bugfix
5340 - Resolve warnings when building on systems that are concerned with
5341 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
5343 - When libscrypt.h is found, but no libscrypt library can be linked,
5344 treat libscrypt as absent. Fixes bug 19161; bugfix
5347 o Minor bugfixes (client):
5348 - Turn all TestingClientBootstrap* into non-testing torrc options.
5349 This changes simply renames them by removing "Testing" in front of
5350 them and they do not require TestingTorNetwork to be enabled
5351 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
5352 - Make directory node selection more reliable, mainly for IPv6-only
5353 clients and clients with few reachable addresses. Fixes bug 18929;
5354 bugfix on 0.2.8.1-alpha. Patch by "teor".
5356 o Minor bugfixes (controller, microdescriptors):
5357 - Make GETINFO dir/status-vote/current/consensus conform to the
5358 control specification by returning "551 Could not open cached
5359 consensus..." when not caching consensuses. Fixes bug 18920;
5360 bugfix on 0.2.2.6-alpha.
5362 o Minor bugfixes (crypto, portability):
5363 - The SHA3 and SHAKE routines now produce the correct output on Big
5364 Endian systems. No code calls either algorithm yet, so this is
5365 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
5366 - Tor now builds again with the recent OpenSSL 1.1 development
5367 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
5370 o Minor bugfixes (directories):
5371 - When fetching extrainfo documents, compare their SHA256 digests
5372 and Ed25519 signing key certificates with the routerinfo that led
5373 us to fetch them, rather than with the most recent routerinfo.
5374 Otherwise we generate many spurious warnings about mismatches.
5375 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
5377 o Minor bugfixes (logging):
5378 - When we can't generate a signing key because OfflineMasterKey is
5379 set, do not imply that we should have been able to load it. Fixes
5380 bug 18133; bugfix on 0.2.7.2-alpha.
5381 - Stop periodic_event_dispatch() from blasting twelve lines per
5382 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
5383 - When rejecting a misformed INTRODUCE2 cell, only log at
5384 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
5386 o Minor bugfixes (pluggable transports):
5387 - Avoid reporting a spurious error when we decide that we don't need
5388 to terminate a pluggable transport because it has already exited.
5389 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
5391 o Minor bugfixes (pointer arithmetic):
5392 - Fix a bug in memarea_alloc() that could have resulted in remote
5393 heap write access, if Tor had ever passed an unchecked size to
5394 memarea_alloc(). Fortunately, all the sizes we pass to
5395 memarea_alloc() are pre-checked to be less than 128 kilobytes.
5396 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
5399 o Minor bugfixes (relays):
5400 - Consider more config options when relays decide whether to
5401 regenerate their descriptor. Fixes more of bug 12538; bugfix
5403 - Resolve some edge cases where we might launch an ORPort
5404 reachability check even when DisableNetwork is set. Noticed while
5405 fixing bug 18616; bugfix on 0.2.3.9-alpha.
5407 o Minor bugfixes (statistics):
5408 - We now include consensus downloads via IPv6 in our directory-
5409 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
5411 o Minor bugfixes (testing):
5412 - Allow directories in small networks to bootstrap by skipping
5413 DirPort checks when the consensus has no exits. Fixes bug 19003;
5414 bugfix on 0.2.8.1-alpha. Patch by teor.
5415 - Fix a small memory leak that would occur when the
5416 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
5417 bugfix on 0.2.5.2-alpha.
5419 o Minor bugfixes (time handling):
5420 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
5421 field. Otherwise, our unit tests crash on Windows. Fixes bug
5422 18977; bugfix on 0.2.2.25-alpha.
5425 - Document the contents of the 'datadir/keys' subdirectory in the
5426 manual page. Closes ticket 17621.
5427 - Stop recommending use of nicknames to identify relays in our
5428 MapAddress documentation. Closes ticket 18312.
5431 Changes in version 0.2.8.2-alpha - 2016-03-28
5432 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
5433 bugs in earlier versions of Tor, including some that prevented
5434 authorities using Tor 0.2.7.x from running correctly. IPv6 and
5435 directory support should also be much improved.
5437 o New system requirements:
5438 - Tor no longer supports versions of OpenSSL with a broken
5439 implementation of counter mode. (This bug was present in OpenSSL
5440 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
5441 longer runs with, these versions.
5442 - Tor no longer attempts to support platforms where the "time_t"
5443 type is unsigned. (To the best of our knowledge, only OpenVMS does
5444 this, and Tor has never actually built on OpenVMS.) Closes
5446 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
5447 later (released in 2008 and 2009 respectively). If you are
5448 building Tor from the git repository instead of from the source
5449 distribution, and your tools are older than this, you will need to
5450 upgrade. Closes ticket 17732.
5452 o Major bugfixes (security, pointers):
5453 - Avoid a difficult-to-trigger heap corruption attack when extending
5454 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5455 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5456 Reported by Guido Vranken.
5458 o Major bugfixes (bridges, pluggable transports):
5459 - Modify the check for OR connections to private addresses. Allow
5460 bridges on private addresses, including pluggable transports that
5461 ignore the (potentially private) address in the bridge line. Fixes
5462 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
5464 o Major bugfixes (compilation):
5465 - Repair hardened builds under the clang compiler. Previously, our
5466 use of _FORTIFY_SOURCE would conflict with clang's address
5467 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
5469 o Major bugfixes (crash on shutdown):
5470 - Correctly handle detaching circuits from muxes when shutting down.
5471 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
5472 - Fix an assert-on-exit bug related to counting memory usage in
5473 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
5475 o Major bugfixes (crash on startup):
5476 - Fix a segfault during startup: If a Unix domain socket was
5477 configured as listener (such as a ControlSocket or a SocksPort
5478 "unix:" socket), and tor was started as root but not configured to
5479 switch to another user, tor would segfault while trying to string
5480 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
5483 o Major bugfixes (dns proxy mode, crash):
5484 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5485 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5487 o Major bugfixes (relays, bridge clients):
5488 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
5489 bridge clients use the address configured in the bridge line.
5490 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
5493 o Major bugfixes (voting):
5494 - Actually enable support for authorities to match routers by their
5495 Ed25519 identities. Previously, the code had been written, but
5496 some debugging code that had accidentally been left in the
5497 codebase made it stay turned off. Fixes bug 17702; bugfix
5499 - When collating votes by Ed25519 identities, authorities now
5500 include a "NoEdConsensus" flag if the ed25519 value (or lack
5501 thereof) for a server does not reflect the majority consensus.
5502 Related to bug 17668; bugfix on 0.2.7.2-alpha.
5503 - When generating a vote with keypinning disabled, never include two
5504 entries for the same ed25519 identity. This bug was causing
5505 authorities to generate votes that they could not parse when a
5506 router violated key pinning by changing its RSA identity but
5507 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
5508 18318. Bugfix on 0.2.7.2-alpha.
5510 o Minor features (security, win32):
5511 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
5512 attack. Fixes bug 18123; bugfix on all tor versions. Patch
5515 o Minor features (bug-resistance):
5516 - Make Tor survive errors involving connections without a
5517 corresponding event object. Previously we'd fail with an
5518 assertion; now we produce a log message. Related to bug 16248.
5520 o Minor features (build):
5521 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
5522 as having possible IPFW support. Closes ticket 18448. Patch from
5525 o Minor features (code hardening):
5526 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
5527 level code, to harden against accidental failures to NUL-
5528 terminate. Part of ticket 17852. Patch from jsturgix. Found
5531 o Minor features (crypto):
5532 - Validate the hard-coded Diffie-Hellman parameters and ensure that
5533 p is a safe prime, and g is a suitable generator. Closes
5536 o Minor features (geoip):
5537 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
5540 o Minor features (hidden service directory):
5541 - Streamline relay-side hsdir handling: when relays consider whether
5542 to accept an uploaded hidden service descriptor, they no longer
5543 check whether they are one of the relays in the network that is
5544 "supposed" to handle that descriptor. Implements ticket 18332.
5546 o Minor features (IPv6):
5547 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
5548 to 1, tor prefers IPv6 directory addresses.
5549 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
5550 avoids using IPv4 for client OR and directory connections.
5551 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
5552 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
5553 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
5555 o Minor features (linux seccomp2 sandbox):
5556 - Reject attempts to change our Address with "Sandbox 1" enabled.
5557 Changing Address with Sandbox turned on would never actually work,
5558 but previously it would fail in strange and confusing ways. Found
5561 o Minor features (robustness):
5562 - Exit immediately with an error message if the code attempts to use
5563 Libevent without having initialized it. This should resolve some
5564 frequently-made mistakes in our unit tests. Closes ticket 18241.
5566 o Minor features (unix domain sockets):
5567 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
5568 Unix domain sockets without checking the permissions on the parent
5569 directory. (Tor checks permissions by default because some
5570 operating systems only check permissions on the parent directory.
5571 However, some operating systems do look at permissions on the
5572 socket, and tor's default check is unneeded.) Closes ticket 18458.
5575 o Minor bugfixes (exit policies, security):
5576 - Refresh an exit relay's exit policy when interface addresses
5577 change. Previously, tor only refreshed the exit policy when the
5578 configured external address changed. Fixes bug 18208; bugfix on
5579 0.2.7.3-rc. Patch by teor.
5581 o Minor bugfixes (security, hidden services):
5582 - Prevent hidden services connecting to client-supplied rendezvous
5583 addresses that are reserved as internal or multicast. Fixes bug
5584 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
5586 o Minor bugfixes (build):
5587 - Do not link the unit tests against both the testing and non-
5588 testing versions of the static libraries. Fixes bug 18490; bugfix
5590 - Avoid spurious failures from configure files related to calling
5591 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
5592 0.2.0.1-alpha. Patch from "cypherpunks".
5593 - Silence spurious clang-scan warnings in the ed25519_donna code by
5594 explicitly initializing some objects. Fixes bug 18384; bugfix on
5595 0.2.7.2-alpha. Patch by teor.
5597 o Minor bugfixes (client, bootstrap):
5598 - Count receipt of new microdescriptors as progress towards
5599 bootstrapping. Previously, with EntryNodes set, Tor might not
5600 successfully repopulate the guard set on bootstrapping. Fixes bug
5601 16825; bugfix on 0.2.3.1-alpha.
5603 o Minor bugfixes (code correctness):
5604 - Update to the latest version of Trunnel, which tries harder to
5605 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
5606 by clang address sanitizer. Fixes bug 18373; bugfix
5609 o Minor bugfixes (configuration):
5610 - Fix a tiny memory leak when parsing a port configuration ending in
5611 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
5613 o Minor bugfixes (containers):
5614 - If we somehow attempt to construct a heap with more than
5615 1073741822 elements, avoid an integer overflow when maintaining
5616 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
5618 o Minor bugfixes (correctness):
5619 - Fix a bad memory handling bug that would occur if we had queued a
5620 cell on a channel's incoming queue. Fortunately, we can't actually
5621 queue a cell like that as our code is constructed today, but it's
5622 best to avoid this kind of error, even if there isn't any code
5623 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
5625 o Minor bugfixes (directory):
5626 - When generating a URL for a directory server on an IPv6 address,
5627 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
5628 on 0.2.3.9-alpha. Patch from Malek.
5630 o Minor bugfixes (fallback directory mirrors):
5631 - When requesting extrainfo descriptors from a trusted directory
5632 server, check whether it is an authority or a fallback directory
5633 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
5634 0.2.4.7-alpha. Reported by atagar, patch by teor.
5636 o Minor bugfixes (hidden service, client):
5637 - Handle the case where the user makes several fast consecutive
5638 requests to the same .onion address. Previously, the first six
5639 requests would each trigger a descriptor fetch, each picking a
5640 directory (there are 6 overall) and the seventh one would fail
5641 because no directories were left, thereby triggering a close on
5642 all current directory connections asking for the hidden service.
5643 The solution here is to not close the connections if we have
5644 pending directory fetches. Fixes bug 15937; bugfix
5647 o Minor bugfixes (hidden service, control port):
5648 - Add the onion address to the HS_DESC event for the UPLOADED action
5649 both on success or failure. It was previously hardcoded with
5650 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
5652 o Minor bugfixes (hidden service, directory):
5653 - Bridges now refuse "rendezvous2" (hidden service descriptor)
5654 publish attempts. Suggested by ticket 18332.
5656 o Minor bugfixes (linux seccomp2 sandbox):
5657 - Allow the setrlimit syscall, and the prlimit and prlimit64
5658 syscalls, which some libc implementations use under the hood.
5659 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
5660 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
5661 enabled and no DNS resolvers configured. This should help TAILS
5662 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
5663 - Fix the sandbox's interoperability with unix domain sockets under
5664 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
5666 o Minor bugfixes (logging):
5667 - When logging information about an unparsable networkstatus vote or
5668 consensus, do not say "vote" when we mean consensus. Fixes bug
5669 18368; bugfix on 0.2.0.8-alpha.
5670 - Scrub service name in "unrecognized service ID" log messages.
5671 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
5672 - Downgrade logs and backtraces about IP versions to info-level.
5673 Only log backtraces once each time tor runs. Assists in diagnosing
5674 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
5675 Christian, patch by teor.
5677 o Minor bugfixes (memory safety):
5678 - Avoid freeing an uninitialized pointer when opening a socket fails
5679 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
5680 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
5682 - Correctly duplicate addresses in get_interface_address6_list().
5683 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
5684 patch by "cypherpunks".
5685 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
5687 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
5688 18672; bugfix on 0.2.5.1-alpha.
5690 o Minor bugfixes (private directory):
5691 - Prevent a race condition when creating private directories. Fixes
5692 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
5693 Patch from jsturgix. Found with Flawfinder.
5695 o Minor bugfixes (test networks, IPv6):
5696 - Allow internal IPv6 addresses in descriptors in test networks.
5697 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
5700 o Minor bugfixes (testing):
5701 - We no longer disable assertions in the unit tests when coverage is
5702 enabled. Instead, we require you to say --disable-asserts-in-tests
5703 to the configure script if you need assertions disabled in the
5704 unit tests (for example, if you want to perform branch coverage).
5705 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
5707 o Minor bugfixes (time parsing):
5708 - Avoid overflow in tor_timegm when parsing dates in and after 2038
5709 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
5710 0.0.2pre14. Patch by teor.
5712 o Minor bugfixes (tor-gencert):
5713 - Correctly handle the case where an authority operator enters a
5714 passphrase but sends an EOF before sending a newline. Fixes bug
5715 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
5717 o Code simplification and refactoring:
5718 - Quote all the string interpolations in configure.ac -- even those
5719 which we are pretty sure can't contain spaces. Closes ticket
5720 17744. Patch from zerosion.
5721 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
5722 inplace, so there's no need to have a separate implementation for
5723 the non-inplace code. Closes ticket 18258. Patch from Malek.
5724 - Simplify return types for some crypto functions that can't
5725 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
5728 - Change build messages to refer to "Fedora" instead of "Fedora
5729 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
5730 Patches from "icanhasaccount" and "cypherpunks".
5733 - We no longer maintain an internal freelist in memarea.c.
5734 Allocators should be good enough to make this code unnecessary,
5735 and it's doubtful that it ever had any performance benefit.
5738 - Fix several warnings from clang's address sanitizer produced in
5740 - Treat backtrace test failures as expected on FreeBSD until we
5741 solve bug 17808. Closes ticket 18204.
5744 Changes in version 0.2.8.1-alpha - 2016-02-04
5745 Tor 0.2.8.1-alpha is the first alpha release in its series. It
5746 includes numerous small features and bugfixes against previous Tor
5747 versions, and numerous small infrastructure improvements. The most
5748 notable features are a set of improvements to the directory subsystem.
5750 o Major features (security, Linux):
5751 - When Tor starts as root on Linux and is told to switch user ID, it
5752 can now retain the capability to bind to low ports. By default,
5753 Tor will do this only when it's switching user ID and some low
5754 ports have been configured. You can change this behavior with the
5755 new option KeepBindCapabilities. Closes ticket 8195.
5757 o Major features (directory system):
5758 - When bootstrapping multiple consensus downloads at a time, use the
5759 first one that starts downloading, and close the rest. This
5760 reduces failures when authorities or fallback directories are slow
5761 or down. Together with the code for feature 15775, this feature
5762 should reduces failures due to fallback churn. Implements ticket
5763 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
5764 "mikeperry" and "teor".
5765 - Include a trial list of 21 default fallback directories, generated
5766 in January 2016, based on an opt-in survey of suitable relays.
5767 Doing this should make clients bootstrap more quickly and reliably,
5768 and reduce the load on the directory authorities. Closes ticket
5769 15775. Patch by "teor".
5770 Candidates identified using an OnionOO script by "weasel", "teor",
5771 "gsathya", and "karsten".
5772 - Previously only relays that explicitly opened a directory port
5773 (DirPort) accepted directory requests from clients. Now all
5774 relays, with and without a DirPort, accept and serve tunneled
5775 directory requests that they receive through their ORPort. You can
5776 disable this behavior using the new DirCache option. Closes
5779 o Major key updates:
5780 - Update the V3 identity key for the dannenberg directory authority:
5781 it was changed on 18 November 2015. Closes task 17906. Patch
5784 o Minor features (security, clock):
5785 - Warn when the system clock appears to move back in time (when the
5786 state file was last written in the future). Tor doesn't know that
5787 consensuses have expired if the clock is in the past. Patch by
5788 "teor". Implements ticket 17188.
5790 o Minor features (security, exit policies):
5791 - ExitPolicyRejectPrivate now rejects more private addresses by
5792 default. Specifically, it now rejects the relay's outbound bind
5793 addresses (if configured), and the relay's configured port
5794 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
5795 0.2.0.11-alpha. Patch by "teor".
5797 o Minor features (security, memory erasure):
5798 - Set the unused entries in a smartlist to NULL. This helped catch
5799 a (harmless) bug, and shouldn't affect performance too much.
5800 Implements ticket 17026.
5801 - Use SecureMemoryWipe() function to securely clean memory on
5802 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
5803 Implements feature 17986.
5804 - Use explicit_bzero or memset_s when present. Previously, we'd use
5805 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
5806 from <logan@hackers.mu> and <selven@hackers.mu>.
5807 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5808 zero size. Check size argument to memwipe() for underflow. Fixes
5809 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5812 o Minor features (security, RNG):
5813 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
5814 positively are not allowed to fail. Previously we depended on
5815 internal details of OpenSSL's behavior. Closes ticket 17686.
5816 - Never use the system entropy output directly for anything besides
5817 seeding the PRNG. When we want to generate important keys, instead
5818 of using system entropy directly, we now hash it with the PRNG
5819 stream. This may help resist certain attacks based on broken OS
5820 entropy implementations. Closes part of ticket 17694.
5821 - Use modern system calls (like getentropy() or getrandom()) to
5822 generate strong entropy on platforms that have them. Closes
5825 o Minor features (accounting):
5826 - Added two modes to the AccountingRule option: One for limiting
5827 only the number of bytes sent ("AccountingRule out"), and one for
5828 limiting only the number of bytes received ("AccountingRule in").
5829 Closes ticket 15989; patch from "unixninja92".
5831 o Minor features (build):
5832 - Since our build process now uses "make distcheck", we no longer
5833 force "make dist" to depend on "make check". Closes ticket 17893;
5834 patch from "cypherpunks."
5835 - Tor now builds successfully with the recent OpenSSL 1.1
5836 development branch, and with the latest LibreSSL. Closes tickets
5837 17549, 17921, and 17984.
5839 o Minor features (controller):
5840 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
5841 tickets 16774 and 17817. Patch by George Tankersley.
5842 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
5843 service descriptor from a service's local hidden service
5844 descriptor cache. Closes ticket 14846.
5845 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
5846 controllers can examine the the reject rules added by
5847 ExitPolicyRejectPrivate. This makes it easier for stem to display
5850 o Minor features (crypto):
5851 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
5853 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
5854 - When allocating a digest state object, allocate no more space than
5855 we actually need. Previously, we would allocate as much space as
5856 the state for the largest algorithm would need. This change saves
5857 up to 672 bytes per circuit. Closes ticket 17796.
5858 - Improve performance when hashing non-multiple of 8 sized buffers,
5859 based on Andrew Moon's public domain SipHash-2-4 implementation.
5860 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
5862 o Minor features (directory downloads):
5863 - Wait for busy authorities and fallback directories to become non-
5864 busy when bootstrapping. (A similar change was made in 6c443e987d
5865 for directory caches chosen from the consensus.) Closes ticket
5866 17864; patch by "teor".
5867 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
5868 directory mirrors. The default is 1; set it to 0 to disable
5869 fallbacks. Implements ticket 17576. Patch by "teor".
5871 o Minor features (geoip):
5872 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
5875 o Minor features (IPv6):
5876 - Add an argument 'ipv6=address:orport' to the DirAuthority and
5877 FallbackDir torrc options, to specify an IPv6 address for an
5878 authority or fallback directory. Add hard-coded ipv6 addresses for
5879 directory authorities that have them. Closes ticket 17327; patch
5880 from Nick Mathewson and "teor".
5881 - Add address policy assume_action support for IPv6 addresses.
5882 - Limit IPv6 mask bits to 128.
5883 - Warn when comparing against an AF_UNSPEC address in a policy, it's
5884 almost always a bug. Closes ticket 17863; patch by "teor".
5885 - Allow users to configure directory authorities and fallback
5886 directory servers with IPv6 addresses and ORPorts. Resolves
5888 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
5889 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
5890 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
5891 17638; bugfix on 0.0.2pre8. Patch by "teor".
5893 o Minor features (logging):
5894 - When logging to syslog, allow a tag to be added to the syslog
5895 identity (the string prepended to every log message). The tag can
5896 be configured with SyslogIdentityTag and defaults to none. Setting
5897 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
5900 o Minor features (portability):
5901 - Use timingsafe_memcmp() where available. Closes ticket 17944;
5902 patch from <logan@hackers.mu>.
5904 o Minor features (relay, address discovery):
5905 - Add a family argument to get_interface_addresses_raw() and
5906 subfunctions to make network interface address interogation more
5907 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
5908 types of interfaces from the operating system. Resolves
5910 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
5911 fails to enumerate interface addresses using the platform-specific
5912 API, have it rely on the UDP socket fallback technique to try and
5913 find out what IP addresses (both IPv4 and IPv6) our machine has.
5914 Resolves ticket 17951.
5916 o Minor features (replay cache):
5917 - The replay cache now uses SHA256 instead of SHA1. Implements
5918 feature 8961. Patch by "teor", issue reported by "rransom".
5920 o Minor features (unix file permissions):
5921 - Defer creation of Unix sockets until after setuid. This avoids
5922 needing CAP_CHOWN and CAP_FOWNER when using systemd's
5923 CapabilityBoundingSet, or chown and fowner when using SELinux.
5924 Implements part of ticket 17562. Patch from Jamie Nguyen.
5925 - If any directory created by Tor is marked as group readable, the
5926 filesystem group is allowed to be either the default GID or the
5927 root user. Allowing root to read the DataDirectory prevents the
5928 need for CAP_READ_SEARCH when using systemd's
5929 CapabilityBoundingSet, or dac_read_search when using SELinux.
5930 Implements part of ticket 17562. Patch from Jamie Nguyen.
5931 - Introduce a new DataDirectoryGroupReadable option. If it is set to
5932 1, the DataDirectory will be made readable by the default GID.
5933 Implements part of ticket 17562. Patch from Jamie Nguyen.
5935 o Minor bugfixes (accounting):
5936 - The max bandwidth when using 'AccountRule sum' is now correctly
5937 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
5940 o Minor bugfixes (code correctness):
5941 - When closing an entry connection, generate a warning if we should
5942 have sent an end cell for it but we haven't. Fixes bug 17876;
5943 bugfix on 0.2.3.2-alpha.
5944 - Assert that allocated memory held by the reputation code is freed
5945 according to its internal counters. Fixes bug 17753; bugfix
5947 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
5950 o Minor bugfixes (compilation):
5951 - Mark all object files that include micro-revision.i as depending
5952 on it, so as to make parallel builds more reliable. Fixes bug
5953 17826; bugfix on 0.2.5.1-alpha.
5954 - Don't try to use the pthread_condattr_setclock() function unless
5955 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
5956 17819; bugfix on 0.2.6.3-alpha.
5957 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
5959 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
5960 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
5961 - Fix search for libevent libraries on OpenBSD (and other systems
5962 that install libevent 1 and libevent 2 in parallel). Fixes bug
5963 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
5964 - Isolate environment variables meant for tests from the rest of the
5965 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
5966 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
5968 - Remove config.log only from make distclean, not from make clean.
5969 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
5971 o Minor bugfixes (crypto):
5972 - Check the return value of HMAC() and assert on failure. Fixes bug
5973 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
5975 o Minor bugfixes (fallback directories):
5976 - Mark fallbacks as "too busy" when they return a 503 response,
5977 rather than just marking authorities. Fixes bug 17572; bugfix on
5978 0.2.4.7-alpha. Patch by "teor".
5980 o Minor bugfixes (IPv6):
5981 - Update the limits in max_dl_per_request for IPv6 address length.
5982 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
5984 o Minor bugfixes (linux seccomp2 sandbox):
5985 - Fix a crash when using offline master ed25519 keys with the Linux
5986 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
5988 o Minor bugfixes (logging):
5989 - In log messages that include a function name, use __FUNCTION__
5990 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
5991 with clang __PRETTY_FUNCTION__ has extra information we don't
5992 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
5994 - Remove needless quotes from a log message about unparseable
5995 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
5997 o Minor bugfixes (portability):
5998 - Remove an #endif from configure.ac so that we correctly detect the
5999 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
6002 o Minor bugfixes (relays):
6003 - Check that both the ORPort and DirPort (if present) are reachable
6004 before publishing a relay descriptor. Otherwise, relays publish a
6005 descriptor with DirPort 0 when the DirPort reachability test takes
6006 longer than the ORPort reachability test. Fixes bug 18050; bugfix
6007 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
6009 o Minor bugfixes (relays, hidden services):
6010 - Refuse connection requests to private OR addresses unless
6011 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
6012 then refuse to send any cells to a private address. Fixes bugs
6013 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
6015 o Minor bugfixes (safe logging):
6016 - When logging a malformed hostname received through socks4, scrub
6017 it if SafeLogging says we should. Fixes bug 17419; bugfix
6020 o Minor bugfixes (statistics code):
6021 - Consistently check for overflow in round_*_to_next_multiple_of
6022 functions, and add unit tests with additional and maximal values.
6023 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
6024 - Handle edge cases in the laplace functions: avoid division by
6025 zero, avoid taking the log of zero, and silence clang type
6026 conversion warnings using round and trunc. Add unit tests for edge
6027 cases with maximal values. Fixes part of bug 13192; bugfix
6030 o Minor bugfixes (testing):
6031 - The test for log_heartbeat was incorrectly failing in timezones
6032 with non-integer offsets. Instead of comparing the end of the time
6033 string against a constant, compare it to the output of
6034 format_local_iso_time when given the correct input. Fixes bug
6035 18039; bugfix on 0.2.5.4-alpha.
6036 - Make unit tests pass on IPv6-only systems, and systems without
6037 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
6038 bugfix on 0.2.7.3-rc. Patch by "teor".
6039 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
6041 - Check the full results of SHA256 and SHA512 digests in the unit
6042 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
6044 o Code simplification and refactoring:
6045 - Move logging of redundant policy entries in
6046 policies_parse_exit_policy_internal into its own function. Closes
6047 ticket 17608; patch from "juce".
6048 - Extract the more complicated parts of circuit_mark_for_close()
6049 into a new function that we run periodically before circuits are
6050 freed. This change removes more than half of the functions
6051 currently in the "blob". Closes ticket 17218.
6052 - Clean up a little duplicated code in
6053 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
6055 - Decouple the list of streams waiting to be attached to circuits
6056 from the overall connection list. This change makes it possible to
6057 attach streams quickly while simplifying Tor's callgraph and
6058 avoiding O(N) scans of the entire connection list. Closes
6060 - When a direct directory request fails immediately on launch,
6061 instead of relaunching that request from inside the code that
6062 launches it, instead mark the connection for teardown. This change
6063 simplifies Tor's callback and prevents the directory-request
6064 launching code from invoking itself recursively. Closes
6066 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
6067 use them. Closes ticket 17926.
6070 - Add a description of the correct use of the '--keygen' command-
6071 line option. Closes ticket 17583; based on text by 's7r'.
6072 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
6073 - Explain actual minima for BandwidthRate. Closes ticket 16382.
6074 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
6075 - Mention torspec URL in the manpage and point the reader to it
6076 whenever we mention a document that belongs in torspce. Fixes
6080 - Remove client-side support for connecting to Tor relays running
6081 versions of Tor before 0.2.3.6-alpha. These relays didn't support
6082 the v3 TLS handshake protocol, and are no longer allowed on the
6083 Tor network. Implements the client side of ticket 11150. Based on
6084 patches by Tom van der Woerdt.
6087 - Add unit tests to check for common RNG failure modes, such as
6088 returning all zeroes, identical values, or incrementing values
6089 (OpenSSL's rand_predictable feature). Patch by "teor".
6090 - Log more information when the backtrace tests fail. Closes ticket
6091 17892. Patch from "cypherpunks."
6092 - Always test both ed25519 backends, so that we can be sure that our
6093 batch-open replacement code works. Part of ticket 16794.
6094 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
6095 portion of ticket 16831.
6096 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
6097 util_format.c, directory.c, and options_validate.c. Closes tickets
6098 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
6100 - Unit tests for directory_handle_command_get. Closes ticket 17004.
6101 Patch from Reinaldo de Souza Jr.
6104 Changes in version 0.2.7.6 - 2015-12-10
6105 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
6106 well as a minor bug in hidden service reliability.
6108 o Major bugfixes (guard selection):
6109 - Actually look at the Guard flag when selecting a new directory
6110 guard. When we implemented the directory guard design, we
6111 accidentally started treating all relays as if they have the Guard
6112 flag during guard selection, leading to weaker anonymity and worse
6113 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
6116 o Minor features (geoip):
6117 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
6120 o Minor bugfixes (compilation):
6121 - When checking for net/pfvar.h, include netinet/in.h if possible.
6122 This fixes transparent proxy detection on OpenBSD. Fixes bug
6123 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
6124 - Fix a compilation warning with Clang 3.6: Do not check the
6125 presence of an address which can never be NULL. Fixes bug 17781.
6127 o Minor bugfixes (correctness):
6128 - When displaying an IPv6 exit policy, include the mask bits
6129 correctly even when the number is greater than 31. Fixes bug
6130 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
6131 - The wrong list was used when looking up expired intro points in a
6132 rend service object, causing what we think could be reachability
6133 issues for hidden services, and triggering a BUG log. Fixes bug
6134 16702; bugfix on 0.2.7.2-alpha.
6135 - Fix undefined behavior in the tor_cert_checksig function. Fixes
6136 bug 17722; bugfix on 0.2.7.2-alpha.
6139 Changes in version 0.2.7.5 - 2015-11-20
6140 The Tor 0.2.7 release series is dedicated to the memory of Tor user
6141 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
6142 tirelessly to advocate human rights regardless of national borders,
6143 and oppose the encroachments of mass surveillance. He opposed national
6144 exceptionalism, he brought clarity to legal and policy debates, he
6145 understood and predicted the impact of mass surveillance on the world,
6146 and he laid the groundwork for resisting it. While serving on the Tor
6147 Project's board of directors, he brought us his uncompromising focus
6148 on technical excellence in the service of humankind. Caspar was an
6149 inimitable force for good and a wonderful friend. He was kind,
6150 humorous, generous, gallant, and believed we should protect one
6151 another without exception. We honor him here for his ideals, his
6152 efforts, and his accomplishments. Please honor his memory with works
6153 that would make him proud.
6155 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
6157 The 0.2.7 series adds a more secure identity key type for relays,
6158 improves cryptography performance, resolves several longstanding
6159 hidden-service performance issues, improves controller support for
6160 hidden services, and includes small bugfixes and performance
6161 improvements throughout the program. This release series also includes
6162 more tests than before, and significant simplifications to which parts
6163 of Tor invoke which others.
6165 (This release contains no code changes since 0.2.7.4-rc.)
6168 Changes in version 0.2.7.4-rc - 2015-10-21
6169 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
6170 fixes some important memory leaks, and a scary-looking (but mostly
6171 harmless in practice) invalid-read bug. It also has a few small
6172 bugfixes, notably fixes for compilation and portability on different
6173 platforms. If no further significant bounds are found, the next
6174 release will the the official stable release.
6176 o Major bugfixes (security, correctness):
6177 - Fix an error that could cause us to read 4 bytes before the
6178 beginning of an openssl string. This bug could be used to cause
6179 Tor to crash on systems with unusual malloc implementations, or
6180 systems with unusual hardening installed. Fixes bug 17404; bugfix
6183 o Major bugfixes (correctness):
6184 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
6185 bug 17401; bugfix on 0.2.7.3-rc.
6187 o Major bugfixes (memory leaks):
6188 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
6189 17398; bugfix on 0.2.6.1-alpha.
6190 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
6191 17402; bugfix on 0.2.7.3-rc.
6192 - Fix a memory leak when reading an expired signing key from disk.
6193 Fixes bug 17403; bugfix on 0.2.7.2-rc.
6195 o Minor features (geoIP):
6196 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
6199 o Minor bugfixes (compilation):
6200 - Repair compilation with the most recent (unreleased, alpha)
6201 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
6202 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
6203 17251; bugfix on 0.2.7.2-alpha.
6204 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
6205 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
6207 o Minor bugfixes (portability):
6208 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
6209 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
6212 o Minor bugfixes (sandbox):
6213 - Add the "hidserv-stats" filename to our sandbox filter for the
6214 HiddenServiceStatistics option to work properly. Fixes bug 17354;
6215 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
6217 o Minor bugfixes (testing):
6218 - Add unit tests for get_interface_address* failure cases. Fixes bug
6219 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
6220 - Fix breakage when running 'make check' with BSD make. Fixes bug
6221 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
6222 - Make the get_ifaddrs_* unit tests more tolerant of different
6223 network configurations. (Don't assume every test box has an IPv4
6224 address, and don't assume every test box has a non-localhost
6225 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
6226 - Skip backtrace tests when backtrace support is not compiled in.
6227 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
6231 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
6232 - Note that HiddenServicePorts can take a unix domain socket. Closes
6236 Changes in version 0.2.7.3-rc - 2015-09-25
6237 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
6238 contains numerous usability fixes for Ed25519 keys, safeguards against
6239 several misconfiguration problems, significant simplifications to
6240 Tor's callgraph, and numerous bugfixes and small features.
6242 This is the most tested release of Tor to date. The unit tests cover
6243 39.40% of the code, and the integration tests (accessible with "make
6244 test-full-online", requiring stem and chutney and a network
6245 connection) raise the coverage to 64.49%.
6247 o Major features (security, hidden services):
6248 - Hidden services, if using the EntryNodes option, are required to
6249 use more than one EntryNode, in order to avoid a guard discovery
6250 attack. (This would only affect people who had configured hidden
6251 services and manually specified the EntryNodes option with a
6252 single entry-node. The impact was that it would be easy to
6253 remotely identify the guard node used by such a hidden service.
6254 See ticket for more information.) Fixes ticket 14917.
6256 o Major features (Ed25519 keys, keypinning):
6257 - The key-pinning option on directory authorities is now advisory-
6258 only by default. In a future version, or when the AuthDirPinKeys
6259 option is set, pins are enforced again. Disabling key-pinning
6260 seemed like a good idea so that we can survive the fallout of any
6261 usability problems associated with Ed25519 keys. Closes
6264 o Major features (Ed25519 performance):
6265 - Improve the speed of Ed25519 operations and Curve25519 keypair
6266 generation when built targeting 32 bit x86 platforms with SSE2
6267 available. Implements ticket 16535.
6268 - Improve the runtime speed of Ed25519 signature verification by
6269 using Ed25519-donna's batch verification support. Implements
6272 o Major features (performance testing):
6273 - The test-network.sh script now supports performance testing.
6274 Requires corresponding chutney performance testing changes. Patch
6275 by "teor". Closes ticket 14175.
6277 o Major features (relay, Ed25519):
6278 - Significant usability improvements for Ed25519 key management. Log
6279 messages are better, and the code can recover from far more
6280 failure conditions. Thanks to "s7r" for reporting and diagnosing
6282 - Add a new OfflineMasterKey option to tell Tor never to try loading
6283 or generating a secret Ed25519 identity key. You can use this in
6284 combination with tor --keygen to manage offline and/or encrypted
6285 Ed25519 keys. Implements ticket 16944.
6286 - Add a --newpass option to allow changing or removing the
6287 passphrase of an encrypted key with tor --keygen. Implements part
6289 - On receiving a HUP signal, check to see whether the Ed25519
6290 signing key has changed, and reload it if so. Closes ticket 16790.
6292 o Major bugfixes (relay, Ed25519):
6293 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
6294 0.2.7.2-alpha. Reported by "s7r".
6295 - Improve handling of expired signing keys with offline master keys.
6296 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
6298 o Minor features (client-side privacy):
6299 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
6300 lifespan when IsolateSOCKSAuth and streams with SOCKS
6301 authentication are attached to the circuit. This allows
6302 applications like TorBrowser to manage circuit lifetime on their
6303 own. Implements feature 15482.
6304 - When logging malformed hostnames from SOCKS5 requests, respect
6305 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
6307 o Minor features (compilation):
6308 - Give a warning as early as possible when trying to build with an
6309 unsupported OpenSSL version. Closes ticket 16901.
6310 - Fail during configure if we're trying to build against an OpenSSL
6311 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
6312 which started requiring ECC.
6314 o Minor features (geoip):
6315 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
6318 o Minor features (hidden services):
6319 - Relays need to have the Fast flag to get the HSDir flag. As this
6320 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
6321 drop. This change should make some attacks against the hidden
6322 service directory system harder. Fixes ticket 15963.
6323 - Turn on hidden service statistics collection by setting the torrc
6324 option HiddenServiceStatistics to "1" by default. (This keeps
6325 track only of the fraction of traffic used by hidden services, and
6326 the total number of hidden services in existence.) Closes
6328 - Client now uses an introduction point failure cache to know when
6329 to fetch or keep a descriptor in their cache. Previously, failures
6330 were recorded implicitly, but not explicitly remembered. Closes
6333 o Minor features (testing, authorities, documentation):
6334 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
6335 explicitly manage consensus flags in testing networks. Patch by
6336 "robgjansen", modified by "teor". Implements part of ticket 14882.
6338 o Minor bugfixes (security, exit policies):
6339 - ExitPolicyRejectPrivate now also rejects the relay's published
6340 IPv6 address (if any), and any publicly routable IPv4 or IPv6
6341 addresses on any local interfaces. ticket 17027. Patch by "teor".
6342 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
6344 o Minor bug fixes (torrc exit policies):
6345 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
6346 produce IPv6 wildcard addresses. Previously they would produce
6347 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
6348 of bug 16069; bugfix on 0.2.4.7-alpha.
6349 - When parsing torrc ExitPolicies, we now warn for a number of cases
6350 where the user's intent is likely to differ from Tor's actual
6351 behavior. These include: using an IPv4 address with an accept6 or
6352 reject6 line; using "private" on an accept6 or reject6 line; and
6353 including any ExitPolicy lines after accept *:* or reject *:*.
6354 Related to ticket 16069.
6355 - When parsing torrc ExitPolicies, we now issue an info-level
6356 message when expanding an "accept/reject *" line to include both
6357 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
6358 - In each instance above, usage advice is provided to avoid the
6359 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
6360 16069; bugfix on 0.2.4.7-alpha.
6362 o Minor bugfixes (authority):
6363 - Don't assign "HSDir" to a router if it isn't Valid and Running.
6364 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
6365 - Downgrade log messages about Ed25519 key issues if they are in old
6366 cached router descriptors. Fixes part of bug 16286; bugfix
6368 - When we find an Ed25519 key issue in a cached descriptor, stop
6369 saying the descriptor was just "uploaded". Fixes another part of
6370 bug 16286; bugfix on 0.2.7.2-alpha.
6372 o Minor bugfixes (control port):
6373 - Repair a warning and a spurious result when getting the maximum
6374 number of file descriptors from the controller. Fixes bug 16697;
6375 bugfix on 0.2.7.2-alpha.
6377 o Minor bugfixes (correctness):
6378 - When calling channel_free_list(), avoid calling smartlist_remove()
6379 while inside a FOREACH loop. This partially reverts commit
6380 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
6381 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
6383 o Minor bugfixes (documentation):
6384 - Advise users on how to configure separate IPv4 and IPv6 exit
6385 policies in the manpage and sample torrcs. Related to ticket 16069.
6386 - Fix the usage message of tor-resolve(1) so that it no longer lists
6387 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
6388 - Fix an error in the manual page and comments for
6389 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
6390 required "ORPort connectivity". While this is true, it is in no
6391 way unique to the HSDir flag. Of all the flags, only HSDirs need a
6392 DirPort configured in order for the authorities to assign that
6393 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
6396 o Minor bugfixes (Ed25519):
6397 - Fix a memory leak when reading router descriptors with expired
6398 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
6400 o Minor bugfixes (linux seccomp2 sandbox):
6401 - Allow bridge authorities to run correctly under the seccomp2
6402 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
6403 - Allow routers with ed25519 keys to run correctly under the
6404 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
6406 o Minor bugfixes (open file limit):
6407 - Fix set_max_file_descriptors() to set by default the max open file
6408 limit to the current limit when setrlimit() fails. Fixes bug
6409 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
6411 o Minor bugfixes (portability):
6412 - Try harder to normalize the exit status of the Tor process to the
6413 standard-provided range. Fixes bug 16975; bugfix on every version
6415 - Check correctly for Windows socket errors in the workqueue
6416 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
6417 - Fix the behavior of crypto_rand_time_range() when told to consider
6418 times before 1970. (These times were possible when running in a
6419 simulated network environment where time()'s output starts at
6420 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
6421 - Restore correct operation of TLS client-cipher detection on
6422 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
6424 o Minor bugfixes (relay):
6425 - Ensure that worker threads actually exit when a fatal error or
6426 shutdown is indicated. This fix doesn't currently affect the
6427 behavior of Tor, because Tor workers never indicates fatal error
6428 or shutdown except in the unit tests. Fixes bug 16868; bugfix
6430 - Unblock threads before releasing the work queue mutex to ensure
6431 predictable scheduling behavior. Fixes bug 16644; bugfix
6434 o Code simplification and refactoring:
6435 - Change the function that's called when we need to retry all
6436 downloads so that it only reschedules the downloads to happen
6437 immediately, rather than launching them all at once itself. This
6438 further simplifies Tor's callgraph.
6439 - Move some format-parsing functions out of crypto.c and
6440 crypto_curve25519.c into crypto_format.c and/or util_format.c.
6441 - Move the client-only parts of init_keys() into a separate
6442 function. Closes ticket 16763.
6443 - Simplify the microdesc_free() implementation so that it no longer
6444 appears (to code analysis tools) to potentially invoke a huge
6445 suite of other microdesc functions.
6446 - Simply the control graph further by deferring the inner body of
6447 directory_all_unreachable() into a callback. Closes ticket 16762.
6448 - Treat the loss of an owning controller as equivalent to a SIGTERM
6449 signal. This removes a tiny amount of duplicated code, and
6450 simplifies our callgraph. Closes ticket 16788.
6451 - When generating an event to send to the controller, we no longer
6452 put the event over the network immediately. Instead, we queue
6453 these events, and use a Libevent callback to deliver them. This
6454 change simplifies Tor's callgraph by reducing the number of
6455 functions from which all other Tor functions are reachable. Closes
6457 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
6458 that try to scan or compile every file on Unix won't decide that
6460 - Remove the unused "nulterminate" argument from buf_pullup().
6463 - Recommend a 40 GB example AccountingMax in torrc.sample rather
6464 than a 4 GB max. Closes ticket 16742.
6465 - Include the TUNING document in our source tarball. It is referred
6466 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
6470 - The internal pure-C tor-fw-helper tool is now removed from the Tor
6471 distribution, in favor of the pure-Go clone available from
6472 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
6473 used by the C tor-fw-helper are not, in our opinion, very
6474 confidence- inspiring in their secure-programming techniques.
6475 Closes ticket 13338.
6476 - Remove the code that would try to aggressively flush controller
6477 connections while writing to them. This code was introduced in
6478 0.1.2.7-alpha, in order to keep output buffers from exceeding
6479 their limits. But there is no longer a maximum output buffer size,
6480 and flushing data in this way caused some undesirable recursions
6481 in our call graph. Closes ticket 16480.
6484 - Make "bridges+hs" the default test network. This tests almost all
6485 tor functionality during make test-network, while allowing tests
6486 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
6487 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
6488 (chutney). Patches by "teor".
6489 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
6490 by-side in the same parent directory. Closes ticket 16903. Patch
6492 - Use environment variables rather than autoconf substitutions to
6493 send variables from the build system to the test scripts. This
6494 change should be easier to maintain, and cause 'make distcheck' to
6495 work better than before. Fixes bug 17148.
6496 - Add a new set of callgraph analysis scripts that use clang to
6497 produce a list of which Tor functions are reachable from which
6498 other Tor functions. We're planning to use these to help simplify
6499 our code structure by identifying illogical dependencies.
6500 - Add new 'test-full' and 'test-full-online' targets to run all
6501 tests, including integration tests with stem and chutney.
6502 - Make the test-workqueue test work on Windows by initializing the
6503 network before we begin.
6504 - New make target (make test-network-all) to run multiple applicable
6505 chutney test cases. Patch from Teor; closes 16953.
6506 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
6507 functions in dns.c. Implements a portion of ticket 16831.
6508 - When building Tor with testing coverage enabled, run Chutney tests
6509 (if any) using the 'tor-cov' coverage binary.
6510 - When running test-network or test-stem, check for the absence of
6511 stem/chutney before doing any build operations.
6514 Changes in version 0.2.7.2-alpha - 2015-07-27
6515 This, the second alpha in the Tor 0.2.7 series, has a number of new
6516 features, including a way to manually pick the number of introduction
6517 points for hidden services, and the much stronger Ed25519 signing key
6518 algorithm for regular Tor relays (including support for encrypted
6519 offline identity keys in the new algorithm).
6521 Support for Ed25519 on relays is currently limited to signing router
6522 descriptors; later alphas in this series will extend Ed25519 key
6523 support to more parts of the Tor protocol.
6525 o Major features (Ed25519 identity keys, Proposal 220):
6526 - All relays now maintain a stronger identity key, using the Ed25519
6527 elliptic curve signature format. This master key is designed so
6528 that it can be kept offline. Relays also generate an online
6529 signing key, and a set of other Ed25519 keys and certificates.
6530 These are all automatically regenerated and rotated as needed.
6531 Implements part of ticket 12498.
6532 - Directory authorities now vote on Ed25519 identity keys along with
6533 RSA1024 keys. Implements part of ticket 12498.
6534 - Directory authorities track which Ed25519 identity keys have been
6535 used with which RSA1024 identity keys, and do not allow them to
6536 vary freely. Implements part of ticket 12498.
6537 - Microdescriptors now include Ed25519 identity keys. Implements
6538 part of ticket 12498.
6539 - Add support for offline encrypted Ed25519 master keys. To use this
6540 feature on your tor relay, run "tor --keygen" to make a new master
6541 key (or to make a new signing key if you already have a master
6542 key). Closes ticket 13642.
6544 o Major features (Hidden services):
6545 - Add the torrc option HiddenServiceNumIntroductionPoints, to
6546 specify a fixed number of introduction points. Its maximum value
6547 is 10 and default is 3. Using this option can increase a hidden
6548 service's reliability under load, at the cost of making it more
6549 visible that the hidden service is facing extra load. Closes
6551 - Remove the adaptive algorithm for choosing the number of
6552 introduction points, which used to change the number of
6553 introduction points (poorly) depending on the number of
6554 connections the HS sees. Closes ticket 4862.
6556 o Major features (onion key cross-certification):
6557 - Relay descriptors now include signatures of their own identity
6558 keys, made using the TAP and ntor onion keys. These signatures
6559 allow relays to prove ownership of their own onion keys. Because
6560 of this change, microdescriptors will no longer need to include
6561 RSA identity keys. Implements proposal 228; closes ticket 12499.
6563 o Major features (performance):
6564 - Improve the runtime speed of Ed25519 operations by using the
6565 public-domain Ed25519-donna by Andrew M. ("floodyberry").
6566 Implements ticket 16467.
6567 - Improve the runtime speed of the ntor handshake by using an
6568 optimized curve25519 basepoint scalarmult implementation from the
6569 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
6570 ideas by Adam Langley. Implements ticket 9663.
6572 o Major bugfixes (client-side privacy, also in 0.2.6.9):
6573 - Properly separate out each SOCKSPort when applying stream
6574 isolation. The error occurred because each port's session group
6575 was being overwritten by a default value when the listener
6576 connection was initialized. Fixes bug 16247; bugfix on
6577 0.2.6.3-alpha. Patch by "jojelino".
6579 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
6580 - Stop refusing to store updated hidden service descriptors on a
6581 client. This reverts commit 9407040c59218 (which indeed fixed bug
6582 14219, but introduced a major hidden service reachability
6583 regression detailed in bug 16381). This is a temporary fix since
6584 we can live with the minor issue in bug 14219 (it just results in
6585 some load on the network) but the regression of 16381 is too much
6586 of a setback. First-round fix for bug 16381; bugfix
6589 o Major bugfixes (hidden services):
6590 - When cannibalizing a circuit for an introduction point, always
6591 extend to the chosen exit node (creating a 4 hop circuit).
6592 Previously Tor would use the current circuit exit node, which
6593 changed the original choice of introduction point, and could cause
6594 the hidden service to skip excluded introduction points or
6595 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
6598 o Major bugfixes (open file limit):
6599 - The open file limit wasn't checked before calling
6600 tor_accept_socket_nonblocking(), which would make Tor exceed the
6601 limit. Now, before opening a new socket, Tor validates the open
6602 file limit just before, and if the max has been reached, return an
6603 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
6605 o Major bugfixes (stability, also in 0.2.6.10):
6606 - Stop crashing with an assertion failure when parsing certain kinds
6607 of malformed or truncated microdescriptors. Fixes bug 16400;
6608 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
6609 by "cypherpunks_backup".
6610 - Stop random client-side assertion failures that could occur when
6611 connecting to a busy hidden service, or connecting to a hidden
6612 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
6615 o Minor features (directory authorities, security, also in 0.2.6.9):
6616 - The HSDir flag given by authorities now requires the Stable flag.
6617 For the current network, this results in going from 2887 to 2806
6618 HSDirs. Also, it makes it harder for an attacker to launch a sybil
6619 attack by raising the effort for a relay to become Stable to
6620 require at the very least 7 days, while maintaining the 96 hours
6621 uptime requirement for HSDir. Implements ticket 8243.
6623 o Minor features (client):
6624 - Relax the validation of hostnames in SOCKS5 requests, allowing the
6625 character '_' to appear, in order to cope with domains observed in
6626 the wild that are serving non-RFC compliant records. Resolves
6628 - Relax the validation done to hostnames in SOCKS5 requests, and
6629 allow a single trailing '.' to cope with clients that pass FQDNs
6630 using that syntax to explicitly indicate that the domain name is
6631 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
6632 - Add GroupWritable and WorldWritable options to unix-socket based
6633 SocksPort and ControlPort options. These options apply to a single
6634 socket, and override {Control,Socks}SocketsGroupWritable. Closes
6637 o Minor features (control protocol):
6638 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
6639 the control protocol. Resolves ticket 15358.
6641 o Minor features (directory authorities):
6642 - Directory authorities no longer vote against the "Fast", "Stable",
6643 and "HSDir" flags just because they were going to vote against
6644 "Running": if the consensus turns out to be that the router was
6645 running, then the authority's vote should count. Patch from Peter
6646 Retzlaff; closes issue 8712.
6648 o Minor features (geoip, also in 0.2.6.10):
6649 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
6650 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
6652 o Minor features (hidden services):
6653 - Add the new options "HiddenServiceMaxStreams" and
6654 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
6655 limit the maximum number of simultaneous streams per circuit, and
6656 optionally tear down the circuit when the limit is exceeded. Part
6659 o Minor features (portability):
6660 - Use C99 variadic macros when the compiler is not GCC. This avoids
6661 failing compilations on MSVC, and fixes a log-file-based race
6662 condition in our old workarounds. Original patch from Gisle Vanem.
6664 o Minor bugfixes (compilation, also in 0.2.6.9):
6665 - Build with --enable-systemd correctly when libsystemd is
6666 installed, but systemd is not. Fixes bug 16164; bugfix on
6667 0.2.6.3-alpha. Patch from Peter Palfrader.
6669 o Minor bugfixes (controller):
6670 - Add the descriptor ID in each HS_DESC control event. It was
6671 missing, but specified in control-spec.txt. Fixes bug 15881;
6672 bugfix on 0.2.5.2-alpha.
6674 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
6675 - Check for failures from crypto_early_init, and refuse to continue.
6676 A previous typo meant that we could keep going with an
6677 uninitialized crypto library, and would have OpenSSL initialize
6678 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
6679 when implementing ticket 4900. Patch by "teor".
6681 o Minor bugfixes (hidden services):
6682 - Fix a crash when reloading configuration while at least one
6683 configured and one ephemeral hidden service exists. Fixes bug
6684 16060; bugfix on 0.2.7.1-alpha.
6685 - Avoid crashing with a double-free bug when we create an ephemeral
6686 hidden service but adding it fails for some reason. Fixes bug
6687 16228; bugfix on 0.2.7.1-alpha.
6689 o Minor bugfixes (Linux seccomp2 sandbox):
6690 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
6691 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
6693 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
6694 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
6695 these when eventfd2() support is missing. Fixes bug 16363; bugfix
6696 on 0.2.6.3-alpha. Patch from "teor".
6698 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
6699 - Fix sandboxing to work when running as a relay, by allowing the
6700 renaming of secret_id_key, and allowing the eventfd2 and futex
6701 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
6703 - Allow systemd connections to work with the Linux seccomp2 sandbox
6704 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
6707 o Minor bugfixes (relay):
6708 - Fix a rarely-encountered memory leak when failing to initialize
6709 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
6712 o Minor bugfixes (systemd):
6713 - Fix an accidental formatting error that broke the systemd
6714 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
6715 - Tor's systemd unit file no longer contains extraneous spaces.
6716 These spaces would sometimes confuse tools like deb-systemd-
6717 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
6719 o Minor bugfixes (tests):
6720 - Use the configured Python executable when running test-stem-full.
6721 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
6723 o Minor bugfixes (tests, also in 0.2.6.9):
6724 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
6725 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
6727 o Minor bugfixes (threads, comments):
6728 - Always initialize return value in compute_desc_id in rendcommon.c
6729 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
6730 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
6731 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
6732 - Remove undefined directive-in-macro in test_util_writepid clang
6733 3.7 complains that using a preprocessor directive inside a macro
6734 invocation in test_util_writepid in test_util.c is undefined.
6735 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
6737 o Code simplification and refactoring:
6738 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
6739 to ensure they remain consistent and visible everywhere.
6740 - Remove some vestigial workarounds for the MSVC6 compiler. We
6741 haven't supported that in ages.
6742 - The link authentication code has been refactored for better
6743 testability and reliability. It now uses code generated with the
6744 "trunnel" binary encoding generator, to reduce the risk of bugs
6745 due to programmer error. Done as part of ticket 12498.
6748 - Include a specific and (hopefully) accurate documentation of the
6749 torrc file's meta-format in doc/torrc_format.txt. This is mainly
6750 of interest to people writing programs to parse or generate torrc
6751 files. This document is not a commitment to long-term
6752 compatibility; some aspects of the current format are a bit
6753 ridiculous. Closes ticket 2325.
6756 - Tor no longer supports copies of OpenSSL that are missing support
6757 for Elliptic Curve Cryptography. (We began using ECC when
6758 available in 0.2.4.8-alpha, for more safe and efficient key
6759 negotiation.) In particular, support for at least one of P256 or
6760 P224 is now required, with manual configuration needed if only
6761 P224 is available. Resolves ticket 16140.
6762 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
6763 on an operating system that has not upgraded to OpenSSL 1.0 or
6764 later, and you compile Tor from source, you will need to install a
6765 more recent OpenSSL to link Tor against.) These versions of
6766 OpenSSL are still supported by the OpenSSL, but the numerous
6767 cryptographic improvements in later OpenSSL releases makes them a
6768 clear choice. Resolves ticket 16034.
6769 - Remove the HidServDirectoryV2 option. Now all relays offer to
6770 store hidden service descriptors. Related to 16543.
6771 - Remove the VoteOnHidServDirectoriesV2 option, since all
6772 authorities have long set it to 1. Closes ticket 16543.
6775 - Document use of coverity, clang static analyzer, and clang dynamic
6776 undefined behavior and address sanitizers in doc/HACKING. Include
6777 detailed usage instructions in the blacklist. Patch by "teor".
6778 Closes ticket 15817.
6779 - The link authentication protocol code now has extensive tests.
6780 - The relay descriptor signature testing code now has
6782 - The test_workqueue program now runs faster, and is enabled by
6783 default as a part of "make check".
6784 - Now that OpenSSL has its own scrypt implementation, add an unit
6785 test that checks for interoperability between libscrypt_scrypt()
6786 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
6787 and rely on EVP_PBE_scrypt() whenever possible. Resolves
6791 Changes in version 0.2.6.10 - 2015-07-12
6792 Tor version 0.2.6.10 fixes some significant stability and hidden
6793 service client bugs, bulletproofs the cryptography init process, and
6794 fixes a bug when using the sandbox code with some older versions of
6795 Linux. Everyone running an older version, especially an older version
6796 of 0.2.6, should upgrade.
6798 o Major bugfixes (hidden service clients, stability):
6799 - Stop refusing to store updated hidden service descriptors on a
6800 client. This reverts commit 9407040c59218 (which indeed fixed bug
6801 14219, but introduced a major hidden service reachability
6802 regression detailed in bug 16381). This is a temporary fix since
6803 we can live with the minor issue in bug 14219 (it just results in
6804 some load on the network) but the regression of 16381 is too much
6805 of a setback. First-round fix for bug 16381; bugfix
6808 o Major bugfixes (stability):
6809 - Stop crashing with an assertion failure when parsing certain kinds
6810 of malformed or truncated microdescriptors. Fixes bug 16400;
6811 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
6812 by "cypherpunks_backup".
6813 - Stop random client-side assertion failures that could occur when
6814 connecting to a busy hidden service, or connecting to a hidden
6815 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
6818 o Minor features (geoip):
6819 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
6820 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
6822 o Minor bugfixes (crypto error-handling):
6823 - Check for failures from crypto_early_init, and refuse to continue.
6824 A previous typo meant that we could keep going with an
6825 uninitialized crypto library, and would have OpenSSL initialize
6826 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
6827 when implementing ticket 4900. Patch by "teor".
6829 o Minor bugfixes (Linux seccomp2 sandbox):
6830 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
6831 these when eventfd2() support is missing. Fixes bug 16363; bugfix
6832 on 0.2.6.3-alpha. Patch from "teor".
6835 Changes in version 0.2.6.9 - 2015-06-11
6836 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
6837 requirements for receiving an HSDir flag, and addresses some other small
6838 bugs in the systemd and sandbox code. Clients using circuit isolation
6839 should upgrade; all directory authorities should upgrade.
6841 o Major bugfixes (client-side privacy):
6842 - Properly separate out each SOCKSPort when applying stream
6843 isolation. The error occurred because each port's session group was
6844 being overwritten by a default value when the listener connection
6845 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
6848 o Minor feature (directory authorities, security):
6849 - The HSDir flag given by authorities now requires the Stable flag.
6850 For the current network, this results in going from 2887 to 2806
6851 HSDirs. Also, it makes it harder for an attacker to launch a sybil
6852 attack by raising the effort for a relay to become Stable which
6853 takes at the very least 7 days to do so and by keeping the 96
6854 hours uptime requirement for HSDir. Implements ticket 8243.
6856 o Minor bugfixes (compilation):
6857 - Build with --enable-systemd correctly when libsystemd is
6858 installed, but systemd is not. Fixes bug 16164; bugfix on
6859 0.2.6.3-alpha. Patch from Peter Palfrader.
6861 o Minor bugfixes (Linux seccomp2 sandbox):
6862 - Fix sandboxing to work when running as a relaymby renaming of
6863 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
6864 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
6865 - Allow systemd connections to work with the Linux seccomp2 sandbox
6866 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
6869 o Minor bugfixes (tests):
6870 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
6871 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
6874 Changes in version 0.2.6.8 - 2015-05-21
6875 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
6876 fixes an authority-side bug in assigning the HSDir flag. All directory
6877 authorities should upgrade.
6879 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
6880 - Revert commit that made directory authorities assign the HSDir
6881 flag to relays without a DirPort; this was bad because such relays
6882 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
6885 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
6886 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
6887 a client authorized hidden service. Fixes bug 15823; bugfix
6890 o Minor features (geoip):
6891 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
6892 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
6896 Changes in version 0.2.7.1-alpha - 2015-05-12
6897 Tor 0.2.7.1-alpha is the first alpha release in its series. It
6898 includes numerous small features and bugfixes against previous Tor
6899 versions, and numerous small infrastructure improvements. The most
6900 notable features are several new ways for controllers to interact with
6901 the hidden services subsystem.
6903 o New system requirements:
6904 - Tor no longer includes workarounds to support Libevent versions
6905 before 1.3e. Libevent 2.0 or later is recommended. Closes
6908 o Major features (controller):
6909 - Add the ADD_ONION and DEL_ONION commands that allow the creation
6910 and management of hidden services via the controller. Closes
6912 - New "GETINFO onions/current" and "GETINFO onions/detached"
6913 commands to get information about hidden services created via the
6914 controller. Part of ticket 6411.
6915 - New HSFETCH command to launch a request for a hidden service
6916 descriptor. Closes ticket 14847.
6917 - New HSPOST command to upload a hidden service descriptor. Closes
6918 ticket 3523. Patch by "DonnchaC".
6920 o Major bugfixes (hidden services):
6921 - Revert commit that made directory authorities assign the HSDir
6922 flag to relays without a DirPort; this was bad because such relays
6923 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
6926 o Minor features (clock-jump tolerance):
6927 - Recover better when our clock jumps back many hours, like might
6928 happen for Tails or Whonix users who start with a very wrong
6929 hardware clock, use Tor to discover a more accurate time, and then
6930 fix their clock. Resolves part of ticket 8766.
6932 o Minor features (command-line interface):
6933 - Make --hash-password imply --hush to prevent unnecessary noise.
6934 Closes ticket 15542. Patch from "cypherpunks".
6935 - Print a warning whenever we find a relative file path being used
6936 as torrc option. Resolves issue 14018.
6938 o Minor features (controller):
6939 - Add DirAuthority lines for default directory authorities to the
6940 output of the "GETINFO config/defaults" command if not already
6941 present. Implements ticket 14840.
6942 - Controllers can now use "GETINFO hs/client/desc/id/..." to
6943 retrieve items from the client's hidden service descriptor cache.
6944 Closes ticket 14845.
6945 - Implement a new controller command "GETINFO status/fresh-relay-
6946 descs" to fetch a descriptor/extrainfo pair that was generated on
6947 demand just for the controller's use. Implements ticket 14784.
6949 o Minor features (DoS-resistance):
6950 - Make it harder for attackers to overload hidden services with
6951 introductions, by blocking multiple introduction requests on the
6952 same circuit. Resolves ticket 15515.
6954 o Minor features (geoip):
6955 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
6956 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
6959 o Minor features (HS popularity countermeasure):
6960 - To avoid leaking HS popularity, don't cycle the introduction point
6961 when we've handled a fixed number of INTRODUCE2 cells but instead
6962 cycle it when a random number of introductions is reached, thus
6963 making it more difficult for an attacker to find out the amount of
6964 clients that have used the introduction point for a specific HS.
6965 Closes ticket 15745.
6967 o Minor features (logging):
6968 - Include the Tor version in all LD_BUG log messages, since people
6969 tend to cut and paste those into the bugtracker. Implements
6972 o Minor features (pluggable transports):
6973 - When launching managed pluggable transports on Linux systems,
6974 attempt to have the kernel deliver a SIGTERM on tor exit if the
6975 pluggable transport process is still running. Resolves
6977 - When launching managed pluggable transports, setup a valid open
6978 stdin in the child process that can be used to detect if tor has
6979 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
6980 can be used by implementations to detect this new behavior.
6981 Resolves ticket 15435.
6983 o Minor features (testing):
6984 - Add a test to verify that the compiler does not eliminate our
6985 memwipe() implementation. Closes ticket 15377.
6986 - Add make rule `check-changes` to verify the format of changes
6987 files. Closes ticket 15180.
6988 - Add unit tests for control_event_is_interesting(). Add a compile-
6989 time check that the number of events doesn't exceed the capacity
6990 of control_event_t.event_mask. Closes ticket 15431, checks for
6991 bugs similar to 13085. Patch by "teor".
6992 - Command-line argument tests moved to Stem. Resolves ticket 14806.
6993 - Integrate the ntor, backtrace, and zero-length keys tests into the
6994 automake test suite. Closes ticket 15344.
6995 - Remove assertions during builds to determine Tor's test coverage.
6996 We don't want to trigger these even in assertions, so including
6997 them artificially makes our branch coverage look worse than it is.
6998 This patch provides the new test-stem-full and coverage-html-full
6999 configure options. Implements ticket 15400.
7001 o Minor bugfixes (build):
7002 - Improve out-of-tree builds by making non-standard rules work and
7003 clean up additional files and directories. Fixes bug 15053; bugfix
7006 o Minor bugfixes (command-line interface):
7007 - When "--quiet" is provided along with "--validate-config", do not
7008 write anything to stdout on success. Fixes bug 14994; bugfix
7010 - When complaining about bad arguments to "--dump-config", use
7013 o Minor bugfixes (configuration, unit tests):
7014 - Only add the default fallback directories when the DirAuthorities,
7015 AlternateDirAuthority, and FallbackDir directory config options
7016 are set to their defaults. The default fallback directory list is
7017 currently empty, this fix will only change tor's behavior when it
7018 has default fallback directories. Includes unit tests for
7019 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
7020 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
7022 o Minor bugfixes (correctness):
7023 - For correctness, avoid modifying a constant string in
7024 handle_control_postdescriptor. Fixes bug 15546; bugfix
7026 - Remove side-effects from tor_assert() calls. This was harmless,
7027 because we never disable assertions, but it is bad style and
7028 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
7031 o Minor bugfixes (hidden service):
7032 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7033 a client authorized hidden service. Fixes bug 15823; bugfix
7035 - Remove an extraneous newline character from the end of hidden
7036 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
7038 o Minor bugfixes (interface):
7039 - Print usage information for --dump-config when it is used without
7040 an argument. Also, fix the error message to use different wording
7041 and add newline at the end. Fixes bug 15541; bugfix
7044 o Minor bugfixes (logs):
7045 - When building Tor under Clang, do not include an extra set of
7046 parentheses in log messages that include function names. Fixes bug
7047 15269; bugfix on every released version of Tor when compiled with
7048 recent enough Clang.
7050 o Minor bugfixes (network):
7051 - When attempting to use fallback technique for network interface
7052 lookup, disregard loopback and multicast addresses since they are
7053 unsuitable for public communications.
7055 o Minor bugfixes (statistics):
7056 - Disregard the ConnDirectionStatistics torrc options when Tor is
7057 not a relay since in that mode of operation no sensible data is
7058 being collected and because Tor might run into measurement hiccups
7059 when running as a client for some time, then becoming a relay.
7060 Fixes bug 15604; bugfix on 0.2.2.35.
7062 o Minor bugfixes (test networks):
7063 - When self-testing reachability, use ExtendAllowPrivateAddresses to
7064 determine if local/private addresses imply reachability. The
7065 previous fix used TestingTorNetwork, which implies
7066 ExtendAllowPrivateAddresses, but this excluded rare configurations
7067 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
7068 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
7069 issue discovered by CJ Ess.
7071 o Minor bugfixes (testing):
7072 - Check for matching value in server response in ntor_ref.py. Fixes
7073 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
7075 - Set the severity correctly when testing
7076 get_interface_addresses_ifaddrs() and
7077 get_interface_addresses_win32(), so that the tests fail gracefully
7078 instead of triggering an assertion. Fixes bug 15759; bugfix on
7079 0.2.6.3-alpha. Reported by Nicolas Derive.
7081 o Code simplification and refactoring:
7082 - Move the hacky fallback code out of get_interface_address6() into
7083 separate function and get it covered with unit-tests. Resolves
7085 - Refactor hidden service client-side cache lookup to intelligently
7086 report its various failure cases, and disentangle failure cases
7087 involving a lack of introduction points. Closes ticket 14391.
7088 - Use our own Base64 encoder instead of OpenSSL's, to allow more
7089 control over the output. Part of ticket 15652.
7092 - Improve the descriptions of statistics-related torrc options in
7093 the manpage to describe rationale and possible uses cases. Fixes
7095 - Improve the layout and formatting of ./configure --help messages.
7096 Closes ticket 15024. Patch from "cypherpunks".
7097 - Standardize on the term "server descriptor" in the manual page.
7098 Previously, we had used "router descriptor", "server descriptor",
7099 and "relay descriptor" interchangeably. Part of ticket 14987.
7102 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
7103 and always use the internal Base64 decoder. The internal decoder
7104 has been part of tor since 0.2.0.10-alpha, and no one should
7105 be using the OpenSSL one. Part of ticket 15652.
7106 - Remove the 'tor_strclear()' function; use memwipe() instead.
7107 Closes ticket 14922.
7110 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
7111 fingerprinting we now recommend pluggable transports; for forward-
7112 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
7113 - Remove the undocumented "--digests" command-line option. It
7114 complicated our build process, caused subtle build issues on
7115 multiple platforms, and is now redundant since we started
7116 including git version identifiers. Closes ticket 14742.
7117 - Tor no longer contains checks for ancient directory cache versions
7118 that didn't know about microdescriptors.
7119 - Tor no longer contains workarounds for stat files generated by
7120 super-old versions of Tor that didn't choose guards sensibly.
7123 Changes in version 0.2.4.27 - 2015-04-06
7124 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
7125 could be used by an attacker to crash hidden services, or crash clients
7126 visiting hidden services. Hidden services should upgrade as soon as
7127 possible; clients should upgrade whenever packages become available.
7129 This release also backports a simple improvement to make hidden
7130 services a bit less vulnerable to denial-of-service attacks.
7132 o Major bugfixes (security, hidden service):
7133 - Fix an issue that would allow a malicious client to trigger an
7134 assertion failure and halt a hidden service. Fixes bug 15600;
7135 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7136 - Fix a bug that could cause a client to crash with an assertion
7137 failure when parsing a malformed hidden service descriptor. Fixes
7138 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7140 o Minor features (DoS-resistance, hidden service):
7141 - Introduction points no longer allow multiple INTRODUCE1 cells to
7142 arrive on the same circuit. This should make it more expensive for
7143 attackers to overwhelm hidden services with introductions.
7144 Resolves ticket 15515.
7147 Changes in version 0.2.5.12 - 2015-04-06
7148 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
7149 could be used by an attacker to crash hidden services, or crash clients
7150 visiting hidden services. Hidden services should upgrade as soon as
7151 possible; clients should upgrade whenever packages become available.
7153 This release also backports a simple improvement to make hidden
7154 services a bit less vulnerable to denial-of-service attacks.
7156 o Major bugfixes (security, hidden service):
7157 - Fix an issue that would allow a malicious client to trigger an
7158 assertion failure and halt a hidden service. Fixes bug 15600;
7159 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7160 - Fix a bug that could cause a client to crash with an assertion
7161 failure when parsing a malformed hidden service descriptor. Fixes
7162 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7164 o Minor features (DoS-resistance, hidden service):
7165 - Introduction points no longer allow multiple INTRODUCE1 cells to
7166 arrive on the same circuit. This should make it more expensive for
7167 attackers to overwhelm hidden services with introductions.
7168 Resolves ticket 15515.
7171 Changes in version 0.2.6.7 - 2015-04-06
7172 Tor 0.2.6.7 fixes two security issues that could be used by an
7173 attacker to crash hidden services, or crash clients visiting hidden
7174 services. Hidden services should upgrade as soon as possible; clients
7175 should upgrade whenever packages become available.
7177 This release also contains two simple improvements to make hidden
7178 services a bit less vulnerable to denial-of-service attacks.
7180 o Major bugfixes (security, hidden service):
7181 - Fix an issue that would allow a malicious client to trigger an
7182 assertion failure and halt a hidden service. Fixes bug 15600;
7183 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7184 - Fix a bug that could cause a client to crash with an assertion
7185 failure when parsing a malformed hidden service descriptor. Fixes
7186 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7188 o Minor features (DoS-resistance, hidden service):
7189 - Introduction points no longer allow multiple INTRODUCE1 cells to
7190 arrive on the same circuit. This should make it more expensive for
7191 attackers to overwhelm hidden services with introductions.
7192 Resolves ticket 15515.
7193 - Decrease the amount of reattempts that a hidden service performs
7194 when its rendezvous circuits fail. This reduces the computational
7195 cost for running a hidden service under heavy load. Resolves
7199 Changes in version 0.2.6.6 - 2015-03-24
7200 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
7202 It adds numerous safety, security, correctness, and performance
7203 improvements. Client programs can be configured to use more kinds of
7204 sockets, AutomapHosts works better, the multithreading backend is
7205 improved, cell transmission is refactored, test coverage is much
7206 higher, more denial-of-service attacks are handled, guard selection is
7207 improved to handle long-term guards better, pluggable transports
7208 should work a bit better, and some annoying hidden service performance
7209 bugs should be addressed.
7211 o Minor bugfixes (portability):
7212 - Use the correct datatype in the SipHash-2-4 function to prevent
7213 compilers from assuming any sort of alignment. Fixes bug 15436;
7214 bugfix on 0.2.5.3-alpha.
7216 Changes in version 0.2.6.5-rc - 2015-03-18
7217 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
7218 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
7220 o Major bugfixes (client):
7221 - Avoid crashing when making certain configuration option changes on
7222 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
7225 o Major bugfixes (pluggable transports):
7226 - Initialize the extended OR Port authentication cookie before
7227 launching pluggable transports. This prevents a race condition
7228 that occured when server-side pluggable transports would cache the
7229 authentication cookie before it has been (re)generated. Fixes bug
7230 15240; bugfix on 0.2.5.1-alpha.
7232 o Major bugfixes (portability):
7233 - Do not crash on startup when running on Solaris. Fixes a bug
7234 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
7237 o Minor features (heartbeat):
7238 - On relays, report how many connections we negotiated using each
7239 version of the Tor link protocols. This information will let us
7240 know if removing support for very old versions of the Tor
7241 protocols is harming the network. Closes ticket 15212.
7243 o Code simplification and refactoring:
7244 - Refactor main loop to extract the 'loop' part. This makes it
7245 easier to run Tor under Shadow. Closes ticket 15176.
7248 Changes in version 0.2.5.11 - 2015-03-17
7249 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
7251 It backports several bugfixes from the 0.2.6 branch, including a
7252 couple of medium-level security fixes for relays and exit nodes.
7253 It also updates the list of directory authorities.
7255 o Directory authority changes:
7256 - Remove turtles as a directory authority.
7257 - Add longclaw as a new (v3) directory authority. This implements
7258 ticket 13296. This keeps the directory authority count at 9.
7259 - The directory authority Faravahar has a new IP address. This
7260 closes ticket 14487.
7262 o Major bugfixes (crash, OSX, security):
7263 - Fix a remote denial-of-service opportunity caused by a bug in
7264 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7267 o Major bugfixes (relay, stability, possible security):
7268 - Fix a bug that could lead to a relay crashing with an assertion
7269 failure if a buffer of exactly the wrong layout was passed to
7270 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7271 0.2.0.10-alpha. Patch from 'cypherpunks'.
7272 - Do not assert if the 'data' pointer on a buffer is advanced to the
7273 very end of the buffer; log a BUG message instead. Only assert if
7274 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7276 o Major bugfixes (exit node stability):
7277 - Fix an assertion failure that could occur under high DNS load.
7278 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7279 diagnosed and fixed by "cypherpunks".
7281 o Major bugfixes (Linux seccomp2 sandbox):
7282 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7283 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7284 0.2.5.1-alpha. Patch from "sanic".
7286 o Minor features (controller):
7287 - New "GETINFO bw-event-cache" to get information about recent
7288 bandwidth events. Closes ticket 14128. Useful for controllers to
7289 get recent bandwidth history after the fix for ticket 13988.
7291 o Minor features (geoip):
7292 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7293 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7296 o Minor bugfixes (client, automapping):
7297 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
7298 no value follows the option. Fixes bug 14142; bugfix on
7299 0.2.4.7-alpha. Patch by "teor".
7300 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
7301 14195; bugfix on 0.1.0.1-rc.
7303 o Minor bugfixes (compilation):
7304 - Build without warnings with the stock OpenSSL srtp.h header, which
7305 has a duplicate declaration of SSL_get_selected_srtp_profile().
7306 Fixes bug 14220; this is OpenSSL's bug, not ours.
7308 o Minor bugfixes (directory authority):
7309 - Allow directory authorities to fetch more data from one another if
7310 they find themselves missing lots of votes. Previously, they had
7311 been bumping against the 10 MB queued data limit. Fixes bug 14261;
7312 bugfix on 0.1.2.5-alpha.
7313 - Enlarge the buffer to read bwauth generated files to avoid an
7314 issue when parsing the file in dirserv_read_measured_bandwidths().
7315 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
7317 o Minor bugfixes (statistics):
7318 - Increase period over which bandwidth observations are aggregated
7319 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
7321 o Minor bugfixes (preventative security, C safety):
7322 - When reading a hexadecimal, base-32, or base-64 encoded value from
7323 a string, always overwrite the whole output buffer. This prevents
7324 some bugs where we would look at (but fortunately, not reveal)
7325 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
7329 Changes in version 0.2.4.26 - 2015-03-17
7330 Tor 0.2.4.26 includes an updated list of directory authorities. It
7331 also backports a couple of stability and security bugfixes from 0.2.5
7334 o Directory authority changes:
7335 - Remove turtles as a directory authority.
7336 - Add longclaw as a new (v3) directory authority. This implements
7337 ticket 13296. This keeps the directory authority count at 9.
7338 - The directory authority Faravahar has a new IP address. This
7339 closes ticket 14487.
7341 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
7342 - Fix an assertion failure that could occur under high DNS load.
7343 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7344 diagnosed and fixed by "cypherpunks".
7346 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
7347 - Fix a bug that could lead to a relay crashing with an assertion
7348 failure if a buffer of exactly the wrong layout was passed to
7349 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7350 0.2.0.10-alpha. Patch from 'cypherpunks'.
7351 - Do not assert if the 'data' pointer on a buffer is advanced to the
7352 very end of the buffer; log a BUG message instead. Only assert if
7353 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7355 o Minor features (geoip):
7356 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7357 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7360 Changes in version 0.2.6.4-rc - 2015-03-09
7361 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
7362 attacker might be able to use in order to crash certain Tor
7363 directories. It also resolves some minor issues left over from, or
7364 introduced in, Tor 0.2.6.3-alpha or earlier.
7366 o Major bugfixes (crash, OSX, security):
7367 - Fix a remote denial-of-service opportunity caused by a bug in
7368 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7371 o Major bugfixes (relay, stability, possible security):
7372 - Fix a bug that could lead to a relay crashing with an assertion
7373 failure if a buffer of exactly the wrong layout is passed to
7374 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7375 0.2.0.10-alpha. Patch from "cypherpunks".
7376 - Do not assert if the 'data' pointer on a buffer is advanced to the
7377 very end of the buffer; log a BUG message instead. Only assert if
7378 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7380 o Major bugfixes (FreeBSD IPFW transparent proxy):
7381 - Fix address detection with FreeBSD transparent proxies, when
7382 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
7385 o Major bugfixes (Linux seccomp2 sandbox):
7386 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
7387 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
7389 - Allow AF_UNIX hidden services to be used with the seccomp2
7390 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
7391 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7392 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7393 0.2.5.1-alpha. Patch from "sanic".
7395 o Minor features (controller):
7396 - Messages about problems in the bootstrap process now include
7397 information about the server we were trying to connect to when we
7398 noticed the problem. Closes ticket 15006.
7400 o Minor features (geoip):
7401 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7402 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7405 o Minor features (logs):
7406 - Quiet some log messages in the heartbeat and at startup. Closes
7409 o Minor bugfixes (certificate handling):
7410 - If an authority operator accidentally makes a signing certificate
7411 with a future publication time, do not discard its real signing
7412 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
7413 - Remove any old authority certificates that have been superseded
7414 for at least two days. Previously, we would keep superseded
7415 certificates until they expired, if they were published close in
7416 time to the certificate that superseded them. Fixes bug 11454;
7417 bugfix on 0.2.1.8-alpha.
7419 o Minor bugfixes (compilation):
7420 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
7422 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
7425 o Minor bugfixes (testing):
7426 - Fix endianness issues in unit test for resolve_my_address() to
7427 have it pass on big endian systems. Fixes bug 14980; bugfix on
7429 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
7430 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
7431 - When running the new 'make test-stem' target, use the configured
7432 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
7434 - When running the zero-length-keys tests, do not use the default
7435 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
7438 o Directory authority IP change:
7439 - The directory authority Faravahar has a new IP address. This
7440 closes ticket 14487.
7443 - Remove some lingering dead code that once supported mempools.
7444 Mempools were disabled by default in 0.2.5, and removed entirely
7445 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
7449 Changes in version 0.2.6.3-alpha - 2015-02-19
7450 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
7451 the 0.2.6.x series. It introduces support for more kinds of sockets,
7452 makes it harder to accidentally run an exit, improves our
7453 multithreading backend, incorporates several fixes for the
7454 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
7456 If no major regressions or security holes are found in this version,
7457 the next version will be a release candidate.
7459 o Deprecated versions:
7460 - Tor relays older than 0.2.4.18-rc are no longer allowed to
7461 advertise themselves on the network. Closes ticket 13555.
7463 o Major features (security, unix domain sockets):
7464 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
7465 applications can reach Tor without having to create AF_INET or
7466 AF_INET6 sockets, meaning they can completely disable their
7467 ability to make non-Tor network connections. To create a socket of
7468 this type, use "SocksPort unix:/path/to/socket". Implements
7470 - Support mapping hidden service virtual ports to AF_UNIX sockets.
7471 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
7472 Implements ticket 11485.
7474 o Major features (changed defaults):
7475 - Prevent relay operators from unintentionally running exits: When a
7476 relay is configured as an exit node, we now warn the user unless
7477 the "ExitRelay" option is set to 1. We warn even more loudly if
7478 the relay is configured with the default exit policy, since this
7479 can indicate accidental misconfiguration. Setting "ExitRelay 0"
7480 stops Tor from running as an exit relay. Closes ticket 10067.
7482 o Major features (directory system):
7483 - When downloading server- or microdescriptors from a directory
7484 server, we no longer launch multiple simultaneous requests to the
7485 same server. This reduces load on the directory servers,
7486 especially when directory guards are in use. Closes ticket 9969.
7487 - When downloading server- or microdescriptors over a tunneled
7488 connection, do not limit the length of our requests to what the
7489 Squid proxy is willing to handle. Part of ticket 9969.
7490 - Authorities can now vote on the correct digests and latest
7491 versions for different software packages. This allows packages
7492 that include Tor to use the Tor authority system as a way to get
7493 notified of updates and their correct digests. Implements proposal
7494 227. Closes ticket 10395.
7496 o Major features (guards):
7497 - Introduce the Guardfraction feature to improves load balancing on
7498 guard nodes. Specifically, it aims to reduce the traffic gap that
7499 guard nodes experience when they first get the Guard flag. This is
7500 a required step if we want to increase the guard lifetime to 9
7501 months or greater. Closes ticket 9321.
7503 o Major features (performance):
7504 - Make the CPU worker implementation more efficient by avoiding the
7505 kernel and lengthening pipelines. The original implementation used
7506 sockets to transfer data from the main thread to the workers, and
7507 didn't allow any thread to be assigned more than a single piece of
7508 work at once. The new implementation avoids communications
7509 overhead by making requests in shared memory, avoiding kernel IO
7510 where possible, and keeping more requests in flight at once.
7511 Implements ticket 9682.
7513 o Major features (relay):
7514 - Raise the minimum acceptable configured bandwidth rate for bridges
7515 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
7516 20 KiB/sec.) Closes ticket 13822.
7518 o Major bugfixes (exit node stability):
7519 - Fix an assertion failure that could occur under high DNS load.
7520 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7521 diagnosed and fixed by "cypherpunks".
7523 o Major bugfixes (mixed relay-client operation):
7524 - When running as a relay and client at the same time (not
7525 recommended), if we decide not to use a new guard because we want
7526 to retry older guards, only close the locally-originating circuits
7527 passing through that guard. Previously we would close all the
7528 circuits through that guard. Fixes bug 9819; bugfix on
7529 0.2.1.1-alpha. Reported by "skruffy".
7531 o Minor features (build):
7532 - New --disable-system-torrc compile-time option to prevent Tor from
7533 looking for the system-wide torrc or torrc-defaults files.
7534 Resolves ticket 13037.
7536 o Minor features (controller):
7537 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
7538 events so controllers can observe circuit isolation inputs. Closes
7540 - ControlPort now supports the unix:/path/to/socket syntax as an
7541 alternative to the ControlSocket option, for consistency with
7542 SocksPort and HiddenServicePort. Closes ticket 14451.
7543 - New "GETINFO bw-event-cache" to get information about recent
7544 bandwidth events. Closes ticket 14128. Useful for controllers to
7545 get recent bandwidth history after the fix for ticket 13988.
7547 o Minor features (Denial of service resistance):
7548 - Count the total number of bytes used storing hidden service
7549 descriptors against the value of MaxMemInQueues. If we're low on
7550 memory, and more than 20% of our memory is used holding hidden
7551 service descriptors, free them until no more than 10% of our
7552 memory holds hidden service descriptors. Free the least recently
7553 fetched descriptors first. Resolves ticket 13806.
7554 - When we have recently been under memory pressure (over 3/4 of
7555 MaxMemInQueues is allocated), then allocate smaller zlib objects
7556 for small requests. Closes ticket 11791.
7558 o Minor features (geoip):
7559 - Update geoip and geoip6 files to the January 7 2015 Maxmind
7560 GeoLite2 Country database.
7562 o Minor features (guard nodes):
7563 - Reduce the time delay before saving guard status to disk from 10
7564 minutes to 30 seconds (or from one hour to 10 minutes if
7565 AvoidDiskWrites is set). Closes ticket 12485.
7567 o Minor features (hidden service):
7568 - Make Sybil attacks against hidden services harder by changing the
7569 minimum time required to get the HSDir flag from 25 hours up to 96
7570 hours. Addresses ticket 14149.
7571 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
7572 services to disable the anti-scanning feature introduced in
7573 0.2.6.2-alpha. With this option not set, a connection to an
7574 unlisted port closes the circuit. With this option set, only a
7575 RELAY_DONE cell is sent. Closes ticket 14084.
7577 o Minor features (interface):
7578 - Implement "-f -" command-line option to read torrc configuration
7579 from standard input, if you don't want to store the torrc file in
7580 the file system. Implements feature 13865.
7582 o Minor features (logging):
7583 - Add a count of unique clients to the bridge heartbeat message.
7584 Resolves ticket 6852.
7585 - Suppress "router info incompatible with extra info" message when
7586 reading extrainfo documents from cache. (This message got loud
7587 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
7589 - Elevate hidden service authorized-client message from DEBUG to
7590 INFO. Closes ticket 14015.
7592 o Minor features (stability):
7593 - Add assertions in our hash-table iteration code to check for
7594 corrupted values that could cause infinite loops. Closes
7597 o Minor features (systemd):
7598 - Various improvements and modernizations in systemd hardening
7599 support. Closes ticket 13805. Patch from Craig Andrews.
7601 o Minor features (testing networks):
7602 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
7603 and the default on a testing network to 2 minutes. Drop the
7604 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
7605 keep the default on a testing network at 30 seconds. This reduces
7606 HS bootstrap time to around 25 seconds. Also, change the default
7607 time in test-network.sh to match. Closes ticket 13401. Patch
7609 - Create TestingDirAuthVoteHSDir to correspond to
7610 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
7611 HSDir flag for the listed relays regardless of uptime or ORPort
7612 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
7613 Partial implementation for ticket 14067. Patch by "teor".
7615 o Minor features (tor2web mode):
7616 - Introduce the config option Tor2webRendezvousPoints, which allows
7617 clients in Tor2webMode to select a specific Rendezvous Point to be
7618 used in HS circuits. This might allow better performance for
7619 Tor2Web nodes. Implements ticket 12844.
7621 o Minor bugfixes (client DNS):
7622 - Report the correct cached DNS expiration times on SOCKS port or in
7623 DNS replies. Previously, we would report everything as "never
7624 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
7625 - Avoid a small memory leak when we find a cached answer for a
7626 reverse DNS lookup in a client-side DNS cache. (Remember, client-
7627 side DNS caching is off by default, and is not recommended.) Fixes
7628 bug 14259; bugfix on 0.2.0.1-alpha.
7630 o Minor bugfixes (client, automapping):
7631 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
7632 no value follows the option. Fixes bug 14142; bugfix on
7633 0.2.4.7-alpha. Patch by "teor".
7634 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
7635 14195; bugfix on 0.1.0.1-rc.
7636 - Prevent changes to other options from removing the wildcard value
7637 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
7639 - Allow MapAddress and AutomapHostsOnResolve to work together when
7640 an address is mapped into another address type (like .onion) that
7641 must be automapped at resolve time. Fixes bug 7555; bugfix
7644 o Minor bugfixes (client, bridges):
7645 - When we are using bridges and we had a network connectivity
7646 problem, only retry connecting to our currently configured
7647 bridges, not all bridges we know about and remember using. Fixes
7648 bug 14216; bugfix on 0.2.2.17-alpha.
7650 o Minor bugfixes (client, IPv6):
7651 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
7652 flag is not set; and not because the NoIPv4Traffic flag was set.
7653 Previously we'd looked at the NoIPv4Traffic flag for both types of
7654 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
7656 o Minor bugfixes (compilation):
7657 - The address of an array in the middle of a structure will always
7658 be non-NULL. clang recognises this and complains. Disable the
7659 tautologous and redundant check to silence this warning. Fixes bug
7660 14001; bugfix on 0.2.1.2-alpha.
7661 - Avoid warnings when building with systemd 209 or later. Fixes bug
7662 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
7663 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
7664 Addresses ticket 14188.
7665 - Build without warnings with the stock OpenSSL srtp.h header, which
7666 has a duplicate declaration of SSL_get_selected_srtp_profile().
7667 Fixes bug 14220; this is OpenSSL's bug, not ours.
7668 - Do not compile any code related to Tor2Web mode when Tor2Web mode
7669 is not enabled at compile time. Previously, this code was included
7670 in a disabled state. See discussion on ticket 12844.
7671 - Remove the --disable-threads configure option again. It was
7672 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
7673 14819; bugfix on 0.2.6.2-alpha.
7675 o Minor bugfixes (controller):
7676 - Report "down" in response to the "GETINFO entry-guards" command
7677 when relays are down with an unreachable_since value. Previously,
7678 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
7679 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
7680 14116; bugfix on 0.2.2.9-alpha.
7681 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
7682 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
7684 o Minor bugfixes (directory authority):
7685 - Allow directory authorities to fetch more data from one another if
7686 they find themselves missing lots of votes. Previously, they had
7687 been bumping against the 10 MB queued data limit. Fixes bug 14261;
7688 bugfix on 0.1.2.5-alpha.
7689 - Do not attempt to download extrainfo documents which we will be
7690 unable to validate with a matching server descriptor. Fixes bug
7691 13762; bugfix on 0.2.0.1-alpha.
7692 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
7693 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
7694 - Enlarge the buffer to read bwauth generated files to avoid an
7695 issue when parsing the file in dirserv_read_measured_bandwidths().
7696 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
7698 o Minor bugfixes (file handling):
7699 - Stop failing when key files are zero-length. Instead, generate new
7700 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
7701 on all versions of Tor. Patch by "teor".
7702 - Stop generating a fresh .old RSA onion key file when the .old file
7703 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
7704 - Avoid overwriting .old key files with empty key files.
7705 - Skip loading zero-length extrainfo store, router store, stats,
7706 state, and key files.
7707 - Avoid crashing when trying to reload a torrc specified as a
7708 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
7711 o Minor bugfixes (hidden services):
7712 - Close the introduction circuit when we have no more usable intro
7713 points, instead of waiting for it to time out. This also ensures
7714 that no follow-up HS descriptor fetch is triggered when the
7715 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
7716 - When fetching a hidden service descriptor for a down service that
7717 was recently up, do not keep refetching until we try the same
7718 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
7719 - Successfully launch Tor with a nonexistent hidden service
7720 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
7721 14106; bugfix on 0.2.6.2-alpha.
7723 o Minor bugfixes (logging):
7724 - Avoid crashing when there are more log domains than entries in
7725 domain_list. Bugfix on 0.2.3.1-alpha.
7726 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
7728 - Don't log messages to stdout twice when starting up. Fixes bug
7729 13993; bugfix on 0.2.6.1-alpha.
7731 o Minor bugfixes (parsing):
7732 - Stop accepting milliseconds (or other junk) at the end of
7733 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
7734 - Support two-number and three-number version numbers correctly, in
7735 case we change the Tor versioning system in the future. Fixes bug
7736 13661; bugfix on 0.0.8pre1.
7738 o Minor bugfixes (path counting):
7739 - When deciding whether the consensus lists any exit nodes, count
7740 the number listed in the consensus, not the number we have
7741 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
7742 - When deciding whether we have any exit nodes, only examine
7743 ExitNodes when the ExitNodes option is actually set. Fixes part of
7744 bug 14918; bugfix on 0.2.6.2-alpha.
7745 - Get rid of redundant and possibly scary warnings that we are
7746 missing directory information while we bootstrap. Fixes part of
7747 bug 14918; bugfix on 0.2.6.2-alpha.
7749 o Minor bugfixes (portability):
7750 - Fix the ioctl()-based network interface lookup code so that it
7751 will work on systems that have variable-length struct ifreq, for
7753 - Fix scheduler compilation on targets where char is unsigned. Fixes
7754 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
7756 o Minor bugfixes (sandbox):
7757 - Allow glibc fatal errors to be sent to stderr before Tor exits.
7758 Previously, glibc would try to write them to /dev/tty, and the
7759 sandbox would trap the call and make Tor exit prematurely. Fixes
7760 bug 14759; bugfix on 0.2.5.1-alpha.
7762 o Minor bugfixes (shutdown):
7763 - When shutting down, always call event_del() on lingering read or
7764 write events before freeing them. Otherwise, we risk double-frees
7765 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
7768 o Minor bugfixes (small memory leaks):
7769 - Avoid leaking memory when using IPv6 virtual address mappings.
7770 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
7773 o Minor bugfixes (statistics):
7774 - Increase period over which bandwidth observations are aggregated
7775 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
7777 o Minor bugfixes (systemd support):
7778 - Fix detection and operation of systemd watchdog. Fixes part of bug
7779 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
7780 - Run correctly under systemd with the RunAsDaemon option set. Fixes
7781 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
7782 - Inform the systemd supervisor about more changes in the Tor
7783 process status. Implements part of ticket 14141. Patch from
7785 - Cause the "--disable-systemd" option to actually disable systemd
7786 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
7789 o Minor bugfixes (TLS):
7790 - Check more thoroughly throughout the TLS code for possible
7791 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
7793 o Minor bugfixes (transparent proxy):
7794 - Use getsockname, not getsockopt, to retrieve the address for a
7795 TPROXY-redirected connection. Fixes bug 13796; bugfix
7798 o Code simplification and refactoring:
7799 - Move fields related to isolating and configuring client ports into
7800 a shared structure. Previously, they were duplicated across
7801 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
7802 to copy them correctly had been the cause of at least one bug in
7803 the past. Closes ticket 8546.
7804 - Refactor the get_interface_addresses_raw() doom-function into
7805 multiple smaller and simpler subfunctions. Cover the resulting
7806 subfunctions with unit-tests. Fixes a significant portion of
7808 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
7809 only for version <= 0.2.2.24 which is now deprecated. Closes
7811 - Remove a test for a long-defunct broken version-one
7815 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
7816 for writing the OpenBSD-specific tips. Resolves ticket 13702.
7817 - Make the tor-resolve documentation match its help string and its
7818 options. Resolves part of ticket 14325.
7819 - Log a more useful error message from tor-resolve when failing to
7820 look up a hidden service address. Resolves part of ticket 14325.
7822 o Downgraded warnings:
7823 - Don't warn when we've attempted to contact a relay using the wrong
7824 ntor onion key. Closes ticket 9635.
7827 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
7828 longer silently accepted as an alias for "ExitNodes".
7829 - The --enable-mempool and --enable-buf-freelists options, which
7830 were originally created to work around bad malloc implementations,
7831 no longer exist. They were off-by-default in 0.2.5. Closes
7835 - Make the checkdir/perms test complete successfully even if the
7836 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
7837 - Test that tor does not fail when key files are zero-length. Check
7838 that tor generates new keys, and overwrites the empty key files.
7839 - Test that tor generates new keys when keys are missing
7840 (existing behavior).
7841 - Test that tor does not overwrite key files that already contain
7842 data (existing behavior). Tests bug 13111. Patch by "teor".
7843 - New "make test-stem" target to run stem integration tests.
7844 Requires that the "STEM_SOURCE_DIR" environment variable be set.
7845 Closes ticket 14107.
7846 - Make the test_cmdline_args.py script work correctly on Windows.
7847 Patch from Gisle Vanem.
7848 - Move the slower unit tests into a new "./src/test/test-slow"
7849 binary that can be run independently of the other tests. Closes
7851 - Avoid undefined behavior when sampling huge values from the
7852 Laplace distribution. This made unittests fail on Raspberry Pi.
7853 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
7856 Changes in version 0.2.6.2-alpha - 2014-12-31
7857 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
7858 It introduces a major new backend for deciding when to send cells on
7859 channels, which should lead down the road to big performance
7860 increases. It contains security and statistics features for better
7861 work on hidden services, and numerous bugfixes.
7863 This release contains many new unit tests, along with major
7864 performance improvements for running testing networks using Chutney.
7865 Thanks to a series of patches contributed by "teor", testing networks
7866 should now bootstrap in seconds, rather than minutes.
7868 o Major features (relay, infrastructure):
7869 - Complete revision of the code that relays use to decide which cell
7870 to send next. Formerly, we selected the best circuit to write on
7871 each channel, but we didn't select among channels in any
7872 sophisticated way. Now, we choose the best circuits globally from
7873 among those whose channels are ready to deliver traffic.
7875 This patch implements a new inter-cmux comparison API, a global
7876 high/low watermark mechanism and a global scheduler loop for
7877 transmission prioritization across all channels as well as among
7878 circuits on one channel. This schedule is currently tuned to
7879 (tolerantly) avoid making changes in network performance, but it
7880 should form the basis for major circuit performance increases in
7881 the future. Code by Andrea; tuning by Rob Jansen; implements
7884 o Major features (hidden services):
7885 - Make HS port scanning more difficult by immediately closing the
7886 circuit when a user attempts to connect to a nonexistent port.
7887 Closes ticket 13667.
7888 - Add a HiddenServiceStatistics option that allows Tor relays to
7889 gather and publish statistics about the overall size and volume of
7890 hidden service usage. Specifically, when this option is turned on,
7891 an HSDir will publish an approximate number of hidden services
7892 that have published descriptors to it the past 24 hours. Also, if
7893 a relay has acted as a hidden service rendezvous point, it will
7894 publish the approximate amount of rendezvous cells it has relayed
7895 the past 24 hours. The statistics themselves are obfuscated so
7896 that the exact values cannot be derived. For more details see
7897 proposal 238, "Better hidden service stats from Tor relays". This
7898 feature is currently disabled by default. Implements feature 13192.
7900 o Major bugfixes (client, automap):
7901 - Repair automapping with IPv6 addresses. This automapping should
7902 have worked previously, but one piece of debugging code that we
7903 inserted to detect a regression actually caused the regression to
7904 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
7905 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
7908 o Major bugfixes (hidden services):
7909 - When closing an introduction circuit that was opened in parallel
7910 with others, don't mark the introduction point as unreachable.
7911 Previously, the first successful connection to an introduction
7912 point would make the other introduction points get marked as
7913 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
7915 o Directory authority changes:
7916 - Remove turtles as a directory authority.
7917 - Add longclaw as a new (v3) directory authority. This implements
7918 ticket 13296. This keeps the directory authority count at 9.
7920 o Major removed features:
7921 - Tor clients no longer support connecting to hidden services
7922 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
7923 option has been removed. (There shouldn't be any hidden services
7924 running these versions on the network.) Closes ticket 7803.
7926 o Minor features (client):
7927 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
7928 is enabled, reject requests with IP addresses as hostnames.
7929 Resolves ticket 13315.
7931 o Minor features (controller):
7932 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
7933 write an unscheduled heartbeat message to the log. Implements
7936 o Minor features (geoip):
7937 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
7940 o Minor features (hidden services):
7941 - When re-enabling the network, don't try to build introduction
7942 circuits until we have successfully built a circuit. This makes
7943 hidden services come up faster when the network is re-enabled.
7944 Patch from "akwizgran". Closes ticket 13447.
7945 - When we fail to retrieve a hidden service descriptor, send the
7946 controller an "HS_DESC FAILED" controller event. Implements
7948 - New HiddenServiceDirGroupReadable option to cause hidden service
7949 directories and hostname files to be created group-readable. Patch
7950 from "anon", David Stainton, and "meejah". Closes ticket 11291.
7952 o Minor features (systemd):
7953 - Where supported, when running with systemd, report successful
7954 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
7955 - When running with systemd, support systemd watchdog messages. Part
7956 of ticket 11016. Patch by Michael Scherer.
7958 o Minor features (transparent proxy):
7959 - Update the transparent proxy option checks to allow for both ipfw
7960 and pf on OS X. Closes ticket 14002.
7961 - Use the correct option when using IPv6 with transparent proxy
7962 support on Linux. Resolves 13808. Patch by Francisco Blas
7965 o Minor bugfixes (preventative security, C safety):
7966 - When reading a hexadecimal, base-32, or base-64 encoded value from
7967 a string, always overwrite the whole output buffer. This prevents
7968 some bugs where we would look at (but fortunately, not reveal)
7969 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
7971 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
7972 just the part that's used. This makes it harder for data leak bugs
7973 to occur in the event of other programming failures. Resolves
7976 o Minor bugfixes (client, microdescriptors):
7977 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
7978 computing which microdescriptors to download. This keeps us from
7979 erroneous download behavior if two microdescriptor digests ever
7980 have the same first 160 bits. Fixes part of bug 13399; bugfix
7982 - Reset a router's status if its microdescriptor digest changes,
7983 even if the first 160 bits remain the same. Fixes part of bug
7984 13399; bugfix on 0.2.3.1-alpha.
7986 o Minor bugfixes (compilation):
7987 - Silence clang warnings under --enable-expensive-hardening,
7988 including implicit truncation of 64 bit values to 32 bit, const
7989 char assignment to self, tautological compare, and additional
7990 parentheses around equality tests. Fixes bug 13577; bugfix
7992 - Fix a clang warning about checking whether an address in the
7993 middle of a structure is NULL. Fixes bug 14001; bugfix
7996 o Minor bugfixes (hidden services):
7997 - Correctly send a controller event when we find that a rendezvous
7998 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
7999 - Pre-check directory permissions for new hidden-services to avoid
8000 at least one case of "Bug: Acting on config options left us in a
8001 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
8002 - When adding a new hidden service (for example, via SETCONF), Tor
8003 no longer congratulates the user for running a relay. Fixes bug
8004 13941; bugfix on 0.2.6.1-alpha.
8005 - When fetching hidden service descriptors, we now check not only
8006 for whether we got the hidden service we had in mind, but also
8007 whether we got the particular descriptors we wanted. This prevents
8008 a class of inefficient but annoying DoS attacks by hidden service
8009 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
8012 o Minor bugfixes (Linux seccomp2 sandbox):
8013 - Make transparent proxy support work along with the seccomp2
8014 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
8015 by Francisco Blas Izquierdo Riera.
8016 - Fix a memory leak in tor-resolve when running with the sandbox
8017 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
8019 o Minor bugfixes (logging):
8020 - Downgrade warnings about RSA signature failures to info log level.
8021 Emit a warning when an extra info document is found incompatible
8022 with a corresponding router descriptor. Fixes bug 9812; bugfix
8024 - Make connection_ap_handshake_attach_circuit() log the circuit ID
8025 correctly. Fixes bug 13701; bugfix on 0.0.6.
8027 o Minor bugfixes (misc):
8028 - Stop allowing invalid address patterns like "*/24" that contain
8029 both a wildcard address and a bit prefix length. This affects all
8030 our address-range parsing code. Fixes bug 7484; bugfix
8033 o Minor bugfixes (testing networks, fast startup):
8034 - Allow Tor to build circuits using a consensus with no exits. If
8035 the consensus has no exits (typical of a bootstrapping test
8036 network), allow Tor to build circuits once enough descriptors have
8037 been downloaded. This assists in bootstrapping a testing Tor
8038 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
8040 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
8041 header to directory servers. This allows us to obtain consensuses
8042 promptly when the consensus interval is very short. This assists
8043 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
8044 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
8045 - Stop assuming that private addresses are local when checking
8046 reachability in a TestingTorNetwork. Instead, when testing, assume
8047 all OR connections are remote. (This is necessary due to many test
8048 scenarios running all relays on localhost.) This assists in
8049 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
8050 0.1.0.1-rc. Patch by "teor".
8051 - Avoid building exit circuits from a consensus with no exits. Now
8052 thanks to our fix for 13718, we accept a no-exit network as not
8053 wholly lost, but we need to remember not to try to build exit
8054 circuits on it. Closes ticket 13814; patch by "teor".
8055 - Stop requiring exits to have non-zero bandwithcapacity in a
8056 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
8057 ignore exit bandwidthcapacity. This assists in bootstrapping a
8058 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
8059 on 0.2.0.3-alpha. Patch by "teor".
8060 - Add "internal" to some bootstrap statuses when no exits are
8061 available. If the consensus does not contain Exits, Tor will only
8062 build internal circuits. In this case, relevant statuses will
8063 contain the word "internal" as indicated in the Tor control-
8064 spec.txt. When bootstrap completes, Tor will be ready to build
8065 internal circuits. If a future consensus contains Exits, exit
8066 circuits may become available. Fixes part of bug 13718; bugfix on
8067 0.2.4.10-alpha. Patch by "teor".
8068 - Decrease minimum consensus interval to 10 seconds when
8069 TestingTorNetwork is set, or 5 seconds for the first consensus.
8070 Fix assumptions throughout the code that assume larger intervals.
8071 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
8073 - Avoid excluding guards from path building in minimal test
8074 networks, when we're in a test network and excluding guards would
8075 exclude all relays. This typically occurs in incredibly small tor
8076 networks, and those using "TestingAuthVoteGuard *". Fixes part of
8077 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
8079 o Code simplification and refactoring:
8080 - Stop using can_complete_circuits as a global variable; access it
8081 with a function instead.
8082 - Avoid using operators directly as macro arguments: this lets us
8083 apply coccinelle transformations to our codebase more directly.
8084 Closes ticket 13172.
8085 - Combine the functions used to parse ClientTransportPlugin and
8086 ServerTransportPlugin into a single function. Closes ticket 6456.
8087 - Add inline functions and convenience macros for inspecting channel
8088 state. Refactor the code to use convenience macros instead of
8089 checking channel state directly. Fixes issue 7356.
8090 - Document all members of was_router_added_t and rename
8091 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
8092 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
8093 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
8094 constant instead of hardcoded value. Fixes issue 13840.
8095 - Refactor our generic strmap and digestmap types into a single
8096 implementation, so that we can add a new digest256map
8100 - Document the bridge-authority-only 'networkstatus-bridges' file.
8101 Closes ticket 13713; patch from "tom".
8102 - Fix typo in PredictedPortsRelevanceTime option description in
8103 manpage. Resolves issue 13707.
8104 - Stop suggesting that users specify relays by nickname: it isn't a
8105 good idea. Also, properly cross-reference how to specify relays in
8106 all parts of manual documenting options that take a list of
8107 relays. Closes ticket 13381.
8108 - Clarify the HiddenServiceDir option description in manpage to make
8109 it clear that relative paths are taken with respect to the current
8110 working directory. Also clarify that this behavior is not
8111 guaranteed to remain indefinitely. Fixes issue 13913.
8114 - New tests for many parts of channel, relay, and circuitmux
8115 functionality. Code by Andrea; part of 9262.
8116 - New tests for parse_transport_line(). Part of ticket 6456.
8117 - In the unit tests, use chgrp() to change the group of the unit
8118 test temporary directory to the current user, so that the sticky
8119 bit doesn't interfere with tests that check directory groups.
8121 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
8125 Changes in version 0.2.6.1-alpha - 2014-10-30
8126 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
8127 includes numerous code cleanups and new tests, and fixes a large
8128 number of annoying bugs. Out-of-memory conditions are handled better
8129 than in 0.2.5, pluggable transports have improved proxy support, and
8130 clients now use optimistic data for contacting hidden services. Also,
8131 we are now more robust to changes in what we consider a parseable
8132 directory object, so that tightening restrictions does not have a risk
8133 of introducing infinite download loops.
8135 This is the first alpha release in a new series, so expect there to be
8136 bugs. Users who would rather test out a more stable branch should stay
8137 with 0.2.5.x for now.
8139 o New compiler and system requirements:
8140 - Tor 0.2.6.x requires that your compiler support more of the C99
8141 language standard than before. The 'configure' script now detects
8142 whether your compiler supports C99 mid-block declarations and
8143 designated initializers. If it does not, Tor will not compile.
8145 We may revisit this requirement if it turns out that a significant
8146 number of people need to build Tor with compilers that don't
8147 bother implementing a 15-year-old standard. Closes ticket 13233.
8148 - Tor no longer supports systems without threading support. When we
8149 began working on Tor, there were several systems that didn't have
8150 threads, or where the thread support wasn't able to run the
8151 threads of a single process on multiple CPUs. That no longer
8152 holds: every system where Tor needs to run well now has threading
8153 support. Resolves ticket 12439.
8155 o Removed platform support:
8156 - We no longer include special code to build on Windows CE; as far
8157 as we know, nobody has used Tor on Windows CE in a very long time.
8158 Closes ticket 11446.
8160 o Major features (bridges):
8161 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
8162 transports if they are configured via the "TOR_PT_PROXY"
8163 environment variable. Implements proposal 232. Resolves
8166 o Major features (client performance, hidden services):
8167 - Allow clients to use optimistic data when connecting to a hidden
8168 service, which should remove a round-trip from hidden service
8169 initialization. See proposal 181 for details. Implements
8172 o Major features (directory system):
8173 - Upon receiving an unparseable directory object, if its digest
8174 matches what we expected, then don't try to download it again.
8175 Previously, when we got a descriptor we didn't like, we would keep
8176 trying to download it over and over. Closes ticket 11243.
8178 o Major features (sample torrc):
8179 - Add a new, infrequently-changed "torrc.minimal". This file is
8180 similar to torrc.sample, but it will change as infrequently as
8181 possible, for the benefit of users whose systems prompt them for
8182 intervention whenever a default configuration file is changed.
8183 Making this change allows us to update torrc.sample to be a more
8184 generally useful "sample torrc".
8186 o Major bugfixes (directory authorities):
8187 - Do not assign the HSDir flag to relays if they are not Valid, or
8188 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
8190 o Major bugfixes (directory bandwidth performance):
8191 - Don't flush the zlib buffer aggressively when compressing
8192 directory information for clients. This should save about 7% of
8193 the bandwidth currently used for compressed descriptors and
8194 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
8196 o Minor features (security, memory wiping):
8197 - Ensure we securely wipe keys from memory after
8198 crypto_digest_get_digest and init_curve25519_keypair_from_file
8199 have finished using them. Resolves ticket 13477.
8201 o Minor features (security, out-of-memory handling):
8202 - When handling an out-of-memory condition, allocate less memory for
8203 temporary data structures. Fixes issue 10115.
8204 - When handling an out-of-memory condition, consider more types of
8205 buffers, including those on directory connections, and zlib
8206 buffers. Resolves ticket 11792.
8209 - When identity keypair is generated for first time, log a
8210 congratulatory message that links to the new relay lifecycle
8211 document. Implements feature 10427.
8213 o Minor features (client):
8214 - Clients are now willing to send optimistic data (before they
8215 receive a 'connected' cell) to relays of any version. (Relays
8216 without support for optimistic data are no longer supported on the
8217 Tor network.) Resolves ticket 13153.
8219 o Minor features (directory authorities):
8220 - Don't list relays with a bandwidth estimate of 0 in the consensus.
8221 Implements a feature proposed during discussion of bug 13000.
8222 - In tor-gencert, report an error if the user provides the same
8223 argument more than once.
8224 - If a directory authority can't find a best consensus method in the
8225 votes that it holds, it now falls back to its favorite consensus
8226 method. Previously, it fell back to method 1. Neither of these is
8227 likely to get enough signatures, but "fall back to favorite"
8228 doesn't require us to maintain support an obsolete consensus
8229 method. Implements part of proposal 215.
8231 o Minor features (logging):
8232 - On Unix-like systems, you can now use named pipes as the target of
8233 the Log option, and other options that try to append to files.
8234 Closes ticket 12061. Patch from "carlo von lynX".
8235 - When opening a log file at startup, send it every log message that
8236 we generated between startup and opening it. Previously, log
8237 messages that were generated before opening the log file were only
8238 logged to stdout. Closes ticket 6938.
8239 - Add a TruncateLogFile option to overwrite logs instead of
8240 appending to them. Closes ticket 5583.
8242 o Minor features (portability, Solaris):
8243 - Threads are no longer disabled by default on Solaris; we believe
8244 that the versions of Solaris with broken threading support are all
8245 obsolete by now. Resolves ticket 9495.
8247 o Minor features (relay):
8248 - Re-check our address after we detect a changed IP address from
8249 getsockname(). This ensures that the controller command "GETINFO
8250 address" will report the correct value. Resolves ticket 11582.
8252 - A new AccountingRule option lets Relays set whether they'd like
8253 AccountingMax to be applied separately to inbound and outbound
8254 traffic, or applied to the sum of inbound and outbound traffic.
8255 Resolves ticket 961. Patch by "chobe".
8257 o Minor features (testing networks):
8258 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
8259 the "Exit" flag regardless of their uptime, bandwidth, or exit
8260 policy. TestingTorNetwork must be set for this option to have any
8261 effect. Previously, authorities would take up to 35 minutes to
8262 give nodes the Exit flag in a test network. Partially implements
8265 o Minor features (validation):
8266 - Check all date/time values passed to tor_timegm and
8267 parse_rfc1123_time for validity, taking leap years into account.
8268 Improves HTTP header validation. Implemented with bug 13476.
8269 - In correct_tm(), limit the range of values returned by system
8270 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
8271 This means we don't have to deal with negative or too large dates,
8272 even if a clock is wrong. Otherwise we might fail to read a file
8273 written by us which includes such a date. Fixes bug 13476.
8275 o Minor bugfixes (bridge clients):
8276 - When configured to use a bridge without an identity digest (not
8277 recommended), avoid launching an extra channel to it when
8278 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
8280 o Minor bugfixes (bridges):
8281 - When DisableNetwork is set, do not launch pluggable transport
8282 plugins, and if any are running, terminate them. Fixes bug 13213;
8283 bugfix on 0.2.3.6-alpha.
8285 o Minor bugfixes (C correctness):
8286 - Fix several instances of possible integer overflow/underflow/NaN.
8287 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
8289 - In circuit_build_times_calculate_timeout() in circuitstats.c,
8290 avoid dividing by zero in the pareto calculations. This traps
8291 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
8293 - Fix an integer overflow in format_time_interval(). Fixes bug
8294 13393; bugfix on 0.2.0.10-alpha.
8295 - Set the correct day of year value when the system's localtime(_r)
8296 or gmtime(_r) functions fail to set struct tm. Not externally
8297 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
8298 - Avoid unlikely signed integer overflow in tor_timegm on systems
8299 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
8301 o Minor bugfixes (client):
8302 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
8303 BadExit flag are not considered worthy candidates. Fixes bug
8304 13066; bugfix on 0.1.2.3-alpha.
8305 - Use the consensus schedule for downloading consensuses, and not
8306 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
8307 - Handle unsupported or malformed SOCKS5 requests properly by
8308 responding with the appropriate error message before closing the
8309 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
8311 o Minor bugfixes (client, torrc):
8312 - Stop modifying the value of our DirReqStatistics torrc option just
8313 because we're not a bridge or relay. This bug was causing Tor
8314 Browser users to write "DirReqStatistics 0" in their torrc files
8315 as if they had chosen to change the config. Fixes bug 4244; bugfix
8317 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
8318 that our options have changed every time we SIGHUP. Fixes bug
8319 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
8321 o Minor bugfixes (controller):
8322 - Return an error when the second or later arguments of the
8323 "setevents" controller command are invalid events. Previously we
8324 would return success while silently skipping invalid events. Fixes
8325 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
8327 o Minor bugfixes (directory system):
8328 - Always believe that v3 directory authorities serve extra-info
8329 documents, whether they advertise "caches-extra-info" or not.
8330 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8331 - When running as a v3 directory authority, advertise that you serve
8332 extra-info documents so that clients who want them can find them
8333 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8334 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
8335 Previously, directories offering BRIDGE_DIRINFO and some other
8336 flag (i.e. microdescriptors or extrainfo) would be ignored when
8337 looking for bridges. Partially fixes bug 13163; bugfix
8340 o Minor bugfixes (networking):
8341 - Check for orconns and use connection_or_close_for_error() rather
8342 than connection_mark_for_close() directly in the getsockopt()
8343 failure case of connection_handle_write_impl(). Fixes bug 11302;
8344 bugfix on 0.2.4.4-alpha.
8346 o Minor bugfixes (relay):
8347 - When generating our family list, remove spaces from around the
8348 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
8349 - If our previous bandwidth estimate was 0 bytes, allow publishing a
8350 new relay descriptor immediately. Fixes bug 13000; bugfix
8353 o Minor bugfixes (testing networks):
8354 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
8355 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
8356 - Stop using the default authorities in networks which provide both
8357 AlternateDirAuthority and AlternateBridgeAuthority. Partially
8358 fixes bug 13163; bugfix on 0.2.0.13-alpha.
8360 o Minor bugfixes (testing):
8361 - Stop spawn test failures due to a race condition between the
8362 SIGCHLD handler updating the process status, and the test reading
8363 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
8365 o Minor bugfixes (testing, Windows):
8366 - Avoid passing an extra backslash when creating a temporary
8367 directory for running the unit tests on Windows. Fixes bug 12392;
8368 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
8370 o Minor bugfixes (windows):
8371 - Remove code to special-case handling of NTE_BAD_KEYSET when
8372 acquiring windows CryptoAPI context. This error can't actually
8373 occur for the parameters we're providing. Fixes bug 10816; bugfix
8376 o Minor bugfixes (zlib):
8377 - Avoid truncating a zlib stream when trying to finalize it with an
8378 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
8381 - Allow our configure script to build correctly with autoconf 2.62
8382 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
8383 - Improve the error message from ./configure to make it clear that
8384 when asciidoc has not been found, the user will have to either add
8385 --disable-asciidoc argument or install asciidoc. Resolves
8388 o Code simplification and refactoring:
8389 - Change the entry_is_live() function to take named bitfield
8390 elements instead of an unnamed list of booleans. Closes
8392 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
8393 Resolves ticket 12205.
8394 - Use calloc and reallocarray functions instead of multiply-
8395 then-malloc. This makes it less likely for us to fall victim to an
8396 integer overflow attack when allocating. Resolves ticket 12855.
8397 - Use the standard macro name SIZE_MAX, instead of our
8399 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
8400 functions which take them as arguments. Replace 0 with NO_DIRINFO
8401 in a function call for clarity. Seeks to prevent future issues
8403 - Avoid 4 null pointer errors under clang static analysis by using
8404 tor_assert() to prove that the pointers aren't null. Fixes
8406 - Rework the API of policies_parse_exit_policy() to use a bitmask to
8407 represent parsing options, instead of a confusing mess of
8408 booleans. Resolves ticket 8197.
8409 - Introduce a helper function to parse ExitPolicy in
8410 or_options_t structure.
8413 - Add a doc/TUNING document with tips for handling large numbers of
8414 TCP connections when running busy Tor relay. Update the warning
8415 message to point to this file when running out of sockets
8416 operating system is allowing to use simultaneously. Resolves
8420 - We no longer remind the user about configuration options that have
8421 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
8422 - Remove our old, non-weighted bandwidth-based node selection code.
8423 Previously, we used it as a fallback when we couldn't perform
8424 weighted bandwidth-based node selection. But that would only
8425 happen in the cases where we had no consensus, or when we had a
8426 consensus generated by buggy or ancient directory authorities. In
8427 either case, it's better to use the more modern, better maintained
8428 algorithm, with reasonable defaults for the weights. Closes
8430 - Remove the --disable-curve25519 configure option. Relays and
8431 clients now are required to support curve25519 and the
8433 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
8434 used to be deprecated synonyms for "StrictNodes", are now marked
8435 obsolete. Resolves ticket 12226.
8436 - Clients don't understand the BadDirectory flag in the consensus
8437 anymore, and ignore it.
8440 - Refactor the function that chooses guard nodes so that it can more
8441 easily be tested; write some tests for it.
8442 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
8443 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
8444 - Create unit tests for format_time_interval(). With bug 13393.
8445 - Add unit tests for tor_timegm signed overflow, tor_timegm and
8446 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
8447 tests (visible) fixes in bug 13476.
8448 - Add a "coverage-html" make target to generate HTML-visualized
8449 coverage results when building with --enable-coverage. (Requires
8450 lcov.) Patch from Kevin Murray.
8451 - Enable the backtrace handler (where supported) when running the
8453 - Revise all unit tests that used the legacy test_* macros to
8454 instead use the recommended tt_* macros. This patch was generated
8455 with coccinelle, to avoid manual errors. Closes ticket 13119.
8457 o Distribution (systemd):
8458 - systemd unit file: only allow tor to write to /var/lib/tor and
8459 /var/log/tor. The rest of the filesystem is accessible for reading
8460 only. Patch by intrigeri; resolves ticket 12751.
8461 - systemd unit file: ensure that the process and all its children
8462 can never gain new privileges. Patch by intrigeri; resolves
8464 - systemd unit file: set up /var/run/tor as writable for the Tor
8465 service. Patch by intrigeri; resolves ticket 13196.
8467 o Removed features (directory authorities):
8468 - Remove code that prevented authorities from listing Tor relays
8469 affected by CVE-2011-2769 as guards. These relays are already
8470 rejected altogether due to the minimum version requirement of
8471 0.2.3.16-alpha. Closes ticket 13152.
8472 - The "AuthDirRejectUnlisted" option no longer has any effect, as
8473 the fingerprints file (approved-routers) has been deprecated.
8474 - Directory authorities do not support being Naming dirauths anymore.
8475 The "NamingAuthoritativeDir" config option is now obsolete.
8476 - Directory authorities do not support giving out the BadDirectory
8478 - Directory authorities no longer advertise or support consensus
8479 methods 1 through 12 inclusive. These consensus methods were
8480 obsolete and/or insecure: maintaining the ability to support them
8481 served no good purpose. Implements part of proposal 215; closes
8484 o Testing (test-network.sh):
8485 - Stop using "echo -n", as some shells' built-in echo doesn't
8486 support "-n". Instead, use "/bin/echo -n". Partially fixes
8488 - Stop an apparent test-network hang when used with make -j2. Fixes
8490 - Add a --delay option to test-network.sh, which configures the
8491 delay before the chutney network tests for data transmission.
8492 Partially implements ticket 13161.
8495 Changes in version 0.2.5.10 - 2014-10-24
8496 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
8498 It adds several new security features, including improved
8499 denial-of-service resistance for relays, new compiler hardening
8500 options, and a system-call sandbox for hardened installations on Linux
8501 (requires seccomp2). The controller protocol has several new features,
8502 resolving IPv6 addresses should work better than before, and relays
8503 should be a little more CPU-efficient. We've added support for more
8504 OpenBSD and FreeBSD transparent proxy types. We've improved the build
8505 system and testing infrastructure to allow unit testing of more parts
8506 of the Tor codebase. Finally, we've addressed several nagging pluggable
8507 transport usability issues, and included numerous other small bugfixes
8508 and features mentioned below.
8510 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
8511 have accumulated many known flaws; everyone should upgrade.
8513 o Deprecated versions:
8514 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
8515 attention for some while.
8518 Changes in version 0.2.5.9-rc - 2014-10-20
8519 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
8520 series. It disables SSL3 in response to the recent "POODLE" attack
8521 (even though POODLE does not affect Tor). It also works around a crash
8522 bug caused by some operating systems' response to the "POODLE" attack
8523 (which does affect Tor). It also contains a few miscellaneous fixes.
8525 o Major security fixes:
8526 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
8527 today support TLS 1.0 or later, so we can safely turn off support
8528 for this old (and insecure) protocol. Fixes bug 13426.
8530 o Major bugfixes (openssl bug workaround):
8531 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
8532 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
8533 13471. This is a workaround for an OpenSSL bug.
8536 - Disable the sandbox name resolver cache when running tor-resolve:
8537 tor-resolve doesn't use the sandbox code, and turning it on was
8538 breaking attempts to do tor-resolve on a non-default server on
8539 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
8541 o Compilation fixes:
8542 - Build and run correctly on systems like OpenBSD-current that have
8543 patched OpenSSL to remove get_cipher_by_char and/or its
8544 implementations. Fixes issue 13325.
8546 o Downgraded warnings:
8547 - Downgrade the severity of the 'unexpected sendme cell from client'
8548 from 'warn' to 'protocol warning'. Closes ticket 8093.
8551 Changes in version 0.2.4.25 - 2014-10-20
8552 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
8553 (even though POODLE does not affect Tor). It also works around a crash
8554 bug caused by some operating systems' response to the "POODLE" attack
8555 (which does affect Tor).
8557 o Major security fixes (also in 0.2.5.9-rc):
8558 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
8559 today support TLS 1.0 or later, so we can safely turn off support
8560 for this old (and insecure) protocol. Fixes bug 13426.
8562 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
8563 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
8564 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
8565 13471. This is a workaround for an OpenSSL bug.
8568 Changes in version 0.2.5.8-rc - 2014-09-22
8569 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
8570 series. It fixes a bug that affects consistency and speed when
8571 connecting to hidden services, and it updates the location of one of
8572 the directory authorities.
8575 - Clients now send the correct address for their chosen rendezvous
8576 point when trying to access a hidden service. They used to send
8577 the wrong address, which would still work some of the time because
8578 they also sent the identity digest of the rendezvous point, and if
8579 the hidden service happened to try connecting to the rendezvous
8580 point from a relay that already had a connection open to it,
8581 the relay would reuse that connection. Now connections to hidden
8582 services should be more robust and faster. Also, this bug meant
8583 that clients were leaking to the hidden service whether they were
8584 on a little-endian (common) or big-endian (rare) system, which for
8585 some users might have reduced their anonymity. Fixes bug 13151;
8586 bugfix on 0.2.1.5-alpha.
8588 o Directory authority changes:
8589 - Change IP address for gabelmoo (v3 directory authority).
8592 Changes in version 0.2.4.24 - 2014-09-22
8593 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
8594 connecting to hidden services, and it updates the location of one of
8595 the directory authorities.
8598 - Clients now send the correct address for their chosen rendezvous
8599 point when trying to access a hidden service. They used to send
8600 the wrong address, which would still work some of the time because
8601 they also sent the identity digest of the rendezvous point, and if
8602 the hidden service happened to try connecting to the rendezvous
8603 point from a relay that already had a connection open to it,
8604 the relay would reuse that connection. Now connections to hidden
8605 services should be more robust and faster. Also, this bug meant
8606 that clients were leaking to the hidden service whether they were
8607 on a little-endian (common) or big-endian (rare) system, which for
8608 some users might have reduced their anonymity. Fixes bug 13151;
8609 bugfix on 0.2.1.5-alpha.
8611 o Directory authority changes:
8612 - Change IP address for gabelmoo (v3 directory authority).
8614 o Minor features (geoip):
8615 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
8619 Changes in version 0.2.5.7-rc - 2014-09-11
8620 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
8621 release series, and some long-standing bugs related to ORPort reachability
8622 testing and failure to send CREATE cells. It is the first release
8623 candidate for the Tor 0.2.5.x series.
8625 o Major bugfixes (client, startup):
8626 - Start making circuits as soon as DisabledNetwork is turned off.
8627 When Tor started with DisabledNetwork set, it would correctly
8628 conclude that it shouldn't build circuits, but it would mistakenly
8629 cache this conclusion, and continue believing it even when
8630 DisableNetwork is set to 0. Fixes the bug introduced by the fix
8631 for bug 11200; bugfix on 0.2.5.4-alpha.
8632 - Resume expanding abbreviations for command-line options. The fix
8633 for bug 4647 accidentally removed our hack from bug 586 that
8634 rewrote HashedControlPassword to __HashedControlSessionPassword
8635 when it appears on the commandline (which allowed the user to set
8636 her own HashedControlPassword in the torrc file while the
8637 controller generates a fresh session password for each run). Fixes
8638 bug 12948; bugfix on 0.2.5.1-alpha.
8639 - Warn about attempts to run hidden services and relays in the same
8640 process: that's probably not a good idea. Closes ticket 12908.
8642 o Major bugfixes (relay):
8643 - Avoid queuing or sending destroy cells for circuit ID zero when we
8644 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
8645 Found and fixed by "cypherpunks".
8646 - Fix ORPort reachability detection on relays running behind a
8647 proxy, by correctly updating the "local" mark on the controlling
8648 channel when changing the address of an or_connection_t after the
8649 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
8651 o Minor features (bridge):
8652 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
8653 cookie file for the ExtORPort g+r by default.
8655 o Minor features (geoip):
8656 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
8659 o Minor bugfixes (logging):
8660 - Reduce the log severity of the "Pluggable transport proxy does not
8661 provide any needed transports and will not be launched." message,
8662 since Tor Browser includes several ClientTransportPlugin lines in
8663 its torrc-defaults file, leading every Tor Browser user who looks
8664 at her logs to see these notices and wonder if they're dangerous.
8665 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
8666 - Downgrade "Unexpected onionskin length after decryption" warning
8667 to a protocol-warn, since there's nothing relay operators can do
8668 about a client that sends them a malformed create cell. Resolves
8669 bug 12996; bugfix on 0.0.6rc1.
8670 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
8671 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
8672 - When logging information about an EXTEND2 or EXTENDED2 cell, log
8673 their names correctly. Fixes part of bug 12700; bugfix
8675 - When logging information about a relay cell whose command we don't
8676 recognize, log its command as an integer. Fixes part of bug 12700;
8677 bugfix on 0.2.1.10-alpha.
8678 - Escape all strings from the directory connection before logging
8679 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
8681 o Minor bugfixes (controller):
8682 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
8683 bug 12864; bugfix on 0.2.5.1-alpha.
8684 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
8685 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
8688 o Minor bugfixes (compilation):
8689 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
8690 bugfix on 0.2.5.5-alpha.
8691 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
8692 0.2.5.1-alpha. Patch from "NewEraCracker".
8693 - In routerlist_assert_ok(), don't take the address of a
8694 routerinfo's cache_info member unless that routerinfo is non-NULL.
8695 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
8696 - Fix a large number of false positive warnings from the clang
8697 analyzer static analysis tool. This should make real warnings
8698 easier for clang analyzer to find. Patch from "teor". Closes
8701 o Distribution (systemd):
8702 - Verify configuration file via ExecStartPre in the systemd unit
8703 file. Patch from intrigeri; resolves ticket 12730.
8704 - Explicitly disable RunAsDaemon in the systemd unit file. Our
8705 current systemd unit uses "Type = simple", so systemd does not
8706 expect tor to fork. If the user has "RunAsDaemon 1" in their
8707 torrc, then things won't work as expected. This is e.g. the case
8708 on Debian (and derivatives), since there we pass "--defaults-torrc
8709 /usr/share/tor/tor-service-defaults-torrc" (that contains
8710 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
8714 - Adjust the URLs in the README to refer to the new locations of
8715 several documents on the website. Fixes bug 12830. Patch from
8717 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
8721 Changes in version 0.2.5.6-alpha - 2014-07-28
8722 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
8723 risk from guard rotation, and fixes a variety of other issues to get
8724 us closer to a release candidate.
8726 o Major features (also in 0.2.4.23):
8727 - Make the number of entry guards configurable via a new
8728 NumEntryGuards consensus parameter, and the number of directory
8729 guards configurable via a new NumDirectoryGuards consensus
8730 parameter. Implements ticket 12688.
8732 o Major bugfixes (also in 0.2.4.23):
8733 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
8734 implementation that caused incorrect results on 32-bit
8735 implementations when certain malformed inputs were used along with
8736 a small class of private ntor keys. This bug does not currently
8737 appear to allow an attacker to learn private keys or impersonate a
8738 Tor server, but it could provide a means to distinguish 32-bit Tor
8739 implementations from 64-bit Tor implementations. Fixes bug 12694;
8740 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
8744 - Perform circuit cleanup operations even when circuit
8745 construction operations are disabled (because the network is
8746 disabled, or because there isn't enough directory information).
8747 Previously, when we were not building predictive circuits, we
8748 were not closing expired circuits either. Fixes bug 8387; bugfix on
8749 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
8750 became more strict about when we have "enough directory information
8754 - Authorities now assign the Guard flag to the fastest 25% of the
8755 network (it used to be the fastest 50%). Also raise the consensus
8756 weight that guarantees the Guard flag from 250 to 2000. For the
8757 current network, this results in about 1100 guards, down from 2500.
8758 This step paves the way for moving the number of entry guards
8759 down to 1 (proposal 236) while still providing reasonable expected
8760 performance for most users. Implements ticket 12690.
8761 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
8763 - Slightly enhance the diagnostic message for bug 12184.
8765 o Minor bugfixes (also in 0.2.4.23):
8766 - Warn and drop the circuit if we receive an inbound 'relay early'
8767 cell. Those used to be normal to receive on hidden service circuits
8768 due to bug 1038, but the buggy Tor versions are long gone from
8769 the network so we can afford to resume watching for them. Resolves
8770 the rest of bug 1038; bugfix on 0.2.1.19.
8771 - Correct a confusing error message when trying to extend a circuit
8772 via the control protocol but we don't know a descriptor or
8773 microdescriptor for one of the specified relays. Fixes bug 12718;
8774 bugfix on 0.2.3.1-alpha.
8777 - Fix compilation when building with bufferevents enabled. (This
8778 configuration is still not expected to work, however.)
8779 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
8780 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
8782 - Compile correctly with builds and forks of OpenSSL (such as
8783 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
8784 0.2.1.1-alpha. Patch from "dhill".
8787 Changes in version 0.2.4.23 - 2014-07-28
8788 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
8789 guard rotation, and also backports several important fixes from the
8790 Tor 0.2.5 alpha release series.
8793 - Clients now look at the "usecreatefast" consensus parameter to
8794 decide whether to use CREATE_FAST or CREATE cells for the first hop
8795 of their circuit. This approach can improve security on connections
8796 where Tor's circuit handshake is stronger than the available TLS
8797 connection security levels, but the tradeoff is more computational
8798 load on guard relays. Implements proposal 221. Resolves ticket 9386.
8799 - Make the number of entry guards configurable via a new
8800 NumEntryGuards consensus parameter, and the number of directory
8801 guards configurable via a new NumDirectoryGuards consensus
8802 parameter. Implements ticket 12688.
8805 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
8806 implementation that caused incorrect results on 32-bit
8807 implementations when certain malformed inputs were used along with
8808 a small class of private ntor keys. This bug does not currently
8809 appear to allow an attacker to learn private keys or impersonate a
8810 Tor server, but it could provide a means to distinguish 32-bit Tor
8811 implementations from 64-bit Tor implementations. Fixes bug 12694;
8812 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
8816 - Warn and drop the circuit if we receive an inbound 'relay early'
8817 cell. Those used to be normal to receive on hidden service circuits
8818 due to bug 1038, but the buggy Tor versions are long gone from
8819 the network so we can afford to resume watching for them. Resolves
8820 the rest of bug 1038; bugfix on 0.2.1.19.
8821 - Correct a confusing error message when trying to extend a circuit
8822 via the control protocol but we don't know a descriptor or
8823 microdescriptor for one of the specified relays. Fixes bug 12718;
8824 bugfix on 0.2.3.1-alpha.
8825 - Avoid an illegal read from stack when initializing the TLS
8826 module using a version of OpenSSL without all of the ciphers
8827 used by the v2 link handshake. Fixes bug 12227; bugfix on
8828 0.2.4.8-alpha. Found by "starlight".
8831 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
8835 Changes in version 0.2.5.5-alpha - 2014-06-18
8836 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
8837 0.2.5.x release series, including a couple of DoS issues, some
8838 performance regressions, a large number of bugs affecting the Linux
8839 seccomp2 sandbox code, and various other bugfixes. It also adds
8840 diagnostic bugfixes for a few tricky issues that we're trying to
8843 o Major features (security, traffic analysis resistance):
8844 - Several major improvements to the algorithm used to decide when to
8845 close TLS connections. Previous versions of Tor closed connections
8846 at a fixed interval after the last time a non-padding cell was
8847 sent over the connection, regardless of the target of the
8848 connection. Now, we randomize the intervals by adding up to 50% of
8849 their base value, we measure the length of time since connection
8850 last had at least one circuit, and we allow connections to known
8851 ORs to remain open a little longer (15 minutes instead of 3
8852 minutes minimum). These changes should improve Tor's resistance
8853 against some kinds of traffic analysis, and lower some overhead
8854 from needlessly closed connections. Fixes ticket 6799.
8855 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
8857 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
8858 - Fix a memory leak that could occur if a microdescriptor parse
8859 fails during the tokenizing step. This bug could enable a memory
8860 exhaustion attack by directory servers. Fixes bug 11649; bugfix
8863 o Major bugfixes (security, directory authorities):
8864 - Directory authorities now include a digest of each relay's
8865 identity key as a part of its microdescriptor.
8867 This is a workaround for bug 11743 (reported by "cypherpunks"),
8868 where Tor clients do not support receiving multiple
8869 microdescriptors with the same SHA256 digest in the same
8870 consensus. When clients receive a consensus like this, they only
8871 use one of the relays. Without this fix, a hostile relay could
8872 selectively disable some client use of target relays by
8873 constructing a router descriptor with a different identity and the
8874 same microdescriptor parameters and getting the authorities to
8875 list it in a microdescriptor consensus. This fix prevents an
8876 attacker from causing a microdescriptor collision, because the
8877 router's identity is not forgeable.
8879 o Major bugfixes (relay):
8880 - Use a direct dirport connection when uploading non-anonymous
8881 descriptors to the directory authorities. Previously, relays would
8882 incorrectly use tunnel connections under a fairly wide variety of
8883 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
8884 - When a circuit accidentally has the same circuit ID for its
8885 forward and reverse direction, correctly detect the direction of
8886 cells using that circuit. Previously, this bug made roughly one
8887 circuit in a million non-functional. Fixes bug 12195; this is a
8888 bugfix on every version of Tor.
8890 o Major bugfixes (client, pluggable transports):
8891 - When managing pluggable transports, use OS notification facilities
8892 to learn if they have crashed, and don't attempt to kill any
8893 process that has already exited. Fixes bug 8746; bugfix
8896 o Minor features (diagnostic):
8897 - When logging a warning because of bug 7164, additionally check the
8898 hash table for consistency (as proposed on ticket 11737). This may
8899 help diagnose bug 7164.
8900 - When we log a heartbeat, log how many one-hop circuits we have
8901 that are at least 30 minutes old, and log status information about
8902 a few of them. This is an attempt to track down bug 8387.
8903 - When encountering an unexpected CR while writing text to a file on
8904 Windows, log the name of the file. Should help diagnosing
8906 - Give more specific warnings when a client notices that an onion
8907 handshake has failed. Fixes ticket 9635.
8908 - Add significant new logging code to attempt to diagnose bug 12184,
8909 where relays seem to run out of available circuit IDs.
8910 - Improve the diagnostic log message for bug 8387 even further to
8911 try to improve our odds of figuring out why one-hop directory
8912 circuits sometimes do not get closed.
8914 o Minor features (security, memory management):
8915 - Memory allocation tricks (mempools and buffer freelists) are now
8916 disabled by default. You can turn them back on with
8917 --enable-mempools and --enable-buf-freelists respectively. We're
8918 disabling these features because malloc performance is good enough
8919 on most platforms, and a similar feature in OpenSSL exacerbated
8920 exploitation of the Heartbleed attack. Resolves ticket 11476.
8922 o Minor features (security):
8923 - Apply the secure SipHash-2-4 function to the hash table mapping
8924 circuit IDs and channels to circuits. We missed this one when we
8925 were converting all the other hash functions to use SipHash back
8926 in 0.2.5.3-alpha. Resolves ticket 11750.
8928 o Minor features (build):
8929 - The configure script has a --disable-seccomp option to turn off
8930 support for libseccomp on systems that have it, in case it (or
8931 Tor's use of it) is broken. Resolves ticket 11628.
8933 o Minor features (other):
8934 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
8937 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
8938 - When running a hidden service, do not allow TunneledDirConns 0;
8939 this will keep the hidden service from running, and also
8940 make it publish its descriptors directly over HTTP. Fixes bug 10849;
8941 bugfix on 0.2.1.1-alpha.
8943 o Minor bugfixes (performance):
8944 - Avoid a bug where every successful connection made us recompute
8945 the flag telling us whether we have sufficient information to
8946 build circuits. Previously, we would forget our cached value
8947 whenever we successfully opened a channel (or marked a router as
8948 running or not running for any other reason), regardless of
8949 whether we had previously believed the router to be running. This
8950 forced us to run an expensive update operation far too often.
8951 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
8952 - Avoid using tor_memeq() for checking relay cell integrity. This
8953 removes a possible performance bottleneck. Fixes part of bug
8954 12169; bugfix on 0.2.1.31.
8956 o Minor bugfixes (compilation):
8957 - Fix compilation of test_status.c when building with MVSC. Bugfix
8958 on 0.2.5.4-alpha. Patch from Gisle Vanem.
8959 - Resolve GCC complaints on OpenBSD about discarding constness in
8960 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
8961 on 0.1.1.23. Patch from Dana Koch.
8962 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
8963 treatment of long and time_t as comparable types. Fixes part of
8964 bug 11633. Patch from Dana Koch.
8965 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
8966 11623; bugfix on 0.2.5.3-alpha.
8967 - When deciding whether to build the 64-bit curve25519
8968 implementation, detect platforms where we can compile 128-bit
8969 arithmetic but cannot link it. Fixes bug 11729; bugfix on
8970 0.2.4.8-alpha. Patch from "conradev".
8971 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
8972 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
8973 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
8976 o Minor bugfixes (Directory server):
8977 - When sending a compressed set of descriptors or microdescriptors,
8978 make sure to finalize the zlib stream. Previously, we would write
8979 all the compressed data, but if the last descriptor we wanted to
8980 send was missing or too old, we would not mark the stream as
8981 finished. This caused problems for decompression tools. Fixes bug
8982 11648; bugfix on 0.1.1.23.
8984 o Minor bugfixes (Linux seccomp sandbox):
8985 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
8986 11622; bugfix on 0.2.5.1-alpha.
8987 - Avoid crashing when re-opening listener ports with the seccomp
8988 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
8989 - Avoid crashing with the seccomp sandbox enabled along with
8990 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
8991 - When we receive a SIGHUP with the sandbox enabled, correctly
8992 support rotating our log files. Fixes bug 12032; bugfix
8994 - Avoid crash when running with sandboxing enabled and
8995 DirReqStatistics not disabled. Fixes bug 12035; bugfix
8997 - Fix a "BUG" warning when trying to write bridge-stats files with
8998 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
9000 - Prevent the sandbox from crashing on startup when run with the
9001 --enable-expensive-hardening configuration option. Fixes bug
9002 11477; bugfix on 0.2.5.4-alpha.
9003 - When running with DirPortFrontPage and sandboxing both enabled,
9004 reload the DirPortFrontPage correctly when restarting. Fixes bug
9005 12028; bugfix on 0.2.5.1-alpha.
9006 - Don't try to enable the sandbox when using the Tor binary to check
9007 its configuration, hash a passphrase, or so on. Doing so was
9008 crashing on startup for some users. Fixes bug 11609; bugfix
9010 - Avoid warnings when running with sandboxing and node statistics
9011 enabled at the same time. Fixes part of 12064; bugfix on
9012 0.2.5.1-alpha. Patch from Michael Wolf.
9013 - Avoid warnings when running with sandboxing enabled at the same
9014 time as cookie authentication, hidden services, or directory
9015 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
9016 - Do not allow options that require calls to exec to be enabled
9017 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
9018 bug 12043; bugfix on 0.2.5.1-alpha.
9019 - Handle failures in getpwnam()/getpwuid() when running with the
9020 User option set and the Linux syscall sandbox enabled. Fixes bug
9021 11946; bugfix on 0.2.5.1-alpha.
9022 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
9023 to avoid calling getaddrinfo() after installing the sandbox
9024 filters. Previously, it preloaded a cache with the IPv4 address
9025 for our hostname, and nothing else. Now, it loads the cache with
9026 every address that it used to initialize the Tor process. Fixes
9027 bug 11970; bugfix on 0.2.5.1-alpha.
9029 o Minor bugfixes (pluggable transports):
9030 - Enable the ExtORPortCookieAuthFile option, to allow changing the
9031 default location of the authentication token for the extended OR
9032 Port as used by sever-side pluggable transports. We had
9033 implemented this option before, but the code to make it settable
9034 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
9035 - Avoid another 60-second delay when starting Tor in a pluggable-
9036 transport-using configuration when we already have cached
9037 descriptors for our bridges. Fixes bug 11965; bugfix
9040 o Minor bugfixes (client):
9041 - Avoid "Tried to open a socket with DisableNetwork set" warnings
9042 when starting a client with bridges configured and DisableNetwork
9043 set. (Tor launcher starts Tor with DisableNetwork set the first
9044 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
9046 o Minor bugfixes (testing):
9047 - The Python parts of the test scripts now work on Python 3 as well
9048 as Python 2, so systems where '/usr/bin/python' is Python 3 will
9049 no longer have the tests break. Fixes bug 11608; bugfix
9051 - When looking for versions of python that we could run the tests
9052 with, check for "python2.7" and "python3.3"; previously we were
9053 only looking for "python", "python2", and "python3". Patch from
9054 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
9055 - Fix all valgrind warnings produced by the unit tests. There were
9056 over a thousand memory leak warnings previously, mostly produced
9057 by forgetting to free things in the unit test code. Fixes bug
9058 11618, bugfixes on many versions of Tor.
9060 o Minor bugfixes (tor-fw-helper):
9061 - Give a correct log message when tor-fw-helper fails to launch.
9062 (Previously, we would say something like "tor-fw-helper sent us a
9063 string we could not parse".) Fixes bug 9781; bugfix
9066 o Minor bugfixes (relay, threading):
9067 - Check return code on spawn_func() in cpuworker code, so that we
9068 don't think we've spawned a nonworking cpuworker and write junk to
9069 it forever. Fix related to bug 4345; bugfix on all released Tor
9070 versions. Found by "skruffy".
9071 - Use a pthread_attr to make sure that spawn_func() cannot return an
9072 error while at the same time launching a thread. Fix related to
9073 bug 4345; bugfix on all released Tor versions. Reported
9076 o Minor bugfixes (relay, oom prevention):
9077 - Correctly detect the total available system memory. We tried to do
9078 this in 0.2.5.4-alpha, but the code was set up to always return an
9079 error value, even on success. Fixes bug 11805; bugfix
9082 o Minor bugfixes (relay, other):
9083 - We now drop CREATE cells for already-existent circuit IDs and for
9084 zero-valued circuit IDs, regardless of other factors that might
9085 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
9087 - Avoid an illegal read from stack when initializing the TLS module
9088 using a version of OpenSSL without all of the ciphers used by the
9089 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
9091 - When rejecting DATA cells for stream_id zero, still count them
9092 against the circuit's deliver window so that we don't fail to send
9093 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
9095 o Minor bugfixes (logging):
9096 - Fix a misformatted log message about delayed directory fetches.
9097 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
9098 - Squelch a spurious LD_BUG message "No origin circuit for
9099 successful SOCKS stream" in certain hidden service failure cases;
9103 - Include a tor.service file in contrib/dist for use with systemd.
9104 Some distributions will be able to use this file unmodified;
9105 others will need to tweak it, or write their own. Patch from Jamie
9106 Nguyen; resolves ticket 8368.
9109 - Clean up several option names in the manpage to match their real
9110 names, add the missing documentation for a couple of testing and
9111 directory authority options, remove the documentation for a
9112 V2-directory fetching option that no longer exists. Resolves
9114 - Correct the documenation so that it lists the correct directory
9115 for the stats files. (They are in a subdirectory called "stats",
9117 - In the manpage, move more authority-only options into the
9118 directory authority section so that operators of regular directory
9119 caches don't get confused.
9122 - The contrib directory has been sorted and tidied. Before, it was
9123 an unsorted dumping ground for useful and not-so-useful things.
9124 Now, it is divided based on functionality, and the items which
9125 seemed to be nonfunctional or useless have been removed. Resolves
9126 ticket 8966; based on patches from "rl1987".
9129 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
9130 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
9131 - The TunnelDirConns and PreferTunnelledDirConns options no longer
9132 exist; tunneled directory connections have been available since
9133 0.1.2.5-alpha, and turning them off is not a good idea. This is a
9134 brute-force fix for 10849, where "TunnelDirConns 0" would break
9138 Changes in version 0.2.4.22 - 2014-05-16
9139 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
9140 alpha release series. These include blocking all authority signing
9141 keys that may have been affected by the OpenSSL "heartbleed" bug,
9142 choosing a far more secure set of TLS ciphersuites by default, closing
9143 a couple of memory leaks that could be used to run a target relay out
9144 of RAM, and several others.
9146 o Major features (security, backport from 0.2.5.4-alpha):
9147 - Block authority signing keys that were used on authorities
9148 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9149 don't have any evidence that these keys _were_ compromised; we're
9150 doing this to be prudent.) Resolves ticket 11464.
9152 o Major bugfixes (security, OOM):
9153 - Fix a memory leak that could occur if a microdescriptor parse
9154 fails during the tokenizing step. This bug could enable a memory
9155 exhaustion attack by directory servers. Fixes bug 11649; bugfix
9158 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
9159 - The relay ciphersuite list is now generated automatically based on
9160 uniform criteria, and includes all OpenSSL ciphersuites with
9161 acceptable strength and forward secrecy. Previously, we had left
9162 some perfectly fine ciphersuites unsupported due to omission or
9163 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9164 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9165 - Relays now trust themselves to have a better view than clients of
9166 which TLS ciphersuites are better than others. (Thanks to bug
9167 11513, the relay list is now well-considered, whereas the client
9168 list has been chosen mainly for anti-fingerprinting purposes.)
9169 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9170 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9171 AES128. Resolves ticket 11528.
9172 - Clients now try to advertise the same list of ciphersuites as
9173 Firefox 28. This change enables selection of (fast) GCM
9174 ciphersuites, disables some strange old ciphers, and stops
9175 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9176 Resolves ticket 11438.
9178 o Minor bugfixes (configuration, security):
9179 - When running a hidden service, do not allow TunneledDirConns 0:
9180 trying to set that option together with a hidden service would
9181 otherwise prevent the hidden service from running, and also make
9182 it publish its descriptors directly over HTTP. Fixes bug 10849;
9183 bugfix on 0.2.1.1-alpha.
9185 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
9186 - Avoid sending a garbage value to the controller when a circuit is
9187 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
9189 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
9190 - Stop leaking memory when we successfully resolve a PTR record.
9191 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
9193 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
9194 - Avoid 60-second delays in the bootstrapping process when Tor is
9195 launching for a second time while using bridges. Fixes bug 9229;
9196 bugfix on 0.2.0.3-alpha.
9198 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
9199 - Give the correct URL in the warning message when trying to run a
9200 relay on an ancient version of Windows. Fixes bug 9393.
9202 o Minor bugfixes (compilation):
9203 - Fix a compilation error when compiling with --disable-curve25519.
9204 Fixes bug 9700; bugfix on 0.2.4.17-rc.
9207 - Downgrade the warning severity for the the "md was still
9208 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
9209 for trying to diagnose this bug, and the current warning in
9210 earlier versions of tor achieves nothing useful. Addresses warning
9213 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
9214 - When we run out of usable circuit IDs on a channel, log only one
9215 warning for the whole channel, and describe how many circuits
9216 there were on the channel. Fixes part of ticket 11553.
9218 o Minor features (security, backport from 0.2.5.4-alpha):
9219 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
9220 leave the default at 8GBytes), to better support Raspberry Pi
9221 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
9223 o Documentation (backport from 0.2.5.4-alpha):
9224 - Correctly document that we search for a system torrc file before
9225 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
9229 Changes in version 0.2.5.4-alpha - 2014-04-25
9230 Tor 0.2.5.4-alpha includes several security and performance
9231 improvements for clients and relays, including blacklisting authority
9232 signing keys that were used while susceptible to the OpenSSL
9233 "heartbleed" bug, fixing two expensive functions on busy relays,
9234 improved TLS ciphersuite preference lists, support for run-time
9235 hardening on compilers that support AddressSanitizer, and more work on
9236 the Linux sandbox code.
9238 There are also several usability fixes for clients (especially clients
9239 that use bridges), two new TransPort protocols supported (one on
9240 OpenBSD, one on FreeBSD), and various other bugfixes.
9242 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
9243 have accumulated many known flaws; everyone should upgrade.
9245 o Major features (security):
9246 - If you don't specify MaxMemInQueues yourself, Tor now tries to
9247 pick a good value based on your total system memory. Previously,
9248 the default was always 8 GB. You can still override the default by
9249 setting MaxMemInQueues yourself. Resolves ticket 11396.
9250 - Block authority signing keys that were used on authorities
9251 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9252 don't have any evidence that these keys _were_ compromised; we're
9253 doing this to be prudent.) Resolves ticket 11464.
9255 o Major features (relay performance):
9256 - Speed up server-side lookups of rendezvous and introduction point
9257 circuits by using hashtables instead of linear searches. These
9258 functions previously accounted between 3 and 7% of CPU usage on
9259 some busy relays. Resolves ticket 9841.
9260 - Avoid wasting CPU when extending a circuit over a channel that is
9261 nearly out of circuit IDs. Previously, we would do a linear scan
9262 over possible circuit IDs before finding one or deciding that we
9263 had exhausted our possibilities. Now, we try at most 64 random
9264 circuit IDs before deciding that we probably won't succeed. Fixes
9265 a possible root cause of ticket 11553.
9267 o Major features (seccomp2 sandbox, Linux only):
9268 - The seccomp2 sandbox can now run a test network for multiple hours
9269 without crashing. The sandbox is still experimental, and more bugs
9270 will probably turn up. To try it, enable "Sandbox 1" on a Linux
9271 host. Resolves ticket 11351.
9272 - Strengthen sandbox code: the sandbox can now test the arguments
9273 for rename(), and blocks _sysctl() entirely. Resolves another part
9275 - When the sandbox blocks a system call, it now tries to log a stack
9276 trace before exiting. Resolves ticket 11465.
9278 o Major bugfixes (TLS cipher selection):
9279 - The relay ciphersuite list is now generated automatically based on
9280 uniform criteria, and includes all OpenSSL ciphersuites with
9281 acceptable strength and forward secrecy. Previously, we had left
9282 some perfectly fine ciphersuites unsupported due to omission or
9283 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9284 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9285 - Relays now trust themselves to have a better view than clients of
9286 which TLS ciphersuites are better than others. (Thanks to bug
9287 11513, the relay list is now well-considered, whereas the client
9288 list has been chosen mainly for anti-fingerprinting purposes.)
9289 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9290 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9291 AES128. Resolves ticket 11528.
9292 - Clients now try to advertise the same list of ciphersuites as
9293 Firefox 28. This change enables selection of (fast) GCM
9294 ciphersuites, disables some strange old ciphers, and stops
9295 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9296 Resolves ticket 11438.
9298 o Major bugfixes (bridge client):
9299 - Avoid 60-second delays in the bootstrapping process when Tor is
9300 launching for a second time while using bridges. Fixes bug 9229;
9301 bugfix on 0.2.0.3-alpha.
9303 o Minor features (transparent proxy, *BSD):
9304 - Support FreeBSD's ipfw firewall interface for TransPort ports on
9305 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
9306 10267; patch from "yurivict".
9307 - Support OpenBSD's divert-to rules with the pf firewall for
9308 transparent proxy ports. To enable it, set "TransProxyType
9309 pf-divert". This allows Tor to run a TransPort transparent proxy
9310 port on OpenBSD 4.4 or later without root privileges. See the
9311 pf.conf(5) manual page for information on configuring pf to use
9312 divert-to rules. Closes ticket 10896; patch from Dana Koch.
9314 o Minor features (security):
9315 - New --enable-expensive-hardening option to enable security
9316 hardening options that consume nontrivial amounts of CPU and
9317 memory. Right now, this includes AddressSanitizer and UbSan, which
9318 are supported in newer versions of GCC and Clang. Closes ticket
9321 o Minor features (log verbosity):
9322 - Demote the message that we give when a flushing connection times
9323 out for too long from NOTICE to INFO. It was usually meaningless.
9324 Resolves ticket 5286.
9325 - Don't log so many notice-level bootstrapping messages at startup
9326 about downloading descriptors. Previously, we'd log a notice
9327 whenever we learned about more routers. Now, we only log a notice
9328 at every 5% of progress. Fixes bug 9963.
9329 - Warn less verbosely when receiving a malformed
9330 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
9331 - When we run out of usable circuit IDs on a channel, log only one
9332 warning for the whole channel, and describe how many circuits
9333 there were on the channel. Fixes part of ticket 11553.
9335 o Minor features (relay):
9336 - If a circuit timed out for at least 3 minutes, check if we have a
9337 new external IP address, and publish a new descriptor with the new
9338 IP address if it changed. Resolves ticket 2454.
9340 o Minor features (controller):
9341 - Make the entire exit policy available from the control port via
9342 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
9344 - Because of the fix for ticket 11396, the real limit for memory
9345 usage may no longer match the configured MaxMemInQueues value. The
9346 real limit is now exposed via GETINFO limits/max-mem-in-queues.
9348 o Minor features (bridge client):
9349 - Report a more useful failure message when we can't connect to a
9350 bridge because we don't have the right pluggable transport
9351 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
9353 o Minor features (diagnostic):
9354 - Add more log messages to diagnose bug 7164, which causes
9355 intermittent "microdesc_free() called but md was still referenced"
9356 warnings. We now include more information, to figure out why we
9357 might be cleaning a microdescriptor for being too old if it's
9358 still referenced by a live node_t object.
9360 o Minor bugfixes (client, DNSPort):
9361 - When using DNSPort, try to respond to AAAA requests with AAAA
9362 answers. Previously, we hadn't looked at the request type when
9363 deciding which answer type to prefer. Fixes bug 10468; bugfix on
9365 - When receiving a DNS query for an unsupported record type, reply
9366 with no answer rather than with a NOTIMPL error. This behavior
9367 isn't correct either, but it will break fewer client programs, we
9368 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
9371 o Minor bugfixes (exit relay):
9372 - Stop leaking memory when we successfully resolve a PTR record.
9373 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
9375 o Minor bugfixes (bridge client):
9376 - Stop accepting bridge lines containing hostnames. Doing so would
9377 cause clients to perform DNS requests on the hostnames, which was
9378 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
9379 - Avoid a 60-second delay in the bootstrapping process when a Tor
9380 client with pluggable transports re-reads its configuration at
9381 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
9383 o Minor bugfixes (client, logging during bootstrap):
9384 - Warn only once if we start logging in an unsafe way. Previously,
9385 we complain as many times as we had problems. Fixes bug 9870;
9386 bugfix on 0.2.5.1-alpha.
9387 - Only report the first fatal bootstrap error on a given OR
9388 connection. This stops us from telling the controller bogus error
9389 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
9390 - Be more helpful when trying to run sandboxed on Linux without
9391 libseccomp. Instead of saying "Sandbox is not implemented on this
9392 platform", we now explain that we need to be built with
9393 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
9394 - Avoid generating spurious warnings when starting with
9395 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
9398 o Minor bugfixes (closing OR connections):
9399 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
9400 check if it's an or_connection_t and correctly call
9401 connection_or_close_for_error() rather than
9402 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
9404 - When closing all connections on setting DisableNetwork to 1, use
9405 connection_or_close_normally() rather than closing OR connections
9406 out from under the channel layer. Fixes bug 11306; bugfix on
9409 o Minor bugfixes (controller):
9410 - Avoid sending a garbage value to the controller when a circuit is
9411 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
9413 o Minor bugfixes (tor-fw-helper):
9414 - Allow tor-fw-helper to build again by adding src/ext to its
9415 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
9417 o Minor bugfixes (bridges):
9418 - Avoid potential crashes or bad behavior when launching a
9419 server-side managed proxy with ORPort or ExtORPort temporarily
9420 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
9422 o Minor bugfixes (platform-specific):
9423 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
9424 bug 11426; bugfix on 0.2.5.3-alpha.
9425 - When dumping a malformed directory object to disk, save it in
9426 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
9428 - Don't report failures from make_socket_reuseable() on incoming
9429 sockets on OSX: this can happen when incoming connections close
9430 early. Fixes bug 10081.
9432 o Minor bugfixes (trivial memory leaks):
9433 - Fix a small memory leak when signing a directory object. Fixes bug
9434 11275; bugfix on 0.2.4.13-alpha.
9435 - Free placeholder entries in our circuit table at exit; fixes a
9436 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
9437 - Don't re-initialize a second set of OpenSSL mutexes when starting
9438 up. Previously, we'd make one set of mutexes, and then immediately
9439 replace them with another. Fixes bug 11726; bugfix on
9441 - Resolve some memory leaks found by coverity in the unit tests, on
9442 exit in tor-gencert, and on a failure to compute digests for our
9443 own keys when generating a v3 networkstatus vote. These leaks
9444 should never have affected anyone in practice.
9446 o Minor bugfixes (hidden service):
9447 - Only retry attempts to connect to a chosen rendezvous point 8
9448 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
9450 o Minor bugfixes (misc code correctness):
9451 - Fix various instances of undefined behavior in channeltls.c,
9452 tor_memmem(), and eventdns.c that would cause us to construct
9453 pointers to memory outside an allocated object. (These invalid
9454 pointers were not accessed, but C does not even allow them to
9455 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
9456 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
9457 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
9458 fix some miscellaneous errors in our tests and codebase. Fixes bug
9459 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
9460 - Always check return values for unlink, munmap, UnmapViewOfFile;
9461 check strftime return values more often. In some cases all we can
9462 do is report a warning, but this may help prevent deeper bugs from
9463 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
9465 - Fix numerous warnings from the clang "scan-build" static analyzer.
9466 Some of these are programming style issues; some of them are false
9467 positives that indicated awkward code; some are undefined behavior
9468 cases related to constructing (but not using) invalid pointers;
9469 some are assumptions about API behavior; some are (harmlessly)
9470 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
9471 correct; and one or two are genuine bugs that weren't reachable
9472 from the rest of the program. Fixes bug 8793; bugfixes on many,
9476 - Build the torify.1 manpage again. Previously, we were only trying
9477 to build it when also building tor-fw-helper. That's why we didn't
9478 notice that we'd broken the ability to build it. Fixes bug 11321;
9479 bugfix on 0.2.5.1-alpha.
9480 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
9481 11061; bugfix on 0.2.4.7-alpha.
9482 - Correctly document that we search for a system torrc file before
9483 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
9485 - Resolve warnings from Doxygen.
9487 o Code simplifications and refactoring:
9488 - Remove is_internal_IP() function. Resolves ticket 4645.
9489 - Remove unused function circuit_dump_by_chan from circuitlist.c.
9490 Closes issue 9107; patch from "marek".
9491 - Change our use of the ENUM_BF macro to avoid declarations that
9494 o Deprecated versions:
9495 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
9496 attention for some while. Directory authorities no longer accept
9497 descriptors from relays running any version of Tor prior to Tor
9498 0.2.3.16-alpha. Resolves ticket 11149.
9501 - New macros in test.h to simplify writing mock-functions for unit
9502 tests. Part of ticket 11507. Patch from Dana Koch.
9503 - Complete tests for the status.c module. Resolves ticket 11507.
9504 Patch from Dana Koch.
9507 - Remove all code for the long unused v1 directory protocol.
9508 Resolves ticket 11070.
9511 Changes in version 0.2.5.3-alpha - 2014-03-22
9512 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
9513 two new anti-DoS features for Tor relays, resolves a bug that kept
9514 SOCKS5 support for IPv6 from working, fixes several annoying usability
9515 issues for bridge users, and removes more old code for unused
9518 The Tor 0.2.5.x release series is now in patch-freeze: no feature
9519 patches not already written will be considered for inclusion in 0.2.5.x.
9521 o Major features (relay security, DoS-resistance):
9522 - When deciding whether we have run out of memory and we need to
9523 close circuits, also consider memory allocated in buffers for
9524 streams attached to each circuit.
9526 This change, which extends an anti-DoS feature introduced in
9527 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
9528 better resist more memory-based DoS attacks than before. Since the
9529 MaxMemInCellQueues option now applies to all queues, it is renamed
9530 to MaxMemInQueues. This feature fixes bug 10169.
9531 - Avoid hash-flooding denial-of-service attacks by using the secure
9532 SipHash-2-4 hash function for our hashtables. Without this
9533 feature, an attacker could degrade performance of a targeted
9534 client or server by flooding their data structures with a large
9535 number of entries to be stored at the same hash table position,
9536 thereby slowing down the Tor instance. With this feature, hash
9537 table positions are derived from a randomized cryptographic key,
9538 and an attacker cannot predict which entries will collide. Closes
9540 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
9541 the default at 8GBytes), to better support Raspberry Pi users. Fixes
9542 bug 9686; bugfix on 0.2.4.14-alpha.
9544 o Minor features (bridges, pluggable transports):
9545 - Bridges now write the SHA1 digest of their identity key
9546 fingerprint (that is, a hash of a hash of their public key) to
9547 notice-level logs, and to a new hashed-fingerprint file. This
9548 information will help bridge operators look up their bridge in
9549 Globe and similar tools. Resolves ticket 10884.
9550 - Improve the message that Tor displays when running as a bridge
9551 using pluggable transports without an Extended ORPort listener.
9552 Also, log the message in the log file too. Resolves ticket 11043.
9554 o Minor features (other):
9555 - Add a new option, PredictedPortsRelevanceTime, to control how long
9556 after having received a request to connect to a given port Tor
9557 will try to keep circuits ready in anticipation of future requests
9558 for that port. Patch from "unixninja92"; implements ticket 9176.
9559 - Generate a warning if any ports are listed in the SocksPolicy,
9560 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
9561 AuthDirBadExit options. (These options only support address
9562 ranges.) Fixes part of ticket 11108.
9563 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
9566 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
9567 - Build without warnings under clang 3.4. (We have some macros that
9568 define static functions only some of which will get used later in
9569 the module. Starting with clang 3.4, these give a warning unless the
9570 unused attribute is set on them.) Resolves ticket 10904.
9571 - Fix build warnings about missing "a2x" comment when building the
9572 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
9573 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
9575 o Minor bugfixes (client):
9576 - Improve the log message when we can't connect to a hidden service
9577 because all of the hidden service directory nodes hosting its
9578 descriptor are excluded. Improves on our fix for bug 10722, which
9579 was a bugfix on 0.2.0.10-alpha.
9580 - Raise a control port warning when we fail to connect to all of
9581 our bridges. Previously, we didn't inform the controller, and
9582 the bootstrap process would stall. Fixes bug 11069; bugfix on
9584 - Exit immediately when a process-owning controller exits.
9585 Previously, tor relays would wait for a little while after their
9586 controller exited, as if they had gotten an INT signal -- but this
9587 was problematic, since there was no feedback for the user. To do a
9588 clean shutdown, controllers should send an INT signal and give Tor
9589 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
9590 - Stop attempting to connect to bridges before our pluggable
9591 transports are configured (harmless but resulted in some erroneous
9592 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
9593 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
9594 generating incorrect SOCKS5 responses, and confusing client
9595 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
9597 o Minor bugfixes (relays and bridges):
9598 - Avoid crashing on a malformed resolv.conf file when running a
9599 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
9600 - Non-exit relays no longer launch mock DNS requests to check for
9601 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
9602 non-exit relays stopped servicing DNS requests. Fixes bug 965;
9603 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
9604 - Bridges now report complete directory request statistics. Related
9605 to bug 5824; bugfix on 0.2.2.1-alpha.
9606 - Bridges now never collect statistics that were designed for
9607 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
9608 - Stop giving annoying warning messages when we decide not to launch
9609 a pluggable transport proxy that we don't need (because there are
9610 no bridges configured to use it). Resolves ticket 5018; bugfix
9612 - Give the correct URL in the warning message when trying to run a
9613 relay on an ancient version of Windows. Fixes bug 9393.
9615 o Minor bugfixes (backtrace support):
9616 - Support automatic backtraces on more platforms by using the
9617 "-fasynchronous-unwind-tables" compiler option. This option is
9618 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
9619 is on by default and table generation is not. This doesn't yet
9620 add Windows support; only Linux, OSX, and some BSDs are affected.
9621 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
9622 - Avoid strange behavior if two threads hit failed assertions at the
9623 same time and both try to log backtraces at once. (Previously, if
9624 this had happened, both threads would have stored their intermediate
9625 results in the same buffer, and generated junk outputs.) Reported by
9626 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
9627 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
9628 0.2.5.2-alpha; patch from Nick Hopper.
9630 o Minor bugfixes (unit tests):
9631 - Fix a small bug in the unit tests that might have made the tests
9632 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
9633 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
9636 - Remove all remaining code related to version-0 hidden service
9637 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
9638 the rest of bug 10841.
9641 - Document in the manpage that "KBytes" may also be written as
9642 "kilobytes" or "KB", that "Kbits" may also be written as
9643 "kilobits", and so forth. Closes ticket 9222.
9644 - Document that the ClientOnly config option overrides ORPort.
9645 Our old explanation made ClientOnly sound as though it did
9646 nothing at all. Resolves bug 9059.
9647 - Explain that SocksPolicy, DirPolicy, and similar options don't
9648 take port arguments. Fixes the other part of ticket 11108.
9649 - Fix a comment about the rend_server_descriptor_t.protocols field
9650 to more accurately describe its range. Also, make that field
9651 unsigned, to more accurately reflect its usage. Fixes bug 9099;
9652 bugfix on 0.2.1.5-alpha.
9653 - Fix the manpage's description of HiddenServiceAuthorizeClient:
9654 the maximum client name length is 16, not 19. Fixes bug 11118;
9655 bugfix on 0.2.1.6-alpha.
9657 o Code simplifications and refactoring:
9658 - Get rid of router->address, since in all cases it was just the
9659 string representation of router->addr. Resolves ticket 5528.
9661 o Test infrastructure:
9662 - Update to the latest version of tinytest.
9663 - Improve the tinytest implementation of string operation tests so
9664 that comparisons with NULL strings no longer crash the tests; they
9665 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
9668 Changes in version 0.2.4.21 - 2014-02-28
9669 Tor 0.2.4.21 further improves security against potential adversaries who
9670 find breaking 1024-bit crypto doable, and backports several stability
9671 and robustness patches from the 0.2.5 branch.
9673 o Major features (client security):
9674 - When we choose a path for a 3-hop circuit, make sure it contains
9675 at least one relay that supports the NTor circuit extension
9676 handshake. Otherwise, there is a chance that we're building
9677 a circuit that's worth attacking by an adversary who finds
9678 breaking 1024-bit crypto doable, and that chance changes the game
9679 theory. Implements ticket 9777.
9682 - Do not treat streams that fail with reason
9683 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
9684 since it could also indicate an ENETUNREACH connection error. Fixes
9685 part of bug 10777; bugfix on 0.2.4.8-alpha.
9687 o Code simplification and refactoring:
9688 - Remove data structures which were introduced to implement the
9689 CellStatistics option: they are now redundant with the new timestamp
9690 field in the regular packed_cell_t data structure, which we did
9691 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
9694 - Always clear OpenSSL bignums before freeing them -- even bignums
9695 that don't contain secrets. Resolves ticket 10793. Patch by
9697 - Build without warnings under clang 3.4. (We have some macros that
9698 define static functions only some of which will get used later in
9699 the module. Starting with clang 3.4, these give a warning unless the
9700 unused attribute is set on them.) Resolves ticket 10904.
9701 - Update geoip and geoip6 files to the February 7 2014 Maxmind
9702 GeoLite2 Country database.
9705 - Set the listen() backlog limit to the largest actually supported
9706 on the system, not to the value in a header file. Fixes bug 9716;
9707 bugfix on every released Tor.
9708 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
9709 exit node as a NOROUTE error, not an INTERNAL error, since they
9710 can apparently happen when trying to connect to the wrong sort
9711 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
9712 - Fix build warnings about missing "a2x" comment when building the
9713 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
9714 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
9715 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
9716 not entirely remove it from the connection lists. Fixes bug 9602;
9717 bugfix on 0.2.4.4-alpha.
9718 - Fix a segmentation fault in our benchmark code when running with
9719 Fedora's OpenSSL package, or any other OpenSSL that provides
9720 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
9721 - Turn "circuit handshake stats since last time" log messages into a
9722 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
9724 o Documentation fixes:
9725 - Document that all but one DirPort entry must have the NoAdvertise
9726 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
9729 Changes in version 0.2.5.2-alpha - 2014-02-13
9730 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
9731 like the "poor random number generation" fix and the "building too many
9732 circuits" fix. It also further improves security against potential
9733 adversaries who find breaking 1024-bit crypto doable, and launches
9734 pluggable transports on demand (which gets us closer to integrating
9735 pluggable transport support by default -- not to be confused with Tor
9736 bundles enabling pluggable transports and bridges by default).
9738 o Major features (client security):
9739 - When we choose a path for a 3-hop circuit, make sure it contains
9740 at least one relay that supports the NTor circuit extension
9741 handshake. Otherwise, there is a chance that we're building
9742 a circuit that's worth attacking by an adversary who finds
9743 breaking 1024-bit crypto doable, and that chance changes the game
9744 theory. Implements ticket 9777.
9745 - Clients now look at the "usecreatefast" consensus parameter to
9746 decide whether to use CREATE_FAST or CREATE cells for the first hop
9747 of their circuit. This approach can improve security on connections
9748 where Tor's circuit handshake is stronger than the available TLS
9749 connection security levels, but the tradeoff is more computational
9750 load on guard relays. Implements proposal 221. Resolves ticket 9386.
9752 o Major features (bridges):
9753 - Don't launch pluggable transport proxies if we don't have any
9754 bridges configured that would use them. Now we can list many
9755 pluggable transports, and Tor will dynamically start one when it
9756 hears a bridge address that needs it. Resolves ticket 5018.
9757 - The bridge directory authority now assigns status flags (Stable,
9758 Guard, etc) to bridges based on thresholds calculated over all
9759 Running bridges. Now bridgedb can finally make use of its features
9760 to e.g. include at least one Stable bridge in its answers. Fixes
9763 o Major features (other):
9764 - Extend ORCONN controller event to include an "ID" parameter,
9765 and add four new controller event types CONN_BW, CIRC_BW,
9766 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
9767 The new events are emitted in private Tor networks only, with the
9768 goal of being able to better track performance and load during
9769 full-network simulations. Implements proposal 218 and ticket 7359.
9770 - On some platforms (currently: recent OSX versions, glibc-based
9771 platforms that support the ELF format, and a few other
9772 Unix-like operating systems), Tor can now dump stack traces
9773 when a crash occurs or an assertion fails. By default, traces
9774 are dumped to stderr (if possible) and to any logs that are
9775 reporting errors. Implements ticket 9299.
9778 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
9779 not entirely remove it from the connection lists. Fixes bug 9602;
9780 bugfix on 0.2.4.4-alpha.
9781 - Do not treat streams that fail with reason
9782 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
9783 since it could also indicate an ENETUNREACH connection error. Fixes
9784 part of bug 10777; bugfix on 0.2.4.8-alpha.
9786 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
9787 - Do not allow OpenSSL engines to replace the PRNG, even when
9788 HardwareAccel is set. The only default builtin PRNG engine uses
9789 the Intel RDRAND instruction to replace the entire PRNG, and
9790 ignores all attempts to seed it with more entropy. That's
9791 cryptographically stupid: the right response to a new alleged
9792 entropy source is never to discard all previously used entropy
9793 sources. Fixes bug 10402; works around behavior introduced in
9794 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
9796 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
9797 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
9798 - Avoid launching spurious extra circuits when a stream is pending.
9799 This fixes a bug where any circuit that _wasn't_ unusable for new
9800 streams would be treated as if it were, causing extra circuits to
9801 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
9803 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
9804 - No longer stop reading or writing on cpuworker connections when
9805 our rate limiting buckets go empty. Now we should handle circuit
9806 handshake requests more promptly. Resolves bug 9731.
9807 - Stop trying to bootstrap all our directory information from
9808 only our first guard. Discovered while fixing bug 9946; bugfix
9811 o Minor features (bridges, pluggable transports):
9812 - Add threshold cutoffs to the networkstatus document created by
9813 the Bridge Authority. Fixes bug 1117.
9814 - On Windows, spawn background processes using the CREATE_NO_WINDOW
9815 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
9816 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
9817 Vidalia set this option for us.) Implements ticket 10297.
9819 o Minor features (security):
9820 - Always clear OpenSSL bignums before freeing them -- even bignums
9821 that don't contain secrets. Resolves ticket 10793. Patch by
9824 o Minor features (config options and command line):
9825 - Add an --allow-missing-torrc commandline option that tells Tor to
9826 run even if the configuration file specified by -f is not available.
9827 Implements ticket 10060.
9828 - Add support for the TPROXY transparent proxying facility on Linux.
9829 See documentation for the new TransProxyType option for more
9830 details. Implementation by "thomo". Closes ticket 10582.
9832 o Minor features (controller):
9833 - Add a new "HS_DESC" controller event that reports activities
9834 related to hidden service descriptors. Resolves ticket 8510.
9835 - New "DROPGUARDS" controller command to forget all current entry
9836 guards. Not recommended for ordinary use, since replacing guards
9837 too frequently makes several attacks easier. Resolves ticket 9934;
9840 o Minor features (build):
9841 - Assume that a user using ./configure --host wants to cross-compile,
9842 and give an error if we cannot find a properly named
9843 tool-chain. Add a --disable-tool-name-check option to proceed
9844 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
9845 - If we run ./configure and the compiler recognizes -fstack-protector
9846 but the linker rejects it, warn the user about a potentially missing
9847 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
9849 o Minor features (testing):
9850 - If Python is installed, "make check" now runs extra tests beyond
9851 the unit test scripts.
9852 - When bootstrapping a test network, sometimes very few relays get
9853 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
9854 specify a set of relays which should be voted Guard regardless of
9855 their uptime or bandwidth. Addresses ticket 9206.
9857 o Minor features (log messages):
9858 - When ServerTransportPlugin is set on a bridge, Tor can write more
9859 useful statistics about bridge use in its extrainfo descriptors,
9860 but only if the Extended ORPort ("ExtORPort") is set too. Add a
9861 log message to inform the user in this case. Resolves ticket 9651.
9862 - When receiving a new controller connection, log the origin address.
9863 Resolves ticket 9698; patch from "sigpipe".
9864 - When logging OpenSSL engine status at startup, log the status of
9865 more engines. Fixes ticket 10043; patch from Joshua Datko.
9866 - Turn "circuit handshake stats since last time" log messages into a
9867 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
9869 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
9870 - Improve the circuit queue out-of-memory handler. Previously, when
9871 we ran low on memory, we'd close whichever circuits had the most
9872 queued cells. Now, we close those that have the *oldest* queued
9873 cells, on the theory that those are most responsible for us
9874 running low on memory. Based on analysis from a forthcoming paper
9875 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
9876 - Generate bootstrapping status update events correctly when fetching
9877 microdescriptors. Fixes bug 9927.
9878 - Update to the October 2 2013 Maxmind GeoLite Country database.
9880 o Minor bugfixes (clients):
9881 - When closing a channel that has already been open, do not close
9882 pending circuits that were waiting to connect to the same relay.
9883 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
9886 o Minor bugfixes (relays):
9887 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
9888 exit node as a NOROUTE error, not an INTERNAL error, since they
9889 can apparently happen when trying to connect to the wrong sort
9890 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
9892 o Minor bugfixes (bridges):
9893 - Fix a bug where the first connection works to a bridge that uses a
9894 pluggable transport with client-side parameters, but we don't send
9895 the client-side parameters on subsequent connections. (We don't
9896 use any pluggable transports with client-side parameters yet,
9897 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
9898 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
9900 o Minor bugfixes (node selection):
9901 - If ExcludeNodes is set, consider non-excluded hidden service
9902 directory servers before excluded ones. Do not consider excluded
9903 hidden service directory servers at all if StrictNodes is
9904 set. (Previously, we would sometimes decide to connect to those
9905 servers, and then realize before we initiated a connection that
9906 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
9908 - If we set the ExitNodes option but it doesn't include any nodes
9909 that have the Exit flag, we would choose not to bootstrap. Now we
9910 bootstrap so long as ExitNodes includes nodes which can exit to
9911 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
9913 o Minor bugfixes (controller and command-line):
9914 - If changing a config option via "setconf" fails in a recoverable
9915 way, we used to nonetheless write our new control ports to the
9916 file described by the "ControlPortWriteToFile" option. Now we only
9917 write out that file if we successfully switch to the new config
9918 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
9919 - When a command-line option such as --version or --help that
9920 ordinarily implies --hush appears on the command line along with
9921 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
9922 only if it appeared later on the command line. Fixes bug 9578;
9923 bugfix on 0.2.5.1-alpha.
9925 o Minor bugfixes (code correctness):
9926 - Previously we used two temporary files when writing descriptors to
9927 disk; now we only use one. Fixes bug 1376.
9928 - Remove an erroneous (but impossible and thus harmless) pointer
9929 comparison that would have allowed compilers to skip a bounds
9930 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
9931 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
9932 - Fix an always-true assertion in pluggable transports code so it
9933 actually checks what it was trying to check. Fixes bug 10046;
9934 bugfix on 0.2.3.9-alpha. Found by "dcb".
9936 o Minor bugfixes (protocol correctness):
9937 - When receiving a VERSIONS cell with an odd number of bytes, close
9938 the connection immediately since the cell is malformed. Fixes bug
9939 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
9942 o Minor bugfixes (build):
9943 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
9944 turned off (that is, without support for v2 link handshakes). Fixes
9945 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
9946 - Fix compilation warnings and startup issues when running with
9947 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
9949 - Fix compilation on Solaris 9, which didn't like us having an
9950 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
9952 o Minor bugfixes (testing):
9953 - Fix a segmentation fault in our benchmark code when running with
9954 Fedora's OpenSSL package, or any other OpenSSL that provides
9955 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
9957 o Minor bugfixes (log messages):
9958 - Fix a bug where clients using bridges would report themselves
9959 as 50% bootstrapped even without a live consensus document.
9960 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
9961 - Suppress a warning where, if there's only one directory authority
9962 in the network, we would complain that votes and signatures cannot
9963 be uploaded to other directory authorities. Fixes bug 10842;
9964 bugfix on 0.2.2.26-beta.
9965 - Report bootstrapping progress correctly when we're downloading
9966 microdescriptors. We had updated our "do we have enough microdescs
9967 to begin building circuits?" logic most recently in 0.2.4.10-alpha
9968 (see bug 5956), but we left the bootstrap status event logic at
9969 "how far through getting 1/4 of them are we?" Fixes bug 9958;
9970 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
9972 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
9973 - Avoid a crash bug when starting with a corrupted microdescriptor
9974 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
9975 - If we fail to dump a previously cached microdescriptor to disk, avoid
9976 freeing duplicate data later on. Fixes bug 10423; bugfix on
9977 0.2.4.13-alpha. Spotted by "bobnomnom".
9979 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
9980 - Correctly log long IPv6 exit policies, instead of truncating them
9981 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
9982 - Our default TLS ecdhe groups were backwards: we meant to be using
9983 P224 for relays (for performance win) and P256 for bridges (since
9984 it is more common in the wild). Instead we had it backwards. After
9985 reconsideration, we decided that the default should be P256 on all
9986 hosts, since its security is probably better, and since P224 is
9987 reportedly used quite little in the wild. Found by "skruffy" on
9988 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
9989 - Free directory authority certificate download statuses on exit
9990 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
9992 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
9993 - If the guard we choose first doesn't answer, we would try the
9994 second guard, but once we connected to the second guard we would
9995 abandon it and retry the first one, slowing down bootstrapping.
9996 The fix is to treat all our initially chosen guards as acceptable
9997 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
9998 - Fix an assertion failure that would occur when disabling the
9999 ORPort setting on a running Tor process while accounting was
10000 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10001 - When examining the list of network interfaces to find our address,
10002 do not consider non-running or disabled network interfaces. Fixes
10003 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10004 - Avoid an off-by-one error when checking buffer boundaries when
10005 formatting the exit status of a pluggable transport helper.
10006 This is probably not an exploitable bug, but better safe than
10007 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10010 o Removed code and features:
10011 - Clients now reject any directory authority certificates lacking
10012 a dir-key-crosscert element. These have been included since
10013 0.2.1.9-alpha, so there's no real reason for them to be optional
10014 any longer. Completes proposal 157. Resolves ticket 10162.
10015 - Remove all code that existed to support the v2 directory system,
10016 since there are no longer any v2 directory authorities. Resolves
10018 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
10019 options, which were used for designating authorities as "Hidden
10020 service authorities". There has been no use of hidden service
10021 authorities since 0.2.2.1-alpha, when we stopped uploading or
10022 downloading v0 hidden service descriptors. Fixes bug 10881; also
10023 part of a fix for bug 10841.
10025 o Code simplification and refactoring:
10026 - Remove some old fallback code designed to keep Tor clients working
10027 in a network with only two working relays. Elsewhere in the code we
10028 have long since stopped supporting such networks, so there wasn't
10029 much point in keeping it around. Addresses ticket 9926.
10030 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
10031 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
10032 - Remove data structures which were introduced to implement the
10033 CellStatistics option: they are now redundant with the addition
10034 of a timestamp to the regular packed_cell_t data structure, which
10035 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
10038 o Documentation (man page) fixes:
10039 - Update manpage to describe some of the files you can expect to
10040 find in Tor's DataDirectory. Addresses ticket 9839.
10041 - Document that all but one DirPort entry must have the NoAdvertise
10042 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
10044 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
10045 - Clarify the usage and risks of setting the ContactInfo torrc line
10046 for your relay or bridge. Resolves ticket 9854.
10047 - Add anchors to the manpage so we can link to the html version of
10048 the documentation for specific options. Resolves ticket 9866.
10049 - Replace remaining references to DirServer in man page and
10050 log entries. Resolves ticket 10124.
10053 - Make the "tor-gencert" tool used by directory authority operators
10054 create 2048-bit signing keys by default (rather than 1024-bit, since
10055 1024-bit is uncomfortably small these days). Addresses ticket 10324.
10058 Changes in version 0.2.4.20 - 2013-12-22
10059 Tor 0.2.4.20 fixes potentially poor random number generation for users
10060 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
10061 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
10062 and 4) have no state file in their DataDirectory (as would happen on
10063 first start). Users who generated relay or hidden service identity
10064 keys in such a situation should discard them and generate new ones.
10066 This release also fixes a logic error that caused Tor clients to build
10067 many more preemptive circuits than they actually need.
10070 - Do not allow OpenSSL engines to replace the PRNG, even when
10071 HardwareAccel is set. The only default builtin PRNG engine uses
10072 the Intel RDRAND instruction to replace the entire PRNG, and
10073 ignores all attempts to seed it with more entropy. That's
10074 cryptographically stupid: the right response to a new alleged
10075 entropy source is never to discard all previously used entropy
10076 sources. Fixes bug 10402; works around behavior introduced in
10077 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
10079 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
10080 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
10081 - Avoid launching spurious extra circuits when a stream is pending.
10082 This fixes a bug where any circuit that _wasn't_ unusable for new
10083 streams would be treated as if it were, causing extra circuits to
10084 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
10087 - Avoid a crash bug when starting with a corrupted microdescriptor
10088 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
10089 - If we fail to dump a previously cached microdescriptor to disk, avoid
10090 freeing duplicate data later on. Fixes bug 10423; bugfix on
10091 0.2.4.13-alpha. Spotted by "bobnomnom".
10094 Changes in version 0.2.4.19 - 2013-12-11
10095 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
10096 (1986-2013). Aaron worked on diverse projects including helping to guide
10097 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
10098 transparency to the U.S government's PACER documents, and contributing
10099 design and development for Tor and Tor2Web. Aaron was one of the latest
10100 martyrs in our collective fight for civil liberties and human rights,
10101 and his death is all the more painful because he was one of us.
10103 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
10104 a new circuit handshake and link encryption that use ECC to provide
10105 better security and efficiency; makes relays better manage circuit
10106 creation requests; uses "directory guards" to reduce client enumeration
10107 risks; makes bridges collect and report statistics about the pluggable
10108 transports they support; cleans up and improves our geoip database;
10109 gets much closer to IPv6 support for clients, bridges, and relays; makes
10110 directory authorities use measured bandwidths rather than advertised
10111 ones when computing flags and thresholds; disables client-side DNS
10112 caching to reduce tracking risks; and fixes a big bug in bridge
10113 reachability testing. This release introduces two new design
10114 abstractions in the code: a new "channel" abstraction between circuits
10115 and or_connections to allow for implementing alternate relay-to-relay
10116 transports, and a new "circuitmux" abstraction storing the queue of
10117 circuits for a channel. The release also includes many stability,
10118 security, and privacy fixes.
10121 Changes in version 0.2.4.18-rc - 2013-11-16
10122 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
10123 series. It takes a variety of fixes from the 0.2.5.x branch to improve
10124 stability, performance, and better handling of edge cases.
10127 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
10128 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
10129 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
10130 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
10131 them to solve bug 6033.)
10134 - No longer stop reading or writing on cpuworker connections when
10135 our rate limiting buckets go empty. Now we should handle circuit
10136 handshake requests more promptly. Resolves bug 9731.
10137 - If we are unable to save a microdescriptor to the journal, do not
10138 drop it from memory and then reattempt downloading it. Fixes bug
10139 9645; bugfix on 0.2.2.6-alpha.
10140 - Stop trying to bootstrap all our directory information from
10141 only our first guard. Discovered while fixing bug 9946; bugfix
10143 - The new channel code sometimes lost track of in-progress circuits,
10144 causing long-running clients to stop building new circuits. The
10145 fix is to always call circuit_n_chan_done(chan, 0) from
10146 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
10148 o Minor bugfixes (on 0.2.4.x):
10149 - Correctly log long IPv6 exit policies, instead of truncating them
10150 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
10151 - Our default TLS ecdhe groups were backwards: we meant to be using
10152 P224 for relays (for performance win) and P256 for bridges (since
10153 it is more common in the wild). Instead we had it backwards. After
10154 reconsideration, we decided that the default should be P256 on all
10155 hosts, since its security is probably better, and since P224 is
10156 reportedly used quite little in the wild. Found by "skruffy" on
10157 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
10158 - Free directory authority certificate download statuses on exit
10159 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
10161 o Minor bugfixes (on 0.2.3.x and earlier):
10162 - If the guard we choose first doesn't answer, we would try the
10163 second guard, but once we connected to the second guard we would
10164 abandon it and retry the first one, slowing down bootstrapping.
10165 The fix is to treat all our initially chosen guards as acceptable
10166 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
10167 - Fix an assertion failure that would occur when disabling the
10168 ORPort setting on a running Tor process while accounting was
10169 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10170 - When examining the list of network interfaces to find our address,
10171 do not consider non-running or disabled network interfaces. Fixes
10172 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10173 - Avoid an off-by-one error when checking buffer boundaries when
10174 formatting the exit status of a pluggable transport helper.
10175 This is probably not an exploitable bug, but better safe than
10176 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10179 o Minor features (protecting client timestamps):
10180 - Clients no longer send timestamps in their NETINFO cells. These were
10181 not used for anything, and they provided one small way for clients
10182 to be distinguished from each other as they moved from network to
10183 network or behind NAT. Implements part of proposal 222.
10184 - Clients now round timestamps in INTRODUCE cells down to the nearest
10185 10 minutes. If a new Support022HiddenServices option is set to 0, or
10186 if it's set to "auto" and the feature is disabled in the consensus,
10187 the timestamp is sent as 0 instead. Implements part of proposal 222.
10188 - Stop sending timestamps in AUTHENTICATE cells. This is not such
10189 a big deal from a security point of view, but it achieves no actual
10190 good purpose, and isn't needed. Implements part of proposal 222.
10191 - Reduce down accuracy of timestamps in hidden service descriptors.
10192 Implements part of proposal 222.
10194 o Minor features (other):
10195 - Improve the circuit queue out-of-memory handler. Previously, when
10196 we ran low on memory, we'd close whichever circuits had the most
10197 queued cells. Now, we close those that have the *oldest* queued
10198 cells, on the theory that those are most responsible for us
10199 running low on memory. Based on analysis from a forthcoming paper
10200 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
10201 - Generate bootstrapping status update events correctly when fetching
10202 microdescriptors. Fixes bug 9927.
10203 - Update to the October 2 2013 Maxmind GeoLite Country database.
10205 o Documentation fixes:
10206 - Clarify the usage and risks of setting the ContactInfo torrc line
10207 for your relay or bridge. Resolves ticket 9854.
10208 - Add anchors to the manpage so we can link to the html version of
10209 the documentation for specific options. Resolves ticket 9866.
10210 - Replace remaining references to DirServer in man page and
10211 log entries. Resolves ticket 10124.
10214 Changes in version 0.2.5.1-alpha - 2013-10-02
10215 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
10216 on Linux, allows bridges that offer pluggable transports to report usage
10217 statistics, fixes many issues to make testing easier, and provides
10218 a pile of minor features and bugfixes that have been waiting for a
10219 release of the new branch.
10221 This is the first alpha release in a new series, so expect there to
10222 be bugs. Users who would rather test out a more stable branch should
10223 stay with 0.2.4.x for now.
10225 o Major features (security):
10226 - Use the seccomp2 syscall filtering facility on Linux to limit
10227 which system calls Tor can invoke. This is an experimental,
10228 Linux-only feature to provide defense-in-depth against unknown
10229 attacks. To try turning it on, set "Sandbox 1" in your torrc
10230 file. Please be ready to report bugs. We hope to add support
10231 for better sandboxing in the future, including more fine-grained
10232 filters, better division of responsibility, and support for more
10233 platforms. This work has been done by Cristian-Matei Toader for
10234 Google Summer of Code.
10235 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
10236 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
10237 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
10238 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
10239 them to solve bug 6033.)
10241 o Major features (other):
10242 - Add support for passing arguments to managed pluggable transport
10243 proxies. Implements ticket 3594.
10244 - Bridges now track GeoIP information and the number of their users
10245 even when pluggable transports are in use, and report usage
10246 statistics in their extra-info descriptors. Resolves tickets 4773
10248 - Make testing Tor networks bootstrap better: lower directory fetch
10249 retry schedules and maximum interval without directory requests,
10250 and raise maximum download tries. Implements ticket 6752.
10251 - Add make target 'test-network' to run tests on a Chutney network.
10252 Implements ticket 8530.
10253 - The ntor handshake is now on-by-default, no matter what the
10254 directory authorities recommend. Implements ticket 8561.
10257 - Instead of writing destroy cells directly to outgoing connection
10258 buffers, queue them and intersperse them with other outgoing cells.
10259 This can prevent a set of resource starvation conditions where too
10260 many pending destroy cells prevent data cells from actually getting
10261 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
10262 bugfix on 0.2.0.1-alpha.
10263 - If we are unable to save a microdescriptor to the journal, do not
10264 drop it from memory and then reattempt downloading it. Fixes bug
10265 9645; bugfix on 0.2.2.6-alpha.
10266 - The new channel code sometimes lost track of in-progress circuits,
10267 causing long-running clients to stop building new circuits. The
10268 fix is to always call circuit_n_chan_done(chan, 0) from
10269 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
10272 - Tor now builds each source file in two modes: a mode that avoids
10273 exposing identifiers needlessly, and another mode that exposes
10274 more identifiers for testing. This lets the compiler do better at
10275 optimizing the production code, while enabling us to take more
10276 radical measures to let the unit tests test things.
10277 - The production builds no longer include functions used only in
10278 the unit tests; all functions exposed from a module only for
10279 unit-testing are now static in production builds.
10280 - Add an --enable-coverage configuration option to make the unit
10281 tests (and a new src/or/tor-cov target) to build with gcov test
10285 - We now have rudimentary function mocking support that our unit
10286 tests can use to test functions in isolation. Function mocking
10287 lets the tests temporarily replace a function's dependencies with
10288 stub functions, so that the tests can check the function without
10289 invoking the other functions it calls.
10290 - Add more unit tests for the <circid,channel>->circuit map, and
10291 the destroy-cell-tracking code to fix bug 7912.
10292 - Unit tests for failing cases of the TAP onion handshake.
10293 - More unit tests for address-manipulation functions.
10295 o Minor features (protecting client timestamps):
10296 - Clients no longer send timestamps in their NETINFO cells. These were
10297 not used for anything, and they provided one small way for clients
10298 to be distinguished from each other as they moved from network to
10299 network or behind NAT. Implements part of proposal 222.
10300 - Clients now round timestamps in INTRODUCE cells down to the nearest
10301 10 minutes. If a new Support022HiddenServices option is set to 0, or
10302 if it's set to "auto" and the feature is disabled in the consensus,
10303 the timestamp is sent as 0 instead. Implements part of proposal 222.
10304 - Stop sending timestamps in AUTHENTICATE cells. This is not such
10305 a big deal from a security point of view, but it achieves no actual
10306 good purpose, and isn't needed. Implements part of proposal 222.
10307 - Reduce down accuracy of timestamps in hidden service descriptors.
10308 Implements part of proposal 222.
10310 o Minor features (config options):
10311 - Config (torrc) lines now handle fingerprints which are missing
10312 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
10313 - Support a --dump-config option to print some or all of the
10314 configured options. Mainly useful for debugging the command-line
10315 option parsing code. Helps resolve ticket 4647.
10316 - Raise awareness of safer logging: notify user of potentially
10317 unsafe config options, like logging more verbosely than severity
10318 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
10319 - Add a new configuration option TestingV3AuthVotingStartOffset
10320 that bootstraps a network faster by changing the timing for
10321 consensus votes. Addresses ticket 8532.
10322 - Add a new torrc option "ServerTransportOptions" that allows
10323 bridge operators to pass configuration parameters to their
10324 pluggable transports. Resolves ticket 8929.
10325 - The config (torrc) file now accepts bandwidth and space limits in
10326 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
10327 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
10330 o Minor features (build):
10331 - Add support for `--library-versions` flag. Implements ticket 6384.
10332 - Return the "unexpected sendme" warnings to a warn severity, but make
10333 them rate limited, to help diagnose ticket 8093.
10334 - Detect a missing asciidoc, and warn the user about it, during
10335 configure rather than at build time. Fixes issue 6506. Patch from
10338 o Minor features (other):
10339 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
10340 sockets in a single system call. Implements ticket 5129.
10341 - Log current accounting state (bytes sent and received + remaining
10342 time for the current accounting period) in the relay's heartbeat
10343 message. Implements ticket 5526; patch from Peter Retzlaff.
10344 - Implement the TRANSPORT_LAUNCHED control port event that
10345 notifies controllers about new launched pluggable
10346 transports. Resolves ticket 5609.
10347 - If we're using the pure-C 32-bit curve25519_donna implementation
10348 of curve25519, build it with the -fomit-frame-pointer option to
10349 make it go faster on register-starved hosts. This improves our
10350 handshake performance by about 6% on i386 hosts without nacl.
10351 Closes ticket 8109.
10352 - Update to the September 4 2013 Maxmind GeoLite Country database.
10355 - Set the listen() backlog limit to the largest actually supported
10356 on the system, not to the value in a header file. Fixes bug 9716;
10357 bugfix on every released Tor.
10358 - No longer accept malformed http headers when parsing urls from
10359 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
10360 bugfix on 0.0.6pre1.
10361 - In munge_extrainfo_into_routerinfo(), check the return value of
10362 memchr(). This would have been a serious issue if we ever passed
10363 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
10365 - On the chance that somebody manages to build Tor on a
10366 platform where time_t is unsigned, correct the way that
10367 microdesc_add_to_cache() handles negative time arguments.
10368 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
10369 - Reject relative control socket paths and emit a warning. Previously,
10370 single-component control socket paths would be rejected, but Tor
10371 would not log why it could not validate the config. Fixes bug 9258;
10372 bugfix on 0.2.3.16-alpha.
10374 o Minor bugfixes (command line):
10375 - Use a single command-line parser for parsing torrc options on the
10376 command line and for finding special command-line options to avoid
10377 inconsistent behavior for torrc option arguments that have the same
10378 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
10380 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
10381 9573; bugfix on 0.0.9pre5.
10383 o Minor fixes (build, auxiliary programs):
10384 - Stop preprocessing the "torify" script with autoconf, since
10385 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
10387 - The tor-fw-helper program now follows the standard convention and
10388 exits with status code "0" on success. Fixes bug 9030; bugfix on
10389 0.2.3.1-alpha. Patch by Arlo Breault.
10390 - Corrected ./configure advice for what openssl dev package you should
10391 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
10393 o Minor code improvements:
10394 - Remove constants and tests for PKCS1 padding; it's insecure and
10395 shouldn't be used for anything new. Fixes bug 8792; patch
10397 - Remove instances of strcpy() from the unit tests. They weren't
10398 hurting anything, since they were only in the unit tests, but it's
10399 embarassing to have strcpy() in the code at all, and some analysis
10400 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
10401 0.2.3.8-alpha. Patch from Arlo Breault.
10403 o Removed features:
10404 - Remove migration code from when we renamed the "cached-routers"
10405 file to "cached-descriptors" back in 0.2.0.8-alpha. This
10406 incidentally resolves ticket 6502 by cleaning up the related code
10407 a bit. Patch from Akshay Hebbar.
10409 o Code simplification and refactoring:
10410 - Extract the common duplicated code for creating a subdirectory
10411 of the data directory and writing to a file in it. Fixes ticket
10412 4282; patch from Peter Retzlaff.
10413 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
10414 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
10415 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
10416 - Add a set of accessor functions for the circuit timeout data
10417 structure. Fixes ticket 6153; patch from "piet".
10418 - Clean up exit paths from connection_listener_new(). Closes ticket
10419 8789. Patch from Arlo Breault.
10420 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
10421 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
10422 - Use a doubly-linked list to implement the global circuit list.
10423 Resolves ticket 9108. Patch from Marek Majkowski.
10424 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
10427 Changes in version 0.2.4.17-rc - 2013-09-05
10428 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
10429 series. It adds an emergency step to help us tolerate the massive
10430 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
10431 circuit-level handshakes now effectively jump the queue compared to
10432 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
10433 big bug hindering bridge reachability tests.
10436 - Relays now process the new "NTor" circuit-level handshake requests
10437 with higher priority than the old "TAP" circuit-level handshake
10438 requests. We still process some TAP requests to not totally starve
10439 0.2.3 clients when NTor becomes popular. A new consensus parameter
10440 "NumNTorsPerTAP" lets us tune the balance later if we need to.
10441 Implements ticket 9574.
10444 - If the circuit build timeout logic is disabled (via the consensus,
10445 or because we are an authority), then don't build testing circuits.
10446 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
10447 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
10448 previously they did not, which prevented them from receiving
10449 successful connections from relays for self-test or bandwidth
10450 testing. Also, when a relay is extending a circuit to a bridge,
10451 it needs to send a NETINFO cell, even when the bridge hasn't sent
10452 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
10453 - If the time to download the next old-style networkstatus is in
10454 the future, do not decline to consider whether to download the
10455 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
10459 - Avoid double-closing the listener socket in our socketpair()
10460 replacement (used on Windows) in the case where the addresses on
10461 our opened sockets don't match what we expected. Fixes bug 9400;
10462 bugfix on 0.0.2pre7. Found by Coverity.
10464 o Minor fixes (config options):
10465 - Avoid overflows when the user sets MaxCircuitDirtiness to a
10466 ridiculously high value, by imposing a (ridiculously high) 30-day
10467 maximum on MaxCircuitDirtiness.
10468 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
10469 message is logged at notice, not at info.
10470 - Warn and fail if a server is configured not to advertise any
10471 ORPorts at all. (We need *something* to put in our descriptor,
10472 or we just won't work.)
10475 - Track how many "TAP" and "NTor" circuit handshake requests we get,
10476 and how many we complete, and log it every hour to help relay
10477 operators follow trends in network load. Addresses ticket 9658.
10478 - Update to the August 7 2013 Maxmind GeoLite Country database.
10481 Changes in version 0.2.4.16-rc - 2013-08-10
10482 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
10483 series. It fixes several crash bugs in the 0.2.4 branch.
10486 - Fix a bug in the voting algorithm that could yield incorrect results
10487 when a non-naming authority declared too many flags. Fixes bug 9200;
10488 bugfix on 0.2.0.3-alpha.
10489 - Fix an uninitialized read that could in some cases lead to a remote
10490 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
10491 Anybody running a hidden service on the experimental 0.2.4.x
10492 branch should upgrade. (This is, so far as we know, unrelated to
10494 - Avoid an assertion failure when processing DNS replies without the
10495 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
10496 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
10497 0.2.4.15-rc. Found by stem integration tests.
10500 - Fix an invalid memory read that occured when a pluggable
10501 transport proxy failed its configuration protocol.
10502 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
10503 - When evaluating whether to use a connection that we haven't
10504 decided is canonical using a recent link protocol version,
10505 decide that it's canonical only if it used address _does_
10506 match the desired address. Fixes bug 9309; bugfix on
10507 0.2.4.4-alpha. Reported by skruffy.
10508 - Make the default behavior of NumDirectoryGuards be to track
10509 NumEntryGuards. Now a user who changes only NumEntryGuards will get
10510 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
10511 - Fix a spurious compilation warning with some older versions of
10512 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
10515 - Update to the July 3 2013 Maxmind GeoLite Country database.
10518 Changes in version 0.2.4.15-rc - 2013-07-01
10519 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
10520 series. It fixes a few smaller bugs, but generally appears stable.
10521 Please test it and let us know whether it is!
10524 - When receiving a new configuration file via the control port's
10525 LOADCONF command, do not treat the defaults file as absent.
10526 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
10529 - Issue a warning when running with the bufferevents backend enabled.
10530 It's still not stable, and people should know that they're likely
10531 to hit unexpected problems. Closes ticket 9147.
10534 Changes in version 0.2.4.14-alpha - 2013-06-18
10535 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
10536 present in 0.2.4.13-alpha.
10539 - When we have too much memory queued in circuits (according to a new
10540 MaxMemInCellQueues option), close the circuits consuming the most
10541 memory. This prevents us from running out of memory as a relay if
10542 circuits fill up faster than they can be drained. Fixes bug 9063;
10543 bugfix on the 54th commit of Tor. This bug is a further fix beyond
10544 bug 6252, whose fix was merged into 0.2.3.21-rc.
10546 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
10547 where we tried to solve this issue simply by imposing an upper limit
10548 on the number of queued cells for a single circuit. That approach
10549 proved to be problematic, since there are ways to provoke clients to
10550 send a number of cells in excess of any such reasonable limit. Fixes
10551 bug 9072; bugfix on 0.2.4.13-alpha.
10553 - Limit hidden service descriptors to at most ten introduction
10554 points, to slow one kind of guard enumeration. Fixes bug 9002;
10555 bugfix on 0.1.1.11-alpha.
10558 Changes in version 0.2.4.13-alpha - 2013-06-14
10559 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
10560 vulnerabilities, makes socks5 username/password circuit isolation
10561 actually actually work (this time for sure!), and cleans up a bunch
10562 of other issues in preparation for a release candidate.
10564 o Major bugfixes (robustness):
10565 - Close any circuit that has too many cells queued on it. Fixes
10566 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
10567 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
10568 - Prevent the get_freelists() function from running off the end of
10569 the list of freelists if it somehow gets an unrecognized
10570 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
10572 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
10573 when an exit connection with optimistic data succeeds immediately
10574 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
10576 - Fix a directory authority crash bug when building a consensus
10577 using an older consensus as its basis. Fixes bug 8833. Bugfix
10581 - Avoid a memory leak where we would leak a consensus body when we
10582 find that a consensus which we couldn't previously verify due to
10583 missing certificates is now verifiable. Fixes bug 8719; bugfix
10585 - We used to always request authority certificates by identity digest,
10586 meaning we'd get the newest one even when we wanted one with a
10587 different signing key. Then we would complain about being given
10588 a certificate we already had, and never get the one we really
10589 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
10590 resource to request the one we want. Fixes bug 5595; bugfix on
10592 - Follow the socks5 protocol when offering username/password
10593 authentication. The fix for bug 8117 exposed this bug, and it
10594 turns out real-world applications like Pidgin do care. Bugfix on
10595 0.2.3.2-alpha; fixes bug 8879.
10596 - Prevent failures on Windows Vista and later when rebuilding the
10597 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
10598 bugfix on 0.2.4.12-alpha.
10601 - Fix an impossible buffer overrun in the AES unit tests. Fixes
10602 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
10603 - If for some reason we fail to write a microdescriptor while
10604 rebuilding the cache, do not let the annotations from that
10605 microdescriptor linger in the cache file, and do not let the
10606 microdescriptor stay recorded as present in its old location.
10607 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
10608 - Fix a memory leak that would occur whenever a configuration
10609 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
10610 - Paste the description for PathBias parameters from the man
10611 page into or.h, so the code documents them too. Fixes bug 7982;
10612 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
10613 - Relays now treat a changed IPv6 ORPort as sufficient reason to
10614 publish an updated descriptor. Fixes bug 6026; bugfix on
10616 - When launching a resolve request on behalf of an AF_UNIX control
10617 socket, omit the address field of the new entry connection, used in
10618 subsequent controller events, rather than letting tor_dup_addr()
10619 set it to "<unknown address type>". Fixes bug 8639; bugfix on
10622 o Minor bugfixes (log messages):
10623 - Fix a scaling issue in the path bias accounting code that
10624 resulted in "Bug:" log messages from either
10625 pathbias_scale_close_rates() or pathbias_count_build_success().
10626 This represents a bugfix on a previous bugfix: the original fix
10627 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
10629 - Give a less useless error message when the user asks for an IPv4
10630 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
10634 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
10635 to tolerate bug 8093 for now.
10636 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
10637 in directory authority votes to describe whether they have enough
10638 measured bandwidths to ignore advertised (relay descriptor)
10639 bandwidth claims. Resolves ticket 8711.
10640 - Update to the June 5 2013 Maxmind GeoLite Country database.
10642 o Removed documentation:
10643 - Remove some of the older contents of doc/ as obsolete; move others
10644 to torspec.git. Fixes bug 8965.
10646 o Code simplification and refactoring:
10647 - Avoid using character buffers when constructing most directory
10648 objects: this approach was unwieldy and error-prone. Instead,
10649 build smartlists of strings, and concatenate them when done.
10652 Changes in version 0.2.4.12-alpha - 2013-04-18
10653 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
10654 process for lengthening the guard rotation period, makes directory
10655 authority opinions in the consensus a bit less gameable, makes socks5
10656 username/password circuit isolation actually work, and fixes a wide
10657 variety of other issues.
10660 - Raise the default time that a client keeps an entry guard from
10661 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
10662 2012 paper. (We would make it even longer, but we need better client
10663 load balancing first.) Also, make the guard lifetime controllable
10664 via a new GuardLifetime torrc option and a GuardLifetime consensus
10665 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
10666 - Directory authorities now prefer using measured bandwidths to
10667 advertised ones when computing flags and thresholds. Resolves
10669 - Directory authorities that have more than a threshold number
10670 of relays with measured bandwidths now treat relays with unmeasured
10671 bandwidths as having bandwidth 0. Resolves ticket 8435.
10673 o Major bugfixes (assert / resource use):
10674 - Avoid a bug where our response to TLS renegotiation under certain
10675 network conditions could lead to a busy-loop, with 100% CPU
10676 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
10677 - Avoid an assertion when we discover that we'd like to write a cell
10678 onto a closing connection: just discard the cell. Fixes another
10679 case of bug 7350; bugfix on 0.2.4.4-alpha.
10681 o Major bugfixes (client-side privacy):
10682 - When we mark a circuit as unusable for new circuits, have it
10683 continue to be unusable for new circuits even if MaxCircuitDirtiness
10684 is increased too much at the wrong time, or the system clock jumps
10685 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
10686 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
10687 which have resolved to internal addresses") is set, apply that
10688 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
10689 - When an exit relay rejects a stream with reason "exit policy", but
10690 we only know an exit policy summary (e.g. from the microdesc
10691 consensus) for it, do not mark the relay as useless for all exiting.
10692 Instead, mark just the circuit as unsuitable for that particular
10693 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
10694 - Allow applications to get proper stream isolation with
10695 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
10696 username/password authentication also offer "no authentication". Tor
10697 had previously preferred "no authentication", so the applications
10698 never actually sent Tor their auth details. Now Tor selects
10699 username/password authentication if it's offered. You can disable
10700 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
10701 bug 8117; bugfix on 0.2.3.3-alpha.
10703 o Major bugfixes (other):
10704 - When unable to find any working directory nodes to use as a
10705 directory guard, give up rather than adding the same non-working
10706 nodes to the directory guard list over and over. Fixes bug 8231;
10707 bugfix on 0.2.4.8-alpha.
10710 - Reject as invalid most directory objects containing a NUL.
10711 Belt-and-suspender fix for bug 8037.
10712 - In our testsuite, create temporary directories with a bit more
10713 entropy in their name to make name collisions less likely. Fixes
10715 - Add CACHED keyword to ADDRMAP events in the control protocol
10716 to indicate whether a DNS result will be cached or not. Resolves
10718 - Update to the April 3 2013 Maxmind GeoLite Country database.
10720 o Minor features (build):
10721 - Detect and reject attempts to build Tor with threading support
10722 when OpenSSL has been compiled without threading support.
10724 - Clarify that when autoconf is checking for nacl, it is checking
10725 specifically for nacl with a fast curve25519 implementation.
10727 - Warn if building on a platform with an unsigned time_t: there
10728 are too many places where Tor currently assumes that time_t can
10729 hold negative values. We'd like to fix them all, but probably
10732 o Minor bugfixes (build):
10733 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
10734 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
10735 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
10736 - Add the old src/or/micro-revision.i filename to CLEANFILES.
10737 On the off chance that somebody has one, it will go away as soon
10738 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
10739 - Build Tor correctly on 32-bit platforms where the compiler can build
10740 but not run code using the "uint128_t" construction. Fixes bug 8587;
10741 bugfix on 0.2.4.8-alpha.
10742 - Fix compilation warning with some versions of clang that would
10743 prefer the -Wswitch-enum compiler flag to warn about switch
10744 statements with missing enum values, even if those switch
10745 statements have a "default:" statement. Fixes bug 8598; bugfix
10748 o Minor bugfixes (protocol):
10749 - Fix the handling of a TRUNCATE cell when it arrives while the
10750 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
10751 - Fix a misframing issue when reading the version numbers in a
10752 VERSIONS cell. Previously we would recognize [00 01 00 02] as
10753 'version 1, version 2, and version 0x100', when it should have
10754 only included versions 1 and 2. Fixes bug 8059; bugfix on
10755 0.2.0.10-alpha. Reported pseudonymously.
10756 - Make the format and order of STREAM events for DNS lookups
10757 consistent among the various ways to launch DNS lookups. Fixes
10758 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
10759 - Correct our check for which versions of Tor support the EXTEND2
10760 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
10761 later, when support was really added in version 0.2.4.8-alpha.
10762 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
10764 o Minor bugfixes (other):
10765 - Correctly store microdescriptors and extrainfo descriptors with
10766 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
10767 Bug reported by "cypherpunks".
10768 - Increase the width of the field used to remember a connection's
10769 link protocol version to two bytes. Harmless for now, since the
10770 only currently recognized versions are one byte long. Reported
10771 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
10772 - If the state file's path bias counts are invalid (presumably from a
10773 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
10774 additional checks and log messages to the scaling of Path Bias
10775 counts, in case there still are remaining issues with scaling.
10776 Should help resolve bug 8235.
10777 - Eliminate several instances where we use "Nickname=ID" to refer to
10778 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
10779 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
10780 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
10782 o Minor bugfixes (syscalls):
10783 - Always check the return values of functions fcntl() and
10784 setsockopt(). We don't believe these are ever actually failing in
10785 practice, but better safe than sorry. Also, checking these return
10786 values should please analysis tools like Coverity. Patch from
10787 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
10788 - Use direct writes rather than stdio when building microdescriptor
10789 caches, in an attempt to mitigate bug 8031, or at least make it
10792 o Minor bugfixes (config):
10793 - When rejecting a configuration because we were unable to parse a
10794 quoted string, log an actual error message. Fixes bug 7950; bugfix
10796 - Behave correctly when the user disables LearnCircuitBuildTimeout
10797 but doesn't tell us what they would like the timeout to be. Fixes
10798 bug 6304; bugfix on 0.2.2.14-alpha.
10799 - When autodetecting the number of CPUs, use the number of available
10800 CPUs in preference to the number of configured CPUs. Inform the
10801 user if this reduces the number of available CPUs. Fixes bug 8002;
10802 bugfix on 0.2.3.1-alpha.
10803 - Make it an error when you set EntryNodes but disable UseGuardNodes,
10804 since it will (surprisingly to some users) ignore EntryNodes. Fixes
10805 bug 8180; bugfix on 0.2.3.11-alpha.
10806 - Allow TestingTorNetworks to override the 4096-byte minimum for
10807 the Fast threshold. Otherwise they can't bootstrap until they've
10808 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
10809 - Fix some logic errors when the user manually overrides the
10810 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
10813 o Minor bugfixes (log messages to help diagnose bugs):
10814 - If we fail to free a microdescriptor because of bug 7164, log
10815 the filename and line number from which we tried to free it.
10816 - Add another diagnostic to the heartbeat message: track and log
10817 overhead that TLS is adding to the data we write. If this is
10818 high, we are sending too little data to SSL_write at a time.
10819 Diagnostic for bug 7707.
10820 - Add more detail to a log message about relaxed timeouts, to help
10822 - Warn more aggressively when flushing microdescriptors to a
10823 microdescriptor cache fails, in an attempt to mitigate bug 8031,
10824 or at least make it more diagnosable.
10825 - Improve debugging output to help track down bug 8185 ("Bug:
10826 outgoing relay cell has n_chan==NULL. Dropping.")
10827 - Log the purpose of a path-bias testing circuit correctly.
10828 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
10830 o Minor bugfixes (0.2.4.x log messages that were too noisy):
10831 - Don't attempt to relax the timeout of already opened 1-hop circuits.
10832 They might never timeout. This should eliminate some/all cases of
10833 the relaxed timeout log message.
10834 - Use circuit creation time for network liveness evaluation. This
10835 should eliminate warning log messages about liveness caused
10836 by changes in timeout evaluation. Fixes bug 6572; bugfix on
10838 - Reduce a path bias length check from notice to info. The message
10839 is triggered when creating controller circuits. Fixes bug 8196;
10840 bugfix on 0.2.4.8-alpha.
10841 - Fix a path state issue that triggered a notice during relay startup.
10842 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
10843 - Reduce occurrences of warns about circuit purpose in
10844 connection_ap_expire_building(). Fixes bug 8477; bugfix on
10847 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
10848 - If we encounter a write failure on a SOCKS connection before we
10849 finish our SOCKS handshake, don't warn that we closed the
10850 connection before we could send a SOCKS reply. Fixes bug 8427;
10851 bugfix on 0.1.0.1-rc.
10852 - Correctly recognize that [::1] is a loopback address. Fixes
10853 bug 8377; bugfix on 0.2.1.3-alpha.
10854 - Fix a directory authority warn caused when we have a large amount
10855 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
10856 - Don't log inappropriate heartbeat messages when hibernating: a
10857 hibernating node is _expected_ to drop out of the consensus,
10858 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
10859 bugfix on 0.2.3.1-alpha.
10860 - Don't complain about bootstrapping problems while hibernating.
10861 These complaints reflect a general code problem, but not one
10862 with any problematic effects (no connections are actually
10863 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
10865 o Documentation fixes:
10866 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
10867 names match. Fixes bug 7768.
10868 - Make the torify manpage no longer refer to tsocks; torify hasn't
10869 supported tsocks since 0.2.3.14-alpha.
10870 - Make the tor manpage no longer reference tsocks.
10871 - Fix the GeoIPExcludeUnknown documentation to refer to
10872 ExcludeExitNodes rather than the currently nonexistent
10873 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
10876 - The tor-tsocks.conf is no longer distributed or installed. We
10877 recommend that tsocks users use torsocks instead. Resolves
10881 Changes in version 0.2.4.11-alpha - 2013-03-11
10882 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
10883 more robust, makes hidden service authentication work again, and
10884 resolves a DPI fingerprint for Tor's SSL transport.
10886 o Major features (directory authorities):
10887 - Directory authorities now support a new consensus method (17)
10888 where they cap the published bandwidth of servers for which
10889 insufficient bandwidth measurements exist. Fixes part of bug 2286.
10890 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
10891 serve any v2 directory information. Now we can test disabling the
10892 old deprecated v2 directory format, and see whether doing so has
10893 any effect on network load. Begins to fix bug 6783.
10894 - Directory authorities now include inside each vote a statement of
10895 the performance thresholds they used when assigning flags.
10896 Implements ticket 8151.
10898 o Major bugfixes (directory authorities):
10899 - Stop marking every relay as having been down for one hour every
10900 time we restart a directory authority. These artificial downtimes
10901 were messing with our Stable and Guard flag calculations. Fixes
10902 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
10904 o Major bugfixes (hidden services):
10905 - Allow hidden service authentication to succeed again. When we
10906 refactored the hidden service introduction code back
10907 in 0.2.4.1-alpha, we didn't update the code that checks
10908 whether authentication information is present, causing all
10909 authentication checks to return "false". Fix for bug 8207; bugfix
10910 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
10912 o Minor features (relays, bridges):
10913 - Make bridge relays check once a minute for whether their IP
10914 address has changed, rather than only every 15 minutes. Resolves
10915 bugs 1913 and 1992.
10916 - Refactor resolve_my_address() so it returns the method by which we
10917 decided our public IP address (explicitly configured, resolved from
10918 explicit hostname, guessed from interfaces, learned by gethostname).
10919 Now we can provide more helpful log messages when a relay guesses
10920 its IP address incorrectly (e.g. due to unexpected lines in
10921 /etc/hosts). Resolves ticket 2267.
10922 - Teach bridge-using clients to avoid 0.2.2 bridges when making
10923 microdescriptor-related dir requests, and only fall back to normal
10924 descriptors if none of their bridges can handle microdescriptors
10925 (as opposed to the fix in ticket 4013, which caused them to fall
10926 back to normal descriptors if *any* of their bridges preferred
10927 them). Resolves ticket 4994.
10928 - Randomize the lifetime of our SSL link certificate, so censors can't
10929 use the static value for filtering Tor flows. Resolves ticket 8443;
10930 related to ticket 4014 which was included in 0.2.2.33.
10931 - Support a new version of the link protocol that allows 4-byte circuit
10932 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
10933 a possible resource exhaustion issue. Closes ticket 7351; implements
10936 o Minor features (portability):
10937 - Tweak the curve25519-donna*.c implementations to tolerate systems
10938 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
10939 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
10940 the signs of types during autoconf. This is better than our old
10941 approach, which didn't work when cross-compiling.
10942 - Detect the sign of enum values, rather than assuming that MSC is the
10943 only compiler where enum types are all signed. Fixes bug 7727;
10944 bugfix on 0.2.4.10-alpha.
10946 o Minor features (other):
10947 - Say "KBytes" rather than "KB" in the man page (for various values
10948 of K), to further reduce confusion about whether Tor counts in
10949 units of memory or fractions of units of memory. Resolves ticket 7054.
10950 - Clear the high bit on curve25519 public keys before passing them to
10951 our backend, in case we ever wind up using a backend that doesn't do
10952 so itself. If we used such a backend, and *didn't* clear the high bit,
10953 we could wind up in a situation where users with such backends would
10954 be distinguishable from users without. Fixes bug 8121; bugfix on
10956 - Update to the March 6 2013 Maxmind GeoLite Country database.
10958 o Minor bugfixes (clients):
10959 - When we receive a RELAY_END cell with the reason DONE, or with no
10960 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
10961 status as "connection refused". Previously we reported these cases
10962 as success but then immediately closed the connection. Fixes bug
10963 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
10964 - Downgrade an assertion in connection_ap_expire_beginning to an
10965 LD_BUG message. The fix for bug 8024 should prevent this message
10966 from displaying, but just in case, a warn that we can diagnose
10967 is better than more assert crashes. Fixes bug 8065; bugfix on
10969 - Lower path use bias thresholds to .80 for notice and .60 for warn.
10970 Also make the rate limiting flags for the path use bias log messages
10971 independent from the original path bias flags. Fixes bug 8161;
10972 bugfix on 0.2.4.10-alpha.
10974 o Minor bugfixes (relays):
10975 - Stop trying to resolve our hostname so often (e.g. every time we
10976 think about doing a directory fetch). Now we reuse the cached
10977 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
10978 and 2410 (bugfix on 0.1.2.2-alpha).
10979 - Stop sending a stray "(null)" in some cases for the server status
10980 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
10982 - When choosing which stream on a formerly stalled circuit to wake
10983 first, make better use of the platform's weak RNG. Previously,
10984 we had been using the % ("modulo") operator to try to generate a
10985 1/N chance of picking each stream, but this behaves badly with
10986 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
10988 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
10989 Irix's random() only return 15 bits; Solaris's random() returns more
10990 bits but its RAND_MAX says it only returns 15, and so on. Motivated
10991 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
10993 o Minor bugfixes (directory authorities):
10994 - Directory authorities now use less space when formatting identical
10995 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
10998 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
10999 - Avoid leaking memory if we fail to compute a consensus signature
11000 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
11001 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
11003 - Fix a memory leak during safe-cookie controller authentication.
11004 Bugfix on 0.2.3.13-alpha.
11005 - Avoid memory leak of IPv6 policy content if we fail to format it into
11006 a router descriptor. Bugfix on 0.2.4.7-alpha.
11008 o Minor bugfixes (other code correctness issues):
11009 - Avoid a crash if we fail to generate an extrainfo descriptor.
11010 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
11011 this is CID 718634.
11012 - When detecting the largest possible file descriptor (in order to
11013 close all file descriptors when launching a new program), actually
11014 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
11015 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
11017 - Fix a copy-and-paste error when adding a missing A1 to a routerset
11018 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
11019 Bugfix on 0.2.4.10-alpha.
11020 - Fix an impossible-to-trigger integer overflow when estimating how
11021 long our onionskin queue would take. (This overflow would require us
11022 to accept 4 million onionskins before processing 100 of them.) Fixes
11023 bug 8210; bugfix on 0.2.4.10-alpha.
11025 o Code simplification and refactoring:
11026 - Add a wrapper function for the common "log a message with a
11030 Changes in version 0.2.4.10-alpha - 2013-02-04
11031 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
11032 certain attacks that flood the network with relays; changes the queue
11033 for circuit create requests from a sized-based limit to a time-based
11034 limit; resumes building with MSVC on Windows; and fixes a wide variety
11037 o Major bugfixes (directory authority):
11038 - When computing directory thresholds, ignore any rejected-as-sybil
11039 nodes during the computation so that they can't influence Fast,
11040 Guard, etc. (We should have done this for proposal 109.) Fixes
11042 - When marking a node as a likely sybil, reset its uptime metrics
11043 to zero, so that it cannot time towards getting marked as Guard,
11044 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
11048 - When a TLS write is partially successful but incomplete, remember
11049 that the flushed part has been flushed, and notice that bytes were
11050 actually written. Reported and fixed pseudonymously. Fixes bug
11051 7708; bugfix on Tor 0.1.0.5-rc.
11052 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
11053 ID: these could be used to create unexpected streams and circuits
11054 which would count as "present" to some parts of Tor but "absent"
11055 to others, leading to zombie circuits and streams or to a bandwidth
11056 denial-of-service. Fixes bug 7889; bugfix on every released version
11057 of Tor. Reported by "oftc_must_be_destroyed".
11058 - Rename all macros in our local copy of queue.h to begin with "TOR_".
11059 This change seems the only good way to permanently prevent conflicts
11060 with queue.h on various operating systems. Fixes bug 8107; bugfix
11063 o Major features (relay):
11064 - Instead of limiting the number of queued onionskins (aka circuit
11065 create requests) to a fixed, hard-to-configure number, we limit
11066 the size of the queue based on how many we expect to be able to
11067 process in a given amount of time. We estimate the time it will
11068 take to process an onionskin based on average processing time
11069 of previous onionskins. Closes ticket 7291. You'll never have to
11070 configure MaxOnionsPending again.
11072 o Major features (portability):
11073 - Resume building correctly with MSVC and Makefile.nmake. This patch
11074 resolves numerous bugs and fixes reported by ultramage, including
11075 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
11076 - Make the ntor and curve25519 code build correctly with MSVC.
11077 Fix on 0.2.4.8-alpha.
11080 - When directory authorities are computing thresholds for flags,
11081 never let the threshold for the Fast flag fall below 4096
11082 bytes. Also, do not consider nodes with extremely low bandwidths
11083 when deciding thresholds for various directory flags. This change
11084 should raise our threshold for Fast relays, possibly in turn
11085 improving overall network performance; see ticket 1854. Resolves
11087 - The Tor client now ignores sub-domain components of a .onion
11088 address. This change makes HTTP "virtual" hosting
11089 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
11090 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
11091 hosted on the same hidden service. Implements proposal 204.
11092 - We compute the overhead from passing onionskins back and forth to
11093 cpuworkers, and report it when dumping statistics in response to
11094 SIGUSR1. Supports ticket 7291.
11096 o Minor features (path selection):
11097 - When deciding whether we have enough descriptors to build circuits,
11098 instead of looking at raw relay counts, look at which fraction
11099 of (bandwidth-weighted) paths we're able to build. This approach
11100 keeps clients from building circuits if their paths are likely to
11101 stand out statistically. The default fraction of paths needed is
11102 taken from the consensus directory; you can override it with the
11103 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
11104 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
11105 and we have GeoIP information, also exclude all nodes with unknown
11106 countries "??" and "A1". This behavior is controlled by the
11107 new GeoIPExcludeUnknown option: you can make such nodes always
11108 excluded with "GeoIPExcludeUnknown 1", and disable the feature
11109 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
11110 gets you the default behavior. Implements feature 7706.
11111 - Path Use Bias: Perform separate accounting for successful circuit
11112 use. Keep separate statistics on stream attempt rates versus stream
11113 success rates for each guard. Provide configurable thresholds to
11114 determine when to emit log messages or disable use of guards that
11115 fail too many stream attempts. Resolves ticket 7802.
11117 o Minor features (log messages):
11118 - When learning a fingerprint for a bridge, log its corresponding
11119 transport type. Implements ticket 7896.
11120 - Improve the log message when "Bug/attack: unexpected sendme cell
11121 from client" occurs, to help us track bug 8093.
11124 - Remove a couple of extraneous semicolons that were upsetting the
11125 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
11126 bugfix on 0.2.2.1-alpha.
11127 - Remove a source of rounding error during path bias count scaling;
11128 don't count cannibalized circuits as used for path bias until we
11129 actually try to use them; and fix a circuit_package_relay_cell()
11130 warning message about n_chan==NULL. Fixes bug 7802.
11131 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
11132 actually link against nacl when we're configured to use it. Fixes
11133 bug 7972; bugfix on 0.2.4.8-alpha.
11134 - Compile correctly with the --disable-curve25519 option. Fixes
11135 bug 8153; bugfix on 0.2.4.8-alpha.
11137 o Build improvements:
11138 - Do not report status verbosely from autogen.sh unless the -v flag
11139 is specified. Fixes issue 4664. Patch from Onizuka.
11140 - Replace all calls to snprintf() outside of src/ext with
11141 tor_snprintf(). Also remove the #define to replace snprintf with
11142 _snprintf on Windows; they have different semantics, and all of
11143 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
11144 - Try to detect if we are ever building on a platform where
11145 memset(...,0,...) does not set the value of a double to 0.0. Such
11146 platforms are permitted by the C standard, though in practice
11147 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
11148 currently support them, but it's better to detect them and fail
11149 than to perform erroneously.
11151 o Removed features:
11152 - Stop exporting estimates of v2 and v3 directory traffic shares
11153 in extrainfo documents. They were unneeded and sometimes inaccurate.
11154 Also stop exporting any v2 directory request statistics. Resolves
11156 - Drop support for detecting and warning about versions of Libevent
11157 before 1.3e. Nothing reasonable ships with them any longer;
11158 warning the user about them shouldn't be needed. Resolves ticket
11161 o Code simplifications and refactoring:
11162 - Rename "isin" functions to "contains", for grammar. Resolves
11164 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
11165 with the natural logarithm function from the system libm. Resolves
11169 Changes in version 0.2.4.9-alpha - 2013-01-15
11170 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
11171 work more robustly.
11174 - Fix backward compatibility logic when receiving an embedded ntor
11175 handshake tunneled in a CREATE cell. This clears up the "Bug:
11176 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
11180 Changes in version 0.2.4.8-alpha - 2013-01-14
11181 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
11182 risks, adds a new stronger and faster circuit handshake, and offers
11183 stronger and faster link encryption when both sides support it.
11186 - Preliminary support for directory guards (proposal 207): when
11187 possible, clients now use their entry guards for non-anonymous
11188 directory requests. This can help prevent client enumeration. Note
11189 that this behavior only works when we have a usable consensus
11190 directory, and when options about what to download are more or less
11191 standard. In the future we should re-bootstrap from our guards,
11192 rather than re-bootstrapping from the preconfigured list of
11193 directory sources that ships with Tor. Resolves ticket 6526.
11194 - Tor relays and clients now support a better CREATE/EXTEND cell
11195 format, allowing the sender to specify multiple address, identity,
11196 and handshake types. Implements Robert Ransom's proposal 200;
11197 closes ticket 7199.
11199 o Major features (new circuit handshake):
11200 - Tor now supports a new circuit extension handshake designed by Ian
11201 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
11202 circuit extension handshake, later called "TAP", was a bit slow
11203 (especially on the relay side), had a fragile security proof, and
11204 used weaker keys than we'd now prefer. The new circuit handshake
11205 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
11206 function, making it significantly more secure than the older
11207 handshake, and significantly faster. Tor can use one of two built-in
11208 pure-C curve25519-donna implementations by Adam Langley, or it
11209 can link against the "nacl" library for a tuned version if present.
11211 The built-in version is very fast for 64-bit systems when building
11212 with GCC. The built-in 32-bit version is still faster than the
11213 old TAP protocol, but using libnacl is better on most such hosts.
11215 Clients don't currently use this protocol by default, since
11216 comparatively few clients support it so far. To try it, set
11217 UseNTorHandshake to 1.
11219 Implements proposal 216; closes ticket 7202.
11221 o Major features (better link encryption):
11222 - Relays can now enable the ECDHE TLS ciphersuites when available
11223 and appropriate. These ciphersuites let us negotiate forward-secure
11224 TLS secret keys more safely and more efficiently than with our
11225 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
11226 public relays prefer the (faster) P224 group, and bridges prefer
11227 the (more common) P256 group; you can override this with the
11230 Enabling these ciphers was a little tricky, since for a long time,
11231 clients had been claiming to support them without actually doing
11232 so, in order to foil fingerprinting. But with the client-side
11233 implementation of proposal 198 in 0.2.3.17-beta, clients can now
11234 match the ciphers from recent Firefox versions *and* list the
11235 ciphers they actually mean, so relays can believe such clients
11236 when they advertise ECDHE support in their TLS ClientHello messages.
11238 This feature requires clients running 0.2.3.17-beta or later,
11239 and requires both sides to be running OpenSSL 1.0.0 or later
11240 with ECC support. OpenSSL 1.0.1, with the compile-time option
11241 "enable-ec_nistp_64_gcc_128", is highly recommended.
11243 Implements the relay side of proposal 198; closes ticket 7200.
11246 - Avoid crashing when, as a relay without IPv6-exit support, a
11247 client insists on getting an IPv6 address or nothing. Fixes bug
11248 7814; bugfix on 0.2.4.7-alpha.
11251 - Improve circuit build timeout handling for hidden services.
11252 In particular: adjust build timeouts more accurately depending
11253 upon the number of hop-RTTs that a particular circuit type
11254 undergoes. Additionally, launch intro circuits in parallel
11255 if they timeout, and take the first one to reply as valid.
11256 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
11257 separate error codes; or at least, don't break for that reason.
11258 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
11259 - Update to the January 2 2013 Maxmind GeoLite Country database.
11261 o Minor features (testing):
11262 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
11263 (P-256) Diffie-Hellman handshakes to src/or/bench.
11264 - Add benchmark functions to test onion handshake performance.
11266 o Minor features (path bias detection):
11267 - Alter the Path Bias log messages to be more descriptive in terms
11268 of reporting timeouts and other statistics.
11269 - Create three levels of Path Bias log messages, as opposed to just
11270 two. These are configurable via consensus as well as via the torrc
11271 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
11272 The default values are 0.70, 0.50, and 0.30 respectively.
11273 - Separate the log message levels from the decision to drop guards,
11274 which also is available via torrc option PathBiasDropGuards.
11275 PathBiasDropGuards still defaults to 0 (off).
11276 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
11277 in combination with PathBiasExtremeRate.
11278 - Increase the default values for PathBiasScaleThreshold and
11279 PathBiasCircThreshold from (200, 20) to (300, 150).
11280 - Add in circuit usage accounting to path bias. If we try to use a
11281 built circuit but fail for any reason, it counts as path bias.
11282 Certain classes of circuits where the adversary gets to pick your
11283 destination node are exempt from this accounting. Usage accounting
11284 can be specifically disabled via consensus parameter or torrc.
11285 - Convert all internal path bias state to double-precision floating
11286 point, to avoid roundoff error and other issues.
11287 - Only record path bias information for circuits that have completed
11288 *two* hops. Assuming end-to-end tagging is the attack vector, this
11289 makes us more resilient to ambient circuit failure without any
11290 detection capability loss.
11292 o Minor bugfixes (log messages):
11293 - Rate-limit the "No circuits are opened. Relaxed timeout for a
11294 circuit with channel state open..." message to once per hour to
11295 keep it from filling the notice logs. Mitigates bug 7799 but does
11296 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
11297 - Avoid spurious warnings when configuring multiple client ports of
11298 which only some are nonlocal. Previously, we had claimed that some
11299 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
11302 o Code simplifications and refactoring:
11303 - Get rid of a couple of harmless clang warnings, where we compared
11304 enums to ints. These warnings are newly introduced in clang 3.2.
11305 - Split the onion.c file into separate modules for the onion queue
11306 and the different handshakes it supports.
11307 - Remove the marshalling/unmarshalling code for sending requests to
11308 cpuworkers over a socket, and instead just send structs. The
11309 recipient will always be the same Tor binary as the sender, so
11310 any encoding is overkill.
11313 Changes in version 0.2.4.7-alpha - 2012-12-24
11314 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
11315 directory mirrors for more robust bootstrapping; fixes more issues where
11316 clients with changing network conditions refuse to make any circuits;
11317 adds initial support for exiting to IPv6 addresses; resumes being able
11318 to update our GeoIP database, and includes the geoip6 file this time;
11319 turns off the client-side DNS cache by default due to privacy risks;
11320 and fixes a variety of other issues.
11322 o Major features (client resilience):
11323 - Add a new "FallbackDir" torrc option to use when we can't use
11324 a directory mirror from the consensus (either because we lack a
11325 consensus, or because they're all down). Currently, all authorities
11326 are fallbacks by default, and there are no other default fallbacks,
11327 but that will change. This option will allow us to give clients a
11328 longer list of servers to try to get a consensus from when first
11329 connecting to the Tor network, and thereby reduce load on the
11330 directory authorities. Implements proposal 206, "Preconfigured
11331 directory sources for bootstrapping". We also removed the old
11332 "FallbackNetworkstatus" option, since we never got it working well
11333 enough to use it. Closes bug 572.
11334 - If we have no circuits open, use a relaxed timeout (the
11335 95-percentile cutoff) until a circuit succeeds. This heuristic
11336 should allow Tor to succeed at building circuits even when the
11337 network connection drastically changes. Should help with bug 3443.
11339 o Major features (IPv6):
11340 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
11341 connectivity, then set the IPv6Exit flag to 1. Also make sure your
11342 exit policy reads as you would like: the address * applies to all
11343 address families, whereas *4 is IPv4 address only, and *6 is IPv6
11344 addresses only. On the client side, you'll need to wait until the
11345 authorities have upgraded, wait for enough exits to support IPv6,
11346 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
11347 ticket 5547, implements proposal 117 as revised in proposal 208.
11349 We DO NOT recommend that clients with actual anonymity needs start
11350 using IPv6 over Tor yet, since not enough exits support it yet.
11352 o Major features (geoip database):
11353 - Maxmind began labelling Tor relays as being in country "A1",
11354 which breaks by-country node selection inside Tor. Now we use a
11355 script to replace "A1" ("Anonymous Proxy") entries in our geoip
11356 file with real country codes. This script fixes about 90% of "A1"
11357 entries automatically and uses manual country code assignments to
11358 fix the remaining 10%. See src/config/README.geoip for details.
11359 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
11360 Country database, as modified above.
11362 o Major bugfixes (client-side DNS):
11363 - Turn off the client-side DNS cache by default. Updating and using
11364 the DNS cache is now configurable on a per-client-port
11365 level. SOCKSPort, DNSPort, etc lines may now contain
11366 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
11367 cache these types of DNS answers when we receive them from an
11368 exit node in response to an application request on this port, and
11369 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
11370 cached DNS answers of these types, we shouldn't use them. It's
11371 potentially risky to use cached DNS answers at the client, since
11372 doing so can indicate to one exit what answers we've gotten
11373 for DNS lookups in the past. With IPv6, this becomes especially
11374 problematic. Using cached DNS answers for requests on the same
11375 circuit would present less linkability risk, since all traffic
11376 on a circuit is already linkable, but it would also provide
11377 little performance benefit: the exit node caches DNS replies
11378 too. Implements a simplified version of Proposal 205. Implements
11381 o Major bugfixes (other):
11382 - Alter circuit build timeout measurement to start at the point
11383 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
11384 initialization). This should make our timeout measurements more
11385 uniform. Previously, we were sometimes including ORconn setup time
11386 in our circuit build time measurements. Should resolve bug 3443.
11387 - Fix an assertion that could trigger in hibernate_go_dormant() when
11388 closing an or_connection_t: call channel_mark_for_close() rather
11389 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
11391 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
11392 7655; bugfix on 0.2.4.6-alpha.
11395 - Add a new torrc option "ServerTransportListenAddr" to let bridge
11396 operators select the address where their pluggable transports will
11397 listen for connections. Resolves ticket 7013.
11398 - Allow an optional $ before the node identity digest in the
11399 controller command GETINFO ns/id/<identity>, for consistency with
11400 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
11401 - Log packaged cell fullness as part of the heartbeat message.
11402 Diagnosis to try to determine the extent of bug 7743.
11404 o Minor features (IPv6):
11405 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
11406 prefer to hand out virtual IPv6 addresses, since there are more of
11407 them and we can't run out. To override this behavior and make IPv4
11408 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
11409 or DNSPort you're using for resolving. Implements ticket 7571.
11410 - AutomapHostsOnResolve responses are now randomized, to avoid
11411 annoying situations where Tor is restarted and applications
11412 connect to the wrong addresses.
11413 - Never try more than 1000 times to pick a new virtual address when
11414 AutomapHostsOnResolve is set. That's good enough so long as we
11415 aren't close to handing out our entire virtual address space;
11416 if you're getting there, it's best to switch to IPv6 virtual
11420 - The ADDRMAP command can no longer generate an ill-formed error
11421 code on a failed MAPADDRESS. It now says "internal" rather than
11422 an English sentence fragment with spaces in the middle. Bugfix on
11423 Tor 0.2.0.19-alpha.
11424 - Fix log messages and comments to avoid saying "GMT" when we mean
11425 "UTC". Fixes bug 6113.
11426 - Compile on win64 using mingw64. Fixes bug 7260; patches from
11428 - Fix a crash when debugging unit tests on Windows: deallocate a
11429 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
11430 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
11433 - The DirServer option is now DirAuthority, for consistency with
11434 current naming patterns. You can still use the old DirServer form.
11436 o Code simplification and refactoring:
11437 - Move the client-side address-map/virtual-address/DNS-cache code
11438 out of connection_edge.c into a new addressmap.c module.
11439 - Remove unused code for parsing v1 directories and "running routers"
11440 documents. Fixes bug 6887.
11443 Changes in version 0.2.3.25 - 2012-11-19
11444 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
11445 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
11446 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
11447 programmer, and friend. Unstinting in his dedication to the cause of
11448 freedom, he inspired and helped many of us as we began our work on
11449 anonymity, and inspires us still. Please honor his memory by writing
11450 software to protect people's freedoms, and by helping others to do so.
11452 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
11453 significantly reduced directory overhead (via microdescriptors),
11454 enormous crypto performance improvements for fast relays on new
11455 enough hardware, a new v3 TLS handshake protocol that can better
11456 resist fingerprinting, support for protocol obfuscation plugins (aka
11457 pluggable transports), better scalability for hidden services, IPv6
11458 support for bridges, performance improvements like allowing clients
11459 to skip the first round-trip on the circuit ("optimistic data") and
11460 refilling token buckets more often, a new "stream isolation" design
11461 to isolate different applications on different circuits, and many
11462 stability, security, and privacy fixes.
11465 - Tor tries to wipe potentially sensitive data after using it, so
11466 that if some subsequent security failure exposes Tor's memory,
11467 the damage will be limited. But we had a bug where the compiler
11468 was eliminating these wipe operations when it decided that the
11469 memory was no longer visible to a (correctly running) program,
11470 hence defeating our attempt at defense in depth. We fix that
11471 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
11472 is unlikely to optimize away. Future versions of Tor may use
11473 a less ridiculously heavy approach for this. Fixes bug 7352.
11474 Reported in an article by Andrey Karpov.
11477 - Fix a harmless bug when opting against publishing a relay descriptor
11478 because DisableNetwork is set. Fixes bug 7464; bugfix on
11482 Changes in version 0.2.4.6-alpha - 2012-11-13
11483 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
11484 makes our defense-in-depth memory wiping more reliable, and begins to
11485 count IPv6 addresses in bridge statistics,
11488 - Fix an assertion failure that could occur when closing a connection
11489 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
11491 - Tor tries to wipe potentially sensitive data after using it, so
11492 that if some subsequent security failure exposes Tor's memory,
11493 the damage will be limited. But we had a bug where the compiler
11494 was eliminating these wipe operations when it decided that the
11495 memory was no longer visible to a (correctly running) program,
11496 hence defeating our attempt at defense in depth. We fix that
11497 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
11498 is unlikely to optimize away. Future versions of Tor may use
11499 a less ridiculously heavy approach for this. Fixes bug 7352.
11500 Reported in an article by Andrey Karpov.
11503 - Add GeoIP database for IPv6 addresses. The new config option
11505 - Bridge statistics now count bridge clients connecting over IPv6:
11506 bridge statistics files now list "bridge-ip-versions" and
11507 extra-info documents list "geoip6-db-digest". The control protocol
11508 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
11509 implementation by "shkoo", addressing ticket 5055.
11512 - Warn when we are binding low ports when hibernation is enabled;
11513 previously we had warned when we were _advertising_ low ports with
11514 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
11515 - Fix a harmless bug when opting against publishing a relay descriptor
11516 because DisableNetwork is set. Fixes bug 7464; bugfix on
11518 - Add warning message when a managed proxy dies during configuration.
11519 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
11520 - Fix a linking error when building tor-fw-helper without miniupnp.
11521 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
11522 - Check for closing an or_connection_t without going through correct
11523 channel functions; emit a warning and then call
11524 connection_or_close_for_error() so we don't assert as in bugs 7212
11526 - Compile correctly on compilers without C99 designated initializer
11527 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
11528 - Avoid a possible assert that can occur when channel_send_destroy() is
11529 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
11530 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
11531 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
11532 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
11533 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
11535 o Code simplification and refactoring:
11536 - Start using OpenBSD's implementation of queue.h, so that we don't
11537 need to hand-roll our own pointer and list structures whenever we
11538 need them. (We can't rely on a sys/queue.h, since some operating
11539 systems don't have them, and the ones that do have them don't all
11540 present the same extensions.)
11543 Changes in version 0.2.4.5-alpha - 2012-10-25
11544 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
11545 two important security vulnerabilities that could lead to remotely
11546 triggerable relay crashes, fix a major bug that was preventing clients
11547 from choosing suitable exit nodes, and refactor some of our code.
11549 o Major bugfixes (security, also in 0.2.3.24-rc):
11550 - Fix a group of remotely triggerable assertion failures related to
11551 incorrect link protocol negotiation. Found, diagnosed, and fixed
11552 by "some guy from France". Fix for CVE-2012-2250; bugfix on
11554 - Fix a denial of service attack by which any directory authority
11555 could crash all the others, or by which a single v2 directory
11556 authority could crash everybody downloading v2 directory
11557 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
11559 o Major bugfixes (also in 0.2.3.24-rc):
11560 - When parsing exit policy summaries from microdescriptors, we had
11561 previously been ignoring the last character in each one, so that
11562 "accept 80,443,8080" would be treated by clients as indicating
11563 a node that allows access to ports 80, 443, and 808. That would
11564 lead to clients attempting connections that could never work,
11565 and ignoring exit nodes that would support their connections. Now
11566 clients parse these exit policy summaries correctly. Fixes bug 7192;
11567 bugfix on 0.2.3.1-alpha.
11569 o Minor bugfixes (also in 0.2.3.24-rc):
11570 - Clients now consider the ClientRejectInternalAddresses config option
11571 when using a microdescriptor consensus stanza to decide whether
11572 an exit relay would allow exiting to an internal address. Fixes
11573 bug 7190; bugfix on 0.2.3.1-alpha.
11576 - Only disable TLS session ticket support when running as a TLS
11577 server. Now clients will blend better with regular Firefox
11578 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
11580 o Code simplification and refactoring:
11581 - Start using OpenBSD's implementation of queue.h (originally by
11583 - Move the entry node code from circuitbuild.c to its own file.
11584 - Move the circuit build timeout tracking code from circuitbuild.c
11588 Changes in version 0.2.3.24-rc - 2012-10-25
11589 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
11590 could lead to remotely triggerable relay crashes, and fixes
11591 a major bug that was preventing clients from choosing suitable exit
11594 o Major bugfixes (security):
11595 - Fix a group of remotely triggerable assertion failures related to
11596 incorrect link protocol negotiation. Found, diagnosed, and fixed
11597 by "some guy from France". Fix for CVE-2012-2250; bugfix on
11599 - Fix a denial of service attack by which any directory authority
11600 could crash all the others, or by which a single v2 directory
11601 authority could crash everybody downloading v2 directory
11602 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
11605 - When parsing exit policy summaries from microdescriptors, we had
11606 previously been ignoring the last character in each one, so that
11607 "accept 80,443,8080" would be treated by clients as indicating
11608 a node that allows access to ports 80, 443, and 808. That would
11609 lead to clients attempting connections that could never work,
11610 and ignoring exit nodes that would support their connections. Now
11611 clients parse these exit policy summaries correctly. Fixes bug 7192;
11612 bugfix on 0.2.3.1-alpha.
11615 - Clients now consider the ClientRejectInternalAddresses config option
11616 when using a microdescriptor consensus stanza to decide whether
11617 an exit relay would allow exiting to an internal address. Fixes
11618 bug 7190; bugfix on 0.2.3.1-alpha.
11621 Changes in version 0.2.4.4-alpha - 2012-10-20
11622 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
11623 vulnerability introduced by a change in OpenSSL, fixes a remotely
11624 triggerable assert, and adds new channel_t and circuitmux_t abstractions
11625 that will make it easier to test new connection transport and cell
11626 scheduling algorithms.
11628 o New directory authorities (also in 0.2.3.23-rc):
11629 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
11630 authority. Closes ticket 5749.
11632 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
11633 - Disable TLS session tickets. OpenSSL's implementation was giving
11634 our TLS session keys the lifetime of our TLS context objects, when
11635 perfect forward secrecy would want us to discard anything that
11636 could decrypt a link connection as soon as the link connection
11637 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
11638 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
11639 - Discard extraneous renegotiation attempts once the V3 link
11640 protocol has been initiated. Failure to do so left us open to
11641 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
11642 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
11644 o Internal abstraction features:
11645 - Introduce new channel_t abstraction between circuits and
11646 or_connection_t to allow for implementing alternate OR-to-OR
11647 transports. A channel_t is an abstract object which can either be a
11648 cell-bearing channel, which is responsible for authenticating and
11649 handshaking with the remote OR and transmitting cells to and from
11650 it, or a listening channel, which spawns new cell-bearing channels
11651 at the request of remote ORs. Implements part of ticket 6465.
11652 - Also new is the channel_tls_t subclass of channel_t, adapting it
11653 to the existing or_connection_t code. The V2/V3 protocol handshaking
11654 code which formerly resided in command.c has been moved below the
11655 channel_t abstraction layer and may be found in channeltls.c now.
11656 Implements the rest of ticket 6465.
11657 - Introduce new circuitmux_t storing the queue of circuits for
11658 a channel; this encapsulates and abstracts the queue logic and
11659 circuit selection policy, and allows the latter to be overridden
11660 easily by switching out a policy object. The existing EWMA behavior
11661 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
11663 o Required libraries:
11664 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
11665 strongly recommended.
11668 - Warn users who run hidden services on a Tor client with
11669 UseEntryGuards disabled that their hidden services will be
11670 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
11671 attack which motivated Tor to support entry guards in the first
11672 place). Resolves ticket 6889.
11673 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
11674 dhill. Resolves ticket 6982.
11675 - Option OutboundBindAddress can be specified multiple times and
11676 accepts IPv6 addresses. Resolves ticket 6876.
11678 o Minor bugfixes (also in 0.2.3.23-rc):
11679 - Don't serve or accept v2 hidden service descriptors over a
11680 relay's DirPort. It's never correct to do so, and disabling it
11681 might make it more annoying to exploit any bugs that turn up in the
11682 descriptor-parsing code. Fixes bug 7149.
11683 - Fix two cases in src/or/transports.c where we were calling
11684 fmt_addr() twice in a parameter list. Bug found by David
11685 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
11686 - Fix memory leaks whenever we logged any message about the "path
11687 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
11688 - When relays refuse a "create" cell because their queue of pending
11689 create cells is too big (typically because their cpu can't keep up
11690 with the arrival rate), send back reason "resource limit" rather
11691 than reason "internal", so network measurement scripts can get a
11692 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
11695 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
11696 - Free some more still-in-use memory at exit, to make hunting for
11697 memory leaks easier. Resolves bug 7029.
11698 - When a Tor client gets a "truncated" relay cell, the first byte of
11699 its payload specifies why the circuit was truncated. We were
11700 ignoring this 'reason' byte when tearing down the circuit, resulting
11701 in the controller not being told why the circuit closed. Now we
11702 pass the reason from the truncated cell to the controller. Bugfix
11703 on 0.1.2.3-alpha; fixes bug 7039.
11704 - Downgrade "Failed to hand off onionskin" messages to "debug"
11705 severity, since they're typically redundant with the "Your computer
11706 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
11707 - Make clients running with IPv6 bridges connect over IPv6 again,
11708 even without setting new config options ClientUseIPv6 and
11709 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
11710 - Use square brackets around IPv6 addresses in numerous places
11711 that needed them, including log messages, HTTPS CONNECT proxy
11712 requests, TransportProxy statefile entries, and pluggable transport
11713 extra-info lines. Fixes bug 7011; patch by David Fifield.
11715 o Code refactoring and cleanup:
11716 - Source files taken from other packages now reside in src/ext;
11717 previously they were scattered around the rest of Tor.
11718 - Avoid use of reserved identifiers in our C code. The C standard
11719 doesn't like us declaring anything that starts with an
11720 underscore, so let's knock it off before we get in trouble. Fix
11721 for bug 1031; bugfix on the first Tor commit.
11724 Changes in version 0.2.3.23-rc - 2012-10-20
11725 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
11726 vulnerability introduced by a change in OpenSSL, and fixes a variety
11727 of smaller bugs in preparation for the release.
11729 o New directory authorities:
11730 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
11731 authority. Closes ticket 5749.
11733 o Major bugfixes (security/privacy):
11734 - Disable TLS session tickets. OpenSSL's implementation was giving
11735 our TLS session keys the lifetime of our TLS context objects, when
11736 perfect forward secrecy would want us to discard anything that
11737 could decrypt a link connection as soon as the link connection
11738 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
11739 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
11740 - Discard extraneous renegotiation attempts once the V3 link
11741 protocol has been initiated. Failure to do so left us open to
11742 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
11743 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
11746 - Fix a possible crash bug when checking for deactivated circuits
11747 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
11748 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
11750 o Minor bugfixes (on 0.2.3.x):
11751 - Fix two cases in src/or/transports.c where we were calling
11752 fmt_addr() twice in a parameter list. Bug found by David
11753 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
11754 - Convert an assert in the pathbias code to a log message. The assert
11755 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
11756 bugfix on 0.2.3.17-beta.
11757 - Fix memory leaks whenever we logged any message about the "path
11758 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
11760 o Minor bugfixes (on 0.2.2.x and earlier):
11761 - Don't serve or accept v2 hidden service descriptors over a relay's
11762 DirPort. It's never correct to do so, and disabling it might
11763 make it more annoying to exploit any bugs that turn up in the
11764 descriptor-parsing code. Fixes bug 7149.
11765 - When relays refuse a "create" cell because their queue of pending
11766 create cells is too big (typically because their cpu can't keep up
11767 with the arrival rate), send back reason "resource limit" rather
11768 than reason "internal", so network measurement scripts can get a
11769 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
11770 - Correct file sizes when reading binary files on Cygwin, to avoid
11771 a bug where Tor would fail to read its state file. Fixes bug 6844;
11772 bugfix on 0.1.2.7-alpha.
11773 - Avoid undefined behavior when parsing the list of supported
11774 rendezvous/introduction protocols in a hidden service descriptor.
11775 Previously, Tor would have confused (as-yet-unused) protocol version
11776 numbers greater than 32 with lower ones on many platforms. Fixes
11777 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
11779 o Documentation fixes:
11780 - Clarify that hidden services are TCP only. Fixes bug 6024.
11783 Changes in version 0.2.4.3-alpha - 2012-09-22
11784 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
11785 assertion, resumes letting relays test reachability of their DirPort,
11786 and cleans up a bunch of smaller bugs.
11789 - Fix an assertion failure in tor_timegm() that could be triggered
11790 by a badly formatted directory object. Bug found by fuzzing with
11791 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
11794 - Fix a possible crash bug when checking for deactivated circuits
11795 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
11796 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
11797 - Allow routers to detect that their own DirPorts are running. When
11798 we removed support for versions_supports_begindir, we also
11799 accidentally removed the mechanism we used to self-test our
11800 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
11801 bugfix on 0.2.4.2-alpha.
11803 o Security features:
11804 - Switch to a completely time-invariant approach for picking nodes
11805 weighted by bandwidth. Our old approach would run through the
11806 part of the loop after it had made its choice slightly slower
11807 than it ran through the part of the loop before it had made its
11808 choice. Addresses ticket 6538.
11809 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
11810 by tor2web clients allows hidden services to identify tor2web
11811 clients through their repeated selection of the same rendezvous
11812 and introduction point circuit endpoints (their guards). Resolves
11816 - Enable Tor to read configuration, state, and key information from
11817 a FIFO. Previously Tor would only read from files with a positive
11818 stat.st_size. Code from meejah; fixes bug 6044.
11821 - Correct file sizes when reading binary files on Cygwin, to avoid
11822 a bug where Tor would fail to read its state file. Fixes bug 6844;
11823 bugfix on 0.1.2.7-alpha.
11824 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
11825 bugfix on 0.2.0.3-alpha.
11826 - When complaining about a client port on a public address, log
11827 which address we're complaining about. Fixes bug 4020; bugfix on
11828 0.2.3.3-alpha. Patch by Tom Fitzhenry.
11829 - Convert an assert in the pathbias code to a log message. The assert
11830 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
11831 bugfix on 0.2.3.17-beta.
11832 - Our new buildsystem was overzealous about rebuilding manpages: it
11833 would rebuild them all whenever any one of them changed. Now our
11834 dependency checking should be correct. Fixes bug 6843; bugfix on
11836 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
11837 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
11838 - Correct log printout about which address family is preferred
11839 when connecting to a bridge with both an IPv4 and IPv6 OR port.
11840 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
11842 o Minor bugfixes (code cleanliness):
11843 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
11844 with large values. This situation was untriggered, but nevertheless
11845 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
11846 - Reject consensus votes with more than 64 known-flags. We aren't even
11847 close to that limit yet, and our code doesn't handle it correctly.
11848 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
11849 - Avoid undefined behavior when parsing the list of supported
11850 rendezvous/introduction protocols in a hidden service descriptor.
11851 Previously, Tor would have confused (as-yet-unused) protocol version
11852 numbers greater than 32 with lower ones on many platforms. Fixes
11853 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
11854 - Fix handling of rendezvous client authorization types over 8.
11855 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
11856 - Fix building with older versions of GCC (2.95, for one) that don't
11857 like preprocessor directives inside macro arguments. Found by
11858 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
11859 - Switch weighted node selection rule from using a list of doubles
11860 to using a list of int64_t. This change should make the process
11861 slightly easier to debug and maintain. Needed to finish ticket 6538.
11863 o Code simplification and refactoring:
11864 - Move the generic "config" code into a new file, and have "config.c"
11865 hold only torrc- and state-related code. Resolves ticket 6823.
11866 - Move the core of our "choose a weighted element at random" logic
11867 into its own function, and give it unit tests. Now the logic is
11868 testable, and a little less fragile too.
11869 - Removed the testing_since field of node_t, which hasn't been used
11870 for anything since 0.2.0.9-alpha.
11872 o Documentation fixes:
11873 - Clarify that hidden services are TCP only. Fixes bug 6024.
11874 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
11878 Changes in version 0.2.3.22-rc - 2012-09-11
11879 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
11883 - Fix an assertion failure in tor_timegm() that could be triggered
11884 by a badly formatted directory object. Bug found by fuzzing with
11885 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
11888 - Avoid segfault when starting up having run with an extremely old
11889 version of Tor and parsing its state file. Fixes bug 6801; bugfix
11893 Changes in version 0.2.2.39 - 2012-09-11
11894 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
11898 - Fix an assertion failure in tor_timegm() that could be triggered
11899 by a badly formatted directory object. Bug found by fuzzing with
11900 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
11901 - Do not crash when comparing an address with port value 0 to an
11902 address policy. This bug could have been used to cause a remote
11903 assertion failure by or against directory authorities, or to
11904 allow some applications to crash clients. Fixes bug 6690; bugfix
11908 Changes in version 0.2.4.2-alpha - 2012-09-10
11909 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
11910 raises the default rate limiting even more, and makes the bootstrapping
11911 log messages less noisy.
11914 - Automatically forward the TCP ports of pluggable transport
11915 proxies using tor-fw-helper if PortForwarding is enabled. Implements
11919 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
11920 to 1GB/1GB. The previous defaults were intended to be "basically
11921 infinite", but it turns out they're now limiting our 100mbit+
11922 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
11923 last time we raised it).
11926 - Detect when we're running with a version of OpenSSL other than the
11927 one we compiled with. This has occasionally given people hard-to-
11929 - Log fewer lines at level "notice" about our OpenSSL and Libevent
11930 versions and capabilities when everything is going right. Resolves
11931 part of ticket 6736.
11932 - Directory authorities no long accept descriptors for any version of
11933 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
11934 These versions are insecure, unsupported, or both. Implements
11938 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
11939 to start with a triple-underscore so the controller won't touch it.
11940 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
11941 - Avoid segfault when starting up having run with an extremely old
11942 version of Tor and parsing its state file. Fixes bug 6801; bugfix
11944 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
11945 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
11946 - Don't follow the NULL pointer if microdescriptor generation fails.
11947 (This does not appear to be triggerable, but it's best to be safe.)
11948 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
11949 - Fix mis-declared dependencies on src/common/crypto.c and
11950 src/or/tor_main.c that could break out-of-tree builds under some
11951 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
11952 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
11953 6778; bugfix on 0.2.4.1-alpha.
11954 - Fix a harmless (in this case) build warning for implicitly
11955 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
11957 o Removed features:
11958 - Now that all versions before 0.2.2.x are disallowed, we no longer
11959 need to work around their missing features. Thus we can remove a
11960 bunch of compatibility code.
11962 o Code refactoring:
11963 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
11964 TCP ports to forward. In the past it only accepted two ports:
11965 the ORPort and the DirPort.
11968 Changes in version 0.2.4.1-alpha - 2012-09-05
11969 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
11970 bridgedb; lets relays use IPv6 addresses and directory authorities
11971 advertise them; and switches to a cleaner build interface.
11973 This is the first alpha release in a new series, so expect there to
11974 be bugs. Users who would rather test out a more stable branch should
11975 stay with 0.2.3.x for now.
11977 o Major features (bridges):
11978 - Bridges now report the pluggable transports they support to the
11979 bridge authority, so it can pass the supported transports on to
11980 bridgedb and/or eventually do reachability testing. Implements
11983 o Major features (IPv6):
11984 - Bridge authorities now accept IPv6 bridge addresses and include
11985 them in network status documents. Implements ticket 5534.
11986 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
11987 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
11988 to happen. Implements ticket 5535.
11989 - All kind of relays, not just bridges, can now advertise an IPv6
11990 OR port. Implements ticket 6362.
11991 - Directory authorities vote on IPv6 OR ports using the new consensus
11992 method 14. Implements ticket 6363.
11994 o Major features (build):
11995 - Switch to a nonrecursive Makefile structure. Now instead of each
11996 Makefile.am invoking other Makefile.am's, there is a master
11997 Makefile.am that includes the others. This change makes our build
11998 process slightly more maintainable, and improves parallelism for
11999 building with make -j. Original patch by Stewart Smith; various
12000 fixes by Jim Meyering.
12001 - Where available, we now use automake's "silent" make rules by
12002 default, so that warnings are easier to spot. You can get the old
12003 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
12005 o Minor features (code security and spec conformance):
12006 - Clear keys and key-derived material left on the stack in
12007 rendservice.c and rendclient.c. Check return value of
12008 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
12009 These fixes should make us more forward-secure against cold-boot
12010 attacks and the like. Fixes bug 2385.
12011 - Reject EXTEND cells sent to nonexistent streams. According to the
12012 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
12013 we were only checking for stream IDs that were currently in use.
12014 Found while hunting for more instances of bug 6271. Bugfix on
12015 0.0.2pre8, which introduced incremental circuit construction.
12017 o Minor features (streamlining);
12018 - No longer include the "opt" prefix when generating routerinfos
12019 or v2 directories: it has been needless since Tor 0.1.2. Closes
12021 - Remove some now-needless code that tried to aggressively flush
12022 OR connections as data was added to them. Since 0.2.0.1-alpha, our
12023 cell queue logic has saved us from the failure mode that this code
12024 was supposed to prevent. Removing this code will limit the number
12025 of baroque control flow paths through Tor's network logic. Reported
12026 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
12028 o Minor features (controller):
12029 - Add a "GETINFO signal/names" control port command. Implements
12031 - Provide default values for all options via "GETINFO config/defaults".
12032 Implements ticket 4971.
12034 o Minor features (IPv6):
12035 - New config option "AuthDirHasIPv6Connectivity 1" that directory
12036 authorities should set if they have IPv6 connectivity and want to
12037 do reachability tests for IPv6 relays. Implements feature 5974.
12038 - A relay with an IPv6 OR port now sends that address in NETINFO
12039 cells (in addition to its other address). Implements ticket 6364.
12041 o Minor features (log messages):
12042 - Omit the first heartbeat log message, because it never has anything
12043 useful to say, and it clutters up the bootstrapping messages.
12044 Resolves ticket 6758.
12045 - Don't log about reloading the microdescriptor cache at startup. Our
12046 bootstrap warnings are supposed to tell the user when there's a
12047 problem, and our bootstrap notices say when there isn't. Resolves
12048 ticket 6759; bugfix on 0.2.2.6-alpha.
12049 - Don't log "I learned some more directory information" when we're
12050 reading cached directory information. Reserve it for when new
12051 directory information arrives in response to a fetch. Resolves
12053 - Prevent rounding error in path bias counts when scaling
12054 them down, and use the correct scale factor default. Also demote
12055 some path bias related log messages down a level and make others
12056 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
12057 - We no longer warn so much when generating manpages from their
12060 o Code simplifications and refactoring:
12061 - Enhance our internal sscanf replacement so that we can eliminate
12062 the last remaining uses of the system sscanf. (Though those uses
12063 of sscanf were safe, sscanf itself is generally error prone, so
12064 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
12066 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
12067 - Move last_reachable and testing_since from routerinfo_t to node_t.
12068 Implements ticket 5529.
12069 - Add replaycache_t structure, functions and unit tests, then refactor
12070 rend_service_introduce() to be more clear to read, improve, debug,
12071 and test. Resolves bug 6177.
12072 - Finally remove support for malloc_good_size and malloc_usable_size.
12073 We had hoped that these functions would let us eke a little more
12074 memory out of our malloc implementation. Unfortunately, the only
12075 implementations that provided these functions are also ones that
12076 are already efficient about not overallocation: they never got us
12077 more than 7 or so bytes per allocation. Removing them saves us a
12078 little code complexity and a nontrivial amount of build complexity.
12080 o New requirements:
12081 - Tor maintainers now require Automake version 1.9 or later to build
12082 Tor from the Git repository. (Automake is not required when building
12083 from a source distribution.)
12086 Changes in version 0.2.3.21-rc - 2012-09-05
12087 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
12088 series. It fixes a trio of potential security bugs, fixes a bug where
12089 we were leaving some of the fast relays out of the microdescriptor
12090 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
12091 and cleans up other smaller issues.
12093 o Major bugfixes (security):
12094 - Tear down the circuit if we get an unexpected SENDME cell. Clients
12095 could use this trick to make their circuits receive cells faster
12096 than our flow control would have allowed, or to gum up the network,
12097 or possibly to do targeted memory denial-of-service attacks on
12098 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
12099 from July 2002, before the release of Tor 0.0.0. We had committed
12100 this patch previously, but we had to revert it because of bug 6271.
12101 Now that 6271 is fixed, this patch appears to work.
12102 - Reject any attempt to extend to an internal address. Without
12103 this fix, a router could be used to probe addresses on an internal
12104 network to see whether they were accepting connections. Fixes bug
12105 6710; bugfix on 0.0.8pre1.
12106 - Do not crash when comparing an address with port value 0 to an
12107 address policy. This bug could have been used to cause a remote
12108 assertion failure by or against directory authorities, or to
12109 allow some applications to crash clients. Fixes bug 6690; bugfix
12113 - Remove the upper bound on microdescriptor length. We were hitting
12114 the limit for routers with complex exit policies or family
12115 declarations, causing clients to not use them. Fixes the first
12116 piece of bug 6404; fix on 0.2.2.6-alpha.
12117 - Detect "ORPort 0" as meaning, uniformly, that we're not running
12118 as a relay. Previously, some of our code would treat the presence
12119 of any ORPort line as meaning that we should act like a relay,
12120 even though our new listener code would correctly not open any
12121 ORPorts for ORPort 0. Similar bugs in other Port options are also
12122 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
12125 - Avoid a pair of double-free and use-after-mark bugs that can
12126 occur with certain timings in canceled and re-received DNS
12127 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
12128 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
12129 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
12130 - Allow one-hop directory fetching circuits the full "circuit build
12131 timeout" period, rather than just half of it, before failing them
12132 and marking the relay down. This fix should help reduce cases where
12133 clients declare relays (or worse, bridges) unreachable because
12134 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
12135 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
12137 - Authorities no longer include any router in their microdescriptor
12138 consensuses for which they couldn't generate or agree on a
12139 microdescriptor. Fixes the second piece of bug 6404; fix on
12141 - Detect and reject attempts to specify both "FooPort" and
12142 "FooPort 0" in the same configuration domain. (It's still okay
12143 to have a FooPort in your configuration file, and use "FooPort 0"
12144 on the command line to disable it.) Fixes the second half of bug
12145 6507; bugfix on 0.2.3.3-alpha.
12146 - Make wildcarded addresses (that is, ones beginning with "*.") work
12147 when provided via the controller's MapAddress command. Previously,
12148 they were accepted, but we never actually noticed that they were
12149 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
12150 - Avoid crashing on a malformed state file where EntryGuardPathBias
12151 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
12152 - Add a (probably redundant) memory clear between iterations of
12153 the router status voting loop, to prevent future coding errors
12154 where data might leak between iterations of the loop. Resolves
12157 o Minor bugfixes (log messages):
12158 - Downgrade "set buildtimeout to low value" messages to "info"
12159 severity; they were never an actual problem, there was never
12160 anything reasonable to do about them, and they tended to spam logs
12161 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
12162 - Downgrade path-bias warning messages to "info". We'll try to get
12163 them working better in 0.2.4. Add internal circuit construction
12164 state to protect against the noisy warn message "Unexpectedly high
12165 circuit_successes". Also add some additional rate-limited notice
12166 messages to help determine the root cause of the warn. Fixes bug
12167 6475. Bugfix against 0.2.3.17-beta.
12168 - Move log message when unable to find a microdesc in a routerstatus
12169 entry to parse time. Previously we'd spam this warning every time
12170 we tried to figure out which microdescriptors to download. Fixes
12171 the third piece of bug 6404; fix on 0.2.3.18-rc.
12174 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
12175 change when the authority is deciding whether to accept a newly
12176 uploaded descriptor. Implements ticket 6423.
12177 - Add missing documentation for consensus and microdesc files.
12178 Resolves ticket 6732.
12181 Changes in version 0.2.2.38 - 2012-08-12
12182 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
12183 attack that could in theory leak path information.
12186 - Avoid an uninitialized memory read when reading a vote or consensus
12187 document that has an unrecognized flavor name. This read could
12188 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
12189 - Try to leak less information about what relays a client is
12190 choosing to a side-channel attacker. Previously, a Tor client would
12191 stop iterating through the list of available relays as soon as it
12192 had chosen one, thus finishing a little earlier when it picked
12193 a router earlier in the list. If an attacker can recover this
12194 timing information (nontrivial but not proven to be impossible),
12195 they could learn some coarse-grained information about which relays
12196 a client was picking (middle nodes in particular are likelier to
12197 be affected than exits). The timing attack might be mitigated by
12198 other factors (see bug 6537 for some discussion), but it's best
12199 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
12202 Changes in version 0.2.3.20-rc - 2012-08-05
12203 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
12204 series. It fixes a pair of code security bugs and a potential anonymity
12205 issue, updates our RPM spec files, and cleans up other smaller issues.
12208 - Avoid read-from-freed-memory and double-free bugs that could occur
12209 when a DNS request fails while launching it. Fixes bug 6480;
12210 bugfix on 0.2.0.1-alpha.
12211 - Avoid an uninitialized memory read when reading a vote or consensus
12212 document that has an unrecognized flavor name. This read could
12213 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
12214 - Try to leak less information about what relays a client is
12215 choosing to a side-channel attacker. Previously, a Tor client would
12216 stop iterating through the list of available relays as soon as it
12217 had chosen one, thus finishing a little earlier when it picked
12218 a router earlier in the list. If an attacker can recover this
12219 timing information (nontrivial but not proven to be impossible),
12220 they could learn some coarse-grained information about which relays
12221 a client was picking (middle nodes in particular are likelier to
12222 be affected than exits). The timing attack might be mitigated by
12223 other factors (see bug 6537 for some discussion), but it's best
12224 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
12227 - Try to make the warning when giving an obsolete SOCKSListenAddress
12228 a little more useful.
12229 - Terminate active server managed proxies if Tor stops being a
12230 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
12231 - Provide a better error message about possible OSX Asciidoc failure
12232 reasons. Fixes bug 6436.
12233 - Warn when Tor is configured to use accounting in a way that can
12234 link a hidden service to some other hidden service or public
12235 address. Resolves ticket 6490.
12238 - Check return value of fputs() when writing authority certificate
12239 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
12240 - Ignore ServerTransportPlugin lines when Tor is not configured as
12241 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
12242 - When disabling guards for having too high a proportion of failed
12243 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
12247 - Update our default RPM spec files to work with mock and rpmbuild
12248 on RHEL/Fedora. They have an updated set of dependencies and
12249 conflicts, a fix for an ancient typo when creating the "_tor"
12250 user, and better instructions. Thanks to Ondrej Mikle for the
12251 patch series. Fixes bug 6043.
12254 - Make it possible to set the TestingTorNetwork configuration
12255 option using AlternateDirAuthority and AlternateBridgeAuthority
12256 as an alternative to setting DirServer. Addresses ticket 6377.
12259 - Clarify the documentation for the Alternate*Authority options.
12261 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
12263 o Code simplification and refactoring:
12264 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
12265 10 lines. Also, don't nest them. Doing so in the past has
12266 led to hard-to-debug code. The new style is to use the
12267 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
12270 Changes in version 0.2.3.19-rc - 2012-07-06
12271 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
12272 series. It fixes the compile on Windows, reverts to a GeoIP database
12273 that isn't as broken, and fixes a flow control bug that has been around
12274 since the beginning of Tor.
12277 - Fix a bug handling SENDME cells on nonexistent streams that could
12278 result in bizarre window values. Report and patch contributed
12279 pseudonymously. Fixes part of bug 6271. This bug was introduced
12280 before the first Tor release, in svn commit r152.
12281 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
12282 June 2012 database, Maxmind marked many Tor relays as country "A1",
12283 which will cause risky behavior for clients that set EntryNodes
12284 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
12285 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
12286 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
12289 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
12290 bugfix on 0.2.1.10-alpha.
12293 Changes in version 0.2.3.18-rc - 2012-06-28
12294 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
12295 series. It fixes a few smaller bugs, but generally appears stable.
12296 Please test it and let us know whether it is!
12299 - Allow wildcarded mapaddress targets to be specified on the
12300 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
12301 - Make our linker option detection code more robust against linkers
12302 such as on FreeBSD 8, where a bad combination of options completes
12303 successfully but makes an unrunnable binary. Fixes bug 6173;
12304 bugfix on 0.2.3.17-beta.
12306 o Minor bugfixes (on 0.2.2.x and earlier):
12307 - Avoid a false positive in the util/threads unit test by increasing
12308 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
12309 - Replace "Sending publish request" log messages with "Launching
12310 upload", so that they no longer confusingly imply that we're
12311 sending something to a directory we might not even be connected
12312 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
12313 - Make sure to set *socket_error in all error cases in
12314 connection_connect(), so it can't produce a warning about
12315 errno being zero from errno_to_orconn_end_reason(). Bugfix on
12316 0.2.1.1-alpha; resolves ticket 6028.
12317 - Downgrade "Got a certificate, but we already have it" log messages
12318 from warning to info, except when we're a dirauth. Fixes bug 5238;
12319 bugfix on 0.2.1.7-alpha.
12320 - When checking for requested signatures on the latest consensus
12321 before serving it to a client, make sure to check the right
12322 consensus flavor. Bugfix on 0.2.2.6-alpha.
12323 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
12324 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
12326 o Minor bugfixes (on 0.2.3.x):
12327 - Make format_helper_exit_status() avoid unnecessary space padding
12328 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
12330 - Downgrade a message about cleaning the microdescriptor cache to
12331 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
12332 - Log a BUG message at severity INFO if we have a networkstatus with
12333 a missing entry for some microdescriptor. Continues on a patch
12335 - Improve the log message when a managed proxy fails to launch. Fixes
12336 bug 5099; bugfix on 0.2.3.6-alpha.
12337 - Don't do DNS lookups when parsing corrupted managed proxy protocol
12338 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
12339 - When formatting wildcarded address mappings for the controller,
12340 be sure to include "*." as appropriate. Partially fixes bug 6244;
12341 bugfix on 0.2.3.9-alpha.
12342 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
12343 Bugfix on 0.2.3.13-alpha.
12344 - Stop logging messages about running with circuit timeout learning
12345 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
12346 - Disable a spurious warning about reading on a marked and flushing
12347 connection. We shouldn't be doing that, but apparently we
12348 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
12349 - Fix a bug that stopped AllowDotExit from working on addresses
12350 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
12353 o Code simplification, refactoring, unit tests:
12354 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
12355 Libevent's notion of cached time when possible.
12356 - Remove duplicate code for invoking getrlimit() from control.c.
12357 - Add a unit test for the environment_variable_names_equal function.
12360 - Document the --defaults-torrc option, and the new (in 0.2.3)
12361 semantics for overriding, extending, and clearing lists of
12362 options. Closes bug 4748.
12365 Changes in version 0.2.3.17-beta - 2012-06-15
12366 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
12367 gets our TLS handshake back on track for being able to blend in with
12368 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
12369 with Vidalia, and otherwise continues to get us closer to a release
12373 - Enable gcc and ld hardening by default. Resolves ticket 5210.
12374 - Update TLS cipher list to match Firefox 8 and later. Resolves
12376 - Implement the client side of proposal 198: remove support for
12377 clients falsely claiming to support standard ciphersuites that
12378 they can actually provide. As of modern OpenSSL versions, it's not
12379 necessary to fake any standard ciphersuite, and doing so prevents
12380 us from using better ciphersuites in the future, since servers
12381 can't know whether an advertised ciphersuite is really supported or
12382 not. Some hosts -- notably, ones with very old versions of OpenSSL
12383 or where OpenSSL has been built with ECC disabled -- will stand
12384 out because of this change; TBB users should not be affected.
12387 - Change the default value for DynamicDHGroups (introduced in
12388 0.2.3.9-alpha) to 0. This feature can make Tor relays less
12389 identifiable by their use of the mod_ssl DH group, but at
12390 the cost of some usability (#4721) and bridge tracing (#6087)
12391 regressions. Resolves ticket 5598.
12392 - Send a CRLF at the end of each STATUS_* control protocol event. This
12393 bug tickled a bug in Vidalia which would make it freeze. Fixes
12394 bug 6094; bugfix on 0.2.3.16-alpha.
12397 - Disable writing on marked-for-close connections when they are
12398 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
12399 bug 5263; bugfix on 0.0.2pre13, where we first added a special
12400 case for flushing marked connections.
12401 - Detect SSL handshake even when the initial attempt to write the
12402 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
12403 - Change the AllowDotExit rules so they should actually work.
12404 We now enforce AllowDotExit only immediately after receiving an
12405 address via SOCKS or DNSPort: other sources are free to provide
12406 .exit addresses after the resolution occurs. Fixes bug 3940;
12407 bugfix on 0.2.2.1-alpha.
12408 - Fix a (harmless) integer overflow in cell statistics reported by
12409 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
12410 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
12411 right places and never depends on the consensus parameters or
12412 computes adaptive timeouts when it is disabled. Fixes bug 5049;
12413 bugfix on 0.2.2.14-alpha.
12414 - When building Tor on Windows with -DUNICODE (not default), ensure
12415 that error messages, filenames, and DNS server names are always
12416 NUL-terminated when we convert them to a single-byte encoding.
12417 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
12418 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
12419 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
12420 - Fix an edge case where TestingTorNetwork is set but the authorities
12421 and relays all have an uptime of zero, where the private Tor network
12422 could briefly lack support for hidden services. Fixes bug 3886;
12423 bugfix on 0.2.2.18-alpha.
12424 - Correct the manpage's descriptions for the default values of
12425 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
12427 - Fix the documentation for the --hush and --quiet command line
12428 options, which changed their behavior back in 0.2.3.3-alpha.
12429 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
12433 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
12434 more information to it, so that we can track it down in case it
12435 returns again. Mitigates bug 5235.
12436 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
12437 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
12438 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
12439 - Warn the user when HTTPProxy, but no other proxy type, is
12440 configured. This can cause surprising behavior: it doesn't send
12441 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
12442 directory traffic only. Resolves ticket 4663.
12443 - Issue a notice if a guard completes less than 40% of your circuits.
12444 Threshold is configurable by torrc option PathBiasNoticeRate and
12445 consensus parameter pb_noticepct. There is additional, off-by-
12446 default code to disable guards which fail too many circuits.
12447 Addresses ticket 5458.
12448 - Update to the June 6 2012 Maxmind GeoLite Country database.
12450 o Code simplifications and refactoring:
12451 - Remove validate_pluggable_transports_config(): its warning
12452 message is now handled by connection_or_connect().
12455 Changes in version 0.2.2.37 - 2012-06-06
12456 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
12457 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
12461 - Work around a bug in OpenSSL that broke renegotiation with TLS
12462 1.1 and TLS 1.2. Without this workaround, all attempts to speak
12463 the v2 Tor connection protocol when both sides were using OpenSSL
12464 1.0.1 would fail. Resolves ticket 6033.
12465 - When waiting for a client to renegotiate, don't allow it to add
12466 any bytes to the input buffer. This fixes a potential DoS issue.
12467 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
12468 - Fix an edge case where if we fetch or publish a hidden service
12469 descriptor, we might build a 4-hop circuit and then use that circuit
12470 for exiting afterwards -- even if the new last hop doesn't obey our
12471 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
12474 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
12475 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
12478 - Tell GCC and Clang to check for any errors in format strings passed
12479 to the tor_v*(print|scan)f functions.
12482 Changes in version 0.2.3.16-alpha - 2012-06-05
12483 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
12484 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
12485 currently). It also fixes a variety of smaller bugs and other cleanups
12486 that get us closer to a release candidate.
12488 o Major bugfixes (general):
12489 - Work around a bug in OpenSSL that broke renegotiation with TLS
12490 1.1 and TLS 1.2. Without this workaround, all attempts to speak
12491 the v2 Tor connection protocol when both sides were using OpenSSL
12492 1.0.1 would fail. Resolves ticket 6033.
12493 - When waiting for a client to renegotiate, don't allow it to add
12494 any bytes to the input buffer. This fixes a potential DoS issue.
12495 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
12496 - Pass correct OR address to managed proxies (like obfsproxy),
12497 even when ORListenAddress is used. Fixes bug 4865; bugfix on
12499 - The advertised platform of a router now includes only its operating
12500 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
12501 service pack level (for Windows) or its CPU architecture (for Unix).
12502 We also no longer include the "git-XYZ" tag in the version. Resolves
12505 o Major bugfixes (clients):
12506 - If we are unable to find any exit that supports our predicted ports,
12507 stop calling them predicted, so that we don't loop and build
12508 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
12509 which introduced predicted ports.
12510 - Fix an edge case where if we fetch or publish a hidden service
12511 descriptor, we might build a 4-hop circuit and then use that circuit
12512 for exiting afterwards -- even if the new last hop doesn't obey our
12513 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
12514 - Check at each new consensus whether our entry guards were picked
12515 long enough ago that we should rotate them. Previously, we only
12516 did this check at startup, which could lead to us holding a guard
12517 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
12518 - When fetching a bridge descriptor from a bridge authority,
12519 always do so anonymously, whether we have been able to open
12520 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
12521 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
12522 but we'll need to wait for bug 6010 before it's actually usable.
12524 o Major bugfixes (directory authorities):
12525 - When computing weight parameters, behave more robustly in the
12526 presence of a bad bwweightscale value. Previously, the authorities
12527 would crash if they agreed on a sufficiently broken weight_scale
12528 value: now, they use a reasonable default and carry on. Partial
12529 fix for 5786; bugfix on 0.2.2.17-alpha.
12530 - Check more thoroughly to prevent a rogue authority from
12531 double-voting on any consensus directory parameter. Previously,
12532 authorities would crash in this case if the total number of
12533 votes for any parameter exceeded the number of active voters,
12534 but would let it pass otherwise. Partial fix for bug 5786; bugfix
12538 - Rate-limit log messages when asked to connect anonymously to
12539 a private address. When these hit, they tended to hit fast and
12540 often. Also, don't bother trying to connect to addresses that we
12541 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
12542 reply makes us think we have been lied to, even when the address the
12543 client tried to connect to was "localhost." Resolves ticket 2822.
12544 - Allow packagers to insert an extra string in server descriptor
12545 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
12546 Resolves the rest of ticket 2988.
12547 - Raise the threshold of server descriptors needed (75%) and exit
12548 server descriptors needed (50%) before we will declare ourselves
12549 bootstrapped. This will make clients start building circuits a
12550 little later, but makes the initially constructed circuits less
12551 skewed and less in conflict with further directory fetches. Fixes
12553 - Close any connection that sends unrecognized junk before the
12554 handshake. Solves an issue noted in bug 4369.
12555 - Improve log messages about managed transports. Resolves ticket 5070.
12556 - Tag a bridge's descriptor as "never to be sent unencrypted".
12557 This shouldn't matter, since bridges don't open non-anonymous
12558 connections to the bridge authority and don't allow unencrypted
12559 directory connections from clients, but we might as well make
12560 sure. Closes bug 5139.
12561 - Expose our view of whether we have gone dormant to the controller,
12562 via a new "GETINFO dormant" value. Torbutton and other controllers
12563 can use this to avoid doing periodic requests through Tor while
12564 it's dormant (bug 4718). Fixes bug 5954.
12565 - Tell GCC and Clang to check for any errors in format strings passed
12566 to the tor_v*(print|scan)f functions.
12567 - Update to the May 1 2012 Maxmind GeoLite Country database.
12569 o Minor bugfixes (already included in 0.2.2.36):
12570 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
12571 Fixes bug 5346; bugfix on 0.0.8pre3.
12572 - Correct parsing of certain date types in parse_http_time().
12573 Without this patch, If-Modified-Since would behave
12574 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
12575 Esteban Manchado Velázques.
12576 - Make our number-parsing functions always treat too-large values
12577 as an error, even when those values exceed the width of the
12578 underlying type. Previously, if the caller provided these
12579 functions with minima or maxima set to the extreme values of the
12580 underlying integer type, these functions would return those
12581 values on overflow rather than treating overflow as an error.
12582 Fixes part of bug 5786; bugfix on 0.0.9.
12583 - If we hit the error case where routerlist_insert() replaces an
12584 existing (old) server descriptor, make sure to remove that
12585 server descriptor from the old_routers list. Fix related to bug
12586 1776. Bugfix on 0.2.2.18-alpha.
12587 - Clarify the behavior of MaxCircuitDirtiness with hidden service
12588 circuits. Fixes issue 5259.
12590 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
12591 - Prevent a null-pointer dereference when receiving a data cell
12592 for a nonexistent stream when the circuit in question has an
12593 empty deliver window. We don't believe this is triggerable,
12594 since we don't currently allow deliver windows to become empty,
12595 but the logic is tricky enough that it's better to make the code
12596 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
12597 - Fix a memory leak when trying to launch a DNS request when the
12598 network is disabled or the nameservers are unconfigurable. Fixes
12599 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
12600 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
12601 - Don't hold a Windows file handle open for every file mapping;
12602 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
12604 - Avoid O(n^2) performance characteristics when parsing a large
12605 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
12606 - Format more doubles with %f, not %lf. Patch from grarpamp to make
12607 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
12609 - Make our replacement implementation of strtok_r() compatible with
12610 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
12611 bugfix on 0.2.2.1-alpha.
12612 - Fix a NULL-pointer dereference on a badly formed
12613 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
12614 bugfix on 0.2.2.9-alpha.
12615 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
12616 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
12617 - Defensively refactor rend_mid_rendezvous() so that protocol
12618 violations and length checks happen in the beginning. Fixes
12620 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
12621 that IPv6 stuff will compile on MSVC, and compilation issues
12622 will be easier to track down. Fixes bug 5861.
12624 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
12625 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
12626 resource exhaustion, so that clients can adjust their load to
12627 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
12628 started using END_STREAM_REASON_RESOURCELIMIT.
12629 - Don't check for whether the address we're using for outbound
12630 connections has changed until after the outbound connection has
12631 completed. On Windows, getsockname() doesn't succeed until the
12632 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
12633 - If the configuration tries to set MyFamily on a bridge, refuse to
12634 do so, and warn about the security implications. Fixes bug 4657;
12635 bugfix on 0.2.0.3-alpha.
12636 - If the client fails to set a reasonable set of ciphersuites
12637 during its v2 handshake renegotiation, allow the renegotiation to
12638 continue nevertheless (i.e. send all the required certificates).
12639 Fixes bug 4591; bugfix on 0.2.0.20-rc.
12640 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
12641 option is set to 0 (which Vidalia version 0.2.16 now does when
12642 a SAVECONF attempt fails), perform other actions that SIGHUP
12643 usually causes (like reopening the logs). Fixes bug 5095; bugfix
12645 - If we fail to write a microdescriptor to the disk cache, do not
12646 continue replacing the old microdescriptor file. Fixes bug 2954;
12647 bugfix on 0.2.2.6-alpha.
12648 - Exit nodes don't need to fetch certificates for authorities that
12649 they don't recognize; only directory authorities, bridges,
12650 and caches need to do that. Fixes part of bug 2297; bugfix on
12652 - Correctly handle checking the permissions on the parent
12653 directory of a control socket in the root directory. Bug found
12654 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
12656 - When told to add a bridge with the same digest as a preexisting
12657 bridge but a different addr:port, change the addr:port as
12658 requested. Previously we would not notice the change. Fixes half
12659 of bug 5603; fix on 0.2.2.26-beta.
12660 - End AUTHCHALLENGE error messages (in the control protocol) with
12661 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
12663 o Minor bugfixes (on 0.2.3.x):
12664 - Turn an assertion (that the number of handshakes received as a
12665 server is not < 1) into a warning. Fixes bug 4873; bugfix on
12667 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
12668 we had reversed them when the answer was cached.) Fixes bug
12669 5723; bugfix on 0.2.3.1-alpha.
12670 - Work correctly on Linux systems with accept4 support advertised in
12671 their headers, but without accept4 support in the kernel. Fix
12672 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
12673 - When told to add a bridge with the same addr:port as a preexisting
12674 bridge but a different transport, change the transport as
12675 requested. Previously we would not notice the change. Fixes half
12676 of bug 5603; fix on 0.2.3.2-alpha.
12677 - Avoid a "double-reply" warning when replying to a SOCKS request
12678 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
12679 bugfix on 0.2.3.4-alpha.
12680 - Fix a bug where a bridge authority crashes if it has seen no
12681 directory requests when it's time to write statistics to disk.
12682 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
12684 - Don't try to open non-control listeners when DisableNetwork is set.
12685 Previously, we'd open all listeners, then immediately close them.
12686 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
12687 - Don't abort the managed proxy protocol if the managed proxy
12688 sends us an unrecognized line; ignore it instead. Fixes bug
12689 5910; bugfix on 0.2.3.9-alpha.
12690 - Fix a compile warning in crypto.c when compiling with clang 3.1.
12691 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
12692 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
12693 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
12694 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
12695 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
12696 - Resolve numerous small warnings and build issues with MSVC. Resolves
12699 o Documentation fixes:
12700 - Improve the manual's documentation for the NT Service command-line
12701 options. Addresses ticket 3964.
12702 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
12703 - Document the changes to the ORPort and DirPort options, and the
12704 fact that {OR/Dir}ListenAddress is now unnecessary (and
12705 therefore deprecated). Resolves ticket 5597.
12708 - Remove the torrc.bridge file: we don't use it for anything, and
12709 it had become badly desynchronized from torrc.sample. Resolves
12713 Changes in version 0.2.2.36 - 2012-05-24
12714 Tor 0.2.2.36 updates the addresses for two of the eight directory
12715 authorities, fixes some potential anonymity and security issues,
12716 and fixes several crash bugs.
12718 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
12719 known flaws, and nobody should be using them. You should upgrade. If
12720 you're using a Linux or BSD and its packages are obsolete, stop using
12721 those packages and upgrade anyway.
12723 o Directory authority changes:
12724 - Change IP address for maatuska (v3 directory authority).
12725 - Change IP address for ides (v3 directory authority), and rename
12729 - When building or running with any version of OpenSSL earlier
12730 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
12731 versions have a bug (CVE-2011-4576) in which their block cipher
12732 padding includes uninitialized data, potentially leaking sensitive
12733 information to any peer with whom they make a SSLv3 connection. Tor
12734 does not use SSL v3 by default, but a hostile client or server
12735 could force an SSLv3 connection in order to gain information that
12736 they shouldn't have been able to get. The best solution here is to
12737 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
12738 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
12739 to make sure that the bug can't happen.
12740 - Never use a bridge or a controller-supplied node as an exit, even
12741 if its exit policy allows it. Found by wanoskarnet. Fixes bug
12742 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
12743 and 0.2.0.3-alpha (for bridge-purpose descriptors).
12744 - Only build circuits if we have a sufficient threshold of the total
12745 descriptors that are marked in the consensus with the "Exit"
12746 flag. This mitigates an attack proposed by wanoskarnet, in which
12747 all of a client's bridges collude to restrict the exit nodes that
12748 the client knows about. Fixes bug 5343.
12749 - Provide controllers with a safer way to implement the cookie
12750 authentication mechanism. With the old method, if another locally
12751 running program could convince a controller that it was the Tor
12752 process, then that program could trick the controller into telling
12753 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
12754 authentication method uses a challenge-response approach to prevent
12755 this attack. Fixes bug 5185; implements proposal 193.
12758 - Avoid logging uninitialized data when unable to decode a hidden
12759 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
12760 - Avoid a client-side assertion failure when receiving an INTRODUCE2
12761 cell on a general purpose circuit. Fixes bug 5644; bugfix on
12763 - Fix builds when the path to sed, openssl, or sha1sum contains
12764 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
12766 - Correct our replacements for the timeradd() and timersub() functions
12767 on platforms that lack them (for example, Windows). The timersub()
12768 function is used when expiring circuits, while timeradd() is
12769 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
12770 bugfix on 0.2.2.24-alpha.
12771 - Fix the SOCKET_OK test that we use to tell when socket
12772 creation fails so that it works on Win64. Fixes part of bug 4533;
12773 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
12776 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
12777 Fixes bug 5346; bugfix on 0.0.8pre3.
12778 - Make our number-parsing functions always treat too-large values
12779 as an error, even when those values exceed the width of the
12780 underlying type. Previously, if the caller provided these
12781 functions with minima or maxima set to the extreme values of the
12782 underlying integer type, these functions would return those
12783 values on overflow rather than treating overflow as an error.
12784 Fixes part of bug 5786; bugfix on 0.0.9.
12785 - Older Linux kernels erroneously respond to strange nmap behavior
12786 by having accept() return successfully with a zero-length
12787 socket. When this happens, just close the connection. Previously,
12788 we would try harder to learn the remote address: but there was
12789 no such remote address to learn, and our method for trying to
12790 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
12791 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
12792 - Correct parsing of certain date types in parse_http_time().
12793 Without this patch, If-Modified-Since would behave
12794 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
12795 Esteban Manchado Velázques.
12796 - Change the BridgePassword feature (part of the "bridge community"
12797 design, which is not yet implemented) to use a time-independent
12798 comparison. The old behavior might have allowed an adversary
12799 to use timing to guess the BridgePassword value. Fixes bug 5543;
12800 bugfix on 0.2.0.14-alpha.
12801 - Detect and reject certain misformed escape sequences in
12802 configuration values. Previously, these values would cause us
12803 to crash if received in a torrc file or over an authenticated
12804 control port. Bug found by Esteban Manchado Velázquez, and
12805 independently by Robert Connolly from Matta Consulting who further
12806 noted that it allows a post-authentication heap overflow. Patch
12807 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
12808 bugfix on 0.2.0.16-alpha.
12809 - Fix a compile warning when using the --enable-openbsd-malloc
12810 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
12811 - During configure, detect when we're building with clang version
12812 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
12813 CFLAGS. clang doesn't support them yet.
12814 - When sending an HTTP/1.1 proxy request, include a Host header.
12815 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
12816 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
12817 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
12818 - If we hit the error case where routerlist_insert() replaces an
12819 existing (old) server descriptor, make sure to remove that
12820 server descriptor from the old_routers list. Fix related to bug
12821 1776. Bugfix on 0.2.2.18-alpha.
12823 o Minor bugfixes (documentation and log messages):
12824 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
12825 Fixes bug 4856; bugfix on Tor 0.0.6.
12826 - Update "ClientOnly" man page entry to explain that there isn't
12827 really any point to messing with it. Resolves ticket 5005.
12828 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
12829 directory authority option (introduced in Tor 0.2.2.34).
12830 - Downgrade the "We're missing a certificate" message from notice
12831 to info: people kept mistaking it for a real problem, whereas it
12832 is seldom the problem even when we are failing to bootstrap. Fixes
12833 bug 5067; bugfix on 0.2.0.10-alpha.
12834 - Correctly spell "connect" in a log message on failure to create a
12835 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
12836 - Clarify the behavior of MaxCircuitDirtiness with hidden service
12837 circuits. Fixes issue 5259.
12840 - Directory authorities now reject versions of Tor older than
12841 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
12842 inclusive. These versions accounted for only a small fraction of
12843 the Tor network, and have numerous known security issues. Resolves
12845 - Update to the May 1 2012 Maxmind GeoLite Country database.
12848 - When sending or relaying a RELAY_EARLY cell, we used to convert
12849 it to a RELAY cell if the connection was using the v1 link
12850 protocol. This was a workaround for older versions of Tor, which
12851 didn't handle RELAY_EARLY cells properly. Now that all supported
12852 versions can handle RELAY_EARLY cells, and now that we're enforcing
12853 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
12854 remove this workaround. Addresses bug 4786.
12857 Changes in version 0.2.3.15-alpha - 2012-04-30
12858 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
12859 the development branch build on Windows again.
12861 o Minor bugfixes (on 0.2.2.x and earlier):
12862 - Make sure that there are no unhandled pending TLS errors before
12863 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
12864 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
12865 Bugfix on 0.1.0.5-rc; fixes bug 4528.
12866 - Fix an assert that directory authorities could trigger on sighup
12867 during some configuration state transitions. We now don't treat
12868 it as a fatal error when the new descriptor we just generated in
12869 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
12870 - After we pick a directory mirror, we would refuse to use it if
12871 it's in our ExcludeExitNodes list, resulting in mysterious failures
12872 to bootstrap for people who just wanted to avoid exiting from
12873 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
12874 - When building with --enable-static-tor on OpenBSD, do not
12875 erroneously attempt to link -lrt. Fixes bug 5103.
12877 o Minor bugfixes (on 0.2.3.x):
12878 - When Tor is built with kernel headers from a recent (last few
12879 years) Linux kernel, do not fail to run on older (pre-2.6.28
12880 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
12881 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
12882 and 0.2.3.12-alpha.
12883 - Fix compilation with miniupnpc version 1.6; patch from
12884 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
12885 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
12886 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
12887 - Fix compilation on platforms without unistd.h, or where environ
12888 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
12891 - Directory authorities are now a little more lenient at accepting
12892 older router descriptors, or newer router descriptors that don't
12893 make big changes. This should help ameliorate past and future
12894 issues where routers think they have uploaded valid descriptors,
12895 but the authorities don't think so. Fix for ticket 2479.
12896 - Make the code that clients use to detect an address change be
12897 IPv6-aware, so that it won't fill clients' logs with error
12898 messages when trying to get the IPv4 address of an IPv6
12899 connection. Implements ticket 5537.
12901 o Removed features:
12902 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
12903 authorities needed to use it for a while to keep the network working
12904 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
12905 that was six months ago. As of now, it should no longer be needed
12909 Changes in version 0.2.3.14-alpha - 2012-04-23
12910 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
12911 candidate. It also dramatically speeds up AES: fast relays should
12912 consider switching to the newer OpenSSL library.
12914 o Directory authority changes:
12915 - Change IP address for ides (v3 directory authority), and rename
12919 - Avoid logging uninitialized data when unable to decode a hidden
12920 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
12921 - Avoid a client-side assertion failure when receiving an INTRODUCE2
12922 cell on a general purpose circuit. Fixes bug 5644; bugfix on
12924 - If authorities are unable to get a v2 consensus document from other
12925 directory authorities, they no longer fall back to fetching
12926 them from regular directory caches. Fixes bug 5635; bugfix on
12927 0.2.2.26-beta, where routers stopped downloading v2 consensus
12928 documents entirely.
12929 - When we start a Tor client with a normal consensus already cached,
12930 be willing to download a microdescriptor consensus. Fixes bug 4011;
12931 fix on 0.2.3.1-alpha.
12933 o Major features (performance):
12934 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
12935 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
12936 vectorized AES implementations as appropriate. These can be much,
12937 much faster than other AES implementations.
12939 o Minor bugfixes (0.2.2.x and earlier):
12940 - Don't launch more than 10 service-side introduction-point circuits
12941 for a hidden service in five minutes. Previously, we would consider
12942 launching more introduction-point circuits if at least one second
12943 had passed without any introduction-point circuits failing. Fixes
12944 bug 4607; bugfix on 0.0.7pre1.
12945 - Change the BridgePassword feature (part of the "bridge community"
12946 design, which is not yet implemented) to use a time-independent
12947 comparison. The old behavior might have allowed an adversary
12948 to use timing to guess the BridgePassword value. Fixes bug 5543;
12949 bugfix on 0.2.0.14-alpha.
12950 - Enforce correct return behavior of tor_vsscanf() when the '%%'
12951 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
12952 - When sending an HTTP/1.1 proxy request, include a Host header.
12953 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
12954 - Don't log that we have "decided to publish new relay descriptor"
12955 unless we are actually publishing a descriptor. Fixes bug 3942;
12956 bugfix on 0.2.2.28-beta.
12958 o Minor bugfixes (0.2.3.x):
12959 - Fix a bug where a bridge authority crashes (on a failed assert)
12960 if it has seen no directory requests when it's time to write
12961 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
12962 - Fix bug stomping on ORPort option NoListen and ignoring option
12963 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
12964 - In the testsuite, provide a large enough buffer in the tor_sscanf
12965 unit test. Otherwise we'd overrun that buffer and crash during
12966 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
12968 - Make sure we create the keys directory if it doesn't exist and we're
12969 about to store the dynamic Diffie-Hellman parameters. Fixes bug
12970 5572; bugfix on 0.2.3.13-alpha.
12971 - Fix a small memory leak when trying to decode incorrect base16
12972 authenticator during SAFECOOKIE authentication. Found by
12973 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
12976 - Add more information to a log statement that might help track down
12977 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
12978 non-IP address" messages (or any Bug messages, for that matter!),
12979 please let us know about it.
12980 - Relays now understand an IPv6 address when they get one from a
12981 directory server. Resolves ticket 4875.
12982 - Resolve IPv6 addresses in bridge and entry statistics to country
12983 code "??" which means we at least count them. Resolves ticket 5053;
12984 improves on 0.2.3.9-alpha.
12985 - Update to the April 3 2012 Maxmind GeoLite Country database.
12986 - Begin a doc/state-contents.txt file to explain the contents of
12987 the Tor state file. Fixes bug 2987.
12989 o Default torrc changes:
12990 - Stop listing "socksport 9050" in torrc.sample. We open a socks
12991 port on 9050 by default anyway, so this should not change anything
12993 - Stop mentioning the deprecated *ListenAddress options in
12994 torrc.sample. Fixes bug 5438.
12995 - Document unit of bandwidth related options in sample torrc.
12998 o Removed features:
12999 - The "torify" script no longer supports the "tsocks" socksifier
13000 tool, since tsocks doesn't support DNS and UDP right for Tor.
13001 Everyone should be using torsocks instead. Fixes bugs 3530 and
13002 5180. Based on a patch by "ugh".
13004 o Code refactoring:
13005 - Change the symmetric cipher interface so that creating and
13006 initializing a stream cipher are no longer separate functions.
13007 - Remove all internal support for unpadded RSA. We never used it, and
13008 it would be a bad idea to start.
13011 Changes in version 0.2.3.13-alpha - 2012-03-26
13012 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
13013 in managed pluggable transports, as well as providing other cleanups
13014 that get us closer to a release candidate.
13016 o Directory authority changes:
13017 - Change IP address for maatuska (v3 directory authority).
13020 - Provide controllers with a safer way to implement the cookie
13021 authentication mechanism. With the old method, if another locally
13022 running program could convince a controller that it was the Tor
13023 process, then that program could trick the controller into telling
13024 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
13025 authentication method uses a challenge-response approach to prevent
13026 this attack. Fixes bug 5185, implements proposal 193.
13027 - Never use a bridge or a controller-supplied node as an exit, even
13028 if its exit policy allows it. Found by wanoskarnet. Fixes bug
13029 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
13030 and 0.2.0.3-alpha (for bridge-purpose descriptors).
13031 - Only build circuits if we have a sufficient threshold of the total
13032 descriptors that are marked in the consensus with the "Exit"
13033 flag. This mitigates an attack proposed by wanoskarnet, in which
13034 all of a client's bridges collude to restrict the exit nodes that
13035 the client knows about. Fixes bug 5343.
13037 o Major bugfixes (on Tor 0.2.3.x):
13038 - Avoid an assert when managed proxies like obfsproxy are configured,
13039 and we receive HUP signals or setconf attempts too rapidly. This
13040 situation happens most commonly when Vidalia tries to attach to
13041 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
13042 bugfix on 0.2.3.6-alpha.
13043 - Fix a relay-side pluggable transports bug where managed proxies were
13044 unreachable from the Internet, because Tor asked them to bind on
13045 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
13046 - Stop discarding command-line arguments when TestingTorNetwork
13047 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
13048 0.2.3.9-alpha, where task 4552 added support for two layers of
13050 - Resume allowing the unit tests to run in gdb. This was accidentally
13051 made impossible when the DisableDebuggerAttachment option was
13052 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
13053 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
13054 0.2.3.11-alpha. Reported by Anthony G. Basile.
13056 o Minor bugfixes (on 0.2.2.x and earlier):
13057 - Ensure we don't cannibalize circuits that are longer than three hops
13058 already, so we don't end up making circuits with 5 or more
13059 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
13060 0.1.0.1-rc which introduced cannibalization.
13061 - Detect and reject certain misformed escape sequences in
13062 configuration values. Previously, these values would cause us
13063 to crash if received in a torrc file or over an authenticated
13064 control port. Bug found by Esteban Manchado Velázquez, and
13065 independently by Robert Connolly from Matta Consulting who further
13066 noted that it allows a post-authentication heap overflow. Patch
13067 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
13068 bugfix on 0.2.0.16-alpha.
13069 - Fix a compile warning when using the --enable-openbsd-malloc
13070 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
13071 - Directory caches no longer refuse to clean out descriptors because
13072 of missing v2 networkstatus documents, unless they're configured
13073 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
13074 0.2.2.26-beta. Patch by Daniel Bryg.
13075 - Update to the latest version of the tinytest unit testing framework.
13076 This includes a couple of bugfixes that can be relevant for
13077 running forked unit tests on Windows, and removes all reserved
13080 o Minor bugfixes (on 0.2.3.x):
13081 - On a failed pipe() call, don't leak file descriptors. Fixes bug
13082 4296; bugfix on 0.2.3.1-alpha.
13083 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
13084 until after we have received a CERTS cell. Fixes bug 4361; bugfix
13085 on 0.2.3.6-alpha. Patch by "frosty".
13086 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
13087 option, so that the IP stack doesn't decide to use it for IPv4
13088 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
13089 - Ensure that variables set in Tor's environment cannot override
13090 environment variables that Tor passes to a managed
13091 pluggable-transport proxy. Previously, Tor would pass every
13092 variable in its environment to managed proxies along with the new
13093 ones, in such a way that on many operating systems, the inherited
13094 environment variables would override those which Tor tried to
13095 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
13096 bugfix on 0.2.3.9-alpha for Windows.
13099 - A wide variety of new unit tests by Esteban Manchado Velázquez.
13100 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
13101 - Update to the March 6 2012 Maxmind GeoLite Country database.
13104 Changes in version 0.2.3.12-alpha - 2012-02-13
13105 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
13106 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
13107 when Tor is configured to use a pluggable transport like obfsproxy.
13110 - Fix builds when the path to sed, openssl, or sha1sum contains
13111 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
13113 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
13114 connections. This change should allow busy exit relays to stop
13115 running out of available sockets as quickly. Fixes bug 4950;
13116 bugfix on 0.2.2.26-beta.
13117 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
13118 would ask the bridge for microdescriptors, which are only supported
13119 in 0.2.3.x, and then fail to bootstrap when it didn't get the
13120 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
13121 - Properly set up obfsproxy's environment when in managed mode. The
13122 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
13123 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
13124 5076 and 5082; bugfix on 0.2.3.6-alpha.
13127 - Use the dead_strip option when building Tor on OS X. This reduces
13128 binary size by almost 19% when linking openssl and libevent
13129 statically, which we do for Tor Browser Bundle.
13130 - Fix broken URLs in the sample torrc file, and tell readers about
13131 the OutboundBindAddress, ExitPolicyRejectPrivate, and
13132 PublishServerDescriptor options. Addresses bug 4652.
13133 - Update to the February 7 2012 Maxmind GeoLite Country database.
13136 - Downgrade the "We're missing a certificate" message from notice
13137 to info: people kept mistaking it for a real problem, whereas it
13138 is seldom the problem even when we are failing to bootstrap. Fixes
13139 bug 5067; bugfix on 0.2.0.10-alpha.
13140 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
13141 managed pluggable transport server proxy's environment.
13142 Previously, we would put it there, even though Tor doesn't
13143 implement an 'extended server port' yet, and even though Tor
13144 almost certainly isn't listening at that address. For now, we set
13145 it to an empty string to avoid crashing older obfsproxies. Bugfix
13147 - Log the heartbeat message every HeartbeatPeriod seconds, not every
13148 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
13149 0.2.3.1-alpha. Bug reported by Scott Bennett.
13150 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
13151 bugfix on 0.2.3.11-alpha.
13152 - Update "ClientOnly" man page entry to explain that there isn't
13153 really any point to messing with it. Resolves ticket 5005.
13154 - Use the correct CVE number for CVE-2011-4576 in our comments and
13155 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
13158 o Code simplifications and refactoring:
13159 - Use the _WIN32 macro throughout our code to detect Windows.
13160 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
13164 Changes in version 0.2.3.11-alpha - 2012-01-22
13165 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
13166 the last step of the plan to limit maximum circuit length, includes
13167 a wide variety of hidden service performance and correctness fixes,
13168 works around an OpenSSL security flaw if your distro is too stubborn
13169 to upgrade, and fixes a bunch of smaller issues.
13172 - Now that Tor 0.2.0.x is completely deprecated, enable the final
13173 part of "Proposal 110: Avoiding infinite length circuits" by
13174 refusing all circuit-extend requests that do not use a relay_early
13175 cell. This change helps Tor resist a class of denial-of-service
13176 attacks by limiting the maximum circuit length.
13177 - Adjust the number of introduction points that a hidden service
13178 will try to maintain based on how long its introduction points
13179 remain in use and how many introductions they handle. Fixes
13181 - Try to use system facilities for enumerating local interface
13182 addresses, before falling back to our old approach (which was
13183 binding a UDP socket, and calling getsockname() on it). That
13184 approach was scaring OS X users whose draconian firewall
13185 software warned about binding to UDP sockets, regardless of
13186 whether packets were sent. Now we try to use getifaddrs(),
13187 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
13188 system supports. Resolves ticket 1827.
13190 o Major security workaround:
13191 - When building or running with any version of OpenSSL earlier
13192 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
13193 versions have a bug (CVE-2011-4576) in which their block cipher
13194 padding includes uninitialized data, potentially leaking sensitive
13195 information to any peer with whom they make a SSLv3 connection. Tor
13196 does not use SSL v3 by default, but a hostile client or server
13197 could force an SSLv3 connection in order to gain information that
13198 they shouldn't have been able to get. The best solution here is to
13199 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
13200 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
13201 to make sure that the bug can't happen.
13204 - Fix the SOCKET_OK test that we use to tell when socket
13205 creation fails so that it works on Win64. Fixes part of bug 4533;
13206 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
13207 - Correct our replacements for the timeradd() and timersub() functions
13208 on platforms that lack them (for example, Windows). The timersub()
13209 function is used when expiring circuits, while timeradd() is
13210 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
13211 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
13212 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
13213 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
13214 bug at runtime, not compile time, because some distributions hack
13215 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
13216 on 0.2.3.9-alpha. Found by Pascal.
13218 o Minor features (controller):
13219 - Use absolute path names when reporting the torrc filename in the
13220 control protocol, so a controller can more easily find the torrc
13221 file. Resolves bug 1101.
13222 - Extend the control protocol to report flags that control a circuit's
13223 path selection in CIRC events and in replies to 'GETINFO
13224 circuit-status'. Implements part of ticket 2411.
13225 - Extend the control protocol to report the hidden service address
13226 and current state of a hidden-service-related circuit in CIRC
13227 events and in replies to 'GETINFO circuit-status'. Implements part
13229 - When reporting the path to the cookie file to the controller,
13230 give an absolute path. Resolves ticket 4881.
13231 - Allow controllers to request an event notification whenever a
13232 circuit is cannibalized or its purpose is changed. Implements
13233 part of ticket 3457.
13234 - Include the creation time of a circuit in CIRC and CIRC2
13235 control-port events and the list produced by the 'GETINFO
13236 circuit-status' control-port command.
13238 o Minor features (directory authorities):
13239 - Directory authorities now reject versions of Tor older than
13240 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
13241 inclusive. These versions accounted for only a small fraction of
13242 the Tor network, and have numerous known security issues. Resolves
13244 - Authority operators can now vote for all relays in a given
13245 set of countries to be BadDir/BadExit/Invalid/Rejected.
13246 - Provide two consensus parameters (FastFlagMinThreshold and
13247 FastFlagMaxThreshold) to control the range of allowable bandwidths
13248 for the Fast directory flag. These allow authorities to run
13249 experiments on appropriate requirements for being a "Fast" node.
13250 The AuthDirFastGuarantee config value still applies. Implements
13252 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
13253 directory authority option (introduced in Tor 0.2.2.34).
13255 o Minor features (other):
13256 - Don't disable the DirPort when we cannot exceed our AccountingMax
13257 limit during this interval because the effective bandwidthrate is
13258 low enough. This is useful in a situation where AccountMax is only
13259 used as an additional safeguard or to provide statistics.
13260 - Prepend an informative header to generated dynamic_dh_params files.
13261 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
13262 EntryNodes will have no effect. Resolves issue 2571.
13263 - Log more useful messages when we fail to disable debugger
13265 - Log which authority we're missing votes from when we go to fetch
13266 them from the other auths.
13267 - Log (at debug level) whenever a circuit's purpose is changed.
13268 - Add missing documentation for the MaxClientCircuitsPending,
13269 UseMicrodescriptors, UserspaceIOCPBuffers, and
13270 _UseFilteringSSLBufferevents options, all introduced during
13271 the 0.2.3.x series.
13272 - Update to the January 3 2012 Maxmind GeoLite Country database.
13274 o Minor bugfixes (hidden services):
13275 - Don't close hidden service client circuits which have almost
13276 finished connecting to their destination when they reach
13277 the normal circuit-build timeout. Previously, we would close
13278 introduction circuits which are waiting for an acknowledgement
13279 from the introduction point, and rendezvous circuits which have
13280 been specified in an INTRODUCE1 cell sent to a hidden service,
13281 after the normal CBT. Now, we mark them as 'timed out', and launch
13282 another rendezvous attempt in parallel. This behavior change can
13283 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
13284 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
13285 - Don't close hidden-service-side rendezvous circuits when they
13286 reach the normal circuit-build timeout. This behavior change can
13287 be disabled using the new
13288 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
13289 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
13290 - Make sure we never mark the wrong rendezvous circuit as having
13291 had its introduction cell acknowleged by the introduction-point
13292 relay. Previously, when we received an INTRODUCE_ACK cell on a
13293 client-side hidden-service introduction circuit, we might have
13294 marked a rendezvous circuit other than the one we specified in
13295 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
13296 a warning message and interfered with the hidden service
13297 connection-establishment process. Fixes bug 4759; bugfix on
13298 0.2.3.3-alpha, when we added the stream-isolation feature which
13299 might cause Tor to open multiple rendezvous circuits for the same
13301 - Don't trigger an assertion failure when we mark a new client-side
13302 hidden-service introduction circuit for close during the process
13303 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
13306 o Minor bugfixes (log messages):
13307 - Correctly spell "connect" in a log message on failure to create a
13308 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
13310 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
13311 Fixes bug 4856; bugfix on Tor 0.0.6.
13312 - Fix the log message describing how we work around discovering
13313 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
13314 4837; bugfix on 0.2.2.9-alpha.
13315 - When logging about a disallowed .exit name, do not also call it
13316 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
13318 o Minor bugfixes (build fixes):
13319 - During configure, detect when we're building with clang version
13320 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
13321 CFLAGS. clang doesn't support them yet.
13322 - During configure, search for library containing cos function as
13323 libm lives in libcore on some platforms (BeOS/Haiku). Linking
13324 against libm was hard-coded before. Fixes the first part of bug
13325 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
13327 - Detect attempts to build Tor on (as yet hypothetical) versions
13328 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
13329 fix for bug 4533. Bugfix on 0.2.2.28-beta.
13330 - Preprocessor directives should not be put inside the arguments
13331 of a macro. This would break compilation with GCC releases prior
13332 to version 3.3. We would never recommend such an old GCC version,
13333 but it is apparently required for binary compatibility on some
13334 platforms (namely, certain builds of Haiku). Fixes the other part
13335 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
13338 o Minor bugfixes (other):
13339 - Older Linux kernels erroneously respond to strange nmap behavior
13340 by having accept() return successfully with a zero-length
13341 socket. When this happens, just close the connection. Previously,
13342 we would try harder to learn the remote address: but there was
13343 no such remote address to learn, and our method for trying to
13344 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
13345 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
13346 - Fix null-pointer access that could occur if TLS allocation failed.
13347 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
13348 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
13349 accidentally been reverted.
13350 - Fix our implementation of crypto_random_hostname() so it can't
13351 overflow on ridiculously large inputs. (No Tor version has ever
13352 provided this kind of bad inputs, but let's be correct in depth.)
13353 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
13354 - Find more places in the code that should have been testing for
13355 invalid sockets using the SOCKET_OK macro. Required for a fix
13356 for bug 4533. Bugfix on 0.2.2.28-beta.
13357 - Fix an assertion failure when, while running with bufferevents, a
13358 connection finishes connecting after it is marked for close, but
13359 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
13360 - test_util_spawn_background_ok() hardcoded the expected value
13361 for ENOENT to 2. This isn't portable as error numbers are
13362 platform specific, and particularly the hurd has ENOENT at
13363 0x40000002. Construct expected string at runtime, using the correct
13364 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
13365 - Reject attempts to disable DisableDebuggerAttachment while Tor is
13366 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
13367 - Use an appropriate-width type for sockets in tor-fw-helper on
13368 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
13371 - When sending or relaying a RELAY_EARLY cell, we used to convert
13372 it to a RELAY cell if the connection was using the v1 link
13373 protocol. This was a workaround for older versions of Tor, which
13374 didn't handle RELAY_EARLY cells properly. Now that all supported
13375 versions can handle RELAY_EARLY cells, and now that we're enforcing
13376 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
13377 remove this workaround. Addresses bug 4786.
13379 o Code simplifications and refactoring:
13380 - Use OpenSSL's built-in SSL_state_string_long() instead of our
13381 own homebrewed ssl_state_to_string() replacement. Patch from
13382 Emile Snyder. Fixes bug 4653.
13383 - Use macros to indicate OpenSSL versions, so we don't need to worry
13384 about accidental hexadecimal bit shifts.
13385 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
13387 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
13388 - Use the smartlist_add_asprintf() alias more consistently.
13389 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
13390 invalid value, rather than just -1.
13391 - Rename a handful of old identifiers, mostly related to crypto
13392 structures and crypto functions. By convention, our "create an
13393 object" functions are called "type_new()", our "free an object"
13394 functions are called "type_free()", and our types indicate that
13395 they are types only with a final "_t". But a handful of older
13396 types and functions broke these rules, with function names like
13397 "type_create" or "subsystem_op_type", or with type names like
13401 Changes in version 0.2.3.10-alpha - 2011-12-16
13402 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
13403 Tor's buffers code. Absolutely everybody should upgrade.
13405 The bug relied on an incorrect calculation when making data continuous
13406 in one of our IO buffers, if the first chunk of the buffer was
13407 misaligned by just the wrong amount. The miscalculation would allow an
13408 attacker to overflow a piece of heap-allocated memory. To mount this
13409 attack, the attacker would need to either open a SOCKS connection to
13410 Tor's SocksPort (usually restricted to localhost), or target a Tor
13411 instance configured to make its connections through a SOCKS proxy
13412 (which Tor does not do by default).
13414 Good security practice requires that all heap-overflow bugs should be
13415 presumed to be exploitable until proven otherwise, so we are treating
13416 this as a potential code execution attack. Please upgrade immediately!
13417 This bug does not affect bufferevents-based builds of Tor. Special
13418 thanks to "Vektor" for reporting this issue to us!
13420 This release also contains a few minor bugfixes for issues discovered
13424 - Fix a heap overflow bug that could occur when trying to pull
13425 data into the first chunk of a buffer, when that chunk had
13426 already had some data drained from it. Fixes CVE-2011-2778;
13427 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
13430 - If we can't attach streams to a rendezvous circuit when we
13431 finish connecting to a hidden service, clear the rendezvous
13432 circuit's stream-isolation state and try to attach streams
13433 again. Previously, we cleared rendezvous circuits' isolation
13434 state either too early (if they were freshly built) or not at all
13435 (if they had been built earlier and were cannibalized). Bugfix on
13436 0.2.3.3-alpha; fixes bug 4655.
13437 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
13438 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
13439 - Fix an assertion failure when a relay with accounting enabled
13440 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
13443 - Update to the December 6 2011 Maxmind GeoLite Country database.
13446 Changes in version 0.2.2.35 - 2011-12-16
13447 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
13448 buffers code. Absolutely everybody should upgrade.
13450 The bug relied on an incorrect calculation when making data continuous
13451 in one of our IO buffers, if the first chunk of the buffer was
13452 misaligned by just the wrong amount. The miscalculation would allow an
13453 attacker to overflow a piece of heap-allocated memory. To mount this
13454 attack, the attacker would need to either open a SOCKS connection to
13455 Tor's SocksPort (usually restricted to localhost), or target a Tor
13456 instance configured to make its connections through a SOCKS proxy
13457 (which Tor does not do by default).
13459 Good security practice requires that all heap-overflow bugs should be
13460 presumed to be exploitable until proven otherwise, so we are treating
13461 this as a potential code execution attack. Please upgrade immediately!
13462 This bug does not affect bufferevents-based builds of Tor. Special
13463 thanks to "Vektor" for reporting this issue to us!
13465 Tor 0.2.2.35 also fixes several bugs in previous versions, including
13466 crash bugs for unusual configurations, and a long-term bug that
13467 would prevent Tor from starting on Windows machines with draconian
13470 With this release, we remind everyone that 0.2.0.x has reached its
13471 formal end-of-life. Those Tor versions have many known flaws, and
13472 nobody should be using them. You should upgrade -- ideally to the
13473 0.2.2.x series. If you're using a Linux or BSD and its packages are
13474 obsolete, stop using those packages and upgrade anyway.
13476 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
13477 longer receive support after some time in early 2012.
13480 - Fix a heap overflow bug that could occur when trying to pull
13481 data into the first chunk of a buffer, when that chunk had
13482 already had some data drained from it. Fixes CVE-2011-2778;
13483 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
13484 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
13485 that it doesn't attempt to allocate a socketpair. This could cause
13486 some problems on Windows systems with overzealous firewalls. Fix for
13487 bug 4457; workaround for Libevent versions 2.0.1-alpha through
13489 - If we mark an OR connection for close based on a cell we process,
13490 don't process any further cells on it. We already avoid further
13491 reads on marked-for-close connections, but now we also discard the
13492 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
13493 which was the first version where we might mark a connection for
13494 close based on processing a cell on it.
13495 - Correctly sanity-check that we don't underflow on a memory
13496 allocation (and then assert) for hidden service introduction
13497 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
13498 bugfix on 0.2.1.5-alpha.
13499 - Fix a memory leak when we check whether a hidden service
13500 descriptor has any usable introduction points left. Fixes bug
13501 4424. Bugfix on 0.2.2.25-alpha.
13502 - Don't crash when we're running as a relay and don't have a GeoIP
13503 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
13504 we've had in the 0.2.3.x branch already.
13505 - When running as a client, do not print a misleading (and plain
13506 wrong) log message that we're collecting "directory request"
13507 statistics: clients don't collect statistics. Also don't create a
13508 useless (because empty) stats file in the stats/ directory. Fixes
13509 bug 4353; bugfix on 0.2.2.34.
13512 - Detect failure to initialize Libevent. This fix provides better
13513 detection for future instances of bug 4457.
13514 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
13515 function. This was eating up hideously large amounts of time on some
13516 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
13517 - Resolve an integer overflow bug in smartlist_ensure_capacity().
13518 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
13520 - Don't warn about unused log_mutex in log.c when building with
13521 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
13522 0.1.0.6-rc which introduced --disable-threads.
13523 - When configuring, starting, or stopping an NT service, stop
13524 immediately after the service configuration attempt has succeeded
13525 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
13526 - When sending a NETINFO cell, include the original address
13527 received for the other side, not its canonical address. Found
13528 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
13529 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
13530 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
13531 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
13532 occurred when a client tried to fetch a descriptor for a bridge
13533 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
13534 - Backport fixes for a pair of compilation warnings on Windows.
13535 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
13536 - If we had ever tried to call tor_addr_to_str on an address of
13537 unknown type, we would have done a strdup on an uninitialized
13538 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
13539 Reported by "troll_un".
13540 - Correctly detect and handle transient lookup failures from
13541 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
13542 Reported by "troll_un".
13543 - Fix null-pointer access that could occur if TLS allocation failed.
13544 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
13545 - Use tor_socket_t type for listener argument to accept(). Fixes bug
13546 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
13549 - Add two new config options for directory authorities:
13550 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
13551 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
13552 that is always sufficient to satisfy the bandwidth requirement for
13553 the Guard flag. Now it will be easier for researchers to simulate
13554 Tor networks with different values. Resolves ticket 4484.
13555 - When Tor ignores a hidden service specified in its configuration,
13556 include the hidden service's directory in the warning message.
13557 Previously, we would only tell the user that some hidden service
13558 was ignored. Bugfix on 0.0.6; fixes bug 4426.
13559 - Update to the December 6 2011 Maxmind GeoLite Country database.
13561 o Packaging changes:
13562 - Make it easier to automate expert package builds on Windows,
13563 by removing an absolute path from makensis.exe command.
13566 Changes in version 0.2.1.32 - 2011-12-16
13567 Tor 0.2.1.32 backports important security and privacy fixes for
13568 oldstable. This release is intended only for package maintainers and
13569 others who cannot use the 0.2.2 stable series. All others should be
13570 using Tor 0.2.2.x or newer.
13572 The Tor 0.2.1.x series will reach formal end-of-life some time in
13573 early 2012; we will stop releasing patches for it then.
13575 o Major bugfixes (also included in 0.2.2.x):
13576 - Correctly sanity-check that we don't underflow on a memory
13577 allocation (and then assert) for hidden service introduction
13578 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
13579 bugfix on 0.2.1.5-alpha.
13580 - Fix a heap overflow bug that could occur when trying to pull
13581 data into the first chunk of a buffer, when that chunk had
13582 already had some data drained from it. Fixes CVE-2011-2778;
13583 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
13586 - Update to the December 6 2011 Maxmind GeoLite Country database.
13589 Changes in version 0.2.3.9-alpha - 2011-12-08
13590 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
13591 a "DisableNetwork" security feature that bundles can use to avoid
13592 touching the network until bridges are configured, moves forward on
13593 the pluggable transport design, fixes a flaw in the hidden service
13594 design that unnecessarily prevented clients with wrong clocks from
13595 reaching hidden services, and fixes a wide variety of other issues.
13598 - Clients can now connect to private bridges over IPv6. Bridges
13599 still need at least one IPv4 address in order to connect to
13600 other relays. Note that we don't yet handle the case where the
13601 user has two bridge lines for the same bridge (one IPv4, one
13602 IPv6). Implements parts of proposal 186.
13603 - New "DisableNetwork" config option to prevent Tor from launching any
13604 connections or accepting any connections except on a control port.
13605 Bundles and controllers can set this option before letting Tor talk
13606 to the rest of the network, for example to prevent any connections
13607 to a non-bridge address. Packages like Orbot can also use this
13608 option to instruct Tor to save power when the network is off.
13609 - Clients and bridges can now be configured to use a separate
13610 "transport" proxy. This approach makes the censorship arms race
13611 easier by allowing bridges to use protocol obfuscation plugins. It
13612 implements the "managed proxy" part of proposal 180 (ticket 3472).
13613 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
13614 implementation. It makes AES_CTR about 7% faster than our old one
13615 (which was about 10% faster than the one OpenSSL used to provide).
13616 Resolves ticket 4526.
13617 - Add a "tor2web mode" for clients that want to connect to hidden
13618 services non-anonymously (and possibly more quickly). As a safety
13619 measure to try to keep users from turning this on without knowing
13620 what they are doing, tor2web mode must be explicitly enabled at
13621 compile time, and a copy of Tor compiled to run in tor2web mode
13622 cannot be used as a normal Tor client. Implements feature 2553.
13623 - Add experimental support for running on Windows with IOCP and no
13624 kernel-space socket buffers. This feature is controlled by a new
13625 "UserspaceIOCPBuffers" config option (off by default), which has
13626 no effect unless Tor has been built with support for bufferevents,
13627 is running on Windows, and has enabled IOCP. This may, in the long
13628 run, help solve or mitigate bug 98.
13629 - Use a more secure consensus parameter voting algorithm. Now at
13630 least three directory authorities or a majority of them must
13631 vote on a given parameter before it will be included in the
13632 consensus. Implements proposal 178.
13635 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
13636 They used to check that the timestamp was within 30 minutes
13637 of their system clock, so they could cap the size of their
13638 replay-detection cache, but that approach unnecessarily refused
13639 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
13640 the v3 intro-point protocol (the first one which sent a timestamp
13641 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
13642 - Only use the EVP interface when AES acceleration is enabled,
13643 to avoid a 5-7% performance regression. Resolves issue 4525;
13644 bugfix on 0.2.3.8-alpha.
13646 o Privacy/anonymity features (bridge detection):
13647 - Make bridge SSL certificates a bit more stealthy by using random
13648 serial numbers, in the same fashion as OpenSSL when generating
13649 self-signed certificates. Implements ticket 4584.
13650 - Introduce a new config option "DynamicDHGroups", enabled by
13651 default, which provides each bridge with a unique prime DH modulus
13652 to be used during SSL handshakes. This option attempts to help
13653 against censors who might use the Apache DH modulus as a static
13654 identifier for bridges. Addresses ticket 4548.
13656 o Minor features (new/different config options):
13657 - New configuration option "DisableDebuggerAttachment" (on by default)
13658 to prevent basic debugging attachment attempts by other processes.
13659 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
13660 - Allow MapAddress directives to specify matches against super-domains,
13661 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
13662 Implements issue 933.
13663 - Slightly change behavior of "list" options (that is, config
13664 options that can appear more than once) when they appear both in
13665 torrc and on the command line. Previously, the command-line options
13666 would be appended to the ones from torrc. Now, the command-line
13667 options override the torrc options entirely. This new behavior
13668 allows the user to override list options (like exit policies and
13669 ports to listen on) from the command line, rather than simply
13670 appending to the list.
13671 - You can get the old (appending) command-line behavior for "list"
13672 options by prefixing the option name with a "+".
13673 - You can remove all the values for a "list" option from the command
13674 line without adding any new ones by prefixing the option name
13676 - Add experimental support for a "defaults" torrc file to be parsed
13677 before the regular torrc. Torrc options override the defaults file's
13678 options in the same way that the command line overrides the torrc.
13679 The SAVECONF controller command saves only those options which
13680 differ between the current configuration and the defaults file. HUP
13681 reloads both files. (Note: This is an experimental feature; its
13682 behavior will probably be refined in future 0.2.3.x-alpha versions
13683 to better meet packagers' needs.) Implements task 4552.
13686 - Try to make the introductory warning message that Tor prints on
13687 startup more useful for actually finding help and information.
13688 Resolves ticket 2474.
13689 - Running "make version" now displays the version of Tor that
13690 we're about to build. Idea from katmagic; resolves issue 4400.
13691 - Expire old or over-used hidden service introduction points.
13692 Required by fix for bug 3460.
13693 - Move the replay-detection cache for the RSA-encrypted parts of
13694 INTRODUCE2 cells to the introduction point data structures.
13695 Previously, we would use one replay-detection cache per hidden
13696 service. Required by fix for bug 3460.
13697 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
13698 public key replay-detection cache from 60 minutes to 5 minutes. This
13699 replay-detection cache is now used only to detect multiple
13700 INTRODUCE2 cells specifying the same rendezvous point, so we can
13701 avoid launching multiple simultaneous attempts to connect to it.
13703 o Minor bugfixes (on Tor 0.2.2.x and earlier):
13704 - Resolve an integer overflow bug in smartlist_ensure_capacity().
13705 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
13707 - Fix a minor formatting issue in one of tor-gencert's error messages.
13709 - Prevent a false positive from the check-spaces script, by disabling
13710 the "whitespace between function name and (" check for functions
13712 - Fix a log message suggesting that people contact a non-existent
13713 email address. Fixes bug 3448.
13714 - Fix null-pointer access that could occur if TLS allocation failed.
13715 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
13716 - Report a real bootstrap problem to the controller on router
13717 identity mismatch. Previously we just said "foo", which probably
13718 made a lot of sense at the time. Fixes bug 4169; bugfix on
13720 - If we had ever tried to call tor_addr_to_str() on an address of
13721 unknown type, we would have done a strdup() on an uninitialized
13722 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
13723 Reported by "troll_un".
13724 - Correctly detect and handle transient lookup failures from
13725 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
13726 Reported by "troll_un".
13727 - Use tor_socket_t type for listener argument to accept(). Fixes bug
13728 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
13729 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
13730 bug 4532; found by "troll_un".
13732 o Minor bugfixes (on Tor 0.2.3.x):
13733 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
13735 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
13736 circuit for use as a hidden service client's rendezvous point.
13737 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
13738 with help from wanoskarnet.
13739 - Restore behavior of overriding SocksPort, ORPort, and similar
13740 options from the command line. Bugfix on 0.2.3.3-alpha.
13743 - Properly handle the case where the build-tree is not the same
13744 as the source tree when generating src/common/common_sha1.i,
13745 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
13746 bugfix on 0.2.0.1-alpha.
13748 o Code simplifications, cleanups, and refactorings:
13749 - Remove the pure attribute from all functions that used it
13750 previously. In many cases we assigned it incorrectly, because the
13751 functions might assert or call impure functions, and we don't have
13752 evidence that keeping the pure attribute is worthwhile. Implements
13753 changes suggested in ticket 4421.
13754 - Remove some dead code spotted by coverity. Fixes cid 432.
13755 Bugfix on 0.2.3.1-alpha, closes bug 4637.
13758 Changes in version 0.2.3.8-alpha - 2011-11-22
13759 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
13760 socketpair-related bug that has been bothering Windows users. It adds
13761 support to serve microdescriptors to controllers, so Vidalia's network
13762 map can resume listing relays (once Vidalia implements its side),
13763 and adds better support for hardware AES acceleration. Finally, it
13764 starts the process of adjusting the bandwidth cutoff for getting the
13765 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
13766 that tiny relays harm performance more than they help network capacity.
13769 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
13770 that it doesn't attempt to allocate a socketpair. This could cause
13771 some problems on Windows systems with overzealous firewalls. Fix for
13772 bug 4457; workaround for Libevent versions 2.0.1-alpha through
13774 - Correctly sanity-check that we don't underflow on a memory
13775 allocation (and then assert) for hidden service introduction
13776 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
13777 bugfix on 0.2.1.5-alpha.
13778 - Remove the artificially low cutoff of 20KB to guarantee the Fast
13779 flag. In the past few years the average relay speed has picked
13780 up, and while the "top 7/8 of the network get the Fast flag" and
13781 "all relays with 20KB or more of capacity get the Fast flag" rules
13782 used to have the same result, now the top 7/8 of the network has
13783 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
13784 - Fix a rare assertion failure when checking whether a v0 hidden
13785 service descriptor has any usable introduction points left, and
13786 we don't have enough information to build a circuit to the first
13787 intro point named in the descriptor. The HS client code in
13788 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
13789 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
13790 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
13791 - Make bridge authorities not crash when they are asked for their own
13792 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
13793 - When running as a client, do not print a misleading (and plain
13794 wrong) log message that we're collecting "directory request"
13795 statistics: clients don't collect statistics. Also don't create a
13796 useless (because empty) stats file in the stats/ directory. Fixes
13797 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
13800 - Allow Tor controllers like Vidalia to obtain the microdescriptor
13801 for a relay by identity digest or nickname. Previously,
13802 microdescriptors were only available by their own digests, so a
13803 controller would have to ask for and parse the whole microdescriptor
13804 consensus in order to look up a single relay's microdesc. Fixes
13805 bug 3832; bugfix on 0.2.3.1-alpha.
13806 - Use OpenSSL's EVP interface for AES encryption, so that all AES
13807 operations can use hardware acceleration (if present). Resolves
13810 o Minor bugfixes (on 0.2.2.x and earlier):
13811 - Detect failure to initialize Libevent. This fix provides better
13812 detection for future instances of bug 4457.
13813 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
13814 function. This was eating up hideously large amounts of time on some
13815 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
13816 - Don't warn about unused log_mutex in log.c when building with
13817 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
13818 0.1.0.6-rc which introduced --disable-threads.
13819 - Allow manual 'authenticate' commands to the controller interface
13820 from netcat (nc) as well as telnet. We were rejecting them because
13821 they didn't come with the expected whitespace at the end of the
13822 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
13823 - Fix some (not actually triggerable) buffer size checks in usage of
13824 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
13826 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
13827 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
13828 - When configuring, starting, or stopping an NT service, stop
13829 immediately after the service configuration attempt has succeeded
13830 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
13831 - When sending a NETINFO cell, include the original address
13832 received for the other side, not its canonical address. Found
13833 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
13834 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
13835 can pick them up when the tests aren't disabled. Bugfix on
13836 0.2.2.4-alpha which introduced tinytest.
13837 - Fix a memory leak when we check whether a hidden service
13838 descriptor has any usable introduction points left. Fixes bug
13839 4424. Bugfix on 0.2.2.25-alpha.
13840 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
13841 occurred when a client tried to fetch a descriptor for a bridge
13842 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
13844 o Minor bugfixes (on 0.2.3.x):
13845 - Make util unit tests build correctly with MSVC. Bugfix on
13846 0.2.3.3-alpha. Patch by Gisle Vanem.
13847 - Successfully detect AUTH_CHALLENGE cells with no recognized
13848 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
13849 Found by frosty_un.
13850 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
13851 it should still send a NETINFO cell to allow the connection to
13852 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
13854 - Log less loudly when we get an invalid authentication certificate
13855 from a source other than a directory authority: it's not unusual
13856 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
13858 - Tolerate servers with more clock skew in their authentication
13859 certificates than previously. Fixes bug 4371; bugfix on
13861 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
13862 on 0.2.3.4-alpha and 0.2.3.6-alpha.
13865 - Add two new config options for directory authorities:
13866 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
13867 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
13868 that is always sufficient to satisfy the bandwidth requirement for
13869 the Guard flag. Now it will be easier for researchers to simulate
13870 Tor networks with different values. Resolves ticket 4484.
13871 - When Tor ignores a hidden service specified in its configuration,
13872 include the hidden service's directory in the warning message.
13873 Previously, we would only tell the user that some hidden service
13874 was ignored. Bugfix on 0.0.6; fixes bug 4426.
13875 - When we fail to initialize Libevent, retry with IOCP disabled so we
13876 don't need to turn on multi-threading support in Libevent, which in
13877 turn requires a working socketpair(). This is a workaround for bug
13878 4457, which affects Libevent versions from 2.0.1-alpha through
13880 - Detect when we try to build on a platform that doesn't define
13881 AF_UNSPEC to 0. We don't work there, so refuse to compile.
13882 - Update to the November 1 2011 Maxmind GeoLite Country database.
13884 o Packaging changes:
13885 - Make it easier to automate expert package builds on Windows,
13886 by removing an absolute path from makensis.exe command.
13888 o Code simplifications and refactoring:
13889 - Remove some redundant #include directives throughout the code.
13890 Patch from Andrea Gelmini.
13891 - Unconditionally use OpenSSL's AES implementation instead of our
13892 old built-in one. OpenSSL's AES has been better for a while, and
13893 relatively few servers should still be on any version of OpenSSL
13894 that doesn't have good optimized assembly AES.
13895 - Use the name "CERTS" consistently to refer to the new cell type;
13896 we were calling it CERT in some places and CERTS in others.
13899 - Numerous new unit tests for functions in util.c and address.c by
13901 - The long-disabled benchmark tests are now split into their own
13902 ./src/test/bench binary.
13903 - The benchmark tests can now use more accurate timers than
13904 gettimeofday() when such timers are available.
13907 Changes in version 0.2.3.7-alpha - 2011-10-30
13908 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
13909 the new v3 handshake. It also resolves yet another bridge address
13913 - If we mark an OR connection for close based on a cell we process,
13914 don't process any further cells on it. We already avoid further
13915 reads on marked-for-close connections, but now we also discard the
13916 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
13917 which was the first version where we might mark a connection for
13918 close based on processing a cell on it.
13919 - Fix a double-free bug that would occur when we received an invalid
13920 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
13921 bugfix on 0.2.3.6-alpha.
13922 - Bridges no longer include their address in NETINFO cells on outgoing
13923 OR connections, to allow them to blend in better with clients.
13924 Removes another avenue for enumerating bridges. Reported by
13925 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
13926 cells were introduced.
13929 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
13930 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
13933 Changes in version 0.2.3.6-alpha - 2011-10-26
13934 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
13935 anonymity vulnerability where an attacker can deanonymize Tor
13936 users. Everybody should upgrade.
13938 This release also features support for a new v3 connection handshake
13939 protocol, and fixes to make hidden service connections more robust.
13942 - Implement a new handshake protocol (v3) for authenticating Tors to
13943 each other over TLS. It should be more resistant to fingerprinting
13944 than previous protocols, and should require less TLS hacking for
13945 future Tor implementations. Implements proposal 176.
13946 - Allow variable-length padding cells to disguise the length of
13947 Tor's TLS records. Implements part of proposal 184.
13949 o Privacy/anonymity fixes (clients):
13950 - Clients and bridges no longer send TLS certificate chains on
13951 outgoing OR connections. Previously, each client or bridge would
13952 use the same cert chain for all outgoing OR connections until
13953 its IP address changes, which allowed any relay that the client
13954 or bridge contacted to determine which entry guards it is using.
13955 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
13956 - If a relay receives a CREATE_FAST cell on a TLS connection, it
13957 no longer considers that connection as suitable for satisfying a
13958 circuit EXTEND request. Now relays can protect clients from the
13959 CVE-2011-2768 issue even if the clients haven't upgraded yet.
13960 - Directory authorities no longer assign the Guard flag to relays
13961 that haven't upgraded to the above "refuse EXTEND requests
13962 to client connections" fix. Now directory authorities can
13963 protect clients from the CVE-2011-2768 issue even if neither
13964 the clients nor the relays have upgraded yet. There's a new
13965 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
13966 to let us transition smoothly, else tomorrow there would be no
13969 o Major bugfixes (hidden services):
13970 - Improve hidden service robustness: when an attempt to connect to
13971 a hidden service ends, be willing to refetch its hidden service
13972 descriptors from each of the HSDir relays responsible for them
13973 immediately. Previously, we would not consider refetching the
13974 service's descriptors from each HSDir for 15 minutes after the last
13975 fetch, which was inconvenient if the hidden service was not running
13976 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
13977 - When one of a hidden service's introduction points appears to be
13978 unreachable, stop trying it. Previously, we would keep trying
13979 to build circuits to the introduction point until we lost the
13980 descriptor, usually because the user gave up and restarted Tor.
13981 Partly fixes bug 3825.
13982 - Don't launch a useless circuit after failing to use one of a
13983 hidden service's introduction points. Previously, we would
13984 launch a new introduction circuit, but not set the hidden service
13985 which that circuit was intended to connect to, so it would never
13986 actually be used. A different piece of code would then create a
13987 new introduction circuit correctly. Bug reported by katmagic and
13988 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
13990 o Major bugfixes (other):
13991 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
13992 that they initiated. Relays could distinguish incoming bridge
13993 connections from client connections, creating another avenue for
13994 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
13995 Found by "frosty_un".
13996 - Don't update the AccountingSoftLimitHitAt state file entry whenever
13997 tor gets started. This prevents a wrong average bandwidth
13998 estimate, which would cause relays to always start a new accounting
13999 interval at the earliest possible moment. Fixes bug 2003; bugfix
14000 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
14001 immensely in tracking this bug down.
14002 - Fix a crash bug when changing node restrictions while a DNS lookup
14003 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
14006 o Minor bugfixes (on 0.2.2.x and earlier):
14007 - When a hidden service turns an extra service-side introduction
14008 circuit into a general-purpose circuit, free the rend_data and
14009 intro_key fields first, so we won't leak memory if the circuit
14010 is cannibalized for use as another service-side introduction
14011 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
14012 - Rephrase the log message emitted if the TestSocks check is
14013 successful. Patch from Fabian Keil; fixes bug 4094.
14014 - Bridges now skip DNS self-tests, to act a little more stealthily.
14015 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
14016 bridges. Patch by "warms0x".
14017 - Remove a confusing dollar sign from the example fingerprint in the
14018 man page, and also make the example fingerprint a valid one. Fixes
14019 bug 4309; bugfix on 0.2.1.3-alpha.
14020 - Fix internal bug-checking logic that was supposed to catch
14021 failures in digest generation so that it will fail more robustly
14022 if we ask for a nonexistent algorithm. Found by Coverity Scan.
14023 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
14024 - Report any failure in init_keys() calls launched because our
14025 IP address has changed. Spotted by Coverity Scan. Bugfix on
14026 0.1.1.4-alpha; fixes CID 484.
14028 o Minor bugfixes (on 0.2.3.x):
14029 - Fix a bug in configure.in that kept it from building a configure
14030 script with autoconf versions earlier than 2.61. Fixes bug 2430;
14031 bugfix on 0.2.3.1-alpha.
14032 - Don't warn users that they are exposing a client port to the
14033 Internet if they have specified an RFC1918 address. Previously,
14034 we would warn if the user had specified any non-loopback
14035 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
14036 - Fix memory leaks in the failing cases of the new SocksPort and
14037 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
14038 fixes coverity CIDs 485, 486, and 487.
14041 - When a hidden service's introduction point times out, consider
14042 trying it again during the next attempt to connect to the
14043 HS. Previously, we would not try it again unless a newly fetched
14044 descriptor contained it. Required by fixes for bugs 1297 and 3825.
14045 - The next version of Windows will be called Windows 8, and it has
14046 a major version of 6, minor version of 2. Correctly identify that
14047 version instead of calling it "Very recent version". Resolves
14048 ticket 4153; reported by funkstar.
14049 - The Bridge Authority now writes statistics on how many bridge
14050 descriptors it gave out in total, and how many unique descriptors
14051 it gave out. It also lists how often the most and least commonly
14052 fetched descriptors were given out, as well as the median and
14053 25th/75th percentile. Implements tickets 4200 and 4294.
14054 - Update to the October 4 2011 Maxmind GeoLite Country database.
14056 o Code simplifications and refactoring:
14057 - Remove some old code to remember statistics about which descriptors
14058 we've served as a directory mirror. The feature wasn't used and
14059 is outdated now that microdescriptors are around.
14060 - Rename Tor functions that turn strings into addresses, so that
14061 "parse" indicates that no hostname resolution occurs, and
14062 "lookup" indicates that hostname resolution may occur. This
14063 should help prevent mistakes in the future. Fixes bug 3512.
14066 Changes in version 0.2.2.34 - 2011-10-26
14067 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
14068 can deanonymize Tor users. Everybody should upgrade.
14070 The attack relies on four components: 1) Clients reuse their TLS cert
14071 when talking to different relays, so relays can recognize a user by
14072 the identity key in her cert. 2) An attacker who knows the client's
14073 identity key can probe each guard relay to see if that identity key
14074 is connected to that guard relay right now. 3) A variety of active
14075 attacks in the literature (starting from "Low-Cost Traffic Analysis
14076 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
14077 discover the guard relays that a Tor user visiting the website is using.
14078 4) Clients typically pick three guards at random, so the set of guards
14079 for a given user could well be a unique fingerprint for her. This
14080 release fixes components #1 and #2, which is enough to block the attack;
14081 the other two remain as open research problems. Special thanks to
14082 "frosty_un" for reporting the issue to us!
14084 Clients should upgrade so they are no longer recognizable by the TLS
14085 certs they present. Relays should upgrade so they no longer allow a
14086 remote attacker to probe them to test whether unpatched clients are
14087 currently connected to them.
14089 This release also fixes several vulnerabilities that allow an attacker
14090 to enumerate bridge relays. Some bridge enumeration attacks still
14091 remain; see for example proposal 188.
14093 o Privacy/anonymity fixes (clients):
14094 - Clients and bridges no longer send TLS certificate chains on
14095 outgoing OR connections. Previously, each client or bridge would
14096 use the same cert chain for all outgoing OR connections until
14097 its IP address changes, which allowed any relay that the client
14098 or bridge contacted to determine which entry guards it is using.
14099 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14100 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14101 no longer considers that connection as suitable for satisfying a
14102 circuit EXTEND request. Now relays can protect clients from the
14103 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14104 - Directory authorities no longer assign the Guard flag to relays
14105 that haven't upgraded to the above "refuse EXTEND requests
14106 to client connections" fix. Now directory authorities can
14107 protect clients from the CVE-2011-2768 issue even if neither
14108 the clients nor the relays have upgraded yet. There's a new
14109 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
14110 to let us transition smoothly, else tomorrow there would be no
14113 o Privacy/anonymity fixes (bridge enumeration):
14114 - Bridge relays now do their directory fetches inside Tor TLS
14115 connections, like all the other clients do, rather than connecting
14116 directly to the DirPort like public relays do. Removes another
14117 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
14118 - Bridges relays now build circuits for themselves in a more similar
14119 way to how clients build them. Removes another avenue for
14120 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
14121 when bridges were introduced.
14122 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14123 that they initiated. Relays could distinguish incoming bridge
14124 connections from client connections, creating another avenue for
14125 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14126 Found by "frosty_un".
14129 - Fix a crash bug when changing node restrictions while a DNS lookup
14130 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
14132 - Don't launch a useless circuit after failing to use one of a
14133 hidden service's introduction points. Previously, we would
14134 launch a new introduction circuit, but not set the hidden service
14135 which that circuit was intended to connect to, so it would never
14136 actually be used. A different piece of code would then create a
14137 new introduction circuit correctly. Bug reported by katmagic and
14138 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
14141 - Change an integer overflow check in the OpenBSD_Malloc code so
14142 that GCC is less likely to eliminate it as impossible. Patch
14143 from Mansour Moufid. Fixes bug 4059.
14144 - When a hidden service turns an extra service-side introduction
14145 circuit into a general-purpose circuit, free the rend_data and
14146 intro_key fields first, so we won't leak memory if the circuit
14147 is cannibalized for use as another service-side introduction
14148 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
14149 - Bridges now skip DNS self-tests, to act a little more stealthily.
14150 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
14151 bridges. Patch by "warms0x".
14152 - Fix internal bug-checking logic that was supposed to catch
14153 failures in digest generation so that it will fail more robustly
14154 if we ask for a nonexistent algorithm. Found by Coverity Scan.
14155 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
14156 - Report any failure in init_keys() calls launched because our
14157 IP address has changed. Spotted by Coverity Scan. Bugfix on
14158 0.1.1.4-alpha; fixes CID 484.
14160 o Minor bugfixes (log messages and documentation):
14161 - Remove a confusing dollar sign from the example fingerprint in the
14162 man page, and also make the example fingerprint a valid one. Fixes
14163 bug 4309; bugfix on 0.2.1.3-alpha.
14164 - The next version of Windows will be called Windows 8, and it has
14165 a major version of 6, minor version of 2. Correctly identify that
14166 version instead of calling it "Very recent version". Resolves
14167 ticket 4153; reported by funkstar.
14168 - Downgrade log messages about circuit timeout calibration from
14169 "notice" to "info": they don't require or suggest any human
14170 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
14171 bugfix on 0.2.2.14-alpha.
14174 - Turn on directory request statistics by default and include them in
14175 extra-info descriptors. Don't break if we have no GeoIP database.
14176 Backported from 0.2.3.1-alpha; implements ticket 3951.
14177 - Update to the October 4 2011 Maxmind GeoLite Country database.
14180 Changes in version 0.2.1.31 - 2011-10-26
14181 Tor 0.2.1.31 backports important security and privacy fixes for
14182 oldstable. This release is intended only for package maintainers and
14183 others who cannot use the 0.2.2 stable series. All others should be
14184 using Tor 0.2.2.x or newer.
14186 o Security fixes (also included in 0.2.2.x):
14187 - Replace all potentially sensitive memory comparison operations
14188 with versions whose runtime does not depend on the data being
14189 compared. This will help resist a class of attacks where an
14190 adversary can use variations in timing information to learn
14191 sensitive data. Fix for one case of bug 3122. (Safe memcmp
14192 implementation by Robert Ransom based partially on code by DJB.)
14193 - Fix an assert in parsing router descriptors containing IPv6
14194 addresses. This one took down the directory authorities when
14195 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
14197 o Privacy/anonymity fixes (also included in 0.2.2.x):
14198 - Clients and bridges no longer send TLS certificate chains on
14199 outgoing OR connections. Previously, each client or bridge would
14200 use the same cert chain for all outgoing OR connections until
14201 its IP address changes, which allowed any relay that the client
14202 or bridge contacted to determine which entry guards it is using.
14203 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
14204 - If a relay receives a CREATE_FAST cell on a TLS connection, it
14205 no longer considers that connection as suitable for satisfying a
14206 circuit EXTEND request. Now relays can protect clients from the
14207 CVE-2011-2768 issue even if the clients haven't upgraded yet.
14208 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
14209 that they initiated. Relays could distinguish incoming bridge
14210 connections from client connections, creating another avenue for
14211 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
14212 Found by "frosty_un".
14213 - When receiving a hidden service descriptor, check that it is for
14214 the hidden service we wanted. Previously, Tor would store any
14215 hidden service descriptors that a directory gave it, whether it
14216 wanted them or not. This wouldn't have let an attacker impersonate
14217 a hidden service, but it did let directories pre-seed a client
14218 with descriptors that it didn't want. Bugfix on 0.0.6.
14219 - Avoid linkability based on cached hidden service descriptors: forget
14220 all hidden service descriptors cached as a client when processing a
14221 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
14222 - Make the bridge directory authority refuse to answer directory
14223 requests for "all" descriptors. It used to include bridge
14224 descriptors in its answer, which was a major information leak.
14225 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
14226 - Don't attach new streams to old rendezvous circuits after SIGNAL
14227 NEWNYM. Previously, we would keep using an existing rendezvous
14228 circuit if it remained open (i.e. if it were kept open by a
14229 long-lived stream, or if a new stream were attached to it before
14230 Tor could notice that it was old and no longer in use). Bugfix on
14231 0.1.1.15-rc; fixes bug 3375.
14233 o Minor bugfixes (also included in 0.2.2.x):
14234 - When we restart our relay, we might get a successful connection
14235 from the outside before we've started our reachability tests,
14236 triggering a warning: "ORPort found reachable, but I have no
14237 routerinfo yet. Failing to inform controller of success." This
14238 bug was harmless unless Tor is running under a controller
14239 like Vidalia, in which case the controller would never get a
14240 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
14242 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
14243 enabled. Fixes bug 1526.
14244 - Remove undocumented option "-F" from tor-resolve: it hasn't done
14245 anything since 0.2.1.16-rc.
14246 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
14247 None of the cases where we did this before were wrong, but by making
14248 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
14249 - Fix a rare crash bug that could occur when a client was configured
14250 with a large number of bridges. Fixes bug 2629; bugfix on
14251 0.2.1.2-alpha. Bugfix by trac user "shitlei".
14252 - Correct the warning displayed when a rendezvous descriptor exceeds
14253 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
14255 - Fix an uncommon assertion failure when running with DNSPort under
14256 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
14257 - When warning about missing zlib development packages during compile,
14258 give the correct package names. Bugfix on 0.2.0.1-alpha.
14259 - Require that introduction point keys and onion keys have public
14260 exponent 65537. Bugfix on 0.2.0.10-alpha.
14261 - Do not crash when our configuration file becomes unreadable, for
14262 example due to a permissions change, between when we start up
14263 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
14265 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
14267 - Always NUL-terminate the sun_path field of a sockaddr_un before
14268 passing it to the kernel. (Not a security issue: kernels are
14269 smart enough to reject bad sockaddr_uns.) Found by Coverity;
14270 CID #428. Bugfix on Tor 0.2.0.3-alpha.
14271 - Don't stack-allocate the list of supplementary GIDs when we're
14272 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
14273 could take up to 256K, which is way too much stack. Found by
14274 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
14276 o Minor bugfixes (only in 0.2.1.x):
14277 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
14278 rely on them. Bugfix on 0.2.1.30.
14279 - Use git revisions instead of svn revisions when generating our
14280 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
14282 o Minor features (also included in 0.2.2.x):
14283 - Adjust the expiration time on our SSL session certificates to
14284 better match SSL certs seen in the wild. Resolves ticket 4014.
14285 - Allow nameservers with IPv6 address. Resolves bug 2574.
14286 - Update to the October 4 2011 Maxmind GeoLite Country database.
14289 Changes in version 0.2.3.5-alpha - 2011-09-28
14290 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
14291 bridge relays; fixes an assertion error that many users started hitting
14292 today; and adds the ability to refill token buckets more often than
14293 once per second, allowing significant performance improvements.
14296 - Bridge relays now do their directory fetches inside Tor TLS
14297 connections, like all the other clients do, rather than connecting
14298 directly to the DirPort like public relays do. Removes another
14299 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
14300 - Bridges relays now build circuits for themselves in a more similar
14301 way to how clients build them. Removes another avenue for
14302 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
14303 when bridges were introduced.
14306 - Fix an "Assertion md->held_by_node == 1 failed" error that could
14307 occur when the same microdescriptor was referenced by two node_t
14308 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
14310 o Major features (networking):
14311 - Add a new TokenBucketRefillInterval option to refill token buckets
14312 more frequently than once per second. This should improve network
14313 performance, alleviate queueing problems, and make traffic less
14314 bursty. Implements proposal 183; closes ticket 3630. Design by
14315 Florian Tschorsch and Björn Scheuermann; implementation by
14319 - Change an integer overflow check in the OpenBSD_Malloc code so
14320 that GCC is less likely to eliminate it as impossible. Patch
14321 from Mansour Moufid. Fixes bug 4059.
14323 o Minor bugfixes (usability):
14324 - Downgrade log messages about circuit timeout calibration from
14325 "notice" to "info": they don't require or suggest any human
14326 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
14327 bugfix on 0.2.2.14-alpha.
14329 o Minor features (diagnostics):
14330 - When the system call to create a listener socket fails, log the
14331 error message explaining why. This may help diagnose bug 4027.
14334 Changes in version 0.2.3.4-alpha - 2011-09-13
14335 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
14336 tweak to Tor's TLS handshake that makes relays and bridges that run
14337 this new version reachable from Iran again. It also fixes a few new
14338 bugs in 0.2.3.x, and teaches relays to recognize when they're not
14339 listed in the network consensus and republish.
14341 o Major bugfixes (also part of 0.2.2.33):
14342 - Avoid an assertion failure when reloading a configuration with
14343 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
14344 3923; bugfix on 0.2.2.25-alpha.
14346 o Minor features (security, also part of 0.2.2.33):
14347 - Check for replays of the public-key encrypted portion of an
14348 INTRODUCE1 cell, in addition to the current check for replays of
14349 the g^x value. This prevents a possible class of active attacks
14350 by an attacker who controls both an introduction point and a
14351 rendezvous point, and who uses the malleability of AES-CTR to
14352 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
14353 that these attacks are infeasible (requiring the attacker to send
14354 on the order of zettabytes of altered cells in a short interval),
14355 but we'd rather block them off in case there are any classes of
14356 this attack that we missed. Reported by Willem Pinckaers.
14358 o Minor features (also part of 0.2.2.33):
14359 - Adjust the expiration time on our SSL session certificates to
14360 better match SSL certs seen in the wild. Resolves ticket 4014.
14361 - Change the default required uptime for a relay to be accepted as
14362 a HSDir (hidden service directory) from 24 hours to 25 hours.
14363 Improves on 0.2.0.10-alpha; resolves ticket 2649.
14364 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
14365 authorities to abstain from voting on assignment of the HSDir
14366 consensus flag. Related to bug 2649.
14367 - Update to the September 6 2011 Maxmind GeoLite Country database.
14369 o Minor bugfixes (also part of 0.2.2.33):
14370 - Demote the 'replay detected' log message emitted when a hidden
14371 service receives the same Diffie-Hellman public key in two different
14372 INTRODUCE2 cells to info level. A normal Tor client can cause that
14373 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
14374 fixes part of bug 2442.
14375 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
14376 level. There is nothing that a hidden service's operator can do
14377 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
14379 - Clarify a log message specifying the characters permitted in
14380 HiddenServiceAuthorizeClient client names. Previously, the log
14381 message said that "[A-Za-z0-9+-_]" were permitted; that could have
14382 given the impression that every ASCII character between "+" and "_"
14383 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
14385 o Build fixes (also part of 0.2.2.33):
14386 - Clean up some code issues that prevented Tor from building on older
14387 BSDs. Fixes bug 3894; reported by "grarpamp".
14388 - Search for a platform-specific version of "ar" when cross-compiling.
14389 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
14392 - Fix a bug where the SocksPort option (for example) would get
14393 ignored and replaced by the default if a SocksListenAddress
14394 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
14398 - Relays now try regenerating and uploading their descriptor more
14399 frequently if they are not listed in the consensus, or if the
14400 version of their descriptor listed in the consensus is too
14401 old. This fix should prevent situations where a server declines
14402 to re-publish itself because it has done so too recently, even
14403 though the authorities decided not to list its recent-enough
14404 descriptor. Fix for bug 3327.
14407 - Relays now include a reason for regenerating their descriptors
14408 in an HTTP header when uploading to the authorities. This will
14409 make it easier to debug descriptor-upload issues in the future.
14410 - When starting as root and then changing our UID via the User
14411 control option, and we have a ControlSocket configured, make sure
14412 that the ControlSocket is owned by the same account that Tor will
14413 run under. Implements ticket 3421; fix by Jérémy Bobbio.
14416 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
14417 utility function used in the control-port code). This shouldn't
14418 ever happen unless Tor is completely out of memory, but if it did
14419 happen and Tor somehow recovered from it, Tor could have sent a log
14420 message to a control port in the middle of a reply to a controller
14421 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
14422 - Make 'FetchUselessDescriptors' cause all descriptor types and
14423 all consensus types (including microdescriptors) to get fetched.
14424 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
14426 o Code refactoring:
14427 - Make a new "entry connection" struct as an internal subtype of "edge
14428 connection", to simplify the code and make exit connections smaller.
14431 Changes in version 0.2.2.33 - 2011-09-13
14432 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
14433 TLS handshake that makes relays and bridges that run this new version
14434 reachable from Iran again.
14437 - Avoid an assertion failure when reloading a configuration with
14438 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
14439 3923; bugfix on 0.2.2.25-alpha.
14441 o Minor features (security):
14442 - Check for replays of the public-key encrypted portion of an
14443 INTRODUCE1 cell, in addition to the current check for replays of
14444 the g^x value. This prevents a possible class of active attacks
14445 by an attacker who controls both an introduction point and a
14446 rendezvous point, and who uses the malleability of AES-CTR to
14447 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
14448 that these attacks are infeasible (requiring the attacker to send
14449 on the order of zettabytes of altered cells in a short interval),
14450 but we'd rather block them off in case there are any classes of
14451 this attack that we missed. Reported by Willem Pinckaers.
14454 - Adjust the expiration time on our SSL session certificates to
14455 better match SSL certs seen in the wild. Resolves ticket 4014.
14456 - Change the default required uptime for a relay to be accepted as
14457 a HSDir (hidden service directory) from 24 hours to 25 hours.
14458 Improves on 0.2.0.10-alpha; resolves ticket 2649.
14459 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
14460 authorities to abstain from voting on assignment of the HSDir
14461 consensus flag. Related to bug 2649.
14462 - Update to the September 6 2011 Maxmind GeoLite Country database.
14464 o Minor bugfixes (documentation and log messages):
14465 - Correct the man page to explain that HashedControlPassword and
14466 CookieAuthentication can both be set, in which case either method
14467 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
14468 when we decided to allow these config options to both be set. Issue
14469 raised by bug 3898.
14470 - Demote the 'replay detected' log message emitted when a hidden
14471 service receives the same Diffie-Hellman public key in two different
14472 INTRODUCE2 cells to info level. A normal Tor client can cause that
14473 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
14474 fixes part of bug 2442.
14475 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
14476 level. There is nothing that a hidden service's operator can do
14477 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
14479 - Clarify a log message specifying the characters permitted in
14480 HiddenServiceAuthorizeClient client names. Previously, the log
14481 message said that "[A-Za-z0-9+-_]" were permitted; that could have
14482 given the impression that every ASCII character between "+" and "_"
14483 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
14486 - Provide a substitute implementation of lround() for MSVC, which
14487 apparently lacks it. Patch from Gisle Vanem.
14488 - Clean up some code issues that prevented Tor from building on older
14489 BSDs. Fixes bug 3894; reported by "grarpamp".
14490 - Search for a platform-specific version of "ar" when cross-compiling.
14491 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
14494 Changes in version 0.2.3.3-alpha - 2011-09-01
14495 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
14496 security, and provides client-side support for the microdescriptor
14497 and optimistic data features introduced earlier in the 0.2.3.x
14498 series. It also includes numerous critical bugfixes in the (optional)
14499 bufferevent-based networking backend.
14501 o Major features (stream isolation):
14502 - You can now configure Tor so that streams from different
14503 applications are isolated on different circuits, to prevent an
14504 attacker who sees your streams as they leave an exit node from
14505 linking your sessions to one another. To do this, choose some way
14506 to distinguish the applications: have them connect to different
14507 SocksPorts, or have one of them use SOCKS4 while the other uses
14508 SOCKS5, or have them pass different authentication strings to the
14509 SOCKS proxy. Then, use the new SocksPort syntax to configure the
14510 degree of isolation you need. This implements Proposal 171.
14511 - There's a new syntax for specifying multiple client ports (such as
14512 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
14513 multiple *Port entries with full addr:port syntax on each.
14514 The old *ListenAddress format is still supported, but you can't
14515 mix it with the new *Port syntax.
14517 o Major features (other):
14518 - Enable microdescriptor fetching by default for clients. This allows
14519 clients to download a much smaller amount of directory information.
14520 To disable it (and go back to the old-style consensus and
14521 descriptors), set "UseMicrodescriptors 0" in your torrc file.
14522 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
14523 "PortForwarding" config option), now supports Windows.
14524 - When using an exit relay running 0.2.3.x, clients can now
14525 "optimistically" send data before the exit relay reports that
14526 the stream has opened. This saves a round trip when starting
14527 connections where the client speaks first (such as web browsing).
14528 This behavior is controlled by a consensus parameter (currently
14529 disabled). To turn it on or off manually, use the "OptimisticData"
14530 torrc option. Implements proposal 181; code by Ian Goldberg.
14532 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
14533 - When using IOCP on Windows, we need to enable Libevent windows
14535 - The IOCP backend now works even when the user has not specified
14536 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
14537 Fixes part of bug 3752.
14538 - Correctly record the bytes we've read and written when using
14539 bufferevents, so that we can include them in our bandwidth history
14540 and advertised bandwidth. Fixes bug 3803.
14541 - Apply rate-limiting only at the bottom of a chain of filtering
14542 bufferevents. This prevents us from filling up internal read
14543 buffers and violating rate-limits when filtering bufferevents
14544 are enabled. Fixes part of bug 3804.
14545 - Add high-watermarks to the output buffers for filtered
14546 bufferevents. This prevents us from filling up internal write
14547 buffers and wasting CPU cycles when filtering bufferevents are
14548 enabled. Fixes part of bug 3804.
14549 - Correctly notice when data has been written from a bufferevent
14550 without flushing it completely. Fixes bug 3805.
14551 - Fix a bug where server-side tunneled bufferevent-based directory
14552 streams would get closed prematurely. Fixes bug 3814.
14553 - Fix a use-after-free error with per-connection rate-limiting
14554 buckets. Fixes bug 3888.
14556 o Major bugfixes (also part of 0.2.2.31-rc):
14557 - If we're configured to write our ControlPorts to disk, only write
14558 them after switching UID and creating the data directory. This way,
14559 we don't fail when starting up with a nonexistent DataDirectory
14560 and a ControlPortWriteToFile setting based on that directory. Fixes
14561 bug 3747; bugfix on Tor 0.2.2.26-beta.
14564 - Added a new CONF_CHANGED event so that controllers can be notified
14565 of any configuration changes made by other controllers, or by the
14566 user. Implements ticket 1692.
14567 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
14568 leak when using bufferevents, and lets Libevent worry about how to
14569 best copy data out of a buffer.
14570 - Replace files in stats/ rather than appending to them. Now that we
14571 include statistics in extra-info descriptors, it makes no sense to
14572 keep old statistics forever. Implements ticket 2930.
14574 o Minor features (build compatibility):
14575 - Limited, experimental support for building with nmake and MSVC.
14576 - Provide a substitute implementation of lround() for MSVC, which
14577 apparently lacks it. Patch from Gisle Vanem.
14579 o Minor features (also part of 0.2.2.31-rc):
14580 - Update to the August 2 2011 Maxmind GeoLite Country database.
14582 o Minor bugfixes (on 0.2.3.x-alpha):
14583 - Fix a spurious warning when parsing SOCKS requests with
14584 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
14585 - Get rid of a harmless warning that could happen on relays running
14586 with bufferevents. The warning was caused by someone doing an http
14587 request to a relay's orport. Also don't warn for a few related
14588 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
14590 o Minor bugfixes (on 2.2.x and earlier):
14591 - Correct the man page to explain that HashedControlPassword and
14592 CookieAuthentication can both be set, in which case either method
14593 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
14594 when we decided to allow these config options to both be set. Issue
14595 raised by bug 3898.
14596 - The "--quiet" and "--hush" options now apply not only to Tor's
14597 behavior before logs are configured, but also to Tor's behavior in
14598 the absense of configured logs. Fixes bug 3550; bugfix on
14601 o Minor bugfixes (also part of 0.2.2.31-rc):
14602 - Write several files in text mode, on OSes that distinguish text
14603 mode from binary mode (namely, Windows). These files are:
14604 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
14605 that collect those statistics; 'client_keys' and 'hostname' for
14606 hidden services that use authentication; and (in the tor-gencert
14607 utility) newly generated identity and signing keys. Previously,
14608 we wouldn't specify text mode or binary mode, leading to an
14609 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
14610 the DirRecordUsageByCountry option which would have triggered
14611 the assertion failure was added), although this assertion failure
14612 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
14613 - Selectively disable deprecation warnings on OS X because Lion
14614 started deprecating the shipped copy of openssl. Fixes bug 3643.
14615 - Remove an extra pair of quotation marks around the error
14616 message in control-port STATUS_GENERAL BUG events. Bugfix on
14617 0.1.2.6-alpha; fixes bug 3732.
14618 - When unable to format an address as a string, report its value
14619 as "???" rather than reusing the last formatted address. Bugfix
14622 o Code simplifications and refactoring:
14623 - Rewrite the listener-selection logic so that parsing which ports
14624 we want to listen on is now separate from binding to the ports
14628 - Building Tor with bufferevent support now requires Libevent
14629 2.0.13-stable or later. Previous versions of Libevent had bugs in
14630 SSL-related bufferevents and related issues that would make Tor
14631 work badly with bufferevents. Requiring 2.0.13-stable also allows
14632 Tor with bufferevents to take advantage of Libevent APIs
14633 introduced after 2.0.8-rc.
14636 Changes in version 0.2.2.32 - 2011-08-27
14637 The Tor 0.2.2 release series is dedicated to the memory of Andreas
14638 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
14639 a founder of the PETS community, a leader in our field, a mentor,
14640 and a friend. He left us with these words: "I had the possibility
14641 to contribute to this world that is not as it should be. I hope I
14642 could help in some areas to make the world a better place, and that
14643 I could also encourage other people to be engaged in improving the
14644 world. Please, stay engaged. This world needs you, your love, your
14645 initiative -- now I cannot be part of that anymore."
14647 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
14648 ready. More than two years in the making, this release features improved
14649 client performance and hidden service reliability, better compatibility
14650 for Android, correct behavior for bridges that listen on more than
14651 one address, more extensible and flexible directory object handling,
14652 better reporting of network statistics, improved code security, and
14653 many many other features and bugfixes.
14656 Changes in version 0.2.2.31-rc - 2011-08-17
14657 Tor 0.2.2.31-rc is the second and hopefully final release candidate
14658 for the Tor 0.2.2.x series.
14661 - Remove an extra pair of quotation marks around the error
14662 message in control-port STATUS_GENERAL BUG events. Bugfix on
14663 0.1.2.6-alpha; fixes bug 3732.
14664 - If we're configured to write our ControlPorts to disk, only write
14665 them after switching UID and creating the data directory. This way,
14666 we don't fail when starting up with a nonexistent DataDirectory
14667 and a ControlPortWriteToFile setting based on that directory. Fixes
14668 bug 3747; bugfix on Tor 0.2.2.26-beta.
14671 - Update to the August 2 2011 Maxmind GeoLite Country database.
14674 - Allow GETINFO fingerprint to return a fingerprint even when
14675 we have not yet built a router descriptor. Fixes bug 3577;
14676 bugfix on 0.2.0.1-alpha.
14677 - Write several files in text mode, on OSes that distinguish text
14678 mode from binary mode (namely, Windows). These files are:
14679 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
14680 that collect those statistics; 'client_keys' and 'hostname' for
14681 hidden services that use authentication; and (in the tor-gencert
14682 utility) newly generated identity and signing keys. Previously,
14683 we wouldn't specify text mode or binary mode, leading to an
14684 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
14685 the DirRecordUsageByCountry option which would have triggered
14686 the assertion failure was added), although this assertion failure
14687 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
14688 - Selectively disable deprecation warnings on OS X because Lion
14689 started deprecating the shipped copy of openssl. Fixes bug 3643.
14690 - When unable to format an address as a string, report its value
14691 as "???" rather than reusing the last formatted address. Bugfix
14695 Changes in version 0.2.3.2-alpha - 2011-07-18
14696 Tor 0.2.3.2-alpha introduces two new experimental features:
14697 microdescriptors and pluggable transports. It also continues cleaning
14698 up a variety of recently introduced features.
14701 - Clients can now use microdescriptors instead of regular descriptors
14702 to build circuits. Microdescriptors are authority-generated
14703 summaries of regular descriptors' contents, designed to change
14704 very rarely (see proposal 158 for details). This feature is
14705 designed to save bandwidth, especially for clients on slow internet
14706 connections. It's off by default for now, since nearly no caches
14707 support it, but it will be on-by-default for clients in a future
14708 version. You can use the UseMicrodescriptors option to turn it on.
14709 - Tor clients using bridges can now be configured to use a separate
14710 'transport' proxy for each bridge. This approach helps to resist
14711 censorship by allowing bridges to use protocol obfuscation
14712 plugins. It implements part of proposal 180. Implements ticket 2841.
14713 - While we're trying to bootstrap, record how many TLS connections
14714 fail in each state, and report which states saw the most failures
14715 in response to any bootstrap failures. This feature may speed up
14716 diagnosis of censorship events. Implements ticket 3116.
14718 o Major bugfixes (on 0.2.3.1-alpha):
14719 - When configuring a large set of nodes in EntryNodes (as with
14720 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
14721 random subset to be guards, and choose them in random
14722 order. Fixes bug 2798.
14723 - Tor could crash when remembering a consensus in a non-used consensus
14724 flavor without having a current consensus set. Fixes bug 3361.
14725 - Comparing an unknown address to a microdescriptor's shortened exit
14726 policy would always give a "rejected" result. Fixes bug 3599.
14727 - Using microdescriptors as a client no longer prevents Tor from
14728 uploading and downloading hidden service descriptors. Fixes
14732 - Allow nameservers with IPv6 address. Resolves bug 2574.
14733 - Accept attempts to include a password authenticator in the
14734 handshake, as supported by SOCKS5. This handles SOCKS clients that
14735 don't know how to omit a password when authenticating. Resolves
14737 - When configuring a large set of nodes in EntryNodes, and there are
14738 enough of them listed as Guard so that we don't need to consider
14739 the non-guard entries, prefer the ones listed with the Guard flag.
14740 - Check for and recover from inconsistency in the microdescriptor
14741 cache. This will make it harder for us to accidentally free a
14742 microdescriptor without removing it from the appropriate data
14743 structures. Fixes issue 3135; issue noted by "wanoskarnet".
14744 - Log SSL state transitions at log level DEBUG, log domain
14745 HANDSHAKE. This can be useful for debugging censorship events.
14746 Implements ticket 3264.
14747 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
14748 implements ticket 3439.
14750 o Minor bugfixes (on 0.2.3.1-alpha):
14751 - Do not free all general-purpose regular descriptors just
14752 because microdescriptor use is enabled. Fixes bug 3113.
14753 - Correctly link libevent_openssl when --enable-static-libevent
14754 is passed to configure. Fixes bug 3118.
14755 - Bridges should not complain during their heartbeat log messages that
14756 they are unlisted in the consensus: that's more or less the point
14757 of being a bridge. Fixes bug 3183.
14758 - Report a SIGNAL event to controllers when acting on a delayed
14759 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
14760 event to the controller if we acted on a SIGNAL NEWNYM command
14761 immediately, and otherwise not report a SIGNAL event for the
14762 command at all. Fixes bug 3349.
14763 - Fix a crash when handling the SIGNAL controller command or
14764 reporting ERR-level status events with bufferevents enabled. Found
14765 by Robert Ransom. Fixes bug 3367.
14766 - Always ship the tor-fw-helper manpage in our release tarballs.
14767 Fixes bug 3389. Reported by Stephen Walker.
14768 - Fix a class of double-mark-for-close bugs when bufferevents
14769 are enabled. Fixes bug 3403.
14770 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
14771 - Add SIGNAL to the list returned by the 'GETINFO events/names'
14772 control-port command. Fixes part of bug 3465.
14773 - Prevent using negative indices during unit test runs when read_all()
14774 fails. Spotted by coverity.
14775 - Fix a rare memory leak when checking the nodelist without it being
14776 present. Found by coverity.
14777 - Only try to download a microdescriptor-flavored consensus from
14778 a directory cache that provides them.
14780 o Minor bugfixes (on 0.2.2.x and earlier):
14781 - Assert that hidden-service-related operations are not performed
14782 using single-hop circuits. Previously, Tor would assert that
14783 client-side streams are not attached to single-hop circuits,
14784 but not that other sensitive operations on the client and service
14785 side are not performed using single-hop circuits. Fixes bug 3332;
14787 - Don't publish a new relay descriptor when we reload our onion key,
14788 unless the onion key has actually changed. Fixes bug 3263 and
14789 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
14790 - Allow GETINFO fingerprint to return a fingerprint even when
14791 we have not yet built a router descriptor. Fixes bug 3577;
14792 bugfix on 0.2.0.1-alpha.
14793 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
14794 on 0.2.2.4-alpha; fixes bug 3427.
14796 o Code simplification and refactoring:
14797 - Use tor_sscanf() in place of scanf() in more places through the
14798 code. This makes us a little more locale-independent, and
14799 should help shut up code-analysis tools that can't tell
14800 a safe sscanf string from a dangerous one.
14801 - Use tt_assert(), not tor_assert(), for checking for test failures.
14802 This makes the unit tests more able to go on in the event that
14804 - Split connection_about_to_close() into separate functions for each
14808 - On Windows, we now define the _WIN32_WINNT macros only if they
14809 are not already defined. This lets the person building Tor decide,
14810 if they want, to require a later version of Windows.
14813 Changes in version 0.2.2.30-rc - 2011-07-07
14814 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
14815 series. It fixes a few smaller bugs, but generally appears stable.
14816 Please test it and let us know whether it is!
14819 - Send a SUCCEEDED stream event to the controller when a reverse
14820 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
14821 discovered by katmagic.
14822 - Always NUL-terminate the sun_path field of a sockaddr_un before
14823 passing it to the kernel. (Not a security issue: kernels are
14824 smart enough to reject bad sockaddr_uns.) Found by Coverity;
14825 CID #428. Bugfix on Tor 0.2.0.3-alpha.
14826 - Don't stack-allocate the list of supplementary GIDs when we're
14827 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
14828 could take up to 256K, which is way too much stack. Found by
14829 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
14830 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
14831 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
14832 fixes part of bug 3465.
14833 - Fix a memory leak when receiving a descriptor for a hidden
14834 service we didn't ask for. Found by Coverity; CID #30. Bugfix
14838 - Update to the July 1 2011 Maxmind GeoLite Country database.
14841 Changes in version 0.2.2.29-beta - 2011-06-20
14842 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
14843 have bridge lines in their torrc but don't want to use them; gets
14844 us closer to having the control socket feature working on Debian;
14845 and fixes a variety of smaller bugs.
14848 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
14849 When we changed the default behavior to "use bridges if any
14850 are listed in the torrc", we surprised users who had bridges
14851 in their torrc files but who didn't actually want to use them.
14852 Partial resolution for bug 3354.
14855 - Don't attach new streams to old rendezvous circuits after SIGNAL
14856 NEWNYM. Previously, we would keep using an existing rendezvous
14857 circuit if it remained open (i.e. if it were kept open by a
14858 long-lived stream, or if a new stream were attached to it before
14859 Tor could notice that it was old and no longer in use). Bugfix on
14860 0.1.1.15-rc; fixes bug 3375.
14863 - Fix a bug when using ControlSocketsGroupWritable with User. The
14864 directory's group would be checked against the current group, not
14865 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
14866 bugfix on 0.2.2.26-beta.
14867 - Make connection_printf_to_buf()'s behavior sane. Its callers
14868 expect it to emit a CRLF iff the format string ends with CRLF;
14869 it actually emitted a CRLF iff (a) the format string ended with
14870 CRLF or (b) the resulting string was over 1023 characters long or
14871 (c) the format string did not end with CRLF *and* the resulting
14872 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
14873 fixes part of bug 3407.
14874 - Make send_control_event_impl()'s behavior sane. Its callers
14875 expect it to always emit a CRLF at the end of the string; it
14876 might have emitted extra control characters as well. Bugfix on
14877 0.1.1.9-alpha; fixes another part of bug 3407.
14878 - Make crypto_rand_int() check the value of its input correctly.
14879 Previously, it accepted values up to UINT_MAX, but could return a
14880 negative number if given a value above INT_MAX+1. Found by George
14881 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
14882 - Avoid a segfault when reading a malformed circuit build state
14883 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
14885 - When asked about a DNS record type we don't support via a
14886 client DNSPort, reply with NOTIMPL rather than an empty
14887 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
14888 - Fix a rare memory leak during stats writing. Found by coverity.
14891 - Update to the June 1 2011 Maxmind GeoLite Country database.
14893 o Code simplifications and refactoring:
14894 - Remove some dead code as indicated by coverity.
14895 - Remove a few dead assignments during router parsing. Found by
14897 - Add some forgotten return value checks during unit tests. Found
14899 - Don't use 1-bit wide signed bit fields. Found by coverity.
14902 Changes in version 0.2.2.28-beta - 2011-06-04
14903 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
14904 fixed a big bug in whether relays stay in the consensus consistently,
14905 we moved closer to handling bridges and hidden services correctly,
14906 and we started the process of better handling the dreaded "my Vidalia
14907 died, and now my Tor demands a password when I try to reconnect to it"
14911 - Don't decide to make a new descriptor when receiving a HUP signal.
14912 This bug has caused a lot of 0.2.2.x relays to disappear from the
14913 consensus periodically. Fixes the most common case of triggering
14914 bug 1810; bugfix on 0.2.2.7-alpha.
14915 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
14916 - Don't try to build descriptors if "ORPort auto" is set and we
14917 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
14919 - Resolve a crash that occurred when setting BridgeRelay to 1 with
14920 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
14921 - Apply circuit timeouts to opened hidden-service-related circuits
14922 based on the correct start time. Previously, we would apply the
14923 circuit build timeout based on time since the circuit's creation;
14924 it was supposed to be applied based on time since the circuit
14925 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
14926 - Use the same circuit timeout for client-side introduction
14927 circuits as for other four-hop circuits, rather than the timeout
14928 for single-hop directory-fetch circuits; the shorter timeout may
14929 have been appropriate with the static circuit build timeout in
14930 0.2.1.x and earlier, but caused many hidden service access attempts
14931 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
14932 on 0.2.2.2-alpha; fixes another part of bug 1297.
14933 - In ticket 2511 we fixed a case where you could use an unconfigured
14934 bridge if you had configured it as a bridge the last time you ran
14935 Tor. Now fix another edge case: if you had configured it as a bridge
14936 but then switched to a different bridge via the controller, you
14937 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
14941 - Add an __OwningControllerProcess configuration option and a
14942 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
14943 that when it exits, Tor will shut down. Implements feature 3049.
14944 - If "UseBridges 1" is set and no bridges are configured, Tor will
14945 now refuse to build any circuits until some bridges are set.
14946 If "UseBridges auto" is set, Tor will use bridges if they are
14947 configured and we are not running as a server, but otherwise will
14948 make circuits as usual. The new default is "auto". Patch by anonym,
14949 so the Tails LiveCD can stop automatically revealing you as a Tor
14953 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
14954 - Remove a trailing asterisk from "exit-policy/default" in the
14955 output of the control port command "GETINFO info/names". Bugfix
14957 - Use a wide type to hold sockets when built for 64-bit Windows builds.
14959 - Warn when the user configures two HiddenServiceDir lines that point
14960 to the same directory. Bugfix on 0.0.6 (the version introducing
14961 HiddenServiceDir); fixes bug 3289.
14962 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
14963 part of bug 2748; bugfix on 0.2.0.10-alpha.
14964 - Log malformed requests for rendezvous descriptors as protocol
14965 warnings, not warnings. Also, use a more informative log message
14966 in case someone sees it at log level warning without prior
14967 info-level messages. Fixes the other part of bug 2748; bugfix
14969 - Clear the table recording the time of the last request for each
14970 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
14971 Previously, we would clear our HS descriptor cache on SIGNAL
14972 NEWNYM, but if we had previously retrieved a descriptor (or tried
14973 to) from every directory responsible for it, we would refuse to
14974 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
14976 - Fix a log message that said "bits" while displaying a value in
14977 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
14979 - When checking for 1024-bit keys, check for 1024 bits, not 128
14980 bytes. This allows Tor to correctly discard keys of length 1017
14981 through 1023. Bugfix on 0.0.9pre5.
14984 - Relays now log the reason for publishing a new relay descriptor,
14985 so we have a better chance of hunting down instances of bug 1810.
14986 Resolves ticket 3252.
14987 - Revise most log messages that refer to nodes by nickname to
14988 instead use the "$key=nickname at address" format. This should be
14989 more useful, especially since nicknames are less and less likely
14990 to be unique. Resolves ticket 3045.
14991 - Log (at info level) when purging pieces of hidden-service-client
14992 state because of SIGNAL NEWNYM.
14995 - Remove undocumented option "-F" from tor-resolve: it hasn't done
14996 anything since 0.2.1.16-rc.
14999 Changes in version 0.2.2.27-beta - 2011-05-18
15000 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
15001 release, and also adds a few more general bugfixes.
15004 - Fix a crash bug when changing bridges in a running Tor process.
15005 Fixes bug 3213; bugfix on 0.2.2.26-beta.
15006 - When the controller configures a new bridge, don't wait 10 to 60
15007 seconds before trying to fetch its descriptor. Bugfix on
15008 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
15011 - Require that onion keys have exponent 65537 in microdescriptors too.
15012 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
15013 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
15014 Changed the limit to 512 characters by removing base64 newlines.
15015 Fixes bug 2752. Fix by Michael Yakubovich.
15016 - When a client starts or stops using bridges, never use a circuit
15017 that was built before the configuration change. This behavior could
15018 put at risk a user who uses bridges to ensure that her traffic
15019 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
15023 Changes in version 0.2.2.26-beta - 2011-05-17
15024 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
15025 also introduces a new "socksport auto" approach that should make it
15026 easier to run multiple Tors on the same system, and does a lot of
15027 cleanup to get us closer to a release candidate.
15029 o Security/privacy fixes:
15030 - Replace all potentially sensitive memory comparison operations
15031 with versions whose runtime does not depend on the data being
15032 compared. This will help resist a class of attacks where an
15033 adversary can use variations in timing information to learn
15034 sensitive data. Fix for one case of bug 3122. (Safe memcmp
15035 implementation by Robert Ransom based partially on code by DJB.)
15036 - When receiving a hidden service descriptor, check that it is for
15037 the hidden service we wanted. Previously, Tor would store any
15038 hidden service descriptors that a directory gave it, whether it
15039 wanted them or not. This wouldn't have let an attacker impersonate
15040 a hidden service, but it did let directories pre-seed a client
15041 with descriptors that it didn't want. Bugfix on 0.0.6.
15042 - On SIGHUP, do not clear out all TrackHostExits mappings, client
15043 DNS cache entries, and virtual address mappings: that's what
15044 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
15047 - The options SocksPort, ControlPort, and so on now all accept a
15048 value "auto" that opens a socket on an OS-selected port. A
15049 new ControlPortWriteToFile option tells Tor to write its
15050 actual control port or ports to a chosen file. If the option
15051 ControlPortFileGroupReadable is set, the file is created as
15052 group-readable. Now users can run two Tor clients on the same
15053 system without needing to manually mess with parameters. Resolves
15054 part of ticket 3076.
15055 - Set SO_REUSEADDR on all sockets, not just listeners. This should
15056 help busy exit nodes avoid running out of useable ports just
15057 because all the ports have been used in the near past. Resolves
15061 - New "GETINFO net/listeners/(type)" controller command to return
15062 a list of addresses and ports that are bound for listeners for a
15063 given connection type. This is useful when the user has configured
15064 "SocksPort auto" and the controller needs to know which port got
15065 chosen. Resolves another part of ticket 3076.
15066 - Add a new ControlSocketsGroupWritable configuration option: when
15067 it is turned on, ControlSockets are group-writeable by the default
15068 group of the current user. Patch by Jérémy Bobbio; implements
15070 - Tor now refuses to create a ControlSocket in a directory that is
15071 world-readable (or group-readable if ControlSocketsGroupWritable
15072 is 0). This is necessary because some operating systems do not
15073 enforce permissions on an AF_UNIX sockets. Permissions on the
15074 directory holding the socket, however, seems to work everywhere.
15075 - Rate-limit a warning about failures to download v2 networkstatus
15076 documents. Resolves part of bug 1352.
15077 - Backport code from 0.2.3.x that allows directory authorities to
15078 clean their microdescriptor caches. Needed to resolve bug 2230.
15079 - When an HTTPS proxy reports "403 Forbidden", we now explain
15080 what it means rather than calling it an unexpected status code.
15081 Closes bug 2503. Patch from Michael Yakubovich.
15082 - Update to the May 1 2011 Maxmind GeoLite Country database.
15085 - Authorities now clean their microdesc cache periodically and when
15086 reading from disk initially, not only when adding new descriptors.
15087 This prevents a bug where we could lose microdescriptors. Bugfix
15088 on 0.2.2.6-alpha. Fixes bug 2230.
15089 - Do not crash when our configuration file becomes unreadable, for
15090 example due to a permissions change, between when we start up
15091 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
15093 - Avoid a bug that would keep us from replacing a microdescriptor
15094 cache on Windows. (We would try to replace the file while still
15095 holding it open. That's fine on Unix, but Windows doesn't let us
15096 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
15097 - Add missing explanations for the authority-related torrc options
15098 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
15099 man page. Resolves issue 2379.
15100 - As an authority, do not upload our own vote or signature set to
15101 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
15102 it would get flagged as a duplicate. Resolves bug 3026.
15103 - Accept hidden service descriptors if we think we might be a hidden
15104 service directory, regardless of what our consensus says. This
15105 helps robustness, since clients and hidden services can sometimes
15106 have a more up-to-date view of the network consensus than we do,
15107 and if they think that the directory authorities list us a HSDir,
15108 we might actually be one. Related to bug 2732; bugfix on
15110 - When a controller changes TrackHostExits, remove mappings for
15111 hosts that should no longer have their exits tracked. Bugfix on
15113 - When a controller changes VirtualAddrNetwork, remove any mappings
15114 for hosts that were automapped to the old network. Bugfix on
15116 - When a controller changes one of the AutomapHosts* options, remove
15117 any mappings for hosts that should no longer be automapped. Bugfix
15119 - Do not reset the bridge descriptor download status every time we
15120 re-parse our configuration or get a configuration change. Fixes
15121 bug 3019; bugfix on 0.2.0.3-alpha.
15123 o Minor bugfixes (code cleanup):
15124 - When loading the microdesc journal, remember its current size.
15125 In 0.2.2, this helps prevent the microdesc journal from growing
15126 without limit on authorities (who are the only ones to use it in
15127 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
15128 Fix posted by "cypherpunks."
15129 - The microdesc journal is supposed to get rebuilt only if it is
15130 at least _half_ the length of the store, not _twice_ the length
15131 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
15132 - Fix a potential null-pointer dereference while computing a
15133 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
15135 - Avoid a possible null-pointer dereference when rebuilding the mdesc
15136 cache without actually having any descriptors to cache. Bugfix on
15137 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
15138 - If we fail to compute the identity digest of a v3 legacy keypair,
15139 warn, and don't use a buffer-full of junk instead. Bugfix on
15140 0.2.1.1-alpha; fixes bug 3106.
15141 - Resolve an untriggerable issue in smartlist_string_num_isin(),
15142 where if the function had ever in the future been used to check
15143 for the presence of a too-large number, it would have given an
15144 incorrect result. (Fortunately, we only used it for 16-bit
15145 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
15146 - Require that introduction point keys and onion handshake keys
15147 have a public exponent of 65537. Starts to fix bug 3207; bugfix
15150 o Removed features:
15151 - Caches no longer download and serve v2 networkstatus documents
15152 unless FetchV2Networkstatus flag is set: these documents haven't
15153 haven't been used by clients or relays since 0.2.0.x. Resolves
15157 Changes in version 0.2.3.1-alpha - 2011-05-05
15158 Tor 0.2.3.1-alpha adds some new experimental features, including support
15159 for an improved network IO backend, IOCP networking on Windows,
15160 microdescriptor caching, "fast-start" support for streams, and automatic
15161 home router configuration. There are also numerous internal improvements
15162 to try to make the code easier for developers to work with.
15164 This is the first alpha release in a new series, so expect there to be
15165 bugs. Users who would rather test out a more stable branch should
15166 stay with 0.2.2.x for now.
15169 - Tor can now optionally build with the "bufferevents" buffered IO
15170 backend provided by Libevent 2. To use this feature, make sure you
15171 have the latest possible version of Libevent, and pass the
15172 --enable-bufferevents flag to configure when building Tor from
15173 source. This feature will make our networking code more flexible,
15174 let us stack layers on each other, and let us use more efficient
15175 zero-copy transports where available.
15176 - As an experimental feature, Tor can use IOCP for networking on Windows.
15177 Once this code is tuned and optimized, it promises much better
15178 performance than the select-based backend we've used in the past. To
15179 try this feature, you must build Tor with Libevent 2, configure Tor
15180 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
15181 your torrc. There are known bugs here: only try this if you can help
15182 debug it as it breaks.
15183 - The EntryNodes option can now include country codes like {de} or IP
15184 addresses or network masks. Previously we had disallowed these options
15185 because we didn't have an efficient way to keep the list up to
15186 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
15187 - Exit nodes now accept and queue data on not-yet-connected streams.
15188 Previously, the client wasn't allowed to send data until the stream was
15189 connected, which slowed down all connections. This change will enable
15190 clients to perform a "fast-start" on streams and send data without
15191 having to wait for a confirmation that the stream has opened. (Patch
15192 from Ian Goldberg; implements the server side of Proposal 174.)
15193 - Tor now has initial support for automatic port mapping on the many
15194 home routers that support NAT-PMP or UPnP. (Not yet supported on
15195 Windows). To build the support code, you'll need to have libnatpnp
15196 library and/or the libminiupnpc library, and you'll need to enable the
15197 feature specifically by passing "--enable-upnp" and/or
15198 "--enable-natpnp" to configure. To turn it on, use the new
15199 PortForwarding option.
15200 - Caches now download, cache, and serve multiple "flavors" of the
15201 consensus, including a flavor that describes microdescriptors.
15202 - Caches now download, cache, and serve microdescriptors -- small
15203 summaries of router descriptors that are authenticated by all of the
15204 directory authorities. Once enough caches are running this code,
15205 clients will be able to save significant amounts of directory bandwidth
15206 by downloading microdescriptors instead of router descriptors.
15209 - Make logging resolution configurable with a new LogTimeGranularity
15210 option, and change the default from 1 millisecond to 1 second.
15211 Implements enhancement 1668.
15212 - We log which torrc file we're using on startup. Implements ticket
15214 - Ordinarily, Tor does not count traffic from private addresses (like
15215 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
15216 There is now a new option, CountPrivateBandwidth, to disable this
15217 behavior. Patch from Daniel Cagara.
15218 - New --enable-static-tor configure option for building Tor as
15219 statically as possible. Idea, general hackery and thoughts from
15220 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
15222 - If you set the NumCPUs option to 0, Tor will now try to detect how
15223 many CPUs you have. This is the new default behavior.
15224 - Turn on directory request statistics by default and include them in
15225 extra-info descriptors. Don't break if we have no GeoIP database.
15226 - Relays that set "ConnDirectionStatistics 1" write statistics on the
15227 bidirectional use of connections to disk every 24 hours.
15228 - Add a GeoIP file digest to the extra-info descriptor. Implements
15230 - The NodeFamily option -- which let you declare that you want to
15231 consider nodes to be part of a family whether they list themselves
15232 that way or not -- now allows IP address ranges and country codes.
15233 - Add a new 'Heartbeat' log message type to periodically log a message
15234 describing Tor's status at level Notice. This feature is meant for
15235 operators who log at notice, and want to make sure that their Tor
15236 server is still working. Implementation by George Kadianakis.
15238 o Minor bugfixes (on 0.2.2.25-alpha):
15239 - When loading the microdesc journal, remember its current size.
15240 In 0.2.2, this helps prevent the microdesc journal from growing
15241 without limit on authorities (who are the only ones to use it in
15242 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
15243 Fix posted by "cypherpunks."
15244 - The microdesc journal is supposed to get rebuilt only if it is
15245 at least _half_ the length of the store, not _twice_ the length
15246 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
15247 - If as an authority we fail to compute the identity digest of a v3
15248 legacy keypair, warn, and don't use a buffer-full of junk instead.
15249 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
15250 - Authorities now clean their microdesc cache periodically and when
15251 reading from disk initially, not only when adding new descriptors.
15252 This prevents a bug where we could lose microdescriptors. Bugfix
15255 o Minor features (controller):
15256 - Add a new SIGNAL event to the controller interface so that
15257 controllers can be notified when Tor handles a signal. Resolves
15258 issue 1955. Patch by John Brooks.
15259 - Add a new GETINFO option to get total bytes read and written. Patch
15260 from pipe, revised by atagar. Resolves ticket 2345.
15261 - Implement some GETINFO controller fields to provide information about
15262 the Tor process's pid, euid, username, and resource limits.
15265 - Our build system requires automake 1.6 or later to create the
15266 Makefile.in files. Previously, you could have used 1.4.
15267 This only affects developers and people building Tor from git;
15268 people who build Tor from the source distribution without changing
15269 the Makefile.am files should be fine.
15270 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
15271 so on. This is more robust against some of the failure modes
15272 associated with running the autotools pieces on their own.
15274 o Minor packaging issues:
15275 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
15276 already created. Patch from Andreas Stieger. Fixes bug 2573.
15278 o Code simplifications and refactoring:
15279 - A major revision to our internal node-selecting and listing logic.
15280 Tor already had at least two major ways to look at the question of
15281 "which Tor servers do we know about": a list of router descriptors,
15282 and a list of entries in the current consensus. With
15283 microdescriptors, we're adding a third. Having so many systems
15284 without an abstraction layer over them was hurting the codebase.
15285 Now, we have a new "node_t" abstraction that presents a consistent
15286 interface to a client's view of a Tor node, and holds (nearly) all
15287 of the mutable state formerly in routerinfo_t and routerstatus_t.
15288 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
15289 no longer link against Libevent: they never used it, but
15290 our library structure used to force them to link it.
15292 o Removed features:
15293 - Remove some old code to work around even older versions of Tor that
15294 used forked processes to handle DNS requests. Such versions of Tor
15295 are no longer in use as servers.
15297 o Documentation fixes:
15298 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
15299 - Add missing documentation for the authority-related torrc options
15300 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
15304 Changes in version 0.2.2.25-alpha - 2011-04-29
15305 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
15306 robust, routers no longer overreport their bandwidth, Win7 should crash
15307 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
15308 now prevents hidden service-related activity from being linkable. It
15309 provides more information to Vidalia so you can see if your bridge is
15310 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
15311 StrictNodes configuration options to make them more reliable, more
15312 understandable, and more regularly applied. If you use those options,
15313 please see the revised documentation for them in the manual page.
15316 - Relays were publishing grossly inflated bandwidth values because
15317 they were writing their state files wrong--now they write the
15318 correct value. Also, resume reading bandwidth history from the
15319 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
15320 - Improve hidden service robustness: When we find that we have
15321 extended a hidden service's introduction circuit to a relay not
15322 listed as an introduction point in the HS descriptor we currently
15323 have, retry with an introduction point from the current
15324 descriptor. Previously we would just give up. Fixes bugs 1024 and
15325 1930; bugfix on 0.2.0.10-alpha.
15326 - Clients now stop trying to use an exit node associated with a given
15327 destination by TrackHostExits if they fail to reach that exit node.
15328 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
15329 - Fix crash bug on platforms where gmtime and localtime can return
15330 NULL. Windows 7 users were running into this one. Fixes part of bug
15331 2077. Bugfix on all versions of Tor. Found by boboper.
15333 o Security and stability fixes:
15334 - Don't double-free a parsable, but invalid, microdescriptor, even if
15335 it is followed in the blob we're parsing by an unparsable
15336 microdescriptor. Fixes an issue reported in a comment on bug 2954.
15337 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
15338 - If the Nickname configuration option isn't given, Tor would pick a
15339 nickname based on the local hostname as the nickname for a relay.
15340 Because nicknames are not very important in today's Tor and the
15341 "Unnamed" nickname has been implemented, this is now problematic
15342 behavior: It leaks information about the hostname without being
15343 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
15344 introduced the Unnamed nickname. Reported by tagnaq.
15345 - Fix an uncommon assertion failure when running with DNSPort under
15346 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
15347 - Avoid linkability based on cached hidden service descriptors: forget
15348 all hidden service descriptors cached as a client when processing a
15349 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
15352 - Export GeoIP information on bridge usage to controllers even if we
15353 have not yet been running for 24 hours. Now Vidalia bridge operators
15354 can get more accurate and immediate feedback about their
15355 contributions to the network.
15357 o Major features and bugfixes (node selection):
15358 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
15359 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
15360 options. Previously, we had been ambiguous in describing what
15361 counted as an "exit" node, and what operations exactly "StrictNodes
15362 0" would permit. This created confusion when people saw nodes built
15363 through unexpected circuits, and made it hard to tell real bugs from
15364 surprises. Now the intended behavior is:
15365 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
15366 a node that delivers user traffic outside the Tor network.
15367 . "Entry", in the context of EntryNodes, means a node used as the
15368 first hop of a multihop circuit. It doesn't include direct
15369 connections to directory servers.
15370 . "ExcludeNodes" applies to all nodes.
15371 . "StrictNodes" changes the behavior of ExcludeNodes only. When
15372 StrictNodes is set, Tor should avoid all nodes listed in
15373 ExcludeNodes, even when it will make user requests fail. When
15374 StrictNodes is *not* set, then Tor should follow ExcludeNodes
15375 whenever it can, except when it must use an excluded node to
15376 perform self-tests, connect to a hidden service, provide a
15377 hidden service, fulfill a .exit request, upload directory
15378 information, or fetch directory information.
15379 Collectively, the changes to implement the behavior fix bug 1090.
15380 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
15381 a node is listed in both, it's treated as excluded.
15382 - ExcludeNodes now applies to directory nodes -- as a preference if
15383 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
15384 Don't exclude all the directory authorities and set StrictNodes to 1
15385 unless you really want your Tor to break.
15386 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
15387 - ExcludeExitNodes now overrides .exit requests.
15388 - We don't use bridges listed in ExcludeNodes.
15389 - When StrictNodes is 1:
15390 . We now apply ExcludeNodes to hidden service introduction points
15391 and to rendezvous points selected by hidden service users. This
15392 can make your hidden service less reliable: use it with caution!
15393 . If we have used ExcludeNodes on ourself, do not try relay
15394 reachability self-tests.
15395 . If we have excluded all the directory authorities, we will not
15396 even try to upload our descriptor if we're a relay.
15397 . Do not honor .exit requests to an excluded node.
15398 - Remove a misfeature that caused us to ignore the Fast/Stable flags
15399 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
15400 - When the set of permitted nodes changes, we now remove any mappings
15401 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
15403 - We never cannibalize a circuit that had excluded nodes on it, even
15404 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
15405 - Revert a change where we would be laxer about attaching streams to
15406 circuits than when building the circuits. This was meant to prevent
15407 a set of bugs where streams were never attachable, but our improved
15408 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
15409 - Keep track of how many times we launch a new circuit to handle a
15410 given stream. Too many launches could indicate an inconsistency
15411 between our "launch a circuit to handle this stream" logic and our
15412 "attach this stream to one of the available circuits" logic.
15413 - Improve log messages related to excluded nodes.
15416 - Fix a spurious warning when moving from a short month to a long
15417 month on relays with month-based BandwidthAccounting. Bugfix on
15418 0.2.2.17-alpha; fixes bug 3020.
15419 - When a client finds that an origin circuit has run out of 16-bit
15420 stream IDs, we now mark it as unusable for new streams. Previously,
15421 we would try to close the entire circuit. Bugfix on 0.0.6.
15422 - Add a forgotten cast that caused a compile warning on OS X 10.6.
15423 Bugfix on 0.2.2.24-alpha.
15424 - Be more careful about reporting the correct error from a failed
15425 connect() system call. Under some circumstances, it was possible to
15426 look at an incorrect value for errno when sending the end reason.
15427 Bugfix on 0.1.0.1-rc.
15428 - Correctly handle an "impossible" overflow cases in connection byte
15429 counting, where we write or read more than 4GB on an edge connection
15430 in a single second. Bugfix on 0.1.2.8-beta.
15431 - Correct the warning displayed when a rendezvous descriptor exceeds
15432 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
15434 - Clients and hidden services now use HSDir-flagged relays for hidden
15435 service descriptor downloads and uploads even if the relays have no
15436 DirPort set and the client has disabled TunnelDirConns. This will
15437 eventually allow us to give the HSDir flag to relays with no
15438 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
15439 - Downgrade "no current certificates known for authority" message from
15440 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
15441 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
15442 2917. Bugfix on 0.1.1.1-alpha.
15443 - Only limit the lengths of single HS descriptors, even when multiple
15444 HS descriptors are published to an HSDir relay in a single POST
15445 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
15446 - Write the current time into the LastWritten line in our state file,
15447 rather than the time from the previous write attempt. Also, stop
15448 trying to use a time of -1 in our log statements. Fixes bug 3039;
15449 bugfix on 0.2.2.14-alpha.
15450 - Be more consistent in our treatment of file system paths. "~" should
15451 get expanded to the user's home directory in the Log config option.
15452 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
15453 feature for the -f and --DataDirectory options.
15456 - Make sure every relay writes a state file at least every 12 hours.
15457 Previously, a relay could go for weeks without writing its state
15458 file, and on a crash could lose its bandwidth history, capacity
15459 estimates, client country statistics, and so on. Addresses bug 3012.
15460 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
15461 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
15462 clients are already deprecated because of security bugs.
15463 - Don't allow v0 hidden service authorities to act as clients.
15464 Required by fix for bug 3000.
15465 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
15466 by fix for bug 3000.
15467 - Ensure that no empty [dirreq-](read|write)-history lines are added
15468 to an extrainfo document. Implements ticket 2497.
15470 o Code simplification and refactoring:
15471 - Remove workaround code to handle directory responses from servers
15472 that had bug 539 (they would send HTTP status 503 responses _and_
15473 send a body too). Since only server versions before
15474 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
15475 keep the workaround in place.
15476 - Remove the old 'fuzzy time' logic. It was supposed to be used for
15477 handling calculations where we have a known amount of clock skew and
15478 an allowed amount of unknown skew. But we only used it in three
15479 places, and we never adjusted the known/unknown skew values. This is
15480 still something we might want to do someday, but if we do, we'll
15481 want to do it differently.
15482 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
15483 None of the cases where we did this before were wrong, but by making
15484 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
15485 - Use GetTempDir to find the proper temporary directory location on
15486 Windows when generating temporary files for the unit tests. Patch by
15490 Changes in version 0.2.2.24-alpha - 2011-04-08
15491 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
15492 prevented Tor clients from effectively using "multihomed" bridges,
15493 that is, bridges that listen on multiple ports or IP addresses so users
15494 can continue to use some of their addresses even if others get blocked.
15497 - Fix a bug where bridge users who configure the non-canonical
15498 address of a bridge automatically switch to its canonical
15499 address. If a bridge listens at more than one address, it should be
15500 able to advertise those addresses independently and any non-blocked
15501 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
15503 - If you configured Tor to use bridge A, and then quit and
15504 configured Tor to use bridge B instead, it would happily continue
15505 to use bridge A if it's still reachable. While this behavior is
15506 a feature if your goal is connectivity, in some scenarios it's a
15507 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
15508 - Directory authorities now use data collected from their own
15509 uptime observations when choosing whether to assign the HSDir flag
15510 to relays, instead of trusting the uptime value the relay reports in
15511 its descriptor. This change helps prevent an attack where a small
15512 set of nodes with frequently-changing identity keys can blackhole
15513 a hidden service. (Only authorities need upgrade; others will be
15514 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
15517 - When we restart our relay, we might get a successful connection
15518 from the outside before we've started our reachability tests,
15519 triggering a warning: "ORPort found reachable, but I have no
15520 routerinfo yet. Failing to inform controller of success." This
15521 bug was harmless unless Tor is running under a controller
15522 like Vidalia, in which case the controller would never get a
15523 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
15525 - Make directory authorities more accurate at recording when
15526 relays that have failed several reachability tests became
15527 unreachable, so we can provide more accuracy at assigning Stable,
15528 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
15529 - Fix an issue that prevented static linking of libevent on
15530 some platforms (notably Linux). Fixes bug 2698; bugfix on
15531 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
15532 the --with-static-libevent configure option).
15533 - We now ask the other side of a stream (the client or the exit)
15534 for more data on that stream when the amount of queued data on
15535 that stream dips low enough. Previously, we wouldn't ask the
15536 other side for more data until either it sent us more data (which
15537 it wasn't supposed to do if it had exhausted its window!) or we
15538 had completely flushed all our queued data. This flow control fix
15539 should improve throughput. Fixes bug 2756; bugfix on the earliest
15540 released versions of Tor (svn commit r152).
15541 - Avoid a double-mark-for-free warning when failing to attach a
15542 transparent proxy connection. (We thought we had fixed this in
15543 0.2.2.23-alpha, but it turns out our fix was checking the wrong
15544 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
15545 bug) and 0.2.2.23-alpha (the incorrect fix).
15546 - When warning about missing zlib development packages during compile,
15547 give the correct package names. Bugfix on 0.2.0.1-alpha.
15550 - Directory authorities now log the source of a rejected POSTed v3
15551 networkstatus vote.
15552 - Make compilation with clang possible when using
15553 --enable-gcc-warnings by removing two warning options that clang
15554 hasn't implemented yet and by fixing a few warnings. Implements
15556 - When expiring circuits, use microsecond timers rather than
15557 one-second timers. This can avoid an unpleasant situation where a
15558 circuit is launched near the end of one second and expired right
15559 near the beginning of the next, and prevent fluctuations in circuit
15561 - Use computed circuit-build timeouts to decide when to launch
15562 parallel introduction circuits for hidden services. (Previously,
15563 we would retry after 15 seconds.)
15564 - Update to the April 1 2011 Maxmind GeoLite Country database.
15567 - Create the /var/run/tor directory on startup on OpenSUSE if it is
15568 not already created. Patch from Andreas Stieger. Fixes bug 2573.
15570 o Documentation changes:
15571 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
15572 - Resolve all doxygen warnings except those for missing documentation.
15574 - Add doxygen documentation for more functions, fields, and types.
15577 Changes in version 0.2.2.23-alpha - 2011-03-08
15578 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
15579 they restart they don't lose their bandwidth capacity estimate. This
15580 release also fixes a diverse set of user-facing bugs, ranging from
15581 relays overrunning their rate limiting to clients falsely warning about
15582 clock skew to bridge descriptor leaks by our bridge directory authority.
15585 - Stop sending a CLOCK_SKEW controller status event whenever
15586 we fetch directory information from a relay that has a wrong clock.
15587 Instead, only inform the controller when it's a trusted authority
15588 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
15589 the rest of bug 1074.
15590 - Fix an assert in parsing router descriptors containing IPv6
15591 addresses. This one took down the directory authorities when
15592 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
15593 - Make the bridge directory authority refuse to answer directory
15594 requests for "all" descriptors. It used to include bridge
15595 descriptors in its answer, which was a major information leak.
15596 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
15597 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
15598 Tor would ignore their RelayBandwidthBurst setting,
15599 potentially using more bandwidth than expected. Bugfix on
15600 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
15601 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
15602 hidserv" in her torrc. The 'hidserv' argument never controlled
15603 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
15606 - Relays now save observed peak bandwidth throughput rates to their
15607 state file (along with total usage, which was already saved)
15608 so that they can determine their correct estimated bandwidth on
15609 restart. Resolves bug 1863, where Tor relays would reset their
15610 estimated bandwidth to 0 after restarting.
15611 - Directory authorities now take changes in router IP address and
15612 ORPort into account when determining router stability. Previously,
15613 if a router changed its IP or ORPort, the authorities would not
15614 treat it as having any downtime for the purposes of stability
15615 calculation, whereas clients would experience downtime since the
15616 change could take a while to propagate to them. Resolves issue 1035.
15617 - Enable Address Space Layout Randomization (ASLR) and Data Execution
15618 Prevention (DEP) by default on Windows to make it harder for
15619 attackers to exploit vulnerabilities. Patch from John Brooks.
15621 o Minor bugfixes (on 0.2.1.x and earlier):
15622 - Fix a rare crash bug that could occur when a client was configured
15623 with a large number of bridges. Fixes bug 2629; bugfix on
15624 0.2.1.2-alpha. Bugfix by trac user "shitlei".
15625 - Avoid a double mark-for-free warning when failing to attach a
15626 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
15628 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
15629 found by "cypherpunks". This bug was introduced before the first
15630 Tor release, in svn commit r110.
15631 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
15632 don't mention them in the manpage. Fixes bug 2450; issue
15633 spotted by keb and G-Lo.
15634 - Fix a bug in bandwidth history state parsing that could have been
15635 triggered if a future version of Tor ever changed the timing
15636 granularity at which bandwidth history is measured. Bugfix on
15637 Tor 0.1.1.11-alpha.
15638 - When a relay decides that its DNS is too broken for it to serve
15639 as an exit server, it advertised itself as a non-exit, but
15640 continued to act as an exit. This could create accidental
15641 partitioning opportunities for users. Instead, if a relay is
15642 going to advertise reject *:* as its exit policy, it should
15643 really act with exit policy "reject *:*". Fixes bug 2366.
15644 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
15645 - In the special case where you configure a public exit relay as your
15646 bridge, Tor would be willing to use that exit relay as the last
15647 hop in your circuit as well. Now we fail that circuit instead.
15648 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
15649 - Fix a bug with our locking implementation on Windows that couldn't
15650 correctly detect when a file was already locked. Fixes bug 2504,
15651 bugfix on 0.2.1.6-alpha.
15652 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
15653 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
15655 - Set target port in get_interface_address6() correctly. Bugfix
15656 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
15657 - Directory authorities are now more robust to hops back in time
15658 when calculating router stability. Previously, if a run of uptime
15659 or downtime appeared to be negative, the calculation could give
15660 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
15662 - Fix an assert that got triggered when using the TestingTorNetwork
15663 configuration option and then issuing a GETINFO config-text control
15664 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
15666 o Minor bugfixes (on 0.2.2.x):
15667 - Clients should not weight BadExit nodes as Exits in their node
15668 selection. Similarly, directory authorities should not count BadExit
15669 bandwidth as Exit bandwidth when computing bandwidth-weights.
15670 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
15671 - Correctly clear our dir_read/dir_write history when there is an
15672 error parsing any bw history value from the state file. Bugfix on
15673 Tor 0.2.2.15-alpha.
15674 - Resolve a bug in verifying signatures of directory objects
15675 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
15676 Fixes bug 2409. Found by "piebeer".
15677 - Bridge authorities no longer crash on SIGHUP when they try to
15678 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
15682 - Log less aggressively about circuit timeout changes, and improve
15683 some other circuit timeout messages. Resolves bug 2004.
15684 - Log a little more clearly about the times at which we're no longer
15685 accepting new connections. Resolves bug 2181.
15686 - Reject attempts at the client side to open connections to private
15687 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
15688 a randomly chosen exit node. Attempts to do so are always
15689 ill-defined, generally prevented by exit policies, and usually
15690 in error. This will also help to detect loops in transparent
15691 proxy configurations. You can disable this feature by setting
15692 "ClientRejectInternalAddresses 0" in your torrc.
15693 - Always treat failure to allocate an RSA key as an unrecoverable
15695 - Update to the March 1 2011 Maxmind GeoLite Country database.
15697 o Minor features (log subsystem):
15698 - Add documentation for configuring logging at different severities in
15699 different log domains. We've had this feature since 0.2.1.1-alpha,
15700 but for some reason it never made it into the manpage. Fixes
15702 - Make it simpler to specify "All log domains except for A and B".
15703 Previously you needed to say "[*,~A,~B]". Now you can just say
15705 - Add a "LogMessageDomains 1" option to include the domains of log
15706 messages along with the messages. Without this, there's no way
15707 to use log domains without reading the source or doing a lot
15710 o Packaging changes:
15711 - Stop shipping the Tor specs files and development proposal documents
15712 in the tarball. They are now in a separate git repository at
15713 git://git.torproject.org/torspec.git
15716 Changes in version 0.2.1.30 - 2011-02-23
15717 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
15718 change is a slight tweak to Tor's TLS handshake that makes relays
15719 and bridges that run this new version reachable from Iran again.
15720 We don't expect this tweak will win the arms race long-term, but it
15721 buys us time until we roll out a better solution.
15724 - Stop sending a CLOCK_SKEW controller status event whenever
15725 we fetch directory information from a relay that has a wrong clock.
15726 Instead, only inform the controller when it's a trusted authority
15727 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
15728 the rest of bug 1074.
15729 - Fix a bounds-checking error that could allow an attacker to
15730 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
15731 Found by "piebeer".
15732 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
15733 Tor would ignore their RelayBandwidthBurst setting,
15734 potentially using more bandwidth than expected. Bugfix on
15735 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
15736 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
15737 hidserv" in her torrc. The 'hidserv' argument never controlled
15738 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
15741 - Adjust our TLS Diffie-Hellman parameters to match those used by
15743 - Update to the February 1 2011 Maxmind GeoLite Country database.
15746 - Check for and reject overly long directory certificates and
15747 directory tokens before they have a chance to hit any assertions.
15748 Bugfix on 0.2.1.28. Found by "doorss".
15749 - Bring the logic that gathers routerinfos and assesses the
15750 acceptability of circuits into line. This prevents a Tor OP from
15751 getting locked in a cycle of choosing its local OR as an exit for a
15752 path (due to a .exit request) and then rejecting the circuit because
15753 its OR is not listed yet. It also prevents Tor clients from using an
15754 OR running in the same instance as an exit (due to a .exit request)
15755 if the OR does not meet the same requirements expected of an OR
15756 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
15758 o Packaging changes:
15759 - Stop shipping the Tor specs files and development proposal documents
15760 in the tarball. They are now in a separate git repository at
15761 git://git.torproject.org/torspec.git
15762 - Do not include Git version tags as though they are SVN tags when
15763 generating a tarball from inside a repository that has switched
15764 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
15767 Changes in version 0.2.2.22-alpha - 2011-01-25
15768 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
15769 main other change is a slight tweak to Tor's TLS handshake that makes
15770 relays and bridges that run this new version reachable from Iran again.
15771 We don't expect this tweak will win the arms race long-term, but it
15772 will buy us a bit more time until we roll out a better solution.
15775 - Fix a bounds-checking error that could allow an attacker to
15776 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
15777 Found by "piebeer".
15778 - Don't assert when changing from bridge to relay or vice versa
15779 via the controller. The assert happened because we didn't properly
15780 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
15781 bug 2433. Reported by bastik.
15784 - Adjust our TLS Diffie-Hellman parameters to match those used by
15786 - Provide a log message stating which geoip file we're parsing
15787 instead of just stating that we're parsing the geoip file.
15788 Implements ticket 2432.
15791 - Check for and reject overly long directory certificates and
15792 directory tokens before they have a chance to hit any assertions.
15793 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
15796 Changes in version 0.2.2.21-alpha - 2011-01-15
15797 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
15798 continues our recent code security audit work. The main fix resolves
15799 a remote heap overflow vulnerability that can allow remote code
15800 execution (CVE-2011-0427). Other fixes address a variety of assert
15801 and crash bugs, most of which we think are hard to exploit remotely.
15803 o Major bugfixes (security), also included in 0.2.1.29:
15804 - Fix a heap overflow bug where an adversary could cause heap
15805 corruption. This bug probably allows remote code execution
15806 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
15808 - Prevent a denial-of-service attack by disallowing any
15809 zlib-compressed data whose compression factor is implausibly
15810 high. Fixes part of bug 2324; reported by "doorss".
15811 - Zero out a few more keys in memory before freeing them. Fixes
15812 bug 2384 and part of bug 2385. These key instances found by
15813 "cypherpunks", based on Andrew Case's report about being able
15814 to find sensitive data in Tor's memory space if you have enough
15815 permissions. Bugfix on 0.0.2pre9.
15817 o Major bugfixes (crashes), also included in 0.2.1.29:
15818 - Prevent calls to Libevent from inside Libevent log handlers.
15819 This had potential to cause a nasty set of crashes, especially
15820 if running Libevent with debug logging enabled, and running
15821 Tor with a controller watching for low-severity log messages.
15822 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
15823 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
15824 underflow errors there too. Fixes the other part of bug 2324.
15825 - Fix a bug where we would assert if we ever had a
15826 cached-descriptors.new file (or another file read directly into
15827 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
15828 on 0.2.1.25. Found by doorss.
15829 - Fix some potential asserts and parsing issues with grossly
15830 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
15833 o Minor bugfixes (other), also included in 0.2.1.29:
15834 - Fix a bug with handling misformed replies to reverse DNS lookup
15835 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
15836 bug reported by doorss.
15837 - Fix compilation on mingw when a pthreads compatibility library
15838 has been installed. (We don't want to use it, so we shouldn't
15839 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
15840 - Fix a bug where we would declare that we had run out of virtual
15841 addresses when the address space was only half-exhausted. Bugfix
15843 - Correctly handle the case where AutomapHostsOnResolve is set but
15844 no virtual addresses are available. Fixes bug 2328; bugfix on
15845 0.1.2.1-alpha. Bug found by doorss.
15846 - Correctly handle wrapping around when we run out of virtual
15847 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
15849 o Minor features, also included in 0.2.1.29:
15850 - Update to the January 1 2011 Maxmind GeoLite Country database.
15851 - Introduce output size checks on all of our decryption functions.
15853 o Build changes, also included in 0.2.1.29:
15854 - Tor does not build packages correctly with Automake 1.6 and earlier;
15855 added a check to Makefile.am to make sure that we're building with
15856 Automake 1.7 or later.
15857 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
15858 because we built it with a too-old version of automake. Thus that
15859 release broke ./configure --enable-openbsd-malloc, which is popular
15860 among really fast exit relays on Linux.
15862 o Major bugfixes, new in 0.2.2.21-alpha:
15863 - Prevent crash/heap corruption when the cbtnummodes consensus
15864 parameter is set to 0 or large values. Fixes bug 2317; bugfix
15867 o Major features, new in 0.2.2.21-alpha:
15868 - Introduce minimum/maximum values that clients will believe
15869 from the consensus. Now we'll have a better chance to avoid crashes
15870 or worse when a consensus param has a weird value.
15872 o Minor features, new in 0.2.2.21-alpha:
15873 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
15874 used on bridges, and it makes bridge scanning somewhat easier.
15875 - If writing the state file to disk fails, wait up to an hour before
15876 retrying again, rather than trying again each second. Fixes bug
15877 2346; bugfix on Tor 0.1.1.3-alpha.
15878 - Make Libevent log messages get delivered to controllers later,
15879 and not from inside the Libevent log handler. This prevents unsafe
15880 reentrant Libevent calls while still letting the log messages
15882 - Detect platforms that brokenly use a signed size_t, and refuse to
15883 build there. Found and analyzed by doorss and rransom.
15884 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
15887 o Minor bugfixes, new in 0.2.2.21-alpha:
15888 - Handle SOCKS messages longer than 128 bytes long correctly, rather
15889 than waiting forever for them to finish. Fixes bug 2330; bugfix
15890 on 0.2.0.16-alpha. Found by doorss.
15891 - Add assertions to check for overflow in arguments to
15892 base32_encode() and base32_decode(); fix a signed-unsigned
15893 comparison there too. These bugs are not actually reachable in Tor,
15894 but it's good to prevent future errors too. Found by doorss.
15895 - Correctly detect failures to create DNS requests when using Libevent
15896 versions before v2. (Before Libevent 2, we used our own evdns
15897 implementation. Its return values for Libevent's evdns_resolve_*()
15898 functions are not consistent with those from Libevent.) Fixes bug
15899 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
15901 o Documentation, new in 0.2.2.21-alpha:
15902 - Document the default socks host and port (127.0.0.1:9050) for
15906 Changes in version 0.2.1.29 - 2011-01-15
15907 Tor 0.2.1.29 continues our recent code security audit work. The main
15908 fix resolves a remote heap overflow vulnerability that can allow remote
15909 code execution. Other fixes address a variety of assert and crash bugs,
15910 most of which we think are hard to exploit remotely.
15912 o Major bugfixes (security):
15913 - Fix a heap overflow bug where an adversary could cause heap
15914 corruption. This bug probably allows remote code execution
15915 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
15917 - Prevent a denial-of-service attack by disallowing any
15918 zlib-compressed data whose compression factor is implausibly
15919 high. Fixes part of bug 2324; reported by "doorss".
15920 - Zero out a few more keys in memory before freeing them. Fixes
15921 bug 2384 and part of bug 2385. These key instances found by
15922 "cypherpunks", based on Andrew Case's report about being able
15923 to find sensitive data in Tor's memory space if you have enough
15924 permissions. Bugfix on 0.0.2pre9.
15926 o Major bugfixes (crashes):
15927 - Prevent calls to Libevent from inside Libevent log handlers.
15928 This had potential to cause a nasty set of crashes, especially
15929 if running Libevent with debug logging enabled, and running
15930 Tor with a controller watching for low-severity log messages.
15931 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
15932 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
15933 underflow errors there too. Fixes the other part of bug 2324.
15934 - Fix a bug where we would assert if we ever had a
15935 cached-descriptors.new file (or another file read directly into
15936 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
15937 on 0.2.1.25. Found by doorss.
15938 - Fix some potential asserts and parsing issues with grossly
15939 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
15942 o Minor bugfixes (other):
15943 - Fix a bug with handling misformed replies to reverse DNS lookup
15944 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
15945 bug reported by doorss.
15946 - Fix compilation on mingw when a pthreads compatibility library
15947 has been installed. (We don't want to use it, so we shouldn't
15948 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
15949 - Fix a bug where we would declare that we had run out of virtual
15950 addresses when the address space was only half-exhausted. Bugfix
15952 - Correctly handle the case where AutomapHostsOnResolve is set but
15953 no virtual addresses are available. Fixes bug 2328; bugfix on
15954 0.1.2.1-alpha. Bug found by doorss.
15955 - Correctly handle wrapping around to when we run out of virtual
15956 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
15957 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
15958 because we built it with a too-old version of automake. Thus that
15959 release broke ./configure --enable-openbsd-malloc, which is popular
15960 among really fast exit relays on Linux.
15963 - Update to the January 1 2011 Maxmind GeoLite Country database.
15964 - Introduce output size checks on all of our decryption functions.
15967 - Tor does not build packages correctly with Automake 1.6 and earlier;
15968 added a check to Makefile.am to make sure that we're building with
15969 Automake 1.7 or later.
15972 Changes in version 0.2.2.20-alpha - 2010-12-17
15973 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
15974 exploitable bugs. We also fix a variety of other significant bugs,
15975 change the IP address for one of our directory authorities, and update
15976 the minimum version that Tor relays must run to join the network.
15979 - Fix a remotely exploitable bug that could be used to crash instances
15980 of Tor remotely by overflowing on the heap. Remote-code execution
15981 hasn't been confirmed, but can't be ruled out. Everyone should
15982 upgrade. Bugfix on the 0.1.1 series and later.
15983 - Fix a bug that could break accounting on 64-bit systems with large
15984 time_t values, making them hibernate for impossibly long intervals.
15985 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
15986 - Fix a logic error in directory_fetches_from_authorities() that
15987 would cause all _non_-exits refusing single-hop-like circuits
15988 to fetch from authorities, when we wanted to have _exits_ fetch
15989 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
15991 - Fix a stream fairness bug that would cause newer streams on a given
15992 circuit to get preference when reading bytes from the origin or
15993 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
15994 introduced before the first Tor release, in svn revision r152.
15996 o Directory authority changes:
15997 - Change IP address and ports for gabelmoo (v3 directory authority).
16000 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
16001 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
16002 - Fix an off-by-one error in calculating some controller command
16003 argument lengths. Fortunately, this mistake is harmless since
16004 the controller code does redundant NUL termination too. Found by
16005 boboper. Bugfix on 0.1.1.1-alpha.
16006 - Do not dereference NULL if a bridge fails to build its
16007 extra-info descriptor. Found by an anonymous commenter on
16008 Trac. Bugfix on 0.2.2.19-alpha.
16011 - Update to the December 1 2010 Maxmind GeoLite Country database.
16012 - Directory authorities now reject relays running any versions of
16013 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
16014 known bugs that keep RELAY_EARLY cells from working on rendezvous
16015 circuits. Followup to fix for bug 2081.
16016 - Directory authorities now reject relays running any version of Tor
16017 older than 0.2.0.26-rc. That version is the earliest that fetches
16018 current directory information correctly. Fixes bug 2156.
16019 - Report only the top 10 ports in exit-port stats in order not to
16020 exceed the maximum extra-info descriptor length of 50 KB. Implements
16024 Changes in version 0.2.1.28 - 2010-12-17
16025 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
16026 exploitable bugs. We also took this opportunity to change the IP address
16027 for one of our directory authorities, and to update the geoip database
16031 - Fix a remotely exploitable bug that could be used to crash instances
16032 of Tor remotely by overflowing on the heap. Remote-code execution
16033 hasn't been confirmed, but can't be ruled out. Everyone should
16034 upgrade. Bugfix on the 0.1.1 series and later.
16036 o Directory authority changes:
16037 - Change IP address and ports for gabelmoo (v3 directory authority).
16040 - Update to the December 1 2010 Maxmind GeoLite Country database.
16043 Changes in version 0.2.1.27 - 2010-11-23
16044 Yet another OpenSSL security patch broke its compatibility with Tor:
16045 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
16046 also took this opportunity to fix several crash bugs, integrate a new
16047 directory authority, and update the bundled GeoIP database.
16050 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
16051 No longer set the tlsext_host_name extension on server SSL objects;
16052 but continue to set it on client SSL objects. Our goal in setting
16053 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
16054 bugfix on 0.2.1.1-alpha.
16055 - Do not log messages to the controller while shrinking buffer
16056 freelists. Doing so would sometimes make the controller connection
16057 try to allocate a buffer chunk, which would mess up the internals
16058 of the freelist and cause an assertion failure. Fixes bug 1125;
16059 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
16060 - Learn our external IP address when we're a relay or bridge, even if
16061 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
16062 where we introduced bridge relays that don't need to publish to
16063 be useful. Fixes bug 2050.
16064 - Do even more to reject (and not just ignore) annotations on
16065 router descriptors received anywhere but from the cache. Previously
16066 we would ignore such annotations at first, but cache them to disk
16067 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
16068 - When you're using bridges and your network goes away and your
16069 bridges get marked as down, recover when you attempt a new socks
16070 connection (if the network is back), rather than waiting up to an
16071 hour to try fetching new descriptors for your bridges. Bugfix on
16072 0.2.0.3-alpha; fixes bug 1981.
16075 - Move to the November 2010 Maxmind GeoLite country db (rather
16076 than the June 2009 ip-to-country GeoIP db) for our statistics that
16077 count how many users relays are seeing from each country. Now we'll
16078 have more accurate data, especially for many African countries.
16080 o New directory authorities:
16081 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
16085 - Fix an assertion failure that could occur in directory caches or
16086 bridge users when using a very short voting interval on a testing
16087 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
16089 - Enforce multiplicity rules when parsing annotations. Bugfix on
16090 0.2.0.8-alpha. Found by piebeer.
16091 - Allow handshaking OR connections to take a full KeepalivePeriod
16092 seconds to handshake. Previously, we would close them after
16093 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
16094 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
16096 - When building with --enable-gcc-warnings on OpenBSD, disable
16097 warnings in system headers. This makes --enable-gcc-warnings
16098 pass on OpenBSD 4.8.
16101 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
16102 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
16103 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
16104 Servers can start sending this code when enough clients recognize
16105 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
16106 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
16107 Patch from mingw-san.
16110 - Remove the old debian/ directory from the main Tor distribution.
16111 The official Tor-for-debian git repository lives at the URL
16112 https://git.torproject.org/debian/tor.git
16113 - Stop shipping the old doc/website/ directory in the tarball. We
16114 changed the website format in late 2010, and what we shipped in
16115 0.2.1.26 really wasn't that useful anyway.
16118 Changes in version 0.2.2.19-alpha - 2010-11-22
16119 Yet another OpenSSL security patch broke its compatibility with Tor:
16120 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
16123 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
16124 No longer set the tlsext_host_name extension on server SSL objects;
16125 but continue to set it on client SSL objects. Our goal in setting
16126 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
16127 bugfix on 0.2.1.1-alpha.
16130 - Try harder not to exceed the maximum length of 50 KB when writing
16131 statistics to extra-info descriptors. This bug was triggered by very
16132 fast relays reporting exit-port, entry, and dirreq statistics.
16133 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
16134 - Publish a router descriptor even if generating an extra-info
16135 descriptor fails. Previously we would not publish a router
16136 descriptor without an extra-info descriptor; this can cause fast
16137 exit relays collecting exit-port statistics to drop from the
16138 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
16141 Changes in version 0.2.2.18-alpha - 2010-11-16
16142 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
16143 us lately, makes unpublished bridge relays able to detect their IP
16144 address, and fixes a wide variety of other bugs to get us much closer
16145 to a stable release.
16148 - Do even more to reject (and not just ignore) annotations on
16149 router descriptors received anywhere but from the cache. Previously
16150 we would ignore such annotations at first, but cache them to disk
16151 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
16152 - Do not log messages to the controller while shrinking buffer
16153 freelists. Doing so would sometimes make the controller connection
16154 try to allocate a buffer chunk, which would mess up the internals
16155 of the freelist and cause an assertion failure. Fixes bug 1125;
16156 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
16157 - Learn our external IP address when we're a relay or bridge, even if
16158 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
16159 where we introduced bridge relays that don't need to publish to
16160 be useful. Fixes bug 2050.
16161 - Maintain separate TLS contexts and certificates for incoming and
16162 outgoing connections in bridge relays. Previously we would use the
16163 same TLS contexts and certs for incoming and outgoing connections.
16164 Bugfix on 0.2.0.3-alpha; addresses bug 988.
16165 - Maintain separate identity keys for incoming and outgoing TLS
16166 contexts in bridge relays. Previously we would use the same
16167 identity keys for incoming and outgoing TLS contexts. Bugfix on
16168 0.2.0.3-alpha; addresses the other half of bug 988.
16169 - Avoid an assertion failure when we as an authority receive a
16170 duplicate upload of a router descriptor that we already have,
16171 but which we previously considered an obsolete descriptor.
16172 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
16173 - Avoid a crash bug triggered by looking at a dangling pointer while
16174 setting the network status consensus. Found by Robert Ransom.
16175 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
16176 - Fix a logic error where servers that _didn't_ act as exits would
16177 try to keep their server lists more aggressively up to date than
16178 exits, when it was supposed to be the other way around. Bugfix
16181 o Minor bugfixes (on Tor 0.2.1.x and earlier):
16182 - When we're trying to guess whether we know our IP address as
16183 a relay, we would log various ways that we failed to guess
16184 our address, but never log that we ended up guessing it
16185 successfully. Now add a log line to help confused and anxious
16186 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
16187 - Bring the logic that gathers routerinfos and assesses the
16188 acceptability of circuits into line. This prevents a Tor OP from
16189 getting locked in a cycle of choosing its local OR as an exit for a
16190 path (due to a .exit request) and then rejecting the circuit because
16191 its OR is not listed yet. It also prevents Tor clients from using an
16192 OR running in the same instance as an exit (due to a .exit request)
16193 if the OR does not meet the same requirements expected of an OR
16194 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
16195 - Correctly describe errors that occur when generating a TLS object.
16196 Previously we would attribute them to a failure while generating a
16197 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
16199 - Enforce multiplicity rules when parsing annotations. Bugfix on
16200 0.2.0.8-alpha. Found by piebeer.
16201 - Fix warnings that newer versions of autoconf produced during
16202 ./autogen.sh. These warnings appear to be harmless in our case,
16203 but they were extremely verbose. Fixes bug 2020.
16205 o Minor bugfixes (on Tor 0.2.2.x):
16206 - Enable protection of small arrays whenever we build with gcc
16207 hardening features, not only when also building with warnings
16208 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
16211 - Make hidden services work better in private Tor networks by not
16212 requiring any uptime to join the hidden service descriptor
16213 DHT. Implements ticket 2088.
16214 - Rate-limit the "your application is giving Tor only an IP address"
16215 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
16216 - When AllowSingleHopExits is set, print a warning to explain to the
16217 relay operator why most clients are avoiding her relay.
16218 - Update to the November 1 2010 Maxmind GeoLite Country database.
16220 o Code simplifications and refactoring:
16221 - When we fixed bug 1038 we had to put in a restriction not to send
16222 RELAY_EARLY cells on rend circuits. This was necessary as long
16223 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
16224 active. Now remove this obsolete check. Resolves bug 2081.
16225 - Some options used different conventions for uppercasing of acronyms
16226 when comparing manpage and source. Fix those in favor of the
16227 manpage, as it makes sense to capitalize acronyms.
16228 - Remove the torrc.complete file. It hasn't been kept up to date
16229 and users will have better luck checking out the manpage.
16230 - Remove the obsolete "NoPublish" option; it has been flagged
16231 as obsolete and has produced a warning since 0.1.1.18-rc.
16232 - Remove everything related to building the expert bundle for OS X.
16233 It has confused many users, doesn't work right on OS X 10.6,
16234 and is hard to get rid of once installed. Resolves bug 1274.
16237 Changes in version 0.2.2.17-alpha - 2010-09-30
16238 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
16239 to use one-hop circuits (which can put the exit relays at higher risk,
16240 plus unbalance the network); fixes a big bug in bandwidth accounting
16241 for relays that want to limit their monthly bandwidth use; fixes a
16242 big pile of bugs in how clients tolerate temporary network failure;
16243 and makes our adaptive circuit build timeout feature (which improves
16244 client performance if your network is fast while not breaking things
16245 if your network is slow) better handle bad networks.
16248 - Exit relays now try harder to block exit attempts from unknown
16249 relays, to make it harder for people to use them as one-hop proxies
16250 a la tortunnel. Controlled by the refuseunknownexits consensus
16251 parameter (currently enabled), or you can override it on your
16252 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
16254 o Major bugfixes (0.2.1.x and earlier):
16255 - Fix a bug in bandwidth accounting that could make us use twice
16256 the intended bandwidth when our interval start changes due to
16257 daylight saving time. Now we tolerate skew in stored vs computed
16258 interval starts: if the start of the period changes by no more than
16259 50% of the period's duration, we remember bytes that we transferred
16260 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
16261 - Always search the Windows system directory for system DLLs, and
16262 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
16263 - When you're using bridges and your network goes away and your
16264 bridges get marked as down, recover when you attempt a new socks
16265 connection (if the network is back), rather than waiting up to an
16266 hour to try fetching new descriptors for your bridges. Bugfix on
16267 0.2.0.3-alpha; fixes bug 1981.
16269 o Major bugfixes (on 0.2.2.x):
16270 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
16272 - Fix a segfault that could happen when operating a bridge relay with
16273 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
16274 - The consensus bandwidth-weights (used by clients to choose fast
16275 relays) entered an unexpected edge case in September where
16276 Exits were much scarcer than Guards, resulting in bad weight
16277 recommendations. Now we compute them using new constraints that
16278 should succeed in all cases. Also alter directory authorities to
16279 not include the bandwidth-weights line if they fail to produce
16280 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
16281 - When weighting bridges during path selection, we used to trust
16282 the bandwidths they provided in their descriptor, only capping them
16283 at 10MB/s. This turned out to be problematic for two reasons:
16284 Bridges could claim to handle a lot more traffic then they
16285 actually would, thus making more clients pick them and have a
16286 pretty effective DoS attack. The other issue is that new bridges
16287 that might not have a good estimate for their bw capacity yet
16288 would not get used at all unless no other bridges are available
16289 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
16291 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
16292 - Ignore cannibalized circuits when recording circuit build times.
16293 This should provide for a minor performance improvement for hidden
16294 service users using 0.2.2.14-alpha, and should remove two spurious
16295 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
16296 - Simplify the logic that causes us to decide if the network is
16297 unavailable for purposes of recording circuit build times. If we
16298 receive no cells whatsoever for the entire duration of a circuit's
16299 full measured lifetime, the network is probably down. Also ignore
16300 one-hop directory fetching circuit timeouts when calculating our
16301 circuit build times. These changes should hopefully reduce the
16302 cases where we see ridiculous circuit build timeouts for people
16303 with spotty wireless connections. Fixes part of bug 1772; bugfix
16305 - Prevent the circuit build timeout from becoming larger than
16306 the maximum build time we have ever seen. Also, prevent the time
16307 period for measurement circuits from becoming larger than twice that
16308 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
16311 - When we run out of directory information such that we can't build
16312 circuits, but then get enough that we can build circuits, log when
16313 we actually construct a circuit, so the user has a better chance of
16314 knowing what's going on. Fixes bug 1362.
16315 - Be more generous with how much bandwidth we'd use up (with
16316 accounting enabled) before entering "soft hibernation". Previously,
16317 we'd refuse new connections and circuits once we'd used up 95% of
16318 our allotment. Now, we use up 95% of our allotment, AND make sure
16319 that we have no more than 500MB (or 3 hours of expected traffic,
16320 whichever is lower) remaining before we enter soft hibernation.
16321 - If we've configured EntryNodes and our network goes away and/or all
16322 our entrynodes get marked down, optimistically retry them all when
16323 a new socks application request appears. Fixes bug 1882.
16324 - Add some more defensive programming for architectures that can't
16325 handle unaligned integer accesses. We don't know of any actual bugs
16326 right now, but that's the best time to fix them. Fixes bug 1943.
16327 - Support line continuations in the torrc config file. If a line
16328 ends with a single backslash character, the newline is ignored, and
16329 the configuration value is treated as continuing on the next line.
16332 o Minor bugfixes (on 0.2.1.x and earlier):
16333 - For bandwidth accounting, calculate our expected bandwidth rate
16334 based on the time during which we were active and not in
16335 soft-hibernation during the last interval. Previously, we were
16336 also considering the time spent in soft-hibernation. If this
16337 was a long time, we would wind up underestimating our bandwidth
16338 by a lot, and skewing our wakeup time towards the start of the
16339 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
16341 o Minor bugfixes (on 0.2.2.x):
16342 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
16343 which were disabled by the circuit build timeout changes in
16344 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
16345 - Make sure we don't warn about missing bandwidth weights when
16346 choosing bridges or other relays not in the consensus. Bugfix on
16347 0.2.2.10-alpha; fixes bug 1805.
16348 - In our logs, do not double-report signatures from unrecognized
16349 authorities both as "from unknown authority" and "not
16350 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
16353 Changes in version 0.2.2.16-alpha - 2010-09-17
16354 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
16355 evident at exit relays), and also continues to resolve all the little
16356 bugs that have been filling up trac lately.
16358 o Major bugfixes (stream-level fairness):
16359 - When receiving a circuit-level SENDME for a blocked circuit, try
16360 to package cells fairly from all the streams that had previously
16361 been blocked on that circuit. Previously, we had started with the
16362 oldest stream, and allowed each stream to potentially exhaust
16363 the circuit's package window. This gave older streams on any
16364 given circuit priority over newer ones. Fixes bug 1937. Detected
16365 originally by Camilo Viecco. This bug was introduced before the
16366 first Tor release, in svn commit r152: it is the new winner of
16367 the longest-lived bug prize.
16368 - When the exit relay got a circuit-level sendme cell, it started
16369 reading on the exit streams, even if had 500 cells queued in the
16370 circuit queue already, so the circuit queue just grew and grew in
16371 some cases. We fix this by not re-enabling reading on receipt of a
16372 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
16373 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
16375 - Newly created streams were allowed to read cells onto circuits,
16376 even if the circuit's cell queue was blocked and waiting to drain.
16377 This created potential unfairness, as older streams would be
16378 blocked, but newer streams would gladly fill the queue completely.
16379 We add code to detect this situation and prevent any stream from
16380 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
16384 - Update to the September 1 2010 Maxmind GeoLite Country database.
16385 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
16386 not. This would lead to a cookie that is still not group readable.
16387 Closes bug 1843. Suggested by katmagic.
16388 - When logging a rate-limited warning, we now mention how many messages
16389 got suppressed since the last warning.
16390 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
16391 do individual connection-level rate limiting of clients. The torrc
16392 config options with the same names trump the consensus params, if
16393 both are present. Replaces the old "bwconnrate" and "bwconnburst"
16394 consensus params which were broken from 0.2.2.7-alpha through
16395 0.2.2.14-alpha. Closes bug 1947.
16396 - When a router changes IP address or port, authorities now launch
16397 a new reachability test for it. Implements ticket 1899.
16398 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
16399 2 no signature, 4 required" messages about consensus signatures
16400 easier to read, and make sure they get logged at the same severity
16401 as the messages explaining which keys are which. Fixes bug 1290.
16402 - Don't warn when we have a consensus that we can't verify because
16403 of missing certificates, unless those certificates are ones
16404 that we have been trying and failing to download. Fixes bug 1145.
16405 - If you configure your bridge with a known identity fingerprint,
16406 and the bridge authority is unreachable (as it is in at least
16407 one country now), fall back to directly requesting the descriptor
16408 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
16410 - When building with --enable-gcc-warnings on OpenBSD, disable
16411 warnings in system headers. This makes --enable-gcc-warnings
16412 pass on OpenBSD 4.8.
16414 o Minor bugfixes (on 0.2.1.x and earlier):
16415 - Authorities will now attempt to download consensuses if their
16416 own efforts to make a live consensus have failed. This change
16417 means authorities that restart will fetch a valid consensus, and
16418 it means authorities that didn't agree with the current consensus
16419 will still fetch and serve it if it has enough signatures. Bugfix
16420 on 0.2.0.9-alpha; fixes bug 1300.
16421 - Ensure DNS requests launched by "RESOLVE" commands from the
16422 controller respect the __LeaveStreamsUnattached setconf options. The
16423 same goes for requests launched via DNSPort or transparent
16424 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
16425 - Allow handshaking OR connections to take a full KeepalivePeriod
16426 seconds to handshake. Previously, we would close them after
16427 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
16428 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
16430 - Rate-limit "Failed to hand off onionskin" warnings.
16431 - Never relay a cell for a circuit we have already destroyed.
16432 Between marking a circuit as closeable and finally closing it,
16433 it may have been possible for a few queued cells to get relayed,
16434 even though they would have been immediately dropped by the next
16435 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
16436 - Never queue a cell for a circuit that's already been marked
16438 - Never vote for a server as "Running" if we have a descriptor for
16439 it claiming to be hibernating, and that descriptor was published
16440 more recently than our last contact with the server. Bugfix on
16441 0.2.0.3-alpha; fixes bug 911.
16442 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
16445 o Minor bugfixes (on 0.2.2.x):
16446 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
16447 down if a directory fetch fails and you've configured either
16448 bridges or EntryNodes. The intent was to mark the relay as down
16449 _unless_ you're using bridges or EntryNodes, since if you are
16450 then you could quickly run out of entry points.
16451 - Fix the Windows directory-listing code. A bug introduced in
16452 0.2.2.14-alpha could make Windows directory servers forget to load
16453 some of their cached v2 networkstatus files.
16454 - Really allow clients to use relays as bridges. Fixes bug 1776;
16455 bugfix on 0.2.2.15-alpha.
16456 - Demote a warn to info that happens when the CellStatistics option
16457 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
16458 Reported by Moritz Bartl.
16459 - On Windows, build correctly either with or without Unicode support.
16460 This is necessary so that Tor can support fringe platforms like
16461 Windows 98 (which has no Unicode), or Windows CE (which has no
16462 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
16465 - Add a unit test for cross-platform directory-listing code.
16468 Changes in version 0.2.2.15-alpha - 2010-08-18
16469 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
16470 fixes a variety of other bugs that were preventing performance
16471 experiments from moving forward, fixes several bothersome memory leaks,
16472 and generally closes a lot of smaller bugs that have been filling up
16476 - Stop assigning the HSDir flag to relays that disable their
16477 DirPort (and thus will refuse to answer directory requests). This
16478 fix should dramatically improve the reachability of hidden services:
16479 hidden services and hidden service clients pick six HSDir relays
16480 to store and retrieve the hidden service descriptor, and currently
16481 about half of the HSDir relays will refuse to work. Bugfix on
16482 0.2.0.10-alpha; fixes part of bug 1693.
16483 - The PerConnBWRate and Burst config options, along with the
16484 bwconnrate and bwconnburst consensus params, initialized each conn's
16485 token bucket values only when the connection is established. Now we
16486 update them if the config options change, and update them every time
16487 we get a new consensus. Otherwise we can encounter an ugly edge
16488 case where we initialize an OR conn to client-level bandwidth,
16489 but then later the relay joins the consensus and we leave it
16490 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
16491 - Fix a regression that caused Tor to rebind its ports if it receives
16492 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
16495 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
16496 should give us approximately 40-50% more Guard-flagged nodes,
16497 improving the anonymity the Tor network can provide and also
16498 decreasing the dropoff in throughput that relays experience when
16499 they first get the Guard flag.
16500 - Allow enabling or disabling the *Statistics config options while
16504 - Update to the August 1 2010 Maxmind GeoLite Country database.
16505 - Have the controller interface give a more useful message than
16506 "Internal Error" in response to failed GETINFO requests.
16507 - Warn when the same option is provided more than once in a torrc
16508 file, on the command line, or in a single SETCONF statement, and
16509 the option is one that only accepts a single line. Closes bug 1384.
16510 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
16511 Patch from mingw-san.
16512 - Add support for the country code "{??}" in torrc options like
16513 ExcludeNodes, to indicate all routers of unknown country. Closes
16515 - Relays report the number of bytes spent on answering directory
16516 requests in extra-info descriptors similar to {read,write}-history.
16517 Implements enhancement 1790.
16519 o Minor bugfixes (on 0.2.1.x and earlier):
16520 - Complain if PublishServerDescriptor is given multiple arguments that
16521 include 0 or 1. This configuration will be rejected in the future.
16522 Bugfix on 0.2.0.1-alpha; closes bug 1107.
16523 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
16524 Bugfix on 0.2.0.13-alpha; closes bug 928.
16525 - Change "Application request when we're believed to be offline."
16526 notice to "Application request when we haven't used client
16527 functionality lately.", to clarify that it's not an error. Bugfix
16528 on 0.0.9.3; fixes bug 1222.
16529 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
16530 would return "551 Internal error" rather than "552 Unrecognized key
16531 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
16532 - Users can't configure a regular relay to be their bridge. It didn't
16533 work because when Tor fetched the bridge descriptor, it found
16534 that it already had it, and didn't realize that the purpose of the
16535 descriptor had changed. Now we replace routers with a purpose other
16536 than bridge with bridge descriptors when fetching them. Bugfix on
16537 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
16538 refetch the descriptor with router purpose 'general', disabling
16540 - Fix a rare bug in rend_fn unit tests: we would fail a test when
16541 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
16542 on 0.2.0.10-alpha; fixes bug 1808.
16543 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
16544 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
16545 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
16546 Servers can start sending this code when enough clients recognize
16547 it. Also update the spec to reflect this new reason. Bugfix on
16548 0.1.0.1-rc; fixes part of bug 1793.
16549 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
16550 when we switch from being a public relay to a bridge. Otherwise
16551 there will still be clients that see the relay in their consensus,
16552 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
16554 - Instead of giving an assertion failure on an internal mismatch
16555 on estimated freelist size, just log a BUG warning and try later.
16556 Mitigates but does not fix bug 1125.
16557 - Fix an assertion failure that could occur in caches or bridge users
16558 when using a very short voting interval on a testing network.
16559 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
16561 o Minor bugfixes (on 0.2.2.x):
16562 - Alter directory authorities to always consider Exit-flagged nodes
16563 as potential Guard nodes in their votes. The actual decision to
16564 use Exits as Guards is done in the consensus bandwidth weights.
16565 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
16566 - When the controller is reporting the purpose of circuits that
16567 didn't finish building before the circuit build timeout, it was
16568 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
16569 - Our libevent version parsing code couldn't handle versions like
16570 1.4.14b-stable and incorrectly warned the user about using an
16571 old and broken version of libevent. Treat 1.4.14b-stable like
16572 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
16574 - Don't use substitution references like $(VAR:MOD) when
16575 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
16576 '$(:x)' to 'x' rather than the empty string. This bites us in
16577 doc/ when configured with --disable-asciidoc. Bugfix on
16578 0.2.2.9-alpha; fixes bug 1773.
16579 - Remove a spurious hidden service server-side log notice about
16580 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
16582 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
16584 - Correctly report written bytes on linked connections. Found while
16585 implementing 1790. Bugfix on 0.2.2.4-alpha.
16586 - Fix three memory leaks: one in circuit_build_times_parse_state(),
16587 one in dirvote_add_signatures_to_pending_consensus(), and one every
16588 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
16589 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
16591 o Code simplifications and refactoring:
16592 - Take a first step towards making or.h smaller by splitting out
16593 function definitions for all source files in src/or/. Leave
16594 structures and defines in or.h for now.
16595 - Remove a bunch of unused function declarations as well as a block of
16596 #if 0'd code from the unit tests. Closes bug 1824.
16597 - New unit tests for exit-port history statistics; refactored exit
16598 statistics code to be more easily tested.
16599 - Remove the old debian/ directory from the main Tor distribution.
16600 The official Tor-for-debian git repository lives at the URL
16601 https://git.torproject.org/debian/tor.git
16604 Changes in version 0.2.2.14-alpha - 2010-07-12
16605 Tor 0.2.2.14-alpha greatly improves client-side handling of
16606 circuit build timeouts, which are used to estimate speed and improve
16607 performance. We also move to a much better GeoIP database, port Tor to
16608 Windows CE, introduce new compile flags that improve code security,
16609 add an eighth v3 directory authority, and address a lot of more
16613 - Tor directory authorities no longer crash when started with a
16614 cached-microdesc-consensus file in their data directory. Bugfix
16615 on 0.2.2.6-alpha; fixes bug 1532.
16616 - Treat an unset $HOME like an empty $HOME rather than triggering an
16617 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
16618 - Ignore negative and large circuit build timeout values that can
16619 happen during a suspend or hibernate. These values caused various
16620 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
16621 - Alter calculation of Pareto distribution parameter 'Xm' for
16622 Circuit Build Timeout learning to use the weighted average of the
16623 top N=3 modes (because we have three entry guards). Considering
16624 multiple modes should improve the timeout calculation in some cases,
16625 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
16627 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
16628 right censored distribution model. This approach improves over the
16629 synthetic timeout generation approach that was producing insanely
16630 high timeout values. Now we calculate build timeouts using truncated
16631 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
16632 - Do not close circuits that are under construction when they reach
16633 the circuit build timeout. Instead, leave them building (but do not
16634 use them) for up until the time corresponding to the 95th percentile
16635 on the Pareto CDF or 60 seconds, whichever is greater. This is done
16636 to provide better data for the new Pareto model. This percentile
16637 can be controlled by the consensus.
16640 - Move to the June 2010 Maxmind GeoLite country db (rather than the
16641 June 2009 ip-to-country GeoIP db) for our statistics that count
16642 how many users relays are seeing from each country. Now we have
16643 more accurate data for many African countries.
16644 - Port Tor to build and run correctly on Windows CE systems, using
16645 the wcecompat library. Contributed by Valerio Lupi.
16646 - New "--enable-gcc-hardening" ./configure flag (off by default)
16647 to turn on gcc compile time hardening options. It ensures
16648 that signed ints have defined behavior (-fwrapv), enables
16649 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
16650 with canaries (-fstack-protector-all), turns on ASLR protection if
16651 supported by the kernel (-fPIE, -pie), and adds additional security
16652 related warnings. Verified to work on Mac OS X and Debian Lenny.
16653 - New "--enable-linker-hardening" ./configure flag (off by default)
16654 to turn on ELF specific hardening features (relro, now). This does
16655 not work with Mac OS X or any other non-ELF binary format.
16657 o New directory authorities:
16658 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
16662 - New config option "WarnUnsafeSocks 0" disables the warning that
16663 occurs whenever Tor receives a socks handshake using a version of
16664 the socks protocol that can only provide an IP address (rather
16665 than a hostname). Setups that do DNS locally over Tor are fine,
16666 and we shouldn't spam the logs in that case.
16667 - Convert the HACKING file to asciidoc, and add a few new sections
16668 to it, explaining how we use Git, how we make changelogs, and
16669 what should go in a patch.
16670 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
16671 event, to give information on the current rate of circuit timeouts
16672 over our stored history.
16673 - Add ability to disable circuit build time learning via consensus
16674 parameter and via a LearnCircuitBuildTimeout config option. Also
16675 automatically disable circuit build time calculation if we are
16676 either a AuthoritativeDirectory, or if we fail to write our state
16677 file. Fixes bug 1296.
16678 - More gracefully handle corrupt state files, removing asserts
16679 in favor of saving a backup and resetting state.
16680 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
16684 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
16686 - When a2x fails, mention that the user could disable manpages instead
16687 of trying to fix their asciidoc installation.
16688 - Where available, use Libevent 2.0's periodic timers so that our
16689 once-per-second cleanup code gets called even more closely to
16690 once per second than it would otherwise. Fixes bug 943.
16691 - If you run a bridge that listens on multiple IP addresses, and
16692 some user configures a bridge address that uses a different IP
16693 address than your bridge writes in its router descriptor, and the
16694 user doesn't specify an identity key, their Tor would discard the
16695 descriptor because "it isn't one of our configured bridges", and
16696 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
16697 Bugfix on 0.2.0.3-alpha.
16698 - If OpenSSL fails to make a duplicate of a private or public key, log
16699 an error message and try to exit cleanly. May help with debugging
16700 if bug 1209 ever remanifests.
16701 - Save a couple bytes in memory allocation every time we escape
16702 certain characters in a string. Patch from Florian Zumbiehl.
16703 - Make it explicit that we don't cannibalize one-hop circuits. This
16704 happens in the wild, but doesn't turn out to be a problem because
16705 we fortunately don't use those circuits. Many thanks to outofwords
16706 for the initial analysis and to swissknife who confirmed that
16707 two-hop circuits are actually created.
16708 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
16709 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
16710 - Eliminate a case where a circuit build time warning was displayed
16711 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
16714 Changes in version 0.2.1.26 - 2010-05-02
16715 Tor 0.2.1.26 addresses the recent connection and memory overload
16716 problems we've been seeing on relays, especially relays with their
16717 DirPort open. If your relay has been crashing, or you turned it off
16718 because it used too many resources, give this release a try.
16720 This release also fixes yet another instance of broken OpenSSL libraries
16721 that was causing some relays to drop out of the consensus.
16724 - Teach relays to defend themselves from connection overload. Relays
16725 now close idle circuits early if it looks like they were intended
16726 for directory fetches. Relays are also more aggressive about closing
16727 TLS connections that have no circuits on them. Such circuits are
16728 unlikely to be re-used, and tens of thousands of them were piling
16729 up at the fast relays, causing the relays to run out of sockets
16730 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
16731 their directory fetches over TLS).
16732 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
16733 that claim to be earlier than 0.9.8m, but which have in reality
16734 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
16735 behavior. Possible fix for some cases of bug 1346.
16736 - Directory mirrors were fetching relay descriptors only from v2
16737 directory authorities, rather than v3 authorities like they should.
16738 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
16739 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
16742 - Finally get rid of the deprecated and now harmful notion of "clique
16743 mode", where directory authorities maintain TLS connections to
16747 - In the util/threads test, no longer free the test_mutex before all
16748 worker threads have finished. Bugfix on 0.2.1.6-alpha.
16749 - The master thread could starve the worker threads quite badly on
16750 certain systems, causing them to run only partially in the allowed
16751 window. This resulted in test failures. Now the master thread sleeps
16752 occasionally for a few microseconds while the two worker-threads
16753 compete for the mutex. Bugfix on 0.2.0.1-alpha.
16756 Changes in version 0.2.2.13-alpha - 2010-04-24
16757 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
16758 problems we've been seeing on relays, especially relays with their
16759 DirPort open. If your relay has been crashing, or you turned it off
16760 because it used too many resources, give this release a try.
16763 - Teach relays to defend themselves from connection overload. Relays
16764 now close idle circuits early if it looks like they were intended
16765 for directory fetches. Relays are also more aggressive about closing
16766 TLS connections that have no circuits on them. Such circuits are
16767 unlikely to be re-used, and tens of thousands of them were piling
16768 up at the fast relays, causing the relays to run out of sockets
16769 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
16770 their directory fetches over TLS).
16773 - Finally get rid of the deprecated and now harmful notion of "clique
16774 mode", where directory authorities maintain TLS connections to
16776 - Directory authorities now do an immediate reachability check as soon
16777 as they hear about a new relay. This change should slightly reduce
16778 the time between setting up a relay and getting listed as running
16779 in the consensus. It should also improve the time between setting
16780 up a bridge and seeing use by bridge users.
16781 - Directory authorities no longer launch a TLS connection to every
16782 relay as they startup. Now that we have 2k+ descriptors cached,
16783 the resulting network hiccup is becoming a burden. Besides,
16784 authorities already avoid voting about Running for the first half
16785 hour of their uptime.
16788 Changes in version 0.2.2.12-alpha - 2010-04-20
16789 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
16790 handle and vote on descriptors. It was causing relays to drop out of
16794 - Many relays have been falling out of the consensus lately because
16795 not enough authorities know about their descriptor for them to get
16796 a majority of votes. When we deprecated the v2 directory protocol,
16797 we got rid of the only way that v3 authorities can hear from each
16798 other about other descriptors. Now authorities examine every v3
16799 vote for new descriptors, and fetch them from that authority. Bugfix
16801 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
16802 and a warning in or.h related to bandwidth_weight_rule_t that
16803 prevented clean compile on OS X. Fixes bug 1363; bugfix on
16805 - Fix a segfault on relays when DirReqStatistics is enabled
16806 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
16810 - Demote a confusing TLS warning that relay operators might get when
16811 someone tries to talk to their OrPort. It is neither the operator's
16812 fault nor can they do anything about it. Fixes bug 1364; bugfix
16816 Changes in version 0.2.2.11-alpha - 2010-04-15
16817 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
16818 libraries that was causing some relays to drop out of the consensus.
16821 - Directory mirrors were fetching relay descriptors only from v2
16822 directory authorities, rather than v3 authorities like they should.
16823 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
16824 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
16825 - Fix a parsing error that made every possible value of
16826 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
16827 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
16828 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
16829 about the option without breaking older ones.
16830 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
16831 that claim to be earlier than 0.9.8m, but which have in reality
16832 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
16833 behavior. Possible fix for some cases of bug 1346.
16836 - Experiment with a more aggressive approach to preventing clients
16837 from making one-hop exit streams. Exit relays who want to try it
16838 out can set "RefuseUnknownExits 1" in their torrc, and then look
16839 for "Attempt by %s to open a stream" log messages. Let us know
16841 - Add support for statically linking zlib by specifying
16842 --enable-static-zlib, to go with our support for statically linking
16843 openssl and libevent. Resolves bug 1358.
16846 - Fix a segfault that happens whenever a Tor client that is using
16847 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
16849 - When we cleaned up the contrib/tor-exit-notice.html file, we left
16850 out the first line. Fixes bug 1295.
16851 - When building the manpage from a tarball, we required asciidoc, but
16852 the asciidoc -> roff/html conversion was already done for the
16853 tarball. Make 'make' complain only when we need asciidoc (either
16854 because we're compiling directly from git, or because we altered
16855 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
16856 - When none of the directory authorities vote on any params, Tor
16857 segfaulted when trying to make the consensus from the votes. We
16858 didn't trigger the bug in practice, because authorities do include
16859 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
16862 - In the util/threads test, no longer free the test_mutex before all
16863 worker threads have finished. Bugfix on 0.2.1.6-alpha.
16864 - The master thread could starve the worker threads quite badly on
16865 certain systems, causing them to run only partially in the allowed
16866 window. This resulted in test failures. Now the master thread sleeps
16867 occasionally for a few microseconds while the two worker-threads
16868 compete for the mutex. Bugfix on 0.2.0.1-alpha.
16871 Changes in version 0.2.2.10-alpha - 2010-03-07
16872 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
16873 could prevent relays from guessing their IP address correctly. It also
16874 starts the groundwork for another client-side performance boost, since
16875 currently we're not making efficient use of relays that have both the
16876 Guard flag and the Exit flag.
16879 - Fix a regression from our patch for bug 1244 that caused relays
16880 to guess their IP address incorrectly if they didn't set Address
16881 in their torrc and/or their address fails to resolve. Bugfix on
16882 0.2.2.9-alpha; fixes bug 1269.
16884 o Major features (performance):
16885 - Directory authorities now compute consensus weightings that instruct
16886 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
16887 and no flag. Clients that use these weightings will distribute
16888 network load more evenly across these different relay types. The
16889 weightings are in the consensus so we can change them globally in
16890 the future. Extra thanks to "outofwords" for finding some nasty
16891 security bugs in the first implementation of this feature.
16893 o Minor features (performance):
16894 - Always perform router selections using weighted relay bandwidth,
16895 even if we don't need a high capacity circuit at the time. Non-fast
16896 circuits now only differ from fast ones in that they can use relays
16897 not marked with the Fast flag. This "feature" could turn out to
16898 be a horrible bug; we should investigate more before it goes into
16902 - Allow disabling building of the manpages. Skipping the manpage
16903 speeds up the build considerably.
16905 o Minor bugfixes (on 0.2.2.x):
16906 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
16907 Bugfix on 0.2.2.9-alpha.
16908 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
16909 config option. Bugfix on 0.2.2.7-alpha.
16910 - Ship the asciidoc-helper file in the tarball, so that people can
16911 build from source if they want to, and touching the .1.txt files
16912 doesn't break the build. Bugfix on 0.2.2.9-alpha.
16914 o Minor bugfixes (on 0.2.1.x or earlier):
16915 - Fix a dereference-then-NULL-check sequence when publishing
16916 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
16918 - Fix another dereference-then-NULL-check sequence. Bugfix on
16919 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
16920 - Make sure we treat potentially not NUL-terminated strings correctly.
16921 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
16923 o Code simplifications and refactoring:
16924 - Fix some urls in the exit notice file and make it XHTML1.1 strict
16925 compliant. Based on a patch from Christian Kujau.
16926 - Don't use sed in asciidoc-helper anymore.
16927 - Make the build process fail if asciidoc cannot be found and
16928 building with asciidoc isn't disabled.
16931 Changes in version 0.2.2.9-alpha - 2010-02-22
16932 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
16933 location of a directory authority, and cleans up a bunch of small bugs.
16935 o Directory authority changes:
16936 - Change IP address for dannenberg (v3 directory authority), and
16937 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
16938 service directory authority) from the list.
16941 - Make Tor work again on the latest OS X: when deciding whether to
16942 use strange flags to turn TLS renegotiation on, detect the OpenSSL
16943 version at run-time, not compile time. We need to do this because
16944 Apple doesn't update its dev-tools headers when it updates its
16945 libraries in a security patch.
16946 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
16947 that could happen on 32-bit platforms with 64-bit time_t. Also fix
16948 a memory leak when requesting a hidden service descriptor we've
16949 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
16951 - Authorities could be tricked into giving out the Exit flag to relays
16952 that didn't allow exiting to any ports. This bug could screw
16953 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
16954 1238. Bug discovered by Martin Kowalczyk.
16955 - When freeing a session key, zero it out completely. We only zeroed
16956 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
16957 patched by ekir. Fixes bug 1254.
16960 - Fix static compilation by listing the openssl libraries in the right
16961 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
16962 - Resume handling .exit hostnames in a special way: originally we
16963 stripped the .exit part and used the requested exit relay. In
16964 0.2.2.1-alpha we stopped treating them in any special way, meaning
16965 if you use a .exit address then Tor will pass it on to the exit
16966 relay. Now we reject the .exit stream outright, since that behavior
16967 might be more expected by the user. Found and diagnosed by Scott
16968 Bennett and Downie on or-talk.
16969 - Don't spam the controller with events when we have no file
16970 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
16971 for log messages was already solved from bug 748.)
16972 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
16974 - Make the DNSPort option work with libevent 2.x. Don't alter the
16975 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
16976 - Emit a GUARD DROPPED controller event for a case we missed.
16977 - Make more fields in the controller protocol case-insensitive, since
16978 control-spec.txt said they were.
16979 - Refactor resolve_my_address() to not use gethostbyname() anymore.
16980 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
16981 - Fix a spec conformance issue: the network-status-version token
16982 must be the first token in a v3 consensus or vote. Discovered by
16983 parakeep. Bugfix on 0.2.0.3-alpha.
16985 o Code simplifications and refactoring:
16986 - Generate our manpage and HTML documentation using Asciidoc. This
16987 change should make it easier to maintain the documentation, and
16988 produce nicer HTML.
16989 - Remove the --enable-iphone option. According to reports from Marco
16990 Bonetti, Tor builds fine without any special tweaking on recent
16991 iPhone SDK versions.
16992 - Removed some unnecessary files from the source distribution. The
16993 AUTHORS file has now been merged into the people page on the
16994 website. The roadmaps and design doc can now be found in the
16995 projects directory in svn.
16996 - Enabled various circuit build timeout constants to be controlled
16997 by consensus parameters. Also set better defaults for these
16998 parameters based on experimentation on broadband and simulated
16999 high latency links.
17002 - The 'EXTENDCIRCUIT' control port command can now be used with
17003 a circ id of 0 and no path. This feature will cause Tor to build
17004 a new 'fast' general purpose circuit using its own path selection
17006 - Added a BUILDTIMEOUT_SET controller event to describe changes
17007 to the circuit build timeout.
17008 - Future-proof the controller protocol a bit by ignoring keyword
17009 arguments we do not recognize.
17010 - Expand homedirs passed to tor-checkkey. This should silence a
17011 coverity complaint about passing a user-supplied string into
17012 open() without checking it.
17015 Changes in version 0.2.1.25 - 2010-03-16
17016 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
17017 prevent relays from guessing their IP address correctly. It also fixes
17018 several minor potential security bugs.
17021 - Fix a regression from our patch for bug 1244 that caused relays
17022 to guess their IP address incorrectly if they didn't set Address
17023 in their torrc and/or their address fails to resolve. Bugfix on
17024 0.2.1.23; fixes bug 1269.
17025 - When freeing a session key, zero it out completely. We only zeroed
17026 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
17027 patched by ekir. Fixes bug 1254.
17030 - Fix a dereference-then-NULL-check sequence when publishing
17031 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
17033 - Fix another dereference-then-NULL-check sequence. Bugfix on
17034 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
17035 - Make sure we treat potentially not NUL-terminated strings correctly.
17036 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
17040 Changes in version 0.2.1.24 - 2010-02-21
17041 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
17045 - Work correctly out-of-the-box with even more vendor-patched versions
17046 of OpenSSL. In particular, make it so Debian and OS X don't need
17047 customized patches to run/build.
17050 Changes in version 0.2.1.23 - 2010-02-13
17051 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
17052 again on the latest OS X, and updates the location of a directory
17055 o Major bugfixes (performance):
17056 - We were selecting our guards uniformly at random, and then weighting
17057 which of our guards we'd use uniformly at random. This imbalance
17058 meant that Tor clients were severely limited on throughput (and
17059 probably latency too) by the first hop in their circuit. Now we
17060 select guards weighted by currently advertised bandwidth. We also
17061 automatically discard guards picked using the old algorithm. Fixes
17062 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
17065 - Make Tor work again on the latest OS X: when deciding whether to
17066 use strange flags to turn TLS renegotiation on, detect the OpenSSL
17067 version at run-time, not compile time. We need to do this because
17068 Apple doesn't update its dev-tools headers when it updates its
17069 libraries in a security patch.
17070 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
17071 that could happen on 32-bit platforms with 64-bit time_t. Also fix
17072 a memory leak when requesting a hidden service descriptor we've
17073 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
17076 o Directory authority changes:
17077 - Change IP address for dannenberg (v3 directory authority), and
17078 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
17079 service directory authority) from the list.
17082 - Refactor resolve_my_address() to not use gethostbyname() anymore.
17083 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
17086 - Avoid a mad rush at the beginning of each month when each client
17087 rotates half of its guards. Instead we spread the rotation out
17088 throughout the month, but we still avoid leaving a precise timestamp
17089 in the state file about when we first picked the guard. Improves
17090 over the behavior introduced in 0.1.2.17.
17093 Changes in version 0.2.2.8-alpha - 2010-01-26
17094 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
17095 causing bridge relays to disappear. If you're running a bridge,
17099 - Fix a memory corruption bug on bridges that occured during the
17100 inclusion of stats data in extra-info descriptors. Also fix the
17101 interface for geoip_get_bridge_stats* to prevent similar bugs in
17102 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
17103 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
17106 - Ignore OutboundBindAddress when connecting to localhost.
17107 Connections to localhost need to come _from_ localhost, or else
17108 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
17112 Changes in version 0.2.2.7-alpha - 2010-01-19
17113 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
17114 as laying the groundwork for further relay-side performance fixes. It
17115 also starts cleaning up client behavior with respect to the EntryNodes,
17116 ExitNodes, and StrictNodes config options.
17118 This release also rotates two directory authority keys, due to a
17119 security breach of some of the Torproject servers.
17121 o Directory authority changes:
17122 - Rotate keys (both v3 identity and relay identity) for moria1
17125 o Major features (performance):
17126 - We were selecting our guards uniformly at random, and then weighting
17127 which of our guards we'd use uniformly at random. This imbalance
17128 meant that Tor clients were severely limited on throughput (and
17129 probably latency too) by the first hop in their circuit. Now we
17130 select guards weighted by currently advertised bandwidth. We also
17131 automatically discard guards picked using the old algorithm. Fixes
17132 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
17133 - When choosing which cells to relay first, relays can now favor
17134 circuits that have been quiet recently, to provide lower latency
17135 for low-volume circuits. By default, relays enable or disable this
17136 feature based on a setting in the consensus. You can override
17137 this default by using the new "CircuitPriorityHalflife" config
17138 option. Design and code by Ian Goldberg, Can Tang, and Chris
17140 - Add separate per-conn write limiting to go with the per-conn read
17141 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
17142 but never per-conn write limits.
17143 - New consensus params "bwconnrate" and "bwconnburst" to let us
17144 rate-limit client connections as they enter the network. It's
17145 controlled in the consensus so we can turn it on and off for
17146 experiments. It's starting out off. Based on proposal 163.
17148 o Major features (relay selection options):
17149 - Switch to a StrictNodes config option, rather than the previous
17150 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
17151 "StrictExcludeNodes" option.
17152 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
17153 change during a config reload, mark and discard all our origin
17154 circuits. This fix should address edge cases where we change the
17155 config options and but then choose a circuit that we created before
17157 - If EntryNodes or ExitNodes are set, be more willing to use an
17158 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
17160 - Make EntryNodes config option much more aggressive even when
17161 StrictNodes is not set. Before it would prepend your requested
17162 entrynodes to your list of guard nodes, but feel free to use others
17163 after that. Now it chooses only from your EntryNodes if any of
17164 those are available, and only falls back to others if a) they're
17165 all down and b) StrictNodes is not set.
17166 - Now we refresh your entry guards from EntryNodes at each consensus
17167 fetch -- rather than just at startup and then they slowly rot as
17168 the network changes.
17171 - Stop bridge directory authorities from answering dbg-stability.txt
17172 directory queries, which would let people fetch a list of all
17173 bridge identities they track. Bugfix on 0.2.1.6-alpha.
17176 - Log a notice when we get a new control connection. Now it's easier
17177 for security-conscious users to recognize when a local application
17178 is knocking on their controller door. Suggested by bug 1196.
17179 - New config option "CircuitStreamTimeout" to override our internal
17180 timeout schedule for how many seconds until we detach a stream from
17181 a circuit and try a new circuit. If your network is particularly
17182 slow, you might want to set this to a number like 60.
17183 - New controller command "getinfo config-text". It returns the
17184 contents that Tor would write if you send it a SAVECONF command,
17185 so the controller can write the file to disk itself.
17186 - New options for SafeLogging to allow scrubbing only log messages
17187 generated while acting as a relay.
17188 - Ship the bridges spec file in the tarball too.
17189 - Avoid a mad rush at the beginning of each month when each client
17190 rotates half of its guards. Instead we spread the rotation out
17191 throughout the month, but we still avoid leaving a precise timestamp
17192 in the state file about when we first picked the guard. Improves
17193 over the behavior introduced in 0.1.2.17.
17195 o Minor bugfixes (compiling):
17196 - Fix compilation on OS X 10.3, which has a stub mlockall() but
17197 hides it. Bugfix on 0.2.2.6-alpha.
17198 - Fix compilation on Solaris by removing support for the
17199 DisableAllSwap config option. Solaris doesn't have an rlimit for
17200 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
17203 o Minor bugfixes (crashes):
17204 - Do not segfault when writing buffer stats when we haven't observed
17205 a single circuit to report about. Found by Fabian Lanze. Bugfix on
17207 - If we're in the pathological case where there's no exit bandwidth
17208 but there is non-exit bandwidth, or no guard bandwidth but there
17209 is non-guard bandwidth, don't crash during path selection. Bugfix
17211 - Fix an impossible-to-actually-trigger buffer overflow in relay
17212 descriptor generation. Bugfix on 0.1.0.15.
17214 o Minor bugfixes (privacy):
17215 - Fix an instance where a Tor directory mirror might accidentally
17216 log the IP address of a misbehaving Tor client. Bugfix on
17218 - Don't list Windows capabilities in relay descriptors. We never made
17219 use of them, and maybe it's a bad idea to publish them. Bugfix
17222 o Minor bugfixes (other):
17223 - Resolve an edge case in path weighting that could make us misweight
17224 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
17225 - Fix statistics on client numbers by country as seen by bridges that
17226 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
17227 intervals instead of variable 12-to-48-hour intervals.
17228 - After we free an internal connection structure, overwrite it
17229 with a different memory value than we use for overwriting a freed
17230 internal circuit structure. Should help with debugging. Suggested
17232 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
17235 o Removed features:
17236 - Remove the HSAuthorityRecordStats option that version 0 hidden
17237 service authorities could have used to track statistics of overall
17238 hidden service usage.
17241 Changes in version 0.2.1.22 - 2010-01-19
17242 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
17243 authorities -- it would tell you its whole history of bridge descriptors
17244 if you make the right directory request. This stable update also
17245 rotates two of the seven v3 directory authority keys and locations.
17247 o Directory authority changes:
17248 - Rotate keys (both v3 identity and relay identity) for moria1
17252 - Stop bridge directory authorities from answering dbg-stability.txt
17253 directory queries, which would let people fetch a list of all
17254 bridge identities they track. Bugfix on 0.2.1.6-alpha.
17257 Changes in version 0.2.1.21 - 2009-12-21
17258 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
17259 library. If you use Tor on Linux / Unix and you're getting SSL
17260 renegotiation errors, upgrading should help. We also recommend an
17261 upgrade if you're an exit relay.
17264 - Work around a security feature in OpenSSL 0.9.8l that prevents our
17265 handshake from working unless we explicitly tell OpenSSL that we
17266 are using SSL renegotiation safely. We are, of course, but OpenSSL
17267 0.9.8l won't work unless we say we are.
17268 - Avoid crashing if the client is trying to upload many bytes and the
17269 circuit gets torn down at the same time, or if the flip side
17270 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
17273 - Do not refuse to learn about authority certs and v2 networkstatus
17274 documents that are older than the latest consensus. This bug might
17275 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
17276 Spotted and fixed by xmux.
17277 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
17278 trigger platform-specific option misparsing case found by Coverity
17280 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
17281 trigger assert. Fixes bug 1173.
17284 Changes in version 0.2.2.6-alpha - 2009-11-19
17285 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
17286 support for the new lower-footprint "microdescriptor" directory design,
17287 future-proofing our consensus format against new hash functions or
17288 other changes, and an Android port. It also makes Tor compatible with
17289 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
17292 - Directory authorities can now create, vote on, and serve multiple
17293 parallel formats of directory data as part of their voting process.
17294 Partially implements Proposal 162: "Publish the consensus in
17296 - Directory authorities can now agree on and publish small summaries
17297 of router information that clients can use in place of regular
17298 server descriptors. This transition will eventually allow clients
17299 to use far less bandwidth for downloading information about the
17300 network. Begins the implementation of Proposal 158: "Clients
17301 download consensus + microdescriptors".
17302 - The directory voting system is now extensible to use multiple hash
17303 algorithms for signatures and resource selection. Newer formats
17304 are signed with SHA256, with a possibility for moving to a better
17305 hash algorithm in the future.
17306 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
17307 current and future memory pages via mlockall(). On supported
17308 platforms (modern Linux and probably BSD but not Windows or OS X),
17309 this should effectively disable any and all attempts to page out
17310 memory. This option requires that you start your Tor as root --
17311 if you use DisableAllSwap, please consider using the User option
17312 to properly reduce the privileges of your Tor.
17313 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
17314 to help Tor build correctly for Android phones.
17317 - Work around a security feature in OpenSSL 0.9.8l that prevents our
17318 handshake from working unless we explicitly tell OpenSSL that we
17319 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
17320 won't work unless we say we are.
17323 - Fix a crash bug when trying to initialize the evdns module in
17324 Libevent 2. Bugfix on 0.2.1.16-rc.
17325 - Stop logging at severity 'warn' when some other Tor client tries
17326 to establish a circuit with us using weak DH keys. It's a protocol
17327 violation, but that doesn't mean ordinary users need to hear about
17328 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
17329 - Do not refuse to learn about authority certs and v2 networkstatus
17330 documents that are older than the latest consensus. This bug might
17331 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
17332 Spotted and fixed by xmux.
17333 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
17334 - If all authorities restart at once right before a consensus vote,
17335 nobody will vote about "Running", and clients will get a consensus
17336 with no usable relays. Instead, authorities refuse to build a
17337 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
17338 - If your relay can't keep up with the number of incoming create
17339 cells, it would log one warning per failure into your logs. Limit
17340 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
17341 - Bridges now use "reject *:*" as their default exit policy. Bugfix
17342 on 0.2.0.3-alpha; fixes bug 1113.
17343 - Fix a memory leak on directory authorities during voting that was
17344 introduced in 0.2.2.1-alpha. Found via valgrind.
17347 Changes in version 0.2.1.20 - 2009-10-15
17348 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
17349 services at once, prepares for more performance improvements, and
17350 fixes a bunch of smaller bugs.
17352 The Windows and OS X bundles also include a more recent Vidalia,
17353 and switch from Privoxy to Polipo.
17355 The OS X installers are now drag and drop. It's best to un-install
17356 Tor/Vidalia and then install this new bundle, rather than upgrade. If
17357 you want to upgrade, you'll need to update the paths for Tor and Polipo
17358 in the Vidalia Settings window.
17361 - Send circuit or stream sendme cells when our window has decreased
17362 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
17363 by Karsten when testing the "reduce circuit window" performance
17364 patch. Bugfix on the 54th commit on Tor -- from July 2002,
17365 before the release of Tor 0.0.0. This is the new winner of the
17367 - Fix a remotely triggerable memory leak when a consensus document
17368 contains more than one signature from the same voter. Bugfix on
17370 - Avoid segfault in rare cases when finishing an introduction circuit
17371 as a client and finding out that we don't have an introduction key
17372 for it. Fixes bug 1073. Reported by Aaron Swartz.
17375 - Tor now reads the "circwindow" parameter out of the consensus,
17376 and uses that value for its circuit package window rather than the
17377 default of 1000 cells. Begins the implementation of proposal 168.
17379 o New directory authorities:
17380 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
17382 - Move moria1 and tonga to alternate IP addresses.
17385 - Fix a signed/unsigned compile warning in 0.2.1.19.
17386 - Fix possible segmentation fault on directory authorities. Bugfix on
17388 - Fix an extremely rare infinite recursion bug that could occur if
17389 we tried to log a message after shutting down the log subsystem.
17390 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
17391 - Fix an obscure bug where hidden services on 64-bit big-endian
17392 systems might mis-read the timestamp in v3 introduce cells, and
17393 refuse to connect back to the client. Discovered by "rotor".
17394 Bugfix on 0.2.1.6-alpha.
17395 - We were triggering a CLOCK_SKEW controller status event whenever
17396 we connect via the v2 connection protocol to any relay that has
17397 a wrong clock. Instead, we should only inform the controller when
17398 it's a trusted authority that claims our clock is wrong. Bugfix
17399 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
17400 - We were telling the controller about CHECKING_REACHABILITY and
17401 REACHABILITY_FAILED status events whenever we launch a testing
17402 circuit or notice that one has failed. Instead, only tell the
17403 controller when we want to inform the user of overall success or
17404 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
17406 - Don't warn when we're using a circuit that ends with a node
17407 excluded in ExcludeExitNodes, but the circuit is not used to access
17408 the outside world. This should help fix bug 1090. Bugfix on
17410 - Work around a small memory leak in some versions of OpenSSL that
17411 stopped the memory used by the hostname TLS extension from being
17415 - Add a "getinfo status/accepted-server-descriptor" controller
17416 command, which is the recommended way for controllers to learn
17417 whether our server descriptor has been successfully received by at
17418 least on directory authority. Un-recommend good-server-descriptor
17419 getinfo and status events until we have a better design for them.
17422 Changes in version 0.2.2.5-alpha - 2009-10-11
17423 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
17426 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
17428 o Directory authorities:
17429 - Temporarily (just for this release) move dizum to an alternate
17433 Changes in version 0.2.2.4-alpha - 2009-10-10
17434 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
17435 introduces a new unit test framework, shifts directry authority
17436 addresses around to reduce the impact from recent blocking events,
17437 and fixes a few smaller bugs.
17440 - Fix several more asserts in the circuit_build_times code, for
17441 example one that causes Tor to fail to start once we have
17442 accumulated 5000 build times in the state file. Bugfixes on
17443 0.2.2.2-alpha; fixes bug 1108.
17445 o New directory authorities:
17446 - Move moria1 and Tonga to alternate IP addresses.
17449 - Log SSL state transitions at debug level during handshake, and
17450 include SSL states in error messages. This may help debug future
17451 SSL handshake issues.
17452 - Add a new "Handshake" log domain for activities that happen
17453 during the TLS handshake.
17454 - Revert to the "June 3 2009" ip-to-country file. The September one
17455 seems to have removed most US IP addresses.
17456 - Directory authorities now reject Tor relays with versions less than
17457 0.1.2.14. This step cuts out four relays from the current network,
17458 none of which are very big.
17461 - Fix a couple of smaller issues with gathering statistics. Bugfixes
17463 - Fix two memory leaks in the error case of
17464 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
17465 - Don't count one-hop circuits when we're estimating how long it
17466 takes circuits to build on average. Otherwise we'll set our circuit
17467 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
17468 - Directory authorities no longer change their opinion of, or vote on,
17469 whether a router is Running, unless they have themselves been
17470 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
17473 o Code simplifications and refactoring:
17474 - Revise our unit tests to use the "tinytest" framework, so we
17475 can run tests in their own processes, have smarter setup/teardown
17476 code, and so on. The unit test code has moved to its own
17477 subdirectory, and has been split into multiple modules.
17480 Changes in version 0.2.2.3-alpha - 2009-09-23
17481 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
17484 - Fix an overzealous assert in our new circuit build timeout code.
17485 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
17488 - If the networkstatus consensus tells us that we should use a
17489 negative circuit package window, ignore it. Otherwise we'll
17490 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
17493 Changes in version 0.2.2.2-alpha - 2009-09-21
17494 Tor 0.2.2.2-alpha introduces our latest performance improvement for
17495 clients: Tor tracks the average time it takes to build a circuit, and
17496 avoids using circuits that take too long to build. For fast connections,
17497 this feature can cut your expected latency in half. For slow or flaky
17498 connections, it could ruin your Tor experience. Let us know if it does!
17501 - Tor now tracks how long it takes to build client-side circuits
17502 over time, and adapts its timeout to local network performance.
17503 Since a circuit that takes a long time to build will also provide
17504 bad performance, we get significant latency improvements by
17505 discarding the slowest 20% of circuits. Specifically, Tor creates
17506 circuits more aggressively than usual until it has enough data
17507 points for a good timeout estimate. Implements proposal 151.
17508 We are especially looking for reports (good and bad) from users with
17509 both EDGE and broadband connections that can move from broadband
17510 to EDGE and find out if the build-time data in the .tor/state gets
17511 reset without loss of Tor usability. You should also see a notice
17512 log message telling you that Tor has reset its timeout.
17513 - Directory authorities can now vote on arbitary integer values as
17514 part of the consensus process. This is designed to help set
17515 network-wide parameters. Implements proposal 167.
17516 - Tor now reads the "circwindow" parameter out of the consensus,
17517 and uses that value for its circuit package window rather than the
17518 default of 1000 cells. Begins the implementation of proposal 168.
17521 - Fix a remotely triggerable memory leak when a consensus document
17522 contains more than one signature from the same voter. Bugfix on
17526 - Fix an extremely rare infinite recursion bug that could occur if
17527 we tried to log a message after shutting down the log subsystem.
17528 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
17529 - Fix parsing for memory or time units given without a space between
17530 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
17531 - A networkstatus vote must contain exactly one signature. Spec
17532 conformance issue. Bugfix on 0.2.0.3-alpha.
17533 - Fix an obscure bug where hidden services on 64-bit big-endian
17534 systems might mis-read the timestamp in v3 introduce cells, and
17535 refuse to connect back to the client. Discovered by "rotor".
17536 Bugfix on 0.2.1.6-alpha.
17537 - We were triggering a CLOCK_SKEW controller status event whenever
17538 we connect via the v2 connection protocol to any relay that has
17539 a wrong clock. Instead, we should only inform the controller when
17540 it's a trusted authority that claims our clock is wrong. Bugfix
17541 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
17542 - We were telling the controller about CHECKING_REACHABILITY and
17543 REACHABILITY_FAILED status events whenever we launch a testing
17544 circuit or notice that one has failed. Instead, only tell the
17545 controller when we want to inform the user of overall success or
17546 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
17548 - Don't warn when we're using a circuit that ends with a node
17549 excluded in ExcludeExitNodes, but the circuit is not used to access
17550 the outside world. This should help fix bug 1090, but more problems
17551 remain. Bugfix on 0.2.1.6-alpha.
17552 - Work around a small memory leak in some versions of OpenSSL that
17553 stopped the memory used by the hostname TLS extension from being
17555 - Make our 'torify' script more portable; if we have only one of
17556 'torsocks' or 'tsocks' installed, don't complain to the user;
17557 and explain our warning about tsocks better.
17560 - Add a "getinfo status/accepted-server-descriptor" controller
17561 command, which is the recommended way for controllers to learn
17562 whether our server descriptor has been successfully received by at
17563 least on directory authority. Un-recommend good-server-descriptor
17564 getinfo and status events until we have a better design for them.
17565 - Update to the "September 4 2009" ip-to-country file.
17568 Changes in version 0.2.2.1-alpha - 2009-08-26
17569 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
17570 Tor clients to bootstrap on networks where only port 80 is reachable,
17571 makes it more straightforward to support hardware crypto accelerators,
17572 and starts the groundwork for gathering stats safely at relays.
17575 - Start the process of disabling ".exit" address notation, since it
17576 can be used for a variety of esoteric application-level attacks
17577 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
17580 o New directory authorities:
17581 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
17585 - New AccelName and AccelDir options add support for dynamic OpenSSL
17586 hardware crypto acceleration engines.
17587 - Tor now supports tunneling all of its outgoing connections over
17588 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
17589 configuration options. Code by Christopher Davis.
17592 - Send circuit or stream sendme cells when our window has decreased
17593 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
17594 by Karsten when testing the "reduce circuit window" performance
17595 patch. Bugfix on the 54th commit on Tor -- from July 2002,
17596 before the release of Tor 0.0.0. This is the new winner of the
17599 o New options for gathering stats safely:
17600 - Directory mirrors that set "DirReqStatistics 1" write statistics
17601 about directory requests to disk every 24 hours. As compared to the
17602 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
17603 1) stats are written to disk exactly every 24 hours; 2) estimated
17604 shares of v2 and v3 requests are determined as mean values, not at
17605 the end of a measurement period; 3) unresolved requests are listed
17606 with country code '??'; 4) directories also measure download times.
17607 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
17608 number of exit streams and transferred bytes per port to disk every
17610 - Relays that set "CellStatistics 1" write statistics on how long
17611 cells spend in their circuit queues to disk every 24 hours.
17612 - Entry nodes that set "EntryStatistics 1" write statistics on the
17613 rough number and origins of connecting clients to disk every 24
17615 - Relays that write any of the above statistics to disk and set
17616 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
17617 their extra-info documents.
17620 - New --digests command-line switch to output the digests of the
17621 source files Tor was built with.
17622 - The "torify" script now uses torsocks where available.
17623 - The memarea code now uses a sentinel value at the end of each area
17624 to make sure nothing writes beyond the end of an area. This might
17625 help debug some conceivable causes of bug 930.
17626 - Time and memory units in the configuration file can now be set to
17627 fractional units. For example, "2.5 GB" is now a valid value for
17629 - Certain Tor clients (such as those behind check.torproject.org) may
17630 want to fetch the consensus in an extra early manner. To enable this
17631 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
17632 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
17633 as only certain clients who must have this information sooner should
17635 - Instead of adding the svn revision to the Tor version string, report
17636 the git commit (when we're building from a git checkout).
17639 - If any of the v3 certs we download are unparseable, we should
17640 actually notice the failure so we don't retry indefinitely. Bugfix
17641 on 0.2.0.x; reported by "rotator".
17642 - If the cached cert file is unparseable, warn but don't exit.
17643 - Fix possible segmentation fault on directory authorities. Bugfix on
17645 - When Tor fails to parse a descriptor of any kind, dump it to disk.
17646 Might help diagnosing bug 1051.
17648 o Deprecated and removed features:
17649 - The controller no longer accepts the old obsolete "addr-mappings/"
17650 or "unregistered-servers-" GETINFO values.
17651 - Hidden services no longer publish version 0 descriptors, and clients
17652 do not request or use version 0 descriptors. However, the old hidden
17653 service authorities still accept and serve version 0 descriptors
17654 when contacted by older hidden services/clients.
17655 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
17656 always on; using them is necessary for correct forward-compatible
17658 - Remove support for .noconnect style addresses. Nobody was using
17659 them, and they provided another avenue for detecting Tor users
17660 via application-level web tricks.
17662 o Packaging changes:
17663 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
17664 installer bundles. See
17665 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
17666 for details of what's new in Vidalia 0.2.3.
17667 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
17668 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
17669 configuration file, rather than the old Privoxy.
17670 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
17671 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
17672 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
17673 better compatibility with OS X 10.6, aka Snow Leopard.
17674 - OS X Vidalia Bundle: The multi-package installer is now replaced
17675 by a simple drag and drop to the /Applications folder. This change
17676 occurred with the upgrade to Vidalia 0.2.3.
17679 Changes in version 0.2.1.19 - 2009-07-28
17680 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
17681 services on Tor 0.2.1.3-alpha through 0.2.1.18.
17684 - Make accessing hidden services on 0.2.1.x work right again.
17685 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
17686 part of patch provided by "optimist".
17689 - When a relay/bridge is writing out its identity key fingerprint to
17690 the "fingerprint" file and to its logs, write it without spaces. Now
17691 it will look like the fingerprints in our bridges documentation,
17692 and confuse fewer users.
17695 - Relays no longer publish a new server descriptor if they change
17696 their MaxAdvertisedBandwidth config option but it doesn't end up
17697 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
17698 fixes bug 1026. Patch from Sebastian.
17699 - Avoid leaking memory every time we get a create cell but we have
17700 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
17701 fixes bug 1034. Reported by BarkerJr.
17704 Changes in version 0.2.1.18 - 2009-07-24
17705 Tor 0.2.1.18 lays the foundations for performance improvements,
17706 adds status events to help users diagnose bootstrap problems, adds
17707 optional authentication/authorization for hidden services, fixes a
17708 variety of potential anonymity problems, and includes a huge pile of
17709 other features and bug fixes.
17712 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
17715 Changes in version 0.2.1.17-rc - 2009-07-07
17716 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
17717 candidate for the 0.2.1.x series. It lays the groundwork for further
17718 client performance improvements, and also fixes a big bug with directory
17719 authorities that were causing them to assign Guard and Stable flags
17722 The Windows bundles also finally include the geoip database that we
17723 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
17724 should actually install Torbutton rather than giving you a cryptic
17725 failure message (oops).
17728 - Clients now use the bandwidth values in the consensus, rather than
17729 the bandwidth values in each relay descriptor. This approach opens
17730 the door to more accurate bandwidth estimates once the directory
17731 authorities start doing active measurements. Implements more of
17735 - When Tor clients restart after 1-5 days, they discard all their
17736 cached descriptors as too old, but they still use the cached
17737 consensus document. This approach is good for robustness, but
17738 bad for performance: since they don't know any bandwidths, they
17739 end up choosing at random rather than weighting their choice by
17740 speed. Fixed by the above feature of putting bandwidths in the
17741 consensus. Bugfix on 0.2.0.x.
17742 - Directory authorities were neglecting to mark relays down in their
17743 internal histories if the relays fall off the routerlist without
17744 ever being found unreachable. So there were relays in the histories
17745 that haven't been seen for eight months, and are listed as being
17746 up for eight months. This wreaked havoc on the "median wfu"
17747 and "median mtbf" calculations, in turn making Guard and Stable
17748 flags very wrong, hurting network performance. Fixes bugs 696 and
17749 969. Bugfix on 0.2.0.6-alpha.
17752 - Serve the DirPortFrontPage page even when we have been approaching
17753 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
17754 - The control port would close the connection before flushing long
17755 replies, such as the network consensus, if a QUIT command was issued
17756 before the reply had completed. Now, the control port flushes all
17757 pending replies before closing the connection. Also fixed a spurious
17758 warning when a QUIT command is issued after a malformed or rejected
17759 AUTHENTICATE command, but before the connection was closed. Patch
17760 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
17761 - When we can't find an intro key for a v2 hidden service descriptor,
17762 fall back to the v0 hidden service descriptor and log a bug message.
17763 Workaround for bug 1024.
17764 - Fix a log message that did not respect the SafeLogging option.
17768 - If we're a relay and we change our IP address, be more verbose
17769 about the reason that made us change. Should help track down
17770 further bugs for relays on dynamic IP addresses.
17773 Changes in version 0.2.0.35 - 2009-06-24
17775 - Avoid crashing in the presence of certain malformed descriptors.
17776 Found by lark, and by automated fuzzing.
17777 - Fix an edge case where a malicious exit relay could convince a
17778 controller that the client's DNS question resolves to an internal IP
17779 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
17782 - Finally fix the bug where dynamic-IP relays disappear when their
17783 IP address changes: directory mirrors were mistakenly telling
17784 them their old address if they asked via begin_dir, so they
17785 never got an accurate answer about their new address, so they
17786 just vanished after a day. For belt-and-suspenders, relays that
17787 don't set Address in their config now avoid using begin_dir for
17788 all direct connections. Should fix bugs 827, 883, and 900.
17789 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
17790 that would occur on some exit nodes when DNS failures and timeouts
17791 occurred in certain patterns. Fix for bug 957.
17794 - When starting with a cache over a few days old, do not leak
17795 memory for the obsolete router descriptors in it. Bugfix on
17796 0.2.0.33; fixes bug 672.
17797 - Hidden service clients didn't use a cached service descriptor that
17798 was older than 15 minutes, but wouldn't fetch a new one either,
17799 because there was already one in the cache. Now, fetch a v2
17800 descriptor unless the same descriptor was added to the cache within
17801 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
17804 Changes in version 0.2.1.16-rc - 2009-06-20
17805 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
17806 a bunch of minor bugs.
17809 - Fix an edge case where a malicious exit relay could convince a
17810 controller that the client's DNS question resolves to an internal IP
17811 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
17813 o Major performance improvements (on 0.2.0.x):
17814 - Disable and refactor some debugging checks that forced a linear scan
17815 over the whole server-side DNS cache. These accounted for over 50%
17816 of CPU time on a relatively busy exit node's gprof profile. Found
17818 - Disable some debugging checks that appeared in exit node profile
17822 - Update to the "June 3 2009" ip-to-country file.
17823 - Do not have tor-resolve automatically refuse all .onion addresses;
17824 if AutomapHostsOnResolve is set in your torrc, this will work fine.
17826 o Minor bugfixes (on 0.2.0.x):
17827 - Log correct error messages for DNS-related network errors on
17829 - Fix a race condition that could cause crashes or memory corruption
17830 when running as a server with a controller listening for log
17832 - Avoid crashing when we have a policy specified in a DirPolicy or
17833 SocksPolicy or ReachableAddresses option with ports set on it,
17834 and we re-load the policy. May fix bug 996.
17835 - Hidden service clients didn't use a cached service descriptor that
17836 was older than 15 minutes, but wouldn't fetch a new one either,
17837 because there was already one in the cache. Now, fetch a v2
17838 descriptor unless the same descriptor was added to the cache within
17839 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
17841 o Minor bugfixes (on 0.2.1.x):
17842 - Don't warn users about low port and hibernation mix when they
17843 provide a *ListenAddress directive to fix that. Bugfix on
17845 - When switching back and forth between bridge mode, do not start
17846 gathering GeoIP data until two hours have passed.
17847 - Do not complain that the user has requested an excluded node as
17848 an exit when the node is not really an exit. This could happen
17849 because the circuit was for testing, or an introduction point.
17853 Changes in version 0.2.1.15-rc - 2009-05-25
17854 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
17855 series. It fixes a major bug on fast exit relays, as well as a variety
17856 of more minor bugs.
17858 o Major bugfixes (on 0.2.0.x):
17859 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
17860 that would occur on some exit nodes when DNS failures and timeouts
17861 occurred in certain patterns. Fix for bug 957.
17863 o Minor bugfixes (on 0.2.0.x):
17864 - Actually return -1 in the error case for read_bandwidth_usage().
17865 Harmless bug, since we currently don't care about the return value
17866 anywhere. Bugfix on 0.2.0.9-alpha.
17867 - Provide a more useful log message if bug 977 (related to buffer
17868 freelists) ever reappears, and do not crash right away.
17869 - Fix an assertion failure on 64-bit platforms when we allocated
17870 memory right up to the end of a memarea, then realigned the memory
17871 one step beyond the end. Fixes a possible cause of bug 930.
17872 - Protect the count of open sockets with a mutex, so we can't
17873 corrupt it when two threads are closing or opening sockets at once.
17874 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
17875 - Don't allow a bridge to publish its router descriptor to a
17876 non-bridge directory authority. Fixes part of bug 932.
17877 - When we change to or from being a bridge, reset our counts of
17878 client usage by country. Fixes bug 932.
17879 - Fix a bug that made stream bandwidth get misreported to the
17881 - Stop using malloc_usable_size() to use more area than we had
17882 actually allocated: it was safe, but made valgrind really unhappy.
17883 - Fix a memory leak when v3 directory authorities load their keys
17884 and cert from disk. Bugfix on 0.2.0.1-alpha.
17886 o Minor bugfixes (on 0.2.1.x):
17887 - Fix use of freed memory when deciding to mark a non-addable
17888 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
17891 Changes in version 0.2.1.14-rc - 2009-04-12
17892 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
17893 series. It begins fixing some major performance problems, and also
17894 finally addresses the bug that was causing relays on dynamic IP
17895 addresses to fall out of the directory.
17898 - Clients replace entry guards that were chosen more than a few months
17899 ago. This change should significantly improve client performance,
17900 especially once more people upgrade, since relays that have been
17901 a guard for a long time are currently overloaded.
17903 o Major bugfixes (on 0.2.0):
17904 - Finally fix the bug where dynamic-IP relays disappear when their
17905 IP address changes: directory mirrors were mistakenly telling
17906 them their old address if they asked via begin_dir, so they
17907 never got an accurate answer about their new address, so they
17908 just vanished after a day. For belt-and-suspenders, relays that
17909 don't set Address in their config now avoid using begin_dir for
17910 all direct connections. Should fix bugs 827, 883, and 900.
17911 - Relays were falling out of the networkstatus consensus for
17912 part of a day if they changed their local config but the
17913 authorities discarded their new descriptor as "not sufficiently
17914 different". Now directory authorities accept a descriptor as changed
17915 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
17916 patch by Sebastian.
17917 - Avoid crashing in the presence of certain malformed descriptors.
17918 Found by lark, and by automated fuzzing.
17921 - When generating circuit events with verbose nicknames for
17922 controllers, try harder to look up nicknames for routers on a
17923 circuit. (Previously, we would look in the router descriptors we had
17924 for nicknames, but not in the consensus.) Partial fix for bug 941.
17925 - If the bridge config line doesn't specify a port, assume 443.
17926 This makes bridge lines a bit smaller and easier for users to
17928 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
17929 bytes (aka 20KB/s), to match our documentation. Also update
17930 directory authorities so they always assign the Fast flag to relays
17931 with 20KB/s of capacity. Now people running relays won't suddenly
17932 find themselves not seeing any use, if the network gets faster
17934 - Update to the "April 3 2009" ip-to-country file.
17937 - Avoid trying to print raw memory to the logs when we decide to
17938 give up on downloading a given relay descriptor. Bugfix on
17940 - In tor-resolve, when the Tor client to use is specified by
17941 <hostname>:<port>, actually use the specified port rather than
17942 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
17943 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
17944 - When starting with a cache over a few days old, do not leak
17945 memory for the obsolete router descriptors in it. Bugfix on
17947 - Avoid double-free on list of successfully uploaded hidden
17948 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
17949 - Change memarea_strndup() implementation to work even when
17950 duplicating a string at the end of a page. This bug was
17951 harmless for now, but could have meant crashes later. Fix by
17952 lark. Bugfix on 0.2.1.1-alpha.
17953 - Limit uploaded directory documents to be 16M rather than 500K.
17954 The directory authorities were refusing v3 consensus votes from
17955 other authorities, since the votes are now 504K. Fixes bug 959;
17956 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
17957 - Directory authorities should never send a 503 "busy" response to
17958 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
17962 Changes in version 0.2.1.13-alpha - 2009-03-09
17963 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
17964 cleanups. We're finally getting close to a release candidate.
17967 - Correctly update the list of which countries we exclude as
17968 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
17969 lark. Bugfix on 0.2.1.6-alpha.
17971 o Minor bugfixes (on 0.2.0.x and earlier):
17972 - Automatically detect MacOSX versions earlier than 10.4.0, and
17973 disable kqueue from inside Tor when running with these versions.
17974 We previously did this from the startup script, but that was no
17975 help to people who didn't use the startup script. Resolves bug 863.
17976 - When we had picked an exit node for a connection, but marked it as
17977 "optional", and it turned out we had no onion key for the exit,
17978 stop wanting that exit and try again. This situation may not
17979 be possible now, but will probably become feasible with proposal
17980 158. Spotted by rovv. Fixes another case of bug 752.
17981 - Clients no longer cache certificates for authorities they do not
17982 recognize. Bugfix on 0.2.0.9-alpha.
17983 - When we can't transmit a DNS request due to a network error, retry
17984 it after a while, and eventually transmit a failing response to
17985 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
17986 - If the controller claimed responsibility for a stream, but that
17987 stream never finished making its connection, it would live
17988 forever in circuit_wait state. Now we close it after SocksTimeout
17989 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
17990 - Drop begin cells to a hidden service if they come from the middle
17991 of a circuit. Patch from lark.
17992 - When we erroneously receive two EXTEND cells for the same circuit
17993 ID on the same connection, drop the second. Patch from lark.
17994 - Fix a crash that occurs on exit nodes when a nameserver request
17995 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
17996 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
17998 - Do not assume that a stack-allocated character array will be
17999 64-bit aligned on platforms that demand that uint64_t access is
18000 aligned. Possible fix for bug 604.
18001 - Parse dates and IPv4 addresses in a locale- and libc-independent
18002 manner, to avoid platform-dependent behavior on malformed input.
18003 - Build correctly when configured to build outside the main source
18004 path. Patch from Michael Gold.
18005 - We were already rejecting relay begin cells with destination port
18006 of 0. Now also reject extend cells with destination port or address
18007 of 0. Suggested by lark.
18009 o Minor bugfixes (on 0.2.1.x):
18010 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
18011 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
18012 - If we're an exit node, scrub the IP address to which we are exiting
18013 in the logs. Bugfix on 0.2.1.8-alpha.
18016 - On Linux, use the prctl call to re-enable core dumps when the user
18018 - New controller event NEWCONSENSUS that lists the networkstatus
18019 lines for every recommended relay. Now controllers like Torflow
18020 can keep up-to-date on which relays they should be using.
18021 - Update to the "February 26 2009" ip-to-country file.
18024 Changes in version 0.2.0.34 - 2009-02-08
18025 Tor 0.2.0.34 features several more security-related fixes. You should
18026 upgrade, especially if you run an exit relay (remote crash) or a
18027 directory authority (remote infinite loop), or you're on an older
18028 (pre-XP) or not-recently-patched Windows (remote exploit).
18030 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
18031 have many known flaws, and nobody should be using them. You should
18032 upgrade. If you're using a Linux or BSD and its packages are obsolete,
18033 stop using those packages and upgrade anyway.
18036 - Fix an infinite-loop bug on handling corrupt votes under certain
18037 circumstances. Bugfix on 0.2.0.8-alpha.
18038 - Fix a temporary DoS vulnerability that could be performed by
18039 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
18040 - Avoid a potential crash on exit nodes when processing malformed
18041 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
18042 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
18043 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
18046 - Fix compilation on systems where time_t is a 64-bit integer.
18047 Patch from Matthias Drochner.
18048 - Don't consider expiring already-closed client connections. Fixes
18049 bug 893. Bugfix on 0.0.2pre20.
18052 Changes in version 0.2.1.12-alpha - 2009-02-08
18053 Tor 0.2.1.12-alpha features several more security-related fixes. You
18054 should upgrade, especially if you run an exit relay (remote crash) or
18055 a directory authority (remote infinite loop), or you're on an older
18056 (pre-XP) or not-recently-patched Windows (remote exploit). It also
18057 includes a big pile of minor bugfixes and cleanups.
18060 - Fix an infinite-loop bug on handling corrupt votes under certain
18061 circumstances. Bugfix on 0.2.0.8-alpha.
18062 - Fix a temporary DoS vulnerability that could be performed by
18063 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
18064 - Avoid a potential crash on exit nodes when processing malformed
18065 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
18068 - Let controllers actually ask for the "clients_seen" event for
18069 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
18070 reported by Matt Edman.
18071 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
18073 - Fix a bug in address parsing that was preventing bridges or hidden
18074 service targets from being at IPv6 addresses.
18075 - Solve a bug that kept hardware crypto acceleration from getting
18076 enabled when accounting was turned on. Fixes bug 907. Bugfix on
18078 - Remove a bash-ism from configure.in to build properly on non-Linux
18079 platforms. Bugfix on 0.2.1.1-alpha.
18080 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
18081 headers. Bugfix on 0.2.0.10-alpha.
18082 - Don't consider expiring already-closed client connections. Fixes
18083 bug 893. Bugfix on 0.0.2pre20.
18084 - Fix another interesting corner-case of bug 891 spotted by rovv:
18085 Previously, if two hosts had different amounts of clock drift, and
18086 one of them created a new connection with just the wrong timing,
18087 the other might decide to deprecate the new connection erroneously.
18088 Bugfix on 0.1.1.13-alpha.
18089 - Resolve a very rare crash bug that could occur when the user forced
18090 a nameserver reconfiguration during the middle of a nameserver
18091 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
18092 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
18093 Bugfix on 0.2.1.7-alpha.
18094 - If we're using bridges and our network goes away, be more willing
18095 to forgive our bridges and try again when we get an application
18096 request. Bugfix on 0.2.0.x.
18099 - Support platforms where time_t is 64 bits long. (Congratulations,
18100 NetBSD!) Patch from Matthias Drochner.
18101 - Add a 'getinfo status/clients-seen' controller command, in case
18102 controllers want to hear clients_seen events but connect late.
18105 - Disable GCC's strict alias optimization by default, to avoid the
18106 likelihood of its introducing subtle bugs whenever our code violates
18107 the letter of C99's alias rules.
18110 Changes in version 0.2.0.33 - 2009-01-21
18111 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
18112 useful to users. It also finally fixes a bug where a relay or client
18113 that's been off for many days would take a long time to bootstrap.
18115 This update also fixes an important security-related bug reported by
18116 Ilja van Sprundel. You should upgrade. (We'll send out more details
18117 about the bug once people have had some time to upgrade.)
18120 - Fix a heap-corruption bug that may be remotely triggerable on
18121 some platforms. Reported by Ilja van Sprundel.
18124 - When a stream at an exit relay is in state "resolving" or
18125 "connecting" and it receives an "end" relay cell, the exit relay
18126 would silently ignore the end cell and not close the stream. If
18127 the client never closes the circuit, then the exit relay never
18128 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
18129 reported by "wood".
18130 - When sending CREATED cells back for a given circuit, use a 64-bit
18131 connection ID to find the right connection, rather than an addr:port
18132 combination. Now that we can have multiple OR connections between
18133 the same ORs, it is no longer possible to use addr:port to uniquely
18134 identify a connection.
18135 - Bridge relays that had DirPort set to 0 would stop fetching
18136 descriptors shortly after startup, and then briefly resume
18137 after a new bandwidth test and/or after publishing a new bridge
18138 descriptor. Bridge users that try to bootstrap from them would
18139 get a recent networkstatus but would get descriptors from up to
18140 18 hours earlier, meaning most of the descriptors were obsolete
18141 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
18142 - Prevent bridge relays from serving their 'extrainfo' document
18143 to anybody who asks, now that extrainfo docs include potentially
18144 sensitive aggregated client geoip summaries. Bugfix on
18146 - If the cached networkstatus consensus is more than five days old,
18147 discard it rather than trying to use it. In theory it could be
18148 useful because it lists alternate directory mirrors, but in practice
18149 it just means we spend many minutes trying directory mirrors that
18150 are long gone from the network. Also discard router descriptors as
18151 we load them if they are more than five days old, since the onion
18152 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
18155 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
18156 could make gcc generate non-functional binary search code. Bugfix
18158 - Build correctly on platforms without socklen_t.
18159 - Compile without warnings on solaris.
18160 - Avoid potential crash on internal error during signature collection.
18161 Fixes bug 864. Patch from rovv.
18162 - Correct handling of possible malformed authority signing key
18163 certificates with internal signature types. Fixes bug 880.
18164 Bugfix on 0.2.0.3-alpha.
18165 - Fix a hard-to-trigger resource leak when logging credential status.
18167 - When we can't initialize DNS because the network is down, do not
18168 automatically stop Tor from starting. Instead, we retry failed
18169 dns_init() every 10 minutes, and change the exit policy to reject
18170 *:* until one succeeds. Fixes bug 691.
18171 - Use 64 bits instead of 32 bits for connection identifiers used with
18172 the controller protocol, to greatly reduce risk of identifier reuse.
18173 - When we're choosing an exit node for a circuit, and we have
18174 no pending streams, choose a good general exit rather than one that
18175 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
18176 - Fix another case of assuming, when a specific exit is requested,
18177 that we know more than the user about what hosts it allows.
18178 Fixes one case of bug 752. Patch from rovv.
18179 - Clip the MaxCircuitDirtiness config option to a minimum of 10
18180 seconds. Warn the user if lower values are given in the
18181 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
18182 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
18183 user if lower values are given in the configuration. Bugfix on
18184 0.1.1.17-rc. Patch by Sebastian.
18185 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
18186 the cache because we already had a v0 descriptor with the same ID.
18187 Bugfix on 0.2.0.18-alpha.
18188 - Fix a race condition when freeing keys shared between main thread
18189 and CPU workers that could result in a memory leak. Bugfix on
18190 0.1.0.1-rc. Fixes bug 889.
18191 - Send a valid END cell back when a client tries to connect to a
18192 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
18193 840. Patch from rovv.
18194 - Check which hops rendezvous stream cells are associated with to
18195 prevent possible guess-the-streamid injection attacks from
18196 intermediate hops. Fixes another case of bug 446. Based on patch
18198 - If a broken client asks a non-exit router to connect somewhere,
18199 do not even do the DNS lookup before rejecting the connection.
18200 Fixes another case of bug 619. Patch from rovv.
18201 - When a relay gets a create cell it can't decrypt (e.g. because it's
18202 using the wrong onion key), we were dropping it and letting the
18203 client time out. Now actually answer with a destroy cell. Fixes
18204 bug 904. Bugfix on 0.0.2pre8.
18206 o Minor bugfixes (hidden services):
18207 - Do not throw away existing introduction points on SIGHUP. Bugfix on
18208 0.0.6pre1. Patch by Karsten. Fixes bug 874.
18211 - Report the case where all signatures in a detached set are rejected
18212 differently than the case where there is an error handling the
18214 - When we realize that another process has modified our cached
18215 descriptors, print out a more useful error message rather than
18216 triggering an assertion. Fixes bug 885. Patch from Karsten.
18217 - Implement the 0x20 hack to better resist DNS poisoning: set the
18218 case on outgoing DNS requests randomly, and reject responses that do
18219 not match the case correctly. This logic can be disabled with the
18220 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
18221 of servers that do not reliably preserve case in replies. See
18222 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
18224 - Check DNS replies for more matching fields to better resist DNS
18226 - Never use OpenSSL compression: it wastes RAM and CPU trying to
18227 compress cells, which are basically all encrypted, compressed, or
18231 Changes in version 0.2.1.11-alpha - 2009-01-20
18232 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
18233 week it will take a long time to bootstrap again" bug. It also fixes
18234 an important security-related bug reported by Ilja van Sprundel. You
18235 should upgrade. (We'll send out more details about the bug once people
18236 have had some time to upgrade.)
18239 - Fix a heap-corruption bug that may be remotely triggerable on
18240 some platforms. Reported by Ilja van Sprundel.
18243 - Discard router descriptors as we load them if they are more than
18244 five days old. Otherwise if Tor is off for a long time and then
18245 starts with cached descriptors, it will try to use the onion
18246 keys in those obsolete descriptors when building circuits. Bugfix
18247 on 0.2.0.x. Fixes bug 887.
18250 - Try to make sure that the version of Libevent we're running with
18251 is binary-compatible with the one we built with. May address bug
18253 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
18254 for bug 905. Bugfix on 0.2.1.7-alpha.
18255 - Add a new --enable-local-appdata configuration switch to change
18256 the default location of the datadir on win32 from APPDATA to
18257 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
18258 entirely. Patch from coderman.
18261 - Make outbound DNS packets respect the OutboundBindAddress setting.
18262 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
18263 - When our circuit fails at the first hop (e.g. we get a destroy
18264 cell back), avoid using that OR connection anymore, and also
18265 tell all the one-hop directory requests waiting for it that they
18266 should fail. Bugfix on 0.2.1.3-alpha.
18267 - In the torify(1) manpage, mention that tsocks will leak your
18271 Changes in version 0.2.1.10-alpha - 2009-01-06
18272 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
18273 would make the bridge relay not so useful if it had DirPort set to 0,
18274 and one that could let an attacker learn a little bit of information
18275 about the bridge's users), and a bug that would cause your Tor relay
18276 to ignore a circuit create request it can't decrypt (rather than reply
18277 with an error). It also fixes a wide variety of other bugs.
18280 - If the cached networkstatus consensus is more than five days old,
18281 discard it rather than trying to use it. In theory it could
18282 be useful because it lists alternate directory mirrors, but in
18283 practice it just means we spend many minutes trying directory
18284 mirrors that are long gone from the network. Helps bug 887 a bit;
18286 - Bridge relays that had DirPort set to 0 would stop fetching
18287 descriptors shortly after startup, and then briefly resume
18288 after a new bandwidth test and/or after publishing a new bridge
18289 descriptor. Bridge users that try to bootstrap from them would
18290 get a recent networkstatus but would get descriptors from up to
18291 18 hours earlier, meaning most of the descriptors were obsolete
18292 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
18293 - Prevent bridge relays from serving their 'extrainfo' document
18294 to anybody who asks, now that extrainfo docs include potentially
18295 sensitive aggregated client geoip summaries. Bugfix on
18299 - New controller event "clients_seen" to report a geoip-based summary
18300 of which countries we've seen clients from recently. Now controllers
18301 like Vidalia can show bridge operators that they're actually making
18303 - Build correctly against versions of OpenSSL 0.9.8 or later built
18304 without support for deprecated functions.
18305 - Update to the "December 19 2008" ip-to-country file.
18307 o Minor bugfixes (on 0.2.0.x):
18308 - Authorities now vote for the Stable flag for any router whose
18309 weighted MTBF is at least 5 days, regardless of the mean MTBF.
18310 - Do not remove routers as too old if we do not have any consensus
18311 document. Bugfix on 0.2.0.7-alpha.
18312 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
18313 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
18314 - When an exit relay resolves a stream address to a local IP address,
18315 do not just keep retrying that same exit relay over and
18316 over. Instead, just close the stream. Addresses bug 872. Bugfix
18317 on 0.2.0.32. Patch from rovv.
18318 - If a hidden service sends us an END cell, do not consider
18319 retrying the connection; just close it. Patch from rovv.
18320 - When we made bridge authorities stop serving bridge descriptors over
18321 unencrypted links, we also broke DirPort reachability testing for
18322 bridges. So bridges with a non-zero DirPort were printing spurious
18323 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
18324 - When a relay gets a create cell it can't decrypt (e.g. because it's
18325 using the wrong onion key), we were dropping it and letting the
18326 client time out. Now actually answer with a destroy cell. Fixes
18327 bug 904. Bugfix on 0.0.2pre8.
18328 - Squeeze 2-5% out of client performance (according to oprofile) by
18329 improving the implementation of some policy-manipulation functions.
18331 o Minor bugfixes (on 0.2.1.x):
18332 - Make get_interface_address() function work properly again; stop
18333 guessing the wrong parts of our address as our address.
18334 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
18335 send on that circuit. Otherwise we might violate the proposal-110
18336 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
18338 - When we're sending non-EXTEND cells to the first hop in a circuit,
18339 for example to use an encrypted directory connection, we don't need
18340 to use RELAY_EARLY cells: the first hop knows what kind of cell
18341 it is, and nobody else can even see the cell type. Conserving
18342 RELAY_EARLY cells makes it easier to cannibalize circuits like
18344 - Stop logging nameserver addresses in reverse order.
18345 - If we are retrying a directory download slowly over and over, do
18346 not automatically give up after the 254th failure. Bugfix on
18348 - Resume reporting accurate "stream end" reasons to the local control
18349 port. They were lost in the changes for Proposal 148. Bugfix on
18352 o Deprecated and removed features:
18353 - The old "tor --version --version" command, which would print out
18354 the subversion "Id" of most of the source files, is now removed. It
18355 turned out to be less useful than we'd expected, and harder to
18358 o Code simplifications and refactoring:
18359 - Change our header file guard macros to be less likely to conflict
18360 with system headers. Adam Langley noticed that we were conflicting
18361 with log.h on Android.
18362 - Tool-assisted documentation cleanup. Nearly every function or
18363 static variable in Tor should have its own documentation now.
18366 Changes in version 0.2.1.9-alpha - 2008-12-25
18367 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
18369 o New directory authorities:
18370 - gabelmoo (the authority run by Karsten Loesing) now has a new
18374 - Never use a connection with a mismatched address to extend a
18375 circuit, unless that connection is canonical. A canonical
18376 connection is one whose address is authenticated by the router's
18377 identity key, either in a NETINFO cell or in a router descriptor.
18378 - Avoid a possible memory corruption bug when receiving hidden service
18379 descriptors. Bugfix on 0.2.1.6-alpha.
18382 - Fix a logic error that would automatically reject all but the first
18383 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
18384 part of bug 813/868. Bug spotted by coderman.
18385 - When a stream at an exit relay is in state "resolving" or
18386 "connecting" and it receives an "end" relay cell, the exit relay
18387 would silently ignore the end cell and not close the stream. If
18388 the client never closes the circuit, then the exit relay never
18389 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
18390 reported by "wood".
18391 - When we can't initialize DNS because the network is down, do not
18392 automatically stop Tor from starting. Instead, retry failed
18393 dns_init() every 10 minutes, and change the exit policy to reject
18394 *:* until one succeeds. Fixes bug 691.
18397 - Give a better error message when an overzealous init script says
18398 "sudo -u username tor --user username". Makes Bug 882 easier for
18400 - When a directory authority gives us a new guess for our IP address,
18401 log which authority we used. Hopefully this will help us debug
18402 the recent complaints about bad IP address guesses.
18403 - Detect svn revision properly when we're using git-svn.
18404 - Try not to open more than one descriptor-downloading connection
18405 to an authority at once. This should reduce load on directory
18406 authorities. Fixes bug 366.
18407 - Add cross-certification to newly generated certificates, so that
18408 a signing key is enough information to look up a certificate.
18409 Partial implementation of proposal 157.
18410 - Start serving certificates by <identity digest, signing key digest>
18411 pairs. Partial implementation of proposal 157.
18412 - Clients now never report any stream end reason except 'MISC'.
18413 Implements proposal 148.
18414 - On platforms with a maximum syslog string length, truncate syslog
18415 messages to that length ourselves, rather than relying on the
18416 system to do it for us.
18417 - Optimize out calls to time(NULL) that occur for every IO operation,
18418 or for every cell. On systems where time() is a slow syscall,
18419 this fix will be slightly helpful.
18420 - Exit servers can now answer resolve requests for ip6.arpa addresses.
18421 - When we download a descriptor that we then immediately (as
18422 a directory authority) reject, do not retry downloading it right
18423 away. Should save some bandwidth on authorities. Fix for bug
18424 888. Patch by Sebastian Hahn.
18425 - When a download gets us zero good descriptors, do not notify
18426 Tor that new directory information has arrived.
18427 - Avoid some nasty corner cases in the logic for marking connections
18428 as too old or obsolete or noncanonical for circuits. Partial
18431 o Minor features (controller):
18432 - New CONSENSUS_ARRIVED event to note when a new consensus has
18433 been fetched and validated.
18434 - When we realize that another process has modified our cached
18435 descriptors file, print out a more useful error message rather
18436 than triggering an assertion. Fixes bug 885. Patch from Karsten.
18437 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
18438 controllers to prevent SIGHUP from reloading the
18439 configuration. Fixes bug 856.
18442 - Resume using the correct "REASON=" stream when telling the
18443 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
18444 - When a canonical connection appears later in our internal list
18445 than a noncanonical one for a given OR ID, always use the
18446 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
18448 - Clip the MaxCircuitDirtiness config option to a minimum of 10
18449 seconds. Warn the user if lower values are given in the
18450 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
18451 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
18452 user if lower values are given in the configuration. Bugfix on
18453 0.1.1.17-rc. Patch by Sebastian.
18454 - Fix a race condition when freeing keys shared between main thread
18455 and CPU workers that could result in a memory leak. Bugfix on
18456 0.1.0.1-rc. Fixes bug 889.
18458 o Minor bugfixes (hidden services):
18459 - Do not throw away existing introduction points on SIGHUP (bugfix on
18460 0.0.6pre1); also, do not stall hidden services because we're
18461 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
18462 by John Brooks. Patch by Karsten. Fixes bug 874.
18463 - Fix a memory leak when we decline to add a v2 rendezvous
18464 descriptor to the cache because we already had a v0 descriptor
18465 with the same ID. Bugfix on 0.2.0.18-alpha.
18467 o Deprecated and removed features:
18468 - RedirectExits has been removed. It was deprecated since
18470 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
18471 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
18472 - Cell pools are now always enabled; --disable-cell-pools is ignored.
18474 o Code simplifications and refactoring:
18475 - Rename the confusing or_is_obsolete field to the more appropriate
18476 is_bad_for_new_circs, and move it to or_connection_t where it
18478 - Move edge-only flags from connection_t to edge_connection_t: not
18479 only is this better coding, but on machines of plausible alignment,
18480 it should save 4-8 bytes per connection_t. "Every little bit helps."
18481 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
18482 for consistency; keep old option working for backward compatibility.
18483 - Simplify the code for finding connections to use for a circuit.
18486 Changes in version 0.2.1.8-alpha - 2008-12-08
18487 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
18488 builds better on unusual platforms like Solaris and old OS X, and
18489 fixes a variety of other issues.
18492 - New DirPortFrontPage option that takes an html file and publishes
18493 it as "/" on the DirPort. Now relay operators can provide a
18494 disclaimer without needing to set up a separate webserver. There's
18495 a sample disclaimer in contrib/tor-exit-notice.html.
18498 - When the client is choosing entry guards, now it selects at most
18499 one guard from a given relay family. Otherwise we could end up with
18500 all of our entry points into the network run by the same operator.
18501 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
18504 - Fix a DOS opportunity during the voting signature collection process
18505 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
18506 - Fix a possible segfault when establishing an exit connection. Bugfix
18510 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
18512 - Made Tor a little less aggressive about deleting expired
18513 certificates. Partial fix for bug 854.
18514 - Stop doing unaligned memory access that generated bus errors on
18515 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
18516 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
18517 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
18518 - Make USR2 log-level switch take effect immediately. Bugfix on
18520 - If one win32 nameserver fails to get added, continue adding the
18521 rest, and don't automatically fail.
18522 - Use fcntl() for locking when flock() is not available. Should fix
18523 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
18524 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
18525 could make gcc generate non-functional binary search code. Bugfix
18527 - Build correctly on platforms without socklen_t.
18528 - Avoid potential crash on internal error during signature collection.
18529 Fixes bug 864. Patch from rovv.
18530 - Do not use C's stdio library for writing to log files. This will
18531 improve logging performance by a minute amount, and will stop
18532 leaking fds when our disk is full. Fixes bug 861.
18533 - Stop erroneous use of O_APPEND in cases where we did not in fact
18534 want to re-seek to the end of a file before every last write().
18535 - Correct handling of possible malformed authority signing key
18536 certificates with internal signature types. Fixes bug 880. Bugfix
18538 - Fix a hard-to-trigger resource leak when logging credential status.
18542 - Directory mirrors no longer fetch the v1 directory or
18543 running-routers files. They are obsolete, and nobody asks for them
18544 anymore. This is the first step to making v1 authorities obsolete.
18546 o Minor features (controller):
18547 - Return circuit purposes in response to GETINFO circuit-status. Fixes
18551 Changes in version 0.2.0.32 - 2008-11-20
18552 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
18553 packages (and maybe other packages) noticed by Theo de Raadt, fixes
18554 a smaller security flaw that might allow an attacker to access local
18555 services, further improves hidden service performance, and fixes a
18556 variety of other issues.
18559 - The "User" and "Group" config options did not clear the
18560 supplementary group entries for the Tor process. The "User" option
18561 is now more robust, and we now set the groups to the specified
18562 user's primary group. The "Group" option is now ignored. For more
18563 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
18564 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
18565 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
18566 - The "ClientDNSRejectInternalAddresses" config option wasn't being
18567 consistently obeyed: if an exit relay refuses a stream because its
18568 exit policy doesn't allow it, we would remember what IP address
18569 the relay said the destination address resolves to, even if it's
18570 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
18573 - Fix a DOS opportunity during the voting signature collection process
18574 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
18576 o Major bugfixes (hidden services):
18577 - When fetching v0 and v2 rendezvous service descriptors in parallel,
18578 we were failing the whole hidden service request when the v0
18579 descriptor fetch fails, even if the v2 fetch is still pending and
18580 might succeed. Similarly, if the last v2 fetch fails, we were
18581 failing the whole hidden service request even if a v0 fetch is
18582 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
18583 - When extending a circuit to a hidden service directory to upload a
18584 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
18585 requests failed, because the router descriptor has not been
18586 downloaded yet. In these cases, do not attempt to upload the
18587 rendezvous descriptor, but wait until the router descriptor is
18588 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
18589 descriptor from a hidden service directory for which the router
18590 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
18594 - Fix several infrequent memory leaks spotted by Coverity.
18595 - When testing for libevent functions, set the LDFLAGS variable
18596 correctly. Found by Riastradh.
18597 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
18598 bootstrapping with tunneled directory connections. Bugfix on
18599 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
18600 - When asked to connect to A.B.exit:80, if we don't know the IP for A
18601 and we know that server B rejects most-but-not all connections to
18602 port 80, we would previously reject the connection. Now, we assume
18603 the user knows what they were asking for. Fixes bug 752. Bugfix
18604 on 0.0.9rc5. Diagnosed by BarkerJr.
18605 - If we overrun our per-second write limits a little, count this as
18606 having used up our write allocation for the second, and choke
18607 outgoing directory writes. Previously, we had only counted this when
18608 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
18609 Bugfix on 0.2.0.x (??).
18610 - Remove the old v2 directory authority 'lefkada' from the default
18611 list. It has been gone for many months.
18612 - Stop doing unaligned memory access that generated bus errors on
18613 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
18614 - Make USR2 log-level switch take effect immediately. Bugfix on
18617 o Minor bugfixes (controller):
18618 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
18619 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
18622 Changes in version 0.2.1.7-alpha - 2008-11-08
18623 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
18624 packages (and maybe other packages) noticed by Theo de Raadt, fixes
18625 a smaller security flaw that might allow an attacker to access local
18626 services, adds better defense against DNS poisoning attacks on exit
18627 relays, further improves hidden service performance, and fixes a
18628 variety of other issues.
18631 - The "ClientDNSRejectInternalAddresses" config option wasn't being
18632 consistently obeyed: if an exit relay refuses a stream because its
18633 exit policy doesn't allow it, we would remember what IP address
18634 the relay said the destination address resolves to, even if it's
18635 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
18636 - The "User" and "Group" config options did not clear the
18637 supplementary group entries for the Tor process. The "User" option
18638 is now more robust, and we now set the groups to the specified
18639 user's primary group. The "Group" option is now ignored. For more
18640 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
18641 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
18642 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
18643 - Do not use or believe expired v3 authority certificates. Patch
18644 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
18647 - Now NodeFamily and MyFamily config options allow spaces in
18648 identity fingerprints, so it's easier to paste them in.
18649 Suggested by Lucky Green.
18650 - Implement the 0x20 hack to better resist DNS poisoning: set the
18651 case on outgoing DNS requests randomly, and reject responses that do
18652 not match the case correctly. This logic can be disabled with the
18653 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
18654 of servers that do not reliably preserve case in replies. See
18655 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
18657 - Preserve case in replies to DNSPort requests in order to support
18658 the 0x20 hack for resisting DNS poisoning attacks.
18660 o Hidden service performance improvements:
18661 - When the client launches an introduction circuit, retry with a
18662 new circuit after 30 seconds rather than 60 seconds.
18663 - Launch a second client-side introduction circuit in parallel
18664 after a delay of 15 seconds (based on work by Christian Wilms).
18665 - Hidden services start out building five intro circuits rather
18666 than three, and when the first three finish they publish a service
18667 descriptor using those. Now we publish our service descriptor much
18668 faster after restart.
18671 - Minor fix in the warning messages when you're having problems
18672 bootstrapping; also, be more forgiving of bootstrap problems when
18673 we're still making incremental progress on a given bootstrap phase.
18674 - When we're choosing an exit node for a circuit, and we have
18675 no pending streams, choose a good general exit rather than one that
18676 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
18677 - Send a valid END cell back when a client tries to connect to a
18678 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
18679 840. Patch from rovv.
18680 - If a broken client asks a non-exit router to connect somewhere,
18681 do not even do the DNS lookup before rejecting the connection.
18682 Fixes another case of bug 619. Patch from rovv.
18683 - Fix another case of assuming, when a specific exit is requested,
18684 that we know more than the user about what hosts it allows.
18685 Fixes another case of bug 752. Patch from rovv.
18686 - Check which hops rendezvous stream cells are associated with to
18687 prevent possible guess-the-streamid injection attacks from
18688 intermediate hops. Fixes another case of bug 446. Based on patch
18690 - Avoid using a negative right-shift when comparing 32-bit
18691 addresses. Possible fix for bug 845 and bug 811.
18692 - Make the assert_circuit_ok() function work correctly on circuits that
18693 have already been marked for close.
18694 - Fix read-off-the-end-of-string error in unit tests when decoding
18695 introduction points.
18696 - Fix uninitialized size field for memory area allocation: may improve
18697 memory performance during directory parsing.
18698 - Treat duplicate certificate fetches as failures, so that we do
18699 not try to re-fetch an expired certificate over and over and over.
18700 - Do not say we're fetching a certificate when we'll in fact skip it
18701 because of a pending download.
18704 Changes in version 0.2.1.6-alpha - 2008-09-30
18705 Tor 0.2.1.6-alpha further improves performance and robustness of
18706 hidden services, starts work on supporting per-country relay selection,
18707 and fixes a variety of smaller issues.
18710 - Implement proposal 121: make it possible to build hidden services
18711 that only certain clients are allowed to connect to. This is
18712 enforced at several points, so that unauthorized clients are unable
18713 to send INTRODUCE cells to the service, or even (depending on the
18714 type of authentication) to learn introduction points. This feature
18715 raises the bar for certain kinds of active attacks against hidden
18716 services. Code by Karsten Loesing.
18717 - Relays now store and serve v2 hidden service descriptors by default,
18718 i.e., the new default value for HidServDirectoryV2 is 1. This is
18719 the last step in proposal 114, which aims to make hidden service
18720 lookups more reliable.
18721 - Start work to allow node restrictions to include country codes. The
18722 syntax to exclude nodes in a country with country code XX is
18723 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
18724 refinement to decide what config options should take priority if
18725 you ask to both use a particular node and exclude it.
18726 - Allow ExitNodes list to include IP ranges and country codes, just
18727 like the Exclude*Nodes lists. Patch from Robert Hogan.
18730 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
18731 Tor to fail to start if you had it configured to use a bridge
18732 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
18733 - When extending a circuit to a hidden service directory to upload a
18734 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
18735 requests failed, because the router descriptor had not been
18736 downloaded yet. In these cases, we now wait until the router
18737 descriptor is downloaded, and then retry. Likewise, clients
18738 now skip over a hidden service directory if they don't yet have
18739 its router descriptor, rather than futilely requesting it and
18740 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
18742 - When fetching v0 and v2 rendezvous service descriptors in parallel,
18743 we were failing the whole hidden service request when the v0
18744 descriptor fetch fails, even if the v2 fetch is still pending and
18745 might succeed. Similarly, if the last v2 fetch fails, we were
18746 failing the whole hidden service request even if a v0 fetch is
18747 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
18748 - DNS replies need to have names matching their requests, but
18749 these names should be in the questions section, not necessarily
18750 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
18753 - Update to the "September 1 2008" ip-to-country file.
18754 - Allow ports 465 and 587 in the default exit policy again. We had
18755 rejected them in 0.1.0.15, because back in 2005 they were commonly
18756 misconfigured and ended up as spam targets. We hear they are better
18757 locked down these days.
18758 - Use a lockfile to make sure that two Tor processes are not
18759 simultaneously running with the same datadir.
18760 - Serve the latest v3 networkstatus consensus via the control
18761 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
18762 - Better logging about stability/reliability calculations on directory
18764 - Drop the requirement to have an open dir port for storing and
18765 serving v2 hidden service descriptors.
18766 - Directory authorities now serve a /tor/dbg-stability.txt URL to
18767 help debug WFU and MTBF calculations.
18768 - Implement most of Proposal 152: allow specialized servers to permit
18769 single-hop circuits, and clients to use those servers to build
18770 single-hop circuits when using a specialized controller. Patch
18771 from Josh Albrecht. Resolves feature request 768.
18772 - Add a -p option to tor-resolve for specifying the SOCKS port: some
18773 people find host:port too confusing.
18774 - Make TrackHostExit mappings expire a while after their last use, not
18775 after their creation. Patch from Robert Hogan.
18776 - Provide circuit purposes along with circuit events to the controller.
18779 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
18781 - Fixed some memory leaks -- some quite frequent, some almost
18782 impossible to trigger -- based on results from Coverity.
18783 - When testing for libevent functions, set the LDFLAGS variable
18784 correctly. Found by Riastradh.
18785 - Fix an assertion bug in parsing policy-related options; possible fix
18787 - Catch and report a few more bootstrapping failure cases when Tor
18788 fails to establish a TCP connection. Cleanup on 0.2.1.x.
18789 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
18790 bootstrapping with tunneled directory connections. Bugfix on
18791 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
18792 - When asked to connect to A.B.exit:80, if we don't know the IP for A
18793 and we know that server B rejects most-but-not all connections to
18794 port 80, we would previously reject the connection. Now, we assume
18795 the user knows what they were asking for. Fixes bug 752. Bugfix
18796 on 0.0.9rc5. Diagnosed by BarkerJr.
18797 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
18798 service directories if they have no advertised dir port. Bugfix
18800 - If we overrun our per-second write limits a little, count this as
18801 having used up our write allocation for the second, and choke
18802 outgoing directory writes. Previously, we had only counted this when
18803 we had met our limits precisely. Fixes bug 824. Patch by rovv.
18804 Bugfix on 0.2.0.x (??).
18805 - Avoid a "0 divided by 0" calculation when calculating router uptime
18806 at directory authorities. Bugfix on 0.2.0.8-alpha.
18807 - Make DNS resolved controller events into "CLOSED", not
18808 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
18810 - Fix a bug where an unreachable relay would establish enough
18811 reachability testing circuits to do a bandwidth test -- if
18812 we already have a connection to the middle hop of the testing
18813 circuit, then it could establish the last hop by using the existing
18814 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
18815 circuits no longer use entry guards in 0.2.1.3-alpha.
18816 - If we have correct permissions on $datadir, we complain to stdout
18817 and fail to start. But dangerous permissions on
18818 $datadir/cached-status/ would cause us to open a log and complain
18819 there. Now complain to stdout and fail to start in both cases. Fixes
18820 bug 820, reported by seeess.
18821 - Remove the old v2 directory authority 'lefkada' from the default
18822 list. It has been gone for many months.
18824 o Code simplifications and refactoring:
18825 - Revise the connection_new functions so that a more typesafe variant
18826 exists. This will work better with Coverity, and let us find any
18827 actual mistakes we're making here.
18828 - Refactor unit testing logic so that dmalloc can be used sensibly
18829 with unit tests to check for memory leaks.
18830 - Move all hidden-service related fields from connection and circuit
18831 structure to substructures: this way they won't eat so much memory.
18834 Changes in version 0.2.0.31 - 2008-09-03
18835 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
18836 a big bug we're seeing where in rare cases traffic from one Tor stream
18837 gets mixed into another stream, and fixes a variety of smaller issues.
18840 - Make sure that two circuits can never exist on the same connection
18841 with the same circuit ID, even if one is marked for close. This
18842 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
18843 - Relays now reject risky extend cells: if the extend cell includes
18844 a digest of all zeroes, or asks to extend back to the relay that
18845 sent the extend cell, tear down the circuit. Ideas suggested
18847 - If not enough of our entry guards are available so we add a new
18848 one, we might use the new one even if it overlapped with the
18849 current circuit's exit relay (or its family). Anonymity bugfix
18850 pointed out by rovv.
18853 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
18854 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
18855 - Correctly detect the presence of the linux/netfilter_ipv4.h header
18856 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
18857 - Pick size of default geoip filename string correctly on windows.
18858 Fixes bug 806. Bugfix on 0.2.0.30.
18859 - Make the autoconf script accept the obsolete --with-ssl-dir
18860 option as an alias for the actually-working --with-openssl-dir
18861 option. Fix the help documentation to recommend --with-openssl-dir.
18862 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
18863 - When using the TransPort option on OpenBSD, and using the User
18864 option to change UID and drop privileges, make sure to open
18865 /dev/pf before dropping privileges. Fixes bug 782. Patch from
18866 Christopher Davis. Bugfix on 0.1.2.1-alpha.
18867 - Try to attach connections immediately upon receiving a RENDEZVOUS2
18868 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
18869 on the client side when connecting to a hidden service. Bugfix
18870 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
18871 - When closing an application-side connection because its circuit is
18872 getting torn down, generate the stream event correctly. Bugfix on
18873 0.1.2.x. Anonymous patch.
18876 Changes in version 0.2.1.5-alpha - 2008-08-31
18877 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
18878 in a lot of the infrastructure for adding authorization to hidden
18879 services, lays the groundwork for having clients read their load
18880 balancing information out of the networkstatus consensus rather than
18881 the individual router descriptors, addresses two potential anonymity
18882 issues, and fixes a variety of smaller issues.
18885 - Convert many internal address representations to optionally hold
18887 - Generate and accept IPv6 addresses in many protocol elements.
18888 - Make resolver code handle nameservers located at ipv6 addresses.
18889 - Begin implementation of proposal 121 ("Client authorization for
18890 hidden services"): configure hidden services with client
18891 authorization, publish descriptors for them, and configure
18892 authorization data for hidden services at clients. The next
18893 step is to actually access hidden services that perform client
18895 - More progress toward proposal 141: Network status consensus
18896 documents and votes now contain bandwidth information for each
18897 router and a summary of that router's exit policy. Eventually this
18898 will be used by clients so that they do not have to download every
18899 known descriptor before building circuits.
18901 o Major bugfixes (on 0.2.0.x and before):
18902 - When sending CREATED cells back for a given circuit, use a 64-bit
18903 connection ID to find the right connection, rather than an addr:port
18904 combination. Now that we can have multiple OR connections between
18905 the same ORs, it is no longer possible to use addr:port to uniquely
18906 identify a connection.
18907 - Relays now reject risky extend cells: if the extend cell includes
18908 a digest of all zeroes, or asks to extend back to the relay that
18909 sent the extend cell, tear down the circuit. Ideas suggested
18911 - If not enough of our entry guards are available so we add a new
18912 one, we might use the new one even if it overlapped with the
18913 current circuit's exit relay (or its family). Anonymity bugfix
18914 pointed out by rovv.
18917 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
18918 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
18919 - When using the TransPort option on OpenBSD, and using the User
18920 option to change UID and drop privileges, make sure to open /dev/pf
18921 before dropping privileges. Fixes bug 782. Patch from Christopher
18922 Davis. Bugfix on 0.1.2.1-alpha.
18923 - Correctly detect the presence of the linux/netfilter_ipv4.h header
18924 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
18925 - Add a missing safe_str() call for a debug log message.
18926 - Use 64 bits instead of 32 bits for connection identifiers used with
18927 the controller protocol, to greatly reduce risk of identifier reuse.
18928 - Make the autoconf script accept the obsolete --with-ssl-dir
18929 option as an alias for the actually-working --with-openssl-dir
18930 option. Fix the help documentation to recommend --with-openssl-dir.
18931 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
18934 - Rate-limit too-many-sockets messages: when they happen, they happen
18935 a lot. Resolves bug 748.
18936 - Resist DNS poisoning a little better by making sure that names in
18937 answer sections match.
18938 - Print the SOCKS5 error message string as well as the error code
18939 when a tor-resolve request fails. Patch from Jacob.
18942 Changes in version 0.2.1.4-alpha - 2008-08-04
18943 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
18946 - The address part of exit policies was not correctly written
18947 to router descriptors. This generated router descriptors that failed
18948 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
18950 - Tor triggered a false assert when extending a circuit to a relay
18951 but we already have a connection open to that relay. Noticed by
18952 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
18955 - Fix a hidden service logging bug: in some edge cases, the router
18956 descriptor of a previously picked introduction point becomes
18957 obsolete and we need to give up on it rather than continually
18958 complaining that it has become obsolete. Observed by xiando. Bugfix
18961 o Removed features:
18962 - Take out the TestVia config option, since it was a workaround for
18963 a bug that was fixed in Tor 0.1.1.21.
18966 Changes in version 0.2.1.3-alpha - 2008-08-03
18967 Tor 0.2.1.3-alpha implements most of the pieces to prevent
18968 infinite-length circuit attacks (see proposal 110); fixes a bug that
18969 might cause exit relays to corrupt streams they send back; allows
18970 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
18971 ExcludeExitNodes config options; and fixes a big pile of bugs.
18973 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
18974 - Send a bootstrap problem "warn" event on the first problem if the
18975 reason is NO_ROUTE (that is, our network is down).
18978 - Implement most of proposal 110: The first K cells to be sent
18979 along a circuit are marked as special "early" cells; only K "early"
18980 cells will be allowed. Once this code is universal, we can block
18981 certain kinds of DOS attack by requiring that EXTEND commands must
18982 be sent using an "early" cell.
18985 - Try to attach connections immediately upon receiving a RENDEZVOUS2
18986 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
18987 on the client side when connecting to a hidden service. Bugfix
18988 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
18989 - Ensure that two circuits can never exist on the same connection
18990 with the same circuit ID, even if one is marked for close. This
18991 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
18994 - When relays do their initial bandwidth measurement, don't limit
18995 to just our entry guards for the test circuits. Otherwise we tend
18996 to have multiple test circuits going through a single entry guard,
18997 which makes our bandwidth test less accurate. Fixes part of bug 654;
18998 patch contributed by Josh Albrecht.
18999 - Add an ExcludeExitNodes option so users can list a set of nodes
19000 that should be be excluded from the exit node position, but
19001 allowed elsewhere. Implements proposal 151.
19002 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
19003 ExcludeNodes and ExcludeExitNodes lists.
19004 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
19005 be more efficient. Formerly it was quadratic in the number of
19006 servers; now it should be linear. Fixes bug 509.
19007 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
19008 and n_conn_id_digest fields into a separate structure that's
19009 only needed when the circuit has not yet attached to an n_conn.
19012 - Change the contrib/tor.logrotate script so it makes the new
19013 logs as "_tor:_tor" rather than the default, which is generally
19014 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
19015 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
19016 warnings (occasionally), but it can also cause the compiler to
19017 eliminate error-checking code. Suggested by Peter Gutmann.
19018 - When a hidden service is giving up on an introduction point candidate
19019 that was not included in the last published rendezvous descriptor,
19020 don't reschedule publication of the next descriptor. Fixes bug 763.
19022 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
19023 HiddenServiceExcludeNodes as obsolete: they never worked properly,
19024 and nobody claims to be using them. Fixes bug 754. Bugfix on
19025 0.1.0.1-rc. Patch from Christian Wilms.
19026 - Fix a small alignment and memory-wasting bug on buffer chunks.
19029 o Minor bugfixes (controller):
19030 - When closing an application-side connection because its circuit
19031 is getting torn down, generate the stream event correctly.
19032 Bugfix on 0.1.2.x. Anonymous patch.
19034 o Removed features:
19035 - Remove all backward-compatibility code to support relays running
19036 versions of Tor so old that they no longer work at all on the
19040 Changes in version 0.2.0.30 - 2008-07-15
19042 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
19043 warnings (occasionally), but it can also cause the compiler to
19044 eliminate error-checking code. Suggested by Peter Gutmann.
19047 Changes in version 0.2.0.29-rc - 2008-07-08
19048 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
19049 hidden-service performance bugs, and fixes a bunch of smaller bugs.
19052 - If you have more than one bridge but don't know their keys,
19053 you would only launch a request for the descriptor of the first one
19054 on your list. (Tor considered launching requests for the others, but
19055 found that it already had a connection on the way for $0000...0000
19056 so it didn't open another.) Bugfix on 0.2.0.x.
19057 - If you have more than one bridge but don't know their keys, and the
19058 connection to one of the bridges failed, you would cancel all
19059 pending bridge connections. (After all, they all have the same
19060 digest.) Bugfix on 0.2.0.x.
19061 - When a hidden service was trying to establish an introduction point,
19062 and Tor had built circuits preemptively for such purposes, we
19063 were ignoring all the preemptive circuits and launching a new one
19064 instead. Bugfix on 0.2.0.14-alpha.
19065 - When a hidden service was trying to establish an introduction point,
19066 and Tor *did* manage to reuse one of the preemptively built
19067 circuits, it didn't correctly remember which one it used,
19068 so it asked for another one soon after, until there were no
19069 more preemptive circuits, at which point it launched one from
19070 scratch. Bugfix on 0.0.9.x.
19071 - Make directory servers include the X-Your-Address-Is: http header in
19072 their responses even for begin_dir conns. Now clients who only
19073 ever use begin_dir connections still have a way to learn their IP
19074 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
19077 - Fix a macro/CPP interaction that was confusing some compilers:
19078 some GCCs don't like #if/#endif pairs inside macro arguments.
19080 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
19081 Fixes bug 704; fix from Steven Murdoch.
19082 - When opening /dev/null in finish_daemonize(), do not pass the
19083 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
19084 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
19085 - Correctly detect transparent proxy support on Linux hosts that
19086 require in.h to be included before netfilter_ipv4.h. Patch
19088 - Disallow session resumption attempts during the renegotiation
19089 stage of the v2 handshake protocol. Clients should never be trying
19090 session resumption at this point, but apparently some did, in
19091 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
19092 found by Geoff Goodell.
19095 Changes in version 0.2.1.2-alpha - 2008-06-20
19096 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
19097 make it easier to set up your own private Tor network; fixes several
19098 big bugs with using more than one bridge relay; fixes a big bug with
19099 offering hidden services quickly after Tor starts; and uses a better
19100 API for reporting potential bootstrapping problems to the controller.
19103 - New TestingTorNetwork config option to allow adjustment of
19104 previously constant values that, while reasonable, could slow
19105 bootstrapping. Implements proposal 135. Patch from Karsten.
19108 - If you have more than one bridge but don't know their digests,
19109 you would only learn a request for the descriptor of the first one
19110 on your list. (Tor considered launching requests for the others, but
19111 found that it already had a connection on the way for $0000...0000
19112 so it didn't open another.) Bugfix on 0.2.0.x.
19113 - If you have more than one bridge but don't know their digests,
19114 and the connection to one of the bridges failed, you would cancel
19115 all pending bridge connections. (After all, they all have the
19116 same digest.) Bugfix on 0.2.0.x.
19117 - When establishing a hidden service, introduction points that
19118 originate from cannibalized circuits are completely ignored and not
19119 included in rendezvous service descriptors. This might be another
19120 reason for delay in making a hidden service available. Bugfix
19121 from long ago (0.0.9.x?)
19124 - Allow OpenSSL to use dynamic locks if it wants.
19125 - When building a consensus, do not include routers that are down.
19126 This will cut down 30% to 40% on consensus size. Implements
19128 - In directory authorities' approved-routers files, allow
19129 fingerprints with or without space.
19130 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
19131 controller can query our current bootstrap state in case it attaches
19132 partway through and wants to catch up.
19133 - Send an initial "Starting" bootstrap status event, so we have a
19134 state to start out in.
19137 - Asking for a conditional consensus at .../consensus/<fingerprints>
19138 would crash a dirserver if it did not already have a
19139 consensus. Bugfix on 0.2.1.1-alpha.
19140 - Clean up some macro/CPP interactions: some GCC versions don't like
19141 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
19144 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
19145 - Directory authorities shouldn't complain about bootstrapping
19146 problems just because they do a lot of reachability testing and
19147 some of the connection attempts fail.
19148 - Start sending "count" and "recommendation" key/value pairs in
19149 bootstrap problem status events, so the controller can hear about
19150 problems even before Tor decides they're worth reporting for sure.
19151 - If you're using bridges, generate "bootstrap problem" warnings
19152 as soon as you run out of working bridges, rather than waiting
19153 for ten failures -- which will never happen if you have less than
19155 - If we close our OR connection because there's been a circuit
19156 pending on it for too long, we were telling our bootstrap status
19157 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
19160 Changes in version 0.2.1.1-alpha - 2008-06-13
19161 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
19162 were making the Tor process bloat especially on Linux; makes our TLS
19163 handshake blend in better; sends "bootstrap phase" status events to
19164 the controller, so it can keep the user informed of progress (and
19165 problems) fetching directory information and establishing circuits;
19166 and adds a variety of smaller features.
19169 - More work on making our TLS handshake blend in: modify the list
19170 of ciphers advertised by OpenSSL in client mode to even more
19171 closely resemble a common web browser. We cheat a little so that
19172 we can advertise ciphers that the locally installed OpenSSL doesn't
19174 - Start sending "bootstrap phase" status events to the controller,
19175 so it can keep the user informed of progress fetching directory
19176 information and establishing circuits. Also inform the controller
19177 if we think we're stuck at a particular bootstrap phase. Implements
19179 - Resume using OpenSSL's RAND_poll() for better (and more portable)
19180 cross-platform entropy collection again. We used to use it, then
19181 stopped using it because of a bug that could crash systems that
19182 called RAND_poll when they had a lot of fds open. It looks like the
19183 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
19184 at startup, and to call RAND_poll() when we reseed later only if
19185 we have a non-buggy OpenSSL version.
19188 - When we choose to abandon a new entry guard because we think our
19189 older ones might be better, close any circuits pending on that
19190 new entry guard connection. This fix should make us recover much
19191 faster when our network is down and then comes back. Bugfix on
19192 0.1.2.8-beta; found by lodger.
19194 o Memory fixes and improvements:
19195 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
19196 to avoid unused RAM in buffer chunks and memory pools.
19197 - Speed up parsing and cut down on memory fragmentation by using
19198 stack-style allocations for parsing directory objects. Previously,
19199 this accounted for over 40% of allocations from within Tor's code
19200 on a typical directory cache.
19201 - Use a Bloom filter rather than a digest-based set to track which
19202 descriptors we need to keep around when we're cleaning out old
19203 router descriptors. This speeds up the computation significantly,
19204 and may reduce fragmentation.
19205 - Reduce the default smartlist size from 32 to 16; it turns out that
19206 most smartlists hold around 8-12 elements tops.
19207 - Make dumpstats() log the fullness and size of openssl-internal
19209 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
19210 patch to their OpenSSL, turn it on to save memory on servers. This
19211 patch will (with any luck) get included in a mainline distribution
19213 - Never use OpenSSL compression: it wastes RAM and CPU trying to
19214 compress cells, which are basically all encrypted, compressed,
19218 - Stop reloading the router list from disk for no reason when we
19219 run out of reachable directory mirrors. Once upon a time reloading
19220 it would set the 'is_running' flag back to 1 for them. It hasn't
19221 done that for a long time.
19222 - In very rare situations new hidden service descriptors were
19223 published earlier than 30 seconds after the last change to the
19224 service. (We currently think that a hidden service descriptor
19225 that's been stable for 30 seconds is worth publishing.)
19228 - Allow separate log levels to be configured for different logging
19229 domains. For example, this allows one to log all notices, warnings,
19230 or errors, plus all memory management messages of level debug or
19231 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
19232 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
19233 and stop using a warning that had become unfixably verbose under
19235 - New --hush command-line option similar to --quiet. While --quiet
19236 disables all logging to the console on startup, --hush limits the
19237 output to messages of warning and error severity.
19238 - Servers support a new URL scheme for consensus downloads that
19239 allows the client to specify which authorities are trusted.
19240 The server then only sends the consensus if the client will trust
19241 it. Otherwise a 404 error is sent back. Clients use this
19242 new scheme when the server supports it (meaning it's running
19243 0.2.1.1-alpha or later). Implements proposal 134.
19244 - New configure/torrc options (--enable-geoip-stats,
19245 DirRecordUsageByCountry) to record how many IPs we've served
19246 directory info to in each country code, how many status documents
19247 total we've sent to each country code, and what share of the total
19248 directory requests we should expect to see.
19249 - Use the TLS1 hostname extension to more closely resemble browser
19251 - Lots of new unit tests.
19252 - Add a macro to implement the common pattern of iterating through
19253 two parallel lists in lockstep.
19256 Changes in version 0.2.0.28-rc - 2008-06-13
19257 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
19258 performance bug, and fixes a bunch of smaller bugs.
19261 - Fix a bug where, when we were choosing the 'end stream reason' to
19262 put in our relay end cell that we send to the exit relay, Tor
19263 clients on Windows were sometimes sending the wrong 'reason'. The
19264 anonymity problem is that exit relays may be able to guess whether
19265 the client is running Windows, thus helping partition the anonymity
19266 set. Down the road we should stop sending reasons to exit relays,
19267 or otherwise prevent future versions of this bug.
19270 - While setting up a hidden service, some valid introduction circuits
19271 were overlooked and abandoned. This might be the reason for
19272 the long delay in making a hidden service available. Bugfix on
19276 - Update to the "June 9 2008" ip-to-country file.
19277 - Run 'make test' as part of 'make dist', so we stop releasing so
19278 many development snapshots that fail their unit tests.
19281 - When we're checking if we have enough dir info for each relay
19282 to begin establishing circuits, make sure that we actually have
19283 the descriptor listed in the consensus, not just any descriptor.
19285 - Bridge relays no longer print "xx=0" in their extrainfo document
19286 for every single country code in the geoip db. Bugfix on
19288 - Only warn when we fail to load the geoip file if we were planning to
19289 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
19290 - If we change our MaxAdvertisedBandwidth and then reload torrc,
19291 Tor won't realize it should publish a new relay descriptor. Fixes
19292 bug 688, reported by mfr. Bugfix on 0.1.2.x.
19293 - When we haven't had any application requests lately, don't bother
19294 logging that we have expired a bunch of descriptors. Bugfix
19296 - Make relay cells written on a connection count as non-padding when
19297 tracking how long a connection has been in use. Bugfix on
19298 0.2.0.1-alpha. Spotted by lodger.
19299 - Fix unit tests in 0.2.0.27-rc.
19300 - Fix compile on Windows.
19303 Changes in version 0.2.0.27-rc - 2008-06-03
19304 Tor 0.2.0.27-rc adds a few features we left out of the earlier
19305 release candidates. In particular, we now include an IP-to-country
19306 GeoIP database, so controllers can easily look up what country a
19307 given relay is in, and so bridge relays can give us some sanitized
19308 summaries about which countries are making use of bridges. (See proposal
19309 126-geoip-fetching.txt for details.)
19312 - Include an IP-to-country GeoIP file in the tarball, so bridge
19313 relays can report sanitized summaries of the usage they're seeing.
19316 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
19317 Robert Hogan. Fixes the first part of bug 681.
19318 - Make bridge authorities never serve extrainfo docs.
19319 - Add support to detect Libevent versions in the 1.4.x series
19321 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
19322 - Include a new contrib/tor-exit-notice.html file that exit relay
19323 operators can put on their website to help reduce abuse queries.
19326 - When tunneling an encrypted directory connection, and its first
19327 circuit fails, do not leave it unattached and ask the controller
19328 to deal. Fixes the second part of bug 681.
19329 - Make bridge authorities correctly expire old extrainfo documents
19333 Changes in version 0.2.0.26-rc - 2008-05-13
19334 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
19335 in Debian's OpenSSL packages. All users running any 0.2.0.x version
19336 should upgrade, whether they're running Debian or not.
19338 o Major security fixes:
19339 - Use new V3 directory authority keys on the tor26, gabelmoo, and
19340 moria1 V3 directory authorities. The old keys were generated with
19341 a vulnerable version of Debian's OpenSSL package, and must be
19342 considered compromised. Other authorities' keys were not generated
19343 with an affected version of OpenSSL.
19346 - List authority signatures as "unrecognized" based on DirServer
19347 lines, not on cert cache. Bugfix on 0.2.0.x.
19350 - Add a new V3AuthUseLegacyKey option to make it easier for
19351 authorities to change their identity keys if they have to.
19354 Changes in version 0.2.0.25-rc - 2008-04-23
19355 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
19358 - Remember to initialize threading before initializing logging.
19359 Otherwise, many BSD-family implementations will crash hard on
19360 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
19363 - Authorities correctly free policies on bad servers on
19364 exit. Fixes bug 672. Bugfix on 0.2.0.x.
19367 Changes in version 0.2.0.24-rc - 2008-04-22
19368 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
19369 v3 directory authority, makes relays with dynamic IP addresses and no
19370 DirPort notice more quickly when their IP address changes, fixes a few
19371 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
19373 o New directory authorities:
19374 - Take lefkada out of the list of v3 directory authorities, since
19375 it has been down for months.
19376 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
19380 - Detect address changes more quickly on non-directory mirror
19381 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
19383 o Minor features (security):
19384 - Reject requests for reverse-dns lookup of names that are in
19385 a private address space. Patch from lodger.
19386 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
19389 o Minor bugfixes (crashes):
19390 - Avoid a rare assert that can trigger when Tor doesn't have much
19391 directory information yet and it tries to fetch a v2 hidden
19392 service descriptor. Fixes bug 651, reported by nwf.
19393 - Initialize log mutex before initializing dmalloc. Otherwise,
19394 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
19395 - Use recursive pthread mutexes in order to avoid deadlock when
19396 logging debug-level messages to a controller. Bug spotted by nwf,
19397 bugfix on 0.2.0.16-alpha.
19399 o Minor bugfixes (resource management):
19400 - Keep address policies from leaking memory: start their refcount
19401 at 1, not 2. Bugfix on 0.2.0.16-alpha.
19402 - Free authority certificates on exit, so they don't look like memory
19403 leaks. Bugfix on 0.2.0.19-alpha.
19404 - Free static hashtables for policy maps and for TLS connections on
19405 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
19406 - Avoid allocating extra space when computing consensuses on 64-bit
19407 platforms. Bug spotted by aakova.
19409 o Minor bugfixes (misc):
19410 - Do not read the configuration file when we've only been told to
19411 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
19412 based on patch from Sebastian Hahn.
19413 - Exit relays that are used as a client can now reach themselves
19414 using the .exit notation, rather than just launching an infinite
19415 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
19416 - When attempting to open a logfile fails, tell us why.
19417 - Fix a dumb bug that was preventing us from knowing that we should
19418 preemptively build circuits to handle expected directory requests.
19419 Fixes bug 660. Bugfix on 0.1.2.x.
19420 - Warn less verbosely about clock skew from netinfo cells from
19421 untrusted sources. Fixes bug 663.
19422 - Make controller stream events for DNS requests more consistent,
19423 by adding "new stream" events for DNS requests, and removing
19424 spurious "stream closed" events" for cached reverse resolves.
19425 Patch from mwenge. Fixes bug 646.
19426 - Correctly notify one-hop connections when a circuit build has
19427 failed. Possible fix for bug 669. Found by lodger.
19430 Changes in version 0.2.0.23-rc - 2008-03-24
19431 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
19432 makes bootstrapping faster if the first directory mirror you contact
19433 is down. The bundles also include the new Vidalia 0.1.2 release.
19436 - When a tunneled directory request is made to a directory server
19437 that's down, notice after 30 seconds rather than 120 seconds. Also,
19438 fail any begindir streams that are pending on it, so they can
19439 retry elsewhere. This was causing multi-minute delays on bootstrap.
19442 Changes in version 0.2.0.22-rc - 2008-03-18
19443 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
19444 enables encrypted directory connections by default for non-relays, fixes
19445 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
19446 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
19449 - Enable encrypted directory connections by default for non-relays,
19450 so censor tools that block Tor directory connections based on their
19451 plaintext patterns will no longer work. This means Tor works in
19452 certain censored countries by default again.
19455 - Make sure servers always request certificates from clients during
19456 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
19457 - Do not enter a CPU-eating loop when a connection is closed in
19458 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
19459 diagnosed by lodger; bugfix on 0.2.0.20-rc.
19460 - Fix assertion failure that could occur when a blocked circuit
19461 became unblocked, and it had pending client DNS requests. Bugfix
19462 on 0.2.0.1-alpha. Fixes bug 632.
19464 o Minor bugfixes (on 0.1.2.x):
19465 - Generate "STATUS_SERVER" events rather than misspelled
19466 "STATUS_SEVER" events. Caught by mwenge.
19467 - When counting the number of bytes written on a TLS connection,
19468 look at the BIO actually used for writing to the network, not
19469 at the BIO used (sometimes) to buffer data for the network.
19470 Looking at different BIOs could result in write counts on the
19471 order of ULONG_MAX. Fixes bug 614.
19472 - On Windows, correctly detect errors when listing the contents of
19473 a directory. Fix from lodger.
19475 o Minor bugfixes (on 0.2.0.x):
19476 - Downgrade "sslv3 alert handshake failure" message to INFO.
19477 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
19478 left BandwidthRate and BandwidthBurst at the default, we would be
19479 silently limited by those defaults. Now raise them to match the
19480 RelayBandwidth* values.
19481 - Fix the SVK version detection logic to work correctly on a branch.
19482 - Make --enable-openbsd-malloc work correctly on Linux with alpha
19483 CPUs. Fixes bug 625.
19484 - Logging functions now check that the passed severity is sane.
19485 - Use proper log levels in the testsuite call of
19486 get_interface_address6().
19487 - When using a nonstandard malloc, do not use the platform values for
19488 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
19489 - Make the openbsd malloc code use 8k pages on alpha CPUs and
19491 - Detect mismatched page sizes when using --enable-openbsd-malloc.
19492 - Avoid double-marked-for-close warning when certain kinds of invalid
19493 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
19494 for bug 617. Bugfix on 0.2.0.1-alpha.
19495 - Make sure that the "NULL-means-reject *:*" convention is followed by
19496 all the policy manipulation functions, avoiding some possible crash
19497 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
19498 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
19499 actually works, and doesn't warn about every single reverse lookup.
19500 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
19503 - Only log guard node status when guard node status has changed.
19504 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
19505 make "INFO" 75% less verbose.
19508 Changes in version 0.2.0.21-rc - 2008-03-02
19509 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
19510 makes Tor work well with Vidalia again, fixes a rare assert bug,
19511 and fixes a pair of more minor bugs. The bundles also include Vidalia
19512 0.1.0 and Torbutton 1.1.16.
19515 - The control port should declare that it requires password auth
19516 when HashedControlSessionPassword is set too. Patch from Matt Edman;
19517 bugfix on 0.2.0.20-rc. Fixes bug 615.
19518 - Downgrade assert in connection_buckets_decrement() to a log message.
19519 This may help us solve bug 614, and in any case will make its
19520 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
19521 - We were sometimes miscounting the number of bytes read from the
19522 network, causing our rate limiting to not be followed exactly.
19523 Bugfix on 0.2.0.16-alpha. Reported by lodger.
19526 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
19527 OpenSSL versions should have been working fine. Diagnosis and patch
19528 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
19529 Bugfix on 0.2.0.20-rc.
19532 Changes in version 0.2.0.20-rc - 2008-02-24
19533 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
19534 makes more progress towards normalizing Tor's TLS handshake, makes
19535 hidden services work better again, helps relays bootstrap if they don't
19536 know their IP address, adds optional support for linking in openbsd's
19537 allocator or tcmalloc, allows really fast relays to scale past 15000
19538 sockets, and fixes a bunch of minor bugs reported by Veracode.
19541 - Enable the revised TLS handshake based on the one designed by
19542 Steven Murdoch in proposal 124, as revised in proposal 130. It
19543 includes version negotiation for OR connections as described in
19544 proposal 105. The new handshake is meant to be harder for censors
19545 to fingerprint, and it adds the ability to detect certain kinds of
19546 man-in-the-middle traffic analysis attacks. The version negotiation
19547 feature will allow us to improve Tor's link protocol more safely
19549 - Choose which bridge to use proportional to its advertised bandwidth,
19550 rather than uniformly at random. This should speed up Tor for
19551 bridge users. Also do this for people who set StrictEntryNodes.
19552 - When a TrackHostExits-chosen exit fails too many times in a row,
19553 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
19556 - Resolved problems with (re-)fetching hidden service descriptors.
19557 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
19558 and 0.2.0.19-alpha.
19559 - If we only ever used Tor for hidden service lookups or posts, we
19560 would stop building circuits and start refusing connections after
19561 24 hours, since we falsely believed that Tor was dormant. Reported
19562 by nwf; bugfix on 0.1.2.x.
19563 - Servers that don't know their own IP address should go to the
19564 authorities for their first directory fetch, even if their DirPort
19565 is off or if they don't know they're reachable yet. This will help
19566 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
19567 - When counting the number of open sockets, count not only the number
19568 of sockets we have received from the socket() call, but also
19569 the number we've gotten from accept() and socketpair(). This bug
19570 made us fail to count all sockets that we were using for incoming
19571 connections. Bugfix on 0.2.0.x.
19572 - Fix code used to find strings within buffers, when those strings
19573 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
19574 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
19575 - Add a new __HashedControlSessionPassword option for controllers
19576 to use for one-off session password hashes that shouldn't get
19577 saved to disk by SAVECONF --- Vidalia users were accumulating a
19578 pile of HashedControlPassword lines in their torrc files, one for
19579 each time they had restarted Tor and then clicked Save. Make Tor
19580 automatically convert "HashedControlPassword" to this new option but
19581 only when it's given on the command line. Partial fix for bug 586.
19583 o Minor features (performance):
19584 - Tune parameters for cell pool allocation to minimize amount of
19586 - Add OpenBSD malloc code from phk as an optional malloc
19587 replacement on Linux: some glibc libraries do very poorly
19588 with Tor's memory allocation patterns. Pass
19589 --enable-openbsd-malloc to get the replacement malloc code.
19590 - Add a --with-tcmalloc option to the configure script to link
19591 against tcmalloc (if present). Does not yet search for
19592 non-system include paths.
19593 - Stop imposing an arbitrary maximum on the number of file descriptors
19594 used for busy servers. Bug reported by Olaf Selke; patch from
19597 o Minor features (other):
19598 - When SafeLogging is disabled, log addresses along with all TLS
19600 - When building with --enable-gcc-warnings, check for whether Apple's
19601 warning "-Wshorten-64-to-32" is available.
19602 - Add a --passphrase-fd argument to the tor-gencert command for
19605 o Minor bugfixes (memory leaks and code problems):
19606 - We were leaking a file descriptor if Tor started with a zero-length
19607 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
19608 - Detect size overflow in zlib code. Reported by Justin Ferguson and
19610 - We were comparing the raw BridgePassword entry with a base64'ed
19611 version of it, when handling a "/tor/networkstatus-bridges"
19612 directory request. Now compare correctly. Noticed by Veracode.
19613 - Recover from bad tracked-since value in MTBF-history file.
19614 Should fix bug 537.
19615 - Alter the code that tries to recover from unhandled write
19616 errors, to not try to flush onto a socket that's given us
19617 unhandled errors. Bugfix on 0.1.2.x.
19618 - Make Unix controlsockets work correctly on OpenBSD. Patch from
19619 tup. Bugfix on 0.2.0.3-alpha.
19621 o Minor bugfixes (other):
19622 - If we have an extra-info document for our server, always make
19623 it available on the control port, even if we haven't gotten
19624 a copy of it from an authority yet. Patch from mwenge.
19625 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
19626 - Directory mirrors no longer include a guess at the client's IP
19627 address if the connection appears to be coming from the same /24
19628 network; it was producing too many wrong guesses.
19629 - Make the new hidden service code respect the SafeLogging setting.
19630 Bugfix on 0.2.0.x. Patch from Karsten.
19631 - When starting as an authority, do not overwrite all certificates
19632 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
19633 - If we're trying to flush the last bytes on a connection (for
19634 example, when answering a directory request), reset the
19635 time-to-give-up timeout every time we manage to write something
19636 on the socket. Bugfix on 0.1.2.x.
19637 - Change the behavior of "getinfo status/good-server-descriptor"
19638 so it doesn't return failure when any authority disappears.
19639 - Even though the man page said that "TrackHostExits ." should
19640 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
19641 - Report TLS "zero return" case as a "clean close" and "IO error"
19642 as a "close". Stop calling closes "unexpected closes": existing
19643 Tors don't use SSL_close(), so having a connection close without
19644 the TLS shutdown handshake is hardly unexpected.
19645 - Send NAMESERVER_STATUS messages for a single failed nameserver
19648 o Code simplifications and refactoring:
19649 - Remove the tor_strpartition function: its logic was confused,
19650 and it was only used for one thing that could be implemented far
19654 Changes in version 0.2.0.19-alpha - 2008-02-09
19655 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
19656 handshake, makes path selection for relays more secure and IP address
19657 guessing more robust, and generally fixes a lot of bugs in preparation
19658 for calling the 0.2.0 branch stable.
19661 - Do not include recognizeable strings in the commonname part of
19662 Tor's x509 certificates.
19665 - If we're a relay, avoid picking ourselves as an introduction point,
19666 a rendezvous point, or as the final hop for internal circuits. Bug
19667 reported by taranis and lodger. Bugfix on 0.1.2.x.
19668 - Patch from "Andrew S. Lists" to catch when we contact a directory
19669 mirror at IP address X and he says we look like we're coming from
19670 IP address X. Bugfix on 0.1.2.x.
19672 o Minor features (security):
19673 - Be more paranoid about overwriting sensitive memory on free(),
19674 as a defensive programming tactic to ensure forward secrecy.
19676 o Minor features (directory authority):
19677 - Actually validate the options passed to AuthDirReject,
19678 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
19679 - Reject router descriptors with out-of-range bandwidthcapacity or
19680 bandwidthburst values.
19682 o Minor features (controller):
19683 - Reject controller commands over 1MB in length. This keeps rogue
19684 processes from running us out of memory.
19686 o Minor features (misc):
19687 - Give more descriptive well-formedness errors for out-of-range
19688 hidden service descriptor/protocol versions.
19689 - Make memory debugging information describe more about history
19690 of cell allocation, so we can help reduce our memory use.
19692 o Deprecated features (controller):
19693 - The status/version/num-versioning and status/version/num-concurring
19694 GETINFO options are no longer useful in the v3 directory protocol:
19695 treat them as deprecated, and warn when they're used.
19698 - When our consensus networkstatus has been expired for a while, stop
19699 being willing to build circuits using it. Fixes bug 401. Bugfix
19701 - Directory caches now fetch certificates from all authorities
19702 listed in a networkstatus consensus, even when they do not
19703 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
19704 - When connecting to a bridge without specifying its key, insert
19705 the connection into the identity-to-connection map as soon as
19706 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
19707 - Detect versions of OS X where malloc_good_size() is present in the
19708 library but never actually declared. Resolves bug 587. Bugfix
19710 - Stop incorrectly truncating zlib responses to directory authority
19711 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
19712 - Stop recommending that every server operator send mail to tor-ops.
19713 Resolves bug 597. Bugfix on 0.1.2.x.
19714 - Don't trigger an assert if we start a directory authority with a
19715 private IP address (like 127.0.0.1).
19716 - Avoid possible failures when generating a directory with routers
19717 with over-long versions strings, or too many flags set. Bugfix
19719 - If an attempt to launch a DNS resolve request over the control
19720 port fails because we have overrun the limit on the number of
19721 connections, tell the controller that the request has failed.
19722 - Avoid using too little bandwidth when our clock skips a few
19723 seconds. Bugfix on 0.1.2.x.
19724 - Fix shell error when warning about missing packages in configure
19725 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
19726 - Do not become confused when receiving a spurious VERSIONS-like
19727 cell from a confused v1 client. Bugfix on 0.2.0.x.
19728 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
19729 introduction points for a hidden service have failed. Patch from
19730 Karsten Loesing. Bugfix on 0.2.0.x.
19732 o Code simplifications and refactoring:
19733 - Remove some needless generality from cpuworker code, for improved
19735 - Stop overloading the circuit_t.onionskin field for both "onionskin
19736 from a CREATE cell that we are waiting for a cpuworker to be
19737 assigned" and "onionskin from an EXTEND cell that we are going to
19738 send to an OR as soon as we are connected". Might help with bug 600.
19739 - Add an in-place version of aes_crypt() so that we can avoid doing a
19740 needless memcpy() call on each cell payload.
19743 Changes in version 0.2.0.18-alpha - 2008-01-25
19744 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
19745 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
19746 that can warn or reject connections to ports generally associated with
19747 vulnerable-plaintext protocols.
19749 o New directory authorities:
19750 - Set up dannenberg (run by CCC) as the sixth v3 directory
19754 - Fix a major memory leak when attempting to use the v2 TLS
19755 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
19756 - We accidentally enabled the under-development v2 TLS handshake
19757 code, which was causing log entries like "TLS error while
19758 renegotiating handshake". Disable it again. Resolves bug 590.
19759 - We were computing the wrong Content-Length: header for directory
19760 responses that need to be compressed on the fly, causing clients
19761 asking for those items to always fail. Bugfix on 0.2.0.x; partially
19765 - Avoid going directly to the directory authorities even if you're a
19766 relay, if you haven't found yourself reachable yet or if you've
19767 decided not to advertise your dirport yet. Addresses bug 556.
19768 - If we've gone 12 hours since our last bandwidth check, and we
19769 estimate we have less than 50KB bandwidth capacity but we could
19770 handle more, do another bandwidth test.
19771 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
19772 Tor can warn and/or refuse connections to ports commonly used with
19773 vulnerable-plaintext protocols. Currently we warn on ports 23,
19774 109, 110, and 143, but we don't reject any.
19777 - When we setconf ClientOnly to 1, close any current OR and Dir
19778 listeners. Reported by mwenge.
19779 - When we get a consensus that's been signed by more people than
19780 we expect, don't log about it; it's not a big deal. Reported
19784 - Don't answer "/tor/networkstatus-bridges" directory requests if
19785 the request isn't encrypted.
19786 - Make "ClientOnly 1" config option disable directory ports too.
19787 - Patches from Karsten Loesing to make v2 hidden services more
19788 robust: work even when there aren't enough HSDir relays available;
19789 retry when a v2 rend desc fetch fails; but don't retry if we
19790 already have a usable v0 rend desc.
19793 Changes in version 0.2.0.17-alpha - 2008-01-17
19794 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
19797 - Make the tor-gencert man page get included correctly in the tarball.
19800 Changes in version 0.2.0.16-alpha - 2008-01-17
19801 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
19802 Loesing, and generally cleans up a lot of features and minor bugs.
19804 o New directory authorities:
19805 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
19808 o Major performance improvements:
19809 - Switch our old ring buffer implementation for one more like that
19810 used by free Unix kernels. The wasted space in a buffer with 1mb
19811 of data will now be more like 8k than 1mb. The new implementation
19812 also avoids realloc();realloc(); patterns that can contribute to
19813 memory fragmentation.
19816 - Configuration files now accept C-style strings as values. This
19817 helps encode characters not allowed in the current configuration
19818 file format, such as newline or #. Addresses bug 557.
19819 - Although we fixed bug 539 (where servers would send HTTP status 503
19820 responses _and_ send a body too), there are still servers out
19821 there that haven't upgraded. Therefore, make clients parse such
19822 bodies when they receive them.
19823 - When we're not serving v2 directory information, there is no reason
19824 to actually keep any around. Remove the obsolete files and directory
19825 on startup if they are very old and we aren't going to serve them.
19827 o Minor performance improvements:
19828 - Reference-count and share copies of address policy entries; only 5%
19829 of them were actually distinct.
19830 - Never walk through the list of logs if we know that no log is
19831 interested in a given message.
19834 - When an authority has not signed a consensus, do not try to
19835 download a nonexistent "certificate with key 00000000". Bugfix
19836 on 0.2.0.x. Fixes bug 569.
19837 - Fix a rare assert error when we're closing one of our threads:
19838 use a mutex to protect the list of logs, so we never write to the
19839 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
19840 bug 575, which is kind of the revenge of bug 222.
19841 - Patch from Karsten Loesing to complain less at both the client
19842 and the relay when a relay used to have the HSDir flag but doesn't
19843 anymore, and we try to upload a hidden service descriptor.
19844 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
19846 - Do not try to download missing certificates until we have tried
19847 to check our fallback consensus. Fixes bug 583.
19848 - Make bridges round reported GeoIP stats info up to the nearest
19849 estimate, not down. Now we can distinguish between "0 people from
19850 this country" and "1 person from this country".
19851 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
19852 - Avoid possible segfault if key generation fails in
19853 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
19854 - Avoid segfault in the case where a badly behaved v2 versioning
19855 directory sends a signed networkstatus with missing client-versions.
19857 - Avoid segfaults on certain complex invocations of
19858 router_get_by_hexdigest(). Bugfix on 0.1.2.
19859 - Correct bad index on array access in parse_http_time(). Bugfix
19861 - Fix possible bug in vote generation when server versions are present
19862 but client versions are not.
19863 - Fix rare bug on REDIRECTSTREAM control command when called with no
19864 port set: it could erroneously report an error when none had
19866 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
19867 compressing large objects and find ourselves with more than 4k
19868 left over. Bugfix on 0.2.0.
19869 - Fix a small memory leak when setting up a hidden service.
19870 - Fix a few memory leaks that could in theory happen under bizarre
19872 - Fix an assert if we post a general-purpose descriptor via the
19873 control port but that descriptor isn't mentioned in our current
19874 network consensus. Bug reported by Jon McLachlan; bugfix on
19877 o Minor features (controller):
19878 - Get NS events working again. Patch from tup.
19879 - The GETCONF command now escapes and quotes configuration values
19880 that don't otherwise fit into the torrc file.
19881 - The SETCONF command now handles quoted values correctly.
19883 o Minor features (directory authorities):
19884 - New configuration options to override default maximum number of
19885 servers allowed on a single IP address. This is important for
19886 running a test network on a single host.
19887 - Actually implement the -s option to tor-gencert.
19888 - Add a manual page for tor-gencert.
19890 o Minor features (bridges):
19891 - Bridge authorities no longer serve bridge descriptors over
19892 unencrypted connections.
19894 o Minor features (other):
19895 - Add hidden services and DNSPorts to the list of things that make
19896 Tor accept that it has running ports. Change starting Tor with no
19897 ports from a fatal error to a warning; we might change it back if
19898 this turns out to confuse anybody. Fixes bug 579.
19901 Changes in version 0.1.2.19 - 2008-01-17
19902 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
19903 exit policy a little bit more conservative so it's safer to run an
19904 exit relay on a home system, and fixes a variety of smaller issues.
19907 - Exit policies now reject connections that are addressed to a
19908 relay's public (external) IP address too, unless
19909 ExitPolicyRejectPrivate is turned off. We do this because too
19910 many relays are running nearby to services that trust them based
19911 on network address.
19914 - When the clock jumps forward a lot, do not allow the bandwidth
19915 buckets to become negative. Fixes bug 544.
19916 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
19917 on every successful resolve. Reported by Mike Perry.
19918 - Purge old entries from the "rephist" database and the hidden
19919 service descriptor database even when DirPort is zero.
19920 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
19921 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
19922 crashing or mis-answering these requests.
19923 - When we decide to send a 503 response to a request for servers, do
19924 not then also send the server descriptors: this defeats the whole
19925 purpose. Fixes bug 539.
19928 - Changing the ExitPolicyRejectPrivate setting should cause us to
19929 rebuild our server descriptor.
19930 - Fix handling of hex nicknames when answering controller requests for
19931 networkstatus by name, or when deciding whether to warn about
19932 unknown routers in a config option. (Patch from mwenge.)
19933 - Fix a couple of hard-to-trigger autoconf problems that could result
19934 in really weird results on platforms whose sys/types.h files define
19935 nonstandard integer types.
19936 - Don't try to create the datadir when running --verify-config or
19937 --hash-password. Resolves bug 540.
19938 - If we were having problems getting a particular descriptor from the
19939 directory caches, and then we learned about a new descriptor for
19940 that router, we weren't resetting our failure count. Reported
19942 - Although we fixed bug 539 (where servers would send HTTP status 503
19943 responses _and_ send a body too), there are still servers out there
19944 that haven't upgraded. Therefore, make clients parse such bodies
19945 when they receive them.
19946 - Run correctly on systems where rlim_t is larger than unsigned long.
19947 This includes some 64-bit systems.
19948 - Run correctly on platforms (like some versions of OS X 10.5) where
19949 the real limit for number of open files is OPEN_FILES, not rlim_max
19950 from getrlimit(RLIMIT_NOFILES).
19951 - Avoid a spurious free on base64 failure.
19952 - Avoid segfaults on certain complex invocations of
19953 router_get_by_hexdigest().
19954 - Fix rare bug on REDIRECTSTREAM control command when called with no
19955 port set: it could erroneously report an error when none had
19959 Changes in version 0.2.0.15-alpha - 2007-12-25
19960 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
19961 features added in 0.2.0.13-alpha.
19964 - Fix several remotely triggerable asserts based on DirPort requests
19965 for a v2 or v3 networkstatus object before we were prepared. This
19966 was particularly bad for 0.2.0.13 and later bridge relays, who
19967 would never have a v2 networkstatus and would thus always crash
19968 when used. Bugfixes on 0.2.0.x.
19969 - Estimate the v3 networkstatus size more accurately, rather than
19970 estimating it at zero bytes and giving it artificially high priority
19971 compared to other directory requests. Bugfix on 0.2.0.x.
19974 - Fix configure.in logic for cross-compilation.
19975 - When we load a bridge descriptor from the cache, and it was
19976 previously unreachable, mark it as retriable so we won't just
19977 ignore it. Also, try fetching a new copy immediately. Bugfixes
19979 - The bridge GeoIP stats were counting other relays, for example
19980 self-reachability and authority-reachability tests.
19983 - Support compilation to target iPhone; patch from cjacker huang.
19984 To build for iPhone, pass the --enable-iphone option to configure.
19987 Changes in version 0.2.0.14-alpha - 2007-12-23
19989 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
19990 without a datadirectory from a previous Tor install. Reported
19992 - Fix a crash when we fetch a descriptor that turns out to be
19993 unexpected (it used to be in our networkstatus when we started
19994 fetching it, but it isn't in our current networkstatus), and we
19995 aren't using bridges. Bugfix on 0.2.0.x.
19996 - Fix a crash when accessing hidden services: it would work the first
19997 time you use a given introduction point for your service, but
19998 on subsequent requests we'd be using garbage memory. Fixed by
19999 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
20000 - Fix a crash when we load a bridge descriptor from disk but we don't
20001 currently have a Bridge line for it in our torrc. Bugfix on
20005 - If bridge authorities set BridgePassword, they will serve a
20006 snapshot of known bridge routerstatuses from their DirPort to
20007 anybody who knows that password. Unset by default.
20010 - Make the unit tests build again.
20011 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
20012 - Make PublishServerDescriptor default to 1, so the default doesn't
20013 have to change as we invent new directory protocol versions.
20014 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
20015 be included unless sys/time.h is already included. Fixes
20016 bug 553. Bugfix on 0.2.0.x.
20017 - If we receive a general-purpose descriptor and then receive an
20018 identical bridge-purpose descriptor soon after, don't discard
20019 the next one as a duplicate.
20022 - If BridgeRelay is set to 1, then the default for
20023 PublishServerDescriptor is now "bridge" rather than "v2,v3".
20024 - If the user sets RelayBandwidthRate but doesn't set
20025 RelayBandwidthBurst, then make them equal rather than erroring out.
20028 Changes in version 0.2.0.13-alpha - 2007-12-21
20029 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
20030 Goodell, fixes many more bugs, and adds a lot of infrastructure for
20033 o New directory authorities:
20034 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
20038 - Only update guard status (usable / not usable) once we have
20039 enough directory information. This was causing us to always pick
20040 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
20041 causing us to discard all our guards on startup if we hadn't been
20042 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
20043 - Purge old entries from the "rephist" database and the hidden
20044 service descriptor databases even when DirPort is zero. Bugfix
20046 - We were ignoring our RelayBandwidthRate for the first 30 seconds
20047 after opening a circuit -- even a relayed circuit. Bugfix on
20049 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
20050 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
20051 crashing or mis-answering these types of requests.
20052 - Relays were publishing their server descriptor to v1 and v2
20053 directory authorities, but they didn't try publishing to v3-only
20054 authorities. Fix this; and also stop publishing to v1 authorities.
20056 - When we were reading router descriptors from cache, we were ignoring
20057 the annotations -- so for example we were reading in bridge-purpose
20058 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
20059 - When we decided to send a 503 response to a request for servers, we
20060 were then also sending the server descriptors: this defeats the
20061 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
20064 - Bridge relays now behave like clients with respect to time
20065 intervals for downloading new consensus documents -- otherwise they
20066 stand out. Bridge users now wait until the end of the interval,
20067 so their bridge relay will be sure to have a new consensus document.
20068 - Three new config options (AlternateDirAuthority,
20069 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
20070 user selectively replace the default directory authorities by type,
20071 rather than the all-or-nothing replacement that DirServer offers.
20072 - Tor can now be configured to read a GeoIP file from disk in one
20073 of two formats. This can be used by controllers to map IP addresses
20074 to countries. Eventually, it may support exit-by-country.
20075 - When possible, bridge relays remember which countries users
20076 are coming from, and report aggregate information in their
20077 extra-info documents, so that the bridge authorities can learn
20078 where Tor is blocked.
20079 - Bridge directory authorities now do reachability testing on the
20080 bridges they know. They provide router status summaries to the
20081 controller via "getinfo ns/purpose/bridge", and also dump summaries
20082 to a file periodically.
20083 - Stop fetching directory info so aggressively if your DirPort is
20084 on but your ORPort is off; stop fetching v2 dir info entirely.
20085 You can override these choices with the new FetchDirInfoEarly
20089 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
20090 consensus documents when there are too many relays at a single
20091 IP address. Now clear it in v2 network status documents too, and
20092 also clear it in routerinfo_t when the relay is no longer listed
20093 in the relevant networkstatus document.
20094 - Don't crash if we get an unexpected value for the
20095 PublishServerDescriptor config option. Reported by Matt Edman;
20096 bugfix on 0.2.0.9-alpha.
20097 - Our new v2 hidden service descriptor format allows descriptors
20098 that have no introduction points. But Tor crashed when we tried
20099 to build a descriptor with no intro points (and it would have
20100 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
20101 by Karsten Loesing.
20102 - Fix building with dmalloc 5.5.2 with glibc.
20103 - Reject uploaded descriptors and extrainfo documents if they're
20104 huge. Otherwise we'll cache them all over the network and it'll
20105 clog everything up. Reported by Aljosha Judmayer.
20106 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
20107 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
20108 - When the DANGEROUS_VERSION controller status event told us we're
20109 running an obsolete version, it used the string "OLD" to describe
20110 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
20111 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
20112 - If we can't expand our list of entry guards (e.g. because we're
20113 using bridges or we have StrictEntryNodes set), don't mark relays
20114 down when they fail a directory request. Otherwise we're too quick
20115 to mark all our entry points down. Bugfix on 0.1.2.x.
20116 - Fix handling of hex nicknames when answering controller requests for
20117 networkstatus by name, or when deciding whether to warn about unknown
20118 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
20119 - Fix a couple of hard-to-trigger autoconf problems that could result
20120 in really weird results on platforms whose sys/types.h files define
20121 nonstandard integer types. Bugfix on 0.1.2.x.
20122 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
20123 - Don't crash on name lookup when we have no current consensus. Fixes
20124 bug 538; bugfix on 0.2.0.x.
20125 - Only Tors that want to mirror the v2 directory info should
20126 create the "cached-status" directory in their datadir. (All Tors
20127 used to create it.) Bugfix on 0.2.0.9-alpha.
20128 - Directory authorities should only automatically download Extra Info
20129 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
20132 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
20133 consumers. (We already do this on HUP.)
20134 - Authorities and caches fetch the v2 networkstatus documents
20135 less often, now that v3 is encouraged.
20136 - Add a new config option BridgeRelay that specifies you want to
20137 be a bridge relay. Right now the only difference is that it makes
20138 you answer begin_dir requests, and it makes you cache dir info,
20139 even if your DirPort isn't on.
20140 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
20141 ask about source, timestamp of arrival, purpose, etc. We need
20142 something like this to help Vidalia not do GeoIP lookups on bridge
20144 - Allow multiple HashedControlPassword config lines, to support
20145 multiple controller passwords.
20146 - Authorities now decide whether they're authoritative for a given
20147 router based on the router's purpose.
20148 - New config options AuthDirBadDir and AuthDirListBadDirs for
20149 authorities to mark certain relays as "bad directories" in the
20150 networkstatus documents. Also supports the "!baddir" directive in
20151 the approved-routers file.
20154 Changes in version 0.2.0.12-alpha - 2007-11-16
20155 This twelfth development snapshot fixes some more build problems as
20156 well as a few minor bugs.
20159 - Make it build on OpenBSD again. Patch from tup.
20160 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
20161 package-building for Red Hat, OS X, etc.
20163 o Minor bugfixes (on 0.1.2.x):
20164 - Changing the ExitPolicyRejectPrivate setting should cause us to
20165 rebuild our server descriptor.
20167 o Minor bugfixes (on 0.2.0.x):
20168 - When we're lacking a consensus, don't try to perform rendezvous
20169 operations. Reported by Karsten Loesing.
20170 - Fix a small memory leak whenever we decide against using a
20171 newly picked entry guard. Reported by Mike Perry.
20172 - When authorities detected more than two relays running on the same
20173 IP address, they were clearing all the status flags but forgetting
20174 to clear the "hsdir" flag. So clients were being told that a
20175 given relay was the right choice for a v2 hsdir lookup, yet they
20176 never had its descriptor because it was marked as 'not running'
20178 - If we're trying to fetch a bridge descriptor and there's no way
20179 the bridge authority could help us (for example, we don't know
20180 a digest, or there is no bridge authority), don't be so eager to
20181 fall back to asking the bridge authority.
20182 - If we're using bridges or have strictentrynodes set, and our
20183 chosen exit is in the same family as all our bridges/entry guards,
20184 then be flexible about families.
20187 - When we negotiate a v2 link-layer connection (not yet implemented),
20188 accept RELAY_EARLY cells and turn them into RELAY cells if we've
20189 negotiated a v1 connection for their next step. Initial code for
20193 Changes in version 0.2.0.11-alpha - 2007-11-12
20194 This eleventh development snapshot fixes some build problems with
20195 the previous snapshot. It also includes a more secure-by-default exit
20196 policy for relays, fixes an enormous memory leak for exit relays, and
20197 fixes another bug where servers were falling out of the directory list.
20200 - Exit policies now reject connections that are addressed to a
20201 relay's public (external) IP address too, unless
20202 ExitPolicyRejectPrivate is turned off. We do this because too
20203 many relays are running nearby to services that trust them based
20204 on network address. Bugfix on 0.1.2.x.
20207 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
20208 on every successful resolve. Reported by Mike Perry; bugfix
20210 - On authorities, never downgrade to old router descriptors simply
20211 because they're listed in the consensus. This created a catch-22
20212 where we wouldn't list a new descriptor because there was an
20213 old one in the consensus, and we couldn't get the new one in the
20214 consensus because we wouldn't list it. Possible fix for bug 548.
20215 Also, this might cause bug 543 to appear on authorities; if so,
20216 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
20218 o Packaging fixes on 0.2.0.10-alpha:
20219 - We were including instructions about what to do with the
20220 src/config/fallback-consensus file, but we weren't actually
20221 including it in the tarball. Disable all of that for now.
20224 - Allow people to say PreferTunnelledDirConns rather than
20225 PreferTunneledDirConns, for those alternate-spellers out there.
20228 - Don't reevaluate all the information from our consensus document
20229 just because we've downloaded a v2 networkstatus that we intend
20230 to cache. Fixes bug 545; bugfix on 0.2.0.x.
20233 Changes in version 0.2.0.10-alpha - 2007-11-10
20234 This tenth development snapshot adds a third v3 directory authority
20235 run by Mike Perry, adds most of Karsten Loesing's new hidden service
20236 descriptor format, fixes a bad crash bug and new bridge bugs introduced
20237 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
20238 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
20239 addresses many more minor issues.
20241 o New directory authorities:
20242 - Set up ides (run by Mike Perry) as the third v3 directory authority.
20245 - Allow tunnelled directory connections to ask for an encrypted
20246 "begin_dir" connection or an anonymized "uses a full Tor circuit"
20247 connection independently. Now we can make anonymized begin_dir
20248 connections for (e.g.) more secure hidden service posting and
20250 - More progress on proposal 114: code from Karsten Loesing to
20251 implement new hidden service descriptor format.
20252 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
20253 accommodate the growing number of servers that use the default
20254 and are reaching it.
20255 - Directory authorities use a new formula for selecting which nodes
20256 to advertise as Guards: they must be in the top 7/8 in terms of
20257 how long we have known about them, and above the median of those
20258 nodes in terms of weighted fractional uptime.
20259 - Make "not enough dir info yet" warnings describe *why* Tor feels
20260 it doesn't have enough directory info yet.
20263 - Stop servers from crashing if they set a Family option (or
20264 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
20266 - Make bridge users work again -- the move to v3 directories in
20267 0.2.0.9-alpha had introduced a number of bugs that made bridges
20268 no longer work for clients.
20269 - When the clock jumps forward a lot, do not allow the bandwidth
20270 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
20272 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
20273 - When the consensus lists a router descriptor that we previously were
20274 mirroring, but that we considered non-canonical, reload the
20275 descriptor as canonical. This fixes bug 543 where Tor servers
20276 would start complaining after a few days that they don't have
20277 enough directory information to build a circuit.
20278 - Consider replacing the current consensus when certificates arrive
20279 that make the pending consensus valid. Previously, we were only
20280 considering replacement when the new certs _didn't_ help.
20281 - Fix an assert error on startup if we didn't already have the
20282 consensus and certs cached in our datadirectory: we were caching
20283 the consensus in consensus_waiting_for_certs but then free'ing it
20285 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
20286 Request) if we need more v3 certs but we've already got pending
20287 requests for all of them.
20288 - Correctly back off from failing certificate downloads. Fixes
20290 - Authorities don't vote on the Running flag if they have been running
20291 for less than 30 minutes themselves. Fixes bug 547, where a newly
20292 started authority would vote that everyone was down.
20294 o New requirements:
20295 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
20296 it, it had no AES, and it hasn't seen any security patches since
20300 - Clients now hold circuitless TLS connections open for 1.5 times
20301 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
20302 rebuild a new circuit over them within that timeframe. Previously,
20303 they held them open only for KeepalivePeriod (5 minutes).
20304 - Use "If-Modified-Since" to avoid retrieving consensus
20305 networkstatuses that we already have.
20306 - When we have no consensus, check FallbackNetworkstatusFile (defaults
20307 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
20308 we start knowing some directory caches.
20309 - When we receive a consensus from the future, warn about skew.
20310 - Improve skew reporting: try to give the user a better log message
20311 about how skewed they are, and how much this matters.
20312 - When we have a certificate for an authority, believe that
20313 certificate's claims about the authority's IP address.
20314 - New --quiet command-line option to suppress the default console log.
20315 Good in combination with --hash-password.
20316 - Authorities send back an X-Descriptor-Not-New header in response to
20317 an accepted-but-discarded descriptor upload. Partially implements
20319 - Make the log message for "tls error. breaking." more useful.
20320 - Better log messages about certificate downloads, to attempt to
20321 track down the second incarnation of bug 546.
20323 o Minor features (bridges):
20324 - If bridge users set UpdateBridgesFromAuthority, but the digest
20325 they ask for is a 404 from the bridge authority, they now fall
20326 back to trying the bridge directly.
20327 - Bridges now use begin_dir to publish their server descriptor to
20328 the bridge authority, even when they haven't set TunnelDirConns.
20330 o Minor features (controller):
20331 - When reporting clock skew, and we know that the clock is _at least
20332 as skewed_ as some value, but we don't know the actual value,
20333 report the value as a "minimum skew."
20336 - Update linux-tor-prio.sh script to allow QoS based on the uid of
20337 the Tor process. Patch from Marco Bonetti with tweaks from Mike
20341 - Refuse to start if both ORPort and UseBridges are set. Bugfix
20342 on 0.2.0.x, suggested by Matt Edman.
20343 - Don't stop fetching descriptors when FetchUselessDescriptors is
20344 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
20345 reported by tup and ioerror.
20346 - Better log message on vote from unknown authority.
20347 - Don't log "Launching 0 request for 0 router" message.
20349 o Minor bugfixes (memory leaks):
20350 - Stop leaking memory every time we parse a v3 certificate. Bugfix
20352 - Stop leaking memory every time we load a v3 certificate. Bugfix
20353 on 0.2.0.1-alpha. Fixes bug 536.
20354 - Stop leaking a cached networkstatus on exit. Bugfix on
20356 - Stop leaking voter information every time we free a consensus.
20357 Bugfix on 0.2.0.3-alpha.
20358 - Stop leaking signed data every time we check a voter signature.
20359 Bugfix on 0.2.0.3-alpha.
20360 - Stop leaking a signature every time we fail to parse a consensus or
20361 a vote. Bugfix on 0.2.0.3-alpha.
20362 - Stop leaking v2_download_status_map on shutdown. Bugfix on
20364 - Stop leaking conn->nickname every time we make a connection to a
20365 Tor relay without knowing its expected identity digest (e.g. when
20366 using bridges). Bugfix on 0.2.0.3-alpha.
20368 - Minor bugfixes (portability):
20369 - Run correctly on platforms where rlim_t is larger than unsigned
20370 long, and/or where the real limit for number of open files is
20371 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
20372 particular, these may be needed for OS X 10.5.
20375 Changes in version 0.1.2.18 - 2007-10-28
20376 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
20377 hidden service introduction that were causing huge delays, and a big
20378 bug that was causing some servers to disappear from the network status
20379 lists for a few hours each day.
20381 o Major bugfixes (crashes):
20382 - If a connection is shut down abruptly because of something that
20383 happened inside connection_flushed_some(), do not call
20384 connection_finished_flushing(). Should fix bug 451:
20385 "connection_stop_writing: Assertion conn->write_event failed"
20386 Bugfix on 0.1.2.7-alpha.
20387 - Fix possible segfaults in functions called from
20388 rend_process_relay_cell().
20390 o Major bugfixes (hidden services):
20391 - Hidden services were choosing introduction points uniquely by
20392 hexdigest, but when constructing the hidden service descriptor
20393 they merely wrote the (potentially ambiguous) nickname.
20394 - Clients now use the v2 intro format for hidden service
20395 connections: they specify their chosen rendezvous point by identity
20396 digest rather than by (potentially ambiguous) nickname. These
20397 changes could speed up hidden service connections dramatically.
20399 o Major bugfixes (other):
20400 - Stop publishing a new server descriptor just because we get a
20401 HUP signal. This led (in a roundabout way) to some servers getting
20402 dropped from the networkstatus lists for a few hours each day.
20403 - When looking for a circuit to cannibalize, consider family as well
20404 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
20405 circuit cannibalization).
20406 - When a router wasn't listed in a new networkstatus, we were leaving
20407 the flags for that router alone -- meaning it remained Named,
20408 Running, etc -- even though absence from the networkstatus means
20409 that it shouldn't be considered to exist at all anymore. Now we
20410 clear all the flags for routers that fall out of the networkstatus
20411 consensus. Fixes bug 529.
20414 - Don't try to access (or alter) the state file when running
20415 --list-fingerprint or --verify-config or --hash-password. Resolves
20417 - When generating information telling us how to extend to a given
20418 router, do not try to include the nickname if it is
20419 absent. Resolves bug 467.
20420 - Fix a user-triggerable segfault in expand_filename(). (There isn't
20421 a way to trigger this remotely.)
20422 - When sending a status event to the controller telling it that an
20423 OR address is reachable, set the port correctly. (Previously we
20424 were reporting the dir port.)
20425 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
20426 command. Bugfix on 0.1.2.17.
20427 - When loading bandwidth history, do not believe any information in
20428 the future. Fixes bug 434.
20429 - When loading entry guard information, do not believe any information
20431 - When we have our clock set far in the future and generate an
20432 onion key, then re-set our clock to be correct, we should not stop
20433 the onion key from getting rotated.
20434 - On some platforms, accept() can return a broken address. Detect
20435 this more quietly, and deal accordingly. Fixes bug 483.
20436 - It's not actually an error to find a non-pending entry in the DNS
20437 cache when canceling a pending resolve. Don't log unless stuff
20438 is fishy. Resolves bug 463.
20439 - Don't reset trusted dir server list when we set a configuration
20440 option. Patch from Robert Hogan.
20441 - Don't try to create the datadir when running --verify-config or
20442 --hash-password. Resolves bug 540.
20445 Changes in version 0.2.0.9-alpha - 2007-10-24
20446 This ninth development snapshot switches clients to the new v3 directory
20447 system; allows servers to be listed in the network status even when they
20448 have the same nickname as a registered server; and fixes many other
20449 bugs including a big one that was causing some servers to disappear
20450 from the network status lists for a few hours each day.
20452 o Major features (directory system):
20453 - Clients now download v3 consensus networkstatus documents instead
20454 of v2 networkstatus documents. Clients and caches now base their
20455 opinions about routers on these consensus documents. Clients only
20456 download router descriptors listed in the consensus.
20457 - Authorities now list servers who have the same nickname as
20458 a different named server, but list them with a new flag,
20459 "Unnamed". Now we can list servers that happen to pick the same
20460 nickname as a server that registered two years ago and then
20461 disappeared. Partially implements proposal 122.
20462 - If the consensus lists a router as "Unnamed", the name is assigned
20463 to a different router: do not identify the router by that name.
20464 Partially implements proposal 122.
20465 - Authorities can now come to a consensus on which method to use to
20466 compute the consensus. This gives us forward compatibility.
20469 - Stop publishing a new server descriptor just because we HUP or
20470 when we find our DirPort to be reachable but won't actually publish
20471 it. New descriptors without any real changes are dropped by the
20472 authorities, and can screw up our "publish every 18 hours" schedule.
20474 - When a router wasn't listed in a new networkstatus, we were leaving
20475 the flags for that router alone -- meaning it remained Named,
20476 Running, etc -- even though absence from the networkstatus means
20477 that it shouldn't be considered to exist at all anymore. Now we
20478 clear all the flags for routers that fall out of the networkstatus
20479 consensus. Fixes bug 529; bugfix on 0.1.2.x.
20480 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
20481 extrainfo documents and then discard them immediately for not
20482 matching the latest router. Bugfix on 0.2.0.1-alpha.
20484 o Minor features (v3 directory protocol):
20485 - Allow tor-gencert to generate a new certificate without replacing
20487 - Allow certificates to include an address.
20488 - When we change our directory-cache settings, reschedule all voting
20489 and download operations.
20490 - Reattempt certificate downloads immediately on failure, as long as
20491 we haven't failed a threshold number of times yet.
20492 - Delay retrying consensus downloads while we're downloading
20493 certificates to verify the one we just got. Also, count getting a
20494 consensus that we already have (or one that isn't valid) as a failure,
20495 and count failing to get the certificates after 20 minutes as a
20497 - Build circuits and download descriptors even if our consensus is a
20498 little expired. (This feature will go away once authorities are
20501 o Minor features (router descriptor cache):
20502 - If we find a cached-routers file that's been sitting around for more
20503 than 28 days unmodified, then most likely it's a leftover from
20504 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
20506 - When we (as a cache) download a descriptor because it was listed
20507 in a consensus, remember when the consensus was supposed to expire,
20508 and don't expire the descriptor until then.
20510 o Minor features (performance):
20511 - Call routerlist_remove_old_routers() much less often. This should
20512 speed startup, especially on directory caches.
20513 - Don't try to launch new descriptor downloads quite so often when we
20514 already have enough directory information to build circuits.
20515 - Base64 decoding was actually showing up on our profile when parsing
20516 the initial descriptor file; switch to an in-process all-at-once
20517 implementation that's about 3.5x times faster than calling out to
20520 o Minor features (compilation):
20521 - Detect non-ASCII platforms (if any still exist) and refuse to
20522 build there: some of our code assumes that 'A' is 65 and so on.
20524 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
20525 - Make the "next period" votes into "current period" votes immediately
20526 after publishing the consensus; avoid a heisenbug that made them
20527 stick around indefinitely.
20528 - When we discard a vote as a duplicate, do not report this as
20530 - Treat missing v3 keys or certificates as an error when running as a
20531 v3 directory authority.
20532 - When we're configured to be a v3 authority, but we're only listed
20533 as a non-v3 authority in our DirServer line for ourself, correct
20535 - If an authority doesn't have a qualified hostname, just put
20536 its address in the vote. This fixes the problem where we referred to
20537 "moria on moria:9031."
20538 - Distinguish between detached signatures for the wrong period, and
20539 detached signatures for a divergent vote.
20540 - Fix a small memory leak when computing a consensus.
20541 - When there's no concensus, we were forming a vote every 30
20542 minutes, but writing the "valid-after" line in our vote based
20543 on our configured V3AuthVotingInterval: so unless the intervals
20544 matched up, we immediately rejected our own vote because it didn't
20545 start at the voting interval that caused us to construct a vote.
20547 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
20548 - Delete unverified-consensus when the real consensus is set.
20549 - Consider retrying a consensus networkstatus fetch immediately
20550 after one fails: don't wait 60 seconds to notice.
20551 - When fetching a consensus as a cache, wait until a newer consensus
20552 should exist before trying to replace the current one.
20553 - Use a more forgiving schedule for retrying failed consensus
20554 downloads than for other types.
20556 o Minor bugfixes (other directory issues):
20557 - Correct the implementation of "download votes by digest." Bugfix on
20559 - Authorities no longer send back "400 you're unreachable please fix
20560 it" errors to Tor servers that aren't online all the time. We're
20561 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
20563 o Minor bugfixes (controller):
20564 - Don't reset trusted dir server list when we set a configuration
20565 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
20566 - Respond to INT and TERM SIGNAL commands before we execute the
20567 signal, in case the signal shuts us down. We had a patch in
20568 0.1.2.1-alpha that tried to do this by queueing the response on
20569 the connection's buffer before shutting down, but that really
20570 isn't the same thing at all. Bug located by Matt Edman.
20572 o Minor bugfixes (misc):
20573 - Correctly check for bad options to the "PublishServerDescriptor"
20574 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
20575 - Stop leaking memory on failing case of base32_decode, and make
20576 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
20577 - Don't try to download extrainfo documents when we're trying to
20578 fetch enough directory info to build a circuit: having enough
20579 info should get priority. Bugfix on 0.2.0.x.
20580 - Don't complain that "your server has not managed to confirm that its
20581 ports are reachable" if we haven't been able to build any circuits
20582 yet. Bug found by spending four hours without a v3 consensus. Bugfix
20584 - Detect the reason for failing to mmap a descriptor file we just
20585 wrote, and give a more useful log message. Fixes bug 533. Bugfix
20588 o Code simplifications and refactoring:
20589 - Remove support for the old bw_accounting file: we've been storing
20590 bandwidth accounting information in the state file since
20591 0.1.2.5-alpha. This may result in bandwidth accounting errors
20592 if you try to upgrade from 0.1.1.x or earlier, or if you try to
20593 downgrade to 0.1.1.x or earlier.
20594 - New convenience code to locate a file within the DataDirectory.
20595 - Move non-authority functionality out of dirvote.c.
20596 - Refactor the arguments for router_pick_{directory_|trusteddir}server
20597 so that they all take the same named flags.
20600 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
20601 Unix users an easy way to script their Tor process (e.g. by
20602 adjusting bandwidth based on the time of the day).
20605 Changes in version 0.2.0.8-alpha - 2007-10-12
20606 This eighth development snapshot fixes a crash bug that's been bothering
20607 us since February 2007, lets bridge authorities store a list of bridge
20608 descriptors they've seen, gets v3 directory voting closer to working,
20609 starts caching v3 directory consensus documents on directory mirrors,
20610 and fixes a variety of smaller issues including some minor memory leaks.
20612 o Major features (router descriptor cache):
20613 - Store routers in a file called cached-descriptors instead of in
20614 cached-routers. Initialize cached-descriptors from cached-routers
20615 if the old format is around. The new format allows us to store
20616 annotations along with descriptors.
20617 - Use annotations to record the time we received each descriptor, its
20618 source, and its purpose.
20619 - Disable the SETROUTERPURPOSE controller command: it is now
20621 - Controllers should now specify cache=no or cache=yes when using
20622 the +POSTDESCRIPTOR command.
20623 - Bridge authorities now write bridge descriptors to disk, meaning
20624 we can export them to other programs and begin distributing them
20627 o Major features (directory authorities):
20628 - When a v3 authority is missing votes or signatures, it now tries
20630 - Directory authorities track weighted fractional uptime as well as
20631 weighted mean-time-between failures. WFU is suitable for deciding
20632 whether a node is "usually up", while MTBF is suitable for deciding
20633 whether a node is "likely to stay up." We need both, because
20634 "usually up" is a good requirement for guards, while "likely to
20635 stay up" is a good requirement for long-lived connections.
20637 o Major features (v3 directory system):
20638 - Caches now download v3 network status documents as needed,
20639 and download the descriptors listed in them.
20640 - All hosts now attempt to download and keep fresh v3 authority
20641 certificates, and re-attempt after failures.
20642 - More internal-consistency checks for vote parsing.
20644 o Major bugfixes (crashes):
20645 - If a connection is shut down abruptly because of something that
20646 happened inside connection_flushed_some(), do not call
20647 connection_finished_flushing(). Should fix bug 451. Bugfix on
20650 o Major bugfixes (performance):
20651 - Fix really bad O(n^2) performance when parsing a long list of
20652 routers: Instead of searching the entire list for an "extra-info "
20653 string which usually wasn't there, once for every routerinfo
20654 we read, just scan lines forward until we find one we like.
20656 - When we add data to a write buffer in response to the data on that
20657 write buffer getting low because of a flush, do not consider the
20658 newly added data as a candidate for immediate flushing, but rather
20659 make it wait until the next round of writing. Otherwise, we flush
20660 and refill recursively, and a single greedy TLS connection can
20661 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
20663 o Minor features (v3 authority system):
20664 - Add more ways for tools to download the votes that lead to the
20666 - Send a 503 when low on bandwidth and a vote, consensus, or
20667 certificate is requested.
20668 - If-modified-since is now implemented properly for all kinds of
20669 certificate requests.
20671 o Minor bugfixes (network statuses):
20672 - Tweak the implementation of proposal 109 slightly: allow at most
20673 two Tor servers on the same IP address, except if it's the location
20674 of a directory authority, in which case allow five. Bugfix on
20677 o Minor bugfixes (controller):
20678 - When sending a status event to the controller telling it that an
20679 OR address is reachable, set the port correctly. (Previously we
20680 were reporting the dir port.) Bugfix on 0.1.2.x.
20682 o Minor bugfixes (v3 directory system):
20683 - Fix logic to look up a cert by its signing key digest. Bugfix on
20685 - Only change the reply to a vote to "OK" if it's not already
20686 set. This gets rid of annoying "400 OK" log messages, which may
20687 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
20688 - When we get a valid consensus, recompute the voting schedule.
20689 - Base the valid-after time of a vote on the consensus voting
20690 schedule, not on our preferred schedule.
20691 - Make the return values and messages from signature uploads and
20692 downloads more sensible.
20693 - Fix a memory leak when serving votes and consensus documents, and
20694 another when serving certificates.
20696 o Minor bugfixes (performance):
20697 - Use a slightly simpler string hashing algorithm (copying Python's
20698 instead of Java's) and optimize our digest hashing algorithm to take
20699 advantage of 64-bit platforms and to remove some possibly-costly
20701 - Fix a minor memory leak whenever we parse guards from our state
20702 file. Bugfix on 0.2.0.7-alpha.
20703 - Fix a minor memory leak whenever we write out a file. Bugfix on
20705 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
20706 command. Bugfix on 0.2.0.5-alpha.
20708 o Minor bugfixes (portability):
20709 - On some platforms, accept() can return a broken address. Detect
20710 this more quietly, and deal accordingly. Fixes bug 483.
20711 - Stop calling tor_strlower() on uninitialized memory in some cases.
20712 Bugfix in 0.2.0.7-alpha.
20714 o Minor bugfixes (usability):
20715 - Treat some 403 responses from directory servers as INFO rather than
20716 WARN-severity events.
20717 - It's not actually an error to find a non-pending entry in the DNS
20718 cache when canceling a pending resolve. Don't log unless stuff is
20719 fishy. Resolves bug 463.
20721 o Minor bugfixes (anonymity):
20722 - Never report that we've used more bandwidth than we're willing to
20723 relay: it leaks how much non-relay traffic we're using. Resolves
20725 - When looking for a circuit to cannibalize, consider family as well
20726 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
20727 circuit cannibalization).
20729 o Code simplifications and refactoring:
20730 - Make a bunch of functions static. Remove some dead code.
20731 - Pull out about a third of the really big routerlist.c; put it in a
20732 new module, networkstatus.c.
20733 - Merge the extra fields in local_routerstatus_t back into
20734 routerstatus_t: we used to need one routerstatus_t for each
20735 authority's opinion, plus a local_routerstatus_t for the locally
20736 computed consensus opinion. To save space, we put the locally
20737 modified fields into local_routerstatus_t, and only the common
20738 stuff into routerstatus_t. But once v3 directories are in use,
20739 clients and caches will no longer need to hold authority opinions;
20740 thus, the rationale for keeping the types separate is now gone.
20741 - Make the code used to reschedule and reattempt downloads more
20743 - Turn all 'Are we a directory server/mirror?' logic into a call to
20745 - Remove the code to generate the oldest (v1) directory format.
20746 The code has been disabled since 0.2.0.5-alpha.
20749 Changes in version 0.2.0.7-alpha - 2007-09-21
20750 This seventh development snapshot makes bridges work again, makes bridge
20751 authorities work for the first time, fixes two huge performance flaws
20752 in hidden services, and fixes a variety of minor issues.
20754 o New directory authorities:
20755 - Set up moria1 and tor26 as the first v3 directory authorities. See
20756 doc/spec/dir-spec.txt for details on the new directory design.
20758 o Major bugfixes (crashes):
20759 - Fix possible segfaults in functions called from
20760 rend_process_relay_cell(). Bugfix on 0.1.2.x.
20762 o Major bugfixes (bridges):
20763 - Fix a bug that made servers send a "404 Not found" in response to
20764 attempts to fetch their server descriptor. This caused Tor servers
20765 to take many minutes to establish reachability for their DirPort,
20766 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
20767 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
20768 users configure that and specify a bridge with an identity
20769 fingerprint, now they will lookup the bridge descriptor at the
20770 default bridge authority via a one-hop tunnel, but once circuits
20771 are established they will switch to a three-hop tunnel for later
20772 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
20774 o Major bugfixes (hidden services):
20775 - Hidden services were choosing introduction points uniquely by
20776 hexdigest, but when constructing the hidden service descriptor
20777 they merely wrote the (potentially ambiguous) nickname.
20778 - Clients now use the v2 intro format for hidden service
20779 connections: they specify their chosen rendezvous point by identity
20780 digest rather than by (potentially ambiguous) nickname. Both
20781 are bugfixes on 0.1.2.x, and they could speed up hidden service
20782 connections dramatically. Thanks to Karsten Loesing.
20784 o Minor features (security):
20785 - As a client, do not believe any server that tells us that an
20786 address maps to an internal address space.
20787 - Make it possible to enable HashedControlPassword and
20788 CookieAuthentication at the same time.
20790 o Minor features (guard nodes):
20791 - Tag every guard node in our state file with the version that
20792 we believe added it, or with our own version if we add it. This way,
20793 if a user temporarily runs an old version of Tor and then switches
20794 back to a new one, she doesn't automatically lose her guards.
20796 o Minor features (speed):
20797 - When implementing AES counter mode, update only the portions of the
20798 counter buffer that need to change, and don't keep separate
20799 network-order and host-order counters when they are the same (i.e.,
20800 on big-endian hosts.)
20802 o Minor features (controller):
20803 - Accept LF instead of CRLF on controller, since some software has a
20804 hard time generating real Internet newlines.
20805 - Add GETINFO values for the server status events
20806 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
20809 o Removed features:
20810 - Routers no longer include bandwidth-history lines in their
20811 descriptors; this information is already available in extra-info
20812 documents, and including it in router descriptors took up 60%
20813 (!) of compressed router descriptor downloads. Completes
20814 implementation of proposal 104.
20815 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
20816 and TorControl.py, as they use the old v0 controller protocol,
20817 and are obsoleted by TorFlow anyway.
20818 - Drop support for v1 rendezvous descriptors, since we never used
20819 them anyway, and the code has probably rotted by now. Based on
20820 patch from Karsten Loesing.
20821 - On OSX, stop warning the user that kqueue support in libevent is
20822 "experimental", since it seems to have worked fine for ages.
20825 - When generating information telling us how to extend to a given
20826 router, do not try to include the nickname if it is absent. Fixes
20827 bug 467. Bugfix on 0.2.0.3-alpha.
20828 - Fix a user-triggerable (but not remotely-triggerable) segfault
20829 in expand_filename(). Bugfix on 0.1.2.x.
20830 - Fix a memory leak when freeing incomplete requests from DNSPort.
20831 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
20832 - Don't try to access (or alter) the state file when running
20833 --list-fingerprint or --verify-config or --hash-password. (Resolves
20834 bug 499.) Bugfix on 0.1.2.x.
20835 - Servers used to decline to publish their DirPort if their
20836 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
20837 were below a threshold. Now they only look at BandwidthRate and
20838 RelayBandwidthRate. Bugfix on 0.1.2.x.
20839 - Remove an optimization in the AES counter-mode code that assumed
20840 that the counter never exceeded 2^68. When the counter can be set
20841 arbitrarily as an IV (as it is by Karsten's new hidden services
20842 code), this assumption no longer holds. Bugfix on 0.1.2.x.
20843 - Resume listing "AUTHORITY" flag for authorities in network status.
20844 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
20846 o Code simplifications and refactoring:
20847 - Revamp file-writing logic so we don't need to have the entire
20848 contents of a file in memory at once before we write to disk. Tor,
20850 - Turn "descriptor store" into a full-fledged type.
20851 - Move all NT services code into a separate source file.
20852 - Unify all code that computes medians, percentile elements, etc.
20853 - Get rid of a needless malloc when parsing address policies.
20856 Changes in version 0.1.2.17 - 2007-08-30
20857 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
20858 X bundles. Vidalia 0.0.14 makes authentication required for the
20859 ControlPort in the default configuration, which addresses important
20860 security risks. Everybody who uses Vidalia (or another controller)
20863 In addition, this Tor update fixes major load balancing problems with
20864 path selection, which should speed things up a lot once many people
20867 o Major bugfixes (security):
20868 - We removed support for the old (v0) control protocol. It has been
20869 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
20870 become more of a headache than it's worth.
20872 o Major bugfixes (load balancing):
20873 - When choosing nodes for non-guard positions, weight guards
20874 proportionally less, since they already have enough load. Patch
20876 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
20877 will allow fast Tor servers to get more attention.
20878 - When we're upgrading from an old Tor version, forget our current
20879 guards and pick new ones according to the new weightings. These
20880 three load balancing patches could raise effective network capacity
20881 by a factor of four. Thanks to Mike Perry for measurements.
20883 o Major bugfixes (stream expiration):
20884 - Expire not-yet-successful application streams in all cases if
20885 they've been around longer than SocksTimeout. Right now there are
20886 some cases where the stream will live forever, demanding a new
20887 circuit every 15 seconds. Fixes bug 454; reported by lodger.
20889 o Minor features (controller):
20890 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
20891 is valid before any authentication has been received. It tells
20892 a controller what kind of authentication is expected, and what
20893 protocol is spoken. Implements proposal 119.
20895 o Minor bugfixes (performance):
20896 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
20897 greatly speeding up loading cached-routers from disk on startup.
20898 - Disable sentinel-based debugging for buffer code: we squashed all
20899 the bugs that this was supposed to detect a long time ago, and now
20900 its only effect is to change our buffer sizes from nice powers of
20901 two (which platform mallocs tend to like) to values slightly over
20902 powers of two (which make some platform mallocs sad).
20904 o Minor bugfixes (misc):
20905 - If exit bandwidth ever exceeds one third of total bandwidth, then
20906 use the correct formula to weight exit nodes when choosing paths.
20907 Based on patch from Mike Perry.
20908 - Choose perfectly fairly among routers when choosing by bandwidth and
20909 weighting by fraction of bandwidth provided by exits. Previously, we
20910 would choose with only approximate fairness, and correct ourselves
20911 if we ran off the end of the list.
20912 - If we require CookieAuthentication but we fail to write the
20913 cookie file, we would warn but not exit, and end up in a state
20914 where no controller could authenticate. Now we exit.
20915 - If we require CookieAuthentication, stop generating a new cookie
20916 every time we change any piece of our config.
20917 - Refuse to start with certain directory authority keys, and
20918 encourage people using them to stop.
20919 - Terminate multi-line control events properly. Original patch
20921 - Fix a minor memory leak when we fail to find enough suitable
20922 servers to choose a circuit.
20923 - Stop leaking part of the descriptor when we run into a particularly
20924 unparseable piece of it.
20927 Changes in version 0.2.0.6-alpha - 2007-08-26
20928 This sixth development snapshot features a new Vidalia version in the
20929 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
20930 the ControlPort in the default configuration, which addresses important
20933 In addition, this snapshot fixes major load balancing problems
20934 with path selection, which should speed things up a lot once many
20935 people have upgraded. The directory authorities also use a new
20936 mean-time-between-failure approach to tracking which servers are stable,
20937 rather than just looking at the most recent uptime.
20939 o New directory authorities:
20940 - Set up Tonga as the default bridge directory authority.
20943 - Directory authorities now track servers by weighted
20944 mean-times-between-failures. When we have 4 or more days of data,
20945 use measured MTBF rather than declared uptime to decide whether
20946 to call a router Stable. Implements proposal 108.
20948 o Major bugfixes (load balancing):
20949 - When choosing nodes for non-guard positions, weight guards
20950 proportionally less, since they already have enough load. Patch
20952 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
20953 will allow fast Tor servers to get more attention.
20954 - When we're upgrading from an old Tor version, forget our current
20955 guards and pick new ones according to the new weightings. These
20956 three load balancing patches could raise effective network capacity
20957 by a factor of four. Thanks to Mike Perry for measurements.
20959 o Major bugfixes (descriptor parsing):
20960 - Handle unexpected whitespace better in malformed descriptors. Bug
20961 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
20964 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
20965 GETINFO for Torstat to use until it can switch to using extrainfos.
20966 - Optionally (if built with -DEXPORTMALLINFO) export the output
20967 of mallinfo via http, as tor/mallinfo.txt. Only accessible
20971 - Do not intermix bridge routers with controller-added
20972 routers. (Bugfix on 0.2.0.x)
20973 - Do not fail with an assert when accept() returns an unexpected
20974 address family. Addresses but does not wholly fix bug 483. (Bugfix
20976 - Let directory authorities startup even when they can't generate
20977 a descriptor immediately, e.g. because they don't know their
20979 - Stop putting the authentication cookie in a file called "0"
20980 in your working directory if you don't specify anything for the
20981 new CookieAuthFile option. Reported by Matt Edman.
20982 - Make it possible to read the PROTOCOLINFO response in a way that
20983 conforms to our control-spec. Reported by Matt Edman.
20984 - Fix a minor memory leak when we fail to find enough suitable
20985 servers to choose a circuit. Bugfix on 0.1.2.x.
20986 - Stop leaking part of the descriptor when we run into a particularly
20987 unparseable piece of it. Bugfix on 0.1.2.x.
20988 - Unmap the extrainfo cache file on exit.
20991 Changes in version 0.2.0.5-alpha - 2007-08-19
20992 This fifth development snapshot fixes compilation on Windows again;
20993 fixes an obnoxious client-side bug that slowed things down and put
20994 extra load on the network; gets us closer to using the v3 directory
20995 voting scheme; makes it easier for Tor controllers to use cookie-based
20996 authentication; and fixes a variety of other bugs.
20998 o Removed features:
20999 - Version 1 directories are no longer generated in full. Instead,
21000 authorities generate and serve "stub" v1 directories that list
21001 no servers. This will stop Tor versions 0.1.0.x and earlier from
21002 working, but (for security reasons) nobody should be running those
21005 o Major bugfixes (compilation, 0.2.0.x):
21006 - Try to fix Win32 compilation again: improve checking for IPv6 types.
21007 - Try to fix MSVC compilation: build correctly on platforms that do
21008 not define s6_addr16 or s6_addr32.
21009 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
21012 o Major bugfixes (stream expiration):
21013 - Expire not-yet-successful application streams in all cases if
21014 they've been around longer than SocksTimeout. Right now there are
21015 some cases where the stream will live forever, demanding a new
21016 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
21017 reported by lodger.
21019 o Minor features (directory servers):
21020 - When somebody requests a list of statuses or servers, and we have
21021 none of those, return a 404 rather than an empty 200.
21023 o Minor features (directory voting):
21024 - Store v3 consensus status consensuses on disk, and reload them
21027 o Minor features (security):
21028 - Warn about unsafe ControlPort configurations.
21029 - Refuse to start with certain directory authority keys, and
21030 encourage people using them to stop.
21032 o Minor features (controller):
21033 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
21034 is valid before any authentication has been received. It tells
21035 a controller what kind of authentication is expected, and what
21036 protocol is spoken. Implements proposal 119.
21037 - New config option CookieAuthFile to choose a new location for the
21038 cookie authentication file, and config option
21039 CookieAuthFileGroupReadable to make it group-readable.
21041 o Minor features (unit testing):
21042 - Add command-line arguments to unit-test executable so that we can
21043 invoke any chosen test from the command line rather than having
21044 to run the whole test suite at once; and so that we can turn on
21045 logging for the unit tests.
21047 o Minor bugfixes (on 0.1.2.x):
21048 - If we require CookieAuthentication but we fail to write the
21049 cookie file, we would warn but not exit, and end up in a state
21050 where no controller could authenticate. Now we exit.
21051 - If we require CookieAuthentication, stop generating a new cookie
21052 every time we change any piece of our config.
21053 - When loading bandwidth history, do not believe any information in
21054 the future. Fixes bug 434.
21055 - When loading entry guard information, do not believe any information
21057 - When we have our clock set far in the future and generate an
21058 onion key, then re-set our clock to be correct, we should not stop
21059 the onion key from getting rotated.
21060 - Clean up torrc sample config file.
21061 - Do not automatically run configure from autogen.sh. This
21062 non-standard behavior tended to annoy people who have built other
21065 o Minor bugfixes (on 0.2.0.x):
21066 - Fix a bug with AutomapHostsOnResolve that would always cause
21067 the second request to fail. Bug reported by Kate. Bugfix on
21069 - Fix a bug in ADDRMAP controller replies that would sometimes
21070 try to print a NULL. Patch from tup.
21071 - Read v3 directory authority keys from the right location.
21072 - Numerous bugfixes to directory voting code.
21075 Changes in version 0.1.2.16 - 2007-08-01
21076 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
21077 remote attacker in certain situations to rewrite the user's torrc
21078 configuration file. This can completely compromise anonymity of users
21079 in most configurations, including those running the Vidalia bundles,
21080 TorK, etc. Or worse.
21082 o Major security fixes:
21083 - Close immediately after missing authentication on control port;
21084 do not allow multiple authentication attempts.
21087 Changes in version 0.2.0.4-alpha - 2007-08-01
21088 This fourth development snapshot fixes a critical security vulnerability
21089 for most users, specifically those running Vidalia, TorK, etc. Everybody
21090 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
21092 o Major security fixes:
21093 - Close immediately after missing authentication on control port;
21094 do not allow multiple authentication attempts.
21096 o Major bugfixes (compilation):
21097 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
21100 o Minor features (performance):
21101 - Be even more aggressive about releasing RAM from small
21102 empty buffers. Thanks to our free-list code, this shouldn't be too
21103 performance-intensive.
21104 - Disable sentinel-based debugging for buffer code: we squashed all
21105 the bugs that this was supposed to detect a long time ago, and
21106 now its only effect is to change our buffer sizes from nice
21107 powers of two (which platform mallocs tend to like) to values
21108 slightly over powers of two (which make some platform mallocs sad).
21109 - Log malloc statistics from mallinfo() on platforms where it
21113 Changes in version 0.2.0.3-alpha - 2007-07-29
21114 This third development snapshot introduces new experimental
21115 blocking-resistance features and a preliminary version of the v3
21116 directory voting design, and includes many other smaller features
21120 - The first pieces of our "bridge" design for blocking-resistance
21121 are implemented. People can run bridge directory authorities;
21122 people can run bridges; and people can configure their Tor clients
21123 with a set of bridges to use as the first hop into the Tor network.
21124 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
21126 - Create listener connections before we setuid to the configured
21127 User and Group. Now non-Windows users can choose port values
21128 under 1024, start Tor as root, and have Tor bind those ports
21129 before it changes to another UID. (Windows users could already
21131 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
21132 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
21133 on "vserver" accounts. (Patch from coderman.)
21134 - Be even more aggressive about separating local traffic from relayed
21135 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
21137 o Major features (experimental):
21138 - First cut of code for "v3 dir voting": directory authorities will
21139 vote on a common network status document rather than each publishing
21140 their own opinion. This code needs more testing and more corner-case
21141 handling before it's ready for use.
21144 - Directory authorities now call routers Fast if their bandwidth is
21145 at least 100KB/s, and consider their bandwidth adequate to be a
21146 Guard if it is at least 250KB/s, no matter the medians. This fix
21147 complements proposal 107. [Bugfix on 0.1.2.x]
21148 - Directory authorities now never mark more than 3 servers per IP as
21149 Valid and Running. (Implements proposal 109, by Kevin Bauer and
21151 - Minor change to organizationName and commonName generation
21152 procedures in TLS certificates during Tor handshakes, to invalidate
21153 some earlier censorware approaches. This is not a long-term
21154 solution, but applying it will give us a bit of time to look into
21155 the epidemiology of countermeasures as they spread.
21157 o Major bugfixes (directory):
21158 - Rewrite directory tokenization code to never run off the end of
21159 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
21161 o Minor features (controller):
21162 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
21163 match requests to applications. (Patch from Robert Hogan.)
21164 - Report address and port correctly on connections to DNSPort. (Patch
21165 from Robert Hogan.)
21166 - Add a RESOLVE command to launch hostname lookups. (Original patch
21167 from Robert Hogan.)
21168 - Add GETINFO status/enough-dir-info to let controllers tell whether
21169 Tor has downloaded sufficient directory information. (Patch
21171 - You can now use the ControlSocket option to tell Tor to listen for
21172 controller connections on Unix domain sockets on systems that
21173 support them. (Patch from Peter Palfrader.)
21174 - STREAM NEW events are generated for DNSPort requests and for
21175 tunneled directory connections. (Patch from Robert Hogan.)
21176 - New "GETINFO address-mappings/*" command to get address mappings
21177 with expiry information. "addr-mappings/*" is now deprecated.
21180 o Minor features (misc):
21181 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
21183 - The tor-gencert tool for v3 directory authorities now creates all
21184 files as readable to the file creator only, and write-protects
21185 the authority identity key.
21186 - When dumping memory usage, list bytes used in buffer memory
21188 - When running with dmalloc, dump more stats on hup and on exit.
21189 - Directory authorities now fail quickly and (relatively) harmlessly
21190 if they generate a network status document that is somehow
21193 o Traffic load balancing improvements:
21194 - If exit bandwidth ever exceeds one third of total bandwidth, then
21195 use the correct formula to weight exit nodes when choosing paths.
21196 (Based on patch from Mike Perry.)
21197 - Choose perfectly fairly among routers when choosing by bandwidth and
21198 weighting by fraction of bandwidth provided by exits. Previously, we
21199 would choose with only approximate fairness, and correct ourselves
21200 if we ran off the end of the list. [Bugfix on 0.1.2.x]
21202 o Performance improvements:
21203 - Be more aggressive with freeing buffer RAM or putting it on the
21205 - Use Critical Sections rather than Mutexes for synchronizing threads
21206 on win32; Mutexes are heavier-weight, and designed for synchronizing
21209 o Deprecated and removed features:
21210 - RedirectExits is now deprecated.
21211 - Stop allowing address masks that do not correspond to bit prefixes.
21212 We have warned about these for a really long time; now it's time
21213 to reject them. (Patch from croup.)
21215 o Minor bugfixes (directory):
21216 - Fix another crash bug related to extra-info caching. (Bug found by
21217 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
21218 - Directories no longer return a "304 not modified" when they don't
21219 have the networkstatus the client asked for. Also fix a memory
21220 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
21221 - We had accidentally labelled 0.1.2.x directory servers as not
21222 suitable for begin_dir requests, and had labelled no directory
21223 servers as suitable for uploading extra-info documents. [Bugfix
21226 o Minor bugfixes (dns):
21227 - Fix a crash when DNSPort is set more than once. (Patch from Robert
21228 Hogan.) [Bugfix on 0.2.0.2-alpha]
21229 - Add DNSPort connections to the global connection list, so that we
21230 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
21232 - Fix a dangling reference that could lead to a crash when DNSPort is
21233 changed or closed (Patch from Robert Hogan.) [Bugfix on
21236 o Minor bugfixes (controller):
21237 - Provide DNS expiry times in GMT, not in local time. For backward
21238 compatibility, ADDRMAP events only provide GMT expiry in an extended
21239 field. "GETINFO address-mappings" always does the right thing.
21240 - Use CRLF line endings properly in NS events.
21241 - Terminate multi-line control events properly. (Original patch
21242 from tup.) [Bugfix on 0.1.2.x-alpha]
21243 - Do not include spaces in SOURCE_ADDR fields in STREAM
21244 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
21247 Changes in version 0.1.2.15 - 2007-07-17
21248 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
21249 problems, fixes compilation on BSD, and fixes a variety of other
21250 bugs. Everybody should upgrade.
21252 o Major bugfixes (compilation):
21253 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
21255 o Major bugfixes (crashes):
21256 - Try even harder not to dereference the first character after
21257 an mmap(). Reported by lodger.
21258 - Fix a crash bug in directory authorities when we re-number the
21259 routerlist while inserting a new router.
21260 - When the cached-routers file is an even multiple of the page size,
21261 don't run off the end and crash. (Fixes bug 455; based on idea
21263 - Fix eventdns.c behavior on Solaris: It is critical to include
21264 orconfig.h _before_ sys/types.h, so that we can get the expected
21265 definition of _FILE_OFFSET_BITS.
21267 o Major bugfixes (security):
21268 - Fix a possible buffer overrun when using BSD natd support. Bug
21270 - When sending destroy cells from a circuit's origin, don't include
21271 the reason for tearing down the circuit. The spec says we didn't,
21272 and now we actually don't. Reported by lodger.
21273 - Keep streamids from different exits on a circuit separate. This
21274 bug may have allowed other routers on a given circuit to inject
21275 cells into streams. Reported by lodger; fixes bug 446.
21276 - If there's a never-before-connected-to guard node in our list,
21277 never choose any guards past it. This way we don't expand our
21278 guard list unless we need to.
21280 o Minor bugfixes (guard nodes):
21281 - Weight guard selection by bandwidth, so that low-bandwidth nodes
21282 don't get overused as guards.
21284 o Minor bugfixes (directory):
21285 - Correctly count the number of authorities that recommend each
21286 version. Previously, we were under-counting by 1.
21287 - Fix a potential crash bug when we load many server descriptors at
21288 once and some of them make others of them obsolete. Fixes bug 458.
21290 o Minor bugfixes (hidden services):
21291 - Stop tearing down the whole circuit when the user asks for a
21292 connection to a port that the hidden service didn't configure.
21295 o Minor bugfixes (misc):
21296 - On Windows, we were preventing other processes from reading
21297 cached-routers while Tor was running. Reported by janbar.
21298 - Fix a possible (but very unlikely) bug in picking routers by
21299 bandwidth. Add a log message to confirm that it is in fact
21300 unlikely. Patch from lodger.
21301 - Backport a couple of memory leak fixes.
21302 - Backport miscellaneous cosmetic bugfixes.
21305 Changes in version 0.2.0.2-alpha - 2007-06-02
21306 o Major bugfixes on 0.2.0.1-alpha:
21307 - Fix an assertion failure related to servers without extra-info digests.
21308 Resolves bugs 441 and 442.
21310 o Minor features (directory):
21311 - Support "If-Modified-Since" when answering HTTP requests for
21312 directories, running-routers documents, and network-status documents.
21313 (There's no need to support it for router descriptors, since those
21314 are downloaded by descriptor digest.)
21316 o Minor build issues:
21317 - Clear up some MIPSPro compiler warnings.
21318 - When building from a tarball on a machine that happens to have SVK
21319 installed, report the micro-revision as whatever version existed
21320 in the tarball, not as "x".
21323 Changes in version 0.2.0.1-alpha - 2007-06-01
21324 This early development snapshot provides new features for people running
21325 Tor as both a client and a server (check out the new RelayBandwidth
21326 config options); lets Tor run as a DNS proxy; and generally moves us
21327 forward on a lot of fronts.
21329 o Major features, server usability:
21330 - New config options RelayBandwidthRate and RelayBandwidthBurst:
21331 a separate set of token buckets for relayed traffic. Right now
21332 relayed traffic is defined as answers to directory requests, and
21333 OR connections that don't have any local circuits on them.
21335 o Major features, client usability:
21336 - A client-side DNS proxy feature to replace the need for
21337 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
21338 for DNS requests on port 9999, use the Tor network to resolve them
21339 anonymously, and send the reply back like a regular DNS server.
21340 The code still only implements a subset of DNS.
21341 - Make PreferTunneledDirConns and TunnelDirConns work even when
21342 we have no cached directory info. This means Tor clients can now
21343 do all of their connections protected by TLS.
21345 o Major features, performance and efficiency:
21346 - Directory authorities accept and serve "extra info" documents for
21347 routers. These documents contain fields from router descriptors
21348 that aren't usually needed, and that use a lot of excess
21349 bandwidth. Once these fields are removed from router descriptors,
21350 the bandwidth savings should be about 60%. [Partially implements
21352 - Servers upload extra-info documents to any authority that accepts
21353 them. Authorities (and caches that have been configured to download
21354 extra-info documents) download them as needed. [Partially implements
21356 - Change the way that Tor buffers data that it is waiting to write.
21357 Instead of queueing data cells in an enormous ring buffer for each
21358 client->OR or OR->OR connection, we now queue cells on a separate
21359 queue for each circuit. This lets us use less slack memory, and
21360 will eventually let us be smarter about prioritizing different kinds
21362 - Use memory pools to allocate cells with better speed and memory
21363 efficiency, especially on platforms where malloc() is inefficient.
21364 - Stop reading on edge connections when their corresponding circuit
21365 buffers are full; start again as the circuits empty out.
21367 o Major features, other:
21368 - Add an HSAuthorityRecordStats option that hidden service authorities
21369 can use to track statistics of overall hidden service usage without
21370 logging information that would be very useful to an attacker.
21371 - Start work implementing multi-level keys for directory authorities:
21372 Add a standalone tool to generate key certificates. (Proposal 103.)
21375 - Directory authorities now call routers Stable if they have an
21376 uptime of at least 30 days, even if that's not the median uptime
21377 in the network. Implements proposal 107, suggested by Kevin Bauer
21380 o Minor fixes (resource management):
21381 - Count the number of open sockets separately from the number
21382 of active connection_t objects. This will let us avoid underusing
21383 our allocated connection limit.
21384 - We no longer use socket pairs to link an edge connection to an
21385 anonymous directory connection or a DirPort test connection.
21386 Instead, we track the link internally and transfer the data
21387 in-process. This saves two sockets per "linked" connection (at the
21388 client and at the server), and avoids the nasty Windows socketpair()
21390 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
21391 for every single inactive connection_t. Free items from the
21392 4k/16k-buffer free lists when they haven't been used for a while.
21394 o Minor features (build):
21395 - Make autoconf search for libevent, openssl, and zlib consistently.
21396 - Update deprecated macros in configure.in.
21397 - When warning about missing headers, tell the user to let us
21398 know if the compile succeeds anyway, so we can downgrade the
21400 - Include the current subversion revision as part of the version
21401 string: either fetch it directly if we're in an SVN checkout, do
21402 some magic to guess it if we're in an SVK checkout, or use
21403 the last-detected version if we're building from a .tar.gz.
21404 Use this version consistently in log messages.
21406 o Minor features (logging):
21407 - Always prepend "Bug: " to any log message about a bug.
21408 - Put a platform string (e.g. "Linux i686") in the startup log
21409 message, so when people paste just their logs, we know if it's
21410 OpenBSD or Windows or what.
21411 - When logging memory usage, break down memory used in buffers by
21414 o Minor features (directory system):
21415 - New config option V2AuthoritativeDirectory that all directory
21416 authorities should set. This will let future authorities choose
21417 not to serve V2 directory information.
21418 - Directory authorities allow multiple router descriptors and/or extra
21419 info documents to be uploaded in a single go. This will make
21420 implementing proposal 104 simpler.
21422 o Minor features (controller):
21423 - Add a new config option __DisablePredictedCircuits designed for
21424 use by the controller, when we don't want Tor to build any circuits
21426 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
21427 so we can exit from the middle of the circuit.
21428 - Implement "getinfo status/circuit-established".
21429 - Implement "getinfo status/version/..." so a controller can tell
21430 whether the current version is recommended, and whether any versions
21431 are good, and how many authorities agree. (Patch from shibz.)
21433 o Minor features (hidden services):
21434 - Allow multiple HiddenServicePort directives with the same virtual
21435 port; when they occur, the user is sent round-robin to one
21436 of the target ports chosen at random. Partially fixes bug 393 by
21437 adding limited ad-hoc round-robining.
21439 o Minor features (other):
21441 - Add a new AutomapHostsOnResolve option: when it is enabled, any
21442 resolve request for hosts matching a given pattern causes Tor to
21443 generate an internal virtual address mapping for that host. This
21444 allows DNSPort to work sensibly with hidden service users. By
21445 default, .exit and .onion addresses are remapped; the list of
21446 patterns can be reconfigured with AutomapHostsSuffixes.
21447 - Add an "-F" option to tor-resolve to force a resolve for a .onion
21448 address. Thanks to the AutomapHostsOnResolve option, this is no
21449 longer a completely silly thing to do.
21450 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
21451 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
21452 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
21453 minus 1 byte: the actual maximum declared bandwidth.
21455 o Removed features:
21456 - Removed support for the old binary "version 0" controller protocol.
21457 This has been deprecated since 0.1.1, and warnings have been issued
21458 since 0.1.2. When we encounter a v0 control message, we now send
21459 back an error and close the connection.
21460 - Remove the old "dns worker" server DNS code: it hasn't been default
21461 since 0.1.2.2-alpha, and all the servers seem to be using the new
21464 o Minor bugfixes (portability):
21465 - Even though Windows is equally happy with / and \ as path separators,
21466 try to use \ consistently on Windows and / consistently on Unix: it
21467 makes the log messages nicer.
21468 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
21469 - Read resolv.conf files correctly on platforms where read() returns
21470 partial results on small file reads.
21472 o Minor bugfixes (directory):
21473 - Correctly enforce that elements of directory objects do not appear
21474 more often than they are allowed to appear.
21475 - When we are reporting the DirServer line we just parsed, we were
21476 logging the second stanza of the key fingerprint, not the first.
21478 o Minor bugfixes (logging):
21479 - When we hit an EOF on a log (probably because we're shutting down),
21480 don't try to remove the log from the list: just mark it as
21481 unusable. (Bulletproofs against bug 222.)
21483 o Minor bugfixes (other):
21484 - In the exitlist script, only consider the most recently published
21485 server descriptor for each server. Also, when the user requests
21486 a list of servers that _reject_ connections to a given address,
21487 explicitly exclude the IPs that also have servers that accept
21488 connections to that address. (Resolves bug 405.)
21489 - Stop allowing hibernating servers to be "stable" or "fast".
21490 - On Windows, we were preventing other processes from reading
21491 cached-routers while Tor was running. (Reported by janbar)
21492 - Make the NodeFamilies config option work. (Reported by
21493 lodger -- it has never actually worked, even though we added it
21495 - Check return values from pthread_mutex functions.
21496 - Don't save non-general-purpose router descriptors to the disk cache,
21497 because we have no way of remembering what their purpose was when
21499 - Add even more asserts to hunt down bug 417.
21500 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
21501 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
21502 Add a log message to confirm that it is in fact unlikely.
21504 o Minor bugfixes (controller):
21505 - Make 'getinfo fingerprint' return a 551 error if we're not a
21506 server, so we match what the control spec claims we do. Reported
21508 - Fix a typo in an error message when extendcircuit fails that
21509 caused us to not follow the \r\n-based delimiter protocol. Reported
21512 o Code simplifications and refactoring:
21513 - Stop passing around circuit_t and crypt_path_t pointers that are
21514 implicit in other procedure arguments.
21515 - Drop the old code to choke directory connections when the
21516 corresponding OR connections got full: thanks to the cell queue
21517 feature, OR conns don't get full any more.
21518 - Make dns_resolve() handle attaching connections to circuits
21519 properly, so the caller doesn't have to.
21520 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
21521 - Keep the connection array as a dynamic smartlist_t, rather than as
21522 a fixed-sized array. This is important, as the number of connections
21523 is becoming increasingly decoupled from the number of sockets.
21526 Changes in version 0.1.2.14 - 2007-05-25
21527 Tor 0.1.2.14 changes the addresses of two directory authorities (this
21528 change especially affects those who serve or use hidden services),
21529 and fixes several other crash- and security-related bugs.
21531 o Directory authority changes:
21532 - Two directory authorities (moria1 and moria2) just moved to new
21533 IP addresses. This change will particularly affect those who serve
21534 or use hidden services.
21536 o Major bugfixes (crashes):
21537 - If a directory server runs out of space in the connection table
21538 as it's processing a begin_dir request, it will free the exit stream
21539 but leave it attached to the circuit, leading to unpredictable
21540 behavior. (Reported by seeess, fixes bug 425.)
21541 - Fix a bug in dirserv_remove_invalid() that would cause authorities
21542 to corrupt memory under some really unlikely scenarios.
21543 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
21544 - Avoid segfaults when reading from mmaped descriptor file. (Reported
21547 o Major bugfixes (security):
21548 - When choosing an entry guard for a circuit, avoid using guards
21549 that are in the same family as the chosen exit -- not just guards
21550 that are exactly the chosen exit. (Reported by lodger.)
21552 o Major bugfixes (resource management):
21553 - If a directory authority is down, skip it when deciding where to get
21554 networkstatus objects or descriptors. Otherwise we keep asking
21555 every 10 seconds forever. Fixes bug 384.
21556 - Count it as a failure if we fetch a valid network-status but we
21557 don't want to keep it. Otherwise we'll keep fetching it and keep
21558 not wanting to keep it. Fixes part of bug 422.
21559 - If all of our dirservers have given us bad or no networkstatuses
21560 lately, then stop hammering them once per minute even when we
21561 think they're failed. Fixes another part of bug 422.
21564 - Actually set the purpose correctly for descriptors inserted with
21565 purpose=controller.
21566 - When we have k non-v2 authorities in our DirServer config,
21567 we ignored the last k authorities in the list when updating our
21569 - Correctly back-off from requesting router descriptors that we are
21570 having a hard time downloading.
21571 - Read resolv.conf files correctly on platforms where read() returns
21572 partial results on small file reads.
21573 - Don't rebuild the entire router store every time we get 32K of
21574 routers: rebuild it when the journal gets very large, or when
21575 the gaps in the store get very large.
21578 - When routers publish SVN revisions in their router descriptors,
21579 authorities now include those versions correctly in networkstatus
21581 - Warn when using a version of libevent before 1.3b to run a server on
21582 OSX or BSD: these versions interact badly with userspace threads.
21585 Changes in version 0.1.2.13 - 2007-04-24
21586 This release features some major anonymity fixes, such as safer path
21587 selection; better client performance; faster bootstrapping, better
21588 address detection, and better DNS support for servers; write limiting as
21589 well as read limiting to make servers easier to run; and a huge pile of
21590 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
21592 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
21593 of the Freenode IRC network, remembering his patience and vision for
21594 free speech on the Internet.
21597 - Fix a memory leak when we ask for "all" networkstatuses and we
21598 get one we don't recognize.
21599 - Add more asserts to hunt down bug 417.
21600 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
21603 Changes in version 0.1.2.12-rc - 2007-03-16
21605 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
21606 directory information requested inside Tor connections (i.e. via
21607 begin_dir cells). It only triggered when the same connection was
21608 serving other data at the same time. Reported by seeess.
21611 - When creating a circuit via the controller, send a 'launched'
21612 event when we're done, so we follow the spec better.
21615 Changes in version 0.1.2.11-rc - 2007-03-15
21616 o Minor bugfixes (controller), reported by daejees:
21617 - Correct the control spec to match how the code actually responds
21618 to 'getinfo addr-mappings/*'.
21619 - The control spec described a GUARDS event, but the code
21620 implemented a GUARD event. Standardize on GUARD, but let people
21621 ask for GUARDS too.
21624 Changes in version 0.1.2.10-rc - 2007-03-07
21625 o Major bugfixes (Windows):
21626 - Do not load the NT services library functions (which may not exist)
21627 just to detect if we're a service trying to shut down. Now we run
21628 on Win98 and friends again.
21630 o Minor bugfixes (other):
21631 - Clarify a couple of log messages.
21632 - Fix a misleading socks5 error number.
21635 Changes in version 0.1.2.9-rc - 2007-03-02
21636 o Major bugfixes (Windows):
21637 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
21638 of the usual GCC "%llu". This prevents a bug when saving 64-bit
21639 int configuration values: the high-order 32 bits would get
21640 truncated. In particular, we were being bitten by the default
21641 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
21642 and maybe also bug 397.)
21644 o Minor bugfixes (performance):
21645 - Use OpenSSL's AES implementation on platforms where it's faster.
21646 This could save us as much as 10% CPU usage.
21648 o Minor bugfixes (server):
21649 - Do not rotate onion key immediately after setting it for the first
21652 o Minor bugfixes (directory authorities):
21653 - Stop calling servers that have been hibernating for a long time
21654 "stable". Also, stop letting hibernating or obsolete servers affect
21655 uptime and bandwidth cutoffs.
21656 - Stop listing hibernating servers in the v1 directory.
21658 o Minor bugfixes (hidden services):
21659 - Upload hidden service descriptors slightly less often, to reduce
21660 load on authorities.
21662 o Minor bugfixes (other):
21663 - Fix an assert that could trigger if a controller quickly set then
21664 cleared EntryNodes. Bug found by Udo van den Heuvel.
21665 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
21667 - Fix a potential race condition in the rpm installer. Found by
21669 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
21670 of 2 as indicating that the server is completely bad; it sometimes
21671 means that the server is just bad for the request in question. (may fix
21672 the last of bug 326.)
21673 - Disable encrypted directory connections when we don't have a server
21674 descriptor for the destination. We'll get this working again in
21678 Changes in version 0.1.2.8-beta - 2007-02-26
21679 o Major bugfixes (crashes):
21680 - Stop crashing when the controller asks us to resetconf more than
21681 one config option at once. (Vidalia 0.0.11 does this.)
21682 - Fix a crash that happened on Win98 when we're given command-line
21683 arguments: don't try to load NT service functions from advapi32.dll
21684 except when we need them. (Bug introduced in 0.1.2.7-alpha;
21686 - Fix a longstanding obscure crash bug that could occur when
21687 we run out of DNS worker processes. (Resolves bug 390.)
21689 o Major bugfixes (hidden services):
21690 - Correctly detect whether hidden service descriptor downloads are
21691 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
21693 o Major bugfixes (accounting):
21694 - When we start during an accounting interval before it's time to wake
21695 up, remember to wake up at the correct time. (May fix bug 342.)
21697 o Minor bugfixes (controller):
21698 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
21699 clear the corresponding on_circuit variable, and remember later
21700 that we don't need to send a redundant CLOSED event. Resolves part
21702 - Report events where a resolve succeeded or where we got a socks
21703 protocol error correctly, rather than calling both of them
21705 - Change reported stream target addresses to IP consistently when
21706 we finally get the IP from an exit node.
21707 - Send log messages to the controller even if they happen to be very
21710 o Minor bugfixes (other):
21711 - Display correct results when reporting which versions are
21712 recommended, and how recommended they are. (Resolves bug 383.)
21713 - Improve our estimates for directory bandwidth to be less random:
21714 guess that an unrecognized directory will have the average bandwidth
21715 from all known directories, not that it will have the average
21716 bandwidth from those directories earlier than it on the list.
21717 - If we start a server with ClientOnly 1, then set ClientOnly to 0
21718 and hup, stop triggering an assert based on an empty onion_key.
21719 - On platforms with no working mmap() equivalent, don't warn the
21720 user when cached-routers doesn't exist.
21721 - Warn the user when mmap() [or its equivalent] fails for some reason
21722 other than file-not-found.
21723 - Don't warn the user when cached-routers.new doesn't exist: that's
21724 perfectly fine when starting up for the first time.
21725 - When EntryNodes are configured, rebuild the guard list to contain,
21726 in order: the EntryNodes that were guards before; the rest of the
21727 EntryNodes; the nodes that were guards before.
21728 - Mask out all signals in sub-threads; only the libevent signal
21729 handler should be processing them. This should prevent some crashes
21730 on some machines using pthreads. (Patch from coderman.)
21731 - Fix switched arguments on memset in the implementation of
21732 tor_munmap() for systems with no mmap() call.
21733 - When Tor receives a router descriptor that it asked for, but
21734 no longer wants (because it has received fresh networkstatuses
21735 in the meantime), do not warn the user. Cache the descriptor if
21736 we're a cache; drop it if we aren't.
21737 - Make earlier entry guards _really_ get retried when the network
21739 - On a malformed DNS reply, always give an error to the corresponding
21741 - Build with recent libevents on platforms that do not define the
21742 nonstandard types "u_int8_t" and friends.
21744 o Minor features (controller):
21745 - Warn the user when an application uses the obsolete binary v0
21746 control protocol. We're planning to remove support for it during
21747 the next development series, so it's good to give people some
21749 - Add STREAM_BW events to report per-entry-stream bandwidth
21750 use. (Patch from Robert Hogan.)
21751 - Rate-limit SIGNEWNYM signals in response to controllers that
21752 impolitely generate them for every single stream. (Patch from
21753 mwenge; closes bug 394.)
21754 - Make REMAP stream events have a SOURCE (cache or exit), and
21755 make them generated in every case where we get a successful
21756 connected or resolved cell.
21758 o Minor bugfixes (performance):
21759 - Call router_have_min_dir_info half as often. (This is showing up in
21760 some profiles, but not others.)
21761 - When using GCC, make log_debug never get called at all, and its
21762 arguments never get evaluated, when no debug logs are configured.
21763 (This is showing up in some profiles, but not others.)
21766 - Remove some never-implemented options. Mark PathlenCoinWeight as
21768 - Implement proposal 106: Stop requiring clients to have well-formed
21769 certificates; stop checking nicknames in certificates. (Clients
21770 have certificates so that they can look like Tor servers, but in
21771 the future we might want to allow them to look like regular TLS
21772 clients instead. Nicknames in certificates serve no purpose other
21773 than making our protocol easier to recognize on the wire.)
21774 - Revise messages on handshake failure again to be even more clear about
21775 which are incoming connections and which are outgoing.
21776 - Discard any v1 directory info that's over 1 month old (for
21777 directories) or over 1 week old (for running-routers lists).
21778 - Do not warn when individual nodes in the configuration's EntryNodes,
21779 ExitNodes, etc are down: warn only when all possible nodes
21780 are down. (Fixes bug 348.)
21781 - Always remove expired routers and networkstatus docs before checking
21782 whether we have enough information to build circuits. (Fixes
21784 - Put a lower-bound on MaxAdvertisedBandwidth.
21787 Changes in version 0.1.2.7-alpha - 2007-02-06
21788 o Major bugfixes (rate limiting):
21789 - Servers decline directory requests much more aggressively when
21790 they're low on bandwidth. Otherwise they end up queueing more and
21791 more directory responses, which can't be good for latency.
21792 - But never refuse directory requests from local addresses.
21793 - Fix a memory leak when sending a 503 response for a networkstatus
21795 - Be willing to read or write on local connections (e.g. controller
21796 connections) even when the global rate limiting buckets are empty.
21797 - If our system clock jumps back in time, don't publish a negative
21798 uptime in the descriptor. Also, don't let the global rate limiting
21799 buckets go absurdly negative.
21800 - Flush local controller connection buffers periodically as we're
21801 writing to them, so we avoid queueing 4+ megabytes of data before
21804 o Major bugfixes (NT services):
21805 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
21806 command-line flag so that admins can override the default by saying
21807 "tor --service install --user "SomeUser"". This will not affect
21808 existing installed services. Also, warn the user that the service
21809 will look for its configuration file in the service user's
21810 %appdata% directory. (We can't do the 'hardwire the user's appdata
21811 directory' trick any more, since we may not have read access to that
21814 o Major bugfixes (other):
21815 - Previously, we would cache up to 16 old networkstatus documents
21816 indefinitely, if they came from nontrusted authorities. Now we
21817 discard them if they are more than 10 days old.
21818 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
21820 - Detect and reject malformed DNS responses containing circular
21822 - If exits are rare enough that we're not marking exits as guards,
21823 ignore exit bandwidth when we're deciding the required bandwidth
21825 - When we're handling a directory connection tunneled over Tor,
21826 don't fill up internal memory buffers with all the data we want
21827 to tunnel; instead, only add it if the OR connection that will
21828 eventually receive it has some room for it. (This can lead to
21829 slowdowns in tunneled dir connections; a better solution will have
21830 to wait for 0.2.0.)
21832 o Minor bugfixes (dns):
21833 - Add some defensive programming to eventdns.c in an attempt to catch
21834 possible memory-stomping bugs.
21835 - Detect and reject DNS replies containing IPv4 or IPv6 records with
21836 an incorrect number of bytes. (Previously, we would ignore the
21838 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
21839 in the correct order, and doesn't crash.
21840 - Free memory held in recently-completed DNS lookup attempts on exit.
21841 This was not a memory leak, but may have been hiding memory leaks.
21842 - Handle TTL values correctly on reverse DNS lookups.
21843 - Treat failure to parse resolv.conf as an error.
21845 o Minor bugfixes (other):
21846 - Fix crash with "tor --list-fingerprint" (reported by seeess).
21847 - When computing clock skew from directory HTTP headers, consider what
21848 time it was when we finished asking for the directory, not what
21850 - Expire socks connections if they spend too long waiting for the
21851 handshake to finish. Previously we would let them sit around for
21852 days, if the connecting application didn't close them either.
21853 - And if the socks handshake hasn't started, don't send a
21854 "DNS resolve socks failed" handshake reply; just close it.
21855 - Stop using C functions that OpenBSD's linker doesn't like.
21856 - Don't launch requests for descriptors unless we have networkstatuses
21857 from at least half of the authorities. This delays the first
21858 download slightly under pathological circumstances, but can prevent
21859 us from downloading a bunch of descriptors we don't need.
21860 - Do not log IPs with TLS failures for incoming TLS
21861 connections. (Fixes bug 382.)
21862 - If the user asks to use invalid exit nodes, be willing to use
21864 - Stop using the reserved ac_cv namespace in our configure script.
21865 - Call stat() slightly less often; use fstat() when possible.
21866 - Refactor the way we handle pending circuits when an OR connection
21867 completes or fails, in an attempt to fix a rare crash bug.
21868 - Only rewrite a conn's address based on X-Forwarded-For: headers
21869 if it's a parseable public IP address; and stop adding extra quotes
21870 to the resulting address.
21873 - Weight directory requests by advertised bandwidth. Now we can
21874 let servers enable write limiting but still allow most clients to
21875 succeed at their directory requests. (We still ignore weights when
21876 choosing a directory authority; I hope this is a feature.)
21879 - Create a new file ReleaseNotes which was the old ChangeLog. The
21880 new ChangeLog file now includes the summaries for all development
21882 - Check for addresses with invalid characters at the exit as well
21883 as at the client, and warn less verbosely when they fail. You can
21884 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
21885 - Adapt a patch from goodell to let the contrib/exitlist script
21886 take arguments rather than require direct editing.
21887 - Inform the server operator when we decide not to advertise a
21888 DirPort due to AccountingMax enabled or a low BandwidthRate. It
21889 was confusing Zax, so now we're hopefully more helpful.
21890 - Bring us one step closer to being able to establish an encrypted
21891 directory tunnel without knowing a descriptor first. Still not
21892 ready yet. As part of the change, now assume we can use a
21893 create_fast cell if we don't know anything about a router.
21894 - Allow exit nodes to use nameservers running on ports other than 53.
21895 - Servers now cache reverse DNS replies.
21896 - Add an --ignore-missing-torrc command-line option so that we can
21897 get the "use sensible defaults if the configuration file doesn't
21898 exist" behavior even when specifying a torrc location on the command
21901 o Minor features (controller):
21902 - Track reasons for OR connection failure; make these reasons
21903 available via the controller interface. (Patch from Mike Perry.)
21904 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
21905 can learn when clients are sending malformed hostnames to Tor.
21906 - Clean up documentation for controller status events.
21907 - Add a REMAP status to stream events to note that a stream's
21908 address has changed because of a cached address or a MapAddress
21912 Changes in version 0.1.2.6-alpha - 2007-01-09
21914 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
21915 connection handles more than 4 gigs in either direction, we crash.
21916 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
21917 advertised exit node, somebody might try to exit from us when
21918 we're bootstrapping and before we've built our descriptor yet.
21919 Refuse the connection rather than crashing.
21922 - Warn if we (as a server) find that we've resolved an address that we
21923 weren't planning to resolve.
21924 - Warn that using select() on any libevent version before 1.1 will be
21925 unnecessarily slow (even for select()).
21926 - Flush ERR-level controller status events just like we currently
21927 flush ERR-level log events, so that a Tor shutdown doesn't prevent
21928 the controller from learning about current events.
21930 o Minor features (more controller status events):
21931 - Implement EXTERNAL_ADDRESS server status event so controllers can
21932 learn when our address changes.
21933 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
21934 can learn when directories reject our descriptor.
21935 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
21936 can learn when a client application is speaking a non-socks protocol
21938 - Implement DANGEROUS_SOCKS client status event so controllers
21939 can learn when a client application is leaking DNS addresses.
21940 - Implement BUG general status event so controllers can learn when
21941 Tor is unhappy about its internal invariants.
21942 - Implement CLOCK_SKEW general status event so controllers can learn
21943 when Tor thinks the system clock is set incorrectly.
21944 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
21945 server status events so controllers can learn when their descriptors
21946 are accepted by a directory.
21947 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
21948 server status events so controllers can learn about Tor's progress in
21949 deciding whether it's reachable from the outside.
21950 - Implement BAD_LIBEVENT general status event so controllers can learn
21951 when we have a version/method combination in libevent that needs to
21953 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
21954 and DNS_USELESS server status events so controllers can learn
21955 about changes to DNS server status.
21957 o Minor features (directory):
21958 - Authorities no longer recommend exits as guards if this would shift
21959 too much load to the exit nodes.
21962 Changes in version 0.1.2.5-alpha - 2007-01-06
21964 - Enable write limiting as well as read limiting. Now we sacrifice
21965 capacity if we're pushing out lots of directory traffic, rather
21966 than overrunning the user's intended bandwidth limits.
21967 - Include TLS overhead when counting bandwidth usage; previously, we
21968 would count only the bytes sent over TLS, but not the bytes used
21970 - Support running the Tor service with a torrc not in the same
21971 directory as tor.exe and default to using the torrc located in
21972 the %appdata%\Tor\ of the user who installed the service. Patch
21974 - Servers now check for the case when common DNS requests are going to
21975 wildcarded addresses (i.e. all getting the same answer), and change
21976 their exit policy to reject *:* if it's happening.
21977 - Implement BEGIN_DIR cells, so we can connect to the directory
21978 server via TLS to do encrypted directory requests rather than
21979 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
21980 config options if you like.
21982 o Minor features (config and docs):
21983 - Start using the state file to store bandwidth accounting data:
21984 the bw_accounting file is now obsolete. We'll keep generating it
21985 for a while for people who are still using 0.1.2.4-alpha.
21986 - Try to batch changes to the state file so that we do as few
21987 disk writes as possible while still storing important things in
21989 - The state file and the bw_accounting file get saved less often when
21990 the AvoidDiskWrites config option is set.
21991 - Make PIDFile work on Windows (untested).
21992 - Add internal descriptions for a bunch of configuration options:
21993 accessible via controller interface and in comments in saved
21995 - Reject *:563 (NNTPS) in the default exit policy. We already reject
21996 NNTP by default, so this seems like a sensible addition.
21997 - Clients now reject hostnames with invalid characters. This should
21998 avoid some inadvertent info leaks. Add an option
21999 AllowNonRFC953Hostnames to disable this behavior, in case somebody
22000 is running a private network with hosts called @, !, and #.
22001 - Add a maintainer script to tell us which options are missing
22002 documentation: "make check-docs".
22003 - Add a new address-spec.txt document to describe our special-case
22004 addresses: .exit, .onion, and .noconnnect.
22006 o Minor features (DNS):
22007 - Ongoing work on eventdns infrastructure: now it has dns server
22008 and ipv6 support. One day Tor will make use of it.
22009 - Add client-side caching for reverse DNS lookups.
22010 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
22011 - When we change nameservers or IP addresses, reset and re-launch
22012 our tests for DNS hijacking.
22014 o Minor features (directory):
22015 - Authorities now specify server versions in networkstatus. This adds
22016 about 2% to the size of compressed networkstatus docs, and allows
22017 clients to tell which servers support BEGIN_DIR and which don't.
22018 The implementation is forward-compatible with a proposed future
22019 protocol version scheme not tied to Tor versions.
22020 - DirServer configuration lines now have an orport= option so
22021 clients can open encrypted tunnels to the authorities without
22022 having downloaded their descriptors yet. Enabled for moria1,
22023 moria2, tor26, and lefkada now in the default configuration.
22024 - Directory servers are more willing to send a 503 "busy" if they
22025 are near their write limit, especially for v1 directory requests.
22026 Now they can use their limited bandwidth for actual Tor traffic.
22027 - Clients track responses with status 503 from dirservers. After a
22028 dirserver has given us a 503, we try not to use it until an hour has
22029 gone by, or until we have no dirservers that haven't given us a 503.
22030 - When we get a 503 from a directory, and we're not a server, we don't
22031 count the failure against the total number of failures allowed
22032 for the thing we're trying to download.
22033 - Report X-Your-Address-Is correctly from tunneled directory
22034 connections; don't report X-Your-Address-Is when it's an internal
22035 address; and never believe reported remote addresses when they're
22037 - Protect against an unlikely DoS attack on directory servers.
22038 - Add a BadDirectory flag to network status docs so that authorities
22039 can (eventually) tell clients about caches they believe to be
22042 o Minor features (controller):
22043 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
22044 - Reimplement GETINFO so that info/names stays in sync with the
22046 - Implement "GETINFO fingerprint".
22047 - Implement "SETEVENTS GUARD" so controllers can get updates on
22048 entry guard status as it changes.
22050 o Minor features (clean up obsolete pieces):
22051 - Remove some options that have been deprecated since at least
22052 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
22053 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
22054 to set log options.
22055 - We no longer look for identity and onion keys in "identity.key" and
22056 "onion.key" -- these were replaced by secret_id_key and
22057 secret_onion_key in 0.0.8pre1.
22058 - We no longer require unrecognized directory entries to be
22061 o Major bugfixes (security):
22062 - Stop sending the HttpProxyAuthenticator string to directory
22063 servers when directory connections are tunnelled through Tor.
22064 - Clients no longer store bandwidth history in the state file.
22065 - Do not log introduction points for hidden services if SafeLogging
22067 - When generating bandwidth history, round down to the nearest
22068 1k. When storing accounting data, round up to the nearest 1k.
22069 - When we're running as a server, remember when we last rotated onion
22070 keys, so that we will rotate keys once they're a week old even if
22071 we never stay up for a week ourselves.
22073 o Major bugfixes (other):
22074 - Fix a longstanding bug in eventdns that prevented the count of
22075 timed-out resolves from ever being reset. This bug caused us to
22076 give up on a nameserver the third time it timed out, and try it
22077 10 seconds later... and to give up on it every time it timed out
22079 - Take out the '5 second' timeout from the connection retry
22080 schedule. Now the first connect attempt will wait a full 10
22081 seconds before switching to a new circuit. Perhaps this will help
22082 a lot. Based on observations from Mike Perry.
22083 - Fix a bug on the Windows implementation of tor_mmap_file() that
22084 would prevent the cached-routers file from ever loading. Reported
22088 - Fix an assert failure when a directory authority sets
22089 AuthDirRejectUnlisted and then receives a descriptor from an
22090 unlisted router. Reported by seeess.
22091 - Avoid a double-free when parsing malformed DirServer lines.
22092 - Fix a bug when a BSD-style PF socket is first used. Patch from
22094 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
22095 to resolve an address at a given exit node even when they ask for
22097 - Servers no longer ever list themselves in their "family" line,
22098 even if configured to do so. This makes it easier to configure
22099 family lists conveniently.
22100 - When running as a server, don't fall back to 127.0.0.1 when no
22101 nameservers are configured in /etc/resolv.conf; instead, make the
22102 user fix resolv.conf or specify nameservers explicitly. (Resolves
22104 - Stop accepting certain malformed ports in configured exit policies.
22105 - Don't re-write the fingerprint file every restart, unless it has
22107 - Stop warning when a single nameserver fails: only warn when _all_ of
22108 our nameservers have failed. Also, when we only have one nameserver,
22109 raise the threshold for deciding that the nameserver is dead.
22110 - Directory authorities now only decide that routers are reachable
22111 if their identity keys are as expected.
22112 - When the user uses bad syntax in the Log config line, stop
22113 suggesting other bad syntax as a replacement.
22114 - Correctly detect ipv6 DNS capability on OpenBSD.
22116 o Minor bugfixes (controller):
22117 - Report the circuit number correctly in STREAM CLOSED events. Bug
22118 reported by Mike Perry.
22119 - Do not report bizarre values for results of accounting GETINFOs
22120 when the last second's write or read exceeds the allotted bandwidth.
22121 - Report "unrecognized key" rather than an empty string when the
22122 controller tries to fetch a networkstatus that doesn't exist.
22125 Changes in version 0.1.1.26 - 2006-12-14
22126 o Security bugfixes:
22127 - Stop sending the HttpProxyAuthenticator string to directory
22128 servers when directory connections are tunnelled through Tor.
22129 - Clients no longer store bandwidth history in the state file.
22130 - Do not log introduction points for hidden services if SafeLogging
22134 - Fix an assert failure when a directory authority sets
22135 AuthDirRejectUnlisted and then receives a descriptor from an
22136 unlisted router (reported by seeess).
22139 Changes in version 0.1.2.4-alpha - 2006-12-03
22141 - Add support for using natd; this allows FreeBSDs earlier than
22142 5.1.2 to have ipfw send connections through Tor without using
22143 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
22146 - Make all connections to addresses of the form ".noconnect"
22147 immediately get closed. This lets application/controller combos
22148 successfully test whether they're talking to the same Tor by
22149 watching for STREAM events.
22150 - Make cross.sh cross-compilation script work even when autogen.sh
22151 hasn't been run. (Patch from Michael Mohr.)
22152 - Statistics dumped by -USR2 now include a breakdown of public key
22153 operations, for profiling.
22156 - Fix a major leak when directory authorities parse their
22157 approved-routers list, a minor memory leak when we fail to pick
22158 an exit node, and a few rare leaks on errors.
22159 - Handle TransPort connections even when the server sends data before
22160 the client sends data. Previously, the connection would just hang
22161 until the client sent data. (Patch from tup based on patch from
22163 - Avoid assert failure when our cached-routers file is empty on
22167 - Don't log spurious warnings when we see a circuit close reason we
22168 don't recognize; it's probably just from a newer version of Tor.
22169 - Have directory authorities allow larger amounts of drift in uptime
22170 without replacing the server descriptor: previously, a server that
22171 restarted every 30 minutes could have 48 "interesting" descriptors
22173 - Start linking to the Tor specification and Tor reference manual
22174 correctly in the Windows installer.
22175 - Add Vidalia to the OS X uninstaller script, so when we uninstall
22176 Tor/Privoxy we also uninstall Vidalia.
22177 - Resume building on Irix64, and fix a lot of warnings from its
22178 MIPSpro C compiler.
22179 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
22180 when we're running as a client.
22183 Changes in version 0.1.1.25 - 2006-11-04
22185 - When a client asks us to resolve (rather than connect to)
22186 an address, and we have a cached answer, give them the cached
22187 answer. Previously, we would give them no answer at all.
22188 - We were building exactly the wrong circuits when we predict
22189 hidden service requirements, meaning Tor would have to build all
22190 its circuits on demand.
22191 - If none of our live entry guards have a high uptime, but we
22192 require a guard with a high uptime, try adding a new guard before
22193 we give up on the requirement. This patch should make long-lived
22194 connections more stable on average.
22195 - When testing reachability of our DirPort, don't launch new
22196 tests when there's already one in progress -- unreachable
22197 servers were stacking up dozens of testing streams.
22199 o Security bugfixes:
22200 - When the user sends a NEWNYM signal, clear the client-side DNS
22201 cache too. Otherwise we continue to act on previous information.
22204 - Avoid a memory corruption bug when creating a hash table for
22206 - Avoid possibility of controller-triggered crash when misusing
22207 certain commands from a v0 controller on platforms that do not
22208 handle printf("%s",NULL) gracefully.
22209 - Avoid infinite loop on unexpected controller input.
22210 - Don't log spurious warnings when we see a circuit close reason we
22211 don't recognize; it's probably just from a newer version of Tor.
22212 - Add Vidalia to the OS X uninstaller script, so when we uninstall
22213 Tor/Privoxy we also uninstall Vidalia.
22216 Changes in version 0.1.2.3-alpha - 2006-10-29
22218 - Prepare for servers to publish descriptors less often: never
22219 discard a descriptor simply for being too old until either it is
22220 recommended by no authorities, or until we get a better one for
22221 the same router. Make caches consider retaining old recommended
22222 routers for even longer.
22223 - If most authorities set a BadExit flag for a server, clients
22224 don't think of it as a general-purpose exit. Clients only consider
22225 authorities that advertise themselves as listing bad exits.
22226 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
22227 headers for content, so that we can work better in the presence of
22228 caching HTTP proxies.
22229 - Allow authorities to list nodes as bad exits by fingerprint or by
22232 o Minor features, controller:
22233 - Add a REASON field to CIRC events; for backward compatibility, this
22234 field is sent only to controllers that have enabled the extended
22235 event format. Also, add additional reason codes to explain why
22236 a given circuit has been destroyed or truncated. (Patches from
22238 - Add a REMOTE_REASON field to extended CIRC events to tell the
22239 controller about why a remote OR told us to close a circuit.
22240 - Stream events also now have REASON and REMOTE_REASON fields,
22241 working much like those for circuit events.
22242 - There's now a GETINFO ns/... field so that controllers can ask Tor
22243 about the current status of a router.
22244 - A new event type "NS" to inform a controller when our opinion of
22245 a router's status has changed.
22246 - Add a GETINFO events/names and GETINFO features/names so controllers
22247 can tell which events and features are supported.
22248 - A new CLEARDNSCACHE signal to allow controllers to clear the
22249 client-side DNS cache without expiring circuits.
22251 o Security bugfixes:
22252 - When the user sends a NEWNYM signal, clear the client-side DNS
22253 cache too. Otherwise we continue to act on previous information.
22256 - Avoid sending junk to controllers or segfaulting when a controller
22257 uses EVENT_NEW_DESC with verbose nicknames.
22258 - Stop triggering asserts if the controller tries to extend hidden
22259 service circuits (reported by mwenge).
22260 - Avoid infinite loop on unexpected controller input.
22261 - When the controller does a "GETINFO network-status", tell it
22262 about even those routers whose descriptors are very old, and use
22263 long nicknames where appropriate.
22264 - Change NT service functions to be loaded on demand. This lets us
22265 build with MinGW without breaking Tor for Windows 98 users.
22266 - Do DirPort reachability tests less often, since a single test
22267 chews through many circuits before giving up.
22268 - In the hidden service example in torrc.sample, stop recommending
22269 esoteric and discouraged hidden service options.
22270 - When stopping an NT service, wait up to 10 sec for it to actually
22271 stop. Patch from Matt Edman; resolves bug 295.
22272 - Fix handling of verbose nicknames with ORCONN controller events:
22273 make them show up exactly when requested, rather than exactly when
22275 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
22276 printing a duplicate "$" in the keys we send (reported by mwenge).
22277 - Correctly set maximum connection limit on Cygwin. (This time
22279 - Try to detect Windows correctly when cross-compiling.
22280 - Detect the size of the routers file correctly even if it is
22281 corrupted (on systems without mmap) or not page-aligned (on systems
22282 with mmap). This bug was harmless.
22283 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
22284 to open a stream fails; now we do in more cases. This should
22285 make clients able to find a good exit faster in some cases, since
22286 unhandleable requests will now get an error rather than timing out.
22287 - Resolve two memory leaks when rebuilding the on-disk router cache
22288 (reported by fookoowa).
22289 - Clean up minor code warnings suggested by the MIPSpro C compiler,
22290 and reported by some Centos users.
22291 - Controller signals now work on non-Unix platforms that don't define
22292 SIGUSR1 and SIGUSR2 the way we expect.
22293 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
22294 values before failing, and always enables eventdns.
22295 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
22296 Try to fix this in configure.in by checking for most functions
22297 before we check for libevent.
22300 Changes in version 0.1.2.2-alpha - 2006-10-07
22302 - Make our async eventdns library on-by-default for Tor servers,
22303 and plan to deprecate the separate dnsworker threads.
22304 - Add server-side support for "reverse" DNS lookups (using PTR
22305 records so clients can determine the canonical hostname for a given
22306 IPv4 address). Only supported by servers using eventdns; servers
22307 now announce in their descriptors whether they support eventdns.
22308 - Specify and implement client-side SOCKS5 interface for reverse DNS
22309 lookups (see doc/socks-extensions.txt).
22310 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
22311 connect to directory servers through Tor. Previously, clients needed
22312 to find Tor exits to make private connections to directory servers.
22313 - Avoid choosing Exit nodes for entry or middle hops when the
22314 total bandwidth available from non-Exit nodes is much higher than
22315 the total bandwidth available from Exit nodes.
22316 - Workaround for name servers (like Earthlink's) that hijack failing
22317 DNS requests and replace the no-such-server answer with a "helpful"
22318 redirect to an advertising-driven search portal. Also work around
22319 DNS hijackers who "helpfully" decline to hijack known-invalid
22320 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
22321 lets you turn it off.
22322 - Send out a burst of long-range padding cells once we've established
22323 that we're reachable. Spread them over 4 circuits, so hopefully
22324 a few will be fast. This exercises our bandwidth and bootstraps
22325 us into the directory more quickly.
22327 o New/improved config options:
22328 - Add new config option "ResolvConf" to let the server operator
22329 choose an alternate resolve.conf file when using eventdns.
22330 - Add an "EnforceDistinctSubnets" option to control our "exclude
22331 servers on the same /16" behavior. It's still on by default; this
22332 is mostly for people who want to operate private test networks with
22333 all the machines on the same subnet.
22334 - If one of our entry guards is on the ExcludeNodes list, or the
22335 directory authorities don't think it's a good guard, treat it as
22336 if it were unlisted: stop using it as a guard, and throw it off
22337 the guards list if it stays that way for a long time.
22338 - Allow directory authorities to be marked separately as authorities
22339 for the v1 directory protocol, the v2 directory protocol, and
22340 as hidden service directories, to make it easier to retire old
22341 authorities. V1 authorities should set "HSAuthoritativeDir 1"
22342 to continue being hidden service authorities too.
22343 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
22345 o Minor features, controller:
22346 - Fix CIRC controller events so that controllers can learn the
22347 identity digests of non-Named servers used in circuit paths.
22348 - Let controllers ask for more useful identifiers for servers. Instead
22349 of learning identity digests for un-Named servers and nicknames
22350 for Named servers, the new identifiers include digest, nickname,
22351 and indication of Named status. Off by default; see control-spec.txt
22352 for more information.
22353 - Add a "getinfo address" controller command so it can display Tor's
22354 best guess to the user.
22355 - New controller event to alert the controller when our server
22356 descriptor has changed.
22357 - Give more meaningful errors on controller authentication failure.
22359 o Minor features, other:
22360 - When asked to resolve a hostname, don't use non-exit servers unless
22361 requested to do so. This allows servers with broken DNS to be
22362 useful to the network.
22363 - Divide eventdns log messages into warn and info messages.
22364 - Reserve the nickname "Unnamed" for routers that can't pick
22365 a hostname: any router can call itself Unnamed; directory
22366 authorities will never allocate Unnamed to any particular router;
22367 clients won't believe that any router is the canonical Unnamed.
22368 - Only include function names in log messages for info/debug messages.
22369 For notice/warn/err, the content of the message should be clear on
22370 its own, and printing the function name only confuses users.
22371 - Avoid some false positives during reachability testing: don't try
22372 to test via a server that's on the same /24 as us.
22373 - If we fail to build a circuit to an intended enclave, and it's
22374 not mandatory that we use that enclave, stop wanting it.
22375 - When eventdns is enabled, allow multithreaded builds on NetBSD and
22376 OpenBSD. (We had previously disabled threads on these platforms
22377 because they didn't have working thread-safe resolver functions.)
22379 o Major bugfixes, anonymity/security:
22380 - If a client asked for a server by name, and there's a named server
22381 in our network-status but we don't have its descriptor yet, we
22382 could return an unnamed server instead.
22383 - Fix NetBSD bug that could allow someone to force uninitialized RAM
22384 to be sent to a server's DNS resolver. This only affects NetBSD
22385 and other platforms that do not bounds-check tolower().
22386 - Reject (most) attempts to use Tor circuits with length one. (If
22387 many people start using Tor as a one-hop proxy, exit nodes become
22388 a more attractive target for compromise.)
22389 - Just because your DirPort is open doesn't mean people should be
22390 able to remotely teach you about hidden service descriptors. Now
22391 only accept rendezvous posts if you've got HSAuthoritativeDir set.
22393 o Major bugfixes, other:
22394 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
22395 - When a client asks the server to resolve (not connect to)
22396 an address, and it has a cached answer, give them the cached answer.
22397 Previously, the server would give them no answer at all.
22398 - Allow really slow clients to not hang up five minutes into their
22399 directory downloads (suggested by Adam J. Richter).
22400 - We were building exactly the wrong circuits when we anticipated
22401 hidden service requirements, meaning Tor would have to build all
22402 its circuits on demand.
22403 - Avoid crashing when we mmap a router cache file of size 0.
22404 - When testing reachability of our DirPort, don't launch new
22405 tests when there's already one in progress -- unreachable
22406 servers were stacking up dozens of testing streams.
22408 o Minor bugfixes, correctness:
22409 - If we're a directory mirror and we ask for "all" network status
22410 documents, we would discard status documents from authorities
22411 we don't recognize.
22412 - Avoid a memory corruption bug when creating a hash table for
22414 - Avoid controller-triggered crash when misusing certain commands
22415 from a v0 controller on platforms that do not handle
22416 printf("%s",NULL) gracefully.
22417 - Don't crash when a controller sends a third argument to an
22418 "extendcircuit" request.
22419 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
22420 response; fix error code when "getinfo dir/status/" fails.
22421 - Avoid crash when telling controller stream-status and a stream
22423 - Patch from Adam Langley to fix assert() in eventdns.c.
22424 - Fix a debug log message in eventdns to say "X resolved to Y"
22425 instead of "X resolved to X".
22426 - Make eventdns give strings for DNS errors, not just error numbers.
22427 - Track unreachable entry guards correctly: don't conflate
22428 'unreachable by us right now' with 'listed as down by the directory
22429 authorities'. With the old code, if a guard was unreachable by
22430 us but listed as running, it would clog our guard list forever.
22431 - Behave correctly in case we ever have a network with more than
22432 2GB/s total advertised capacity.
22433 - Make TrackExitHosts case-insensitive, and fix the behavior of
22434 ".suffix" TrackExitHosts items to avoid matching in the middle of
22436 - Finally fix the openssl warnings from newer gccs that believe that
22437 ignoring a return value is okay, but casting a return value and
22438 then ignoring it is a sign of madness.
22439 - Prevent the contrib/exitlist script from printing the same
22440 result more than once.
22441 - Patch from Steve Hildrey: Generate network status correctly on
22442 non-versioning dirservers.
22443 - Don't listen to the X-Your-Address-Is hint if you did the lookup
22444 via Tor; otherwise you'll think you're the exit node's IP address.
22446 o Minor bugfixes, performance:
22447 - Two small performance improvements on parsing descriptors.
22448 - Major performance improvement on inserting descriptors: change
22449 algorithm from O(n^2) to O(n).
22450 - Make the common memory allocation path faster on machines where
22451 malloc(0) returns a pointer.
22452 - Start remembering X-Your-Address-Is directory hints even if you're
22453 a client, so you can become a server more smoothly.
22454 - Avoid duplicate entries on MyFamily line in server descriptor.
22456 o Packaging, features:
22457 - Remove architecture from OS X builds. The official builds are
22458 now universal binaries.
22459 - The Debian package now uses --verify-config when (re)starting,
22460 to distinguish configuration errors from other errors.
22461 - Update RPMs to require libevent 1.1b.
22463 o Packaging, bugfixes:
22464 - Patches so Tor builds with MinGW on Windows.
22465 - Patches so Tor might run on Cygwin again.
22466 - Resume building on non-gcc compilers and ancient gcc. Resume
22467 building with the -O0 compile flag. Resume building cleanly on
22469 - Run correctly on OS X platforms with case-sensitive filesystems.
22470 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
22471 - Add autoconf checks so Tor can build on Solaris x86 again.
22474 - Documented (and renamed) ServerDNSSearchDomains and
22475 ServerDNSResolvConfFile options.
22476 - Be clearer that the *ListenAddress directives can be repeated
22480 Changes in version 0.1.1.24 - 2006-09-29
22482 - Allow really slow clients to not hang up five minutes into their
22483 directory downloads (suggested by Adam J. Richter).
22484 - Fix major performance regression from 0.1.0.x: instead of checking
22485 whether we have enough directory information every time we want to
22486 do something, only check when the directory information has changed.
22487 This should improve client CPU usage by 25-50%.
22488 - Don't crash if, after a server has been running for a while,
22489 it can't resolve its hostname.
22492 - Allow Tor to start when RunAsDaemon is set but no logs are set.
22493 - Don't crash when the controller receives a third argument to an
22494 "extendcircuit" request.
22495 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
22496 response; fix error code when "getinfo dir/status/" fails.
22497 - Fix configure.in to not produce broken configure files with
22498 more recent versions of autoconf. Thanks to Clint for his auto*
22500 - Fix security bug on NetBSD that could allow someone to force
22501 uninitialized RAM to be sent to a server's DNS resolver. This
22502 only affects NetBSD and other platforms that do not bounds-check
22504 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
22505 methods: these are known to be buggy.
22506 - If we're a directory mirror and we ask for "all" network status
22507 documents, we would discard status documents from authorities
22508 we don't recognize.
22511 Changes in version 0.1.2.1-alpha - 2006-08-27
22513 - Add "eventdns" async dns library from Adam Langley, tweaked to
22514 build on OSX and Windows. Only enabled if you pass the
22515 --enable-eventdns argument to configure.
22516 - Allow servers with no hostname or IP address to learn their
22517 IP address by asking the directory authorities. This code only
22518 kicks in when you would normally have exited with a "no address"
22519 error. Nothing's authenticated, so use with care.
22520 - Rather than waiting a fixed amount of time between retrying
22521 application connections, we wait only 5 seconds for the first,
22522 10 seconds for the second, and 15 seconds for each retry after
22523 that. Hopefully this will improve the expected user experience.
22524 - Patch from Tup to add support for transparent AP connections:
22525 this basically bundles the functionality of trans-proxy-tor
22526 into the Tor mainline. Now hosts with compliant pf/netfilter
22527 implementations can redirect TCP connections straight to Tor
22528 without diverting through SOCKS. Needs docs.
22529 - Busy directory servers save lots of memory by spooling server
22530 descriptors, v1 directories, and v2 networkstatus docs to buffers
22531 as needed rather than en masse. Also mmap the cached-routers
22532 files, so we don't need to keep the whole thing in memory too.
22533 - Automatically avoid picking more than one node from the same
22534 /16 network when constructing a circuit.
22535 - Revise and clean up the torrc.sample that we ship with; add
22536 a section for BandwidthRate and BandwidthBurst.
22539 - Split circuit_t into origin_circuit_t and or_circuit_t, and
22540 split connection_t into edge, or, dir, control, and base structs.
22541 These will save quite a bit of memory on busy servers, and they'll
22542 also help us track down bugs in the code and bugs in the spec.
22543 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
22544 or later. Log when we are doing this, so we can diagnose it when
22545 it fails. (Also, recommend libevent 1.1b for kqueue and
22546 win32 methods; deprecate libevent 1.0b harder; make libevent
22547 recommendation system saner.)
22548 - Start being able to build universal binaries on OS X (thanks
22550 - Export the default exit policy via the control port, so controllers
22551 don't need to guess what it is / will be later.
22552 - Add a man page entry for ProtocolWarnings.
22553 - Add TestVia config option to the man page.
22554 - Remove even more protocol-related warnings from Tor server logs,
22555 such as bad TLS handshakes and malformed begin cells.
22556 - Stop fetching descriptors if you're not a dir mirror and you
22557 haven't tried to establish any circuits lately. [This currently
22558 causes some dangerous behavior, because when you start up again
22559 you'll use your ancient server descriptors.]
22560 - New DirPort behavior: if you have your dirport set, you download
22561 descriptors aggressively like a directory mirror, whether or not
22562 your ORPort is set.
22563 - Get rid of the router_retry_connections notion. Now routers
22564 no longer try to rebuild long-term connections to directory
22565 authorities, and directory authorities no longer try to rebuild
22566 long-term connections to all servers. We still don't hang up
22567 connections in these two cases though -- we need to look at it
22568 more carefully to avoid flapping, and we likely need to wait til
22569 0.1.1.x is obsolete.
22570 - Drop compatibility with obsolete Tors that permit create cells
22571 to have the wrong circ_id_type.
22572 - Re-enable per-connection rate limiting. Get rid of the "OP
22573 bandwidth" concept. Lay groundwork for "bandwidth classes" --
22574 separate global buckets that apply depending on what sort of conn
22576 - Start publishing one minute or so after we find our ORPort
22577 to be reachable. This will help reduce the number of descriptors
22578 we have for ourselves floating around, since it's quite likely
22579 other things (e.g. DirPort) will change during that minute too.
22580 - Fork the v1 directory protocol into its own spec document,
22581 and mark dir-spec.txt as the currently correct (v2) spec.
22584 - When we find our DirPort to be reachable, publish a new descriptor
22585 so we'll tell the world (reported by pnx).
22586 - Publish a new descriptor after we hup/reload. This is important
22587 if our config has changed such that we'll want to start advertising
22588 our DirPort now, etc.
22589 - Allow Tor to start when RunAsDaemon is set but no logs are set.
22590 - When we have a state file we cannot parse, tell the user and
22591 move it aside. Now we avoid situations where the user starts
22592 Tor in 1904, Tor writes a state file with that timestamp in it,
22593 the user fixes her clock, and Tor refuses to start.
22594 - Fix configure.in to not produce broken configure files with
22595 more recent versions of autoconf. Thanks to Clint for his auto*
22597 - "tor --verify-config" now exits with -1(255) or 0 depending on
22598 whether the config options are bad or good.
22599 - Resolve bug 321 when using dnsworkers: append a period to every
22600 address we resolve at the exit node, so that we do not accidentally
22601 pick up local addresses, and so that failing searches are retried
22602 in the resolver search domains. (This is already solved for
22603 eventdns.) (This breaks Blossom servers for now.)
22604 - If we are using an exit enclave and we can't connect, e.g. because
22605 its webserver is misconfigured to not listen on localhost, then
22606 back off and try connecting from somewhere else before we fail.
22609 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
22610 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
22611 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
22612 when the IP address is mapped through MapAddress to a hostname.
22613 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
22614 useless IPv6 DNS resolves.
22615 - Patch suggested by Karsten Loesing: respond to SIGNAL command
22616 before we execute the signal, in case the signal shuts us down.
22617 - Clean up AllowInvalidNodes man page entry.
22618 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
22619 - Add more asserts to track down an assert error on a windows Tor
22620 server with connection_add being called with socket == -1.
22621 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
22622 - Fix misleading log messages: an entry guard that is "unlisted",
22623 as well as not known to be "down" (because we've never heard
22624 of it), is not therefore "up".
22625 - Remove code to special-case "-cvs" ending, since it has not
22626 actually mattered since 0.0.9.
22627 - Make our socks5 handling more robust to broken socks clients:
22628 throw out everything waiting on the buffer in between socks
22629 handshake phases, since they can't possibly (so the theory
22630 goes) have predicted what we plan to respond to them.
22633 Changes in version 0.1.1.23 - 2006-07-30
22635 - Fast Tor servers, especially exit nodes, were triggering asserts
22636 due to a bug in handling the list of pending DNS resolves. Some
22637 bugs still remain here; we're hunting them.
22638 - Entry guards could crash clients by sending unexpected input.
22639 - More fixes on reachability testing: if you find yourself reachable,
22640 then don't ever make any client requests (so you stop predicting
22641 circuits), then hup or have your clock jump, then later your IP
22642 changes, you won't think circuits are working, so you won't try to
22643 test reachability, so you won't publish.
22646 - Avoid a crash if the controller does a resetconf firewallports
22647 and then a setconf fascistfirewall=1.
22648 - Avoid an integer underflow when the dir authority decides whether
22649 a router is stable: we might wrongly label it stable, and compute
22650 a slightly wrong median stability, when a descriptor is published
22652 - Fix a place where we might trigger an assert if we can't build our
22653 own server descriptor yet.
22656 Changes in version 0.1.1.22 - 2006-07-05
22658 - Fix a big bug that was causing servers to not find themselves
22659 reachable if they changed IP addresses. Since only 0.1.1.22+
22660 servers can do reachability testing correctly, now we automatically
22661 make sure to test via one of these.
22662 - Fix to allow clients and mirrors to learn directory info from
22663 descriptor downloads that get cut off partway through.
22664 - Directory authorities had a bug in deciding if a newly published
22665 descriptor was novel enough to make everybody want a copy -- a few
22666 servers seem to be publishing new descriptors many times a minute.
22668 - Fix a rare bug that was causing some servers to complain about
22669 "closing wedged cpuworkers" and skip some circuit create requests.
22670 - Make the Exit flag in directory status documents actually work.
22673 Changes in version 0.1.1.21 - 2006-06-10
22674 o Crash and assert fixes from 0.1.1.20:
22675 - Fix a rare crash on Tor servers that have enabled hibernation.
22676 - Fix a seg fault on startup for Tor networks that use only one
22677 directory authority.
22678 - Fix an assert from a race condition that occurs on Tor servers
22679 while exiting, where various threads are trying to log that they're
22680 exiting, and delete the logs, at the same time.
22681 - Make our unit tests pass again on certain obscure platforms.
22684 - Add support for building SUSE RPM packages.
22685 - Speed up initial bootstrapping for clients: if we are making our
22686 first ever connection to any entry guard, then don't mark it down
22688 - When only one Tor server in the network is labelled as a guard,
22689 and we've already picked him, we would cycle endlessly picking him
22690 again, being unhappy about it, etc. Now we specifically exclude
22691 current guards when picking a new guard.
22692 - Servers send create cells more reliably after the TLS connection
22693 is established: we were sometimes forgetting to send half of them
22694 when we had more than one pending.
22695 - If we get a create cell that asks us to extend somewhere, but the
22696 Tor server there doesn't match the expected digest, we now send
22697 a destroy cell back, rather than silently doing nothing.
22698 - Make options->RedirectExit work again.
22699 - Make cookie authentication for the controller work again.
22700 - Stop being picky about unusual characters in the arguments to
22701 mapaddress. It's none of our business.
22702 - Add a new config option "TestVia" that lets you specify preferred
22703 middle hops to use for test circuits. Perhaps this will let me
22704 debug the reachability problems better.
22706 o Log / documentation fixes:
22707 - If we're a server and some peer has a broken TLS certificate, don't
22708 log about it unless ProtocolWarnings is set, i.e., we want to hear
22709 about protocol violations by others.
22710 - Fix spelling of VirtualAddrNetwork in man page.
22711 - Add a better explanation at the top of the autogenerated torrc file
22712 about what happened to our old torrc.
22715 Changes in version 0.1.1.20 - 2006-05-23
22717 - Downgrade a log severity where servers complain that they're
22719 - Avoid a compile warning on FreeBSD.
22720 - Remove string size limit on NEWDESC messages; solve bug 291.
22721 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
22722 more thoroughly when we're running on windows.
22725 Changes in version 0.1.1.19-rc - 2006-05-03
22727 - Regenerate our local descriptor if it's dirty and we try to use
22728 it locally (e.g. if it changes during reachability detection).
22729 - If we setconf our ORPort to 0, we continued to listen on the
22730 old ORPort and receive connections.
22731 - Avoid a second warning about machine/limits.h on Debian
22733 - Be willing to add our own routerinfo into the routerlist.
22734 Now authorities will include themselves in their directories
22735 and network-statuses.
22736 - Stop trying to upload rendezvous descriptors to every
22737 directory authority: only try the v1 authorities.
22738 - Servers no longer complain when they think they're not
22739 registered with the directory authorities. There were too many
22741 - Backport dist-rpm changes so rpms can be built without errors.
22744 - Implement an option, VirtualAddrMask, to set which addresses
22745 get handed out in response to mapaddress requests. This works
22746 around a bug in tsocks where 127.0.0.0/8 is never socksified.
22749 Changes in version 0.1.1.18-rc - 2006-04-10
22751 - Work harder to download live network-statuses from all the
22752 directory authorities we know about. Improve the threshold
22753 decision logic so we're more robust to edge cases.
22754 - When fetching rendezvous descriptors, we were willing to ask
22755 v2 authorities too, which would always return 404.
22758 - Stop listing down or invalid nodes in the v1 directory. This will
22759 reduce its bulk by about 1/3, and reduce load on directory
22761 - When deciding whether a router is Fast or Guard-worthy, consider
22762 his advertised BandwidthRate and not just the BandwidthCapacity.
22763 - No longer ship INSTALL and README files -- they are useless now.
22764 - Force rpmbuild to behave and honor target_cpu.
22765 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
22766 - Start to include translated versions of the tor-doc-*.html
22767 files, along with the screenshots. Still needs more work.
22768 - Start sending back 512 and 451 errors if mapaddress fails,
22769 rather than not sending anything back at all.
22770 - When we fail to bind or listen on an incoming or outgoing
22771 socket, we should close it before failing. otherwise we just
22772 leak it. (thanks to weasel for finding.)
22773 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
22774 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
22775 - Make NoPublish (even though deprecated) work again.
22776 - Fix a minor security flaw where a versioning auth dirserver
22777 could list a recommended version many times in a row to make
22778 clients more convinced that it's recommended.
22779 - Fix crash bug if there are two unregistered servers running
22780 with the same nickname, one of them is down, and you ask for
22781 them by nickname in your EntryNodes or ExitNodes. Also, try
22782 to pick the one that's running rather than an arbitrary one.
22783 - Fix an infinite loop we could hit if we go offline for too long.
22784 - Complain when we hit WSAENOBUFS on recv() or write() too.
22785 Perhaps this will help us hunt the bug.
22786 - If you're not a versioning dirserver, don't put the string
22787 "client-versions \nserver-versions \n" in your network-status.
22788 - Lower the minimum required number of file descriptors to 1000,
22789 so we can have some overhead for Valgrind on Linux, where the
22790 default ulimit -n is 1024.
22793 - Add tor.dizum.com as the fifth authoritative directory server.
22794 - Add a new config option FetchUselessDescriptors, off by default,
22795 for when you plan to run "exitlist" on your client and you want
22796 to know about even the non-running descriptors.
22799 Changes in version 0.1.1.17-rc - 2006-03-28
22801 - Clients and servers since 0.1.1.10-alpha have been expiring
22802 connections whenever they are idle for 5 minutes and they *do*
22803 have circuits on them. Oops. With this new version, clients will
22804 discard their previous entry guard choices and avoid choosing
22805 entry guards running these flawed versions.
22806 - Fix memory leak when uncompressing concatenated zlib streams. This
22807 was causing substantial leaks over time on Tor servers.
22808 - The v1 directory was including servers as much as 48 hours old,
22809 because that's how the new routerlist->routers works. Now only
22810 include them if they're 20 hours old or less.
22813 - Resume building on irix64, netbsd 2.0, etc.
22814 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
22816 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
22817 and it is confusing some users.
22818 - Mirrors stop caching the v1 directory so often.
22819 - Make the max number of old descriptors that a cache will hold
22820 rise with the number of directory authorities, so we can scale.
22821 - Change our win32 uname() hack to be more forgiving about what
22822 win32 versions it thinks it's found.
22825 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
22827 - When the controller's *setconf commands fail, collect an error
22828 message in a string and hand it back to the controller.
22829 - Make the v2 dir's "Fast" flag based on relative capacity, just
22830 like "Stable" is based on median uptime. Name everything in the
22831 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
22832 - Log server fingerprint on startup, so new server operators don't
22833 have to go hunting around their filesystem for it.
22834 - Return a robots.txt on our dirport to discourage google indexing.
22835 - Let the controller ask for GETINFO dir/status/foo so it can ask
22836 directly rather than connecting to the dir port. Only works when
22837 dirport is set for now.
22839 o New config options rather than constants in the code:
22840 - SocksTimeout: How long do we let a socks connection wait
22841 unattached before we fail it?
22842 - CircuitBuildTimeout: Cull non-open circuits that were born
22843 at least this many seconds ago.
22844 - CircuitIdleTimeout: Cull open clean circuits that were born
22845 at least this many seconds ago.
22848 Changes in version 0.1.1.16-rc - 2006-03-18
22849 o Bugfixes on 0.1.1.15-rc:
22850 - Fix assert when the controller asks to attachstream a connect-wait
22851 or resolve-wait stream.
22852 - Now do address rewriting when the controller asks us to attach
22853 to a particular circuit too. This will let Blossom specify
22854 "moria2.exit" without having to learn what moria2's IP address is.
22855 - Make the "tor --verify-config" command-line work again, so people
22856 can automatically check if their torrc will parse.
22857 - Authoritative dirservers no longer require an open connection from
22858 a server to consider him "reachable". We need this change because
22859 when we add new auth dirservers, old servers won't know not to
22861 - Let Tor build on Sun CC again.
22862 - Fix an off-by-one buffer size in dirserv.c that magically never
22863 hit our three authorities but broke sjmurdoch's own tor network.
22864 - If we as a directory mirror don't know of any v1 directory
22865 authorities, then don't try to cache any v1 directories.
22866 - Stop warning about unknown servers in our family when they are
22867 given as hex digests.
22868 - Stop complaining as quickly to the server operator that he
22869 hasn't registered his nickname/key binding.
22870 - Various cleanups so we can add new V2 Auth Dirservers.
22871 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
22872 reflect the updated flags in our v2 dir protocol.
22873 - Resume allowing non-printable characters for exit streams (both
22874 for connecting and for resolving). Now we tolerate applications
22875 that don't follow the RFCs. But continue to block malformed names
22878 o Bugfixes on 0.1.0.x:
22879 - Fix assert bug in close_logs(): when we close and delete logs,
22880 remove them all from the global "logfiles" list.
22881 - Fix minor integer overflow in calculating when we expect to use up
22882 our bandwidth allocation before hibernating.
22883 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
22884 there are multiple SSLs installed with different versions.
22885 - When we try to be a server and Address is not explicitly set and
22886 our hostname resolves to a private IP address, try to use an
22887 interface address if it has a public address. Now Windows machines
22888 that think of themselves as localhost can work by default.
22891 - Let the controller ask for GETINFO dir/server/foo so it can ask
22892 directly rather than connecting to the dir port.
22893 - Let the controller tell us about certain router descriptors
22894 that it doesn't want Tor to use in circuits. Implement
22895 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
22896 - New config option SafeSocks to reject all application connections
22897 using unsafe socks protocols. Defaults to off.
22900 Changes in version 0.1.1.15-rc - 2006-03-11
22901 o Bugfixes and cleanups:
22902 - When we're printing strings from the network, don't try to print
22903 non-printable characters. This protects us against shell escape
22904 sequence exploits, and also against attacks to fool humans into
22905 misreading their logs.
22906 - Fix a bug where Tor would fail to establish any connections if you
22907 left it off for 24 hours and then started it: we were happy with
22908 the obsolete network statuses, but they all referred to router
22909 descriptors that were too old to fetch, so we ended up with no
22910 valid router descriptors.
22911 - Fix a seg fault in the controller's "getinfo orconn-status"
22912 command while listing status on incoming handshaking connections.
22913 Introduce a status name "NEW" for these connections.
22914 - If we get a linelist or linelist_s config option from the torrc
22915 (e.g. ExitPolicy) and it has no value, warn and skip rather than
22916 silently resetting it to its default.
22917 - Don't abandon entry guards until they've been down or gone for
22919 - Cleaner and quieter log messages.
22922 - New controller signal NEWNYM that makes new application requests
22923 use clean circuits.
22924 - Add a new circuit purpose 'controller' to let the controller ask
22925 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
22926 controller command to let you specify the purpose if you're
22927 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
22928 command to let you change a circuit's purpose after it's been
22930 - Accept "private:*" in routerdesc exit policies; not generated yet
22931 because older Tors do not understand it.
22932 - Add BSD-style contributed startup script "rc.subr" from Peter
22936 Changes in version 0.1.1.14-alpha - 2006-02-20
22937 o Bugfixes on 0.1.1.x:
22938 - Don't die if we ask for a stdout or stderr log (even implicitly)
22939 and we're set to RunAsDaemon -- just warn.
22940 - We still had a few bugs in the OR connection rotation code that
22941 caused directory servers to slowly aggregate connections to other
22942 fast Tor servers. This time for sure!
22943 - Make log entries on Win32 include the name of the function again.
22944 - We were treating a pair of exit policies if they were equal even
22945 if one said accept and the other said reject -- causing us to
22946 not always publish a new descriptor since we thought nothing
22948 - Retry pending server downloads as well as pending networkstatus
22949 downloads when we unexpectedly get a socks request.
22950 - We were ignoring the IS_FAST flag in the directory status,
22951 meaning we were willing to pick trivial-bandwidth nodes for "fast"
22953 - If the controller's SAVECONF command fails (e.g. due to file
22954 permissions), let the controller know that it failed.
22957 - If we're trying to be a Tor server and running Windows 95/98/ME
22958 as a server, explain that we'll likely crash.
22959 - When we're a server, a client asks for an old-style directory,
22960 and our write bucket is empty, don't give it to him. This way
22961 small servers can continue to serve the directory *sometimes*,
22962 without getting overloaded.
22963 - Compress exit policies even more -- look for duplicate lines
22965 - Clients now honor the "guard" flag in the router status when
22966 picking entry guards, rather than looking at is_fast or is_stable.
22967 - Retain unrecognized lines in $DATADIR/state file, so that we can
22968 be forward-compatible.
22969 - Generate 18.0.0.0/8 address policy format in descs when we can;
22970 warn when the mask is not reducible to a bit-prefix.
22971 - Let the user set ControlListenAddress in the torrc. This can be
22972 dangerous, but there are some cases (like a secured LAN) where it
22974 - Split ReachableAddresses into ReachableDirAddresses and
22975 ReachableORAddresses, so we can restrict Dir conns to port 80
22976 and OR conns to port 443.
22977 - Now we can target arch and OS in rpm builds (contributed by
22978 Phobos). Also make the resulting dist-rpm filename match the
22980 - New config options to help controllers: FetchServerDescriptors
22981 and FetchHidServDescriptors for whether to fetch server
22982 info and hidserv info or let the controller do it, and
22983 PublishServerDescriptor and PublishHidServDescriptors.
22984 - Also let the controller set the __AllDirActionsPrivate config
22985 option if you want all directory fetches/publishes to happen via
22986 Tor (it assumes your controller bootstraps your circuits).
22989 Changes in version 0.1.0.17 - 2006-02-17
22990 o Crash bugfixes on 0.1.0.x:
22991 - When servers with a non-zero DirPort came out of hibernation,
22992 sometimes they would trigger an assert.
22994 o Other important bugfixes:
22995 - On platforms that don't have getrlimit (like Windows), we were
22996 artificially constraining ourselves to a max of 1024
22997 connections. Now just assume that we can handle as many as 15000
22998 connections. Hopefully this won't cause other problems.
23000 o Backported features:
23001 - When we're a server, a client asks for an old-style directory,
23002 and our write bucket is empty, don't give it to him. This way
23003 small servers can continue to serve the directory *sometimes*,
23004 without getting overloaded.
23005 - Whenever you get a 503 in response to a directory fetch, try
23006 once more. This will become important once servers start sending
23007 503's whenever they feel busy.
23008 - Fetch a new directory every 120 minutes, not every 40 minutes.
23009 Now that we have hundreds of thousands of users running the old
23010 directory algorithm, it's starting to hurt a lot.
23011 - Bump up the period for forcing a hidden service descriptor upload
23012 from 20 minutes to 1 hour.
23015 Changes in version 0.1.1.13-alpha - 2006-02-09
23016 o Crashes in 0.1.1.x:
23017 - When you tried to setconf ORPort via the controller, Tor would
23018 crash. So people using TorCP to become a server were sad.
23019 - Solve (I hope) the stack-smashing bug that we were seeing on fast
23020 servers. The problem appears to be something do with OpenSSL's
23021 random number generation, or how we call it, or something. Let me
23022 know if the crashes continue.
23023 - Turn crypto hardware acceleration off by default, until we find
23024 somebody smart who can test it for us. (It appears to produce
23025 seg faults in at least some cases.)
23026 - Fix a rare assert error when we've tried all intro points for
23027 a hidden service and we try fetching the service descriptor again:
23028 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
23031 - Fix a major load balance bug: we were round-robining in 16 KB
23032 chunks, and servers with bandwidthrate of 20 KB, while downloading
23033 a 600 KB directory, would starve their other connections. Now we
23034 try to be a bit more fair.
23035 - Dir authorities and mirrors were never expiring the newest
23036 descriptor for each server, causing memory and directory bloat.
23037 - Fix memory-bloating and connection-bloating bug on servers: We
23038 were never closing any connection that had ever had a circuit on
23039 it, because we were checking conn->n_circuits == 0, yet we had a
23040 bug that let it go negative.
23041 - Make Tor work using squid as your http proxy again -- squid
23042 returns an error if you ask for a URL that's too long, and it uses
23043 a really generic error message. Plus, many people are behind a
23044 transparent squid so they don't even realize it.
23045 - On platforms that don't have getrlimit (like Windows), we were
23046 artificially constraining ourselves to a max of 1024
23047 connections. Now just assume that we can handle as many as 15000
23048 connections. Hopefully this won't cause other problems.
23049 - Add a new config option ExitPolicyRejectPrivate which defaults to
23050 1. This means all exit policies will begin with rejecting private
23051 addresses, unless the server operator explicitly turns it off.
23054 - Clients no longer download descriptors for non-running
23056 - Before we add new directory authorities, we should make it
23057 clear that only v1 authorities should receive/publish hidden
23058 service descriptors.
23061 - As soon as we've fetched some more directory info, immediately
23062 try to download more server descriptors. This way we don't have
23063 a 10 second pause during initial bootstrapping.
23064 - Remove even more loud log messages that the server operator can't
23066 - When we're running an obsolete or un-recommended version, make
23067 the log message more clear about what the problem is and what
23068 versions *are* still recommended.
23069 - Provide a more useful warn message when our onion queue gets full:
23070 the CPU is too slow or the exit policy is too liberal.
23071 - Don't warn when we receive a 503 from a dirserver/cache -- this
23072 will pave the way for them being able to refuse if they're busy.
23073 - When we fail to bind a listener, try to provide a more useful
23074 log message: e.g., "Is Tor already running?"
23075 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
23076 Goldberg can prove things about our handshake protocol more
23078 - MaxConn has been obsolete for a while now. Document the ConnLimit
23079 config option, which is a *minimum* number of file descriptors
23080 that must be available else Tor refuses to start.
23081 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
23082 if you log to syslog and want something other than LOG_DAEMON.
23083 - Make dirservers generate a separate "guard" flag to mean,
23084 "would make a good entry guard". Make clients parse it and vote
23085 on it. Not used by clients yet.
23086 - Implement --with-libevent-dir option to ./configure. Also, improve
23087 search techniques to find libevent, and use those for openssl too.
23088 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
23089 - Only start testing reachability once we've established a
23090 circuit. This will make startup on dirservers less noisy.
23091 - Don't try to upload hidden service descriptors until we have
23092 established a circuit.
23093 - Fix the controller's "attachstream 0" command to treat conn like
23094 it just connected, doing address remapping, handling .exit and
23095 .onion idioms, and so on. Now we're more uniform in making sure
23096 that the controller hears about new and closing connections.
23099 Changes in version 0.1.1.12-alpha - 2006-01-11
23100 o Bugfixes on 0.1.1.x:
23101 - The fix to close duplicate server connections was closing all
23102 Tor client connections if they didn't establish a circuit
23103 quickly enough. Oops.
23104 - Fix minor memory issue (double-free) that happened on exit.
23106 o Bugfixes on 0.1.0.x:
23107 - Tor didn't warn when it failed to open a log file.
23110 Changes in version 0.1.1.11-alpha - 2006-01-10
23111 o Crashes in 0.1.1.x:
23112 - Include all the assert/crash fixes from 0.1.0.16.
23113 - If you start Tor and then quit very quickly, there were some
23114 races that tried to free things that weren't allocated yet.
23115 - Fix a rare memory stomp if you're running hidden services.
23116 - Fix segfault when specifying DirServer in config without nickname.
23117 - Fix a seg fault when you finish connecting to a server but at
23118 that moment you dump his server descriptor.
23119 - Extendcircuit and Attachstream controller commands would
23120 assert/crash if you don't give them enough arguments.
23121 - Fix an assert error when we're out of space in the connection_list
23122 and we try to post a hidden service descriptor (reported by weasel).
23123 - If you specify a relative torrc path and you set RunAsDaemon in
23124 your torrc, then it chdir()'s to the new directory. If you HUP,
23125 it tries to load the new torrc location, fails, and exits.
23126 The fix: no longer allow a relative path to torrc using -f.
23129 - Implement "entry guards": automatically choose a handful of entry
23130 nodes and stick with them for all circuits. Only pick new guards
23131 when the ones you have are unsuitable, and if the old guards
23132 become suitable again, switch back. This will increase security
23133 dramatically against certain end-point attacks. The EntryNodes
23134 config option now provides some hints about which entry guards you
23135 want to use most; and StrictEntryNodes means to only use those.
23136 - New directory logic: download by descriptor digest, not by
23137 fingerprint. Caches try to download all listed digests from
23138 authorities; clients try to download "best" digests from caches.
23139 This avoids partitioning and isolating attacks better.
23140 - Make the "stable" router flag in network-status be the median of
23141 the uptimes of running valid servers, and make clients pay
23142 attention to the network-status flags. Thus the cutoff adapts
23143 to the stability of the network as a whole, making IRC, IM, etc
23144 connections more reliable.
23147 - Tor servers with dynamic IP addresses were needing to wait 18
23148 hours before they could start doing reachability testing using
23149 the new IP address and ports. This is because they were using
23150 the internal descriptor to learn what to test, yet they were only
23151 rebuilding the descriptor once they decided they were reachable.
23152 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
23153 to download certain server descriptors, throw them away, and then
23154 fetch them again after 30 minutes. Now mirrors throw away these
23155 server descriptors so clients can't get them.
23156 - We were leaving duplicate connections to other ORs open for a week,
23157 rather than closing them once we detect a duplicate. This only
23158 really affected authdirservers, but it affected them a lot.
23159 - Spread the authdirservers' reachability testing over the entire
23160 testing interval, so we don't try to do 500 TLS's at once every
23164 - If the network is down, and we try to connect to a conn because
23165 we have a circuit in mind, and we timeout (30 seconds) because the
23166 network never answers, we were expiring the circuit, but we weren't
23167 obsoleting the connection or telling the entry_guards functions.
23168 - Some Tor servers process billions of cells per day. These statistics
23169 need to be uint64_t's.
23170 - Check for integer overflows in more places, when adding elements
23171 to smartlists. This could possibly prevent a buffer overflow
23172 on malicious huge inputs. I don't see any, but I haven't looked
23174 - ReachableAddresses kept growing new "reject *:*" lines on every
23176 - When you "setconf log" via the controller, it should remove all
23177 logs. We were automatically adding back in a "log notice stdout".
23178 - Newly bootstrapped Tor networks couldn't establish hidden service
23179 circuits until they had nodes with high uptime. Be more tolerant.
23180 - We were marking servers down when they could not answer every piece
23181 of the directory request we sent them. This was far too harsh.
23182 - Fix the torify (tsocks) config file to not use Tor for localhost
23184 - Directory authorities now go to the proper authority when asking for
23185 a networkstatus, even when they want a compressed one.
23186 - Fix a harmless bug that was causing Tor servers to log
23187 "Got an end because of misc error, but we're not an AP. Closing."
23188 - Authorities were treating their own descriptor changes as cosmetic,
23189 meaning the descriptor available in the network-status and the
23190 descriptor that clients downloaded were different.
23191 - The OS X installer was adding a symlink for tor_resolve but
23192 the binary was called tor-resolve (reported by Thomas Hardly).
23193 - Workaround a problem with some http proxies where they refuse GET
23194 requests that specify "Content-Length: 0" (reported by Adrian).
23195 - Fix wrong log message when you add a "HiddenServiceNodes" config
23196 line without any HiddenServiceDir line (reported by Chris Thomas).
23199 - Write the TorVersion into the state file so we have a prayer of
23200 keeping forward and backward compatibility.
23201 - Revive the FascistFirewall config option rather than eliminating it:
23202 now it's a synonym for ReachableAddresses *:80,*:443.
23203 - Clients choose directory servers from the network status lists,
23204 not from their internal list of router descriptors. Now they can
23205 go to caches directly rather than needing to go to authorities
23207 - Directory authorities ignore router descriptors that have only
23208 cosmetic differences: do this for 0.1.0.x servers now too.
23209 - Add a new flag to network-status indicating whether the server
23210 can answer v2 directory requests too.
23211 - Authdirs now stop whining so loudly about bad descriptors that
23212 they fetch from other dirservers. So when there's a log complaint,
23213 it's for sure from a freshly uploaded descriptor.
23214 - Reduce memory requirements in our structs by changing the order
23216 - There used to be two ways to specify your listening ports in a
23217 server descriptor: on the "router" line and with a separate "ports"
23218 line. Remove support for the "ports" line.
23219 - New config option "AuthDirRejectUnlisted" for auth dirservers as
23220 a panic button: if we get flooded with unusable servers we can
23221 revert to only listing servers in the approved-routers file.
23222 - Auth dir servers can now mark a fingerprint as "!reject" or
23223 "!invalid" in the approved-routers file (as its nickname), to
23224 refuse descriptors outright or include them but marked as invalid.
23225 - Servers store bandwidth history across restarts/crashes.
23226 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
23227 get a better idea of why their circuits failed. Not used yet.
23228 - Directory mirrors now cache up to 16 unrecognized network-status
23229 docs. Now we can add new authdirservers and they'll be cached too.
23230 - When picking a random directory, prefer non-authorities if any
23232 - New controller option "getinfo desc/all-recent" to fetch the
23233 latest server descriptor for every router that Tor knows about.
23236 Changes in version 0.1.0.16 - 2006-01-02
23237 o Crash bugfixes on 0.1.0.x:
23238 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
23239 corrupting the heap, losing FDs, or crashing when we need to resize
23240 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
23241 - It turns out sparc64 platforms crash on unaligned memory access
23242 too -- so detect and avoid this.
23243 - Handle truncated compressed data correctly (by detecting it and
23245 - Fix possible-but-unlikely free(NULL) in control.c.
23246 - When we were closing connections, there was a rare case that
23247 stomped on memory, triggering seg faults and asserts.
23248 - Avoid potential infinite recursion when building a descriptor. (We
23249 don't know that it ever happened, but better to fix it anyway.)
23250 - We were neglecting to unlink marked circuits from soon-to-close OR
23251 connections, which caused some rare scribbling on freed memory.
23252 - Fix a memory stomping race bug when closing the joining point of two
23253 rendezvous circuits.
23254 - Fix an assert in time parsing found by Steven Murdoch.
23256 o Other bugfixes on 0.1.0.x:
23257 - When we're doing reachability testing, provide more useful log
23258 messages so the operator knows what to expect.
23259 - Do not check whether DirPort is reachable when we are suppressing
23260 advertising it because of hibernation.
23261 - When building with -static or on Solaris, we sometimes needed -ldl.
23262 - When we're deciding whether a stream has enough circuits around
23263 that can handle it, count the freshly dirty ones and not the ones
23264 that are so dirty they won't be able to handle it.
23265 - When we're expiring old circuits, we had a logic error that caused
23266 us to close new rendezvous circuits rather than old ones.
23267 - Give a more helpful log message when you try to change ORPort via
23268 the controller: you should upgrade Tor if you want that to work.
23269 - We were failing to parse Tor versions that start with "Tor ".
23270 - Tolerate faulty streams better: when a stream fails for reason
23271 exitpolicy, stop assuming that the router is lying about his exit
23272 policy. When a stream fails for reason misc, allow it to retry just
23273 as if it was resolvefailed. When a stream has failed three times,
23274 reset its failure count so we can try again and get all three tries.
23277 Changes in version 0.1.1.10-alpha - 2005-12-11
23278 o Correctness bugfixes on 0.1.0.x:
23279 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
23280 corrupting the heap, losing FDs, or crashing when we need to resize
23281 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
23282 - Stop doing the complex voodoo overkill checking for insecure
23283 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
23284 - When we were closing connections, there was a rare case that
23285 stomped on memory, triggering seg faults and asserts.
23286 - We were neglecting to unlink marked circuits from soon-to-close OR
23287 connections, which caused some rare scribbling on freed memory.
23288 - When we're deciding whether a stream has enough circuits around
23289 that can handle it, count the freshly dirty ones and not the ones
23290 that are so dirty they won't be able to handle it.
23291 - Recover better from TCP connections to Tor servers that are
23292 broken but don't tell you (it happens!); and rotate TLS
23293 connections once a week.
23294 - When we're expiring old circuits, we had a logic error that caused
23295 us to close new rendezvous circuits rather than old ones.
23296 - Fix a scary-looking but apparently harmless bug where circuits
23297 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
23298 servers, and never switch to state CIRCUIT_STATE_OPEN.
23299 - When building with -static or on Solaris, we sometimes needed to
23301 - Give a useful message when people run Tor as the wrong user,
23302 rather than telling them to start chowning random directories.
23303 - We were failing to inform the controller about new .onion streams.
23305 o Security bugfixes on 0.1.0.x:
23306 - Refuse server descriptors if the fingerprint line doesn't match
23307 the included identity key. Tor doesn't care, but other apps (and
23308 humans) might actually be trusting the fingerprint line.
23309 - We used to kill the circuit when we receive a relay command we
23310 don't recognize. Now we just drop it.
23311 - Start obeying our firewall options more rigorously:
23312 . If we can't get to a dirserver directly, try going via Tor.
23313 . Don't ever try to connect (as a client) to a place our
23314 firewall options forbid.
23315 . If we specify a proxy and also firewall options, obey the
23316 firewall options even when we're using the proxy: some proxies
23317 can only proxy to certain destinations.
23318 - Fix a bug found by Lasse Overlier: when we were making internal
23319 circuits (intended to be cannibalized later for rendezvous and
23320 introduction circuits), we were picking them so that they had
23321 useful exit nodes. There was no need for this, and it actually
23322 aids some statistical attacks.
23323 - Start treating internal circuits and exit circuits separately.
23324 It's important to keep them separate because internal circuits
23325 have their last hops picked like middle hops, rather than like
23326 exit hops. So exiting on them will break the user's expectations.
23328 o Bugfixes on 0.1.1.x:
23329 - Take out the mis-feature where we tried to detect IP address
23330 flapping for people with DynDNS, and chose not to upload a new
23331 server descriptor sometimes.
23332 - Try to be compatible with OpenSSL 0.9.6 again.
23333 - Log fix: when the controller is logging about .onion addresses,
23334 sometimes it didn't include the ".onion" part of the address.
23335 - Don't try to modify options->DirServers internally -- if the
23336 user didn't specify any, just add the default ones directly to
23337 the trusted dirserver list. This fixes a bug where people running
23338 controllers would use SETCONF on some totally unrelated config
23339 option, and Tor would start yelling at them about changing their
23341 - Let the controller's redirectstream command specify a port, in
23342 case the controller wants to change that too.
23343 - When we requested a pile of server descriptors, we sometimes
23344 accidentally launched a duplicate request for the first one.
23345 - Bugfix for trackhostexits: write down the fingerprint of the
23346 chosen exit, not its nickname, because the chosen exit might not
23348 - When parsing foo.exit, if foo is unknown, and we are leaving
23349 circuits unattached, set the chosen_exit field and leave the
23350 address empty. This matters because controllers got confused
23352 - Directory authorities no longer try to download server
23353 descriptors that they know they will reject.
23355 o Features and updates:
23356 - Replace balanced trees with hash tables: this should make stuff
23357 significantly faster.
23358 - Resume using the AES counter-mode implementation that we ship,
23359 rather than OpenSSL's. Ours is significantly faster.
23360 - Many other CPU and memory improvements.
23361 - Add a new config option FastFirstHopPK (on by default) so clients
23362 do a trivial crypto handshake for their first hop, since TLS has
23363 already taken care of confidentiality and authentication.
23364 - Add a new config option TestSocks so people can see if their
23365 applications are using socks4, socks4a, socks5-with-ip, or
23366 socks5-with-hostname. This way they don't have to keep mucking
23367 with tcpdump and wondering if something got cached somewhere.
23368 - Warn when listening on a public address for socks. I suspect a
23369 lot of people are setting themselves up as open socks proxies,
23370 and they have no idea that jerks on the Internet are using them,
23371 since they simply proxy the traffic into the Tor network.
23372 - Add "private:*" as an alias in configuration for policies. Now
23373 you can simplify your exit policy rather than needing to list
23374 every single internal or nonroutable network space.
23375 - Add a new controller event type that allows controllers to get
23376 all server descriptors that were uploaded to a router in its role
23377 as authoritative dirserver.
23378 - Start shipping socks-extensions.txt, tor-doc-unix.html,
23379 tor-doc-server.html, and stylesheet.css in the tarball.
23380 - Stop shipping tor-doc.html in the tarball.
23383 Changes in version 0.1.1.9-alpha - 2005-11-15
23384 o Usability improvements:
23385 - Start calling it FooListenAddress rather than FooBindAddress,
23386 since few of our users know what it means to bind an address
23388 - Reduce clutter in server logs. We're going to try to make
23389 them actually usable now. New config option ProtocolWarnings that
23390 lets you hear about how _other Tors_ are breaking the protocol. Off
23392 - Divide log messages into logging domains. Once we put some sort
23393 of interface on this, it will let people looking at more verbose
23394 log levels specify the topics they want to hear more about.
23395 - Make directory servers return better http 404 error messages
23396 instead of a generic "Servers unavailable".
23397 - Check for even more Windows version flags when writing the platform
23398 string in server descriptors, and note any we don't recognize.
23399 - Clean up more of the OpenSSL memory when exiting, so we can detect
23400 memory leaks better.
23401 - Make directory authorities be non-versioning, non-naming by
23402 default. Now we can add new directory servers without requiring
23403 their operators to pay close attention.
23404 - When logging via syslog, include the pid whenever we provide
23405 a log entry. Suggested by Todd Fries.
23407 o Performance improvements:
23408 - Directory servers now silently throw away new descriptors that
23409 haven't changed much if the timestamps are similar. We do this to
23410 tolerate older Tor servers that upload a new descriptor every 15
23411 minutes. (It seemed like a good idea at the time.)
23412 - Inline bottleneck smartlist functions; use fast versions by default.
23413 - Add a "Map from digest to void*" abstraction digestmap_t so we
23414 can do less hex encoding/decoding. Use it in router_get_by_digest()
23415 to resolve a performance bottleneck.
23416 - Allow tor_gzip_uncompress to extract as much as possible from
23417 truncated compressed data. Try to extract as many
23418 descriptors as possible from truncated http responses (when
23419 DIR_PURPOSE_FETCH_ROUTERDESC).
23420 - Make circ->onionskin a pointer, not a static array. moria2 was using
23421 125000 circuit_t's after it had been up for a few weeks, which
23422 translates to 20+ megs of wasted space.
23423 - The private half of our EDH handshake keys are now chosen out
23424 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
23426 o Security improvements:
23427 - Start making directory caches retain old routerinfos, so soon
23428 clients can start asking by digest of descriptor rather than by
23429 fingerprint of server.
23430 - Add half our entropy from RAND_poll in OpenSSL. This knows how
23431 to use egd (if present), openbsd weirdness (if present), vms/os2
23432 weirdness (if we ever port there), and more in the future.
23434 o Bugfixes on 0.1.0.x:
23435 - Do round-robin writes of at most 16 kB per write. This might be
23436 more fair on loaded Tor servers, and it might resolve our Windows
23437 crash bug. It might also slow things down.
23438 - Our TLS handshakes were generating a single public/private
23439 keypair for the TLS context, rather than making a new one for
23440 each new connections. Oops. (But we were still rotating them
23441 periodically, so it's not so bad.)
23442 - When we were cannibalizing a circuit with a particular exit
23443 node in mind, we weren't checking to see if that exit node was
23444 already present earlier in the circuit. Oops.
23445 - When a Tor server's IP changes (e.g. from a dyndns address),
23446 upload a new descriptor so clients will learn too.
23447 - Really busy servers were keeping enough circuits open on stable
23448 connections that they were wrapping around the circuit_id
23449 space. (It's only two bytes.) This exposed a bug where we would
23450 feel free to reuse a circuit_id even if it still exists but has
23451 been marked for close. Try to fix this bug. Some bug remains.
23452 - If we would close a stream early (e.g. it asks for a .exit that
23453 we know would refuse it) but the LeaveStreamsUnattached config
23454 option is set by the controller, then don't close it.
23456 o Bugfixes on 0.1.1.8-alpha:
23457 - Fix a big pile of memory leaks, some of them serious.
23458 - Do not try to download a routerdesc if we would immediately reject
23460 - Resume inserting a newline between all router descriptors when
23461 generating (old style) signed directories, since our spec says
23463 - When providing content-type application/octet-stream for
23464 server descriptors using .z, we were leaving out the
23465 content-encoding header. Oops. (Everything tolerated this just
23466 fine, but that doesn't mean we need to be part of the problem.)
23467 - Fix a potential seg fault in getconf and getinfo using version 1
23468 of the controller protocol.
23469 - Avoid crash: do not check whether DirPort is reachable when we
23470 are suppressing it because of hibernation.
23471 - Make --hash-password not crash on exit.
23474 Changes in version 0.1.1.8-alpha - 2005-10-07
23475 o New features (major):
23476 - Clients don't download or use the directory anymore. Now they
23477 download and use network-statuses from the trusted dirservers,
23478 and fetch individual server descriptors as needed from mirrors.
23479 See dir-spec.txt for all the gory details.
23480 - Be more conservative about whether to advertise our DirPort.
23481 The main change is to not advertise if we're running at capacity
23482 and either a) we could hibernate or b) our capacity is low and
23483 we're using a default DirPort.
23484 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
23486 o New features (minor):
23487 - Try to be smart about when to retry network-status and
23488 server-descriptor fetches. Still needs some tuning.
23489 - Stop parsing, storing, or using running-routers output (but
23490 mirrors still cache and serve it).
23491 - Consider a threshold of versioning dirservers (dirservers who have
23492 an opinion about which Tor versions are still recommended) before
23493 deciding whether to warn the user that he's obsolete.
23494 - Dirservers can now reject/invalidate by key and IP, with the
23495 config options "AuthDirInvalid" and "AuthDirReject". This is
23496 useful since currently we automatically list servers as running
23497 and usable even if we know they're jerks.
23498 - Provide dire warnings to any users who set DirServer; move it out
23499 of torrc.sample and into torrc.complete.
23500 - Add MyFamily to torrc.sample in the server section.
23501 - Add nicknames to the DirServer line, so we can refer to them
23502 without requiring all our users to memorize their IP addresses.
23503 - When we get an EOF or a timeout on a directory connection, note
23504 how many bytes of serverdesc we are dropping. This will help
23505 us determine whether it is smart to parse incomplete serverdesc
23507 - Add a new function to "change pseudonyms" -- that is, to stop
23508 using any currently-dirty circuits for new streams, so we don't
23509 link new actions to old actions. Currently it's only called on
23510 HUP (or SIGNAL RELOAD).
23511 - On sighup, if UseHelperNodes changed to 1, use new circuits.
23512 - Start using RAND_bytes rather than RAND_pseudo_bytes from
23513 OpenSSL. Also, reseed our entropy every hour, not just at
23514 startup. And entropy in 512-bit chunks, not 160-bit chunks.
23516 o Fixes on 0.1.1.7-alpha:
23517 - Nobody ever implemented EVENT_ADDRMAP for control protocol
23518 version 0, so don't let version 0 controllers ask for it.
23519 - If you requested something with too many newlines via the
23520 v1 controller protocol, you could crash tor.
23521 - Fix a number of memory leaks, including some pretty serious ones.
23522 - Re-enable DirPort testing again, so Tor servers will be willing
23523 to advertise their DirPort if it's reachable.
23524 - On TLS handshake, only check the other router's nickname against
23525 its expected nickname if is_named is set.
23527 o Fixes forward-ported from 0.1.0.15:
23528 - Don't crash when we don't have any spare file descriptors and we
23529 try to spawn a dns or cpu worker.
23530 - Make the numbers in read-history and write-history into uint64s,
23531 so they don't overflow and publish negatives in the descriptor.
23533 o Fixes on 0.1.0.x:
23534 - For the OS X package's modified privoxy config file, comment
23535 out the "logfile" line so we don't log everything passed
23537 - We were whining about using socks4 or socks5-with-local-lookup
23538 even when it's an IP in the "virtual" range we designed exactly
23540 - We were leaking some memory every time the client changes IPs.
23541 - Never call free() on tor_malloc()d memory. This will help us
23542 use dmalloc to detect memory leaks.
23543 - Check for named servers when looking them up by nickname;
23544 warn when we'recalling a non-named server by its nickname;
23545 don't warn twice about the same name.
23546 - Try to list MyFamily elements by key, not by nickname, and warn
23547 if we've not heard of the server.
23548 - Make windows platform detection (uname equivalent) smarter.
23549 - It turns out sparc64 doesn't like unaligned access either.
23552 Changes in version 0.1.0.15 - 2005-09-23
23553 o Bugfixes on 0.1.0.x:
23554 - Reject ports 465 and 587 (spam targets) in default exit policy.
23555 - Don't crash when we don't have any spare file descriptors and we
23556 try to spawn a dns or cpu worker.
23557 - Get rid of IgnoreVersion undocumented config option, and make us
23558 only warn, never exit, when we're running an obsolete version.
23559 - Don't try to print a null string when your server finds itself to
23560 be unreachable and the Address config option is empty.
23561 - Make the numbers in read-history and write-history into uint64s,
23562 so they don't overflow and publish negatives in the descriptor.
23563 - Fix a minor memory leak in smartlist_string_remove().
23564 - We were only allowing ourselves to upload a server descriptor at
23565 most every 20 minutes, even if it changed earlier than that.
23566 - Clean up log entries that pointed to old URLs.
23569 Changes in version 0.1.1.7-alpha - 2005-09-14
23570 o Fixes on 0.1.1.6-alpha:
23571 - Exit servers were crashing when people asked them to make a
23572 connection to an address not in their exit policy.
23573 - Looking up a non-existent stream for a v1 control connection would
23575 - Fix a seg fault if we ask a dirserver for a descriptor by
23576 fingerprint but he doesn't know about him.
23577 - SETCONF was appending items to linelists, not clearing them.
23578 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
23579 out and refuse the setconf if it would fail.
23580 - Downgrade the dirserver log messages when whining about
23584 - Add Peter Palfrader's check-tor script to tor/contrib/
23585 It lets you easily check whether a given server (referenced by
23586 nickname) is reachable by you.
23587 - Numerous changes to move towards client-side v2 directories. Not
23590 o Fixes on 0.1.0.x:
23591 - If the user gave tor an odd number of command-line arguments,
23592 we were silently ignoring the last one. Now we complain and fail.
23593 [This wins the oldest-bug prize -- this bug has been present since
23594 November 2002, as released in Tor 0.0.0.]
23595 - Do not use unaligned memory access on alpha, mips, or mipsel.
23596 It *works*, but is very slow, so we treat them as if it doesn't.
23597 - Retry directory requests if we fail to get an answer we like
23598 from a given dirserver (we were retrying before, but only if
23599 we fail to connect).
23600 - When writing the RecommendedVersions line, sort them first.
23601 - When the client asked for a rendezvous port that the hidden
23602 service didn't want to provide, we were sending an IP address
23603 back along with the end cell. Fortunately, it was zero. But stop
23605 - Correct "your server is reachable" log entries to indicate that
23606 it was self-testing that told us so.
23609 Changes in version 0.1.1.6-alpha - 2005-09-09
23610 o Fixes on 0.1.1.5-alpha:
23611 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
23612 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
23613 - Fix bug with tor_memmem finding a match at the end of the string.
23614 - Make unit tests run without segfaulting.
23615 - Resolve some solaris x86 compile warnings.
23616 - Handle duplicate lines in approved-routers files without warning.
23617 - Fix bug where as soon as a server refused any requests due to his
23618 exit policy (e.g. when we ask for localhost and he tells us that's
23619 127.0.0.1 and he won't do it), we decided he wasn't obeying his
23620 exit policy using him for any exits.
23621 - Only do openssl hardware accelerator stuff if openssl version is
23624 o New controller features/fixes:
23625 - Add a "RESETCONF" command so you can set config options like
23626 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
23627 a config option in the torrc with no value, then it clears it
23628 entirely (rather than setting it to its default).
23629 - Add a "GETINFO config-file" to tell us where torrc is.
23630 - Avoid sending blank lines when GETINFO replies should be empty.
23631 - Add a QUIT command for the controller (for using it manually).
23632 - Fix a bug in SAVECONF that was adding default dirservers and
23633 other redundant entries to the torrc file.
23635 o Start on the new directory design:
23636 - Generate, publish, cache, serve new network-status format.
23637 - Publish individual descriptors (by fingerprint, by "all", and by
23639 - Publish client and server recommended versions separately.
23640 - Allow tor_gzip_uncompress() to handle multiple concatenated
23641 compressed strings. Serve compressed groups of router
23642 descriptors. The compression logic here could be more
23644 - Distinguish v1 authorities (all currently trusted directories)
23645 from v2 authorities (all trusted directories).
23646 - Change DirServers config line to note which dirs are v1 authorities.
23647 - Add configuration option "V1AuthoritativeDirectory 1" which
23648 moria1, moria2, and tor26 should set.
23649 - Remove option when getting directory cache to see whether they
23650 support running-routers; they all do now. Replace it with one
23651 to see whether caches support v2 stuff.
23654 - Dirservers now do their own external reachability testing of each
23655 Tor server, and only list them as running if they've been found to
23656 be reachable. We also send back warnings to the server's logs if
23657 it uploads a descriptor that we already believe is unreachable.
23658 - Implement exit enclaves: if we know an IP address for the
23659 destination, and there's a running Tor server at that address
23660 which allows exit to the destination, then extend the circuit to
23661 that exit first. This provides end-to-end encryption and end-to-end
23662 authentication. Also, if the user wants a .exit address or enclave,
23663 use 4 hops rather than 3, and cannibalize a general circ for it
23665 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
23666 controller. Also, rotate dns and cpu workers if the controller
23667 changes options that will affect them; and initialize the dns
23668 worker cache tree whether or not we start out as a server.
23669 - Only upload a new server descriptor when options change, 18
23670 hours have passed, uptime is reset, or bandwidth changes a lot.
23671 - Check [X-]Forwarded-For headers in HTTP requests when generating
23672 log messages. This lets people run dirservers (and caches) behind
23673 Apache but still know which IP addresses are causing warnings.
23675 o Config option changes:
23676 - Replace (Fascist)Firewall* config options with a new
23677 ReachableAddresses option that understands address policies.
23678 For example, "ReachableAddresses *:80,*:443"
23679 - Get rid of IgnoreVersion undocumented config option, and make us
23680 only warn, never exit, when we're running an obsolete version.
23681 - Make MonthlyAccountingStart config option truly obsolete now.
23683 o Fixes on 0.1.0.x:
23684 - Reject ports 465 and 587 in the default exit policy, since
23685 people have started using them for spam too.
23686 - It turns out we couldn't bootstrap a network since we added
23687 reachability detection in 0.1.0.1-rc. Good thing the Tor network
23688 has never gone down. Add an AssumeReachable config option to let
23689 servers and dirservers bootstrap. When we're trying to build a
23690 high-uptime or high-bandwidth circuit but there aren't enough
23691 suitable servers, try being less picky rather than simply failing.
23692 - Our logic to decide if the OR we connected to was the right guy
23693 was brittle and maybe open to a mitm for unverified routers.
23694 - We weren't cannibalizing circuits correctly for
23695 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
23696 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
23697 build those from scratch. This should make hidden services faster.
23698 - Predict required circuits better, with an eye toward making hidden
23699 services faster on the service end.
23700 - Retry streams if the exit node sends back a 'misc' failure. This
23701 should result in fewer random failures. Also, after failing
23702 from resolve failed or misc, reset the num failures, so we give
23703 it a fair shake next time we try.
23704 - Clean up the rendezvous warn log msgs, and downgrade some to info.
23705 - Reduce severity on logs about dns worker spawning and culling.
23706 - When we're shutting down and we do something like try to post a
23707 server descriptor or rendezvous descriptor, don't complain that
23708 we seem to be unreachable. Of course we are, we're shutting down.
23709 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
23710 We don't use them yet, but maybe one day our DNS resolver will be
23711 able to discover them.
23712 - Make ContactInfo mandatory for authoritative directory servers.
23713 - Require server descriptors to list IPv4 addresses -- hostnames
23714 are no longer allowed. This also fixes some potential security
23715 problems with people providing hostnames as their address and then
23716 preferentially resolving them to partition users.
23717 - Change log line for unreachability to explicitly suggest /etc/hosts
23718 as the culprit. Also make it clearer what IP address and ports we're
23719 testing for reachability.
23720 - Put quotes around user-supplied strings when logging so users are
23721 more likely to realize if they add bad characters (like quotes)
23723 - Let auth dir servers start without specifying an Address config
23725 - Make unit tests (and other invocations that aren't the real Tor)
23726 run without launching listeners, creating subdirectories, and so on.
23729 Changes in version 0.1.1.5-alpha - 2005-08-08
23730 o Bugfixes included in 0.1.0.14.
23732 o Bugfixes on 0.1.0.x:
23733 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
23734 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
23735 it would silently using ignore the 6668.
23738 Changes in version 0.1.0.14 - 2005-08-08
23739 o Bugfixes on 0.1.0.x:
23740 - Fix the other half of the bug with crypto handshakes
23742 - Fix an assert trigger if you send a 'signal term' via the
23743 controller when it's listening for 'event info' messages.
23746 Changes in version 0.1.1.4-alpha - 2005-08-04
23747 o Bugfixes included in 0.1.0.13.
23750 - Improve tor_gettimeofday() granularity on windows.
23751 - Make clients regenerate their keys when their IP address changes.
23752 - Implement some more GETINFO goodness: expose helper nodes, config
23753 options, getinfo keys.
23756 Changes in version 0.1.0.13 - 2005-08-04
23757 o Bugfixes on 0.1.0.x:
23758 - Fix a critical bug in the security of our crypto handshakes.
23759 - Fix a size_t underflow in smartlist_join_strings2() that made
23760 it do bad things when you hand it an empty smartlist.
23761 - Fix Windows installer to ship Tor license (thanks to Aphex for
23762 pointing out this oversight) and put a link to the doc directory
23764 - Explicitly set no-unaligned-access for sparc: it turns out the
23765 new gcc's let you compile broken code, but that doesn't make it
23769 Changes in version 0.1.1.3-alpha - 2005-07-23
23770 o Bugfixes on 0.1.1.2-alpha:
23771 - Fix a bug in handling the controller's "post descriptor"
23773 - Fix several bugs in handling the controller's "extend circuit"
23775 - Fix a bug in handling the controller's "stream status" event.
23776 - Fix an assert failure if we have a controller listening for
23777 circuit events and we go offline.
23778 - Re-allow hidden service descriptors to publish 0 intro points.
23779 - Fix a crash when generating your hidden service descriptor if
23780 you don't have enough intro points already.
23782 o New features on 0.1.1.2-alpha:
23783 - New controller function "getinfo accounting", to ask how
23784 many bytes we've used in this time period.
23785 - Experimental support for helper nodes: a lot of the risk from
23786 a small static adversary comes because users pick new random
23787 nodes every time they rebuild a circuit. Now users will try to
23788 stick to the same small set of entry nodes if they can. Not
23789 enabled by default yet.
23791 o Bugfixes on 0.1.0.12:
23792 - If you're an auth dir server, always publish your dirport,
23793 even if you haven't yet found yourself to be reachable.
23794 - Fix a size_t underflow in smartlist_join_strings2() that made
23795 it do bad things when you hand it an empty smartlist.
23798 Changes in version 0.1.0.12 - 2005-07-18
23799 o New directory servers:
23800 - tor26 has changed IP address.
23802 o Bugfixes on 0.1.0.x:
23803 - Fix a possible double-free in tor_gzip_uncompress().
23804 - When --disable-threads is set, do not search for or link against
23805 pthreads libraries.
23806 - Don't trigger an assert if an authoritative directory server
23807 claims its dirport is 0.
23808 - Fix bug with removing Tor as an NT service: some people were
23809 getting "The service did not return an error." Thanks to Matt
23813 Changes in version 0.1.1.2-alpha - 2005-07-15
23814 o New directory servers:
23815 - tor26 has changed IP address.
23817 o Bugfixes on 0.1.0.x, crashes/leaks:
23818 - Port the servers-not-obeying-their-exit-policies fix from
23820 - Fix an fd leak in start_daemon().
23821 - On Windows, you can't always reopen a port right after you've
23822 closed it. So change retry_listeners() to only close and re-open
23823 ports that have changed.
23824 - Fix a possible double-free in tor_gzip_uncompress().
23826 o Bugfixes on 0.1.0.x, usability:
23827 - When tor_socketpair() fails in Windows, give a reasonable
23828 Windows-style errno back.
23829 - Let people type "tor --install" as well as "tor -install" when
23831 want to make it an NT service.
23832 - NT service patch from Matt Edman to improve error messages.
23833 - When the controller asks for a config option with an abbreviated
23834 name, give the full name in our response.
23835 - Correct the man page entry on TrackHostExitsExpire.
23836 - Looks like we were never delivering deflated (i.e. compressed)
23837 running-routers lists, even when asked. Oops.
23838 - When --disable-threads is set, do not search for or link against
23839 pthreads libraries.
23841 o Bugfixes on 0.1.1.x:
23842 - Fix a seg fault with autodetecting which controller version is
23846 - New hidden service descriptor format: put a version in it, and
23847 let people specify introduction/rendezvous points that aren't
23848 in "the directory" (which is subjective anyway).
23849 - Allow the DEBUG controller event to work again. Mark certain log
23850 entries as "don't tell this to controllers", so we avoid cycles.
23853 Changes in version 0.1.0.11 - 2005-06-30
23854 o Bugfixes on 0.1.0.x:
23855 - Fix major security bug: servers were disregarding their
23856 exit policies if clients behaved unexpectedly.
23857 - Make OS X init script check for missing argument, so we don't
23858 confuse users who invoke it incorrectly.
23859 - Fix a seg fault in "tor --hash-password foo".
23860 - The MAPADDRESS control command was broken.
23863 Changes in version 0.1.1.1-alpha - 2005-06-29
23865 - Make OS X init script check for missing argument, so we don't
23866 confuse users who invoke it incorrectly.
23867 - Fix a seg fault in "tor --hash-password foo".
23868 - Fix a possible way to DoS dirservers.
23869 - When we complain that your exit policy implicitly allows local or
23870 private address spaces, name them explicitly so operators can
23872 - Make the log message less scary when all the dirservers are
23873 temporarily unreachable.
23874 - We were printing the number of idle dns workers incorrectly when
23878 - Revised controller protocol (version 1) that uses ascii rather
23879 than binary. Add supporting libraries in python and java so you
23880 can use the controller from your applications without caring how
23881 our protocol works.
23882 - Spiffy new support for crypto hardware accelerators. Can somebody
23886 Changes in version 0.0.9.10 - 2005-06-16
23887 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
23888 - Refuse relay cells that claim to have a length larger than the
23889 maximum allowed. This prevents a potential attack that could read
23890 arbitrary memory (e.g. keys) from an exit server's process
23894 Changes in version 0.1.0.10 - 2005-06-14
23895 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
23896 libevent before 1.1a.
23899 Changes in version 0.1.0.9-rc - 2005-06-09
23901 - Reset buf->highwater every time buf_shrink() is called, not just on
23902 a successful shrink. This was causing significant memory bloat.
23903 - Fix buffer overflow when checking hashed passwords.
23904 - Security fix: if seeding the RNG on Win32 fails, quit.
23905 - Allow seeding the RNG on Win32 even when you're not running as
23907 - Disable threading on Solaris too. Something is wonky with it,
23908 cpuworkers, and reentrant libs.
23909 - Reenable the part of the code that tries to flush as soon as an
23910 OR outbuf has a full TLS record available. Perhaps this will make
23911 OR outbufs not grow as huge except in rare cases, thus saving lots
23912 of CPU time plus memory.
23913 - Reject malformed .onion addresses rather then passing them on as
23914 normal web requests.
23915 - Adapt patch from Adam Langley: fix possible memory leak in
23916 tor_lookup_hostname().
23917 - Initialize libevent later in the startup process, so the logs are
23918 already established by the time we start logging libevent warns.
23919 - Use correct errno on win32 if libevent fails.
23920 - Check and warn about known-bad/slow libevent versions.
23921 - Pay more attention to the ClientOnly config option.
23922 - Have torctl.in/tor.sh.in check for location of su binary (needed
23924 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
23925 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
23926 HttpProxyAuthenticator
23927 - Stop warning about sigpipes in the logs. We're going to
23928 pretend that getting these occassionally is normal and fine.
23929 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
23931 installer screens; and don't put stuff into StartupItems unless
23932 the user asks you to.
23933 - Require servers that use the default dirservers to have public IP
23934 addresses. We have too many servers that are configured with private
23935 IPs and their admins never notice the log entries complaining that
23936 their descriptors are being rejected.
23937 - Add OSX uninstall instructions. An actual uninstall script will
23941 Changes in version 0.1.0.8-rc - 2005-05-23
23943 - It turns out that kqueue on OS X 10.3.9 was causing kernel
23944 panics. Disable kqueue on all OS X Tors.
23945 - Fix RPM: remove duplicate line accidentally added to the rpm
23947 - Disable threads on openbsd too, since its gethostaddr is not
23949 - Tolerate libevent 0.8 since it still works, even though it's
23951 - Enable building on Red Hat 9.0 again.
23952 - Allow the middle hop of the testing circuit to be running any
23953 version, now that most of them have the bugfix to let them connect
23954 to unknown servers. This will allow reachability testing to work
23955 even when 0.0.9.7-0.0.9.9 become obsolete.
23956 - Handle relay cells with rh.length too large. This prevents
23957 a potential attack that could read arbitrary memory (maybe even
23958 keys) from the exit server's process.
23959 - We screwed up the dirport reachability testing when we don't yet
23960 have a cached version of the directory. Hopefully now fixed.
23961 - Clean up router_load_single_router() (used by the controller),
23962 so it doesn't seg fault on error.
23963 - Fix a minor memory leak when somebody establishes an introduction
23964 point at your Tor server.
23965 - If a socks connection ends because read fails, don't warn that
23966 you're not sending a socks reply back.
23969 - Add HttpProxyAuthenticator config option too, that works like
23970 the HttpsProxyAuthenticator config option.
23971 - Encode hashed controller passwords in hex instead of base64,
23972 to make it easier to write controllers.
23975 Changes in version 0.1.0.7-rc - 2005-05-17
23977 - Fix a bug in the OS X package installer that prevented it from
23978 installing on Tiger.
23979 - Fix a script bug in the OS X package installer that made it
23980 complain during installation.
23981 - Find libevent even if it's hiding in /usr/local/ and your
23982 CFLAGS and LDFLAGS don't tell you to look there.
23983 - Be able to link with libevent as a shared library (the default
23984 after 1.0d), even if it's hiding in /usr/local/lib and even
23985 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
23986 assuming you're running gcc. Otherwise fail and give a useful
23988 - Fix a bug in the RPM packager: set home directory for _tor to
23989 something more reasonable when first installing.
23990 - Free a minor amount of memory that is still reachable on exit.
23993 Changes in version 0.1.0.6-rc - 2005-05-14
23995 - Implement --disable-threads configure option. Disable threads on
23996 netbsd by default, because it appears to have no reentrant resolver
23998 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
23999 release (1.1) detects and disables kqueue if it's broken.
24000 - Append default exit policy before checking for implicit internal
24001 addresses. Now we don't log a bunch of complaints on startup
24002 when using the default exit policy.
24003 - Some people were putting "Address " in their torrc, and they had
24004 a buggy resolver that resolved " " to 0.0.0.0. Oops.
24005 - If DataDir is ~/.tor, and that expands to /.tor, then default to
24006 LOCALSTATEDIR/tor instead.
24007 - Fix fragmented-message bug in TorControl.py.
24008 - Resolve a minor bug which would prevent unreachable dirports
24009 from getting suppressed in the published descriptor.
24010 - When the controller gave us a new descriptor, we weren't resolving
24011 it immediately, so Tor would think its address was 0.0.0.0 until
24012 we fetched a new directory.
24013 - Fix an uppercase/lowercase case error in suppressing a bogus
24014 libevent warning on some Linuxes.
24017 - Begin scrubbing sensitive strings from logs by default. Turn off
24018 the config option SafeLogging if you need to do debugging.
24019 - Switch to a new buffer management algorithm, which tries to avoid
24020 reallocing and copying quite as much. In first tests it looks like
24021 it uses *more* memory on average, but less cpu.
24022 - First cut at support for "create-fast" cells. Clients can use
24023 these when extending to their first hop, since the TLS already
24024 provides forward secrecy and authentication. Not enabled on
24026 - When dirservers refuse a router descriptor, we now log its
24027 contactinfo, platform, and the poster's IP address.
24028 - Call tor_free_all instead of connections_free_all after forking, to
24029 save memory on systems that need to fork.
24030 - Whine at you if you're a server and you don't set your contactinfo.
24031 - Implement --verify-config command-line option to check if your torrc
24032 is valid without actually launching Tor.
24033 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
24034 rather than just rejecting it.
24037 Changes in version 0.1.0.5-rc - 2005-04-27
24039 - Stop trying to print a null pointer if an OR conn fails because
24040 we didn't like its cert.
24042 - Switch our internal buffers implementation to use a ring buffer,
24043 to hopefully improve performance for fast servers a lot.
24044 - Add HttpsProxyAuthenticator support (basic auth only), based
24045 on patch from Adam Langley.
24046 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
24047 the fast servers that have been joining lately.
24048 - Give hidden service accesses extra time on the first attempt,
24049 since 60 seconds is often only barely enough. This might improve
24051 - Improve performance for dirservers: stop re-parsing the whole
24052 directory every time you regenerate it.
24053 - Add more debugging info to help us find the weird dns freebsd
24054 pthreads bug; cleaner debug messages to help track future issues.
24057 Changes in version 0.0.9.9 - 2005-04-23
24058 o Bugfixes on 0.0.9.x:
24059 - If unofficial Tor clients connect and send weird TLS certs, our
24060 Tor server triggers an assert. This release contains a minimal
24061 backport from the broader fix that we put into 0.1.0.4-rc.
24064 Changes in version 0.1.0.4-rc - 2005-04-23
24066 - If unofficial Tor clients connect and send weird TLS certs, our
24067 Tor server triggers an assert. Stop asserting, and start handling
24068 TLS errors better in other situations too.
24069 - When the controller asks us to tell it about all the debug-level
24070 logs, it turns out we were generating debug-level logs while
24071 telling it about them, which turns into a bad loop. Now keep
24072 track of whether you're sending a debug log to the controller,
24073 and don't log when you are.
24074 - Fix the "postdescriptor" feature of the controller interface: on
24075 non-complete success, only say "done" once.
24077 - Clients are now willing to load balance over up to 2mB, not 1mB,
24078 of advertised bandwidth capacity.
24079 - Add a NoPublish config option, so you can be a server (e.g. for
24080 testing running Tor servers in other Tor networks) without
24081 publishing your descriptor to the primary dirservers.
24084 Changes in version 0.1.0.3-rc - 2005-04-08
24085 o Improvements on 0.1.0.2-rc:
24086 - Client now retries when streams end early for 'hibernating' or
24087 'resource limit' reasons, rather than failing them.
24088 - More automated handling for dirserver operators:
24089 - Automatically approve nodes running 0.1.0.2-rc or later,
24090 now that the the reachability detection stuff is working.
24091 - Now we allow two unverified servers with the same nickname
24092 but different keys. But if a nickname is verified, only that
24093 nickname+key are allowed.
24094 - If you're an authdirserver connecting to an address:port,
24095 and it's not the OR you were expecting, forget about that
24096 descriptor. If he *was* the one you were expecting, then forget
24097 about all other descriptors for that address:port.
24098 - Allow servers to publish descriptors from 12 hours in the future.
24099 Corollary: only whine about clock skew from the dirserver if
24100 he's a trusted dirserver (since now even verified servers could
24101 have quite wrong clocks).
24102 - Adjust maximum skew and age for rendezvous descriptors: let skew
24103 be 48 hours rather than 90 minutes.
24104 - Efficiency improvements:
24105 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
24106 it much faster to look up a circuit for each relay cell.
24107 - Remove most calls to assert_all_pending_dns_resolves_ok(),
24108 since they're eating our cpu on exit nodes.
24109 - Stop wasting time doing a case insensitive comparison for every
24110 dns name every time we do any lookup. Canonicalize the names to
24111 lowercase and be done with it.
24112 - Start sending 'truncated' cells back rather than destroy cells,
24113 if the circuit closes in front of you. This means we won't have
24114 to abandon partially built circuits.
24115 - Only warn once per nickname from add_nickname_list_to_smartlist
24116 per failure, so an entrynode or exitnode choice that's down won't
24118 - Put a note in the torrc about abuse potential with the default
24120 - Revise control spec and implementation to allow all log messages to
24121 be sent to controller with their severities intact (suggested by
24122 Matt Edman). Update TorControl to handle new log event types.
24123 - Provide better explanation messages when controller's POSTDESCRIPTOR
24125 - Stop putting nodename in the Platform string in server descriptors.
24126 It doesn't actually help, and it is confusing/upsetting some people.
24128 o Bugfixes on 0.1.0.2-rc:
24129 - We were printing the host mask wrong in exit policies in server
24130 descriptors. This isn't a critical bug though, since we were still
24131 obeying the exit policy internally.
24132 - Fix Tor when compiled with libevent but without pthreads: move
24133 connection_unregister() from _connection_free() to
24135 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
24136 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
24137 when we look through the connection array, we'll find any of the
24138 cpu/dnsworkers. This is no good.
24140 o Bugfixes on 0.0.9.8:
24141 - Fix possible bug on threading platforms (e.g. win32) which was
24142 leaking a file descriptor whenever a cpuworker or dnsworker died.
24143 - When using preferred entry or exit nodes, ignore whether the
24144 circuit wants uptime or capacity. They asked for the nodes, they
24146 - chdir() to your datadirectory at the *end* of the daemonize process,
24147 not the beginning. This was a problem because the first time you
24148 run tor, if your datadir isn't there, and you have runasdaemon set
24149 to 1, it will try to chdir to it before it tries to create it. Oops.
24150 - Handle changed router status correctly when dirserver reloads
24151 fingerprint file. We used to be dropping all unverified descriptors
24152 right then. The bug was hidden because we would immediately
24153 fetch a directory from another dirserver, which would include the
24154 descriptors we just dropped.
24155 - When we're connecting to an OR and he's got a different nickname/key
24156 than we were expecting, only complain loudly if we're an OP or a
24157 dirserver. Complaining loudly to the OR admins just confuses them.
24158 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
24159 artificially capped at 500kB.
24162 Changes in version 0.0.9.8 - 2005-04-07
24163 o Bugfixes on 0.0.9.x:
24164 - We have a bug that I haven't found yet. Sometimes, very rarely,
24165 cpuworkers get stuck in the 'busy' state, even though the cpuworker
24166 thinks of itself as idle. This meant that no new circuits ever got
24167 established. Here's a workaround to kill any cpuworker that's been
24168 busy for more than 100 seconds.
24171 Changes in version 0.1.0.2-rc - 2005-04-01
24172 o Bugfixes on 0.1.0.1-rc:
24173 - Fixes on reachability detection:
24174 - Don't check for reachability while hibernating.
24175 - If ORPort is reachable but DirPort isn't, still publish the
24176 descriptor, but zero out DirPort until it's found reachable.
24177 - When building testing circs for ORPort testing, use only
24178 high-bandwidth nodes, so fewer circuits fail.
24179 - Complain about unreachable ORPort separately from unreachable
24180 DirPort, so the user knows what's going on.
24181 - Make sure we only conclude ORPort reachability if we didn't
24182 initiate the conn. Otherwise we could falsely conclude that
24183 we're reachable just because we connected to the guy earlier
24184 and he used that same pipe to extend to us.
24185 - Authdirservers shouldn't do ORPort reachability detection,
24186 since they're in clique mode, so it will be rare to find a
24187 server not already connected to them.
24188 - When building testing circuits, always pick middle hops running
24189 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
24190 bug. (This is a kludge; it will go away when 0.0.9.x becomes
24192 - When we decide we're reachable, actually publish our descriptor
24194 - Fix bug in redirectstream in the controller.
24195 - Fix the state descriptor strings so logs don't claim edge streams
24196 are in a different state than they actually are.
24197 - Use recent libevent features when possible (this only really affects
24198 win32 and osx right now, because the new libevent with these
24199 features hasn't been released yet). Add code to suppress spurious
24201 - Prevent possible segfault in connection_close_unattached_ap().
24202 - Fix newlines on torrc in win32.
24203 - Improve error msgs when tor-resolve fails.
24205 o Improvements on 0.0.9.x:
24206 - New experimental script tor/contrib/ExerciseServer.py (needs more
24207 work) that uses the controller interface to build circuits and
24208 fetch pages over them. This will help us bootstrap servers that
24209 have lots of capacity but haven't noticed it yet.
24210 - New experimental script tor/contrib/PathDemo.py (needs more work)
24211 that uses the controller interface to let you choose whole paths
24213 "<hostname>.<path,separated by dots>.<length of path>.path"
24214 - When we've connected to an OR and handshaked but didn't like
24215 the result, we were closing the conn without sending destroy
24216 cells back for pending circuits. Now send those destroys.
24219 Changes in version 0.0.9.7 - 2005-04-01
24220 o Bugfixes on 0.0.9.x:
24221 - Fix another race crash bug (thanks to Glenn Fink for reporting).
24222 - Compare identity to identity, not to nickname, when extending to
24223 a router not already in the directory. This was preventing us from
24224 extending to unknown routers. Oops.
24225 - Make sure to create OS X Tor user in <500 range, so we aren't
24226 creating actual system users.
24227 - Note where connection-that-hasn't-sent-end was marked, and fix
24228 a few really loud instances of this harmless bug (it's fixed more
24232 Changes in version 0.1.0.1-rc - 2005-03-28
24234 - Add reachability testing. Your Tor server will automatically try
24235 to see if its ORPort and DirPort are reachable from the outside,
24236 and it won't upload its descriptor until it decides they are.
24237 - Handle unavailable hidden services better. Handle slow or busy
24238 hidden services better.
24239 - Add support for CONNECTing through https proxies, with "HttpsProxy"
24241 - New exit policy: accept most low-numbered ports, rather than
24242 rejecting most low-numbered ports.
24243 - More Tor controller support (still experimental). See
24244 http://tor.eff.org/doc/control-spec.txt for all the new features,
24245 including signals to emulate unix signals from any platform;
24246 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
24247 closestream; closecircuit; etc.
24248 - Make nt services work and start on startup on win32 (based on
24249 patch by Matt Edman).
24250 - Add a new AddressMap config directive to rewrite incoming socks
24251 addresses. This lets you, for example, declare an implicit
24252 required exit node for certain sites.
24253 - Add a new TrackHostExits config directive to trigger addressmaps
24254 for certain incoming socks addresses -- for sites that break when
24255 your exit keeps changing (based on patch by Mike Perry).
24256 - Redo the client-side dns cache so it's just an addressmap too.
24257 - Notice when our IP changes, and reset stats/uptime/reachability.
24258 - When an application is using socks5, give him the whole variety of
24259 potential socks5 responses (connect refused, host unreachable, etc),
24260 rather than just "success" or "failure".
24261 - A more sane version numbering system. See
24262 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
24263 - New contributed script "exitlist": a simple python script to
24264 parse directories and find Tor nodes that exit to listed
24266 - New contributed script "privoxy-tor-toggle" to toggle whether
24267 Privoxy uses Tor. Seems to be configured for Debian by default.
24268 - Report HTTP reasons to client when getting a response from directory
24269 servers -- so you can actually know what went wrong.
24270 - New config option MaxAdvertisedBandwidth which lets you advertise
24271 a low bandwidthrate (to not attract as many circuits) while still
24272 allowing a higher bandwidthrate in reality.
24274 o Robustness/stability fixes:
24275 - Make Tor use Niels Provos's libevent instead of its current
24276 poll-but-sometimes-select mess. This will let us use faster async
24277 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
24279 - pthread support now too. This was forced because when we forked,
24280 we ended up wasting a lot of duplicate ram over time. Also switch
24281 to foo_r versions of some library calls to allow reentry and
24283 - Better handling for heterogeneous / unreliable nodes:
24284 - Annotate circuits w/ whether they aim to contain high uptime nodes
24285 and/or high capacity nodes. When building circuits, choose
24287 - This means that every single node in an intro rend circuit,
24288 not just the last one, will have a minimum uptime.
24289 - New config option LongLivedPorts to indicate application streams
24290 that will want high uptime circuits.
24291 - Servers reset uptime when a dir fetch entirely fails. This
24292 hopefully reflects stability of the server's network connectivity.
24293 - If somebody starts his tor server in Jan 2004 and then fixes his
24294 clock, don't make his published uptime be a year.
24295 - Reset published uptime when you wake up from hibernation.
24296 - Introduce a notion of 'internal' circs, which are chosen without
24297 regard to the exit policy of the last hop. Intro and rendezvous
24298 circs must be internal circs, to avoid leaking information. Resolve
24299 and connect streams can use internal circs if they want.
24300 - New circuit pooling algorithm: make sure to have enough circs around
24301 to satisfy any predicted ports, and also make sure to have 2 internal
24302 circs around if we've required internal circs lately (and with high
24303 uptime if we've seen that lately too).
24304 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
24305 which describes how often we retry making new circuits if current
24306 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
24307 how long we're willing to make use of an already-dirty circuit.
24308 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
24309 circ as necessary, if there are any completed ones lying around
24310 when we try to launch one.
24311 - Make hidden services try to establish a rendezvous for 30 seconds,
24312 rather than for n (where n=3) attempts to build a circuit.
24313 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
24314 "ShutdownWaitLength".
24315 - Try to be more zealous about calling connection_edge_end when
24316 things go bad with edge conns in connection.c.
24317 - Revise tor-spec to add more/better stream end reasons.
24318 - Revise all calls to connection_edge_end to avoid sending "misc",
24319 and to take errno into account where possible.
24322 - Fix a race condition that can trigger an assert, when we have a
24323 pending create cell and an OR connection fails right then.
24324 - Fix several double-mark-for-close bugs, e.g. where we were finding
24325 a conn for a cell even if that conn is already marked for close.
24326 - Make sequence of log messages when starting on win32 with no config
24327 file more reasonable.
24328 - When choosing an exit node for a new non-internal circ, don't take
24329 into account whether it'll be useful for any pending x.onion
24330 addresses -- it won't.
24331 - Turn addr_policy_compare from a tristate to a quadstate; this should
24332 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
24333 for google.com" problem.
24334 - Make "platform" string in descriptor more accurate for Win32 servers,
24335 so it's not just "unknown platform".
24336 - Fix an edge case in parsing config options (thanks weasel).
24337 If they say "--" on the commandline, it's not an option.
24338 - Reject odd-looking addresses at the client (e.g. addresses that
24339 contain a colon), rather than having the server drop them because
24341 - tor-resolve requests were ignoring .exit if there was a working circuit
24342 they could use instead.
24343 - REUSEADDR on normal platforms means you can rebind to the port
24344 right after somebody else has let it go. But REUSEADDR on win32
24345 means to let you bind to the port _even when somebody else
24346 already has it bound_! So, don't do that on Win32.
24347 - Change version parsing logic: a version is "obsolete" if it is not
24348 recommended and (1) there is a newer recommended version in the
24349 same series, or (2) there are no recommended versions in the same
24350 series, but there are some recommended versions in a newer series.
24351 A version is "new" if it is newer than any recommended version in
24353 - Stop most cases of hanging up on a socks connection without sending
24357 - Require BandwidthRate to be at least 20kB/s for servers.
24358 - When a dirserver causes you to give a warn, mention which dirserver
24360 - New config option DirAllowPrivateAddresses for authdirservers.
24361 Now by default they refuse router descriptors that have non-IP or
24362 private-IP addresses.
24363 - Stop publishing socksport in the directory, since it's not
24364 actually meant to be public. For compatibility, publish a 0 there
24366 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
24367 smart" value, that is low for servers and high for clients.
24368 - If our clock jumps forward by 100 seconds or more, assume something
24369 has gone wrong with our network and abandon all not-yet-used circs.
24370 - Warn when exit policy implicitly allows local addresses.
24371 - If we get an incredibly skewed timestamp from a dirserver mirror
24372 that isn't a verified OR, don't warn -- it's probably him that's
24374 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
24375 cookies to disk and doesn't log each web request to disk. (Thanks
24376 to Brett Carrington for pointing this out.)
24377 - When a client asks us for a dir mirror and we don't have one,
24378 launch an attempt to get a fresh one.
24379 - If we're hibernating and we get a SIGINT, exit immediately.
24380 - Add --with-dmalloc ./configure option, to track memory leaks.
24381 - And try to free all memory on closing, so we can detect what
24383 - Cache local dns resolves correctly even when they're .exit
24385 - Give a better warning when some other server advertises an
24386 ORPort that is actually an apache running ssl.
24387 - Add "opt hibernating 1" to server descriptor to make it clearer
24388 whether the server is hibernating.
24391 Changes in version 0.0.9.6 - 2005-03-24
24392 o Bugfixes on 0.0.9.x (crashes and asserts):
24393 - Add new end stream reasons to maintainance branch. Fix bug where
24394 reason (8) could trigger an assert. Prevent bug from recurring.
24395 - Apparently win32 stat wants paths to not end with a slash.
24396 - Fix assert triggers in assert_cpath_layer_ok(), where we were
24397 blowing away the circuit that conn->cpath_layer points to, then
24398 checking to see if the circ is well-formed. Backport check to make
24399 sure we dont use the cpath on a closed connection.
24400 - Prevent circuit_resume_edge_reading_helper() from trying to package
24401 inbufs for marked-for-close streams.
24402 - Don't crash on hup if your options->address has become unresolvable.
24403 - Some systems (like OS X) sometimes accept() a connection and tell
24404 you the remote host is 0.0.0.0:0. If this happens, due to some
24405 other mis-features, we get confused; so refuse the conn for now.
24407 o Bugfixes on 0.0.9.x (other):
24408 - Fix harmless but scary "Unrecognized content encoding" warn message.
24409 - Add new stream error reason: TORPROTOCOL reason means "you are not
24410 speaking a version of Tor I understand; say bye-bye to your stream."
24411 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
24412 into the future, now that we are more tolerant of skew. This
24413 resolves a bug where a Tor server would refuse to cache a directory
24414 because all the directories it gets are too far in the future;
24415 yet the Tor server never logs any complaints about clock skew.
24416 - Mac packaging magic: make man pages useable, and do not overwrite
24417 existing torrc files.
24418 - Make OS X log happily to /var/log/tor/tor.log
24421 Changes in version 0.0.9.5 - 2005-02-22
24422 o Bugfixes on 0.0.9.x:
24423 - Fix an assert race at exit nodes when resolve requests fail.
24424 - Stop picking unverified dir mirrors--it only leads to misery.
24425 - Patch from Matt Edman to make NT services work better. Service
24426 support is still not compiled into the executable by default.
24427 - Patch from Dmitri Bely so the Tor service runs better under
24428 the win32 SYSTEM account.
24429 - Make tor-resolve actually work (?) on Win32.
24430 - Fix a sign bug when getrlimit claims to have 4+ billion
24431 file descriptors available.
24432 - Stop refusing to start when bandwidthburst == bandwidthrate.
24433 - When create cells have been on the onion queue more than five
24434 seconds, just send back a destroy and take them off the list.
24437 Changes in version 0.0.9.4 - 2005-02-03
24438 o Bugfixes on 0.0.9:
24439 - Fix an assert bug that took down most of our servers: when
24440 a server claims to have 1 GB of bandwidthburst, don't
24442 - Don't crash as badly if we have spawned the max allowed number
24443 of dnsworkers, or we're out of file descriptors.
24444 - Block more file-sharing ports in the default exit policy.
24445 - MaxConn is now automatically set to the hard limit of max
24446 file descriptors we're allowed (ulimit -n), minus a few for
24448 - Give a clearer message when servers need to raise their
24449 ulimit -n when they start running out of file descriptors.
24450 - SGI Compatibility patches from Jan Schaumann.
24451 - Tolerate a corrupt cached directory better.
24452 - When a dirserver hasn't approved your server, list which one.
24453 - Go into soft hibernation after 95% of the bandwidth is used,
24454 not 99%. This is especially important for daily hibernators who
24455 have a small accounting max. Hopefully it will result in fewer
24456 cut connections when the hard hibernation starts.
24457 - Load-balance better when using servers that claim more than
24458 800kB/s of capacity.
24459 - Make NT services work (experimental, only used if compiled in).
24462 Changes in version 0.0.9.3 - 2005-01-21
24463 o Bugfixes on 0.0.9:
24464 - Backport the cpu use fixes from main branch, so busy servers won't
24465 need as much processor time.
24466 - Work better when we go offline and then come back, or when we
24467 run Tor at boot before the network is up. We do this by
24468 optimistically trying to fetch a new directory whenever an
24469 application request comes in and we think we're offline -- the
24470 human is hopefully a good measure of when the network is back.
24471 - Backport some minimal hidserv bugfixes: keep rend circuits open as
24472 long as you keep using them; actually publish hidserv descriptors
24473 shortly after they change, rather than waiting 20-40 minutes.
24474 - Enable Mac startup script by default.
24475 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
24476 - When you update AllowUnverifiedNodes or FirewallPorts via the
24477 controller's setconf feature, we were always appending, never
24479 - When you update HiddenServiceDir via setconf, it was screwing up
24480 the order of reading the lines, making it fail.
24481 - Do not rewrite a cached directory back to the cache; otherwise we
24482 will think it is recent and not fetch a newer one on startup.
24483 - Workaround for webservers that lie about Content-Encoding: Tor
24484 now tries to autodetect compressed directories and compression
24485 itself. This lets us Proxypass dir fetches through apache.
24488 Changes in version 0.0.9.2 - 2005-01-04
24489 o Bugfixes on 0.0.9 (crashes and asserts):
24490 - Fix an assert on startup when the disk is full and you're logging
24492 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
24493 style address, then we'd crash.
24494 - Fix an assert trigger when the running-routers string we get from
24495 a dirserver is broken.
24496 - Make worker threads start and run on win32. Now win32 servers
24498 - Bandaid (not actually fix, but now it doesn't crash) an assert
24499 where the dns worker dies mysteriously and the main Tor process
24500 doesn't remember anything about the address it was resolving.
24502 o Bugfixes on 0.0.9 (Win32):
24503 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
24504 name out of the warning/assert messages.
24505 - Fix a superficial "unhandled error on read" bug on win32.
24506 - The win32 installer no longer requires a click-through for our
24507 license, since our Free Software license grants rights but does not
24509 - Win32: When connecting to a dirserver fails, try another one
24510 immediately. (This was already working for non-win32 Tors.)
24511 - Stop trying to parse $HOME on win32 when hunting for default
24513 - Make tor-resolve.c work on win32 by calling network_init().
24515 o Bugfixes on 0.0.9 (other):
24516 - Make 0.0.9.x build on Solaris again.
24517 - Due to a fencepost error, we were blowing away the \n when reporting
24518 confvalue items in the controller. So asking for multiple config
24519 values at once couldn't work.
24520 - When listing circuits that are pending on an opening OR connection,
24521 if we're an OR we were listing circuits that *end* at us as
24522 being pending on every listener, dns/cpu worker, etc. Stop that.
24523 - Dirservers were failing to create 'running-routers' or 'directory'
24524 strings if we had more than some threshold of routers. Fix them so
24525 they can handle any number of routers.
24526 - Fix a superficial "Duplicate mark for close" bug.
24527 - Stop checking for clock skew for OR connections, even for servers.
24528 - Fix a fencepost error that was chopping off the last letter of any
24529 nickname that is the maximum allowed nickname length.
24530 - Update URLs in log messages so they point to the new website.
24531 - Fix a potential problem in mangling server private keys while
24532 writing to disk (not triggered yet, as far as we know).
24533 - Include the licenses for other free software we include in Tor,
24534 now that we're shipping binary distributions more regularly.
24537 Changes in version 0.0.9.1 - 2004-12-15
24538 o Bugfixes on 0.0.9:
24539 - Make hibernation actually work.
24540 - Make HashedControlPassword config option work.
24541 - When we're reporting event circuit status to a controller,
24542 don't use the stream status code.
24545 Changes in version 0.0.9 - 2004-12-12
24547 - Clean up manpage and torrc.sample file.
24548 - Clean up severities and text of log warnings.
24550 - Make servers trigger an assert when they enter hibernation.
24553 Changes in version 0.0.9rc7 - 2004-12-08
24554 o Bugfixes on 0.0.9rc:
24555 - Fix a stack-trashing crash when an exit node begins hibernating.
24556 - Avoid looking at unallocated memory while considering which
24557 ports we need to build circuits to cover.
24558 - Stop a sigpipe: when an 'end' cell races with eof from the app,
24559 we shouldn't hold-open-until-flush if the eof arrived first.
24560 - Fix a bug with init_cookie_authentication() in the controller.
24561 - When recommending new-format log lines, if the upper bound is
24562 LOG_ERR, leave it implicit.
24564 o Bugfixes on 0.0.8.1:
24565 - Fix a whole slew of memory leaks.
24566 - Fix isspace() and friends so they still make Solaris happy
24567 but also so they don't trigger asserts on win32.
24568 - Fix parse_iso_time on platforms without strptime (eg win32).
24569 - win32: tolerate extra "readable" events better.
24570 - win32: when being multithreaded, leave parent fdarray open.
24571 - Make unit tests work on win32.
24574 Changes in version 0.0.9rc6 - 2004-12-06
24575 o Bugfixes on 0.0.9pre:
24576 - Clean up some more integer underflow opportunities (not exploitable
24578 - While hibernating, hup should not regrow our listeners.
24579 - Send an end to the streams we close when we hibernate, rather
24580 than just chopping them off.
24581 - React to eof immediately on non-open edge connections.
24583 o Bugfixes on 0.0.8.1:
24584 - Calculate timeout for waiting for a connected cell from the time
24585 we sent the begin cell, not from the time the stream started. If
24586 it took a long time to establish the circuit, we would time out
24587 right after sending the begin cell.
24588 - Fix router_compare_addr_to_addr_policy: it was not treating a port
24589 of * as always matching, so we were picking reject *:* nodes as
24590 exit nodes too. Oops.
24593 - New circuit building strategy: keep a list of ports that we've
24594 used in the past 6 hours, and always try to have 2 circuits open
24595 or on the way that will handle each such port. Seed us with port
24596 80 so web users won't complain that Tor is "slow to start up".
24597 - Make kill -USR1 dump more useful stats about circuits.
24598 - When warning about retrying or giving up, print the address, so
24599 the user knows which one it's talking about.
24600 - If you haven't used a clean circuit in an hour, throw it away,
24601 just to be on the safe side. (This means after 6 hours a totally
24602 unused Tor client will have no circuits open.)
24605 Changes in version 0.0.9rc5 - 2004-12-01
24606 o Bugfixes on 0.0.8.1:
24607 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
24608 - Let resolve conns retry/expire also, rather than sticking around
24610 - If we are using select, make sure we stay within FD_SETSIZE.
24612 o Bugfixes on 0.0.9pre:
24613 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
24614 but doesn't seem to be currently; thanks to Ilja van Sprundel for
24616 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
24617 instead. Impose minima and maxima for all *Period options; impose
24618 even tighter maxima for fetching if we are a caching dirserver.
24619 Clip rather than rejecting.
24620 - Fetch cached running-routers from servers that serve it (that is,
24621 authdirservers and servers running 0.0.9rc5-cvs or later.)
24624 - Accept *:706 (silc) in default exit policy.
24625 - Implement new versioning format for post 0.1.
24626 - Support "foo.nickname.exit" addresses, to let Alice request the
24627 address "foo" as viewed by exit node "nickname". Based on a patch
24629 - Make tor --version --version dump the cvs Id of every file.
24632 Changes in version 0.0.9rc4 - 2004-11-28
24633 o Bugfixes on 0.0.8.1:
24634 - Make windows sockets actually non-blocking (oops), and handle
24635 win32 socket errors better.
24637 o Bugfixes on 0.0.9rc1:
24638 - Actually catch the -USR2 signal.
24641 Changes in version 0.0.9rc3 - 2004-11-25
24642 o Bugfixes on 0.0.8.1:
24643 - Flush the log file descriptor after we print "Tor opening log file",
24644 so we don't see those messages days later.
24646 o Bugfixes on 0.0.9rc1:
24647 - Make tor-resolve work again.
24648 - Avoid infinite loop in tor-resolve if tor hangs up on it.
24649 - Fix an assert trigger for clients/servers handling resolves.
24652 Changes in version 0.0.9rc2 - 2004-11-24
24653 o Bugfixes on 0.0.9rc1:
24654 - I broke socks5 support while fixing the eof bug.
24655 - Allow unitless bandwidths and intervals; they default to bytes
24657 - New servers don't start out hibernating; they are active until
24658 they run out of bytes, so they have a better estimate of how
24659 long it takes, and so their operators can know they're working.
24662 Changes in version 0.0.9rc1 - 2004-11-23
24663 o Bugfixes on 0.0.8.1:
24664 - Finally fix a bug that's been plaguing us for a year:
24665 With high load, circuit package window was reaching 0. Whenever
24666 we got a circuit-level sendme, we were reading a lot on each
24667 socket, but only writing out a bit. So we would eventually reach
24668 eof. This would be noticed and acted on even when there were still
24669 bytes sitting in the inbuf.
24670 - When poll() is interrupted, we shouldn't believe the revents values.
24672 o Bugfixes on 0.0.9pre6:
24673 - Fix hibernate bug that caused pre6 to be broken.
24674 - Don't keep rephist info for routers that haven't had activity for
24675 24 hours. (This matters now that clients have keys, since we track
24677 - Never call close_temp_logs while validating log options.
24678 - Fix backslash-escaping on tor.sh.in and torctl.in.
24681 - Implement weekly/monthly/daily accounting: now you specify your
24682 hibernation properties by
24683 AccountingMax N bytes|KB|MB|GB|TB
24684 AccountingStart day|week|month [day] HH:MM
24685 Defaults to "month 1 0:00".
24686 - Let bandwidth and interval config options be specified as 5 bytes,
24687 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
24688 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
24689 get back to normal.)
24690 - If your requested entry or exit node has advertised bandwidth 0,
24692 - Be more greedy about filling up relay cells -- we try reading again
24693 once we've processed the stuff we read, in case enough has arrived
24694 to fill the last cell completely.
24695 - Apply NT service patch from Osamu Fujino. Still needs more work.
24698 Changes in version 0.0.9pre6 - 2004-11-15
24699 o Bugfixes on 0.0.8.1:
24700 - Fix assert failure on malformed socks4a requests.
24701 - Use identity comparison, not nickname comparison, to choose which
24702 half of circuit-ID-space each side gets to use. This is needed
24703 because sometimes we think of a router as a nickname, and sometimes
24704 as a hex ID, and we can't predict what the other side will do.
24705 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
24706 write() call will fail and we handle it there.
24707 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
24708 and smartlist_len, which are two major profiling offenders.
24710 o Bugfixes on 0.0.9pre5:
24711 - Fix a bug in read_all that was corrupting config files on windows.
24712 - When we're raising the max number of open file descriptors to
24713 'unlimited', don't log that we just raised it to '-1'.
24714 - Include event code with events, as required by control-spec.txt.
24715 - Don't give a fingerprint when clients do --list-fingerprint:
24716 it's misleading, because it will never be the same again.
24717 - Stop using strlcpy in tor_strndup, since it was slowing us
24719 - Remove warn on startup about missing cached-directory file.
24720 - Make kill -USR1 work again.
24721 - Hibernate if we start tor during the "wait for wakeup-time" phase
24722 of an accounting interval. Log our hibernation plans better.
24723 - Authoritative dirservers now also cache their directory, so they
24724 have it on start-up.
24727 - Fetch running-routers; cache running-routers; compress
24728 running-routers; serve compressed running-routers.z
24729 - Add NSI installer script contributed by J Doe.
24730 - Commit VC6 and VC7 workspace/project files.
24731 - Commit a tor.spec for making RPM files, with help from jbash.
24732 - Add contrib/torctl.in contributed by Glenn Fink.
24733 - Implement the control-spec's SAVECONF command, to write your
24734 configuration to torrc.
24735 - Get cookie authentication for the controller closer to working.
24736 - Include control-spec.txt in the tarball.
24737 - When set_conf changes our server descriptor, upload a new copy.
24738 But don't upload it too often if there are frequent changes.
24739 - Document authentication config in man page, and document signals
24741 - Clean up confusing parts of man page and torrc.sample.
24742 - Make expand_filename handle ~ and ~username.
24743 - Use autoconf to enable largefile support where necessary. Use
24744 ftello where available, since ftell can fail at 2GB.
24745 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
24746 log more informatively.
24747 - Give a slightly more useful output for "tor -h".
24748 - Refuse application socks connections to port 0.
24749 - Check clock skew for verified servers, but allow unverified
24750 servers and clients to have any clock skew.
24751 - Break DirFetchPostPeriod into:
24752 - DirFetchPeriod for fetching full directory,
24753 - StatusFetchPeriod for fetching running-routers,
24754 - DirPostPeriod for posting server descriptor,
24755 - RendPostPeriod for posting hidden service descriptors.
24756 - Make sure the hidden service descriptors are at a random offset
24757 from each other, to hinder linkability.
24760 Changes in version 0.0.9pre5 - 2004-11-09
24761 o Bugfixes on 0.0.9pre4:
24762 - Fix a seg fault in unit tests (doesn't affect main program).
24763 - Fix an assert bug where a hidden service provider would fail if
24764 the first hop of his rendezvous circuit was down.
24765 - Hidden service operators now correctly handle version 1 style
24766 INTRODUCE1 cells (nobody generates them still, so not a critical
24768 - If do_hup fails, actually notice.
24769 - Handle more errnos from accept() without closing the listener.
24770 Some OpenBSD machines were closing their listeners because
24771 they ran out of file descriptors.
24772 - Send resolve cells to exit routers that are running a new
24773 enough version of the resolve code to work right.
24774 - Better handling of winsock includes on non-MSV win32 compilers.
24775 - Some people had wrapped their tor client/server in a script
24776 that would restart it whenever it died. This did not play well
24777 with our "shut down if your version is obsolete" code. Now people
24778 don't fetch a new directory if their local cached version is
24780 - Make our autogen.sh work on ksh as well as bash.
24783 - Hibernation: New config option "AccountingMaxKB" lets you
24784 set how many KBytes per month you want to allow your server to
24785 consume. Rather than spreading those bytes out evenly over the
24786 month, we instead hibernate for some of the month and pop up
24787 at a deterministic time, work until the bytes are consumed, then
24788 hibernate again. Config option "MonthlyAccountingStart" lets you
24789 specify which day of the month your billing cycle starts on.
24790 - Control interface: a separate program can now talk to your
24791 client/server over a socket, and get/set config options, receive
24792 notifications of circuits and streams starting/finishing/dying,
24793 bandwidth used, etc. The next step is to get some GUIs working.
24794 Let us know if you want to help out. See doc/control-spec.txt .
24795 - Ship a contrib/tor-control.py as an example script to interact
24796 with the control port.
24797 - "tor --hash-password zzyxz" will output a salted password for
24798 use in authenticating to the control interface.
24799 - New log format in config:
24800 "Log minsev[-maxsev] stdout|stderr|syslog" or
24801 "Log minsev[-maxsev] file /var/foo"
24804 - DirPolicy config option, to let people reject incoming addresses
24805 from their dirserver.
24806 - "tor --list-fingerprint" will list your identity key fingerprint
24808 - Add "pass" target for RedirectExit, to make it easier to break
24809 out of a sequence of RedirectExit rules.
24810 - Clients now generate a TLS cert too, in preparation for having
24811 them act more like real nodes.
24812 - Ship src/win32/ in the tarball, so people can use it to build.
24813 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
24815 - New "router-status" line in directory, to better bind each verified
24816 nickname to its identity key.
24817 - Deprecate unofficial config option abbreviations, and abbreviations
24818 not on the command line.
24819 - Add a pure-C tor-resolve implementation.
24820 - Use getrlimit and friends to ensure we can reach MaxConn (currently
24821 1024) file descriptors.
24823 o Code security improvements, inspired by Ilja:
24824 - Replace sprintf with snprintf. (I think they were all safe, but
24826 - Replace strcpy/strncpy with strlcpy in more places.
24827 - Avoid strcat; use snprintf or strlcat instead.
24828 - snprintf wrapper with consistent (though not C99) overflow behavior.
24831 Changes in version 0.0.9pre4 - 2004-10-17
24832 o Bugfixes on 0.0.9pre3:
24833 - If the server doesn't specify an exit policy, use the real default
24834 exit policy, not reject *:*.
24835 - Ignore fascistfirewall when uploading/downloading hidden service
24836 descriptors, since we go through Tor for those; and when using
24837 an HttpProxy, since we assume it can reach them all.
24838 - When looking for an authoritative dirserver, use only the ones
24839 configured at boot. Don't bother looking in the directory.
24840 - The rest of the fix for get_default_conf_file() on older win32.
24841 - Make 'Routerfile' config option obsolete.
24844 - New 'MyFamily nick1,...' config option for a server to
24845 specify other servers that shouldn't be used in the same circuit
24846 with it. Only believed if nick1 also specifies us.
24847 - New 'NodeFamily nick1,nick2,...' config option for a client to
24848 specify nodes that it doesn't want to use in the same circuit.
24849 - New 'Redirectexit pattern address:port' config option for a
24850 server to redirect exit connections, e.g. to a local squid.
24853 Changes in version 0.0.9pre3 - 2004-10-13
24854 o Bugfixes on 0.0.8.1:
24855 - Better torrc example lines for dirbindaddress and orbindaddress.
24856 - Improved bounds checking on parsed ints (e.g. config options and
24857 the ones we find in directories.)
24858 - Better handling of size_t vs int, so we're more robust on 64
24860 - Fix the rest of the bug where a newly started OR would appear
24861 as unverified even after we've added his fingerprint and hupped
24863 - Fix a bug from 0.0.7: when read() failed on a stream, we would
24864 close it without sending back an end. So 'connection refused'
24865 would simply be ignored and the user would get no response.
24867 o Bugfixes on 0.0.9pre2:
24868 - Serving the cached-on-disk directory to people is bad. We now
24869 provide no directory until we've fetched a fresh one.
24870 - Workaround for bug on windows where cached-directories get crlf
24872 - Make get_default_conf_file() work on older windows too.
24873 - If we write a *:* exit policy line in the descriptor, don't write
24874 any more exit policy lines.
24877 - Use only 0.0.9pre1 and later servers for resolve cells.
24878 - Make the dirservers file obsolete.
24879 - Include a dir-signing-key token in directories to tell the
24880 parsing entity which key is being used to sign.
24881 - Remove the built-in bulky default dirservers string.
24882 - New config option "Dirserver %s:%d [fingerprint]", which can be
24883 repeated as many times as needed. If no dirservers specified,
24884 default to moria1,moria2,tor26.
24885 - Make moria2 advertise a dirport of 80, so people behind firewalls
24886 will be able to get a directory.
24887 - Http proxy support
24888 - Dirservers translate requests for http://%s:%d/x to /x
24889 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
24890 be routed through this host.
24891 - Clients ask for /tor/x rather than /x for new enough dirservers.
24892 This way we can one day coexist peacefully with apache.
24893 - Clients specify a "Host: %s%d" http header, to be compatible
24894 with more proxies, and so running squid on an exit node can work.
24897 Changes in version 0.0.8.1 - 2004-10-13
24899 - Fix a seg fault that can be triggered remotely for Tor
24900 clients/servers with an open dirport.
24901 - Fix a rare assert trigger, where routerinfos for entries in
24902 our cpath would expire while we're building the path.
24903 - Fix a bug in OutboundBindAddress so it (hopefully) works.
24904 - Fix a rare seg fault for people running hidden services on
24905 intermittent connections.
24906 - Fix a bug in parsing opt keywords with objects.
24907 - Fix a stale pointer assert bug when a stream detaches and
24909 - Fix a string format vulnerability (probably not exploitable)
24910 in reporting stats locally.
24911 - Fix an assert trigger: sometimes launching circuits can fail
24912 immediately, e.g. because too many circuits have failed recently.
24913 - Fix a compile warning on 64 bit platforms.
24916 Changes in version 0.0.9pre2 - 2004-10-03
24918 - Make fetching a cached directory work for 64-bit platforms too.
24919 - Make zlib.h a required header, not an optional header.
24922 Changes in version 0.0.9pre1 - 2004-10-01
24924 - Stop using separate defaults for no-config-file and
24925 empty-config-file. Now you have to explicitly turn off SocksPort,
24926 if you don't want it open.
24927 - Fix a bug in OutboundBindAddress so it (hopefully) works.
24928 - Improve man page to mention more of the 0.0.8 features.
24929 - Fix a rare seg fault for people running hidden services on
24930 intermittent connections.
24931 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
24933 - Fix more dns related bugs: send back resolve_failed and end cells
24934 more reliably when the resolve fails, rather than closing the
24935 circuit and then trying to send the cell. Also attach dummy resolve
24936 connections to a circuit *before* calling dns_resolve(), to fix
24937 a bug where cached answers would never be sent in RESOLVED cells.
24938 - When we run out of disk space, or other log writing error, don't
24939 crash. Just stop logging to that log and continue.
24940 - We were starting to daemonize before we opened our logs, so if
24941 there were any problems opening logs, we would complain to stderr,
24942 which wouldn't work, and then mysteriously exit.
24943 - Fix a rare bug where sometimes a verified OR would connect to us
24944 before he'd uploaded his descriptor, which would cause us to
24945 assign conn->nickname as though he's unverified. Now we look through
24946 the fingerprint list to see if he's there.
24947 - Fix a rare assert trigger, where routerinfos for entries in
24948 our cpath would expire while we're building the path.
24951 - Clients can ask dirservers for /dir.z to get a compressed version
24952 of the directory. Only works for servers running 0.0.9, of course.
24953 - Make clients cache directories and use them to seed their router
24954 lists at startup. This means clients have a datadir again.
24955 - Configuration infrastructure support for warning on obsolete
24957 - Respond to content-encoding headers by trying to uncompress as
24959 - Reply with a deflated directory when a client asks for "dir.z".
24960 We could use allow-encodings instead, but allow-encodings isn't
24961 specified in HTTP 1.0.
24962 - Raise the max dns workers from 50 to 100.
24963 - Discourage people from setting their dirfetchpostperiod more often
24964 than once per minute.
24965 - Protect dirservers from overzealous descriptor uploading -- wait
24966 10 seconds after directory gets dirty, before regenerating.
24969 Changes in version 0.0.8 - 2004-08-25
24970 o Port it to SunOS 5.9 / Athena
24973 Changes in version 0.0.8rc2 - 2004-08-20
24974 o Make it compile on cygwin again.
24975 o When picking unverified routers, skip those with low uptime and/or
24976 low bandwidth, depending on what properties you care about.
24979 Changes in version 0.0.8rc1 - 2004-08-18
24980 o Changes from 0.0.7.3:
24982 - Fix assert triggers: if the other side returns an address 0.0.0.0,
24983 don't put it into the client dns cache.
24984 - If a begin failed due to exit policy, but we believe the IP address
24985 should have been allowed, switch that router to exitpolicy reject *:*
24986 until we get our next directory.
24988 - Clients choose nodes proportional to advertised bandwidth.
24989 - Avoid using nodes with low uptime as introduction points.
24990 - Handle servers with dynamic IP addresses: don't replace
24991 options->Address with the resolved one at startup, and
24992 detect our address right before we make a routerinfo each time.
24993 - 'FascistFirewall' option to pick dirservers and ORs on specific
24994 ports; plus 'FirewallPorts' config option to tell FascistFirewall
24995 which ports are open. (Defaults to 80,443)
24996 - Be more aggressive about trying to make circuits when the network
24997 has changed (e.g. when you unsuspend your laptop).
24998 - Check for time skew on http headers; report date in response to
25000 - If the entrynode config line has only one node, don't pick it as
25002 - Add strict{entry|exit}nodes config options. If set to 1, then
25003 we refuse to build circuits that don't include the specified entry
25005 - OutboundBindAddress config option, to bind to a specific
25006 IP address for outgoing connect()s.
25007 - End truncated log entries (e.g. directories) with "[truncated]".
25009 o Patches to 0.0.8preX:
25011 - Patches to compile and run on win32 again (maybe)?
25012 - Fix crash when looking for ~/.torrc with no $HOME set.
25013 - Fix a race bug in the unit tests.
25014 - Handle verified/unverified name collisions better when new
25015 routerinfo's arrive in a directory.
25016 - Sometimes routers were getting entered into the stats before
25017 we'd assigned their identity_digest. Oops.
25018 - Only pick and establish intro points after we've gotten a
25021 - AllowUnverifiedNodes config option to let circuits choose no-name
25022 routers in entry,middle,exit,introduction,rendezvous positions.
25023 Allow middle and rendezvous positions by default.
25024 - Add a man page for tor-resolve.
25027 Changes in version 0.0.7.3 - 2004-08-12
25028 o Stop dnsworkers from triggering an assert failure when you
25029 ask them to resolve the host "".
25032 Changes in version 0.0.8pre3 - 2004-08-09
25033 o Changes from 0.0.7.2:
25034 - Allow multiple ORs with same nickname in routerlist -- now when
25035 people give us one identity key for a nickname, then later
25036 another, we don't constantly complain until the first expires.
25037 - Remember used bandwidth (both in and out), and publish 15-minute
25038 snapshots for the past day into our descriptor.
25039 - You can now fetch $DIRURL/running-routers to get just the
25040 running-routers line, not the whole descriptor list. (But
25041 clients don't use this yet.)
25042 - When people mistakenly use Tor as an http proxy, point them
25043 at the tor-doc.html rather than the INSTALL.
25044 - Remove our mostly unused -- and broken -- hex_encode()
25045 function. Use base16_encode() instead. (Thanks to Timo Lindfors
25046 for pointing out this bug.)
25047 - Rotate onion keys every 12 hours, not every 2 hours, so we have
25048 fewer problems with people using the wrong key.
25049 - Change the default exit policy to reject the default edonkey,
25050 kazaa, gnutella ports.
25051 - Add replace_file() to util.[ch] to handle win32's rename().
25053 o Changes from 0.0.8preX:
25054 - Fix two bugs in saving onion keys to disk when rotating, so
25055 hopefully we'll get fewer people using old onion keys.
25056 - Fix an assert error that was making SocksPolicy not work.
25057 - Be willing to expire routers that have an open dirport -- it's
25058 just the authoritative dirservers we want to not forget.
25059 - Reject tor-resolve requests for .onion addresses early, so we
25060 don't build a whole rendezvous circuit and then fail.
25061 - When you're warning a server that he's unverified, don't cry
25062 wolf unpredictably.
25063 - Fix a race condition: don't try to extend onto a connection
25064 that's still handshaking.
25065 - For servers in clique mode, require the conn to be open before
25066 you'll choose it for your path.
25067 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
25068 end relay cell, etc.
25069 - Measure bandwidth capacity over the last 24 hours, not just 12
25070 - Bugfix: authoritative dirservers were making and signing a new
25071 directory for each client, rather than reusing the cached one.
25074 Changes in version 0.0.8pre2 - 2004-08-04
25075 o Changes from 0.0.7.2:
25077 - Check directory signature _before_ you decide whether you're
25078 you're running an obsolete version and should exit.
25079 - Check directory signature _before_ you parse the running-routers
25080 list to decide who's running or verified.
25081 - Bugfixes and features:
25082 - Check return value of fclose while writing to disk, so we don't
25083 end up with broken files when servers run out of disk space.
25084 - Log a warning if the user uses an unsafe socks variant, so people
25085 are more likely to learn about privoxy or socat.
25086 - Dirservers now include RFC1123-style dates in the HTTP headers,
25087 which one day we will use to better detect clock skew.
25089 o Changes from 0.0.8pre1:
25090 - Make it compile without warnings again on win32.
25091 - Log a warning if you're running an unverified server, to let you
25092 know you might want to get it verified.
25093 - Only pick a default nickname if you plan to be a server.
25096 Changes in version 0.0.8pre1 - 2004-07-23
25098 - Made our unit tests compile again on OpenBSD 3.5, and tor
25099 itself compile again on OpenBSD on a sparc64.
25100 - We were neglecting milliseconds when logging on win32, so
25101 everything appeared to happen at the beginning of each second.
25103 o Protocol changes:
25104 - 'Extend' relay cell payloads now include the digest of the
25105 intended next hop's identity key. Now we can verify that we're
25106 extending to the right router, and also extend to routers we
25107 hadn't heard of before.
25110 - Tor nodes can now act as relays (with an advertised ORPort)
25111 without being manually verified by the dirserver operators.
25112 - Uploaded descriptors of unverified routers are now accepted
25113 by the dirservers, and included in the directory.
25114 - Verified routers are listed by nickname in the running-routers
25115 list; unverified routers are listed as "$<fingerprint>".
25116 - We now use hash-of-identity-key in most places rather than
25117 nickname or addr:port, for improved security/flexibility.
25118 - To avoid Sybil attacks, paths still use only verified servers.
25119 But now we have a chance to play around with hybrid approaches.
25120 - Nodes track bandwidth usage to estimate capacity (not used yet).
25121 - ClientOnly option for nodes that never want to become servers.
25122 - Directory caching.
25123 - "AuthoritativeDir 1" option for the official dirservers.
25124 - Now other nodes (clients and servers) will cache the latest
25125 directory they've pulled down.
25126 - They can enable their DirPort to serve it to others.
25127 - Clients will pull down a directory from any node with an open
25128 DirPort, and check the signature/timestamp correctly.
25129 - Authoritative dirservers now fetch directories from other
25130 authdirservers, to stay better synced.
25131 - Running-routers list tells who's down also, along with noting
25132 if they're verified (listed by nickname) or unverified (listed
25134 - Allow dirservers to serve running-router list separately.
25135 This isn't used yet.
25136 - ORs connect-on-demand to other ORs
25137 - If you get an extend cell to an OR you're not connected to,
25138 connect, handshake, and forward the create cell.
25139 - The authoritative dirservers stay connected to everybody,
25140 and everybody stays connected to 0.0.7 servers, but otherwise
25141 clients/servers expire unused connections after 5 minutes.
25142 - When servers get a sigint, they delay 30 seconds (refusing new
25143 connections) then exit. A second sigint causes immediate exit.
25144 - File and name management:
25145 - Look for .torrc if no CONFDIR "torrc" is found.
25146 - If no datadir is defined, then choose, make, and secure ~/.tor
25148 - If torrc not found, exitpolicy reject *:*.
25149 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
25150 - If no nickname is defined, derive default from hostname.
25151 - Rename secret key files, e.g. identity.key -> secret_id_key,
25152 to discourage people from mailing their identity key to tor-ops.
25153 - Refuse to build a circuit before the directory has arrived --
25154 it won't work anyway, since you won't know the right onion keys
25156 - Try other dirservers immediately if the one you try is down. This
25157 should tolerate down dirservers better now.
25158 - Parse tor version numbers so we can do an is-newer-than check
25159 rather than an is-in-the-list check.
25160 - New socks command 'resolve', to let us shim gethostbyname()
25162 - A 'tor_resolve' script to access the socks resolve functionality.
25163 - A new socks-extensions.txt doc file to describe our
25164 interpretation and extensions to the socks protocols.
25165 - Add a ContactInfo option, which gets published in descriptor.
25166 - Publish OR uptime in descriptor (and thus in directory) too.
25167 - Write tor version at the top of each log file
25168 - New docs in the tarball:
25170 - Document that you should proxy your SSL traffic too.
25173 Changes in version 0.0.7.2 - 2004-07-07
25174 o A better fix for the 0.0.0.0 problem, that will hopefully
25175 eliminate the remaining related assertion failures.
25178 Changes in version 0.0.7.1 - 2004-07-04
25179 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
25180 since internally we use 0.0.0.0 to signify "not yet resolved".
25183 Changes in version 0.0.7 - 2004-06-07
25184 o Updated the man page to reflect the new features.
25187 Changes in version 0.0.7rc2 - 2004-06-06
25188 o Changes from 0.0.7rc1:
25189 - Make it build on Win32 again.
25190 o Changes from 0.0.6.2:
25191 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
25195 Changes in version 0.0.7rc1 - 2004-06-02
25197 - On sighup, we were adding another log without removing the first
25198 one. So log messages would get duplicated n times for n sighups.
25199 - Several cases of using a connection after we'd freed it. The
25200 problem was that connections that are pending resolve are in both
25201 the pending_resolve tree, and also the circuit's resolving_streams
25202 list. When you want to remove one, you must remove it from both.
25203 - Fix a double-mark-for-close where an end cell arrived for a
25204 resolving stream, and then the resolve failed.
25205 - Check directory signatures based on name of signer, not on whom
25206 we got the directory from. This will let us cache directories more
25209 - Crank up some of our constants to handle more users.
25212 Changes in version 0.0.7pre1 - 2004-06-02
25213 o Fixes for crashes and other obnoxious bugs:
25214 - Fix an epipe bug: sometimes when directory connections failed
25215 to connect, we would give them a chance to flush before closing
25217 - When we detached from a circuit because of resolvefailed, we
25218 would immediately try the same circuit twice more, and then
25219 give up on the resolve thinking we'd tried three different
25221 - Limit the number of intro circuits we'll attempt to build for a
25222 hidden service per 15-minute period.
25223 - Check recommended-software string *early*, before actually parsing
25224 the directory. Thus we can detect an obsolete version and exit,
25225 even if the new directory format doesn't parse.
25226 o Fixes for security bugs:
25227 - Remember which nodes are dirservers when you startup, and if a
25228 random OR enables his dirport, don't automatically assume he's
25229 a trusted dirserver.
25231 - Directory connections were asking the wrong poll socket to
25232 start writing, and not asking themselves to start writing.
25233 - When we detached from a circuit because we sent a begin but
25234 didn't get a connected, we would use it again the first time;
25235 but after that we would correctly switch to a different one.
25236 - Stop warning when the first onion decrypt attempt fails; they
25237 will sometimes legitimately fail now that we rotate keys.
25238 - Override unaligned-access-ok check when $host_cpu is ia64 or
25239 arm. Apparently they allow it but the kernel whines.
25240 - Dirservers try to reconnect periodically too, in case connections
25242 - Fix some memory leaks in directory servers.
25243 - Allow backslash in Win32 filenames.
25244 - Made Tor build complain-free on FreeBSD, hopefully without
25245 breaking other BSD builds. We'll see.
25247 - Doxygen markup on all functions and global variables.
25248 - Make directory functions update routerlist, not replace it. So
25249 now directory disagreements are not so critical a problem.
25250 - Remove the upper limit on number of descriptors in a dirserver's
25251 directory (not that we were anywhere close).
25252 - Allow multiple logfiles at different severity ranges.
25253 - Allow *BindAddress to specify ":port" rather than setting *Port
25254 separately. Allow multiple instances of each BindAddress config
25255 option, so you can bind to multiple interfaces if you want.
25256 - Allow multiple exit policy lines, which are processed in order.
25257 Now we don't need that huge line with all the commas in it.
25258 - Enable accept/reject policies on SOCKS connections, so you can bind
25259 to 0.0.0.0 but still control who can use your OP.
25262 Changes in version 0.0.6.2 - 2004-05-16
25263 o Our integrity-checking digest was checking only the most recent cell,
25264 not the previous cells like we'd thought.
25265 Thanks to Stefan Mark for finding the flaw!
25268 Changes in version 0.0.6.1 - 2004-05-06
25269 o Fix two bugs in our AES counter-mode implementation (this affected
25270 onion-level stream encryption, but not TLS-level). It turns
25271 out we were doing something much more akin to a 16-character
25272 polyalphabetic cipher. Oops.
25273 Thanks to Stefan Mark for finding the flaw!
25274 o Retire moria3 as a directory server, and add tor26 as a directory
25278 Changes in version 0.0.6 - 2004-05-02
25279 [version bump only]
25282 Changes in version 0.0.6rc4 - 2004-05-01
25283 o Update the built-in dirservers list to use the new directory format
25284 o Fix a rare seg fault: if a node offering a hidden service attempts
25285 to build a circuit to Alice's rendezvous point and fails before it
25286 reaches the last hop, it retries with a different circuit, but
25288 o Handle windows socket errors correctly.
25291 Changes in version 0.0.6rc3 - 2004-04-28
25292 o Don't expire non-general excess circuits (if we had enough
25293 circuits open, we were expiring rendezvous circuits -- even
25294 when they had a stream attached. oops.)
25295 o Fetch randomness from /dev/urandom better (not via fopen/fread)
25296 o Better debugging for tls errors
25297 o Some versions of openssl have an SSL_pending function that erroneously
25298 returns bytes when there is a non-application record pending.
25299 o Set Content-Type on the directory and hidserv descriptor.
25300 o Remove IVs from cipher code, since AES-ctr has none.
25301 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
25302 o We were using an array of length zero in a few places.
25303 o win32's gethostbyname can't resolve an IP to an IP.
25304 o win32's close can't close a socket.
25307 Changes in version 0.0.6rc2 - 2004-04-26
25308 o Fix a bug where we were closing tls connections intermittently.
25309 It turns out openssl keeps its errors around -- so if an error
25310 happens, and you don't ask about it, and then another openssl
25311 operation happens and succeeds, and you ask if there was an error,
25312 it tells you about the first error. Fun fun.
25313 o Fix a bug that's been lurking since 27 may 03 (!)
25314 When passing back a destroy cell, we would use the wrong circ id.
25315 'Mostly harmless', but still worth fixing.
25316 o Since we don't support truncateds much, don't bother sending them;
25317 just close the circ.
25318 o check for <machine/limits.h> so we build on NetBSD again (I hope).
25319 o don't crash if a conn that sent a begin has suddenly lost its circuit
25320 (this was quite rare).
25323 Changes in version 0.0.6rc1 - 2004-04-25
25324 o We now rotate link (tls context) keys and onion keys.
25325 o CREATE cells now include oaep padding, so you can tell
25326 if you decrypted them correctly.
25327 o Add bandwidthburst to server descriptor.
25328 o Directories now say which dirserver signed them.
25329 o Use a tor_assert macro that logs failed assertions too.
25332 Changes in version 0.0.6pre5 - 2004-04-18
25333 o changes from 0.0.6pre4:
25334 - make tor build on broken freebsd 5.2 installs
25335 - fix a failed assert when you try an intro point, get a nack, and try
25336 a second one and it works.
25337 - when alice uses a port that the hidden service doesn't accept,
25338 it now sends back an end cell (denied by exit policy). otherwise
25339 alice would just have to wait to time out.
25340 - fix another rare bug: when we had tried all the intro
25341 points for a hidden service, we fetched the descriptor
25342 again, but we left our introcirc thinking it had already
25343 sent an intro, so it kept waiting for a response...
25344 - bugfix: when you sleep your hidden-service laptop, as soon
25345 as it wakes up it tries to upload a service descriptor, but
25346 socketpair fails for some reason (localhost not up yet?).
25347 now we simply give up on that upload, and we'll try again later.
25348 i'd still like to find the bug though.
25349 - if an intro circ waiting for an ack dies before getting one, then
25351 - we were reusing stale service descriptors and refetching usable
25355 Changes in version 0.0.6pre4 - 2004-04-14
25356 o changes from 0.0.6pre3:
25357 - when bob fails to connect to the rendezvous point, and his
25358 circ didn't fail because of the rendezvous point itself, then
25359 he retries a couple of times
25360 - we expire introduction and rendezvous circs more thoroughly
25361 (sometimes they were hanging around forever)
25362 - we expire unattached rendezvous streams that have been around
25363 too long (they were sticking around forever).
25364 - fix a measly fencepost error that was crashing everybody with
25368 Changes in version 0.0.6pre3 - 2004-04-14
25369 o changes from 0.0.6pre2:
25370 - make hup work again
25371 - fix some memory leaks for dirservers
25372 - allow more skew in rendezvous descriptor timestamps, to help
25373 handle people like blanu who don't know what time it is
25374 - normal circs are 3 hops, but some rend/intro circs are 4, if
25375 the initiator doesn't get to choose the last hop
25376 - send acks for introductions, so alice can know whether to try
25378 - bob publishes intro points more correctly
25379 o changes from 0.0.5:
25380 - fix an assert trigger that's been plaguing us since the days
25381 of 0.0.2prexx (thanks weasel!)
25382 - retry stream correctly when we fail to connect because of
25383 exit-policy-reject (should try another) or can't-resolve-address
25384 (also should try another, because dns on random internet servers
25386 - when we hup a dirserver and we've *removed* a server from the
25387 approved-routers list, now we remove that server from the
25388 in-memory directories too
25391 Changes in version 0.0.6pre2 - 2004-04-08
25392 o We fixed our base32 implementation. Now it works on all architectures.
25395 Changes in version 0.0.6pre1 - 2004-04-08
25397 - Hidden services and rendezvous points are implemented. Go to
25398 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
25399 hidden services. (This only works via a socks4a proxy such as
25400 Privoxy, and currently it's quite slow.)
25403 Changes in version 0.0.5 - 2004-03-30
25404 [version bump only]
25407 Changes in version 0.0.5rc3 - 2004-03-29
25408 o Install torrc as torrc.sample -- we no longer clobber your
25410 o Re-enable recommendedversion checking (we broke it in rc2, oops)
25411 o Add in a 'notice' log level for things the operator should hear
25412 but that aren't warnings
25415 Changes in version 0.0.5rc2 - 2004-03-29
25416 o Hold socks connection open until reply is flushed (if possible)
25417 o Make exit nodes resolve IPs to IPs immediately, rather than asking
25418 the dns farm to do it.
25419 o Fix c99 aliasing warnings in rephist.c
25420 o Don't include server descriptors that are older than 24 hours in the
25422 o Give socks 'reject' replies their whole 15s to attempt to flush,
25423 rather than seeing the 60s timeout and assuming the flush had failed.
25424 o Clean automake droppings from the cvs repository
25427 Changes in version 0.0.5rc1 - 2004-03-28
25428 o Fix mangled-state bug in directory fetching (was causing sigpipes).
25429 o Only build circuits after we've fetched the directory: clients were
25430 using only the directory servers before they'd fetched a directory.
25431 This also means longer startup time; so it goes.
25432 o Fix an assert trigger where an OP would fail to handshake, and we'd
25433 expect it to have a nickname.
25434 o Work around a tsocks bug: do a socks reject when AP connection dies
25435 early, else tsocks goes into an infinite loop.
25438 Changes in version 0.0.4 - 2004-03-26
25439 o When connecting to a dirserver or OR and the network is down,
25443 Changes in version 0.0.3 - 2004-03-26
25444 o Warn and fail if server chose a nickname with illegal characters
25445 o Port to Solaris and Sparc:
25446 - include missing header fcntl.h
25447 - have autoconf find -lsocket -lnsl automatically
25448 - deal with hardware word alignment
25449 - make uname() work (solaris has a different return convention)
25450 - switch from using signal() to sigaction()
25451 o Preliminary work on reputation system:
25452 - Keep statistics on success/fail of connect attempts; they're published
25453 by kill -USR1 currently.
25454 - Add a RunTesting option to try to learn link state by creating test
25455 circuits, even when SocksPort is off.
25456 - Remove unused open circuits when there are too many.
25459 Changes in version 0.0.2 - 2004-03-19
25460 - Include strlcpy and strlcat for safer string ops
25461 - define INADDR_NONE so we compile (but still not run) on solaris
25464 Changes in version 0.0.2pre27 - 2004-03-14
25466 - Allow internal tor networks (we were rejecting internal IPs,
25467 now we allow them if they're set explicitly).
25468 - And fix a few endian issues.
25471 Changes in version 0.0.2pre26 - 2004-03-14
25473 - If a stream times out after 15s without a connected cell, don't
25474 try that circuit again: try a new one.
25475 - Retry streams at most 4 times. Then give up.
25476 - When a dirserver gets a descriptor from an unknown router, it
25477 logs its fingerprint (so the dirserver operator can choose to
25478 accept it even without mail from the server operator).
25479 - Inform unapproved servers when we reject their descriptors.
25480 - Make tor build on Windows again. It works as a client, who knows
25482 - Clearer instructions in the torrc for how to set up a server.
25483 - Be more efficient about reading fd's when our global token bucket
25484 (used for rate limiting) becomes empty.
25486 - Stop asserting that computers always go forward in time. It's
25488 - When we sent a cell (e.g. destroy) and then marked an OR connection
25489 expired, we might close it before finishing a flush if the other
25490 side isn't reading right then.
25491 - Don't allow dirservers to start if they haven't defined
25492 RecommendedVersions
25493 - We were caching transient dns failures. Oops.
25494 - Prevent servers from publishing an internal IP as their address.
25495 - Address a strcat vulnerability in circuit.c
25498 Changes in version 0.0.2pre25 - 2004-03-04
25500 - Put the OR's IP in its router descriptor, not its fqdn. That way
25501 we'll stop being stalled by gethostbyname for nodes with flaky dns,
25504 - If the user typed in an address that didn't resolve, the server
25508 Changes in version 0.0.2pre24 - 2004-03-03
25510 - Fix an assertion failure in dns.c, where we were trying to dequeue
25511 a pending dns resolve even if it wasn't pending
25512 - Fix a spurious socks5 warning about still trying to write after the
25513 connection is finished.
25514 - Hold certain marked_for_close connections open until they're finished
25515 flushing, rather than losing bytes by closing them too early.
25516 - Correctly report the reason for ending a stream
25517 - Remove some duplicate calls to connection_mark_for_close
25518 - Put switch_id and start_daemon earlier in the boot sequence, so it
25519 will actually try to chdir() to options.DataDirectory
25520 - Make 'make test' exit(1) if a test fails; fix some unit tests
25521 - Make tor fail when you use a config option it doesn't know about,
25522 rather than warn and continue.
25523 - Make --version work
25524 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
25527 Changes in version 0.0.2pre23 - 2004-02-29
25529 - Print a statement when the first circ is finished, so the user
25530 knows it's working.
25531 - If a relay cell is unrecognized at the end of the circuit,
25532 send back a destroy. (So attacks to mutate cells are more
25534 - New config option 'excludenodes' to avoid certain nodes for circuits.
25535 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
25536 so you can collect coredumps there.
25538 - Fix a bug in tls flushing where sometimes data got wedged and
25539 didn't flush until more data got sent. Hopefully this bug was
25540 a big factor in the random delays we were seeing.
25541 - Make 'connected' cells include the resolved IP, so the client
25542 dns cache actually gets populated.
25543 - Disallow changing from ORPort=0 to ORPort>0 on hup.
25544 - When we time-out on a stream and detach from the circuit, send an
25545 end cell down it first.
25546 - Only warn about an unknown router (in exitnodes, entrynodes,
25547 excludenodes) after we've fetched a directory.
25550 Changes in version 0.0.2pre22 - 2004-02-26
25552 - Servers publish less revealing uname information in descriptors.
25553 - More memory tracking and assertions, to crash more usefully when
25555 - If the default torrc isn't there, just use some default defaults.
25556 Plus provide an internal dirservers file if they don't have one.
25557 - When the user tries to use Tor as an http proxy, give them an http
25558 501 failure explaining that we're a socks proxy.
25559 - Dump a new router.desc on hup, to help confused people who change
25560 their exit policies and then wonder why router.desc doesn't reflect
25562 - Clean up the generic tor.sh init script that we ship with.
25564 - If the exit stream is pending on the resolve, and a destroy arrives,
25565 then the stream wasn't getting removed from the pending list. I
25566 think this was the one causing recent server crashes.
25567 - Use a more robust poll on OSX 10.3, since their poll is flaky.
25568 - When it couldn't resolve any dirservers, it was useless from then on.
25569 Now it reloads the RouterFile (or default dirservers) if it has no
25571 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
25572 many users don't even *have* a /usr/local/sbin/.
25575 Changes in version 0.0.2pre21 - 2004-02-18
25577 - There's a ChangeLog file that actually reflects the changelog.
25578 - There's a 'torify' wrapper script, with an accompanying
25579 tor-tsocks.conf, that simplifies the process of using tsocks for
25580 tor. It even has a man page.
25581 - The tor binary gets installed to sbin rather than bin now.
25582 - Retry streams where the connected cell hasn't arrived in 15 seconds
25583 - Clean up exit policy handling -- get the default out of the torrc,
25584 so we can update it without forcing each server operator to fix
25586 - Allow imaps and pop3s in default exit policy
25588 - Prevent picking middleman nodes as the last node in the circuit
25591 Changes in version 0.0.2pre20 - 2004-01-30
25593 - We now have a deb package, and it's in debian unstable. Go to
25594 it, apt-getters. :)
25595 - I've split the TotalBandwidth option into BandwidthRate (how many
25596 bytes per second you want to allow, long-term) and
25597 BandwidthBurst (how many bytes you will allow at once before the cap
25598 kicks in). This better token bucket approach lets you, say, set
25599 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
25600 performance while not exceeding your monthly bandwidth quota.
25601 - Push out a tls record's worth of data once you've got it, rather
25602 than waiting until you've read everything waiting to be read. This
25603 may improve performance by pipelining better. We'll see.
25604 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
25605 from failed circuits (if they haven't been connected yet) and attach
25607 - Expire old streams that haven't managed to connect. Some day we'll
25608 have them reattach to new circuits instead.
25611 - Fix several memory leaks that were causing servers to become bloated
25613 - Fix a few very rare assert triggers. A few more remain.
25614 - Setuid to User _before_ complaining about running as root.
25617 Changes in version 0.0.2pre19 - 2004-01-07
25619 - Fix deadlock condition in dns farm. We were telling a child to die by
25620 closing the parent's file descriptor to him. But newer children were
25621 inheriting the open file descriptor from the parent, and since they
25622 weren't closing it, the socket never closed, so the child never read
25623 eof, so he never knew to exit. Similarly, dns workers were holding
25624 open other sockets, leading to all sorts of chaos.
25625 - New cleaner daemon() code for forking and backgrounding.
25626 - If you log to a file, it now prints an entry at the top of the
25627 logfile so you know it's working.
25628 - The onionskin challenge length was 30 bytes longer than necessary.
25629 - Started to patch up the spec so it's not quite so out of date.
25632 Changes in version 0.0.2pre18 - 2004-01-02
25634 - Fix endian issues with the 'integrity' field in the relay header.
25635 - Fix a potential bug where connections in state
25636 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
25639 Changes in version 0.0.2pre17 - 2003-12-30
25641 - Made --debuglogfile (or any second log file, actually) work.
25642 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
25643 adversary could force us into an infinite loop.
25646 - Each onionskin handshake now includes a hash of the computed key,
25647 to prove the server's identity and help perfect forward secrecy.
25648 - Changed cell size from 256 to 512 bytes (working toward compatibility
25650 - Changed cell length to 2 bytes, and moved it to the relay header.
25651 - Implemented end-to-end integrity checking for the payloads of
25653 - Separated streamid from 'recognized' (otherwise circuits will get
25654 messed up when we try to have streams exit from the middle). We
25655 use the integrity-checking to confirm that a cell is addressed to
25657 - Randomize the initial circid and streamid values, so an adversary who
25658 breaks into a node can't learn how many circuits or streams have
25662 Changes in version 0.0.2pre16 - 2003-12-14
25664 - Fixed a bug that made HUP trigger an assert
25665 - Fixed a bug where a circuit that immediately failed wasn't being
25666 counted as a failed circuit in counting retries.
25669 - Now we close the circuit when we get a truncated cell: otherwise we're
25670 open to an anonymity attack where a bad node in the path truncates
25671 the circuit and then we open streams at him.
25672 - Add port ranges to exit policies
25673 - Add a conservative default exit policy
25674 - Warn if you're running tor as root
25675 - on HUP, retry OR connections and close/rebind listeners
25676 - options.EntryNodes: try these nodes first when picking the first node
25677 - options.ExitNodes: if your best choices happen to include any of
25678 your preferred exit nodes, you choose among just those preferred
25680 - options.ExcludedNodes: nodes that are never picked in path building
25683 Changes in version 0.0.2pre15 - 2003-12-03
25684 o Robustness and bugfixes:
25685 - Sometimes clients would cache incorrect DNS resolves, which would
25686 really screw things up.
25687 - An OP that goes offline would slowly leak all its sockets and stop
25689 - A wide variety of bugfixes in exit node selection, exit policy
25690 handling, and processing pending streams when a new circuit is
25692 - Pick nodes for a path only from those the directory says are up
25693 - Choose randomly from all running dirservers, not always the first one
25694 - Increase allowed http header size for directory fetch.
25695 - Stop writing to stderr (if we're daemonized it will be closed).
25696 - Enable -g always, so cores will be more useful to me.
25697 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
25700 - Wrote a man page. It lists commonly used options.
25703 - Change default loglevel to warn.
25704 - Make PidFile default to null rather than littering in your CWD.
25705 - OnionRouter config option is now obsolete. Instead it just checks
25707 - Moved to a single unified torrc file for both clients and servers.
25710 Changes in version 0.0.2pre14 - 2003-11-29
25711 o Robustness and bugfixes:
25712 - Force the admin to make the DataDirectory himself
25713 - to get ownership/permissions right
25714 - so clients no longer make a DataDirectory and then never use it
25715 - fix bug where a client who was offline for 45 minutes would never
25716 pull down a directory again
25717 - fix (or at least hide really well) the dns assert bug that was
25718 causing server crashes
25719 - warnings and improved robustness wrt clockskew for certs
25720 - use the native daemon(3) to daemonize, when available
25721 - exit if bind() fails
25722 - exit if neither socksport nor orport is defined
25723 - include our own tor_timegm (Win32 doesn't have its own)
25724 - bugfix for win32 with lots of connections
25725 - fix minor bias in PRNG
25726 - make dirserver more robust to corrupt cached directory
25729 - Wrote the design document (woo)
25731 o Circuit building and exit policies:
25732 - Circuits no longer try to use nodes that the directory has told them
25734 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
25735 bitcounts (18.0.0.0/8).
25736 - Make AP connections standby for a circuit if no suitable circuit
25737 exists, rather than failing
25738 - Circuits choose exit node based on addr/port, exit policies, and
25739 which AP connections are standing by
25740 - Bump min pathlen from 2 to 3
25741 - Relay end cells have a payload to describe why the stream ended.
25742 - If the stream failed because of exit policy, try again with a new
25744 - Clients have a dns cache to remember resolved addresses.
25745 - Notice more quickly when we have no working circuits
25748 - APPort is now called SocksPort
25749 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
25751 - RecommendedVersions is now a config variable rather than
25752 hardcoded (for dirservers)
25753 - Reloads config on HUP
25754 - Usage info on -h or --help
25755 - If you set User and Group config vars, it'll setu/gid to them.
25758 Changes in version 0.0.2pre13 - 2003-10-19
25759 o General stability:
25760 - SSL_write no longer fails when it returns WANTWRITE and the number
25761 of bytes in the buf has changed by the next SSL_write call.
25762 - Fix segfault fetching directory when network is down
25763 - Fix a variety of minor memory leaks
25764 - Dirservers reload the fingerprints file on HUP, so I don't have
25765 to take down the network when I approve a new router
25766 - Default server config file has explicit Address line to specify fqdn
25769 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
25770 - Make listener connections not ever alloc bufs
25772 o Autoconf improvements:
25773 - don't clobber an external CFLAGS in ./configure
25774 - Make install now works
25775 - create var/lib/tor on make install
25776 - autocreate a tor.sh initscript to help distribs
25777 - autocreate the torrc and sample-server-torrc with correct paths
25779 o Log files and Daemonizing now work:
25780 - If --DebugLogFile is specified, log to it at -l debug
25781 - If --LogFile is specified, use it instead of commandline
25782 - If --RunAsDaemon is set, tor forks and backgrounds on startup