1 Changes in version 0.2.9.1-alpha - 2016-08-??
2 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9
5 o New system requirements:
6 - Tor requires Libevent version 2.0.10-stable or later now. This
7 implements ticket 19554.
8 - We now require zlib version 1.2 or later. (Back when we started,
9 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
10 released in 2003. We recommend the latest version.)
12 o Major features (build, hardening):
13 - Tor now builds with -ftrapv by default on compilers that support
14 it. This option detects signed integer overflow, and turns it into
15 a hard-failure. We do not apply this option to code that needs to
16 run in constant time to avoid side-channels; instead, we use
17 -fwrapv. Closes ticket 17983.
18 - When --enable-expensive-hardening is selected, stop applying the
19 clang/gcc sanitizers to code that needs to run in constant-time to
20 avoid side channels: although we are aware of no introduced side-
21 channels, we are not able to prove that this is safe. Related to
24 o Major features (compilation):
25 - Our big list of extra GCC warnings is now enabled by default when
26 building with GCC (or with anything like Clang that claims to be
27 GCC-compatible). To make all warnings into fatal compilation
28 errors, pass --enable-fatal-warnings to configure. Closes
30 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
31 turn on C and POSIX extensions. Closes ticket 19139.
33 o Major features (directory authorities, hidden services):
34 - Directory authorities can now perform the shared randomness
35 protocol specified by proposal 250. Using this protocol, directory
36 authorities can generate a global fresh random number every day.
37 In the future, this global randomness will be used by hidden
38 services to select their responsible HSDirs. This release only
39 implements the directory authority feature; the hidden service
40 side will be implemented in the future as part of proposal 224.
41 Resolves ticket 16943; implements proposal 250.
43 o Major features (downloading):
44 - Use random exponential backoffs when retrying downloads from the
45 dir servers. This prevents a group of Tor instances from becoming
46 too synchronized, or a single Tor instance from becoming too
47 predictable, in its download schedule. Closes ticket 15942.
49 o Major bugfixes (exit policies):
50 - Avoid disclosing exit outbound bind addresses, configured port
51 bind addresses, and local interface addresses in relay descriptors
52 by default under ExitPolicyRejectPrivate. Instead, only reject
53 these (otherwise unlisted) addresses if
54 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
55 0.2.7.2-alpha. Patch by teor.
57 o Major bugfixes (hidden service client):
58 - Allow Tor clients with appropriate controllers to work with
59 FetchHidServDescriptors set to 0. Previously, this option also
60 disabled descriptor cache lookup, thus breaking hidden services
61 entirely when it was set. Fixes bug 18704; bugfix on 0.2.0.20-rc.
64 o Minor features (build, hardening):
65 - Detect and work around a libclang_rt problem that prevents clang
66 from finding __mulodi4() on some 32-bit platforms. This clang bug
67 would keep -ftrapv from linking on those systems. Closes
69 - When building on a system without runtime support for some of the
70 runtime hardening options, try to log a useful warning at
71 configuration time, rather than an incomprehensible warning at
72 link time. If expensive hardening was requested, this warning
73 becomes an error. Closes ticket 18895.
75 o Minor features (code safety):
76 - In our integer-parsing functions, check that the maxiumum value
77 given is no smaller than the minimum value. Closes ticket 19063;
80 o Minor features (controller):
81 - Implement new GETINFO queries for all downloads using
82 download_status_t to schedule retries. Closes ticket 19323.
83 - Add support for configuring basic client authorization on hidden
84 services created with the ADD_ONION control command. Implements
85 ticket 15588. Patch by "special".
86 - Fire a `STATUS_SERVER` event whenever the hibernation status
87 changes between "awake"/"soft"/"hard". Closes ticket 18685.
89 o Minor features (directory authority):
90 - Directory authorities now only give the Guard flag to a relay if
91 they are also giving it the Stable flag. This change allows us to
92 simplify path selection for clients, and it should have minimal
93 effect in practice since >99% of Guards already have the Stable
94 flag. Implements ticket 18624.
95 - Make directory authorities write the v3-status-votes file out to
96 disk earlier in the consensus process, so we have the votes even
97 if we abort the consensus process later. Resolves ticket 19036.
99 o Minor features (hidden service):
100 - Stop being so strict about the payload length of "rendezvous1"
101 cells. We used to be locked in to the "tap" handshake length, and
102 now we can handle better handshakes like "ntor". Resolves
105 o Minor features (infrastructure, time):
106 - Tor now uses the operating system's monotonic timers (where
107 available) for internal fine-grained timing. Previously we would
108 look at the system clock, and then attempt to compensate for the
109 clock running backwards. Closes ticket 18908.
110 - Tor now includes an improved timer backend, so that we can
111 efficiently support tens or hundreds of thousands of concurrent
112 timers, as will be needed for some of our planned anti-traffic-
113 analysis work. This code is based on William Ahern's "timeout.c"
114 project, which implements a "tickless hierarchical timing wheel".
117 o Minor features (logging):
118 - Provide a more useful warning message when configured with an
119 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
120 - When dumping unparseable router descriptors, optionally store them
121 in separate filenames by hash, up to a configurable limit. Closes
123 - Add a set of macros to check nonfatal assertions, for internal
124 use. Migrating more of our checks to these should help us avoid
125 needless crash bugs. Closes ticket 18613.
127 o Minor features (performance):
128 - When fetching a consensus for the first time, use optimistic data.
129 This saves a round-trip during startup. Closes ticket 18815.
131 o Minor features (relay, usability):
132 - When the directory authorities refuse a bad relay's descriptor,
133 encourage the relay operator to contact us. Many relay operators
134 won't notice this line in their logs, but it's a win if even a few
135 learn why we don't like what their relay was doing. Resolves
138 o Minor features (testing):
139 - Let backtrace tests work correctly under AddressSanitizer. Fixes
140 part of bug 18934; bugfix on 0.2.5.2-alpha.
141 - Move the test-network.sh script to chutney, and modify tor's test-
142 network.sh to call the (newer) chutney version when available.
143 Resolves ticket 19116. Patch by teor.
144 - Use the lcov convention for marking lines as unreachable, so that
145 we don't count them when we're generating test coverage data.
146 Update our coverage tools to understand this convention. Closes
149 o Minor bugfixes (bootstrap):
150 - Remember the directory we fetched the consensus or previous
151 certificates from, and use it to fetch future authority
152 certificates. Fixes bug 18963; bugfix on 0.2.8.1-alpha.
154 o Minor bugfixes (build):
155 - Make the test-stem and test-network targets depend only on the tor
156 binary that they will be testing. Previously, they depended on
157 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
158 patch from "cypherpunks".
160 o Minor bugfixes (circuits):
161 - Make sure extend_info_from_router is only called on servers. Fixes
162 bug 19639; bugfix on 0.2.8.1-alpha.
164 o Minor bugfixes (compilation):
165 - When building with Clang, include our full array of GCC warnings.
166 (Previously, we included only a subset, because of the way we
167 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
169 o Minor bugfixes (directory authority):
170 - Authorities now sort the "package" lines in their votes, for ease
171 of debugging. (They are already sorted in the consensus
172 documents.) Fixes bug 18840; bugfix on 0.2.6.3-alpha.
173 - When parsing detached signature, make sure we use the length of
174 the digest algorithm instead of an hardcoded DIGEST256_LEN in
175 order to avoid comparing bytes out of bound with a smaller digest
176 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
178 o Minor bugfixes (documentation):
179 - Document the --passphrase-fd option in the tor manpage. Fixes bug
180 19504; bugfix on 0.2.7.3-rc.
181 - Fix the description of the --passphrase-fd option in the
182 tor-gencert manpage. The option is used to pass the number of a
183 file descriptor to read the passphrase from, not to read the file
184 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
186 o Minor bugfixes (ephemeral hidden service):
187 - When deleting an ephemeral hidden service, close its intro points
188 even if they are not in the open state. Fixes bug 18604; bugfix
191 o Minor bugfixes (guard selection):
192 - Use a single entry guard even if the NumEntryGuards consensus
193 parameter is not provided. Fixes bug 17688; bugfix
195 - Don't mark guards as unreachable if connection_connect() fails.
196 That function fails for local reasons, so it shouldn't reveal
197 anything about the status of the guard. Fixes bug 14334; bugfix
200 o Minor bugfixes (hidden service client):
201 - Increase the minimum number of internal circuits we preemptively
202 build from 2 to 3 so they are available when a client connects to
203 another onion service. Fixes bug 13239; bugfix on 0.1.0.1-rc.
205 o Minor bugfixes (logging):
206 - When logging a directory ownership mismatch, log the owning
207 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
209 o Minor bugfixes (memory leaks):
210 - Fix a small, uncommon memory leak that could occur when reading a
211 truncated ed25519 key file. Fixes bug 18956; bugfix
214 o Minor bugfixes (testing):
215 - Allow clients to retry HSDirs much faster in test networks. Fixes
216 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
217 - Disable ASAN's detection of segmentation faults while running
218 test_bt.sh, so that we can make sure that our own backtrace
219 generation code works. Fixes another aspect of bug 18934; bugfix
220 on 0.2.5.2-alpha. Patch from "cypherpunks".
221 - Fix the test-network-all target on out-of-tree builds by using the
222 correct path to the test driver script. Fixes bug 19421; bugfix
225 o Minor bugfixes (time):
226 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
227 bugfix on all released tor versions.
228 - When computing the difference between two times in milliseconds,
229 we now round to the nearest millisecond correctly. Previously, we
230 could sometimes round in the wrong direction. Fixes bug 19428;
231 bugfix on 0.2.2.2-alpha.
233 o Minor bugfixes (user interface):
234 - Display a more accurate number of suppressed messages in the log
235 rate-limiter. Previously, there was a potential integer overflow
236 in the counter. Now, if the number of messages hits a maximum, the
237 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
239 - Fix a typo in the getting passphrase prompt for the ed25519
240 identity key. Fixes bug 19503; bugfix on 0.2.7.2-alpha.
242 o Code simplification and refactoring:
243 - Remove redundant declarations of the MIN macro. Closes
245 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
246 Closes ticket 18462; patch from "icanhasaccount".
247 - Split the 600-line directory_handle_command_get function into
248 separate functions for different URL types. Closes ticket 16698.
251 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
252 ticket 19153. Patch from "U+039b".
255 - Remove support for "GET /tor/bytes.txt" DirPort request, and
256 "GETINFO dir-usage" controller request, which were only available
257 via a compile-time option in Tor anyway. Feature was added in
258 0.2.2.1-alpha. Resolves ticket 19035.
259 - There is no longer a compile-time option to disable support for
260 TransPort. (If you don't want TransPort; just don't use it.) Patch
261 from "U+039b". Closes ticket 19449.
264 - Run more workqueue tests as part of "make check". These had
265 previously been implemented, but you needed to know special
266 command-line options to enable them.
267 - We now have unit tests for our code to reject zlib "compression
268 bombs". (Fortunately, the code works fine.)
271 Changes in version 0.2.8.6 - 2016-08-02
273 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
275 The Tor 0.2.8 series improves client bootstrapping performance,
276 completes the authority-side implementation of improved identity
277 keys for relays, and includes numerous bugfixes and performance
278 improvements throughout the program. This release continues to
279 improve the coverage of Tor's test suite. For a full list of
280 changes since Tor 0.2.7, see the ReleaseNotes file.
282 Changes since 0.2.8.5-rc:
284 o Minor features (geoip):
285 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
288 o Minor bugfixes (compilation):
289 - Fix a compilation warning in the unit tests on systems where char
290 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
292 o Minor bugfixes (fallback directories):
293 - Remove a fallback that was on the hardcoded list, then opted-out.
294 Fixes bug 19782; update to fallback list from 0.2.8.2-alpha.
296 o Minor bugfixes (Linux seccomp2 sandbox):
297 - Allow more syscalls when running with "Sandbox 1" enabled:
298 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
299 some systems, these are required for Tor to start. Fixes bug
300 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
301 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
302 so that get_interface_address6_via_udp_socket_hack() can work.
303 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
306 Changes in version 0.2.8.5-rc - 2016-07-07
307 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
308 series. If we find no new bugs or regressions here, the first stable
309 0.2.8 release will be identical to it. It has a few small bugfixes
310 against previous versions.
312 o Directory authority changes:
313 - Urras is no longer a directory authority. Closes ticket 19271.
315 o Major bugfixes (heartbeat):
316 - Fix a regression that would crash Tor when the periodic
317 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
318 tor-0.2.8.1-alpha. Reported by "kubaku".
320 o Minor features (build):
321 - Tor now again builds with the recent OpenSSL 1.1 development
322 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
323 - When building manual pages, set the timezone to "UTC", so that the
324 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
325 Patch from intrigeri.
327 o Minor bugfixes (fallback directory selection):
328 - Avoid errors during fallback selection if there are no eligible
329 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
332 o Minor bugfixes (IPv6, microdescriptors):
333 - Don't check node addresses when we only have a routerstatus. This
334 allows IPv6-only clients to bootstrap by fetching microdescriptors
335 from fallback directory mirrors. (The microdescriptor consensus
336 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
339 o Minor bugfixes (logging):
340 - Reduce pointlessly verbose log messages when directory servers
341 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
342 0.2.8.1-alpha. Patch by teor.
343 - When a fallback directory changes its fingerprint from the hard-
344 coded fingerprint, log a less severe, more explanatory log
345 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
347 o Minor bugfixes (Linux seccomp2 sandboxing):
348 - Allow statistics to be written to disk when "Sandbox 1" is
349 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
350 0.2.6.1-alpha respectively.
352 o Minor bugfixes (user interface):
353 - Remove a warning message "Service [scrubbed] not found after
354 descriptor upload". This message appears when one uses HSPOST
355 control command to upload a service descriptor. Since there is
356 only a descriptor and no service, showing this message is
357 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
359 o Fallback directory list:
360 - Add a comment to the generated fallback directory list that
361 explains how to comment out unsuitable fallbacks in a way that's
362 compatible with the stem fallback parser.
363 - Update fallback whitelist and blacklist based on relay operator
364 emails. Blacklist unsuitable (non-working, over-volatile)
365 fallbacks. Resolves ticket 19071. Patch by teor.
366 - Update hard-coded fallback list to remove unsuitable fallbacks.
367 Resolves ticket 19071. Patch by teor.
370 Changes in version 0.2.8.4-rc - 2016-06-15
371 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
372 If we find no new bugs or regressions here, the first stable 0.2.8
373 release will be identical to it. It has a few small bugfixes against
376 o Major bugfixes (user interface):
377 - Correctly give a warning in the cases where a relay is specified
378 by nickname, and one such relay is found, but it is not officially
379 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
381 o Minor features (build):
382 - Tor now builds once again with the recent OpenSSL 1.1 development
383 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
385 o Minor features (geoip):
386 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
389 o Minor bugfixes (compilation):
390 - Cause the unit tests to compile correctly on mingw64 versions that
391 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
393 o Minor bugfixes (downloading):
394 - Predict more correctly whether we'll be downloading over HTTP when
395 we determine the maximum length of a URL. This should avoid a
396 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
400 Changes in version 0.2.8.3-alpha - 2016-05-26
401 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
402 the course of the 0.2.8 development cycle. It improves the behavior of
403 directory clients, fixes several crash bugs, fixes a gap in compiler
404 hardening, and allows the full integration test suite to run on
407 o Major bugfixes (security, client, DNS proxy):
408 - Stop a crash that could occur when a client running with DNSPort
409 received a query with multiple address types, and the first
410 address type was not supported. Found and fixed by Scott Dial.
411 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
413 o Major bugfixes (security, compilation):
414 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
415 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
416 cause a compiler warning, thereby making other checks fail, and
417 needlessly disabling compiler-hardening support. Fixes one case of
418 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
420 o Major bugfixes (security, directory authorities):
421 - Fix a crash and out-of-bounds write during authority voting, when
422 the list of relays includes duplicate ed25519 identity keys. Fixes
423 bug 19032; bugfix on 0.2.8.2-alpha.
425 o Major bugfixes (client, bootstrapping):
426 - Check if bootstrap consensus downloads are still needed when the
427 linked connection attaches. This prevents tor making unnecessary
428 begindir-style connections, which are the only directory
429 connections tor clients make since the fix for 18483 was merged.
430 - Fix some edge cases where consensus download connections may not
431 have been closed, even though they were not needed. Related to fix
433 - Make relays retry consensus downloads the correct number of times,
434 rather than the more aggressive client retry count. Fixes part of
436 - Stop downloading consensuses when we have a consensus, even if we
437 don't have all the certificates for it yet. Fixes bug 18809;
438 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
440 o Major bugfixes (directory mirrors):
441 - Decide whether to advertise begindir support in the the same way
442 we decide whether to advertise our DirPort. Allowing these
443 decisions to become out-of-sync led to surprising behavior like
444 advertising begindir support when hibernation made us not
445 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
448 o Major bugfixes (IPv6 bridges, client):
449 - Actually use IPv6 addresses when selecting directory addresses for
450 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
453 o Major bugfixes (key management):
454 - If OpenSSL fails to generate an RSA key, do not retain a dangling
455 pointer to the previous (uninitialized) key value. The impact here
456 should be limited to a difficult-to-trigger crash, if OpenSSL is
457 running an engine that makes key generation failures possible, or
458 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
459 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
462 o Major bugfixes (testing):
463 - Fix a bug that would block 'make test-network-all' on systems where
464 IPv6 packets were lost. Fixes bug 19008; bugfix on tor-0.2.7.3-rc.
465 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
466 bugfix on 0.2.8.1-alpha.
468 o Minor features (clients):
469 - Make clients, onion services, and bridge relays always use an
470 encrypted begindir connection for directory requests. Resolves
471 ticket 18483. Patch by "teor".
473 o Minor features (fallback directory mirrors):
474 - Give each fallback the same weight for client selection; restrict
475 fallbacks to one per operator; report fallback directory detail
476 changes when rebuilding list; add new fallback directory mirrors
477 to the whitelist; update fallback directories based on the latest
478 OnionOO data; and any other minor simplifications and fixes.
479 Closes tasks 17158, 17905, 18749, bug 18689, and fixes part of bug
480 18812 on 0.2.8.1-alpha; patch by "teor".
482 o Minor features (geoip):
483 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
486 o Minor bugfixes (assert, portability):
487 - Fix an assertion failure in memarea.c on systems where "long" is
488 shorter than the size of a pointer. Fixes bug 18716; bugfix
491 o Minor bugfixes (bootstrap):
492 - Consistently use the consensus download schedule for authority
493 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
495 o Minor bugfixes (build):
496 - Remove a pair of redundant AM_CONDITIONAL declarations from
497 configure.ac. Fixes one final case of bug 17744; bugfix
499 - Resolve warnings when building on systems that are concerned with
500 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
502 - When libscrypt.h is found, but no libscrypt library can be linked,
503 treat libscrypt as absent. Fixes bug 19161; bugfix
506 o Minor bugfixes (client):
507 - Turn all TestingClientBootstrap* into non-testing torrc options.
508 This changes simply renames them by removing "Testing" in front of
509 them and they do not require TestingTorNetwork to be enabled
510 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
511 - Make directory node selection more reliable, mainly for IPv6-only
512 clients and clients with few reachable addresses. Fixes bug 18929;
513 bugfix on 0.2.8.1-alpha. Patch by "teor".
515 o Minor bugfixes (controller, microdescriptors):
516 - Make GETINFO dir/status-vote/current/consensus conform to the
517 control specification by returning "551 Could not open cached
518 consensus..." when not caching consensuses. Fixes bug 18920;
519 bugfix on 0.2.2.6-alpha.
521 o Minor bugfixes (crypto, portability):
522 - The SHA3 and SHAKE routines now produce the correct output on Big
523 Endian systems. No code calls either algorithm yet, so this is
524 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
525 - Tor now builds again with the recent OpenSSL 1.1 development
526 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
529 o Minor bugfixes (directories):
530 - When fetching extrainfo documents, compare their SHA256 digests
531 and Ed25519 signing key certificates with the routerinfo that led
532 us to fetch them, rather than with the most recent routerinfo.
533 Otherwise we generate many spurious warnings about mismatches.
534 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
536 o Minor bugfixes (logging):
537 - When we can't generate a signing key because OfflineMasterKey is
538 set, do not imply that we should have been able to load it. Fixes
539 bug 18133; bugfix on 0.2.7.2-alpha.
540 - Stop periodic_event_dispatch() from blasting twelve lines per
541 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
542 - When rejecting a misformed INTRODUCE2 cell, only log at
543 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
545 o Minor bugfixes (pluggable transports):
546 - Avoid reporting a spurious error when we decide that we don't need
547 to terminate a pluggable transport because it has already exited.
548 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
550 o Minor bugfixes (pointer arithmetic):
551 - Fix a bug in memarea_alloc() that could have resulted in remote
552 heap write access, if Tor had ever passed an unchecked size to
553 memarea_alloc(). Fortunately, all the sizes we pass to
554 memarea_alloc() are pre-checked to be less than 128 kilobytes.
555 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
558 o Minor bugfixes (relays):
559 - Consider more config options when relays decide whether to
560 regenerate their descriptor. Fixes more of bug 12538; bugfix
562 - Resolve some edge cases where we might launch an ORPort
563 reachability check even when DisableNetwork is set. Noticed while
564 fixing bug 18616; bugfix on 0.2.3.9-alpha.
566 o Minor bugfixes (statistics):
567 - We now include consensus downloads via IPv6 in our directory-
568 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
570 o Minor bugfixes (testing):
571 - Allow directories in small networks to bootstrap by skipping
572 DirPort checks when the consensus has no exits. Fixes bug 19003;
573 bugfix on 0.2.8.1-alpha. Patch by teor.
574 - Fix a small memory leak that would occur when the
575 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
576 bugfix on 0.2.5.2-alpha.
578 o Minor bugfixes (time handling):
579 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
580 field. Otherwise, our unit tests crash on Windows. Fixes bug
581 18977; bugfix on 0.2.2.25-alpha.
584 - Document the contents of the 'datadir/keys' subdirectory in the
585 manual page. Closes ticket 17621.
586 - Stop recommending use of nicknames to identify relays in our
587 MapAddress documentation. Closes ticket 18312.
590 Changes in version 0.2.8.2-alpha - 2016-03-28
591 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
592 bugs in earlier versions of Tor, including some that prevented
593 authorities using Tor 0.2.7.x from running correctly. IPv6 and
594 directory support should also be much improved.
596 o New system requirements:
597 - Tor no longer supports versions of OpenSSL with a broken
598 implementation of counter mode. (This bug was present in OpenSSL
599 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
600 longer runs with, these versions.
601 - Tor no longer attempts to support platforms where the "time_t"
602 type is unsigned. (To the best of our knowledge, only OpenVMS does
603 this, and Tor has never actually built on OpenVMS.) Closes
605 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
606 later (released in 2008 and 2009 respectively). If you are
607 building Tor from the git repository instead of from the source
608 distribution, and your tools are older than this, you will need to
609 upgrade. Closes ticket 17732.
611 o Major bugfixes (security, pointers):
612 - Avoid a difficult-to-trigger heap corruption attack when extending
613 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
614 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
615 Reported by Guido Vranken.
617 o Major bugfixes (bridges, pluggable transports):
618 - Modify the check for OR connections to private addresses. Allow
619 bridges on private addresses, including pluggable transports that
620 ignore the (potentially private) address in the bridge line. Fixes
621 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
623 o Major bugfixes (compilation):
624 - Repair hardened builds under the clang compiler. Previously, our
625 use of _FORTIFY_SOURCE would conflict with clang's address
626 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
628 o Major bugfixes (crash on shutdown):
629 - Correctly handle detaching circuits from muxes when shutting down.
630 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
631 - Fix an assert-on-exit bug related to counting memory usage in
632 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
634 o Major bugfixes (crash on startup):
635 - Fix a segfault during startup: If a Unix domain socket was
636 configured as listener (such as a ControlSocket or a SocksPort
637 "unix:" socket), and tor was started as root but not configured to
638 switch to another user, tor would segfault while trying to string
639 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
642 o Major bugfixes (dns proxy mode, crash):
643 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
644 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
646 o Major bugfixes (relays, bridge clients):
647 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
648 bridge clients use the address configured in the bridge line.
649 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
652 o Major bugfixes (voting):
653 - Actually enable support for authorities to match routers by their
654 Ed25519 identities. Previously, the code had been written, but
655 some debugging code that had accidentally been left in the
656 codebase made it stay turned off. Fixes bug 17702; bugfix
658 - When collating votes by Ed25519 identities, authorities now
659 include a "NoEdConsensus" flag if the ed25519 value (or lack
660 thereof) for a server does not reflect the majority consensus.
661 Related to bug 17668; bugfix on 0.2.7.2-alpha.
662 - When generating a vote with keypinning disabled, never include two
663 entries for the same ed25519 identity. This bug was causing
664 authorities to generate votes that they could not parse when a
665 router violated key pinning by changing its RSA identity but
666 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
667 18318. Bugfix on 0.2.7.2-alpha.
669 o Minor features (security, win32):
670 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
671 attack. Fixes bug 18123; bugfix on all tor versions. Patch
674 o Minor features (bug-resistance):
675 - Make Tor survive errors involving connections without a
676 corresponding event object. Previously we'd fail with an
677 assertion; now we produce a log message. Related to bug 16248.
679 o Minor features (build):
680 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
681 as having possible IPFW support. Closes ticket 18448. Patch from
684 o Minor features (code hardening):
685 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
686 level code, to harden against accidental failures to NUL-
687 terminate. Part of ticket 17852. Patch from jsturgix. Found
690 o Minor features (crypto):
691 - Validate the hard-coded Diffie-Hellman parameters and ensure that
692 p is a safe prime, and g is a suitable generator. Closes
695 o Minor features (geoip):
696 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
699 o Minor features (hidden service directory):
700 - Streamline relay-side hsdir handling: when relays consider whether
701 to accept an uploaded hidden service descriptor, they no longer
702 check whether they are one of the relays in the network that is
703 "supposed" to handle that descriptor. Implements ticket 18332.
705 o Minor features (IPv6):
706 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
707 to 1, tor prefers IPv6 directory addresses.
708 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
709 avoids using IPv4 for client OR and directory connections.
710 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
711 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
712 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
714 o Minor features (linux seccomp2 sandbox):
715 - Reject attempts to change our Address with "Sandbox 1" enabled.
716 Changing Address with Sandbox turned on would never actually work,
717 but previously it would fail in strange and confusing ways. Found
720 o Minor features (robustness):
721 - Exit immediately with an error message if the code attempts to use
722 Libevent without having initialized it. This should resolve some
723 frequently-made mistakes in our unit tests. Closes ticket 18241.
725 o Minor features (unix domain sockets):
726 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
727 Unix domain sockets without checking the permissions on the parent
728 directory. (Tor checks permissions by default because some
729 operating systems only check permissions on the parent directory.
730 However, some operating systems do look at permissions on the
731 socket, and tor's default check is unneeded.) Closes ticket 18458.
734 o Minor bugfixes (exit policies, security):
735 - Refresh an exit relay's exit policy when interface addresses
736 change. Previously, tor only refreshed the exit policy when the
737 configured external address changed. Fixes bug 18208; bugfix on
738 0.2.7.3-rc. Patch by teor.
740 o Minor bugfixes (security, hidden services):
741 - Prevent hidden services connecting to client-supplied rendezvous
742 addresses that are reserved as internal or multicast. Fixes bug
743 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
745 o Minor bugfixes (build):
746 - Do not link the unit tests against both the testing and non-
747 testing versions of the static libraries. Fixes bug 18490; bugfix
749 - Avoid spurious failures from configure files related to calling
750 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18625; bugfix on
751 0.2.0.1-alpha. Patch from "cypherpunks".
752 - Silence spurious clang-scan warnings in the ed25519_donna code by
753 explicitly initializing some objects. Fixes bug 18384; bugfix on
754 0.2.7.2-alpha. Patch by teor.
756 o Minor bugfixes (client, bootstrap):
757 - Count receipt of new microdescriptors as progress towards
758 bootstrapping. Previously, with EntryNodes set, Tor might not
759 successfully repopulate the guard set on bootstrapping. Fixes bug
760 16825; bugfix on 0.2.3.1-alpha.
762 o Minor bugfixes (code correctness):
763 - Update to the latest version of Trunnel, which tries harder to
764 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
765 by clang address sanitizer. Fixes bug 18373; bugfix
768 o Minor bugfixes (configuration):
769 - Fix a tiny memory leak when parsing a port configuration ending in
770 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
772 o Minor bugfixes (containers):
773 - If we somehow attempt to construct a heap with more than
774 1073741822 elements, avoid an integer overflow when maintaining
775 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
777 o Minor bugfixes (correctness):
778 - Fix a bad memory handling bug that would occur if we had queued a
779 cell on a channel's incoming queue. Fortunately, we can't actually
780 queue a cell like that as our code is constructed today, but it's
781 best to avoid this kind of error, even if there isn't any code
782 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
784 o Minor bugfixes (directory):
785 - When generating a URL for a directory server on an IPv6 address,
786 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
787 on 0.2.3.9-alpha. Patch from Malek.
789 o Minor bugfixes (fallback directory mirrors):
790 - When requesting extrainfo descriptors from a trusted directory
791 server, check whether it is an authority or a fallback directory
792 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
793 0.2.4.7-alpha. Reported by atagar, patch by teor.
795 o Minor bugfixes (hidden service, client):
796 - Handle the case where the user makes several fast consecutive
797 requests to the same .onion address. Previously, the first six
798 requests would each trigger a descriptor fetch, each picking a
799 directory (there are 6 overall) and the seventh one would fail
800 because no directories were left, thereby triggering a close on
801 all current directory connections asking for the hidden service.
802 The solution here is to not close the connections if we have
803 pending directory fetches. Fixes bug 15937; bugfix
806 o Minor bugfixes (hidden service, control port):
807 - Add the onion address to the HS_DESC event for the UPLOADED action
808 both on success or failure. It was previously hardcoded with
809 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
811 o Minor bugfixes (hidden service, directory):
812 - Bridges now refuse "rendezvous2" (hidden service descriptor)
813 publish attempts. Suggested by ticket 18332.
815 o Minor bugfixes (linux seccomp2 sandbox):
816 - Allow the setrlimit syscall, and the prlimit and prlimit64
817 syscalls, which some libc implementations use under the hood.
818 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
819 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
820 enabled and no DNS resolvers configured. This should help TAILS
821 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
822 - Fix the sandbox's interoperability with unix domain sockets under
823 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
825 o Minor bugfixes (logging):
826 - When logging information about an unparsable networkstatus vote or
827 consensus, do not say "vote" when we mean consensus. Fixes bug
828 18368; bugfix on 0.2.0.8-alpha.
829 - Scrub service name in "unrecognized service ID" log messages.
830 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
831 - Downgrade logs and backtraces about IP versions to info-level.
832 Only log backtraces once each time tor runs. Assists in diagnosing
833 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
834 Christian, patch by teor.
836 o Minor bugfixes (memory safety):
837 - Avoid freeing an uninitialized pointer when opening a socket fails
838 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
839 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
841 - Correctly duplicate addresses in get_interface_address6_list().
842 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
843 patch by "cypherpunks".
844 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
846 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
847 18672; bugfix on 0.2.5.1-alpha.
849 o Minor bugfixes (private directory):
850 - Prevent a race condition when creating private directories. Fixes
851 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
852 Patch from jsturgix. Found with Flawfinder.
854 o Minor bugfixes (test networks, IPv6):
855 - Allow internal IPv6 addresses in descriptors in test networks.
856 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
859 o Minor bugfixes (testing):
860 - We no longer disable assertions in the unit tests when coverage is
861 enabled. Instead, we require you to say --disable-asserts-in-tests
862 to the configure script if you need assertions disabled in the
863 unit tests (for example, if you want to perform branch coverage).
864 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
866 o Minor bugfixes (time parsing):
867 - Avoid overflow in tor_timegm when parsing dates in and after 2038
868 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
869 0.0.2pre14. Patch by teor.
871 o Minor bugfixes (tor-gencert):
872 - Correctly handle the case where an authority operator enters a
873 passphrase but sends an EOF before sending a newline. Fixes bug
874 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
876 o Code simplification and refactoring:
877 - Quote all the string interpolations in configure.ac -- even those
878 which we are pretty sure can't contain spaces. Closes ticket
879 17744. Patch from zerosion.
880 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
881 inplace, so there's no need to have a separate implementation for
882 the non-inplace code. Closes ticket 18258. Patch from Malek.
883 - Simplify return types for some crypto functions that can't
884 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
887 - Change build messages to refer to "Fedora" instead of "Fedora
888 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
889 Patches from "icanhasaccount" and "cypherpunks".
892 - We no longer maintain an internal freelist in memarea.c.
893 Allocators should be good enough to make this code unnecessary,
894 and it's doubtful that it ever had any performance benefit.
897 - Fix several warnings from clang's address sanitizer produced in
899 - Treat backtrace test failures as expected on FreeBSD until we
900 solve bug 17808. Closes ticket 18204.
903 Changes in version 0.2.8.1-alpha - 2016-02-04
904 Tor 0.2.8.1-alpha is the first alpha release in its series. It
905 includes numerous small features and bugfixes against previous Tor
906 versions, and numerous small infrastructure improvements. The most
907 notable features are a set of improvements to the directory subsystem.
909 o Major features (security, Linux):
910 - When Tor starts as root on Linux and is told to switch user ID, it
911 can now retain the capability to bind to low ports. By default,
912 Tor will do this only when it's switching user ID and some low
913 ports have been configured. You can change this behavior with the
914 new option KeepBindCapabilities. Closes ticket 8195.
916 o Major features (directory system):
917 - When bootstrapping multiple consensus downloads at a time, use the
918 first one that starts downloading, and close the rest. This
919 reduces failures when authorities or fallback directories are slow
920 or down. Together with the code for feature 15775, this feature
921 should reduces failures due to fallback churn. Implements ticket
922 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
923 "mikeperry" and "teor".
924 - Include a trial list of default fallback directories, based on an
925 opt-in survey of suitable relays. Doing this should make clients
926 bootstrap more quickly and reliably, and reduce the load on the
927 directory authorities. Closes ticket 15775. Patch by "teor".
928 Candidates identified using an OnionOO script by "weasel", "teor",
929 "gsathya", and "karsten".
930 - Previously only relays that explicitly opened a directory port
931 (DirPort) accepted directory requests from clients. Now all
932 relays, with and without a DirPort, accept and serve tunneled
933 directory requests that they receive through their ORPort. You can
934 disable this behavior using the new DirCache option. Closes
938 - Update the V3 identity key for the dannenberg directory authority:
939 it was changed on 18 November 2015. Closes task 17906. Patch
942 o Minor features (security, clock):
943 - Warn when the system clock appears to move back in time (when the
944 state file was last written in the future). Tor doesn't know that
945 consensuses have expired if the clock is in the past. Patch by
946 "teor". Implements ticket 17188.
948 o Minor features (security, exit policies):
949 - ExitPolicyRejectPrivate now rejects more private addresses by
950 default. Specifically, it now rejects the relay's outbound bind
951 addresses (if configured), and the relay's configured port
952 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
953 0.2.0.11-alpha. Patch by "teor".
955 o Minor features (security, memory erasure):
956 - Set the unused entries in a smartlist to NULL. This helped catch
957 a (harmless) bug, and shouldn't affect performance too much.
958 Implements ticket 17026.
959 - Use SecureMemoryWipe() function to securely clean memory on
960 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
961 Implements feature 17986.
962 - Use explicit_bzero or memset_s when present. Previously, we'd use
963 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
964 from <logan@hackers.mu> and <selven@hackers.mu>.
965 - Make memwipe() do nothing when passed a NULL pointer or buffer of
966 zero size. Check size argument to memwipe() for underflow. Fixes
967 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
970 o Minor features (security, RNG):
971 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
972 positively are not allowed to fail. Previously we depended on
973 internal details of OpenSSL's behavior. Closes ticket 17686.
974 - Never use the system entropy output directly for anything besides
975 seeding the PRNG. When we want to generate important keys, instead
976 of using system entropy directly, we now hash it with the PRNG
977 stream. This may help resist certain attacks based on broken OS
978 entropy implementations. Closes part of ticket 17694.
979 - Use modern system calls (like getentropy() or getrandom()) to
980 generate strong entropy on platforms that have them. Closes
983 o Minor features (accounting):
984 - Added two modes to the AccountingRule option: One for limiting
985 only the number of bytes sent ("AccountingRule out"), and one for
986 limiting only the number of bytes received ("AccountingRule in").
987 Closes ticket 15989; patch from "unixninja92".
989 o Minor features (build):
990 - Since our build process now uses "make distcheck", we no longer
991 force "make dist" to depend on "make check". Closes ticket 17893;
992 patch from "cypherpunks."
993 - Tor now builds successfully with the recent OpenSSL 1.1
994 development branch, and with the latest LibreSSL. Closes tickets
995 17549, 17921, and 17984.
997 o Minor features (controller):
998 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
999 tickets 16774 and 17817. Patch by George Tankersley.
1000 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
1001 service descriptor from a service's local hidden service
1002 descriptor cache. Closes ticket 14846.
1003 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
1004 controllers can examine the the reject rules added by
1005 ExitPolicyRejectPrivate. This makes it easier for stem to display
1008 o Minor features (crypto):
1009 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
1011 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
1012 - When allocating a digest state object, allocate no more space than
1013 we actually need. Previously, we would allocate as much space as
1014 the state for the largest algorithm would need. This change saves
1015 up to 672 bytes per circuit. Closes ticket 17796.
1016 - Improve performance when hashing non-multiple of 8 sized buffers,
1017 based on Andrew Moon's public domain SipHash-2-4 implementation.
1018 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
1020 o Minor features (directory downloads):
1021 - Wait for busy authorities and fallback directories to become non-
1022 busy when bootstrapping. (A similar change was made in 6c443e987d
1023 for directory caches chosen from the consensus.) Closes ticket
1024 17864; patch by "teor".
1025 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
1026 directory mirrors. The default is 1; set it to 0 to disable
1027 fallbacks. Implements ticket 17576. Patch by "teor".
1029 o Minor features (geoip):
1030 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
1033 o Minor features (IPv6):
1034 - Add an argument 'ipv6=address:orport' to the DirAuthority and
1035 FallbackDir torrc options, to specify an IPv6 address for an
1036 authority or fallback directory. Add hard-coded ipv6 addresses for
1037 directory authorities that have them. Closes ticket 17327; patch
1038 from Nick Mathewson and "teor".
1039 - Add address policy assume_action support for IPv6 addresses.
1040 - Limit IPv6 mask bits to 128.
1041 - Warn when comparing against an AF_UNSPEC address in a policy, it's
1042 almost always a bug. Closes ticket 17863; patch by "teor".
1043 - Allow users to configure directory authorities and fallback
1044 directory servers with IPv6 addresses and ORPorts. Resolves
1046 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
1047 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
1048 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
1049 17638; bugfix on 0.0.2pre8. Patch by "teor".
1051 o Minor features (logging):
1052 - When logging to syslog, allow a tag to be added to the syslog
1053 identity (the string prepended to every log message). The tag can
1054 be configured with SyslogIdentityTag and defaults to none. Setting
1055 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
1058 o Minor features (portability):
1059 - Use timingsafe_memcmp() where available. Closes ticket 17944;
1060 patch from <logan@hackers.mu>.
1062 o Minor features (relay, address discovery):
1063 - Add a family argument to get_interface_addresses_raw() and
1064 subfunctions to make network interface address interogation more
1065 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
1066 types of interfaces from the operating system. Resolves
1068 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
1069 fails to enumerate interface addresses using the platform-specific
1070 API, have it rely on the UDP socket fallback technique to try and
1071 find out what IP addresses (both IPv4 and IPv6) our machine has.
1072 Resolves ticket 17951.
1074 o Minor features (replay cache):
1075 - The replay cache now uses SHA256 instead of SHA1. Implements
1076 feature 8961. Patch by "teor", issue reported by "rransom".
1078 o Minor features (unix file permissions):
1079 - Defer creation of Unix sockets until after setuid. This avoids
1080 needing CAP_CHOWN and CAP_FOWNER when using systemd's
1081 CapabilityBoundingSet, or chown and fowner when using SELinux.
1082 Implements part of ticket 17562. Patch from Jamie Nguyen.
1083 - If any directory created by Tor is marked as group readable, the
1084 filesystem group is allowed to be either the default GID or the
1085 root user. Allowing root to read the DataDirectory prevents the
1086 need for CAP_READ_SEARCH when using systemd's
1087 CapabilityBoundingSet, or dac_read_search when using SELinux.
1088 Implements part of ticket 17562. Patch from Jamie Nguyen.
1089 - Introduce a new DataDirectoryGroupReadable option. If it is set to
1090 1, the DataDirectory will be made readable by the default GID.
1091 Implements part of ticket 17562. Patch from Jamie Nguyen.
1093 o Minor bugfixes (accounting):
1094 - The max bandwidth when using 'AccountRule sum' is now correctly
1095 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
1098 o Minor bugfixes (code correctness):
1099 - When closing an entry connection, generate a warning if we should
1100 have sent an end cell for it but we haven't. Fixes bug 17876;
1101 bugfix on 0.2.3.2-alpha.
1102 - Assert that allocated memory held by the reputation code is freed
1103 according to its internal counters. Fixes bug 17753; bugfix
1105 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
1108 o Minor bugfixes (compilation):
1109 - Mark all object files that include micro-revision.i as depending
1110 on it, so as to make parallel builds more reliable. Fixes bug
1111 17826; bugfix on 0.2.5.1-alpha.
1112 - Don't try to use the pthread_condattr_setclock() function unless
1113 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
1114 17819; bugfix on 0.2.6.3-alpha.
1115 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
1117 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
1118 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
1119 - Fix search for libevent libraries on OpenBSD (and other systems
1120 that install libevent 1 and libevent 2 in parallel). Fixes bug
1121 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
1122 - Isolate environment variables meant for tests from the rest of the
1123 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
1124 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
1126 - Remove config.log only from make distclean, not from make clean.
1127 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
1129 o Minor bugfixes (crypto):
1130 - Check the return value of HMAC() and assert on failure. Fixes bug
1131 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
1133 o Minor bugfixes (fallback directories):
1134 - Mark fallbacks as "too busy" when they return a 503 response,
1135 rather than just marking authorities. Fixes bug 17572; bugfix on
1136 0.2.4.7-alpha. Patch by "teor".
1138 o Minor bugfixes (IPv6):
1139 - Update the limits in max_dl_per_request for IPv6 address length.
1140 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
1142 o Minor bugfixes (linux seccomp2 sandbox):
1143 - Fix a crash when using offline master ed25519 keys with the Linux
1144 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
1146 o Minor bugfixes (logging):
1147 - In log messages that include a function name, use __FUNCTION__
1148 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
1149 with clang __PRETTY_FUNCTION__ has extra information we don't
1150 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
1152 - Remove needless quotes from a log message about unparseable
1153 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
1155 o Minor bugfixes (portability):
1156 - Remove an #endif from configure.ac so that we correctly detect the
1157 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
1160 o Minor bugfixes (relays):
1161 - Check that both the ORPort and DirPort (if present) are reachable
1162 before publishing a relay descriptor. Otherwise, relays publish a
1163 descriptor with DirPort 0 when the DirPort reachability test takes
1164 longer than the ORPort reachability test. Fixes bug 18050; bugfix
1165 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
1167 o Minor bugfixes (relays, hidden services):
1168 - Refuse connection requests to private OR addresses unless
1169 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
1170 then refuse to send any cells to a private address. Fixes bugs
1171 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
1173 o Minor bugfixes (safe logging):
1174 - When logging a malformed hostname received through socks4, scrub
1175 it if SafeLogging says we should. Fixes bug 17419; bugfix
1178 o Minor bugfixes (statistics code):
1179 - Consistently check for overflow in round_*_to_next_multiple_of
1180 functions, and add unit tests with additional and maximal values.
1181 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
1182 - Handle edge cases in the laplace functions: avoid division by
1183 zero, avoid taking the log of zero, and silence clang type
1184 conversion warnings using round and trunc. Add unit tests for edge
1185 cases with maximal values. Fixes part of bug 13192; bugfix
1188 o Minor bugfixes (testing):
1189 - The test for log_heartbeat was incorrectly failing in timezones
1190 with non-integer offsets. Instead of comparing the end of the time
1191 string against a constant, compare it to the output of
1192 format_local_iso_time when given the correct input. Fixes bug
1193 18039; bugfix on 0.2.5.4-alpha.
1194 - Make unit tests pass on IPv6-only systems, and systems without
1195 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
1196 bugfix on 0.2.7.3-rc. Patch by "teor".
1197 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
1199 - Check the full results of SHA256 and SHA512 digests in the unit
1200 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
1202 o Code simplification and refactoring:
1203 - Move logging of redundant policy entries in
1204 policies_parse_exit_policy_internal into its own function. Closes
1205 ticket 17608; patch from "juce".
1206 - Extract the more complicated parts of circuit_mark_for_close()
1207 into a new function that we run periodically before circuits are
1208 freed. This change removes more than half of the functions
1209 currently in the "blob". Closes ticket 17218.
1210 - Clean up a little duplicated code in
1211 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
1213 - Decouple the list of streams waiting to be attached to circuits
1214 from the overall connection list. This change makes it possible to
1215 attach streams quickly while simplifying Tor's callgraph and
1216 avoiding O(N) scans of the entire connection list. Closes
1218 - When a direct directory request fails immediately on launch,
1219 instead of relaunching that request from inside the code that
1220 launches it, instead mark the connection for teardown. This change
1221 simplifies Tor's callback and prevents the directory-request
1222 launching code from invoking itself recursively. Closes
1224 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
1225 use them. Closes ticket 17926.
1228 - Add a description of the correct use of the '--keygen' command-
1229 line option. Closes ticket 17583; based on text by 's7r'.
1230 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
1231 - Explain actual minima for BandwidthRate. Closes ticket 16382.
1232 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
1233 - Mention torspec URL in the manpage and point the reader to it
1234 whenever we mention a document that belongs in torspce. Fixes
1238 - Remove client-side support for connecting to Tor relays running
1239 versions of Tor before 0.2.3.6-alpha. These relays didn't support
1240 the v3 TLS handshake protocol, and are no longer allowed on the
1241 Tor network. Implements the client side of ticket 11150. Based on
1242 patches by Tom van der Woerdt.
1245 - Add unit tests to check for common RNG failure modes, such as
1246 returning all zeroes, identical values, or incrementing values
1247 (OpenSSL's rand_predictable feature). Patch by "teor".
1248 - Log more information when the backtrace tests fail. Closes ticket
1249 17892. Patch from "cypherpunks."
1250 - Always test both ed25519 backends, so that we can be sure that our
1251 batch-open replacement code works. Part of ticket 16794.
1252 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
1253 portion of ticket 16831.
1254 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
1255 util_format.c, directory.c, and options_validate.c. Closes tickets
1256 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
1258 - Unit tests for directory_handle_command_get. Closes ticket 17004.
1259 Patch from Reinaldo de Souza Jr.
1262 Changes in version 0.2.7.6 - 2015-12-10
1263 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
1264 well as a minor bug in hidden service reliability.
1266 o Major bugfixes (guard selection):
1267 - Actually look at the Guard flag when selecting a new directory
1268 guard. When we implemented the directory guard design, we
1269 accidentally started treating all relays as if they have the Guard
1270 flag during guard selection, leading to weaker anonymity and worse
1271 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
1274 o Minor features (geoip):
1275 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
1278 o Minor bugfixes (compilation):
1279 - When checking for net/pfvar.h, include netinet/in.h if possible.
1280 This fixes transparent proxy detection on OpenBSD. Fixes bug
1281 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
1282 - Fix a compilation warning with Clang 3.6: Do not check the
1283 presence of an address which can never be NULL. Fixes bug 17781.
1285 o Minor bugfixes (correctness):
1286 - When displaying an IPv6 exit policy, include the mask bits
1287 correctly even when the number is greater than 31. Fixes bug
1288 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
1289 - The wrong list was used when looking up expired intro points in a
1290 rend service object, causing what we think could be reachability
1291 issues for hidden services, and triggering a BUG log. Fixes bug
1292 16702; bugfix on 0.2.7.2-alpha.
1293 - Fix undefined behavior in the tor_cert_checksig function. Fixes
1294 bug 17722; bugfix on 0.2.7.2-alpha.
1297 Changes in version 0.2.7.5 - 2015-11-20
1298 The Tor 0.2.7 release series is dedicated to the memory of Tor user
1299 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
1300 tirelessly to advocate human rights regardless of national borders,
1301 and oppose the encroachments of mass surveillance. He opposed national
1302 exceptionalism, he brought clarity to legal and policy debates, he
1303 understood and predicted the impact of mass surveillance on the world,
1304 and he laid the groundwork for resisting it. While serving on the Tor
1305 Project's board of directors, he brought us his uncompromising focus
1306 on technical excellence in the service of humankind. Caspar was an
1307 inimitable force for good and a wonderful friend. He was kind,
1308 humorous, generous, gallant, and believed we should protect one
1309 another without exception. We honor him here for his ideals, his
1310 efforts, and his accomplishments. Please honor his memory with works
1311 that would make him proud.
1313 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
1315 The 0.2.7 series adds a more secure identity key type for relays,
1316 improves cryptography performance, resolves several longstanding
1317 hidden-service performance issues, improves controller support for
1318 hidden services, and includes small bugfixes and performance
1319 improvements throughout the program. This release series also includes
1320 more tests than before, and significant simplifications to which parts
1321 of Tor invoke which others.
1323 (This release contains no code changes since 0.2.7.4-rc.)
1326 Changes in version 0.2.7.4-rc - 2015-10-21
1327 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
1328 fixes some important memory leaks, and a scary-looking (but mostly
1329 harmless in practice) invalid-read bug. It also has a few small
1330 bugfixes, notably fixes for compilation and portability on different
1331 platforms. If no further significant bounds are found, the next
1332 release will the the official stable release.
1334 o Major bugfixes (security, correctness):
1335 - Fix an error that could cause us to read 4 bytes before the
1336 beginning of an openssl string. This bug could be used to cause
1337 Tor to crash on systems with unusual malloc implementations, or
1338 systems with unusual hardening installed. Fixes bug 17404; bugfix
1341 o Major bugfixes (correctness):
1342 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
1343 bug 17401; bugfix on 0.2.7.3-rc.
1345 o Major bugfixes (memory leaks):
1346 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
1347 17398; bugfix on 0.2.6.1-alpha.
1348 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
1349 17402; bugfix on 0.2.7.3-rc.
1350 - Fix a memory leak when reading an expired signing key from disk.
1351 Fixes bug 17403; bugfix on 0.2.7.2-rc.
1353 o Minor features (geoIP):
1354 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
1357 o Minor bugfixes (compilation):
1358 - Repair compilation with the most recent (unreleased, alpha)
1359 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
1360 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
1361 17251; bugfix on 0.2.7.2-alpha.
1362 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
1363 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
1365 o Minor bugfixes (portability):
1366 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
1367 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
1370 o Minor bugfixes (sandbox):
1371 - Add the "hidserv-stats" filename to our sandbox filter for the
1372 HiddenServiceStatistics option to work properly. Fixes bug 17354;
1373 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
1375 o Minor bugfixes (testing):
1376 - Add unit tests for get_interface_address* failure cases. Fixes bug
1377 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
1378 - Fix breakage when running 'make check' with BSD make. Fixes bug
1379 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
1380 - Make the get_ifaddrs_* unit tests more tolerant of different
1381 network configurations. (Don't assume every test box has an IPv4
1382 address, and don't assume every test box has a non-localhost
1383 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
1384 - Skip backtrace tests when backtrace support is not compiled in.
1385 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
1389 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
1390 - Note that HiddenServicePorts can take a unix domain socket. Closes
1394 Changes in version 0.2.7.3-rc - 2015-09-25
1395 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
1396 contains numerous usability fixes for Ed25519 keys, safeguards against
1397 several misconfiguration problems, significant simplifications to
1398 Tor's callgraph, and numerous bugfixes and small features.
1400 This is the most tested release of Tor to date. The unit tests cover
1401 39.40% of the code, and the integration tests (accessible with "make
1402 test-full-online", requiring stem and chutney and a network
1403 connection) raise the coverage to 64.49%.
1405 o Major features (security, hidden services):
1406 - Hidden services, if using the EntryNodes option, are required to
1407 use more than one EntryNode, in order to avoid a guard discovery
1408 attack. (This would only affect people who had configured hidden
1409 services and manually specified the EntryNodes option with a
1410 single entry-node. The impact was that it would be easy to
1411 remotely identify the guard node used by such a hidden service.
1412 See ticket for more information.) Fixes ticket 14917.
1414 o Major features (Ed25519 keys, keypinning):
1415 - The key-pinning option on directory authorities is now advisory-
1416 only by default. In a future version, or when the AuthDirPinKeys
1417 option is set, pins are enforced again. Disabling key-pinning
1418 seemed like a good idea so that we can survive the fallout of any
1419 usability problems associated with Ed25519 keys. Closes
1422 o Major features (Ed25519 performance):
1423 - Improve the speed of Ed25519 operations and Curve25519 keypair
1424 generation when built targeting 32 bit x86 platforms with SSE2
1425 available. Implements ticket 16535.
1426 - Improve the runtime speed of Ed25519 signature verification by
1427 using Ed25519-donna's batch verification support. Implements
1430 o Major features (performance testing):
1431 - The test-network.sh script now supports performance testing.
1432 Requires corresponding chutney performance testing changes. Patch
1433 by "teor". Closes ticket 14175.
1435 o Major features (relay, Ed25519):
1436 - Significant usability improvements for Ed25519 key management. Log
1437 messages are better, and the code can recover from far more
1438 failure conditions. Thanks to "s7r" for reporting and diagnosing
1440 - Add a new OfflineMasterKey option to tell Tor never to try loading
1441 or generating a secret Ed25519 identity key. You can use this in
1442 combination with tor --keygen to manage offline and/or encrypted
1443 Ed25519 keys. Implements ticket 16944.
1444 - Add a --newpass option to allow changing or removing the
1445 passphrase of an encrypted key with tor --keygen. Implements part
1447 - On receiving a HUP signal, check to see whether the Ed25519
1448 signing key has changed, and reload it if so. Closes ticket 16790.
1450 o Major bugfixes (relay, Ed25519):
1451 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
1452 0.2.7.2-alpha. Reported by "s7r".
1453 - Improve handling of expired signing keys with offline master keys.
1454 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
1456 o Minor features (client-side privacy):
1457 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
1458 lifespan when IsolateSOCKSAuth and streams with SOCKS
1459 authentication are attached to the circuit. This allows
1460 applications like TorBrowser to manage circuit lifetime on their
1461 own. Implements feature 15482.
1462 - When logging malformed hostnames from SOCKS5 requests, respect
1463 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
1465 o Minor features (compilation):
1466 - Give a warning as early as possible when trying to build with an
1467 unsupported OpenSSL version. Closes ticket 16901.
1468 - Fail during configure if we're trying to build against an OpenSSL
1469 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
1470 which started requiring ECC.
1472 o Minor features (geoip):
1473 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
1476 o Minor features (hidden services):
1477 - Relays need to have the Fast flag to get the HSDir flag. As this
1478 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
1479 drop. This change should make some attacks against the hidden
1480 service directory system harder. Fixes ticket 15963.
1481 - Turn on hidden service statistics collection by setting the torrc
1482 option HiddenServiceStatistics to "1" by default. (This keeps
1483 track only of the fraction of traffic used by hidden services, and
1484 the total number of hidden services in existence.) Closes
1486 - Client now uses an introduction point failure cache to know when
1487 to fetch or keep a descriptor in their cache. Previously, failures
1488 were recorded implicitly, but not explicitly remembered. Closes
1491 o Minor features (testing, authorities, documentation):
1492 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
1493 explicitly manage consensus flags in testing networks. Patch by
1494 "robgjansen", modified by "teor". Implements part of ticket 14882.
1496 o Minor bugfixes (security, exit policies):
1497 - ExitPolicyRejectPrivate now also rejects the relay's published
1498 IPv6 address (if any), and any publicly routable IPv4 or IPv6
1499 addresses on any local interfaces. ticket 17027. Patch by "teor".
1500 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
1502 o Minor bug fixes (torrc exit policies):
1503 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
1504 produce IPv6 wildcard addresses. Previously they would produce
1505 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
1506 of bug 16069; bugfix on 0.2.4.7-alpha.
1507 - When parsing torrc ExitPolicies, we now warn for a number of cases
1508 where the user's intent is likely to differ from Tor's actual
1509 behavior. These include: using an IPv4 address with an accept6 or
1510 reject6 line; using "private" on an accept6 or reject6 line; and
1511 including any ExitPolicy lines after accept *:* or reject *:*.
1512 Related to ticket 16069.
1513 - When parsing torrc ExitPolicies, we now issue an info-level
1514 message when expanding an "accept/reject *" line to include both
1515 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
1516 - In each instance above, usage advice is provided to avoid the
1517 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
1518 16069; bugfix on 0.2.4.7-alpha.
1520 o Minor bugfixes (authority):
1521 - Don't assign "HSDir" to a router if it isn't Valid and Running.
1522 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
1523 - Downgrade log messages about Ed25519 key issues if they are in old
1524 cached router descriptors. Fixes part of bug 16286; bugfix
1526 - When we find an Ed25519 key issue in a cached descriptor, stop
1527 saying the descriptor was just "uploaded". Fixes another part of
1528 bug 16286; bugfix on 0.2.7.2-alpha.
1530 o Minor bugfixes (control port):
1531 - Repair a warning and a spurious result when getting the maximum
1532 number of file descriptors from the controller. Fixes bug 16697;
1533 bugfix on 0.2.7.2-alpha.
1535 o Minor bugfixes (correctness):
1536 - When calling channel_free_list(), avoid calling smartlist_remove()
1537 while inside a FOREACH loop. This partially reverts commit
1538 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
1539 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
1541 o Minor bugfixes (documentation):
1542 - Advise users on how to configure separate IPv4 and IPv6 exit
1543 policies in the manpage and sample torrcs. Related to ticket 16069.
1544 - Fix the usage message of tor-resolve(1) so that it no longer lists
1545 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
1546 - Fix an error in the manual page and comments for
1547 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
1548 required "ORPort connectivity". While this is true, it is in no
1549 way unique to the HSDir flag. Of all the flags, only HSDirs need a
1550 DirPort configured in order for the authorities to assign that
1551 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
1554 o Minor bugfixes (Ed25519):
1555 - Fix a memory leak when reading router descriptors with expired
1556 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
1558 o Minor bugfixes (linux seccomp2 sandbox):
1559 - Allow bridge authorities to run correctly under the seccomp2
1560 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
1561 - Allow routers with ed25519 keys to run correctly under the
1562 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
1564 o Minor bugfixes (open file limit):
1565 - Fix set_max_file_descriptors() to set by default the max open file
1566 limit to the current limit when setrlimit() fails. Fixes bug
1567 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
1569 o Minor bugfixes (portability):
1570 - Try harder to normalize the exit status of the Tor process to the
1571 standard-provided range. Fixes bug 16975; bugfix on every version
1573 - Check correctly for Windows socket errors in the workqueue
1574 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
1575 - Fix the behavior of crypto_rand_time_range() when told to consider
1576 times before 1970. (These times were possible when running in a
1577 simulated network environment where time()'s output starts at
1578 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
1579 - Restore correct operation of TLS client-cipher detection on
1580 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
1582 o Minor bugfixes (relay):
1583 - Ensure that worker threads actually exit when a fatal error or
1584 shutdown is indicated. This fix doesn't currently affect the
1585 behavior of Tor, because Tor workers never indicates fatal error
1586 or shutdown except in the unit tests. Fixes bug 16868; bugfix
1588 - Unblock threads before releasing the work queue mutex to ensure
1589 predictable scheduling behavior. Fixes bug 16644; bugfix
1592 o Code simplification and refactoring:
1593 - Change the function that's called when we need to retry all
1594 downloads so that it only reschedules the downloads to happen
1595 immediately, rather than launching them all at once itself. This
1596 further simplifies Tor's callgraph.
1597 - Move some format-parsing functions out of crypto.c and
1598 crypto_curve25519.c into crypto_format.c and/or util_format.c.
1599 - Move the client-only parts of init_keys() into a separate
1600 function. Closes ticket 16763.
1601 - Simplify the microdesc_free() implementation so that it no longer
1602 appears (to code analysis tools) to potentially invoke a huge
1603 suite of other microdesc functions.
1604 - Simply the control graph further by deferring the inner body of
1605 directory_all_unreachable() into a callback. Closes ticket 16762.
1606 - Treat the loss of an owning controller as equivalent to a SIGTERM
1607 signal. This removes a tiny amount of duplicated code, and
1608 simplifies our callgraph. Closes ticket 16788.
1609 - When generating an event to send to the controller, we no longer
1610 put the event over the network immediately. Instead, we queue
1611 these events, and use a Libevent callback to deliver them. This
1612 change simplifies Tor's callgraph by reducing the number of
1613 functions from which all other Tor functions are reachable. Closes
1615 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
1616 that try to scan or compile every file on Unix won't decide that
1618 - Remove the unused "nulterminate" argument from buf_pullup().
1621 - Recommend a 40 GB example AccountingMax in torrc.sample rather
1622 than a 4 GB max. Closes ticket 16742.
1623 - Include the TUNING document in our source tarball. It is referred
1624 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
1628 - The internal pure-C tor-fw-helper tool is now removed from the Tor
1629 distribution, in favor of the pure-Go clone available from
1630 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
1631 used by the C tor-fw-helper are not, in our opinion, very
1632 confidence- inspiring in their secure-programming techniques.
1633 Closes ticket 13338.
1634 - Remove the code that would try to aggressively flush controller
1635 connections while writing to them. This code was introduced in
1636 0.1.2.7-alpha, in order to keep output buffers from exceeding
1637 their limits. But there is no longer a maximum output buffer size,
1638 and flushing data in this way caused some undesirable recursions
1639 in our call graph. Closes ticket 16480.
1642 - Make "bridges+hs" the default test network. This tests almost all
1643 tor functionality during make test-network, while allowing tests
1644 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
1645 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
1646 (chutney). Patches by "teor".
1647 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
1648 by-side in the same parent directory. Closes ticket 16903. Patch
1650 - Use environment variables rather than autoconf substitutions to
1651 send variables from the build system to the test scripts. This
1652 change should be easier to maintain, and cause 'make distcheck' to
1653 work better than before. Fixes bug 17148.
1654 - Add a new set of callgraph analysis scripts that use clang to
1655 produce a list of which Tor functions are reachable from which
1656 other Tor functions. We're planning to use these to help simplify
1657 our code structure by identifying illogical dependencies.
1658 - Add new 'test-full' and 'test-full-online' targets to run all
1659 tests, including integration tests with stem and chutney.
1660 - Make the test-workqueue test work on Windows by initializing the
1661 network before we begin.
1662 - New make target (make test-network-all) to run multiple applicable
1663 chutney test cases. Patch from Teor; closes 16953.
1664 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
1665 functions in dns.c. Implements a portion of ticket 16831.
1666 - When building Tor with testing coverage enabled, run Chutney tests
1667 (if any) using the 'tor-cov' coverage binary.
1668 - When running test-network or test-stem, check for the absence of
1669 stem/chutney before doing any build operations.
1672 Changes in version 0.2.7.2-alpha - 2015-07-27
1673 This, the second alpha in the Tor 0.2.7 series, has a number of new
1674 features, including a way to manually pick the number of introduction
1675 points for hidden services, and the much stronger Ed25519 signing key
1676 algorithm for regular Tor relays (including support for encrypted
1677 offline identity keys in the new algorithm).
1679 Support for Ed25519 on relays is currently limited to signing router
1680 descriptors; later alphas in this series will extend Ed25519 key
1681 support to more parts of the Tor protocol.
1683 o Major features (Ed25519 identity keys, Proposal 220):
1684 - All relays now maintain a stronger identity key, using the Ed25519
1685 elliptic curve signature format. This master key is designed so
1686 that it can be kept offline. Relays also generate an online
1687 signing key, and a set of other Ed25519 keys and certificates.
1688 These are all automatically regenerated and rotated as needed.
1689 Implements part of ticket 12498.
1690 - Directory authorities now vote on Ed25519 identity keys along with
1691 RSA1024 keys. Implements part of ticket 12498.
1692 - Directory authorities track which Ed25519 identity keys have been
1693 used with which RSA1024 identity keys, and do not allow them to
1694 vary freely. Implements part of ticket 12498.
1695 - Microdescriptors now include Ed25519 identity keys. Implements
1696 part of ticket 12498.
1697 - Add support for offline encrypted Ed25519 master keys. To use this
1698 feature on your tor relay, run "tor --keygen" to make a new master
1699 key (or to make a new signing key if you already have a master
1700 key). Closes ticket 13642.
1702 o Major features (Hidden services):
1703 - Add the torrc option HiddenServiceNumIntroductionPoints, to
1704 specify a fixed number of introduction points. Its maximum value
1705 is 10 and default is 3. Using this option can increase a hidden
1706 service's reliability under load, at the cost of making it more
1707 visible that the hidden service is facing extra load. Closes
1709 - Remove the adaptive algorithm for choosing the number of
1710 introduction points, which used to change the number of
1711 introduction points (poorly) depending on the number of
1712 connections the HS sees. Closes ticket 4862.
1714 o Major features (onion key cross-certification):
1715 - Relay descriptors now include signatures of their own identity
1716 keys, made using the TAP and ntor onion keys. These signatures
1717 allow relays to prove ownership of their own onion keys. Because
1718 of this change, microdescriptors will no longer need to include
1719 RSA identity keys. Implements proposal 228; closes ticket 12499.
1721 o Major features (performance):
1722 - Improve the runtime speed of Ed25519 operations by using the
1723 public-domain Ed25519-donna by Andrew M. ("floodyberry").
1724 Implements ticket 16467.
1725 - Improve the runtime speed of the ntor handshake by using an
1726 optimized curve25519 basepoint scalarmult implementation from the
1727 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
1728 ideas by Adam Langley. Implements ticket 9663.
1730 o Major bugfixes (client-side privacy, also in 0.2.6.9):
1731 - Properly separate out each SOCKSPort when applying stream
1732 isolation. The error occurred because each port's session group
1733 was being overwritten by a default value when the listener
1734 connection was initialized. Fixes bug 16247; bugfix on
1735 0.2.6.3-alpha. Patch by "jojelino".
1737 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
1738 - Stop refusing to store updated hidden service descriptors on a
1739 client. This reverts commit 9407040c59218 (which indeed fixed bug
1740 14219, but introduced a major hidden service reachability
1741 regression detailed in bug 16381). This is a temporary fix since
1742 we can live with the minor issue in bug 14219 (it just results in
1743 some load on the network) but the regression of 16381 is too much
1744 of a setback. First-round fix for bug 16381; bugfix
1747 o Major bugfixes (hidden services):
1748 - When cannibalizing a circuit for an introduction point, always
1749 extend to the chosen exit node (creating a 4 hop circuit).
1750 Previously Tor would use the current circuit exit node, which
1751 changed the original choice of introduction point, and could cause
1752 the hidden service to skip excluded introduction points or
1753 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
1756 o Major bugfixes (open file limit):
1757 - The open file limit wasn't checked before calling
1758 tor_accept_socket_nonblocking(), which would make Tor exceed the
1759 limit. Now, before opening a new socket, Tor validates the open
1760 file limit just before, and if the max has been reached, return an
1761 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
1763 o Major bugfixes (stability, also in 0.2.6.10):
1764 - Stop crashing with an assertion failure when parsing certain kinds
1765 of malformed or truncated microdescriptors. Fixes bug 16400;
1766 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
1767 by "cypherpunks_backup".
1768 - Stop random client-side assertion failures that could occur when
1769 connecting to a busy hidden service, or connecting to a hidden
1770 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
1773 o Minor features (directory authorities, security, also in 0.2.6.9):
1774 - The HSDir flag given by authorities now requires the Stable flag.
1775 For the current network, this results in going from 2887 to 2806
1776 HSDirs. Also, it makes it harder for an attacker to launch a sybil
1777 attack by raising the effort for a relay to become Stable to
1778 require at the very least 7 days, while maintaining the 96 hours
1779 uptime requirement for HSDir. Implements ticket 8243.
1781 o Minor features (client):
1782 - Relax the validation of hostnames in SOCKS5 requests, allowing the
1783 character '_' to appear, in order to cope with domains observed in
1784 the wild that are serving non-RFC compliant records. Resolves
1786 - Relax the validation done to hostnames in SOCKS5 requests, and
1787 allow a single trailing '.' to cope with clients that pass FQDNs
1788 using that syntax to explicitly indicate that the domain name is
1789 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
1790 - Add GroupWritable and WorldWritable options to unix-socket based
1791 SocksPort and ControlPort options. These options apply to a single
1792 socket, and override {Control,Socks}SocketsGroupWritable. Closes
1795 o Minor features (control protocol):
1796 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
1797 the control protocol. Resolves ticket 15358.
1799 o Minor features (directory authorities):
1800 - Directory authorities no longer vote against the "Fast", "Stable",
1801 and "HSDir" flags just because they were going to vote against
1802 "Running": if the consensus turns out to be that the router was
1803 running, then the authority's vote should count. Patch from Peter
1804 Retzlaff; closes issue 8712.
1806 o Minor features (geoip, also in 0.2.6.10):
1807 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
1808 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
1810 o Minor features (hidden services):
1811 - Add the new options "HiddenServiceMaxStreams" and
1812 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
1813 limit the maximum number of simultaneous streams per circuit, and
1814 optionally tear down the circuit when the limit is exceeded. Part
1817 o Minor features (portability):
1818 - Use C99 variadic macros when the compiler is not GCC. This avoids
1819 failing compilations on MSVC, and fixes a log-file-based race
1820 condition in our old workarounds. Original patch from Gisle Vanem.
1822 o Minor bugfixes (compilation, also in 0.2.6.9):
1823 - Build with --enable-systemd correctly when libsystemd is
1824 installed, but systemd is not. Fixes bug 16164; bugfix on
1825 0.2.6.3-alpha. Patch from Peter Palfrader.
1827 o Minor bugfixes (controller):
1828 - Add the descriptor ID in each HS_DESC control event. It was
1829 missing, but specified in control-spec.txt. Fixes bug 15881;
1830 bugfix on 0.2.5.2-alpha.
1832 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
1833 - Check for failures from crypto_early_init, and refuse to continue.
1834 A previous typo meant that we could keep going with an
1835 uninitialized crypto library, and would have OpenSSL initialize
1836 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1837 when implementing ticket 4900. Patch by "teor".
1839 o Minor bugfixes (hidden services):
1840 - Fix a crash when reloading configuration while at least one
1841 configured and one ephemeral hidden service exists. Fixes bug
1842 16060; bugfix on 0.2.7.1-alpha.
1843 - Avoid crashing with a double-free bug when we create an ephemeral
1844 hidden service but adding it fails for some reason. Fixes bug
1845 16228; bugfix on 0.2.7.1-alpha.
1847 o Minor bugfixes (Linux seccomp2 sandbox):
1848 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
1849 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
1851 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
1852 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
1853 these when eventfd2() support is missing. Fixes bug 16363; bugfix
1854 on 0.2.6.3-alpha. Patch from "teor".
1856 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
1857 - Fix sandboxing to work when running as a relay, by allowing the
1858 renaming of secret_id_key, and allowing the eventfd2 and futex
1859 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
1861 - Allow systemd connections to work with the Linux seccomp2 sandbox
1862 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
1865 o Minor bugfixes (relay):
1866 - Fix a rarely-encountered memory leak when failing to initialize
1867 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
1870 o Minor bugfixes (systemd):
1871 - Fix an accidental formatting error that broke the systemd
1872 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
1873 - Tor's systemd unit file no longer contains extraneous spaces.
1874 These spaces would sometimes confuse tools like deb-systemd-
1875 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
1877 o Minor bugfixes (tests):
1878 - Use the configured Python executable when running test-stem-full.
1879 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
1881 o Minor bugfixes (tests, also in 0.2.6.9):
1882 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
1883 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
1885 o Minor bugfixes (threads, comments):
1886 - Always initialize return value in compute_desc_id in rendcommon.c
1887 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1888 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
1889 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1890 - Remove undefined directive-in-macro in test_util_writepid clang
1891 3.7 complains that using a preprocessor directive inside a macro
1892 invocation in test_util_writepid in test_util.c is undefined.
1893 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1895 o Code simplification and refactoring:
1896 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
1897 to ensure they remain consistent and visible everywhere.
1898 - Remove some vestigial workarounds for the MSVC6 compiler. We
1899 haven't supported that in ages.
1900 - The link authentication code has been refactored for better
1901 testability and reliability. It now uses code generated with the
1902 "trunnel" binary encoding generator, to reduce the risk of bugs
1903 due to programmer error. Done as part of ticket 12498.
1906 - Include a specific and (hopefully) accurate documentation of the
1907 torrc file's meta-format in doc/torrc_format.txt. This is mainly
1908 of interest to people writing programs to parse or generate torrc
1909 files. This document is not a commitment to long-term
1910 compatibility; some aspects of the current format are a bit
1911 ridiculous. Closes ticket 2325.
1914 - Tor no longer supports copies of OpenSSL that are missing support
1915 for Elliptic Curve Cryptography. (We began using ECC when
1916 available in 0.2.4.8-alpha, for more safe and efficient key
1917 negotiation.) In particular, support for at least one of P256 or
1918 P224 is now required, with manual configuration needed if only
1919 P224 is available. Resolves ticket 16140.
1920 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
1921 on an operating system that has not upgraded to OpenSSL 1.0 or
1922 later, and you compile Tor from source, you will need to install a
1923 more recent OpenSSL to link Tor against.) These versions of
1924 OpenSSL are still supported by the OpenSSL, but the numerous
1925 cryptographic improvements in later OpenSSL releases makes them a
1926 clear choice. Resolves ticket 16034.
1927 - Remove the HidServDirectoryV2 option. Now all relays offer to
1928 store hidden service descriptors. Related to 16543.
1929 - Remove the VoteOnHidServDirectoriesV2 option, since all
1930 authorities have long set it to 1. Closes ticket 16543.
1933 - Document use of coverity, clang static analyzer, and clang dynamic
1934 undefined behavior and address sanitizers in doc/HACKING. Include
1935 detailed usage instructions in the blacklist. Patch by "teor".
1936 Closes ticket 15817.
1937 - The link authentication protocol code now has extensive tests.
1938 - The relay descriptor signature testing code now has
1940 - The test_workqueue program now runs faster, and is enabled by
1941 default as a part of "make check".
1942 - Now that OpenSSL has its own scrypt implementation, add an unit
1943 test that checks for interoperability between libscrypt_scrypt()
1944 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
1945 and rely on EVP_PBE_scrypt() whenever possible. Resolves
1949 Changes in version 0.2.6.10 - 2015-07-12
1950 Tor version 0.2.6.10 fixes some significant stability and hidden
1951 service client bugs, bulletproofs the cryptography init process, and
1952 fixes a bug when using the sandbox code with some older versions of
1953 Linux. Everyone running an older version, especially an older version
1954 of 0.2.6, should upgrade.
1956 o Major bugfixes (hidden service clients, stability):
1957 - Stop refusing to store updated hidden service descriptors on a
1958 client. This reverts commit 9407040c59218 (which indeed fixed bug
1959 14219, but introduced a major hidden service reachability
1960 regression detailed in bug 16381). This is a temporary fix since
1961 we can live with the minor issue in bug 14219 (it just results in
1962 some load on the network) but the regression of 16381 is too much
1963 of a setback. First-round fix for bug 16381; bugfix
1966 o Major bugfixes (stability):
1967 - Stop crashing with an assertion failure when parsing certain kinds
1968 of malformed or truncated microdescriptors. Fixes bug 16400;
1969 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
1970 by "cypherpunks_backup".
1971 - Stop random client-side assertion failures that could occur when
1972 connecting to a busy hidden service, or connecting to a hidden
1973 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
1976 o Minor features (geoip):
1977 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
1978 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
1980 o Minor bugfixes (crypto error-handling):
1981 - Check for failures from crypto_early_init, and refuse to continue.
1982 A previous typo meant that we could keep going with an
1983 uninitialized crypto library, and would have OpenSSL initialize
1984 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1985 when implementing ticket 4900. Patch by "teor".
1987 o Minor bugfixes (Linux seccomp2 sandbox):
1988 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
1989 these when eventfd2() support is missing. Fixes bug 16363; bugfix
1990 on 0.2.6.3-alpha. Patch from "teor".
1993 Changes in version 0.2.6.9 - 2015-06-11
1994 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
1995 requirements for receiving an HSDir flag, and addresses some other small
1996 bugs in the systemd and sandbox code. Clients using circuit isolation
1997 should upgrade; all directory authorities should upgrade.
1999 o Major bugfixes (client-side privacy):
2000 - Properly separate out each SOCKSPort when applying stream
2001 isolation. The error occurred because each port's session group was
2002 being overwritten by a default value when the listener connection
2003 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
2006 o Minor feature (directory authorities, security):
2007 - The HSDir flag given by authorities now requires the Stable flag.
2008 For the current network, this results in going from 2887 to 2806
2009 HSDirs. Also, it makes it harder for an attacker to launch a sybil
2010 attack by raising the effort for a relay to become Stable which
2011 takes at the very least 7 days to do so and by keeping the 96
2012 hours uptime requirement for HSDir. Implements ticket 8243.
2014 o Minor bugfixes (compilation):
2015 - Build with --enable-systemd correctly when libsystemd is
2016 installed, but systemd is not. Fixes bug 16164; bugfix on
2017 0.2.6.3-alpha. Patch from Peter Palfrader.
2019 o Minor bugfixes (Linux seccomp2 sandbox):
2020 - Fix sandboxing to work when running as a relaymby renaming of
2021 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
2022 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
2023 - Allow systemd connections to work with the Linux seccomp2 sandbox
2024 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
2027 o Minor bugfixes (tests):
2028 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
2029 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
2032 Changes in version 0.2.6.8 - 2015-05-21
2033 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
2034 fixes an authority-side bug in assigning the HSDir flag. All directory
2035 authorities should upgrade.
2037 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
2038 - Revert commit that made directory authorities assign the HSDir
2039 flag to relay without a DirPort; this was bad because such relays
2040 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
2043 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
2044 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
2045 a client authorized hidden service. Fixes bug 15823; bugfix
2048 o Minor features (geoip):
2049 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
2050 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
2054 Changes in version 0.2.7.1-alpha - 2015-05-12
2055 Tor 0.2.7.1-alpha is the first alpha release in its series. It
2056 includes numerous small features and bugfixes against previous Tor
2057 versions, and numerous small infrastructure improvements. The most
2058 notable features are several new ways for controllers to interact with
2059 the hidden services subsystem.
2061 o New system requirements:
2062 - Tor no longer includes workarounds to support Libevent versions
2063 before 1.3e. Libevent 2.0 or later is recommended. Closes
2066 o Major features (controller):
2067 - Add the ADD_ONION and DEL_ONION commands that allow the creation
2068 and management of hidden services via the controller. Closes
2070 - New "GETINFO onions/current" and "GETINFO onions/detached"
2071 commands to get information about hidden services created via the
2072 controller. Part of ticket 6411.
2073 - New HSFETCH command to launch a request for a hidden service
2074 descriptor. Closes ticket 14847.
2075 - New HSPOST command to upload a hidden service descriptor. Closes
2076 ticket 3523. Patch by "DonnchaC".
2078 o Major bugfixes (hidden services):
2079 - Revert commit that made directory authorities assign the HSDir
2080 flag to relay without a DirPort; this was bad because such relays
2081 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
2084 o Minor features (clock-jump tolerance):
2085 - Recover better when our clock jumps back many hours, like might
2086 happen for Tails or Whonix users who start with a very wrong
2087 hardware clock, use Tor to discover a more accurate time, and then
2088 fix their clock. Resolves part of ticket 8766.
2090 o Minor features (command-line interface):
2091 - Make --hash-password imply --hush to prevent unnecessary noise.
2092 Closes ticket 15542. Patch from "cypherpunks".
2093 - Print a warning whenever we find a relative file path being used
2094 as torrc option. Resolves issue 14018.
2096 o Minor features (controller):
2097 - Add DirAuthority lines for default directory authorities to the
2098 output of the "GETINFO config/defaults" command if not already
2099 present. Implements ticket 14840.
2100 - Controllers can now use "GETINFO hs/client/desc/id/..." to
2101 retrieve items from the client's hidden service descriptor cache.
2102 Closes ticket 14845.
2103 - Implement a new controller command "GETINFO status/fresh-relay-
2104 descs" to fetch a descriptor/extrainfo pair that was generated on
2105 demand just for the controller's use. Implements ticket 14784.
2107 o Minor features (DoS-resistance):
2108 - Make it harder for attackers to overload hidden services with
2109 introductions, by blocking multiple introduction requests on the
2110 same circuit. Resolves ticket 15515.
2112 o Minor features (geoip):
2113 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
2114 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
2117 o Minor features (HS popularity countermeasure):
2118 - To avoid leaking HS popularity, don't cycle the introduction point
2119 when we've handled a fixed number of INTRODUCE2 cells but instead
2120 cycle it when a random number of introductions is reached, thus
2121 making it more difficult for an attacker to find out the amount of
2122 clients that have used the introduction point for a specific HS.
2123 Closes ticket 15745.
2125 o Minor features (logging):
2126 - Include the Tor version in all LD_BUG log messages, since people
2127 tend to cut and paste those into the bugtracker. Implements
2130 o Minor features (pluggable transports):
2131 - When launching managed pluggable transports on Linux systems,
2132 attempt to have the kernel deliver a SIGTERM on tor exit if the
2133 pluggable transport process is still running. Resolves
2135 - When launching managed pluggable transports, setup a valid open
2136 stdin in the child process that can be used to detect if tor has
2137 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
2138 can be used by implementations to detect this new behavior.
2139 Resolves ticket 15435.
2141 o Minor features (testing):
2142 - Add a test to verify that the compiler does not eliminate our
2143 memwipe() implementation. Closes ticket 15377.
2144 - Add make rule `check-changes` to verify the format of changes
2145 files. Closes ticket 15180.
2146 - Add unit tests for control_event_is_interesting(). Add a compile-
2147 time check that the number of events doesn't exceed the capacity
2148 of control_event_t.event_mask. Closes ticket 15431, checks for
2149 bugs similar to 13085. Patch by "teor".
2150 - Command-line argument tests moved to Stem. Resolves ticket 14806.
2151 - Integrate the ntor, backtrace, and zero-length keys tests into the
2152 automake test suite. Closes ticket 15344.
2153 - Remove assertions during builds to determine Tor's test coverage.
2154 We don't want to trigger these even in assertions, so including
2155 them artificially makes our branch coverage look worse than it is.
2156 This patch provides the new test-stem-full and coverage-html-full
2157 configure options. Implements ticket 15400.
2159 o Minor bugfixes (build):
2160 - Improve out-of-tree builds by making non-standard rules work and
2161 clean up additional files and directories. Fixes bug 15053; bugfix
2164 o Minor bugfixes (command-line interface):
2165 - When "--quiet" is provided along with "--validate-config", do not
2166 write anything to stdout on success. Fixes bug 14994; bugfix
2168 - When complaining about bad arguments to "--dump-config", use
2171 o Minor bugfixes (configuration, unit tests):
2172 - Only add the default fallback directories when the DirAuthorities,
2173 AlternateDirAuthority, and FallbackDir directory config options
2174 are set to their defaults. The default fallback directory list is
2175 currently empty, this fix will only change tor's behavior when it
2176 has default fallback directories. Includes unit tests for
2177 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
2178 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
2180 o Minor bugfixes (correctness):
2181 - For correctness, avoid modifying a constant string in
2182 handle_control_postdescriptor. Fixes bug 15546; bugfix
2184 - Remove side-effects from tor_assert() calls. This was harmless,
2185 because we never disable assertions, but it is bad style and
2186 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
2189 o Minor bugfixes (hidden service):
2190 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
2191 a client authorized hidden service. Fixes bug 15823; bugfix
2193 - Remove an extraneous newline character from the end of hidden
2194 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
2196 o Minor bugfixes (interface):
2197 - Print usage information for --dump-config when it is used without
2198 an argument. Also, fix the error message to use different wording
2199 and add newline at the end. Fixes bug 15541; bugfix
2202 o Minor bugfixes (logs):
2203 - When building Tor under Clang, do not include an extra set of
2204 parentheses in log messages that include function names. Fixes bug
2205 15269; bugfix on every released version of Tor when compiled with
2206 recent enough Clang.
2208 o Minor bugfixes (network):
2209 - When attempting to use fallback technique for network interface
2210 lookup, disregard loopback and multicast addresses since they are
2211 unsuitable for public communications.
2213 o Minor bugfixes (statistics):
2214 - Disregard the ConnDirectionStatistics torrc options when Tor is
2215 not a relay since in that mode of operation no sensible data is
2216 being collected and because Tor might run into measurement hiccups
2217 when running as a client for some time, then becoming a relay.
2218 Fixes bug 15604; bugfix on 0.2.2.35.
2220 o Minor bugfixes (test networks):
2221 - When self-testing reachability, use ExtendAllowPrivateAddresses to
2222 determine if local/private addresses imply reachability. The
2223 previous fix used TestingTorNetwork, which implies
2224 ExtendAllowPrivateAddresses, but this excluded rare configurations
2225 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
2226 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
2227 issue discovered by CJ Ess.
2229 o Minor bugfixes (testing):
2230 - Check for matching value in server response in ntor_ref.py. Fixes
2231 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
2233 - Set the severity correctly when testing
2234 get_interface_addresses_ifaddrs() and
2235 get_interface_addresses_win32(), so that the tests fail gracefully
2236 instead of triggering an assertion. Fixes bug 15759; bugfix on
2237 0.2.6.3-alpha. Reported by Nicolas Derive.
2239 o Code simplification and refactoring:
2240 - Move the hacky fallback code out of get_interface_address6() into
2241 separate function and get it covered with unit-tests. Resolves
2243 - Refactor hidden service client-side cache lookup to intelligently
2244 report its various failure cases, and disentangle failure cases
2245 involving a lack of introduction points. Closes ticket 14391.
2246 - Use our own Base64 encoder instead of OpenSSL's, to allow more
2247 control over the output. Part of ticket 15652.
2250 - Improve the descriptions of statistics-related torrc options in
2251 the manpage to describe rationale and possible uses cases. Fixes
2253 - Improve the layout and formatting of ./configure --help messages.
2254 Closes ticket 15024. Patch from "cypherpunks".
2255 - Standardize on the term "server descriptor" in the manual page.
2256 Previously, we had used "router descriptor", "server descriptor",
2257 and "relay descriptor" interchangeably. Part of ticket 14987.
2260 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
2261 and always use the internal Base64 decoder. The internal decoder
2262 has been part of tor since 0.2.0.10-alpha, and no one should
2263 be using the OpenSSL one. Part of ticket 15652.
2264 - Remove the 'tor_strclear()' function; use memwipe() instead.
2265 Closes ticket 14922.
2268 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
2269 fingerprinting we now recommend pluggable transports; for forward-
2270 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
2271 - Remove the undocumented "--digests" command-line option. It
2272 complicated our build process, caused subtle build issues on
2273 multiple platforms, and is now redundant since we started
2274 including git version identifiers. Closes ticket 14742.
2275 - Tor no longer contains checks for ancient directory cache versions
2276 that didn't know about microdescriptors.
2277 - Tor no longer contains workarounds for stat files generated by
2278 super-old versions of Tor that didn't choose guards sensibly.
2281 Changes in version 0.2.4.27 - 2015-04-06
2282 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
2283 could be used by an attacker to crash hidden services, or crash clients
2284 visiting hidden services. Hidden services should upgrade as soon as
2285 possible; clients should upgrade whenever packages become available.
2287 This release also backports a simple improvement to make hidden
2288 services a bit less vulnerable to denial-of-service attacks.
2290 o Major bugfixes (security, hidden service):
2291 - Fix an issue that would allow a malicious client to trigger an
2292 assertion failure and halt a hidden service. Fixes bug 15600;
2293 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
2294 - Fix a bug that could cause a client to crash with an assertion
2295 failure when parsing a malformed hidden service descriptor. Fixes
2296 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
2298 o Minor features (DoS-resistance, hidden service):
2299 - Introduction points no longer allow multiple INTRODUCE1 cells to
2300 arrive on the same circuit. This should make it more expensive for
2301 attackers to overwhelm hidden services with introductions.
2302 Resolves ticket 15515.
2305 Changes in version 0.2.5.12 - 2015-04-06
2306 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
2307 could be used by an attacker to crash hidden services, or crash clients
2308 visiting hidden services. Hidden services should upgrade as soon as
2309 possible; clients should upgrade whenever packages become available.
2311 This release also backports a simple improvement to make hidden
2312 services a bit less vulnerable to denial-of-service attacks.
2314 o Major bugfixes (security, hidden service):
2315 - Fix an issue that would allow a malicious client to trigger an
2316 assertion failure and halt a hidden service. Fixes bug 15600;
2317 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
2318 - Fix a bug that could cause a client to crash with an assertion
2319 failure when parsing a malformed hidden service descriptor. Fixes
2320 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
2322 o Minor features (DoS-resistance, hidden service):
2323 - Introduction points no longer allow multiple INTRODUCE1 cells to
2324 arrive on the same circuit. This should make it more expensive for
2325 attackers to overwhelm hidden services with introductions.
2326 Resolves ticket 15515.
2329 Changes in version 0.2.6.7 - 2015-04-06
2330 Tor 0.2.6.7 fixes two security issues that could be used by an
2331 attacker to crash hidden services, or crash clients visiting hidden
2332 services. Hidden services should upgrade as soon as possible; clients
2333 should upgrade whenever packages become available.
2335 This release also contains two simple improvements to make hidden
2336 services a bit less vulnerable to denial-of-service attacks.
2338 o Major bugfixes (security, hidden service):
2339 - Fix an issue that would allow a malicious client to trigger an
2340 assertion failure and halt a hidden service. Fixes bug 15600;
2341 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
2342 - Fix a bug that could cause a client to crash with an assertion
2343 failure when parsing a malformed hidden service descriptor. Fixes
2344 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
2346 o Minor features (DoS-resistance, hidden service):
2347 - Introduction points no longer allow multiple INTRODUCE1 cells to
2348 arrive on the same circuit. This should make it more expensive for
2349 attackers to overwhelm hidden services with introductions.
2350 Resolves ticket 15515.
2351 - Decrease the amount of reattempts that a hidden service performs
2352 when its rendezvous circuits fail. This reduces the computational
2353 cost for running a hidden service under heavy load. Resolves
2357 Changes in version 0.2.6.6 - 2015-03-24
2358 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
2360 It adds numerous safety, security, correctness, and performance
2361 improvements. Client programs can be configured to use more kinds of
2362 sockets, AutomapHosts works better, the multithreading backend is
2363 improved, cell transmission is refactored, test coverage is much
2364 higher, more denial-of-service attacks are handled, guard selection is
2365 improved to handle long-term guards better, pluggable transports
2366 should work a bit better, and some annoying hidden service performance
2367 bugs should be addressed.
2369 o Minor bugfixes (portability):
2370 - Use the correct datatype in the SipHash-2-4 function to prevent
2371 compilers from assuming any sort of alignment. Fixes bug 15436;
2372 bugfix on 0.2.5.3-alpha.
2374 Changes in version 0.2.6.5-rc - 2015-03-18
2375 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
2376 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
2378 o Major bugfixes (client):
2379 - Avoid crashing when making certain configuration option changes on
2380 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
2383 o Major bugfixes (pluggable transports):
2384 - Initialize the extended OR Port authentication cookie before
2385 launching pluggable transports. This prevents a race condition
2386 that occured when server-side pluggable transports would cache the
2387 authentication cookie before it has been (re)generated. Fixes bug
2388 15240; bugfix on 0.2.5.1-alpha.
2390 o Major bugfixes (portability):
2391 - Do not crash on startup when running on Solaris. Fixes a bug
2392 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
2395 o Minor features (heartbeat):
2396 - On relays, report how many connections we negotiated using each
2397 version of the Tor link protocols. This information will let us
2398 know if removing support for very old versions of the Tor
2399 protocols is harming the network. Closes ticket 15212.
2401 o Code simplification and refactoring:
2402 - Refactor main loop to extract the 'loop' part. This makes it
2403 easier to run Tor under Shadow. Closes ticket 15176.
2406 Changes in version 0.2.5.11 - 2015-03-17
2407 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
2409 It backports several bugfixes from the 0.2.6 branch, including a
2410 couple of medium-level security fixes for relays and exit nodes.
2411 It also updates the list of directory authorities.
2413 o Directory authority changes:
2414 - Remove turtles as a directory authority.
2415 - Add longclaw as a new (v3) directory authority. This implements
2416 ticket 13296. This keeps the directory authority count at 9.
2417 - The directory authority Faravahar has a new IP address. This
2418 closes ticket 14487.
2420 o Major bugfixes (crash, OSX, security):
2421 - Fix a remote denial-of-service opportunity caused by a bug in
2422 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
2425 o Major bugfixes (relay, stability, possible security):
2426 - Fix a bug that could lead to a relay crashing with an assertion
2427 failure if a buffer of exactly the wrong layout was passed to
2428 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2429 0.2.0.10-alpha. Patch from 'cypherpunks'.
2430 - Do not assert if the 'data' pointer on a buffer is advanced to the
2431 very end of the buffer; log a BUG message instead. Only assert if
2432 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2434 o Major bugfixes (exit node stability):
2435 - Fix an assertion failure that could occur under high DNS load.
2436 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2437 diagnosed and fixed by "cypherpunks".
2439 o Major bugfixes (Linux seccomp2 sandbox):
2440 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
2441 crash during attempts to call wait4. Fixes bug 15088; bugfix on
2442 0.2.5.1-alpha. Patch from "sanic".
2444 o Minor features (controller):
2445 - New "GETINFO bw-event-cache" to get information about recent
2446 bandwidth events. Closes ticket 14128. Useful for controllers to
2447 get recent bandwidth history after the fix for ticket 13988.
2449 o Minor features (geoip):
2450 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2451 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2454 o Minor bugfixes (client, automapping):
2455 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
2456 no value follows the option. Fixes bug 14142; bugfix on
2457 0.2.4.7-alpha. Patch by "teor".
2458 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
2459 14195; bugfix on 0.1.0.1-rc.
2461 o Minor bugfixes (compilation):
2462 - Build without warnings with the stock OpenSSL srtp.h header, which
2463 has a duplicate declaration of SSL_get_selected_srtp_profile().
2464 Fixes bug 14220; this is OpenSSL's bug, not ours.
2466 o Minor bugfixes (directory authority):
2467 - Allow directory authorities to fetch more data from one another if
2468 they find themselves missing lots of votes. Previously, they had
2469 been bumping against the 10 MB queued data limit. Fixes bug 14261;
2470 bugfix on 0.1.2.5-alpha.
2471 - Enlarge the buffer to read bwauth generated files to avoid an
2472 issue when parsing the file in dirserv_read_measured_bandwidths().
2473 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
2475 o Minor bugfixes (statistics):
2476 - Increase period over which bandwidth observations are aggregated
2477 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
2479 o Minor bugfixes (preventative security, C safety):
2480 - When reading a hexadecimal, base-32, or base-64 encoded value from
2481 a string, always overwrite the whole output buffer. This prevents
2482 some bugs where we would look at (but fortunately, not reveal)
2483 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
2487 Changes in version 0.2.4.26 - 2015-03-17
2488 Tor 0.2.4.26 includes an updated list of directory authorities. It
2489 also backports a couple of stability and security bugfixes from 0.2.5
2492 o Directory authority changes:
2493 - Remove turtles as a directory authority.
2494 - Add longclaw as a new (v3) directory authority. This implements
2495 ticket 13296. This keeps the directory authority count at 9.
2496 - The directory authority Faravahar has a new IP address. This
2497 closes ticket 14487.
2499 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
2500 - Fix an assertion failure that could occur under high DNS load.
2501 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2502 diagnosed and fixed by "cypherpunks".
2504 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
2505 - Fix a bug that could lead to a relay crashing with an assertion
2506 failure if a buffer of exactly the wrong layout was passed to
2507 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2508 0.2.0.10-alpha. Patch from 'cypherpunks'.
2509 - Do not assert if the 'data' pointer on a buffer is advanced to the
2510 very end of the buffer; log a BUG message instead. Only assert if
2511 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2513 o Minor features (geoip):
2514 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2515 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2518 Changes in version 0.2.6.4-rc - 2015-03-09
2519 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
2520 attacker might be able to use in order to crash certain Tor
2521 directories. It also resolves some minor issues left over from, or
2522 introduced in, Tor 0.2.6.3-alpha or earlier.
2524 o Major bugfixes (crash, OSX, security):
2525 - Fix a remote denial-of-service opportunity caused by a bug in
2526 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
2529 o Major bugfixes (relay, stability, possible security):
2530 - Fix a bug that could lead to a relay crashing with an assertion
2531 failure if a buffer of exactly the wrong layout is passed to
2532 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2533 0.2.0.10-alpha. Patch from "cypherpunks".
2534 - Do not assert if the 'data' pointer on a buffer is advanced to the
2535 very end of the buffer; log a BUG message instead. Only assert if
2536 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2538 o Major bugfixes (FreeBSD IPFW transparent proxy):
2539 - Fix address detection with FreeBSD transparent proxies, when
2540 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
2543 o Major bugfixes (Linux seccomp2 sandbox):
2544 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
2545 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
2547 - Allow AF_UNIX hidden services to be used with the seccomp2
2548 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
2549 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
2550 crash during attempts to call wait4. Fixes bug 15088; bugfix on
2551 0.2.5.1-alpha. Patch from "sanic".
2553 o Minor features (controller):
2554 - Messages about problems in the bootstrap process now include
2555 information about the server we were trying to connect to when we
2556 noticed the problem. Closes ticket 15006.
2558 o Minor features (geoip):
2559 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2560 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2563 o Minor features (logs):
2564 - Quiet some log messages in the heartbeat and at startup. Closes
2567 o Minor bugfixes (certificate handling):
2568 - If an authority operator accidentally makes a signing certificate
2569 with a future publication time, do not discard its real signing
2570 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
2571 - Remove any old authority certificates that have been superseded
2572 for at least two days. Previously, we would keep superseded
2573 certificates until they expired, if they were published close in
2574 time to the certificate that superseded them. Fixes bug 11454;
2575 bugfix on 0.2.1.8-alpha.
2577 o Minor bugfixes (compilation):
2578 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
2580 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
2583 o Minor bugfixes (testing):
2584 - Fix endianness issues in unit test for resolve_my_address() to
2585 have it pass on big endian systems. Fixes bug 14980; bugfix on
2587 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
2588 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
2589 - When running the new 'make test-stem' target, use the configured
2590 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
2592 - When running the zero-length-keys tests, do not use the default
2593 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
2596 o Directory authority IP change:
2597 - The directory authority Faravahar has a new IP address. This
2598 closes ticket 14487.
2601 - Remove some lingering dead code that once supported mempools.
2602 Mempools were disabled by default in 0.2.5, and removed entirely
2603 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
2607 Changes in version 0.2.6.3-alpha - 2015-02-19
2608 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
2609 the 0.2.6.x series. It introduces support for more kinds of sockets,
2610 makes it harder to accidentally run an exit, improves our
2611 multithreading backend, incorporates several fixes for the
2612 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
2614 If no major regressions or security holes are found in this version,
2615 the next version will be a release candidate.
2617 o Deprecated versions:
2618 - Tor relays older than 0.2.4.18-rc are no longer allowed to
2619 advertise themselves on the network. Closes ticket 13555.
2621 o Major features (security, unix domain sockets):
2622 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
2623 applications can reach Tor without having to create AF_INET or
2624 AF_INET6 sockets, meaning they can completely disable their
2625 ability to make non-Tor network connections. To create a socket of
2626 this type, use "SocksPort unix:/path/to/socket". Implements
2628 - Support mapping hidden service virtual ports to AF_UNIX sockets.
2629 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
2630 Implements ticket 11485.
2632 o Major features (changed defaults):
2633 - Prevent relay operators from unintentionally running exits: When a
2634 relay is configured as an exit node, we now warn the user unless
2635 the "ExitRelay" option is set to 1. We warn even more loudly if
2636 the relay is configured with the default exit policy, since this
2637 can indicate accidental misconfiguration. Setting "ExitRelay 0"
2638 stops Tor from running as an exit relay. Closes ticket 10067.
2640 o Major features (directory system):
2641 - When downloading server- or microdescriptors from a directory
2642 server, we no longer launch multiple simultaneous requests to the
2643 same server. This reduces load on the directory servers,
2644 especially when directory guards are in use. Closes ticket 9969.
2645 - When downloading server- or microdescriptors over a tunneled
2646 connection, do not limit the length of our requests to what the
2647 Squid proxy is willing to handle. Part of ticket 9969.
2648 - Authorities can now vote on the correct digests and latest
2649 versions for different software packages. This allows packages
2650 that include Tor to use the Tor authority system as a way to get
2651 notified of updates and their correct digests. Implements proposal
2652 227. Closes ticket 10395.
2654 o Major features (guards):
2655 - Introduce the Guardfraction feature to improves load balancing on
2656 guard nodes. Specifically, it aims to reduce the traffic gap that
2657 guard nodes experience when they first get the Guard flag. This is
2658 a required step if we want to increase the guard lifetime to 9
2659 months or greater. Closes ticket 9321.
2661 o Major features (performance):
2662 - Make the CPU worker implementation more efficient by avoiding the
2663 kernel and lengthening pipelines. The original implementation used
2664 sockets to transfer data from the main thread to the workers, and
2665 didn't allow any thread to be assigned more than a single piece of
2666 work at once. The new implementation avoids communications
2667 overhead by making requests in shared memory, avoiding kernel IO
2668 where possible, and keeping more requests in flight at once.
2669 Implements ticket 9682.
2671 o Major features (relay):
2672 - Raise the minimum acceptable configured bandwidth rate for bridges
2673 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
2674 20 KiB/sec.) Closes ticket 13822.
2676 o Major bugfixes (exit node stability):
2677 - Fix an assertion failure that could occur under high DNS load.
2678 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2679 diagnosed and fixed by "cypherpunks".
2681 o Major bugfixes (mixed relay-client operation):
2682 - When running as a relay and client at the same time (not
2683 recommended), if we decide not to use a new guard because we want
2684 to retry older guards, only close the locally-originating circuits
2685 passing through that guard. Previously we would close all the
2686 circuits through that guard. Fixes bug 9819; bugfix on
2687 0.2.1.1-alpha. Reported by "skruffy".
2689 o Minor features (build):
2690 - New --disable-system-torrc compile-time option to prevent Tor from
2691 looking for the system-wide torrc or torrc-defaults files.
2692 Resolves ticket 13037.
2694 o Minor features (controller):
2695 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
2696 events so controllers can observe circuit isolation inputs. Closes
2698 - ControlPort now supports the unix:/path/to/socket syntax as an
2699 alternative to the ControlSocket option, for consistency with
2700 SocksPort and HiddenServicePort. Closes ticket 14451.
2701 - New "GETINFO bw-event-cache" to get information about recent
2702 bandwidth events. Closes ticket 14128. Useful for controllers to
2703 get recent bandwidth history after the fix for ticket 13988.
2705 o Minor features (Denial of service resistance):
2706 - Count the total number of bytes used storing hidden service
2707 descriptors against the value of MaxMemInQueues. If we're low on
2708 memory, and more than 20% of our memory is used holding hidden
2709 service descriptors, free them until no more than 10% of our
2710 memory holds hidden service descriptors. Free the least recently
2711 fetched descriptors first. Resolves ticket 13806.
2712 - When we have recently been under memory pressure (over 3/4 of
2713 MaxMemInQueues is allocated), then allocate smaller zlib objects
2714 for small requests. Closes ticket 11791.
2716 o Minor features (geoip):
2717 - Update geoip and geoip6 files to the January 7 2015 Maxmind
2718 GeoLite2 Country database.
2720 o Minor features (guard nodes):
2721 - Reduce the time delay before saving guard status to disk from 10
2722 minutes to 30 seconds (or from one hour to 10 minutes if
2723 AvoidDiskWrites is set). Closes ticket 12485.
2725 o Minor features (hidden service):
2726 - Make Sybil attacks against hidden services harder by changing the
2727 minimum time required to get the HSDir flag from 25 hours up to 96
2728 hours. Addresses ticket 14149.
2729 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
2730 services to disable the anti-scanning feature introduced in
2731 0.2.6.2-alpha. With this option not set, a connection to an
2732 unlisted port closes the circuit. With this option set, only a
2733 RELAY_DONE cell is sent. Closes ticket 14084.
2735 o Minor features (interface):
2736 - Implement "-f -" command-line option to read torrc configuration
2737 from standard input, if you don't want to store the torrc file in
2738 the file system. Implements feature 13865.
2740 o Minor features (logging):
2741 - Add a count of unique clients to the bridge heartbeat message.
2742 Resolves ticket 6852.
2743 - Suppress "router info incompatible with extra info" message when
2744 reading extrainfo documents from cache. (This message got loud
2745 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
2747 - Elevate hidden service authorized-client message from DEBUG to
2748 INFO. Closes ticket 14015.
2750 o Minor features (stability):
2751 - Add assertions in our hash-table iteration code to check for
2752 corrupted values that could cause infinite loops. Closes
2755 o Minor features (systemd):
2756 - Various improvements and modernizations in systemd hardening
2757 support. Closes ticket 13805. Patch from Craig Andrews.
2759 o Minor features (testing networks):
2760 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
2761 and the default on a testing network to 2 minutes. Drop the
2762 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
2763 keep the default on a testing network at 30 seconds. This reduces
2764 HS bootstrap time to around 25 seconds. Also, change the default
2765 time in test-network.sh to match. Closes ticket 13401. Patch
2767 - Create TestingDirAuthVoteHSDir to correspond to
2768 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
2769 HSDir flag for the listed relays regardless of uptime or ORPort
2770 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
2771 Partial implementation for ticket 14067. Patch by "teor".
2773 o Minor features (tor2web mode):
2774 - Introduce the config option Tor2webRendezvousPoints, which allows
2775 clients in Tor2webMode to select a specific Rendezvous Point to be
2776 used in HS circuits. This might allow better performance for
2777 Tor2Web nodes. Implements ticket 12844.
2779 o Minor bugfixes (client DNS):
2780 - Report the correct cached DNS expiration times on SOCKS port or in
2781 DNS replies. Previously, we would report everything as "never
2782 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
2783 - Avoid a small memory leak when we find a cached answer for a
2784 reverse DNS lookup in a client-side DNS cache. (Remember, client-
2785 side DNS caching is off by default, and is not recommended.) Fixes
2786 bug 14259; bugfix on 0.2.0.1-alpha.
2788 o Minor bugfixes (client, automapping):
2789 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
2790 no value follows the option. Fixes bug 14142; bugfix on
2791 0.2.4.7-alpha. Patch by "teor".
2792 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
2793 14195; bugfix on 0.1.0.1-rc.
2794 - Prevent changes to other options from removing the wildcard value
2795 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
2797 - Allow MapAddress and AutomapHostsOnResolve to work together when
2798 an address is mapped into another address type (like .onion) that
2799 must be automapped at resolve time. Fixes bug 7555; bugfix
2802 o Minor bugfixes (client, bridges):
2803 - When we are using bridges and we had a network connectivity
2804 problem, only retry connecting to our currently configured
2805 bridges, not all bridges we know about and remember using. Fixes
2806 bug 14216; bugfix on 0.2.2.17-alpha.
2808 o Minor bugfixes (client, IPv6):
2809 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
2810 flag is not set; and not because the NoIPv4Traffic flag was set.
2811 Previously we'd looked at the NoIPv4Traffic flag for both types of
2812 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
2814 o Minor bugfixes (compilation):
2815 - The address of an array in the middle of a structure will always
2816 be non-NULL. clang recognises this and complains. Disable the
2817 tautologous and redundant check to silence this warning. Fixes bug
2818 14001; bugfix on 0.2.1.2-alpha.
2819 - Avoid warnings when building with systemd 209 or later. Fixes bug
2820 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
2821 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
2822 Addresses ticket 14188.
2823 - Build without warnings with the stock OpenSSL srtp.h header, which
2824 has a duplicate declaration of SSL_get_selected_srtp_profile().
2825 Fixes bug 14220; this is OpenSSL's bug, not ours.
2826 - Do not compile any code related to Tor2Web mode when Tor2Web mode
2827 is not enabled at compile time. Previously, this code was included
2828 in a disabled state. See discussion on ticket 12844.
2829 - Remove the --disable-threads configure option again. It was
2830 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
2831 14819; bugfix on 0.2.6.2-alpha.
2833 o Minor bugfixes (controller):
2834 - Report "down" in response to the "GETINFO entry-guards" command
2835 when relays are down with an unreachable_since value. Previously,
2836 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
2837 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
2838 14116; bugfix on 0.2.2.9-alpha.
2839 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
2840 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
2842 o Minor bugfixes (directory authority):
2843 - Allow directory authorities to fetch more data from one another if
2844 they find themselves missing lots of votes. Previously, they had
2845 been bumping against the 10 MB queued data limit. Fixes bug 14261;
2846 bugfix on 0.1.2.5-alpha.
2847 - Do not attempt to download extrainfo documents which we will be
2848 unable to validate with a matching server descriptor. Fixes bug
2849 13762; bugfix on 0.2.0.1-alpha.
2850 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
2851 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
2852 - Enlarge the buffer to read bwauth generated files to avoid an
2853 issue when parsing the file in dirserv_read_measured_bandwidths().
2854 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
2856 o Minor bugfixes (file handling):
2857 - Stop failing when key files are zero-length. Instead, generate new
2858 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
2859 on all versions of Tor. Patch by "teor".
2860 - Stop generating a fresh .old RSA onion key file when the .old file
2861 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
2862 - Avoid overwriting .old key files with empty key files.
2863 - Skip loading zero-length extrainfo store, router store, stats,
2864 state, and key files.
2865 - Avoid crashing when trying to reload a torrc specified as a
2866 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
2869 o Minor bugfixes (hidden services):
2870 - Close the introduction circuit when we have no more usable intro
2871 points, instead of waiting for it to time out. This also ensures
2872 that no follow-up HS descriptor fetch is triggered when the
2873 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
2874 - When fetching a hidden service descriptor for a down service that
2875 was recently up, do not keep refetching until we try the same
2876 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
2877 - Successfully launch Tor with a nonexistent hidden service
2878 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
2879 14106; bugfix on 0.2.6.2-alpha.
2881 o Minor bugfixes (logging):
2882 - Avoid crashing when there are more log domains than entries in
2883 domain_list. Bugfix on 0.2.3.1-alpha.
2884 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
2886 - Don't log messages to stdout twice when starting up. Fixes bug
2887 13993; bugfix on 0.2.6.1-alpha.
2889 o Minor bugfixes (parsing):
2890 - Stop accepting milliseconds (or other junk) at the end of
2891 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
2892 - Support two-number and three-number version numbers correctly, in
2893 case we change the Tor versioning system in the future. Fixes bug
2894 13661; bugfix on 0.0.8pre1.
2896 o Minor bugfixes (path counting):
2897 - When deciding whether the consensus lists any exit nodes, count
2898 the number listed in the consensus, not the number we have
2899 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
2900 - When deciding whether we have any exit nodes, only examine
2901 ExitNodes when the ExitNodes option is actually set. Fixes part of
2902 bug 14918; bugfix on 0.2.6.2-alpha.
2903 - Get rid of redundant and possibly scary warnings that we are
2904 missing directory information while we bootstrap. Fixes part of
2905 bug 14918; bugfix on 0.2.6.2-alpha.
2907 o Minor bugfixes (portability):
2908 - Fix the ioctl()-based network interface lookup code so that it
2909 will work on systems that have variable-length struct ifreq, for
2911 - Fix scheduler compilation on targets where char is unsigned. Fixes
2912 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
2914 o Minor bugfixes (sandbox):
2915 - Allow glibc fatal errors to be sent to stderr before Tor exits.
2916 Previously, glibc would try to write them to /dev/tty, and the
2917 sandbox would trap the call and make Tor exit prematurely. Fixes
2918 bug 14759; bugfix on 0.2.5.1-alpha.
2920 o Minor bugfixes (shutdown):
2921 - When shutting down, always call event_del() on lingering read or
2922 write events before freeing them. Otherwise, we risk double-frees
2923 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
2926 o Minor bugfixes (small memory leaks):
2927 - Avoid leaking memory when using IPv6 virtual address mappings.
2928 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
2931 o Minor bugfixes (statistics):
2932 - Increase period over which bandwidth observations are aggregated
2933 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
2935 o Minor bugfixes (systemd support):
2936 - Fix detection and operation of systemd watchdog. Fixes part of bug
2937 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
2938 - Run correctly under systemd with the RunAsDaemon option set. Fixes
2939 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
2940 - Inform the systemd supervisor about more changes in the Tor
2941 process status. Implements part of ticket 14141. Patch from
2943 - Cause the "--disable-systemd" option to actually disable systemd
2944 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
2947 o Minor bugfixes (TLS):
2948 - Check more thoroughly throughout the TLS code for possible
2949 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
2951 o Minor bugfixes (transparent proxy):
2952 - Use getsockname, not getsockopt, to retrieve the address for a
2953 TPROXY-redirected connection. Fixes bug 13796; bugfix
2956 o Code simplification and refactoring:
2957 - Move fields related to isolating and configuring client ports into
2958 a shared structure. Previously, they were duplicated across
2959 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
2960 to copy them correctly had been the cause of at least one bug in
2961 the past. Closes ticket 8546.
2962 - Refactor the get_interface_addresses_raw() doom-function into
2963 multiple smaller and simpler subfunctions. Cover the resulting
2964 subfunctions with unit-tests. Fixes a significant portion of
2966 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
2967 only for version <= 0.2.2.24 which is now deprecated. Closes
2969 - Remove a test for a long-defunct broken version-one
2973 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
2974 for writing the OpenBSD-specific tips. Resolves ticket 13702.
2975 - Make the tor-resolve documentation match its help string and its
2976 options. Resolves part of ticket 14325.
2977 - Log a more useful error message from tor-resolve when failing to
2978 look up a hidden service address. Resolves part of ticket 14325.
2980 o Downgraded warnings:
2981 - Don't warn when we've attempted to contact a relay using the wrong
2982 ntor onion key. Closes ticket 9635.
2985 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
2986 longer silently accepted as an alias for "ExitNodes".
2987 - The --enable-mempool and --enable-buf-freelists options, which
2988 were originally created to work around bad malloc implementations,
2989 no longer exist. They were off-by-default in 0.2.5. Closes
2993 - Make the checkdir/perms test complete successfully even if the
2994 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
2995 - Test that tor does not fail when key files are zero-length. Check
2996 that tor generates new keys, and overwrites the empty key files.
2997 - Test that tor generates new keys when keys are missing
2998 (existing behavior).
2999 - Test that tor does not overwrite key files that already contain
3000 data (existing behavior). Tests bug 13111. Patch by "teor".
3001 - New "make test-stem" target to run stem integration tests.
3002 Requires that the "STEM_SOURCE_DIR" environment variable be set.
3003 Closes ticket 14107.
3004 - Make the test_cmdline_args.py script work correctly on Windows.
3005 Patch from Gisle Vanem.
3006 - Move the slower unit tests into a new "./src/test/test-slow"
3007 binary that can be run independently of the other tests. Closes
3009 - Avoid undefined behavior when sampling huge values from the
3010 Laplace distribution. This made unittests fail on Raspberry Pi.
3011 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
3014 Changes in version 0.2.6.2-alpha - 2014-12-31
3015 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
3016 It introduces a major new backend for deciding when to send cells on
3017 channels, which should lead down the road to big performance
3018 increases. It contains security and statistics features for better
3019 work on hidden services, and numerous bugfixes.
3021 This release contains many new unit tests, along with major
3022 performance improvements for running testing networks using Chutney.
3023 Thanks to a series of patches contributed by "teor", testing networks
3024 should now bootstrap in seconds, rather than minutes.
3026 o Major features (relay, infrastructure):
3027 - Complete revision of the code that relays use to decide which cell
3028 to send next. Formerly, we selected the best circuit to write on
3029 each channel, but we didn't select among channels in any
3030 sophisticated way. Now, we choose the best circuits globally from
3031 among those whose channels are ready to deliver traffic.
3033 This patch implements a new inter-cmux comparison API, a global
3034 high/low watermark mechanism and a global scheduler loop for
3035 transmission prioritization across all channels as well as among
3036 circuits on one channel. This schedule is currently tuned to
3037 (tolerantly) avoid making changes in network performance, but it
3038 should form the basis for major circuit performance increases in
3039 the future. Code by Andrea; tuning by Rob Jansen; implements
3042 o Major features (hidden services):
3043 - Make HS port scanning more difficult by immediately closing the
3044 circuit when a user attempts to connect to a nonexistent port.
3045 Closes ticket 13667.
3046 - Add a HiddenServiceStatistics option that allows Tor relays to
3047 gather and publish statistics about the overall size and volume of
3048 hidden service usage. Specifically, when this option is turned on,
3049 an HSDir will publish an approximate number of hidden services
3050 that have published descriptors to it the past 24 hours. Also, if
3051 a relay has acted as a hidden service rendezvous point, it will
3052 publish the approximate amount of rendezvous cells it has relayed
3053 the past 24 hours. The statistics themselves are obfuscated so
3054 that the exact values cannot be derived. For more details see
3055 proposal 238, "Better hidden service stats from Tor relays". This
3056 feature is currently disabled by default. Implements feature 13192.
3058 o Major bugfixes (client, automap):
3059 - Repair automapping with IPv6 addresses. This automapping should
3060 have worked previously, but one piece of debugging code that we
3061 inserted to detect a regression actually caused the regression to
3062 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
3063 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
3066 o Major bugfixes (hidden services):
3067 - When closing an introduction circuit that was opened in parallel
3068 with others, don't mark the introduction point as unreachable.
3069 Previously, the first successful connection to an introduction
3070 point would make the other introduction points get marked as
3071 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
3073 o Directory authority changes:
3074 - Remove turtles as a directory authority.
3075 - Add longclaw as a new (v3) directory authority. This implements
3076 ticket 13296. This keeps the directory authority count at 9.
3078 o Major removed features:
3079 - Tor clients no longer support connecting to hidden services
3080 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
3081 option has been removed. (There shouldn't be any hidden services
3082 running these versions on the network.) Closes ticket 7803.
3084 o Minor features (client):
3085 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
3086 is enabled, reject requests with IP addresses as hostnames.
3087 Resolves ticket 13315.
3089 o Minor features (controller):
3090 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
3091 write an unscheduled heartbeat message to the log. Implements
3094 o Minor features (geoip):
3095 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
3098 o Minor features (hidden services):
3099 - When re-enabling the network, don't try to build introduction
3100 circuits until we have successfully built a circuit. This makes
3101 hidden services come up faster when the network is re-enabled.
3102 Patch from "akwizgran". Closes ticket 13447.
3103 - When we fail to retrieve a hidden service descriptor, send the
3104 controller an "HS_DESC FAILED" controller event. Implements
3106 - New HiddenServiceDirGroupReadable option to cause hidden service
3107 directories and hostname files to be created group-readable. Patch
3108 from "anon", David Stainton, and "meejah". Closes ticket 11291.
3110 o Minor features (systemd):
3111 - Where supported, when running with systemd, report successful
3112 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
3113 - When running with systemd, support systemd watchdog messages. Part
3114 of ticket 11016. Patch by Michael Scherer.
3116 o Minor features (transparent proxy):
3117 - Update the transparent proxy option checks to allow for both ipfw
3118 and pf on OS X. Closes ticket 14002.
3119 - Use the correct option when using IPv6 with transparent proxy
3120 support on Linux. Resolves 13808. Patch by Francisco Blas
3123 o Minor bugfixes (preventative security, C safety):
3124 - When reading a hexadecimal, base-32, or base-64 encoded value from
3125 a string, always overwrite the whole output buffer. This prevents
3126 some bugs where we would look at (but fortunately, not reveal)
3127 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
3129 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
3130 just the part that's used. This makes it harder for data leak bugs
3131 to occur in the event of other programming failures. Resolves
3134 o Minor bugfixes (client, microdescriptors):
3135 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
3136 computing which microdescriptors to download. This keeps us from
3137 erroneous download behavior if two microdescriptor digests ever
3138 have the same first 160 bits. Fixes part of bug 13399; bugfix
3140 - Reset a router's status if its microdescriptor digest changes,
3141 even if the first 160 bits remain the same. Fixes part of bug
3142 13399; bugfix on 0.2.3.1-alpha.
3144 o Minor bugfixes (compilation):
3145 - Silence clang warnings under --enable-expensive-hardening,
3146 including implicit truncation of 64 bit values to 32 bit, const
3147 char assignment to self, tautological compare, and additional
3148 parentheses around equality tests. Fixes bug 13577; bugfix
3150 - Fix a clang warning about checking whether an address in the
3151 middle of a structure is NULL. Fixes bug 14001; bugfix
3154 o Minor bugfixes (hidden services):
3155 - Correctly send a controller event when we find that a rendezvous
3156 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
3157 - Pre-check directory permissions for new hidden-services to avoid
3158 at least one case of "Bug: Acting on config options left us in a
3159 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
3160 - When adding a new hidden service (for example, via SETCONF), Tor
3161 no longer congratulates the user for running a relay. Fixes bug
3162 13941; bugfix on 0.2.6.1-alpha.
3163 - When fetching hidden service descriptors, we now check not only
3164 for whether we got the hidden service we had in mind, but also
3165 whether we got the particular descriptors we wanted. This prevents
3166 a class of inefficient but annoying DoS attacks by hidden service
3167 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
3170 o Minor bugfixes (Linux seccomp2 sandbox):
3171 - Make transparent proxy support work along with the seccomp2
3172 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
3173 by Francisco Blas Izquierdo Riera.
3174 - Fix a memory leak in tor-resolve when running with the sandbox
3175 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
3177 o Minor bugfixes (logging):
3178 - Downgrade warnings about RSA signature failures to info log level.
3179 Emit a warning when an extra info document is found incompatible
3180 with a corresponding router descriptor. Fixes bug 9812; bugfix
3182 - Make connection_ap_handshake_attach_circuit() log the circuit ID
3183 correctly. Fixes bug 13701; bugfix on 0.0.6.
3185 o Minor bugfixes (misc):
3186 - Stop allowing invalid address patterns like "*/24" that contain
3187 both a wildcard address and a bit prefix length. This affects all
3188 our address-range parsing code. Fixes bug 7484; bugfix
3191 o Minor bugfixes (testing networks, fast startup):
3192 - Allow Tor to build circuits using a consensus with no exits. If
3193 the consensus has no exits (typical of a bootstrapping test
3194 network), allow Tor to build circuits once enough descriptors have
3195 been downloaded. This assists in bootstrapping a testing Tor
3196 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
3198 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
3199 header to directory servers. This allows us to obtain consensuses
3200 promptly when the consensus interval is very short. This assists
3201 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
3202 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
3203 - Stop assuming that private addresses are local when checking
3204 reachability in a TestingTorNetwork. Instead, when testing, assume
3205 all OR connections are remote. (This is necessary due to many test
3206 scenarios running all relays on localhost.) This assists in
3207 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
3208 0.1.0.1-rc. Patch by "teor".
3209 - Avoid building exit circuits from a consensus with no exits. Now
3210 thanks to our fix for 13718, we accept a no-exit network as not
3211 wholly lost, but we need to remember not to try to build exit
3212 circuits on it. Closes ticket 13814; patch by "teor".
3213 - Stop requiring exits to have non-zero bandwithcapacity in a
3214 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
3215 ignore exit bandwidthcapacity. This assists in bootstrapping a
3216 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
3217 on 0.2.0.3-alpha. Patch by "teor".
3218 - Add "internal" to some bootstrap statuses when no exits are
3219 available. If the consensus does not contain Exits, Tor will only
3220 build internal circuits. In this case, relevant statuses will
3221 contain the word "internal" as indicated in the Tor control-
3222 spec.txt. When bootstrap completes, Tor will be ready to build
3223 internal circuits. If a future consensus contains Exits, exit
3224 circuits may become available. Fixes part of bug 13718; bugfix on
3225 0.2.4.10-alpha. Patch by "teor".
3226 - Decrease minimum consensus interval to 10 seconds when
3227 TestingTorNetwork is set, or 5 seconds for the first consensus.
3228 Fix assumptions throughout the code that assume larger intervals.
3229 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
3231 - Avoid excluding guards from path building in minimal test
3232 networks, when we're in a test network and excluding guards would
3233 exclude all relays. This typically occurs in incredibly small tor
3234 networks, and those using "TestingAuthVoteGuard *". Fixes part of
3235 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
3237 o Code simplification and refactoring:
3238 - Stop using can_complete_circuits as a global variable; access it
3239 with a function instead.
3240 - Avoid using operators directly as macro arguments: this lets us
3241 apply coccinelle transformations to our codebase more directly.
3242 Closes ticket 13172.
3243 - Combine the functions used to parse ClientTransportPlugin and
3244 ServerTransportPlugin into a single function. Closes ticket 6456.
3245 - Add inline functions and convenience macros for inspecting channel
3246 state. Refactor the code to use convenience macros instead of
3247 checking channel state directly. Fixes issue 7356.
3248 - Document all members of was_router_added_t and rename
3249 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
3250 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
3251 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
3252 constant instead of hardcoded value. Fixes issue 13840.
3253 - Refactor our generic strmap and digestmap types into a single
3254 implementation, so that we can add a new digest256map
3258 - Document the bridge-authority-only 'networkstatus-bridges' file.
3259 Closes ticket 13713; patch from "tom".
3260 - Fix typo in PredictedPortsRelevanceTime option description in
3261 manpage. Resolves issue 13707.
3262 - Stop suggesting that users specify relays by nickname: it isn't a
3263 good idea. Also, properly cross-reference how to specify relays in
3264 all parts of manual documenting options that take a list of
3265 relays. Closes ticket 13381.
3266 - Clarify the HiddenServiceDir option description in manpage to make
3267 it clear that relative paths are taken with respect to the current
3268 working directory. Also clarify that this behavior is not
3269 guaranteed to remain indefinitely. Fixes issue 13913.
3272 - New tests for many parts of channel, relay, and circuitmux
3273 functionality. Code by Andrea; part of 9262.
3274 - New tests for parse_transport_line(). Part of ticket 6456.
3275 - In the unit tests, use chgrp() to change the group of the unit
3276 test temporary directory to the current user, so that the sticky
3277 bit doesn't interfere with tests that check directory groups.
3279 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
3283 Changes in version 0.2.6.1-alpha - 2014-10-30
3284 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
3285 includes numerous code cleanups and new tests, and fixes a large
3286 number of annoying bugs. Out-of-memory conditions are handled better
3287 than in 0.2.5, pluggable transports have improved proxy support, and
3288 clients now use optimistic data for contacting hidden services. Also,
3289 we are now more robust to changes in what we consider a parseable
3290 directory object, so that tightening restrictions does not have a risk
3291 of introducing infinite download loops.
3293 This is the first alpha release in a new series, so expect there to be
3294 bugs. Users who would rather test out a more stable branch should stay
3295 with 0.2.5.x for now.
3297 o New compiler and system requirements:
3298 - Tor 0.2.6.x requires that your compiler support more of the C99
3299 language standard than before. The 'configure' script now detects
3300 whether your compiler supports C99 mid-block declarations and
3301 designated initializers. If it does not, Tor will not compile.
3303 We may revisit this requirement if it turns out that a significant
3304 number of people need to build Tor with compilers that don't
3305 bother implementing a 15-year-old standard. Closes ticket 13233.
3306 - Tor no longer supports systems without threading support. When we
3307 began working on Tor, there were several systems that didn't have
3308 threads, or where the thread support wasn't able to run the
3309 threads of a single process on multiple CPUs. That no longer
3310 holds: every system where Tor needs to run well now has threading
3311 support. Resolves ticket 12439.
3313 o Removed platform support:
3314 - We no longer include special code to build on Windows CE; as far
3315 as we know, nobody has used Tor on Windows CE in a very long time.
3316 Closes ticket 11446.
3318 o Major features (bridges):
3319 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
3320 transports if they are configured via the "TOR_PT_PROXY"
3321 environment variable. Implements proposal 232. Resolves
3324 o Major features (client performance, hidden services):
3325 - Allow clients to use optimistic data when connecting to a hidden
3326 service, which should remove a round-trip from hidden service
3327 initialization. See proposal 181 for details. Implements
3330 o Major features (directory system):
3331 - Upon receiving an unparseable directory object, if its digest
3332 matches what we expected, then don't try to download it again.
3333 Previously, when we got a descriptor we didn't like, we would keep
3334 trying to download it over and over. Closes ticket 11243.
3336 o Major features (sample torrc):
3337 - Add a new, infrequently-changed "torrc.minimal". This file is
3338 similar to torrc.sample, but it will change as infrequently as
3339 possible, for the benefit of users whose systems prompt them for
3340 intervention whenever a default configuration file is changed.
3341 Making this change allows us to update torrc.sample to be a more
3342 generally useful "sample torrc".
3344 o Major bugfixes (directory authorities):
3345 - Do not assign the HSDir flag to relays if they are not Valid, or
3346 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
3348 o Major bugfixes (directory bandwidth performance):
3349 - Don't flush the zlib buffer aggressively when compressing
3350 directory information for clients. This should save about 7% of
3351 the bandwidth currently used for compressed descriptors and
3352 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
3354 o Minor features (security, memory wiping):
3355 - Ensure we securely wipe keys from memory after
3356 crypto_digest_get_digest and init_curve25519_keypair_from_file
3357 have finished using them. Resolves ticket 13477.
3359 o Minor features (security, out-of-memory handling):
3360 - When handling an out-of-memory condition, allocate less memory for
3361 temporary data structures. Fixes issue 10115.
3362 - When handling an out-of-memory condition, consider more types of
3363 buffers, including those on directory connections, and zlib
3364 buffers. Resolves ticket 11792.
3367 - When identity keypair is generated for first time, log a
3368 congratulatory message that links to the new relay lifecycle
3369 document. Implements feature 10427.
3371 o Minor features (client):
3372 - Clients are now willing to send optimistic data (before they
3373 receive a 'connected' cell) to relays of any version. (Relays
3374 without support for optimistic data are no longer supported on the
3375 Tor network.) Resolves ticket 13153.
3377 o Minor features (directory authorities):
3378 - Don't list relays with a bandwidth estimate of 0 in the consensus.
3379 Implements a feature proposed during discussion of bug 13000.
3380 - In tor-gencert, report an error if the user provides the same
3381 argument more than once.
3382 - If a directory authority can't find a best consensus method in the
3383 votes that it holds, it now falls back to its favorite consensus
3384 method. Previously, it fell back to method 1. Neither of these is
3385 likely to get enough signatures, but "fall back to favorite"
3386 doesn't require us to maintain support an obsolete consensus
3387 method. Implements part of proposal 215.
3389 o Minor features (logging):
3390 - On Unix-like systems, you can now use named pipes as the target of
3391 the Log option, and other options that try to append to files.
3392 Closes ticket 12061. Patch from "carlo von lynX".
3393 - When opening a log file at startup, send it every log message that
3394 we generated between startup and opening it. Previously, log
3395 messages that were generated before opening the log file were only
3396 logged to stdout. Closes ticket 6938.
3397 - Add a TruncateLogFile option to overwrite logs instead of
3398 appending to them. Closes ticket 5583.
3400 o Minor features (portability, Solaris):
3401 - Threads are no longer disabled by default on Solaris; we believe
3402 that the versions of Solaris with broken threading support are all
3403 obsolete by now. Resolves ticket 9495.
3405 o Minor features (relay):
3406 - Re-check our address after we detect a changed IP address from
3407 getsockname(). This ensures that the controller command "GETINFO
3408 address" will report the correct value. Resolves ticket 11582.
3410 - A new AccountingRule option lets Relays set whether they'd like
3411 AccountingMax to be applied separately to inbound and outbound
3412 traffic, or applied to the sum of inbound and outbound traffic.
3413 Resolves ticket 961. Patch by "chobe".
3415 o Minor features (testing networks):
3416 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
3417 the "Exit" flag regardless of their uptime, bandwidth, or exit
3418 policy. TestingTorNetwork must be set for this option to have any
3419 effect. Previously, authorities would take up to 35 minutes to
3420 give nodes the Exit flag in a test network. Partially implements
3423 o Minor features (validation):
3424 - Check all date/time values passed to tor_timegm and
3425 parse_rfc1123_time for validity, taking leap years into account.
3426 Improves HTTP header validation. Implemented with bug 13476.
3427 - In correct_tm(), limit the range of values returned by system
3428 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
3429 This means we don't have to deal with negative or too large dates,
3430 even if a clock is wrong. Otherwise we might fail to read a file
3431 written by us which includes such a date. Fixes bug 13476.
3433 o Minor bugfixes (bridge clients):
3434 - When configured to use a bridge without an identity digest (not
3435 recommended), avoid launching an extra channel to it when
3436 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
3438 o Minor bugfixes (bridges):
3439 - When DisableNetwork is set, do not launch pluggable transport
3440 plugins, and if any are running, terminate them. Fixes bug 13213;
3441 bugfix on 0.2.3.6-alpha.
3443 o Minor bugfixes (C correctness):
3444 - Fix several instances of possible integer overflow/underflow/NaN.
3445 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
3447 - In circuit_build_times_calculate_timeout() in circuitstats.c,
3448 avoid dividing by zero in the pareto calculations. This traps
3449 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
3451 - Fix an integer overflow in format_time_interval(). Fixes bug
3452 13393; bugfix on 0.2.0.10-alpha.
3453 - Set the correct day of year value when the system's localtime(_r)
3454 or gmtime(_r) functions fail to set struct tm. Not externally
3455 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
3456 - Avoid unlikely signed integer overflow in tor_timegm on systems
3457 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
3459 o Minor bugfixes (client):
3460 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
3461 BadExit flag are not considered worthy candidates. Fixes bug
3462 13066; bugfix on 0.1.2.3-alpha.
3463 - Use the consensus schedule for downloading consensuses, and not
3464 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
3465 - Handle unsupported or malformed SOCKS5 requests properly by
3466 responding with the appropriate error message before closing the
3467 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
3469 o Minor bugfixes (client, torrc):
3470 - Stop modifying the value of our DirReqStatistics torrc option just
3471 because we're not a bridge or relay. This bug was causing Tor
3472 Browser users to write "DirReqStatistics 0" in their torrc files
3473 as if they had chosen to change the config. Fixes bug 4244; bugfix
3475 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
3476 that our options have changed every time we SIGHUP. Fixes bug
3477 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
3479 o Minor bugfixes (controller):
3480 - Return an error when the second or later arguments of the
3481 "setevents" controller command are invalid events. Previously we
3482 would return success while silently skipping invalid events. Fixes
3483 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
3485 o Minor bugfixes (directory system):
3486 - Always believe that v3 directory authorities serve extra-info
3487 documents, whether they advertise "caches-extra-info" or not.
3488 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
3489 - When running as a v3 directory authority, advertise that you serve
3490 extra-info documents so that clients who want them can find them
3491 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
3492 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
3493 Previously, directories offering BRIDGE_DIRINFO and some other
3494 flag (i.e. microdescriptors or extrainfo) would be ignored when
3495 looking for bridges. Partially fixes bug 13163; bugfix
3498 o Minor bugfixes (networking):
3499 - Check for orconns and use connection_or_close_for_error() rather
3500 than connection_mark_for_close() directly in the getsockopt()
3501 failure case of connection_handle_write_impl(). Fixes bug 11302;
3502 bugfix on 0.2.4.4-alpha.
3504 o Minor bugfixes (relay):
3505 - When generating our family list, remove spaces from around the
3506 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
3507 - If our previous bandwidth estimate was 0 bytes, allow publishing a
3508 new relay descriptor immediately. Fixes bug 13000; bugfix
3511 o Minor bugfixes (testing networks):
3512 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
3513 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
3514 - Stop using the default authorities in networks which provide both
3515 AlternateDirAuthority and AlternateBridgeAuthority. Partially
3516 fixes bug 13163; bugfix on 0.2.0.13-alpha.
3518 o Minor bugfixes (testing):
3519 - Stop spawn test failures due to a race condition between the
3520 SIGCHLD handler updating the process status, and the test reading
3521 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
3523 o Minor bugfixes (testing, Windows):
3524 - Avoid passing an extra backslash when creating a temporary
3525 directory for running the unit tests on Windows. Fixes bug 12392;
3526 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
3528 o Minor bugfixes (windows):
3529 - Remove code to special-case handling of NTE_BAD_KEYSET when
3530 acquiring windows CryptoAPI context. This error can't actually
3531 occur for the parameters we're providing. Fixes bug 10816; bugfix
3534 o Minor bugfixes (zlib):
3535 - Avoid truncating a zlib stream when trying to finalize it with an
3536 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
3539 - Allow our configure script to build correctly with autoconf 2.62
3540 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
3541 - Improve the error message from ./configure to make it clear that
3542 when asciidoc has not been found, the user will have to either add
3543 --disable-asciidoc argument or install asciidoc. Resolves
3546 o Code simplification and refactoring:
3547 - Change the entry_is_live() function to take named bitfield
3548 elements instead of an unnamed list of booleans. Closes
3550 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
3551 Resolves ticket 12205.
3552 - Use calloc and reallocarray functions instead of multiply-
3553 then-malloc. This makes it less likely for us to fall victim to an
3554 integer overflow attack when allocating. Resolves ticket 12855.
3555 - Use the standard macro name SIZE_MAX, instead of our
3557 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
3558 functions which take them as arguments. Replace 0 with NO_DIRINFO
3559 in a function call for clarity. Seeks to prevent future issues
3561 - Avoid 4 null pointer errors under clang static analysis by using
3562 tor_assert() to prove that the pointers aren't null. Fixes
3564 - Rework the API of policies_parse_exit_policy() to use a bitmask to
3565 represent parsing options, instead of a confusing mess of
3566 booleans. Resolves ticket 8197.
3567 - Introduce a helper function to parse ExitPolicy in
3568 or_options_t structure.
3571 - Add a doc/TUNING document with tips for handling large numbers of
3572 TCP connections when running busy Tor relay. Update the warning
3573 message to point to this file when running out of sockets
3574 operating system is allowing to use simultaneously. Resolves
3578 - We no longer remind the user about configuration options that have
3579 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
3580 - Remove our old, non-weighted bandwidth-based node selection code.
3581 Previously, we used it as a fallback when we couldn't perform
3582 weighted bandwidth-based node selection. But that would only
3583 happen in the cases where we had no consensus, or when we had a
3584 consensus generated by buggy or ancient directory authorities. In
3585 either case, it's better to use the more modern, better maintained
3586 algorithm, with reasonable defaults for the weights. Closes
3588 - Remove the --disable-curve25519 configure option. Relays and
3589 clients now are required to support curve25519 and the
3591 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
3592 used to be deprecated synonyms for "StrictNodes", are now marked
3593 obsolete. Resolves ticket 12226.
3594 - Clients don't understand the BadDirectory flag in the consensus
3595 anymore, and ignore it.
3598 - Refactor the function that chooses guard nodes so that it can more
3599 easily be tested; write some tests for it.
3600 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
3601 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
3602 - Create unit tests for format_time_interval(). With bug 13393.
3603 - Add unit tests for tor_timegm signed overflow, tor_timegm and
3604 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
3605 tests (visible) fixes in bug 13476.
3606 - Add a "coverage-html" make target to generate HTML-visualized
3607 coverage results when building with --enable-coverage. (Requires
3608 lcov.) Patch from Kevin Murray.
3609 - Enable the backtrace handler (where supported) when running the
3611 - Revise all unit tests that used the legacy test_* macros to
3612 instead use the recommended tt_* macros. This patch was generated
3613 with coccinelle, to avoid manual errors. Closes ticket 13119.
3615 o Distribution (systemd):
3616 - systemd unit file: only allow tor to write to /var/lib/tor and
3617 /var/log/tor. The rest of the filesystem is accessible for reading
3618 only. Patch by intrigeri; resolves ticket 12751.
3619 - systemd unit file: ensure that the process and all its children
3620 can never gain new privileges. Patch by intrigeri; resolves
3622 - systemd unit file: set up /var/run/tor as writable for the Tor
3623 service. Patch by intrigeri; resolves ticket 13196.
3625 o Removed features (directory authorities):
3626 - Remove code that prevented authorities from listing Tor relays
3627 affected by CVE-2011-2769 as guards. These relays are already
3628 rejected altogether due to the minimum version requirement of
3629 0.2.3.16-alpha. Closes ticket 13152.
3630 - The "AuthDirRejectUnlisted" option no longer has any effect, as
3631 the fingerprints file (approved-routers) has been deprecated.
3632 - Directory authorities do not support being Naming dirauths anymore.
3633 The "NamingAuthoritativeDir" config option is now obsolete.
3634 - Directory authorities do not support giving out the BadDirectory
3636 - Directory authorities no longer advertise or support consensus
3637 methods 1 through 12 inclusive. These consensus methods were
3638 obsolete and/or insecure: maintaining the ability to support them
3639 served no good purpose. Implements part of proposal 215; closes
3642 o Testing (test-network.sh):
3643 - Stop using "echo -n", as some shells' built-in echo doesn't
3644 support "-n". Instead, use "/bin/echo -n". Partially fixes
3646 - Stop an apparent test-network hang when used with make -j2. Fixes
3648 - Add a --delay option to test-network.sh, which configures the
3649 delay before the chutney network tests for data transmission.
3650 Partially implements ticket 13161.
3653 Changes in version 0.2.5.10 - 2014-10-24
3654 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
3656 It adds several new security features, including improved
3657 denial-of-service resistance for relays, new compiler hardening
3658 options, and a system-call sandbox for hardened installations on Linux
3659 (requires seccomp2). The controller protocol has several new features,
3660 resolving IPv6 addresses should work better than before, and relays
3661 should be a little more CPU-efficient. We've added support for more
3662 OpenBSD and FreeBSD transparent proxy types. We've improved the build
3663 system and testing infrastructure to allow unit testing of more parts
3664 of the Tor codebase. Finally, we've addressed several nagging pluggable
3665 transport usability issues, and included numerous other small bugfixes
3666 and features mentioned below.
3668 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
3669 have accumulated many known flaws; everyone should upgrade.
3671 o Deprecated versions:
3672 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
3673 attention for some while.
3676 Changes in version 0.2.5.9-rc - 2014-10-20
3677 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
3678 series. It disables SSL3 in response to the recent "POODLE" attack
3679 (even though POODLE does not affect Tor). It also works around a crash
3680 bug caused by some operating systems' response to the "POODLE" attack
3681 (which does affect Tor). It also contains a few miscellaneous fixes.
3683 o Major security fixes:
3684 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
3685 today support TLS 1.0 or later, so we can safely turn off support
3686 for this old (and insecure) protocol. Fixes bug 13426.
3688 o Major bugfixes (openssl bug workaround):
3689 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
3690 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
3691 13471. This is a workaround for an OpenSSL bug.
3694 - Disable the sandbox name resolver cache when running tor-resolve:
3695 tor-resolve doesn't use the sandbox code, and turning it on was
3696 breaking attempts to do tor-resolve on a non-default server on
3697 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
3699 o Compilation fixes:
3700 - Build and run correctly on systems like OpenBSD-current that have
3701 patched OpenSSL to remove get_cipher_by_char and/or its
3702 implementations. Fixes issue 13325.
3704 o Downgraded warnings:
3705 - Downgrade the severity of the 'unexpected sendme cell from client'
3706 from 'warn' to 'protocol warning'. Closes ticket 8093.
3709 Changes in version 0.2.4.25 - 2014-10-20
3710 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
3711 (even though POODLE does not affect Tor). It also works around a crash
3712 bug caused by some operating systems' response to the "POODLE" attack
3713 (which does affect Tor).
3715 o Major security fixes (also in 0.2.5.9-rc):
3716 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
3717 today support TLS 1.0 or later, so we can safely turn off support
3718 for this old (and insecure) protocol. Fixes bug 13426.
3720 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
3721 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
3722 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
3723 13471. This is a workaround for an OpenSSL bug.
3726 Changes in version 0.2.5.8-rc - 2014-09-22
3727 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
3728 series. It fixes a bug that affects consistency and speed when
3729 connecting to hidden services, and it updates the location of one of
3730 the directory authorities.
3733 - Clients now send the correct address for their chosen rendezvous
3734 point when trying to access a hidden service. They used to send
3735 the wrong address, which would still work some of the time because
3736 they also sent the identity digest of the rendezvous point, and if
3737 the hidden service happened to try connecting to the rendezvous
3738 point from a relay that already had a connection open to it,
3739 the relay would reuse that connection. Now connections to hidden
3740 services should be more robust and faster. Also, this bug meant
3741 that clients were leaking to the hidden service whether they were
3742 on a little-endian (common) or big-endian (rare) system, which for
3743 some users might have reduced their anonymity. Fixes bug 13151;
3744 bugfix on 0.2.1.5-alpha.
3746 o Directory authority changes:
3747 - Change IP address for gabelmoo (v3 directory authority).
3750 Changes in version 0.2.4.24 - 2014-09-22
3751 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
3752 connecting to hidden services, and it updates the location of one of
3753 the directory authorities.
3756 - Clients now send the correct address for their chosen rendezvous
3757 point when trying to access a hidden service. They used to send
3758 the wrong address, which would still work some of the time because
3759 they also sent the identity digest of the rendezvous point, and if
3760 the hidden service happened to try connecting to the rendezvous
3761 point from a relay that already had a connection open to it,
3762 the relay would reuse that connection. Now connections to hidden
3763 services should be more robust and faster. Also, this bug meant
3764 that clients were leaking to the hidden service whether they were
3765 on a little-endian (common) or big-endian (rare) system, which for
3766 some users might have reduced their anonymity. Fixes bug 13151;
3767 bugfix on 0.2.1.5-alpha.
3769 o Directory authority changes:
3770 - Change IP address for gabelmoo (v3 directory authority).
3772 o Minor features (geoip):
3773 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
3777 Changes in version 0.2.5.7-rc - 2014-09-11
3778 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
3779 release series, and some long-standing bugs related to ORPort reachability
3780 testing and failure to send CREATE cells. It is the first release
3781 candidate for the Tor 0.2.5.x series.
3783 o Major bugfixes (client, startup):
3784 - Start making circuits as soon as DisabledNetwork is turned off.
3785 When Tor started with DisabledNetwork set, it would correctly
3786 conclude that it shouldn't build circuits, but it would mistakenly
3787 cache this conclusion, and continue believing it even when
3788 DisableNetwork is set to 0. Fixes the bug introduced by the fix
3789 for bug 11200; bugfix on 0.2.5.4-alpha.
3790 - Resume expanding abbreviations for command-line options. The fix
3791 for bug 4647 accidentally removed our hack from bug 586 that
3792 rewrote HashedControlPassword to __HashedControlSessionPassword
3793 when it appears on the commandline (which allowed the user to set
3794 her own HashedControlPassword in the torrc file while the
3795 controller generates a fresh session password for each run). Fixes
3796 bug 12948; bugfix on 0.2.5.1-alpha.
3797 - Warn about attempts to run hidden services and relays in the same
3798 process: that's probably not a good idea. Closes ticket 12908.
3800 o Major bugfixes (relay):
3801 - Avoid queuing or sending destroy cells for circuit ID zero when we
3802 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
3803 Found and fixed by "cypherpunks".
3804 - Fix ORPort reachability detection on relays running behind a
3805 proxy, by correctly updating the "local" mark on the controlling
3806 channel when changing the address of an or_connection_t after the
3807 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
3809 o Minor features (bridge):
3810 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
3811 cookie file for the ExtORPort g+r by default.
3813 o Minor features (geoip):
3814 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
3817 o Minor bugfixes (logging):
3818 - Reduce the log severity of the "Pluggable transport proxy does not
3819 provide any needed transports and will not be launched." message,
3820 since Tor Browser includes several ClientTransportPlugin lines in
3821 its torrc-defaults file, leading every Tor Browser user who looks
3822 at her logs to see these notices and wonder if they're dangerous.
3823 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
3824 - Downgrade "Unexpected onionskin length after decryption" warning
3825 to a protocol-warn, since there's nothing relay operators can do
3826 about a client that sends them a malformed create cell. Resolves
3827 bug 12996; bugfix on 0.0.6rc1.
3828 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
3829 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
3830 - When logging information about an EXTEND2 or EXTENDED2 cell, log
3831 their names correctly. Fixes part of bug 12700; bugfix
3833 - When logging information about a relay cell whose command we don't
3834 recognize, log its command as an integer. Fixes part of bug 12700;
3835 bugfix on 0.2.1.10-alpha.
3836 - Escape all strings from the directory connection before logging
3837 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
3839 o Minor bugfixes (controller):
3840 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
3841 bug 12864; bugfix on 0.2.5.1-alpha.
3842 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
3843 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
3846 o Minor bugfixes (compilation):
3847 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
3848 bugfix on 0.2.5.5-alpha.
3849 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
3850 0.2.5.1-alpha. Patch from "NewEraCracker".
3851 - In routerlist_assert_ok(), don't take the address of a
3852 routerinfo's cache_info member unless that routerinfo is non-NULL.
3853 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
3854 - Fix a large number of false positive warnings from the clang
3855 analyzer static analysis tool. This should make real warnings
3856 easier for clang analyzer to find. Patch from "teor". Closes
3859 o Distribution (systemd):
3860 - Verify configuration file via ExecStartPre in the systemd unit
3861 file. Patch from intrigeri; resolves ticket 12730.
3862 - Explicitly disable RunAsDaemon in the systemd unit file. Our
3863 current systemd unit uses "Type = simple", so systemd does not
3864 expect tor to fork. If the user has "RunAsDaemon 1" in their
3865 torrc, then things won't work as expected. This is e.g. the case
3866 on Debian (and derivatives), since there we pass "--defaults-torrc
3867 /usr/share/tor/tor-service-defaults-torrc" (that contains
3868 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
3872 - Adjust the URLs in the README to refer to the new locations of
3873 several documents on the website. Fixes bug 12830. Patch from
3875 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
3879 Changes in version 0.2.5.6-alpha - 2014-07-28
3880 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
3881 risk from guard rotation, and fixes a variety of other issues to get
3882 us closer to a release candidate.
3884 o Major features (also in 0.2.4.23):
3885 - Make the number of entry guards configurable via a new
3886 NumEntryGuards consensus parameter, and the number of directory
3887 guards configurable via a new NumDirectoryGuards consensus
3888 parameter. Implements ticket 12688.
3890 o Major bugfixes (also in 0.2.4.23):
3891 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
3892 implementation that caused incorrect results on 32-bit
3893 implementations when certain malformed inputs were used along with
3894 a small class of private ntor keys. This bug does not currently
3895 appear to allow an attacker to learn private keys or impersonate a
3896 Tor server, but it could provide a means to distinguish 32-bit Tor
3897 implementations from 64-bit Tor implementations. Fixes bug 12694;
3898 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
3902 - Perform circuit cleanup operations even when circuit
3903 construction operations are disabled (because the network is
3904 disabled, or because there isn't enough directory information).
3905 Previously, when we were not building predictive circuits, we
3906 were not closing expired circuits either. Fixes bug 8387; bugfix on
3907 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
3908 became more strict about when we have "enough directory information
3912 - Authorities now assign the Guard flag to the fastest 25% of the
3913 network (it used to be the fastest 50%). Also raise the consensus
3914 weight that guarantees the Guard flag from 250 to 2000. For the
3915 current network, this results in about 1100 guards, down from 2500.
3916 This step paves the way for moving the number of entry guards
3917 down to 1 (proposal 236) while still providing reasonable expected
3918 performance for most users. Implements ticket 12690.
3919 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
3921 - Slightly enhance the diagnostic message for bug 12184.
3923 o Minor bugfixes (also in 0.2.4.23):
3924 - Warn and drop the circuit if we receive an inbound 'relay early'
3925 cell. Those used to be normal to receive on hidden service circuits
3926 due to bug 1038, but the buggy Tor versions are long gone from
3927 the network so we can afford to resume watching for them. Resolves
3928 the rest of bug 1038; bugfix on 0.2.1.19.
3929 - Correct a confusing error message when trying to extend a circuit
3930 via the control protocol but we don't know a descriptor or
3931 microdescriptor for one of the specified relays. Fixes bug 12718;
3932 bugfix on 0.2.3.1-alpha.
3935 - Fix compilation when building with bufferevents enabled. (This
3936 configuration is still not expected to work, however.)
3937 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
3938 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
3940 - Compile correctly with builds and forks of OpenSSL (such as
3941 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
3942 0.2.1.1-alpha. Patch from "dhill".
3945 Changes in version 0.2.4.23 - 2014-07-28
3946 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
3947 guard rotation, and also backports several important fixes from the
3948 Tor 0.2.5 alpha release series.
3951 - Clients now look at the "usecreatefast" consensus parameter to
3952 decide whether to use CREATE_FAST or CREATE cells for the first hop
3953 of their circuit. This approach can improve security on connections
3954 where Tor's circuit handshake is stronger than the available TLS
3955 connection security levels, but the tradeoff is more computational
3956 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3957 - Make the number of entry guards configurable via a new
3958 NumEntryGuards consensus parameter, and the number of directory
3959 guards configurable via a new NumDirectoryGuards consensus
3960 parameter. Implements ticket 12688.
3963 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
3964 implementation that caused incorrect results on 32-bit
3965 implementations when certain malformed inputs were used along with
3966 a small class of private ntor keys. This bug does not currently
3967 appear to allow an attacker to learn private keys or impersonate a
3968 Tor server, but it could provide a means to distinguish 32-bit Tor
3969 implementations from 64-bit Tor implementations. Fixes bug 12694;
3970 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
3974 - Warn and drop the circuit if we receive an inbound 'relay early'
3975 cell. Those used to be normal to receive on hidden service circuits
3976 due to bug 1038, but the buggy Tor versions are long gone from
3977 the network so we can afford to resume watching for them. Resolves
3978 the rest of bug 1038; bugfix on 0.2.1.19.
3979 - Correct a confusing error message when trying to extend a circuit
3980 via the control protocol but we don't know a descriptor or
3981 microdescriptor for one of the specified relays. Fixes bug 12718;
3982 bugfix on 0.2.3.1-alpha.
3983 - Avoid an illegal read from stack when initializing the TLS
3984 module using a version of OpenSSL without all of the ciphers
3985 used by the v2 link handshake. Fixes bug 12227; bugfix on
3986 0.2.4.8-alpha. Found by "starlight".
3989 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
3993 Changes in version 0.2.5.5-alpha - 2014-06-18
3994 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
3995 0.2.5.x release series, including a couple of DoS issues, some
3996 performance regressions, a large number of bugs affecting the Linux
3997 seccomp2 sandbox code, and various other bugfixes. It also adds
3998 diagnostic bugfixes for a few tricky issues that we're trying to
4001 o Major features (security, traffic analysis resistance):
4002 - Several major improvements to the algorithm used to decide when to
4003 close TLS connections. Previous versions of Tor closed connections
4004 at a fixed interval after the last time a non-padding cell was
4005 sent over the connection, regardless of the target of the
4006 connection. Now, we randomize the intervals by adding up to 50% of
4007 their base value, we measure the length of time since connection
4008 last had at least one circuit, and we allow connections to known
4009 ORs to remain open a little longer (15 minutes instead of 3
4010 minutes minimum). These changes should improve Tor's resistance
4011 against some kinds of traffic analysis, and lower some overhead
4012 from needlessly closed connections. Fixes ticket 6799.
4013 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
4015 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
4016 - Fix a memory leak that could occur if a microdescriptor parse
4017 fails during the tokenizing step. This bug could enable a memory
4018 exhaustion attack by directory servers. Fixes bug 11649; bugfix
4021 o Major bugfixes (security, directory authorities):
4022 - Directory authorities now include a digest of each relay's
4023 identity key as a part of its microdescriptor.
4025 This is a workaround for bug 11743 (reported by "cypherpunks"),
4026 where Tor clients do not support receiving multiple
4027 microdescriptors with the same SHA256 digest in the same
4028 consensus. When clients receive a consensus like this, they only
4029 use one of the relays. Without this fix, a hostile relay could
4030 selectively disable some client use of target relays by
4031 constructing a router descriptor with a different identity and the
4032 same microdescriptor parameters and getting the authorities to
4033 list it in a microdescriptor consensus. This fix prevents an
4034 attacker from causing a microdescriptor collision, because the
4035 router's identity is not forgeable.
4037 o Major bugfixes (relay):
4038 - Use a direct dirport connection when uploading non-anonymous
4039 descriptors to the directory authorities. Previously, relays would
4040 incorrectly use tunnel connections under a fairly wide variety of
4041 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
4042 - When a circuit accidentally has the same circuit ID for its
4043 forward and reverse direction, correctly detect the direction of
4044 cells using that circuit. Previously, this bug made roughly one
4045 circuit in a million non-functional. Fixes bug 12195; this is a
4046 bugfix on every version of Tor.
4048 o Major bugfixes (client, pluggable transports):
4049 - When managing pluggable transports, use OS notification facilities
4050 to learn if they have crashed, and don't attempt to kill any
4051 process that has already exited. Fixes bug 8746; bugfix
4054 o Minor features (diagnostic):
4055 - When logging a warning because of bug 7164, additionally check the
4056 hash table for consistency (as proposed on ticket 11737). This may
4057 help diagnose bug 7164.
4058 - When we log a heartbeat, log how many one-hop circuits we have
4059 that are at least 30 minutes old, and log status information about
4060 a few of them. This is an attempt to track down bug 8387.
4061 - When encountering an unexpected CR while writing text to a file on
4062 Windows, log the name of the file. Should help diagnosing
4064 - Give more specific warnings when a client notices that an onion
4065 handshake has failed. Fixes ticket 9635.
4066 - Add significant new logging code to attempt to diagnose bug 12184,
4067 where relays seem to run out of available circuit IDs.
4068 - Improve the diagnostic log message for bug 8387 even further to
4069 try to improve our odds of figuring out why one-hop directory
4070 circuits sometimes do not get closed.
4072 o Minor features (security, memory management):
4073 - Memory allocation tricks (mempools and buffer freelists) are now
4074 disabled by default. You can turn them back on with
4075 --enable-mempools and --enable-buf-freelists respectively. We're
4076 disabling these features because malloc performance is good enough
4077 on most platforms, and a similar feature in OpenSSL exacerbated
4078 exploitation of the Heartbleed attack. Resolves ticket 11476.
4080 o Minor features (security):
4081 - Apply the secure SipHash-2-4 function to the hash table mapping
4082 circuit IDs and channels to circuits. We missed this one when we
4083 were converting all the other hash functions to use SipHash back
4084 in 0.2.5.3-alpha. Resolves ticket 11750.
4086 o Minor features (build):
4087 - The configure script has a --disable-seccomp option to turn off
4088 support for libseccomp on systems that have it, in case it (or
4089 Tor's use of it) is broken. Resolves ticket 11628.
4091 o Minor features (other):
4092 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
4095 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
4096 - When running a hidden service, do not allow TunneledDirConns 0;
4097 this will keep the hidden service from running, and also
4098 make it publish its descriptors directly over HTTP. Fixes bug 10849;
4099 bugfix on 0.2.1.1-alpha.
4101 o Minor bugfixes (performance):
4102 - Avoid a bug where every successful connection made us recompute
4103 the flag telling us whether we have sufficient information to
4104 build circuits. Previously, we would forget our cached value
4105 whenever we successfully opened a channel (or marked a router as
4106 running or not running for any other reason), regardless of
4107 whether we had previously believed the router to be running. This
4108 forced us to run an expensive update operation far too often.
4109 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
4110 - Avoid using tor_memeq() for checking relay cell integrity. This
4111 removes a possible performance bottleneck. Fixes part of bug
4112 12169; bugfix on 0.2.1.31.
4114 o Minor bugfixes (compilation):
4115 - Fix compilation of test_status.c when building with MVSC. Bugfix
4116 on 0.2.5.4-alpha. Patch from Gisle Vanem.
4117 - Resolve GCC complaints on OpenBSD about discarding constness in
4118 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
4119 on 0.1.1.23. Patch from Dana Koch.
4120 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
4121 treatment of long and time_t as comparable types. Fixes part of
4122 bug 11633. Patch from Dana Koch.
4123 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
4124 11623; bugfix on 0.2.5.3-alpha.
4125 - When deciding whether to build the 64-bit curve25519
4126 implementation, detect platforms where we can compile 128-bit
4127 arithmetic but cannot link it. Fixes bug 11729; bugfix on
4128 0.2.4.8-alpha. Patch from "conradev".
4129 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
4130 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
4131 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
4134 o Minor bugfixes (Directory server):
4135 - When sending a compressed set of descriptors or microdescriptors,
4136 make sure to finalize the zlib stream. Previously, we would write
4137 all the compressed data, but if the last descriptor we wanted to
4138 send was missing or too old, we would not mark the stream as
4139 finished. This caused problems for decompression tools. Fixes bug
4140 11648; bugfix on 0.1.1.23.
4142 o Minor bugfixes (Linux seccomp sandbox):
4143 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
4144 11622; bugfix on 0.2.5.1-alpha.
4145 - Avoid crashing when re-opening listener ports with the seccomp
4146 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
4147 - Avoid crashing with the seccomp sandbox enabled along with
4148 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
4149 - When we receive a SIGHUP with the sandbox enabled, correctly
4150 support rotating our log files. Fixes bug 12032; bugfix
4152 - Avoid crash when running with sandboxing enabled and
4153 DirReqStatistics not disabled. Fixes bug 12035; bugfix
4155 - Fix a "BUG" warning when trying to write bridge-stats files with
4156 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
4158 - Prevent the sandbox from crashing on startup when run with the
4159 --enable-expensive-hardening configuration option. Fixes bug
4160 11477; bugfix on 0.2.5.4-alpha.
4161 - When running with DirPortFrontPage and sandboxing both enabled,
4162 reload the DirPortFrontPage correctly when restarting. Fixes bug
4163 12028; bugfix on 0.2.5.1-alpha.
4164 - Don't try to enable the sandbox when using the Tor binary to check
4165 its configuration, hash a passphrase, or so on. Doing so was
4166 crashing on startup for some users. Fixes bug 11609; bugfix
4168 - Avoid warnings when running with sandboxing and node statistics
4169 enabled at the same time. Fixes part of 12064; bugfix on
4170 0.2.5.1-alpha. Patch from Michael Wolf.
4171 - Avoid warnings when running with sandboxing enabled at the same
4172 time as cookie authentication, hidden services, or directory
4173 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
4174 - Do not allow options that require calls to exec to be enabled
4175 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
4176 bug 12043; bugfix on 0.2.5.1-alpha.
4177 - Handle failures in getpwnam()/getpwuid() when running with the
4178 User option set and the Linux syscall sandbox enabled. Fixes bug
4179 11946; bugfix on 0.2.5.1-alpha.
4180 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
4181 to avoid calling getaddrinfo() after installing the sandbox
4182 filters. Previously, it preloaded a cache with the IPv4 address
4183 for our hostname, and nothing else. Now, it loads the cache with
4184 every address that it used to initialize the Tor process. Fixes
4185 bug 11970; bugfix on 0.2.5.1-alpha.
4187 o Minor bugfixes (pluggable transports):
4188 - Enable the ExtORPortCookieAuthFile option, to allow changing the
4189 default location of the authentication token for the extended OR
4190 Port as used by sever-side pluggable transports. We had
4191 implemented this option before, but the code to make it settable
4192 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
4193 - Avoid another 60-second delay when starting Tor in a pluggable-
4194 transport-using configuration when we already have cached
4195 descriptors for our bridges. Fixes bug 11965; bugfix
4198 o Minor bugfixes (client):
4199 - Avoid "Tried to open a socket with DisableNetwork set" warnings
4200 when starting a client with bridges configured and DisableNetwork
4201 set. (Tor launcher starts Tor with DisableNetwork set the first
4202 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
4204 o Minor bugfixes (testing):
4205 - The Python parts of the test scripts now work on Python 3 as well
4206 as Python 2, so systems where '/usr/bin/python' is Python 3 will
4207 no longer have the tests break. Fixes bug 11608; bugfix
4209 - When looking for versions of python that we could run the tests
4210 with, check for "python2.7" and "python3.3"; previously we were
4211 only looking for "python", "python2", and "python3". Patch from
4212 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
4213 - Fix all valgrind warnings produced by the unit tests. There were
4214 over a thousand memory leak warnings previously, mostly produced
4215 by forgetting to free things in the unit test code. Fixes bug
4216 11618, bugfixes on many versions of Tor.
4218 o Minor bugfixes (tor-fw-helper):
4219 - Give a correct log message when tor-fw-helper fails to launch.
4220 (Previously, we would say something like "tor-fw-helper sent us a
4221 string we could not parse".) Fixes bug 9781; bugfix
4224 o Minor bugfixes (relay, threading):
4225 - Check return code on spawn_func() in cpuworker code, so that we
4226 don't think we've spawned a nonworking cpuworker and write junk to
4227 it forever. Fix related to bug 4345; bugfix on all released Tor
4228 versions. Found by "skruffy".
4229 - Use a pthread_attr to make sure that spawn_func() cannot return an
4230 error while at the same time launching a thread. Fix related to
4231 bug 4345; bugfix on all released Tor versions. Reported
4234 o Minor bugfixes (relay, oom prevention):
4235 - Correctly detect the total available system memory. We tried to do
4236 this in 0.2.5.4-alpha, but the code was set up to always return an
4237 error value, even on success. Fixes bug 11805; bugfix
4240 o Minor bugfixes (relay, other):
4241 - We now drop CREATE cells for already-existent circuit IDs and for
4242 zero-valued circuit IDs, regardless of other factors that might
4243 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
4245 - Avoid an illegal read from stack when initializing the TLS module
4246 using a version of OpenSSL without all of the ciphers used by the
4247 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
4249 - When rejecting DATA cells for stream_id zero, still count them
4250 against the circuit's deliver window so that we don't fail to send
4251 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
4253 o Minor bugfixes (logging):
4254 - Fix a misformatted log message about delayed directory fetches.
4255 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
4256 - Squelch a spurious LD_BUG message "No origin circuit for
4257 successful SOCKS stream" in certain hidden service failure cases;
4261 - Include a tor.service file in contrib/dist for use with systemd.
4262 Some distributions will be able to use this file unmodified;
4263 others will need to tweak it, or write their own. Patch from Jamie
4264 Nguyen; resolves ticket 8368.
4267 - Clean up several option names in the manpage to match their real
4268 names, add the missing documentation for a couple of testing and
4269 directory authority options, remove the documentation for a
4270 V2-directory fetching option that no longer exists. Resolves
4272 - Correct the documenation so that it lists the correct directory
4273 for the stats files. (They are in a subdirectory called "stats",
4275 - In the manpage, move more authority-only options into the
4276 directory authority section so that operators of regular directory
4277 caches don't get confused.
4280 - The contrib directory has been sorted and tidied. Before, it was
4281 an unsorted dumping ground for useful and not-so-useful things.
4282 Now, it is divided based on functionality, and the items which
4283 seemed to be nonfunctional or useless have been removed. Resolves
4284 ticket 8966; based on patches from "rl1987".
4287 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
4288 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
4289 - The TunnelDirConns and PreferTunnelledDirConns options no longer
4290 exist; tunneled directory connections have been available since
4291 0.1.2.5-alpha, and turning them off is not a good idea. This is a
4292 brute-force fix for 10849, where "TunnelDirConns 0" would break
4296 Changes in version 0.2.4.22 - 2014-05-16
4297 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
4298 alpha release series. These include blocking all authority signing
4299 keys that may have been affected by the OpenSSL "heartbleed" bug,
4300 choosing a far more secure set of TLS ciphersuites by default, closing
4301 a couple of memory leaks that could be used to run a target relay out
4302 of RAM, and several others.
4304 o Major features (security, backport from 0.2.5.4-alpha):
4305 - Block authority signing keys that were used on authorities
4306 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
4307 don't have any evidence that these keys _were_ compromised; we're
4308 doing this to be prudent.) Resolves ticket 11464.
4310 o Major bugfixes (security, OOM):
4311 - Fix a memory leak that could occur if a microdescriptor parse
4312 fails during the tokenizing step. This bug could enable a memory
4313 exhaustion attack by directory servers. Fixes bug 11649; bugfix
4316 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
4317 - The relay ciphersuite list is now generated automatically based on
4318 uniform criteria, and includes all OpenSSL ciphersuites with
4319 acceptable strength and forward secrecy. Previously, we had left
4320 some perfectly fine ciphersuites unsupported due to omission or
4321 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
4322 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
4323 - Relays now trust themselves to have a better view than clients of
4324 which TLS ciphersuites are better than others. (Thanks to bug
4325 11513, the relay list is now well-considered, whereas the client
4326 list has been chosen mainly for anti-fingerprinting purposes.)
4327 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
4328 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
4329 AES128. Resolves ticket 11528.
4330 - Clients now try to advertise the same list of ciphersuites as
4331 Firefox 28. This change enables selection of (fast) GCM
4332 ciphersuites, disables some strange old ciphers, and stops
4333 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
4334 Resolves ticket 11438.
4336 o Minor bugfixes (configuration, security):
4337 - When running a hidden service, do not allow TunneledDirConns 0:
4338 trying to set that option together with a hidden service would
4339 otherwise prevent the hidden service from running, and also make
4340 it publish its descriptors directly over HTTP. Fixes bug 10849;
4341 bugfix on 0.2.1.1-alpha.
4343 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
4344 - Avoid sending a garbage value to the controller when a circuit is
4345 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
4347 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
4348 - Stop leaking memory when we successfully resolve a PTR record.
4349 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
4351 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
4352 - Avoid 60-second delays in the bootstrapping process when Tor is
4353 launching for a second time while using bridges. Fixes bug 9229;
4354 bugfix on 0.2.0.3-alpha.
4356 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
4357 - Give the correct URL in the warning message when trying to run a
4358 relay on an ancient version of Windows. Fixes bug 9393.
4360 o Minor bugfixes (compilation):
4361 - Fix a compilation error when compiling with --disable-curve25519.
4362 Fixes bug 9700; bugfix on 0.2.4.17-rc.
4365 - Downgrade the warning severity for the the "md was still
4366 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
4367 for trying to diagnose this bug, and the current warning in
4368 earlier versions of tor achieves nothing useful. Addresses warning
4371 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
4372 - When we run out of usable circuit IDs on a channel, log only one
4373 warning for the whole channel, and describe how many circuits
4374 there were on the channel. Fixes part of ticket 11553.
4376 o Minor features (security, backport from 0.2.5.4-alpha):
4377 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
4378 leave the default at 8GBytes), to better support Raspberry Pi
4379 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
4381 o Documentation (backport from 0.2.5.4-alpha):
4382 - Correctly document that we search for a system torrc file before
4383 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
4387 Changes in version 0.2.5.4-alpha - 2014-04-25
4388 Tor 0.2.5.4-alpha includes several security and performance
4389 improvements for clients and relays, including blacklisting authority
4390 signing keys that were used while susceptible to the OpenSSL
4391 "heartbleed" bug, fixing two expensive functions on busy relays,
4392 improved TLS ciphersuite preference lists, support for run-time
4393 hardening on compilers that support AddressSanitizer, and more work on
4394 the Linux sandbox code.
4396 There are also several usability fixes for clients (especially clients
4397 that use bridges), two new TransPort protocols supported (one on
4398 OpenBSD, one on FreeBSD), and various other bugfixes.
4400 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
4401 have accumulated many known flaws; everyone should upgrade.
4403 o Major features (security):
4404 - If you don't specify MaxMemInQueues yourself, Tor now tries to
4405 pick a good value based on your total system memory. Previously,
4406 the default was always 8 GB. You can still override the default by
4407 setting MaxMemInQueues yourself. Resolves ticket 11396.
4408 - Block authority signing keys that were used on authorities
4409 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
4410 don't have any evidence that these keys _were_ compromised; we're
4411 doing this to be prudent.) Resolves ticket 11464.
4413 o Major features (relay performance):
4414 - Speed up server-side lookups of rendezvous and introduction point
4415 circuits by using hashtables instead of linear searches. These
4416 functions previously accounted between 3 and 7% of CPU usage on
4417 some busy relays. Resolves ticket 9841.
4418 - Avoid wasting CPU when extending a circuit over a channel that is
4419 nearly out of circuit IDs. Previously, we would do a linear scan
4420 over possible circuit IDs before finding one or deciding that we
4421 had exhausted our possibilities. Now, we try at most 64 random
4422 circuit IDs before deciding that we probably won't succeed. Fixes
4423 a possible root cause of ticket 11553.
4425 o Major features (seccomp2 sandbox, Linux only):
4426 - The seccomp2 sandbox can now run a test network for multiple hours
4427 without crashing. The sandbox is still experimental, and more bugs
4428 will probably turn up. To try it, enable "Sandbox 1" on a Linux
4429 host. Resolves ticket 11351.
4430 - Strengthen sandbox code: the sandbox can now test the arguments
4431 for rename(), and blocks _sysctl() entirely. Resolves another part
4433 - When the sandbox blocks a system call, it now tries to log a stack
4434 trace before exiting. Resolves ticket 11465.
4436 o Major bugfixes (TLS cipher selection):
4437 - The relay ciphersuite list is now generated automatically based on
4438 uniform criteria, and includes all OpenSSL ciphersuites with
4439 acceptable strength and forward secrecy. Previously, we had left
4440 some perfectly fine ciphersuites unsupported due to omission or
4441 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
4442 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
4443 - Relays now trust themselves to have a better view than clients of
4444 which TLS ciphersuites are better than others. (Thanks to bug
4445 11513, the relay list is now well-considered, whereas the client
4446 list has been chosen mainly for anti-fingerprinting purposes.)
4447 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
4448 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
4449 AES128. Resolves ticket 11528.
4450 - Clients now try to advertise the same list of ciphersuites as
4451 Firefox 28. This change enables selection of (fast) GCM
4452 ciphersuites, disables some strange old ciphers, and stops
4453 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
4454 Resolves ticket 11438.
4456 o Major bugfixes (bridge client):
4457 - Avoid 60-second delays in the bootstrapping process when Tor is
4458 launching for a second time while using bridges. Fixes bug 9229;
4459 bugfix on 0.2.0.3-alpha.
4461 o Minor features (transparent proxy, *BSD):
4462 - Support FreeBSD's ipfw firewall interface for TransPort ports on
4463 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
4464 10267; patch from "yurivict".
4465 - Support OpenBSD's divert-to rules with the pf firewall for
4466 transparent proxy ports. To enable it, set "TransProxyType
4467 pf-divert". This allows Tor to run a TransPort transparent proxy
4468 port on OpenBSD 4.4 or later without root privileges. See the
4469 pf.conf(5) manual page for information on configuring pf to use
4470 divert-to rules. Closes ticket 10896; patch from Dana Koch.
4472 o Minor features (security):
4473 - New --enable-expensive-hardening option to enable security
4474 hardening options that consume nontrivial amounts of CPU and
4475 memory. Right now, this includes AddressSanitizer and UbSan, which
4476 are supported in newer versions of GCC and Clang. Closes ticket
4479 o Minor features (log verbosity):
4480 - Demote the message that we give when a flushing connection times
4481 out for too long from NOTICE to INFO. It was usually meaningless.
4482 Resolves ticket 5286.
4483 - Don't log so many notice-level bootstrapping messages at startup
4484 about downloading descriptors. Previously, we'd log a notice
4485 whenever we learned about more routers. Now, we only log a notice
4486 at every 5% of progress. Fixes bug 9963.
4487 - Warn less verbosely when receiving a malformed
4488 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
4489 - When we run out of usable circuit IDs on a channel, log only one
4490 warning for the whole channel, and describe how many circuits
4491 there were on the channel. Fixes part of ticket 11553.
4493 o Minor features (relay):
4494 - If a circuit timed out for at least 3 minutes, check if we have a
4495 new external IP address, and publish a new descriptor with the new
4496 IP address if it changed. Resolves ticket 2454.
4498 o Minor features (controller):
4499 - Make the entire exit policy available from the control port via
4500 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
4502 - Because of the fix for ticket 11396, the real limit for memory
4503 usage may no longer match the configured MaxMemInQueues value. The
4504 real limit is now exposed via GETINFO limits/max-mem-in-queues.
4506 o Minor features (bridge client):
4507 - Report a more useful failure message when we can't connect to a
4508 bridge because we don't have the right pluggable transport
4509 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
4511 o Minor features (diagnostic):
4512 - Add more log messages to diagnose bug 7164, which causes
4513 intermittent "microdesc_free() called but md was still referenced"
4514 warnings. We now include more information, to figure out why we
4515 might be cleaning a microdescriptor for being too old if it's
4516 still referenced by a live node_t object.
4518 o Minor bugfixes (client, DNSPort):
4519 - When using DNSPort, try to respond to AAAA requests with AAAA
4520 answers. Previously, we hadn't looked at the request type when
4521 deciding which answer type to prefer. Fixes bug 10468; bugfix on
4523 - When receiving a DNS query for an unsupported record type, reply
4524 with no answer rather than with a NOTIMPL error. This behavior
4525 isn't correct either, but it will break fewer client programs, we
4526 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
4529 o Minor bugfixes (exit relay):
4530 - Stop leaking memory when we successfully resolve a PTR record.
4531 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
4533 o Minor bugfixes (bridge client):
4534 - Stop accepting bridge lines containing hostnames. Doing so would
4535 cause clients to perform DNS requests on the hostnames, which was
4536 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
4537 - Avoid a 60-second delay in the bootstrapping process when a Tor
4538 client with pluggable transports re-reads its configuration at
4539 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
4541 o Minor bugfixes (client, logging during bootstrap):
4542 - Warn only once if we start logging in an unsafe way. Previously,
4543 we complain as many times as we had problems. Fixes bug 9870;
4544 bugfix on 0.2.5.1-alpha.
4545 - Only report the first fatal bootstrap error on a given OR
4546 connection. This stops us from telling the controller bogus error
4547 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
4548 - Be more helpful when trying to run sandboxed on Linux without
4549 libseccomp. Instead of saying "Sandbox is not implemented on this
4550 platform", we now explain that we need to be built with
4551 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
4552 - Avoid generating spurious warnings when starting with
4553 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
4556 o Minor bugfixes (closing OR connections):
4557 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
4558 check if it's an or_connection_t and correctly call
4559 connection_or_close_for_error() rather than
4560 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
4562 - When closing all connections on setting DisableNetwork to 1, use
4563 connection_or_close_normally() rather than closing OR connections
4564 out from under the channel layer. Fixes bug 11306; bugfix on
4567 o Minor bugfixes (controller):
4568 - Avoid sending a garbage value to the controller when a circuit is
4569 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
4571 o Minor bugfixes (tor-fw-helper):
4572 - Allow tor-fw-helper to build again by adding src/ext to its
4573 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
4575 o Minor bugfixes (bridges):
4576 - Avoid potential crashes or bad behavior when launching a
4577 server-side managed proxy with ORPort or ExtORPort temporarily
4578 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
4580 o Minor bugfixes (platform-specific):
4581 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
4582 bug 11426; bugfix on 0.2.5.3-alpha.
4583 - When dumping a malformed directory object to disk, save it in
4584 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
4586 - Don't report failures from make_socket_reuseable() on incoming
4587 sockets on OSX: this can happen when incoming connections close
4588 early. Fixes bug 10081.
4590 o Minor bugfixes (trivial memory leaks):
4591 - Fix a small memory leak when signing a directory object. Fixes bug
4592 11275; bugfix on 0.2.4.13-alpha.
4593 - Free placeholder entries in our circuit table at exit; fixes a
4594 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
4595 - Don't re-initialize a second set of OpenSSL mutexes when starting
4596 up. Previously, we'd make one set of mutexes, and then immediately
4597 replace them with another. Fixes bug 11726; bugfix on
4599 - Resolve some memory leaks found by coverity in the unit tests, on
4600 exit in tor-gencert, and on a failure to compute digests for our
4601 own keys when generating a v3 networkstatus vote. These leaks
4602 should never have affected anyone in practice.
4604 o Minor bugfixes (hidden service):
4605 - Only retry attempts to connect to a chosen rendezvous point 8
4606 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
4608 o Minor bugfixes (misc code correctness):
4609 - Fix various instances of undefined behavior in channeltls.c,
4610 tor_memmem(), and eventdns.c that would cause us to construct
4611 pointers to memory outside an allocated object. (These invalid
4612 pointers were not accessed, but C does not even allow them to
4613 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
4614 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
4615 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
4616 fix some miscellaneous errors in our tests and codebase. Fixes bug
4617 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
4618 - Always check return values for unlink, munmap, UnmapViewOfFile;
4619 check strftime return values more often. In some cases all we can
4620 do is report a warning, but this may help prevent deeper bugs from
4621 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
4623 - Fix numerous warnings from the clang "scan-build" static analyzer.
4624 Some of these are programming style issues; some of them are false
4625 positives that indicated awkward code; some are undefined behavior
4626 cases related to constructing (but not using) invalid pointers;
4627 some are assumptions about API behavior; some are (harmlessly)
4628 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
4629 correct; and one or two are genuine bugs that weren't reachable
4630 from the rest of the program. Fixes bug 8793; bugfixes on many,
4634 - Build the torify.1 manpage again. Previously, we were only trying
4635 to build it when also building tor-fw-helper. That's why we didn't
4636 notice that we'd broken the ability to build it. Fixes bug 11321;
4637 bugfix on 0.2.5.1-alpha.
4638 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
4639 11061; bugfix on 0.2.4.7-alpha.
4640 - Correctly document that we search for a system torrc file before
4641 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
4643 - Resolve warnings from Doxygen.
4645 o Code simplifications and refactoring:
4646 - Remove is_internal_IP() function. Resolves ticket 4645.
4647 - Remove unused function circuit_dump_by_chan from circuitlist.c.
4648 Closes issue 9107; patch from "marek".
4649 - Change our use of the ENUM_BF macro to avoid declarations that
4652 o Deprecated versions:
4653 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
4654 attention for some while. Directory authorities no longer accept
4655 descriptors from relays running any version of Tor prior to Tor
4656 0.2.3.16-alpha. Resolves ticket 11149.
4659 - New macros in test.h to simplify writing mock-functions for unit
4660 tests. Part of ticket 11507. Patch from Dana Koch.
4661 - Complete tests for the status.c module. Resolves ticket 11507.
4662 Patch from Dana Koch.
4665 - Remove all code for the long unused v1 directory protocol.
4666 Resolves ticket 11070.
4669 Changes in version 0.2.5.3-alpha - 2014-03-22
4670 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
4671 two new anti-DoS features for Tor relays, resolves a bug that kept
4672 SOCKS5 support for IPv6 from working, fixes several annoying usability
4673 issues for bridge users, and removes more old code for unused
4676 The Tor 0.2.5.x release series is now in patch-freeze: no feature
4677 patches not already written will be considered for inclusion in 0.2.5.x.
4679 o Major features (relay security, DoS-resistance):
4680 - When deciding whether we have run out of memory and we need to
4681 close circuits, also consider memory allocated in buffers for
4682 streams attached to each circuit.
4684 This change, which extends an anti-DoS feature introduced in
4685 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
4686 better resist more memory-based DoS attacks than before. Since the
4687 MaxMemInCellQueues option now applies to all queues, it is renamed
4688 to MaxMemInQueues. This feature fixes bug 10169.
4689 - Avoid hash-flooding denial-of-service attacks by using the secure
4690 SipHash-2-4 hash function for our hashtables. Without this
4691 feature, an attacker could degrade performance of a targeted
4692 client or server by flooding their data structures with a large
4693 number of entries to be stored at the same hash table position,
4694 thereby slowing down the Tor instance. With this feature, hash
4695 table positions are derived from a randomized cryptographic key,
4696 and an attacker cannot predict which entries will collide. Closes
4698 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
4699 the default at 8GBytes), to better support Raspberry Pi users. Fixes
4700 bug 9686; bugfix on 0.2.4.14-alpha.
4702 o Minor features (bridges, pluggable transports):
4703 - Bridges now write the SHA1 digest of their identity key
4704 fingerprint (that is, a hash of a hash of their public key) to
4705 notice-level logs, and to a new hashed-fingerprint file. This
4706 information will help bridge operators look up their bridge in
4707 Globe and similar tools. Resolves ticket 10884.
4708 - Improve the message that Tor displays when running as a bridge
4709 using pluggable transports without an Extended ORPort listener.
4710 Also, log the message in the log file too. Resolves ticket 11043.
4712 o Minor features (other):
4713 - Add a new option, PredictedPortsRelevanceTime, to control how long
4714 after having received a request to connect to a given port Tor
4715 will try to keep circuits ready in anticipation of future requests
4716 for that port. Patch from "unixninja92"; implements ticket 9176.
4717 - Generate a warning if any ports are listed in the SocksPolicy,
4718 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
4719 AuthDirBadExit options. (These options only support address
4720 ranges.) Fixes part of ticket 11108.
4721 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
4724 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
4725 - Build without warnings under clang 3.4. (We have some macros that
4726 define static functions only some of which will get used later in
4727 the module. Starting with clang 3.4, these give a warning unless the
4728 unused attribute is set on them.) Resolves ticket 10904.
4729 - Fix build warnings about missing "a2x" comment when building the
4730 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
4731 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
4733 o Minor bugfixes (client):
4734 - Improve the log message when we can't connect to a hidden service
4735 because all of the hidden service directory nodes hosting its
4736 descriptor are excluded. Improves on our fix for bug 10722, which
4737 was a bugfix on 0.2.0.10-alpha.
4738 - Raise a control port warning when we fail to connect to all of
4739 our bridges. Previously, we didn't inform the controller, and
4740 the bootstrap process would stall. Fixes bug 11069; bugfix on
4742 - Exit immediately when a process-owning controller exits.
4743 Previously, tor relays would wait for a little while after their
4744 controller exited, as if they had gotten an INT signal -- but this
4745 was problematic, since there was no feedback for the user. To do a
4746 clean shutdown, controllers should send an INT signal and give Tor
4747 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
4748 - Stop attempting to connect to bridges before our pluggable
4749 transports are configured (harmless but resulted in some erroneous
4750 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
4751 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
4752 generating incorrect SOCKS5 responses, and confusing client
4753 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
4755 o Minor bugfixes (relays and bridges):
4756 - Avoid crashing on a malformed resolv.conf file when running a
4757 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
4758 - Non-exit relays no longer launch mock DNS requests to check for
4759 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
4760 non-exit relays stopped servicing DNS requests. Fixes bug 965;
4761 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
4762 - Bridges now report complete directory request statistics. Related
4763 to bug 5824; bugfix on 0.2.2.1-alpha.
4764 - Bridges now never collect statistics that were designed for
4765 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
4766 - Stop giving annoying warning messages when we decide not to launch
4767 a pluggable transport proxy that we don't need (because there are
4768 no bridges configured to use it). Resolves ticket 5018; bugfix
4770 - Give the correct URL in the warning message when trying to run a
4771 relay on an ancient version of Windows. Fixes bug 9393.
4773 o Minor bugfixes (backtrace support):
4774 - Support automatic backtraces on more platforms by using the
4775 "-fasynchronous-unwind-tables" compiler option. This option is
4776 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
4777 is on by default and table generation is not. This doesn't yet
4778 add Windows support; only Linux, OSX, and some BSDs are affected.
4779 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
4780 - Avoid strange behavior if two threads hit failed assertions at the
4781 same time and both try to log backtraces at once. (Previously, if
4782 this had happened, both threads would have stored their intermediate
4783 results in the same buffer, and generated junk outputs.) Reported by
4784 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
4785 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
4786 0.2.5.2-alpha; patch from Nick Hopper.
4788 o Minor bugfixes (unit tests):
4789 - Fix a small bug in the unit tests that might have made the tests
4790 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
4791 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
4794 - Remove all remaining code related to version-0 hidden service
4795 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
4796 the rest of bug 10841.
4799 - Document in the manpage that "KBytes" may also be written as
4800 "kilobytes" or "KB", that "Kbits" may also be written as
4801 "kilobits", and so forth. Closes ticket 9222.
4802 - Document that the ClientOnly config option overrides ORPort.
4803 Our old explanation made ClientOnly sound as though it did
4804 nothing at all. Resolves bug 9059.
4805 - Explain that SocksPolicy, DirPolicy, and similar options don't
4806 take port arguments. Fixes the other part of ticket 11108.
4807 - Fix a comment about the rend_server_descriptor_t.protocols field
4808 to more accurately describe its range. Also, make that field
4809 unsigned, to more accurately reflect its usage. Fixes bug 9099;
4810 bugfix on 0.2.1.5-alpha.
4811 - Fix the manpage's description of HiddenServiceAuthorizeClient:
4812 the maximum client name length is 16, not 19. Fixes bug 11118;
4813 bugfix on 0.2.1.6-alpha.
4815 o Code simplifications and refactoring:
4816 - Get rid of router->address, since in all cases it was just the
4817 string representation of router->addr. Resolves ticket 5528.
4819 o Test infrastructure:
4820 - Update to the latest version of tinytest.
4821 - Improve the tinytest implementation of string operation tests so
4822 that comparisons with NULL strings no longer crash the tests; they
4823 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
4826 Changes in version 0.2.4.21 - 2014-02-28
4827 Tor 0.2.4.21 further improves security against potential adversaries who
4828 find breaking 1024-bit crypto doable, and backports several stability
4829 and robustness patches from the 0.2.5 branch.
4831 o Major features (client security):
4832 - When we choose a path for a 3-hop circuit, make sure it contains
4833 at least one relay that supports the NTor circuit extension
4834 handshake. Otherwise, there is a chance that we're building
4835 a circuit that's worth attacking by an adversary who finds
4836 breaking 1024-bit crypto doable, and that chance changes the game
4837 theory. Implements ticket 9777.
4840 - Do not treat streams that fail with reason
4841 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
4842 since it could also indicate an ENETUNREACH connection error. Fixes
4843 part of bug 10777; bugfix on 0.2.4.8-alpha.
4845 o Code simplification and refactoring:
4846 - Remove data structures which were introduced to implement the
4847 CellStatistics option: they are now redundant with the new timestamp
4848 field in the regular packed_cell_t data structure, which we did
4849 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
4852 - Always clear OpenSSL bignums before freeing them -- even bignums
4853 that don't contain secrets. Resolves ticket 10793. Patch by
4855 - Build without warnings under clang 3.4. (We have some macros that
4856 define static functions only some of which will get used later in
4857 the module. Starting with clang 3.4, these give a warning unless the
4858 unused attribute is set on them.) Resolves ticket 10904.
4859 - Update geoip and geoip6 files to the February 7 2014 Maxmind
4860 GeoLite2 Country database.
4863 - Set the listen() backlog limit to the largest actually supported
4864 on the system, not to the value in a header file. Fixes bug 9716;
4865 bugfix on every released Tor.
4866 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
4867 exit node as a NOROUTE error, not an INTERNAL error, since they
4868 can apparently happen when trying to connect to the wrong sort
4869 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
4870 - Fix build warnings about missing "a2x" comment when building the
4871 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
4872 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
4873 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
4874 not entirely remove it from the connection lists. Fixes bug 9602;
4875 bugfix on 0.2.4.4-alpha.
4876 - Fix a segmentation fault in our benchmark code when running with
4877 Fedora's OpenSSL package, or any other OpenSSL that provides
4878 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
4879 - Turn "circuit handshake stats since last time" log messages into a
4880 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
4882 o Documentation fixes:
4883 - Document that all but one DirPort entry must have the NoAdvertise
4884 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
4887 Changes in version 0.2.5.2-alpha - 2014-02-13
4888 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
4889 like the "poor random number generation" fix and the "building too many
4890 circuits" fix. It also further improves security against potential
4891 adversaries who find breaking 1024-bit crypto doable, and launches
4892 pluggable transports on demand (which gets us closer to integrating
4893 pluggable transport support by default -- not to be confused with Tor
4894 bundles enabling pluggable transports and bridges by default).
4896 o Major features (client security):
4897 - When we choose a path for a 3-hop circuit, make sure it contains
4898 at least one relay that supports the NTor circuit extension
4899 handshake. Otherwise, there is a chance that we're building
4900 a circuit that's worth attacking by an adversary who finds
4901 breaking 1024-bit crypto doable, and that chance changes the game
4902 theory. Implements ticket 9777.
4903 - Clients now look at the "usecreatefast" consensus parameter to
4904 decide whether to use CREATE_FAST or CREATE cells for the first hop
4905 of their circuit. This approach can improve security on connections
4906 where Tor's circuit handshake is stronger than the available TLS
4907 connection security levels, but the tradeoff is more computational
4908 load on guard relays. Implements proposal 221. Resolves ticket 9386.
4910 o Major features (bridges):
4911 - Don't launch pluggable transport proxies if we don't have any
4912 bridges configured that would use them. Now we can list many
4913 pluggable transports, and Tor will dynamically start one when it
4914 hears a bridge address that needs it. Resolves ticket 5018.
4915 - The bridge directory authority now assigns status flags (Stable,
4916 Guard, etc) to bridges based on thresholds calculated over all
4917 Running bridges. Now bridgedb can finally make use of its features
4918 to e.g. include at least one Stable bridge in its answers. Fixes
4921 o Major features (other):
4922 - Extend ORCONN controller event to include an "ID" parameter,
4923 and add four new controller event types CONN_BW, CIRC_BW,
4924 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
4925 The new events are emitted in private Tor networks only, with the
4926 goal of being able to better track performance and load during
4927 full-network simulations. Implements proposal 218 and ticket 7359.
4928 - On some platforms (currently: recent OSX versions, glibc-based
4929 platforms that support the ELF format, and a few other
4930 Unix-like operating systems), Tor can now dump stack traces
4931 when a crash occurs or an assertion fails. By default, traces
4932 are dumped to stderr (if possible) and to any logs that are
4933 reporting errors. Implements ticket 9299.
4936 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
4937 not entirely remove it from the connection lists. Fixes bug 9602;
4938 bugfix on 0.2.4.4-alpha.
4939 - Do not treat streams that fail with reason
4940 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
4941 since it could also indicate an ENETUNREACH connection error. Fixes
4942 part of bug 10777; bugfix on 0.2.4.8-alpha.
4944 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
4945 - Do not allow OpenSSL engines to replace the PRNG, even when
4946 HardwareAccel is set. The only default builtin PRNG engine uses
4947 the Intel RDRAND instruction to replace the entire PRNG, and
4948 ignores all attempts to seed it with more entropy. That's
4949 cryptographically stupid: the right response to a new alleged
4950 entropy source is never to discard all previously used entropy
4951 sources. Fixes bug 10402; works around behavior introduced in
4952 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
4954 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
4955 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
4956 - Avoid launching spurious extra circuits when a stream is pending.
4957 This fixes a bug where any circuit that _wasn't_ unusable for new
4958 streams would be treated as if it were, causing extra circuits to
4959 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
4961 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4962 - No longer stop reading or writing on cpuworker connections when
4963 our rate limiting buckets go empty. Now we should handle circuit
4964 handshake requests more promptly. Resolves bug 9731.
4965 - Stop trying to bootstrap all our directory information from
4966 only our first guard. Discovered while fixing bug 9946; bugfix
4969 o Minor features (bridges, pluggable transports):
4970 - Add threshold cutoffs to the networkstatus document created by
4971 the Bridge Authority. Fixes bug 1117.
4972 - On Windows, spawn background processes using the CREATE_NO_WINDOW
4973 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
4974 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
4975 Vidalia set this option for us.) Implements ticket 10297.
4977 o Minor features (security):
4978 - Always clear OpenSSL bignums before freeing them -- even bignums
4979 that don't contain secrets. Resolves ticket 10793. Patch by
4982 o Minor features (config options and command line):
4983 - Add an --allow-missing-torrc commandline option that tells Tor to
4984 run even if the configuration file specified by -f is not available.
4985 Implements ticket 10060.
4986 - Add support for the TPROXY transparent proxying facility on Linux.
4987 See documentation for the new TransProxyType option for more
4988 details. Implementation by "thomo". Closes ticket 10582.
4990 o Minor features (controller):
4991 - Add a new "HS_DESC" controller event that reports activities
4992 related to hidden service descriptors. Resolves ticket 8510.
4993 - New "DROPGUARDS" controller command to forget all current entry
4994 guards. Not recommended for ordinary use, since replacing guards
4995 too frequently makes several attacks easier. Resolves ticket 9934;
4998 o Minor features (build):
4999 - Assume that a user using ./configure --host wants to cross-compile,
5000 and give an error if we cannot find a properly named
5001 tool-chain. Add a --disable-tool-name-check option to proceed
5002 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
5003 - If we run ./configure and the compiler recognizes -fstack-protector
5004 but the linker rejects it, warn the user about a potentially missing
5005 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
5007 o Minor features (testing):
5008 - If Python is installed, "make check" now runs extra tests beyond
5009 the unit test scripts.
5010 - When bootstrapping a test network, sometimes very few relays get
5011 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
5012 specify a set of relays which should be voted Guard regardless of
5013 their uptime or bandwidth. Addresses ticket 9206.
5015 o Minor features (log messages):
5016 - When ServerTransportPlugin is set on a bridge, Tor can write more
5017 useful statistics about bridge use in its extrainfo descriptors,
5018 but only if the Extended ORPort ("ExtORPort") is set too. Add a
5019 log message to inform the user in this case. Resolves ticket 9651.
5020 - When receiving a new controller connection, log the origin address.
5021 Resolves ticket 9698; patch from "sigpipe".
5022 - When logging OpenSSL engine status at startup, log the status of
5023 more engines. Fixes ticket 10043; patch from Joshua Datko.
5024 - Turn "circuit handshake stats since last time" log messages into a
5025 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
5027 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
5028 - Improve the circuit queue out-of-memory handler. Previously, when
5029 we ran low on memory, we'd close whichever circuits had the most
5030 queued cells. Now, we close those that have the *oldest* queued
5031 cells, on the theory that those are most responsible for us
5032 running low on memory. Based on analysis from a forthcoming paper
5033 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
5034 - Generate bootstrapping status update events correctly when fetching
5035 microdescriptors. Fixes bug 9927.
5036 - Update to the October 2 2013 Maxmind GeoLite Country database.
5038 o Minor bugfixes (clients):
5039 - When closing a channel that has already been open, do not close
5040 pending circuits that were waiting to connect to the same relay.
5041 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
5044 o Minor bugfixes (relays):
5045 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
5046 exit node as a NOROUTE error, not an INTERNAL error, since they
5047 can apparently happen when trying to connect to the wrong sort
5048 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
5050 o Minor bugfixes (bridges):
5051 - Fix a bug where the first connection works to a bridge that uses a
5052 pluggable transport with client-side parameters, but we don't send
5053 the client-side parameters on subsequent connections. (We don't
5054 use any pluggable transports with client-side parameters yet,
5055 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
5056 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
5058 o Minor bugfixes (node selection):
5059 - If ExcludeNodes is set, consider non-excluded hidden service
5060 directory servers before excluded ones. Do not consider excluded
5061 hidden service directory servers at all if StrictNodes is
5062 set. (Previously, we would sometimes decide to connect to those
5063 servers, and then realize before we initiated a connection that
5064 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
5066 - If we set the ExitNodes option but it doesn't include any nodes
5067 that have the Exit flag, we would choose not to bootstrap. Now we
5068 bootstrap so long as ExitNodes includes nodes which can exit to
5069 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
5071 o Minor bugfixes (controller and command-line):
5072 - If changing a config option via "setconf" fails in a recoverable
5073 way, we used to nonetheless write our new control ports to the
5074 file described by the "ControlPortWriteToFile" option. Now we only
5075 write out that file if we successfully switch to the new config
5076 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
5077 - When a command-line option such as --version or --help that
5078 ordinarily implies --hush appears on the command line along with
5079 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
5080 only if it appeared later on the command line. Fixes bug 9578;
5081 bugfix on 0.2.5.1-alpha.
5083 o Minor bugfixes (code correctness):
5084 - Previously we used two temporary files when writing descriptors to
5085 disk; now we only use one. Fixes bug 1376.
5086 - Remove an erroneous (but impossible and thus harmless) pointer
5087 comparison that would have allowed compilers to skip a bounds
5088 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
5089 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
5090 - Fix an always-true assertion in pluggable transports code so it
5091 actually checks what it was trying to check. Fixes bug 10046;
5092 bugfix on 0.2.3.9-alpha. Found by "dcb".
5094 o Minor bugfixes (protocol correctness):
5095 - When receiving a VERSIONS cell with an odd number of bytes, close
5096 the connection immediately since the cell is malformed. Fixes bug
5097 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
5100 o Minor bugfixes (build):
5101 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
5102 turned off (that is, without support for v2 link handshakes). Fixes
5103 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
5104 - Fix compilation warnings and startup issues when running with
5105 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
5107 - Fix compilation on Solaris 9, which didn't like us having an
5108 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
5110 o Minor bugfixes (testing):
5111 - Fix a segmentation fault in our benchmark code when running with
5112 Fedora's OpenSSL package, or any other OpenSSL that provides
5113 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
5115 o Minor bugfixes (log messages):
5116 - Fix a bug where clients using bridges would report themselves
5117 as 50% bootstrapped even without a live consensus document.
5118 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
5119 - Suppress a warning where, if there's only one directory authority
5120 in the network, we would complain that votes and signatures cannot
5121 be uploaded to other directory authorities. Fixes bug 10842;
5122 bugfix on 0.2.2.26-beta.
5123 - Report bootstrapping progress correctly when we're downloading
5124 microdescriptors. We had updated our "do we have enough microdescs
5125 to begin building circuits?" logic most recently in 0.2.4.10-alpha
5126 (see bug 5956), but we left the bootstrap status event logic at
5127 "how far through getting 1/4 of them are we?" Fixes bug 9958;
5128 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
5130 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
5131 - Avoid a crash bug when starting with a corrupted microdescriptor
5132 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
5133 - If we fail to dump a previously cached microdescriptor to disk, avoid
5134 freeing duplicate data later on. Fixes bug 10423; bugfix on
5135 0.2.4.13-alpha. Spotted by "bobnomnom".
5137 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
5138 - Correctly log long IPv6 exit policies, instead of truncating them
5139 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
5140 - Our default TLS ecdhe groups were backwards: we meant to be using
5141 P224 for relays (for performance win) and P256 for bridges (since
5142 it is more common in the wild). Instead we had it backwards. After
5143 reconsideration, we decided that the default should be P256 on all
5144 hosts, since its security is probably better, and since P224 is
5145 reportedly used quite little in the wild. Found by "skruffy" on
5146 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
5147 - Free directory authority certificate download statuses on exit
5148 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
5150 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
5151 - If the guard we choose first doesn't answer, we would try the
5152 second guard, but once we connected to the second guard we would
5153 abandon it and retry the first one, slowing down bootstrapping.
5154 The fix is to treat all our initially chosen guards as acceptable
5155 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
5156 - Fix an assertion failure that would occur when disabling the
5157 ORPort setting on a running Tor process while accounting was
5158 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
5159 - When examining the list of network interfaces to find our address,
5160 do not consider non-running or disabled network interfaces. Fixes
5161 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
5162 - Avoid an off-by-one error when checking buffer boundaries when
5163 formatting the exit status of a pluggable transport helper.
5164 This is probably not an exploitable bug, but better safe than
5165 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
5168 o Removed code and features:
5169 - Clients now reject any directory authority certificates lacking
5170 a dir-key-crosscert element. These have been included since
5171 0.2.1.9-alpha, so there's no real reason for them to be optional
5172 any longer. Completes proposal 157. Resolves ticket 10162.
5173 - Remove all code that existed to support the v2 directory system,
5174 since there are no longer any v2 directory authorities. Resolves
5176 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
5177 options, which were used for designating authorities as "Hidden
5178 service authorities". There has been no use of hidden service
5179 authorities since 0.2.2.1-alpha, when we stopped uploading or
5180 downloading v0 hidden service descriptors. Fixes bug 10881; also
5181 part of a fix for bug 10841.
5183 o Code simplification and refactoring:
5184 - Remove some old fallback code designed to keep Tor clients working
5185 in a network with only two working relays. Elsewhere in the code we
5186 have long since stopped supporting such networks, so there wasn't
5187 much point in keeping it around. Addresses ticket 9926.
5188 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
5189 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
5190 - Remove data structures which were introduced to implement the
5191 CellStatistics option: they are now redundant with the addition
5192 of a timestamp to the regular packed_cell_t data structure, which
5193 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
5196 o Documentation (man page) fixes:
5197 - Update manpage to describe some of the files you can expect to
5198 find in Tor's DataDirectory. Addresses ticket 9839.
5199 - Document that all but one DirPort entry must have the NoAdvertise
5200 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
5202 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
5203 - Clarify the usage and risks of setting the ContactInfo torrc line
5204 for your relay or bridge. Resolves ticket 9854.
5205 - Add anchors to the manpage so we can link to the html version of
5206 the documentation for specific options. Resolves ticket 9866.
5207 - Replace remaining references to DirServer in man page and
5208 log entries. Resolves ticket 10124.
5211 - Make the "tor-gencert" tool used by directory authority operators
5212 create 2048-bit signing keys by default (rather than 1024-bit, since
5213 1024-bit is uncomfortably small these days). Addresses ticket 10324.
5216 Changes in version 0.2.4.20 - 2013-12-22
5217 Tor 0.2.4.20 fixes potentially poor random number generation for users
5218 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
5219 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
5220 and 4) have no state file in their DataDirectory (as would happen on
5221 first start). Users who generated relay or hidden service identity
5222 keys in such a situation should discard them and generate new ones.
5224 This release also fixes a logic error that caused Tor clients to build
5225 many more preemptive circuits than they actually need.
5228 - Do not allow OpenSSL engines to replace the PRNG, even when
5229 HardwareAccel is set. The only default builtin PRNG engine uses
5230 the Intel RDRAND instruction to replace the entire PRNG, and
5231 ignores all attempts to seed it with more entropy. That's
5232 cryptographically stupid: the right response to a new alleged
5233 entropy source is never to discard all previously used entropy
5234 sources. Fixes bug 10402; works around behavior introduced in
5235 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
5237 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
5238 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
5239 - Avoid launching spurious extra circuits when a stream is pending.
5240 This fixes a bug where any circuit that _wasn't_ unusable for new
5241 streams would be treated as if it were, causing extra circuits to
5242 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
5245 - Avoid a crash bug when starting with a corrupted microdescriptor
5246 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
5247 - If we fail to dump a previously cached microdescriptor to disk, avoid
5248 freeing duplicate data later on. Fixes bug 10423; bugfix on
5249 0.2.4.13-alpha. Spotted by "bobnomnom".
5252 Changes in version 0.2.4.19 - 2013-12-11
5253 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
5254 (1986-2013). Aaron worked on diverse projects including helping to guide
5255 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
5256 transparency to the U.S government's PACER documents, and contributing
5257 design and development for Tor and Tor2Web. Aaron was one of the latest
5258 martyrs in our collective fight for civil liberties and human rights,
5259 and his death is all the more painful because he was one of us.
5261 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
5262 a new circuit handshake and link encryption that use ECC to provide
5263 better security and efficiency; makes relays better manage circuit
5264 creation requests; uses "directory guards" to reduce client enumeration
5265 risks; makes bridges collect and report statistics about the pluggable
5266 transports they support; cleans up and improves our geoip database;
5267 gets much closer to IPv6 support for clients, bridges, and relays; makes
5268 directory authorities use measured bandwidths rather than advertised
5269 ones when computing flags and thresholds; disables client-side DNS
5270 caching to reduce tracking risks; and fixes a big bug in bridge
5271 reachability testing. This release introduces two new design
5272 abstractions in the code: a new "channel" abstraction between circuits
5273 and or_connections to allow for implementing alternate relay-to-relay
5274 transports, and a new "circuitmux" abstraction storing the queue of
5275 circuits for a channel. The release also includes many stability,
5276 security, and privacy fixes.
5279 Changes in version 0.2.4.18-rc - 2013-11-16
5280 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
5281 series. It takes a variety of fixes from the 0.2.5.x branch to improve
5282 stability, performance, and better handling of edge cases.
5285 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
5286 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
5287 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
5288 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
5289 them to solve bug 6033.)
5292 - No longer stop reading or writing on cpuworker connections when
5293 our rate limiting buckets go empty. Now we should handle circuit
5294 handshake requests more promptly. Resolves bug 9731.
5295 - If we are unable to save a microdescriptor to the journal, do not
5296 drop it from memory and then reattempt downloading it. Fixes bug
5297 9645; bugfix on 0.2.2.6-alpha.
5298 - Stop trying to bootstrap all our directory information from
5299 only our first guard. Discovered while fixing bug 9946; bugfix
5301 - The new channel code sometimes lost track of in-progress circuits,
5302 causing long-running clients to stop building new circuits. The
5303 fix is to always call circuit_n_chan_done(chan, 0) from
5304 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
5306 o Minor bugfixes (on 0.2.4.x):
5307 - Correctly log long IPv6 exit policies, instead of truncating them
5308 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
5309 - Our default TLS ecdhe groups were backwards: we meant to be using
5310 P224 for relays (for performance win) and P256 for bridges (since
5311 it is more common in the wild). Instead we had it backwards. After
5312 reconsideration, we decided that the default should be P256 on all
5313 hosts, since its security is probably better, and since P224 is
5314 reportedly used quite little in the wild. Found by "skruffy" on
5315 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
5316 - Free directory authority certificate download statuses on exit
5317 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
5319 o Minor bugfixes (on 0.2.3.x and earlier):
5320 - If the guard we choose first doesn't answer, we would try the
5321 second guard, but once we connected to the second guard we would
5322 abandon it and retry the first one, slowing down bootstrapping.
5323 The fix is to treat all our initially chosen guards as acceptable
5324 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
5325 - Fix an assertion failure that would occur when disabling the
5326 ORPort setting on a running Tor process while accounting was
5327 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
5328 - When examining the list of network interfaces to find our address,
5329 do not consider non-running or disabled network interfaces. Fixes
5330 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
5331 - Avoid an off-by-one error when checking buffer boundaries when
5332 formatting the exit status of a pluggable transport helper.
5333 This is probably not an exploitable bug, but better safe than
5334 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
5337 o Minor features (protecting client timestamps):
5338 - Clients no longer send timestamps in their NETINFO cells. These were
5339 not used for anything, and they provided one small way for clients
5340 to be distinguished from each other as they moved from network to
5341 network or behind NAT. Implements part of proposal 222.
5342 - Clients now round timestamps in INTRODUCE cells down to the nearest
5343 10 minutes. If a new Support022HiddenServices option is set to 0, or
5344 if it's set to "auto" and the feature is disabled in the consensus,
5345 the timestamp is sent as 0 instead. Implements part of proposal 222.
5346 - Stop sending timestamps in AUTHENTICATE cells. This is not such
5347 a big deal from a security point of view, but it achieves no actual
5348 good purpose, and isn't needed. Implements part of proposal 222.
5349 - Reduce down accuracy of timestamps in hidden service descriptors.
5350 Implements part of proposal 222.
5352 o Minor features (other):
5353 - Improve the circuit queue out-of-memory handler. Previously, when
5354 we ran low on memory, we'd close whichever circuits had the most
5355 queued cells. Now, we close those that have the *oldest* queued
5356 cells, on the theory that those are most responsible for us
5357 running low on memory. Based on analysis from a forthcoming paper
5358 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
5359 - Generate bootstrapping status update events correctly when fetching
5360 microdescriptors. Fixes bug 9927.
5361 - Update to the October 2 2013 Maxmind GeoLite Country database.
5363 o Documentation fixes:
5364 - Clarify the usage and risks of setting the ContactInfo torrc line
5365 for your relay or bridge. Resolves ticket 9854.
5366 - Add anchors to the manpage so we can link to the html version of
5367 the documentation for specific options. Resolves ticket 9866.
5368 - Replace remaining references to DirServer in man page and
5369 log entries. Resolves ticket 10124.
5372 Changes in version 0.2.5.1-alpha - 2013-10-02
5373 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
5374 on Linux, allows bridges that offer pluggable transports to report usage
5375 statistics, fixes many issues to make testing easier, and provides
5376 a pile of minor features and bugfixes that have been waiting for a
5377 release of the new branch.
5379 This is the first alpha release in a new series, so expect there to
5380 be bugs. Users who would rather test out a more stable branch should
5381 stay with 0.2.4.x for now.
5383 o Major features (security):
5384 - Use the seccomp2 syscall filtering facility on Linux to limit
5385 which system calls Tor can invoke. This is an experimental,
5386 Linux-only feature to provide defense-in-depth against unknown
5387 attacks. To try turning it on, set "Sandbox 1" in your torrc
5388 file. Please be ready to report bugs. We hope to add support
5389 for better sandboxing in the future, including more fine-grained
5390 filters, better division of responsibility, and support for more
5391 platforms. This work has been done by Cristian-Matei Toader for
5392 Google Summer of Code.
5393 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
5394 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
5395 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
5396 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
5397 them to solve bug 6033.)
5399 o Major features (other):
5400 - Add support for passing arguments to managed pluggable transport
5401 proxies. Implements ticket 3594.
5402 - Bridges now track GeoIP information and the number of their users
5403 even when pluggable transports are in use, and report usage
5404 statistics in their extra-info descriptors. Resolves tickets 4773
5406 - Make testing Tor networks bootstrap better: lower directory fetch
5407 retry schedules and maximum interval without directory requests,
5408 and raise maximum download tries. Implements ticket 6752.
5409 - Add make target 'test-network' to run tests on a Chutney network.
5410 Implements ticket 8530.
5411 - The ntor handshake is now on-by-default, no matter what the
5412 directory authorities recommend. Implements ticket 8561.
5415 - Instead of writing destroy cells directly to outgoing connection
5416 buffers, queue them and intersperse them with other outgoing cells.
5417 This can prevent a set of resource starvation conditions where too
5418 many pending destroy cells prevent data cells from actually getting
5419 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
5420 bugfix on 0.2.0.1-alpha.
5421 - If we are unable to save a microdescriptor to the journal, do not
5422 drop it from memory and then reattempt downloading it. Fixes bug
5423 9645; bugfix on 0.2.2.6-alpha.
5424 - The new channel code sometimes lost track of in-progress circuits,
5425 causing long-running clients to stop building new circuits. The
5426 fix is to always call circuit_n_chan_done(chan, 0) from
5427 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
5430 - Tor now builds each source file in two modes: a mode that avoids
5431 exposing identifiers needlessly, and another mode that exposes
5432 more identifiers for testing. This lets the compiler do better at
5433 optimizing the production code, while enabling us to take more
5434 radical measures to let the unit tests test things.
5435 - The production builds no longer include functions used only in
5436 the unit tests; all functions exposed from a module only for
5437 unit-testing are now static in production builds.
5438 - Add an --enable-coverage configuration option to make the unit
5439 tests (and a new src/or/tor-cov target) to build with gcov test
5443 - We now have rudimentary function mocking support that our unit
5444 tests can use to test functions in isolation. Function mocking
5445 lets the tests temporarily replace a function's dependencies with
5446 stub functions, so that the tests can check the function without
5447 invoking the other functions it calls.
5448 - Add more unit tests for the <circid,channel>->circuit map, and
5449 the destroy-cell-tracking code to fix bug 7912.
5450 - Unit tests for failing cases of the TAP onion handshake.
5451 - More unit tests for address-manipulation functions.
5453 o Minor features (protecting client timestamps):
5454 - Clients no longer send timestamps in their NETINFO cells. These were
5455 not used for anything, and they provided one small way for clients
5456 to be distinguished from each other as they moved from network to
5457 network or behind NAT. Implements part of proposal 222.
5458 - Clients now round timestamps in INTRODUCE cells down to the nearest
5459 10 minutes. If a new Support022HiddenServices option is set to 0, or
5460 if it's set to "auto" and the feature is disabled in the consensus,
5461 the timestamp is sent as 0 instead. Implements part of proposal 222.
5462 - Stop sending timestamps in AUTHENTICATE cells. This is not such
5463 a big deal from a security point of view, but it achieves no actual
5464 good purpose, and isn't needed. Implements part of proposal 222.
5465 - Reduce down accuracy of timestamps in hidden service descriptors.
5466 Implements part of proposal 222.
5468 o Minor features (config options):
5469 - Config (torrc) lines now handle fingerprints which are missing
5470 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
5471 - Support a --dump-config option to print some or all of the
5472 configured options. Mainly useful for debugging the command-line
5473 option parsing code. Helps resolve ticket 4647.
5474 - Raise awareness of safer logging: notify user of potentially
5475 unsafe config options, like logging more verbosely than severity
5476 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
5477 - Add a new configuration option TestingV3AuthVotingStartOffset
5478 that bootstraps a network faster by changing the timing for
5479 consensus votes. Addresses ticket 8532.
5480 - Add a new torrc option "ServerTransportOptions" that allows
5481 bridge operators to pass configuration parameters to their
5482 pluggable transports. Resolves ticket 8929.
5483 - The config (torrc) file now accepts bandwidth and space limits in
5484 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
5485 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
5488 o Minor features (build):
5489 - Add support for `--library-versions` flag. Implements ticket 6384.
5490 - Return the "unexpected sendme" warnings to a warn severity, but make
5491 them rate limited, to help diagnose ticket 8093.
5492 - Detect a missing asciidoc, and warn the user about it, during
5493 configure rather than at build time. Fixes issue 6506. Patch from
5496 o Minor features (other):
5497 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
5498 sockets in a single system call. Implements ticket 5129.
5499 - Log current accounting state (bytes sent and received + remaining
5500 time for the current accounting period) in the relay's heartbeat
5501 message. Implements ticket 5526; patch from Peter Retzlaff.
5502 - Implement the TRANSPORT_LAUNCHED control port event that
5503 notifies controllers about new launched pluggable
5504 transports. Resolves ticket 5609.
5505 - If we're using the pure-C 32-bit curve25519_donna implementation
5506 of curve25519, build it with the -fomit-frame-pointer option to
5507 make it go faster on register-starved hosts. This improves our
5508 handshake performance by about 6% on i386 hosts without nacl.
5510 - Update to the September 4 2013 Maxmind GeoLite Country database.
5513 - Set the listen() backlog limit to the largest actually supported
5514 on the system, not to the value in a header file. Fixes bug 9716;
5515 bugfix on every released Tor.
5516 - No longer accept malformed http headers when parsing urls from
5517 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
5518 bugfix on 0.0.6pre1.
5519 - In munge_extrainfo_into_routerinfo(), check the return value of
5520 memchr(). This would have been a serious issue if we ever passed
5521 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
5523 - On the chance that somebody manages to build Tor on a
5524 platform where time_t is unsigned, correct the way that
5525 microdesc_add_to_cache() handles negative time arguments.
5526 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
5527 - Reject relative control socket paths and emit a warning. Previously,
5528 single-component control socket paths would be rejected, but Tor
5529 would not log why it could not validate the config. Fixes bug 9258;
5530 bugfix on 0.2.3.16-alpha.
5532 o Minor bugfixes (command line):
5533 - Use a single command-line parser for parsing torrc options on the
5534 command line and for finding special command-line options to avoid
5535 inconsistent behavior for torrc option arguments that have the same
5536 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
5538 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
5539 9573; bugfix on 0.0.9pre5.
5541 o Minor fixes (build, auxiliary programs):
5542 - Stop preprocessing the "torify" script with autoconf, since
5543 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
5545 - The tor-fw-helper program now follows the standard convention and
5546 exits with status code "0" on success. Fixes bug 9030; bugfix on
5547 0.2.3.1-alpha. Patch by Arlo Breault.
5548 - Corrected ./configure advice for what openssl dev package you should
5549 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
5551 o Minor code improvements:
5552 - Remove constants and tests for PKCS1 padding; it's insecure and
5553 shouldn't be used for anything new. Fixes bug 8792; patch
5555 - Remove instances of strcpy() from the unit tests. They weren't
5556 hurting anything, since they were only in the unit tests, but it's
5557 embarassing to have strcpy() in the code at all, and some analysis
5558 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
5559 0.2.3.8-alpha. Patch from Arlo Breault.
5562 - Remove migration code from when we renamed the "cached-routers"
5563 file to "cached-descriptors" back in 0.2.0.8-alpha. This
5564 incidentally resolves ticket 6502 by cleaning up the related code
5565 a bit. Patch from Akshay Hebbar.
5567 o Code simplification and refactoring:
5568 - Extract the common duplicated code for creating a subdirectory
5569 of the data directory and writing to a file in it. Fixes ticket
5570 4282; patch from Peter Retzlaff.
5571 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
5572 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
5573 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
5574 - Add a set of accessor functions for the circuit timeout data
5575 structure. Fixes ticket 6153; patch from "piet".
5576 - Clean up exit paths from connection_listener_new(). Closes ticket
5577 8789. Patch from Arlo Breault.
5578 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
5579 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
5580 - Use a doubly-linked list to implement the global circuit list.
5581 Resolves ticket 9108. Patch from Marek Majkowski.
5582 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
5585 Changes in version 0.2.4.17-rc - 2013-09-05
5586 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
5587 series. It adds an emergency step to help us tolerate the massive
5588 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
5589 circuit-level handshakes now effectively jump the queue compared to
5590 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
5591 big bug hindering bridge reachability tests.
5594 - Relays now process the new "NTor" circuit-level handshake requests
5595 with higher priority than the old "TAP" circuit-level handshake
5596 requests. We still process some TAP requests to not totally starve
5597 0.2.3 clients when NTor becomes popular. A new consensus parameter
5598 "NumNTorsPerTAP" lets us tune the balance later if we need to.
5599 Implements ticket 9574.
5602 - If the circuit build timeout logic is disabled (via the consensus,
5603 or because we are an authority), then don't build testing circuits.
5604 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
5605 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
5606 previously they did not, which prevented them from receiving
5607 successful connections from relays for self-test or bandwidth
5608 testing. Also, when a relay is extending a circuit to a bridge,
5609 it needs to send a NETINFO cell, even when the bridge hasn't sent
5610 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
5611 - If the time to download the next old-style networkstatus is in
5612 the future, do not decline to consider whether to download the
5613 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
5617 - Avoid double-closing the listener socket in our socketpair()
5618 replacement (used on Windows) in the case where the addresses on
5619 our opened sockets don't match what we expected. Fixes bug 9400;
5620 bugfix on 0.0.2pre7. Found by Coverity.
5622 o Minor fixes (config options):
5623 - Avoid overflows when the user sets MaxCircuitDirtiness to a
5624 ridiculously high value, by imposing a (ridiculously high) 30-day
5625 maximum on MaxCircuitDirtiness.
5626 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
5627 message is logged at notice, not at info.
5628 - Warn and fail if a server is configured not to advertise any
5629 ORPorts at all. (We need *something* to put in our descriptor,
5630 or we just won't work.)
5633 - Track how many "TAP" and "NTor" circuit handshake requests we get,
5634 and how many we complete, and log it every hour to help relay
5635 operators follow trends in network load. Addresses ticket 9658.
5636 - Update to the August 7 2013 Maxmind GeoLite Country database.
5639 Changes in version 0.2.4.16-rc - 2013-08-10
5640 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
5641 series. It fixes several crash bugs in the 0.2.4 branch.
5644 - Fix a bug in the voting algorithm that could yield incorrect results
5645 when a non-naming authority declared too many flags. Fixes bug 9200;
5646 bugfix on 0.2.0.3-alpha.
5647 - Fix an uninitialized read that could in some cases lead to a remote
5648 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
5649 Anybody running a hidden service on the experimental 0.2.4.x
5650 branch should upgrade. (This is, so far as we know, unrelated to
5652 - Avoid an assertion failure when processing DNS replies without the
5653 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
5654 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
5655 0.2.4.15-rc. Found by stem integration tests.
5658 - Fix an invalid memory read that occured when a pluggable
5659 transport proxy failed its configuration protocol.
5660 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
5661 - When evaluating whether to use a connection that we haven't
5662 decided is canonical using a recent link protocol version,
5663 decide that it's canonical only if it used address _does_
5664 match the desired address. Fixes bug 9309; bugfix on
5665 0.2.4.4-alpha. Reported by skruffy.
5666 - Make the default behavior of NumDirectoryGuards be to track
5667 NumEntryGuards. Now a user who changes only NumEntryGuards will get
5668 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
5669 - Fix a spurious compilation warning with some older versions of
5670 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
5673 - Update to the July 3 2013 Maxmind GeoLite Country database.
5676 Changes in version 0.2.4.15-rc - 2013-07-01
5677 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
5678 series. It fixes a few smaller bugs, but generally appears stable.
5679 Please test it and let us know whether it is!
5682 - When receiving a new configuration file via the control port's
5683 LOADCONF command, do not treat the defaults file as absent.
5684 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
5687 - Issue a warning when running with the bufferevents backend enabled.
5688 It's still not stable, and people should know that they're likely
5689 to hit unexpected problems. Closes ticket 9147.
5692 Changes in version 0.2.4.14-alpha - 2013-06-18
5693 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
5694 present in 0.2.4.13-alpha.
5697 - When we have too much memory queued in circuits (according to a new
5698 MaxMemInCellQueues option), close the circuits consuming the most
5699 memory. This prevents us from running out of memory as a relay if
5700 circuits fill up faster than they can be drained. Fixes bug 9063;
5701 bugfix on the 54th commit of Tor. This bug is a further fix beyond
5702 bug 6252, whose fix was merged into 0.2.3.21-rc.
5704 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
5705 where we tried to solve this issue simply by imposing an upper limit
5706 on the number of queued cells for a single circuit. That approach
5707 proved to be problematic, since there are ways to provoke clients to
5708 send a number of cells in excess of any such reasonable limit. Fixes
5709 bug 9072; bugfix on 0.2.4.13-alpha.
5711 - Limit hidden service descriptors to at most ten introduction
5712 points, to slow one kind of guard enumeration. Fixes bug 9002;
5713 bugfix on 0.1.1.11-alpha.
5716 Changes in version 0.2.4.13-alpha - 2013-06-14
5717 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
5718 vulnerabilities, makes socks5 username/password circuit isolation
5719 actually actually work (this time for sure!), and cleans up a bunch
5720 of other issues in preparation for a release candidate.
5722 o Major bugfixes (robustness):
5723 - Close any circuit that has too many cells queued on it. Fixes
5724 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
5725 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
5726 - Prevent the get_freelists() function from running off the end of
5727 the list of freelists if it somehow gets an unrecognized
5728 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
5730 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
5731 when an exit connection with optimistic data succeeds immediately
5732 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
5734 - Fix a directory authority crash bug when building a consensus
5735 using an older consensus as its basis. Fixes bug 8833. Bugfix
5739 - Avoid a memory leak where we would leak a consensus body when we
5740 find that a consensus which we couldn't previously verify due to
5741 missing certificates is now verifiable. Fixes bug 8719; bugfix
5743 - We used to always request authority certificates by identity digest,
5744 meaning we'd get the newest one even when we wanted one with a
5745 different signing key. Then we would complain about being given
5746 a certificate we already had, and never get the one we really
5747 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
5748 resource to request the one we want. Fixes bug 5595; bugfix on
5750 - Follow the socks5 protocol when offering username/password
5751 authentication. The fix for bug 8117 exposed this bug, and it
5752 turns out real-world applications like Pidgin do care. Bugfix on
5753 0.2.3.2-alpha; fixes bug 8879.
5754 - Prevent failures on Windows Vista and later when rebuilding the
5755 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
5756 bugfix on 0.2.4.12-alpha.
5759 - Fix an impossible buffer overrun in the AES unit tests. Fixes
5760 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
5761 - If for some reason we fail to write a microdescriptor while
5762 rebuilding the cache, do not let the annotations from that
5763 microdescriptor linger in the cache file, and do not let the
5764 microdescriptor stay recorded as present in its old location.
5765 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
5766 - Fix a memory leak that would occur whenever a configuration
5767 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
5768 - Paste the description for PathBias parameters from the man
5769 page into or.h, so the code documents them too. Fixes bug 7982;
5770 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
5771 - Relays now treat a changed IPv6 ORPort as sufficient reason to
5772 publish an updated descriptor. Fixes bug 6026; bugfix on
5774 - When launching a resolve request on behalf of an AF_UNIX control
5775 socket, omit the address field of the new entry connection, used in
5776 subsequent controller events, rather than letting tor_dup_addr()
5777 set it to "<unknown address type>". Fixes bug 8639; bugfix on
5780 o Minor bugfixes (log messages):
5781 - Fix a scaling issue in the path bias accounting code that
5782 resulted in "Bug:" log messages from either
5783 pathbias_scale_close_rates() or pathbias_count_build_success().
5784 This represents a bugfix on a previous bugfix: the original fix
5785 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
5787 - Give a less useless error message when the user asks for an IPv4
5788 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
5792 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
5793 to tolerate bug 8093 for now.
5794 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
5795 in directory authority votes to describe whether they have enough
5796 measured bandwidths to ignore advertised (relay descriptor)
5797 bandwidth claims. Resolves ticket 8711.
5798 - Update to the June 5 2013 Maxmind GeoLite Country database.
5800 o Removed documentation:
5801 - Remove some of the older contents of doc/ as obsolete; move others
5802 to torspec.git. Fixes bug 8965.
5804 o Code simplification and refactoring:
5805 - Avoid using character buffers when constructing most directory
5806 objects: this approach was unwieldy and error-prone. Instead,
5807 build smartlists of strings, and concatenate them when done.
5810 Changes in version 0.2.4.12-alpha - 2013-04-18
5811 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
5812 process for lengthening the guard rotation period, makes directory
5813 authority opinions in the consensus a bit less gameable, makes socks5
5814 username/password circuit isolation actually work, and fixes a wide
5815 variety of other issues.
5818 - Raise the default time that a client keeps an entry guard from
5819 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
5820 2012 paper. (We would make it even longer, but we need better client
5821 load balancing first.) Also, make the guard lifetime controllable
5822 via a new GuardLifetime torrc option and a GuardLifetime consensus
5823 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
5824 - Directory authorities now prefer using measured bandwidths to
5825 advertised ones when computing flags and thresholds. Resolves
5827 - Directory authorities that have more than a threshold number
5828 of relays with measured bandwidths now treat relays with unmeasured
5829 bandwidths as having bandwidth 0. Resolves ticket 8435.
5831 o Major bugfixes (assert / resource use):
5832 - Avoid a bug where our response to TLS renegotiation under certain
5833 network conditions could lead to a busy-loop, with 100% CPU
5834 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
5835 - Avoid an assertion when we discover that we'd like to write a cell
5836 onto a closing connection: just discard the cell. Fixes another
5837 case of bug 7350; bugfix on 0.2.4.4-alpha.
5839 o Major bugfixes (client-side privacy):
5840 - When we mark a circuit as unusable for new circuits, have it
5841 continue to be unusable for new circuits even if MaxCircuitDirtiness
5842 is increased too much at the wrong time, or the system clock jumps
5843 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
5844 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
5845 which have resolved to internal addresses") is set, apply that
5846 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
5847 - When an exit relay rejects a stream with reason "exit policy", but
5848 we only know an exit policy summary (e.g. from the microdesc
5849 consensus) for it, do not mark the relay as useless for all exiting.
5850 Instead, mark just the circuit as unsuitable for that particular
5851 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
5852 - Allow applications to get proper stream isolation with
5853 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
5854 username/password authentication also offer "no authentication". Tor
5855 had previously preferred "no authentication", so the applications
5856 never actually sent Tor their auth details. Now Tor selects
5857 username/password authentication if it's offered. You can disable
5858 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
5859 bug 8117; bugfix on 0.2.3.3-alpha.
5861 o Major bugfixes (other):
5862 - When unable to find any working directory nodes to use as a
5863 directory guard, give up rather than adding the same non-working
5864 nodes to the directory guard list over and over. Fixes bug 8231;
5865 bugfix on 0.2.4.8-alpha.
5868 - Reject as invalid most directory objects containing a NUL.
5869 Belt-and-suspender fix for bug 8037.
5870 - In our testsuite, create temporary directories with a bit more
5871 entropy in their name to make name collisions less likely. Fixes
5873 - Add CACHED keyword to ADDRMAP events in the control protocol
5874 to indicate whether a DNS result will be cached or not. Resolves
5876 - Update to the April 3 2013 Maxmind GeoLite Country database.
5878 o Minor features (build):
5879 - Detect and reject attempts to build Tor with threading support
5880 when OpenSSL has been compiled without threading support.
5882 - Clarify that when autoconf is checking for nacl, it is checking
5883 specifically for nacl with a fast curve25519 implementation.
5885 - Warn if building on a platform with an unsigned time_t: there
5886 are too many places where Tor currently assumes that time_t can
5887 hold negative values. We'd like to fix them all, but probably
5890 o Minor bugfixes (build):
5891 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
5892 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
5893 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
5894 - Add the old src/or/micro-revision.i filename to CLEANFILES.
5895 On the off chance that somebody has one, it will go away as soon
5896 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
5897 - Build Tor correctly on 32-bit platforms where the compiler can build
5898 but not run code using the "uint128_t" construction. Fixes bug 8587;
5899 bugfix on 0.2.4.8-alpha.
5900 - Fix compilation warning with some versions of clang that would
5901 prefer the -Wswitch-enum compiler flag to warn about switch
5902 statements with missing enum values, even if those switch
5903 statements have a "default:" statement. Fixes bug 8598; bugfix
5906 o Minor bugfixes (protocol):
5907 - Fix the handling of a TRUNCATE cell when it arrives while the
5908 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
5909 - Fix a misframing issue when reading the version numbers in a
5910 VERSIONS cell. Previously we would recognize [00 01 00 02] as
5911 'version 1, version 2, and version 0x100', when it should have
5912 only included versions 1 and 2. Fixes bug 8059; bugfix on
5913 0.2.0.10-alpha. Reported pseudonymously.
5914 - Make the format and order of STREAM events for DNS lookups
5915 consistent among the various ways to launch DNS lookups. Fixes
5916 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
5917 - Correct our check for which versions of Tor support the EXTEND2
5918 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
5919 later, when support was really added in version 0.2.4.8-alpha.
5920 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
5922 o Minor bugfixes (other):
5923 - Correctly store microdescriptors and extrainfo descriptors with
5924 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
5925 Bug reported by "cypherpunks".
5926 - Increase the width of the field used to remember a connection's
5927 link protocol version to two bytes. Harmless for now, since the
5928 only currently recognized versions are one byte long. Reported
5929 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
5930 - If the state file's path bias counts are invalid (presumably from a
5931 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
5932 additional checks and log messages to the scaling of Path Bias
5933 counts, in case there still are remaining issues with scaling.
5934 Should help resolve bug 8235.
5935 - Eliminate several instances where we use "Nickname=ID" to refer to
5936 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
5937 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
5938 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
5940 o Minor bugfixes (syscalls):
5941 - Always check the return values of functions fcntl() and
5942 setsockopt(). We don't believe these are ever actually failing in
5943 practice, but better safe than sorry. Also, checking these return
5944 values should please analysis tools like Coverity. Patch from
5945 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
5946 - Use direct writes rather than stdio when building microdescriptor
5947 caches, in an attempt to mitigate bug 8031, or at least make it
5950 o Minor bugfixes (config):
5951 - When rejecting a configuration because we were unable to parse a
5952 quoted string, log an actual error message. Fixes bug 7950; bugfix
5954 - Behave correctly when the user disables LearnCircuitBuildTimeout
5955 but doesn't tell us what they would like the timeout to be. Fixes
5956 bug 6304; bugfix on 0.2.2.14-alpha.
5957 - When autodetecting the number of CPUs, use the number of available
5958 CPUs in preference to the number of configured CPUs. Inform the
5959 user if this reduces the number of available CPUs. Fixes bug 8002;
5960 bugfix on 0.2.3.1-alpha.
5961 - Make it an error when you set EntryNodes but disable UseGuardNodes,
5962 since it will (surprisingly to some users) ignore EntryNodes. Fixes
5963 bug 8180; bugfix on 0.2.3.11-alpha.
5964 - Allow TestingTorNetworks to override the 4096-byte minimum for
5965 the Fast threshold. Otherwise they can't bootstrap until they've
5966 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
5967 - Fix some logic errors when the user manually overrides the
5968 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
5971 o Minor bugfixes (log messages to help diagnose bugs):
5972 - If we fail to free a microdescriptor because of bug 7164, log
5973 the filename and line number from which we tried to free it.
5974 - Add another diagnostic to the heartbeat message: track and log
5975 overhead that TLS is adding to the data we write. If this is
5976 high, we are sending too little data to SSL_write at a time.
5977 Diagnostic for bug 7707.
5978 - Add more detail to a log message about relaxed timeouts, to help
5980 - Warn more aggressively when flushing microdescriptors to a
5981 microdescriptor cache fails, in an attempt to mitigate bug 8031,
5982 or at least make it more diagnosable.
5983 - Improve debugging output to help track down bug 8185 ("Bug:
5984 outgoing relay cell has n_chan==NULL. Dropping.")
5985 - Log the purpose of a path-bias testing circuit correctly.
5986 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
5988 o Minor bugfixes (0.2.4.x log messages that were too noisy):
5989 - Don't attempt to relax the timeout of already opened 1-hop circuits.
5990 They might never timeout. This should eliminate some/all cases of
5991 the relaxed timeout log message.
5992 - Use circuit creation time for network liveness evaluation. This
5993 should eliminate warning log messages about liveness caused
5994 by changes in timeout evaluation. Fixes bug 6572; bugfix on
5996 - Reduce a path bias length check from notice to info. The message
5997 is triggered when creating controller circuits. Fixes bug 8196;
5998 bugfix on 0.2.4.8-alpha.
5999 - Fix a path state issue that triggered a notice during relay startup.
6000 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
6001 - Reduce occurrences of warns about circuit purpose in
6002 connection_ap_expire_building(). Fixes bug 8477; bugfix on
6005 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
6006 - If we encounter a write failure on a SOCKS connection before we
6007 finish our SOCKS handshake, don't warn that we closed the
6008 connection before we could send a SOCKS reply. Fixes bug 8427;
6009 bugfix on 0.1.0.1-rc.
6010 - Correctly recognize that [::1] is a loopback address. Fixes
6011 bug 8377; bugfix on 0.2.1.3-alpha.
6012 - Fix a directory authority warn caused when we have a large amount
6013 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
6014 - Don't log inappropriate heartbeat messages when hibernating: a
6015 hibernating node is _expected_ to drop out of the consensus,
6016 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
6017 bugfix on 0.2.3.1-alpha.
6018 - Don't complain about bootstrapping problems while hibernating.
6019 These complaints reflect a general code problem, but not one
6020 with any problematic effects (no connections are actually
6021 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
6023 o Documentation fixes:
6024 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
6025 names match. Fixes bug 7768.
6026 - Make the torify manpage no longer refer to tsocks; torify hasn't
6027 supported tsocks since 0.2.3.14-alpha.
6028 - Make the tor manpage no longer reference tsocks.
6029 - Fix the GeoIPExcludeUnknown documentation to refer to
6030 ExcludeExitNodes rather than the currently nonexistent
6031 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
6034 - The tor-tsocks.conf is no longer distributed or installed. We
6035 recommend that tsocks users use torsocks instead. Resolves
6039 Changes in version 0.2.4.11-alpha - 2013-03-11
6040 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
6041 more robust, makes hidden service authentication work again, and
6042 resolves a DPI fingerprint for Tor's SSL transport.
6044 o Major features (directory authorities):
6045 - Directory authorities now support a new consensus method (17)
6046 where they cap the published bandwidth of servers for which
6047 insufficient bandwidth measurements exist. Fixes part of bug 2286.
6048 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
6049 serve any v2 directory information. Now we can test disabling the
6050 old deprecated v2 directory format, and see whether doing so has
6051 any effect on network load. Begins to fix bug 6783.
6052 - Directory authorities now include inside each vote a statement of
6053 the performance thresholds they used when assigning flags.
6054 Implements ticket 8151.
6056 o Major bugfixes (directory authorities):
6057 - Stop marking every relay as having been down for one hour every
6058 time we restart a directory authority. These artificial downtimes
6059 were messing with our Stable and Guard flag calculations. Fixes
6060 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
6062 o Major bugfixes (hidden services):
6063 - Allow hidden service authentication to succeed again. When we
6064 refactored the hidden service introduction code back
6065 in 0.2.4.1-alpha, we didn't update the code that checks
6066 whether authentication information is present, causing all
6067 authentication checks to return "false". Fix for bug 8207; bugfix
6068 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
6070 o Minor features (relays, bridges):
6071 - Make bridge relays check once a minute for whether their IP
6072 address has changed, rather than only every 15 minutes. Resolves
6074 - Refactor resolve_my_address() so it returns the method by which we
6075 decided our public IP address (explicitly configured, resolved from
6076 explicit hostname, guessed from interfaces, learned by gethostname).
6077 Now we can provide more helpful log messages when a relay guesses
6078 its IP address incorrectly (e.g. due to unexpected lines in
6079 /etc/hosts). Resolves ticket 2267.
6080 - Teach bridge-using clients to avoid 0.2.2 bridges when making
6081 microdescriptor-related dir requests, and only fall back to normal
6082 descriptors if none of their bridges can handle microdescriptors
6083 (as opposed to the fix in ticket 4013, which caused them to fall
6084 back to normal descriptors if *any* of their bridges preferred
6085 them). Resolves ticket 4994.
6086 - Randomize the lifetime of our SSL link certificate, so censors can't
6087 use the static value for filtering Tor flows. Resolves ticket 8443;
6088 related to ticket 4014 which was included in 0.2.2.33.
6089 - Support a new version of the link protocol that allows 4-byte circuit
6090 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
6091 a possible resource exhaustion issue. Closes ticket 7351; implements
6094 o Minor features (portability):
6095 - Tweak the curve25519-donna*.c implementations to tolerate systems
6096 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
6097 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
6098 the signs of types during autoconf. This is better than our old
6099 approach, which didn't work when cross-compiling.
6100 - Detect the sign of enum values, rather than assuming that MSC is the
6101 only compiler where enum types are all signed. Fixes bug 7727;
6102 bugfix on 0.2.4.10-alpha.
6104 o Minor features (other):
6105 - Say "KBytes" rather than "KB" in the man page (for various values
6106 of K), to further reduce confusion about whether Tor counts in
6107 units of memory or fractions of units of memory. Resolves ticket 7054.
6108 - Clear the high bit on curve25519 public keys before passing them to
6109 our backend, in case we ever wind up using a backend that doesn't do
6110 so itself. If we used such a backend, and *didn't* clear the high bit,
6111 we could wind up in a situation where users with such backends would
6112 be distinguishable from users without. Fixes bug 8121; bugfix on
6114 - Update to the March 6 2013 Maxmind GeoLite Country database.
6116 o Minor bugfixes (clients):
6117 - When we receive a RELAY_END cell with the reason DONE, or with no
6118 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
6119 status as "connection refused". Previously we reported these cases
6120 as success but then immediately closed the connection. Fixes bug
6121 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
6122 - Downgrade an assertion in connection_ap_expire_beginning to an
6123 LD_BUG message. The fix for bug 8024 should prevent this message
6124 from displaying, but just in case, a warn that we can diagnose
6125 is better than more assert crashes. Fixes bug 8065; bugfix on
6127 - Lower path use bias thresholds to .80 for notice and .60 for warn.
6128 Also make the rate limiting flags for the path use bias log messages
6129 independent from the original path bias flags. Fixes bug 8161;
6130 bugfix on 0.2.4.10-alpha.
6132 o Minor bugfixes (relays):
6133 - Stop trying to resolve our hostname so often (e.g. every time we
6134 think about doing a directory fetch). Now we reuse the cached
6135 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
6136 and 2410 (bugfix on 0.1.2.2-alpha).
6137 - Stop sending a stray "(null)" in some cases for the server status
6138 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
6140 - When choosing which stream on a formerly stalled circuit to wake
6141 first, make better use of the platform's weak RNG. Previously,
6142 we had been using the % ("modulo") operator to try to generate a
6143 1/N chance of picking each stream, but this behaves badly with
6144 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
6146 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
6147 Irix's random() only return 15 bits; Solaris's random() returns more
6148 bits but its RAND_MAX says it only returns 15, and so on. Motivated
6149 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
6151 o Minor bugfixes (directory authorities):
6152 - Directory authorities now use less space when formatting identical
6153 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
6156 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
6157 - Avoid leaking memory if we fail to compute a consensus signature
6158 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
6159 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
6161 - Fix a memory leak during safe-cookie controller authentication.
6162 Bugfix on 0.2.3.13-alpha.
6163 - Avoid memory leak of IPv6 policy content if we fail to format it into
6164 a router descriptor. Bugfix on 0.2.4.7-alpha.
6166 o Minor bugfixes (other code correctness issues):
6167 - Avoid a crash if we fail to generate an extrainfo descriptor.
6168 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
6170 - When detecting the largest possible file descriptor (in order to
6171 close all file descriptors when launching a new program), actually
6172 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
6173 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
6175 - Fix a copy-and-paste error when adding a missing A1 to a routerset
6176 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
6177 Bugfix on 0.2.4.10-alpha.
6178 - Fix an impossible-to-trigger integer overflow when estimating how
6179 long our onionskin queue would take. (This overflow would require us
6180 to accept 4 million onionskins before processing 100 of them.) Fixes
6181 bug 8210; bugfix on 0.2.4.10-alpha.
6183 o Code simplification and refactoring:
6184 - Add a wrapper function for the common "log a message with a
6188 Changes in version 0.2.4.10-alpha - 2013-02-04
6189 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
6190 certain attacks that flood the network with relays; changes the queue
6191 for circuit create requests from a sized-based limit to a time-based
6192 limit; resumes building with MSVC on Windows; and fixes a wide variety
6195 o Major bugfixes (directory authority):
6196 - When computing directory thresholds, ignore any rejected-as-sybil
6197 nodes during the computation so that they can't influence Fast,
6198 Guard, etc. (We should have done this for proposal 109.) Fixes
6200 - When marking a node as a likely sybil, reset its uptime metrics
6201 to zero, so that it cannot time towards getting marked as Guard,
6202 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
6206 - When a TLS write is partially successful but incomplete, remember
6207 that the flushed part has been flushed, and notice that bytes were
6208 actually written. Reported and fixed pseudonymously. Fixes bug
6209 7708; bugfix on Tor 0.1.0.5-rc.
6210 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
6211 ID: these could be used to create unexpected streams and circuits
6212 which would count as "present" to some parts of Tor but "absent"
6213 to others, leading to zombie circuits and streams or to a bandwidth
6214 denial-of-service. Fixes bug 7889; bugfix on every released version
6215 of Tor. Reported by "oftc_must_be_destroyed".
6216 - Rename all macros in our local copy of queue.h to begin with "TOR_".
6217 This change seems the only good way to permanently prevent conflicts
6218 with queue.h on various operating systems. Fixes bug 8107; bugfix
6221 o Major features (relay):
6222 - Instead of limiting the number of queued onionskins (aka circuit
6223 create requests) to a fixed, hard-to-configure number, we limit
6224 the size of the queue based on how many we expect to be able to
6225 process in a given amount of time. We estimate the time it will
6226 take to process an onionskin based on average processing time
6227 of previous onionskins. Closes ticket 7291. You'll never have to
6228 configure MaxOnionsPending again.
6230 o Major features (portability):
6231 - Resume building correctly with MSVC and Makefile.nmake. This patch
6232 resolves numerous bugs and fixes reported by ultramage, including
6233 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
6234 - Make the ntor and curve25519 code build correctly with MSVC.
6235 Fix on 0.2.4.8-alpha.
6238 - When directory authorities are computing thresholds for flags,
6239 never let the threshold for the Fast flag fall below 4096
6240 bytes. Also, do not consider nodes with extremely low bandwidths
6241 when deciding thresholds for various directory flags. This change
6242 should raise our threshold for Fast relays, possibly in turn
6243 improving overall network performance; see ticket 1854. Resolves
6245 - The Tor client now ignores sub-domain components of a .onion
6246 address. This change makes HTTP "virtual" hosting
6247 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
6248 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
6249 hosted on the same hidden service. Implements proposal 204.
6250 - We compute the overhead from passing onionskins back and forth to
6251 cpuworkers, and report it when dumping statistics in response to
6252 SIGUSR1. Supports ticket 7291.
6254 o Minor features (path selection):
6255 - When deciding whether we have enough descriptors to build circuits,
6256 instead of looking at raw relay counts, look at which fraction
6257 of (bandwidth-weighted) paths we're able to build. This approach
6258 keeps clients from building circuits if their paths are likely to
6259 stand out statistically. The default fraction of paths needed is
6260 taken from the consensus directory; you can override it with the
6261 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
6262 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
6263 and we have GeoIP information, also exclude all nodes with unknown
6264 countries "??" and "A1". This behavior is controlled by the
6265 new GeoIPExcludeUnknown option: you can make such nodes always
6266 excluded with "GeoIPExcludeUnknown 1", and disable the feature
6267 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
6268 gets you the default behavior. Implements feature 7706.
6269 - Path Use Bias: Perform separate accounting for successful circuit
6270 use. Keep separate statistics on stream attempt rates versus stream
6271 success rates for each guard. Provide configurable thresholds to
6272 determine when to emit log messages or disable use of guards that
6273 fail too many stream attempts. Resolves ticket 7802.
6275 o Minor features (log messages):
6276 - When learning a fingerprint for a bridge, log its corresponding
6277 transport type. Implements ticket 7896.
6278 - Improve the log message when "Bug/attack: unexpected sendme cell
6279 from client" occurs, to help us track bug 8093.
6282 - Remove a couple of extraneous semicolons that were upsetting the
6283 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
6284 bugfix on 0.2.2.1-alpha.
6285 - Remove a source of rounding error during path bias count scaling;
6286 don't count cannibalized circuits as used for path bias until we
6287 actually try to use them; and fix a circuit_package_relay_cell()
6288 warning message about n_chan==NULL. Fixes bug 7802.
6289 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
6290 actually link against nacl when we're configured to use it. Fixes
6291 bug 7972; bugfix on 0.2.4.8-alpha.
6292 - Compile correctly with the --disable-curve25519 option. Fixes
6293 bug 8153; bugfix on 0.2.4.8-alpha.
6295 o Build improvements:
6296 - Do not report status verbosely from autogen.sh unless the -v flag
6297 is specified. Fixes issue 4664. Patch from Onizuka.
6298 - Replace all calls to snprintf() outside of src/ext with
6299 tor_snprintf(). Also remove the #define to replace snprintf with
6300 _snprintf on Windows; they have different semantics, and all of
6301 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
6302 - Try to detect if we are ever building on a platform where
6303 memset(...,0,...) does not set the value of a double to 0.0. Such
6304 platforms are permitted by the C standard, though in practice
6305 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
6306 currently support them, but it's better to detect them and fail
6307 than to perform erroneously.
6310 - Stop exporting estimates of v2 and v3 directory traffic shares
6311 in extrainfo documents. They were unneeded and sometimes inaccurate.
6312 Also stop exporting any v2 directory request statistics. Resolves
6314 - Drop support for detecting and warning about versions of Libevent
6315 before 1.3e. Nothing reasonable ships with them any longer;
6316 warning the user about them shouldn't be needed. Resolves ticket
6319 o Code simplifications and refactoring:
6320 - Rename "isin" functions to "contains", for grammar. Resolves
6322 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
6323 with the natural logarithm function from the system libm. Resolves
6327 Changes in version 0.2.4.9-alpha - 2013-01-15
6328 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
6332 - Fix backward compatibility logic when receiving an embedded ntor
6333 handshake tunneled in a CREATE cell. This clears up the "Bug:
6334 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
6338 Changes in version 0.2.4.8-alpha - 2013-01-14
6339 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
6340 risks, adds a new stronger and faster circuit handshake, and offers
6341 stronger and faster link encryption when both sides support it.
6344 - Preliminary support for directory guards (proposal 207): when
6345 possible, clients now use their entry guards for non-anonymous
6346 directory requests. This can help prevent client enumeration. Note
6347 that this behavior only works when we have a usable consensus
6348 directory, and when options about what to download are more or less
6349 standard. In the future we should re-bootstrap from our guards,
6350 rather than re-bootstrapping from the preconfigured list of
6351 directory sources that ships with Tor. Resolves ticket 6526.
6352 - Tor relays and clients now support a better CREATE/EXTEND cell
6353 format, allowing the sender to specify multiple address, identity,
6354 and handshake types. Implements Robert Ransom's proposal 200;
6357 o Major features (new circuit handshake):
6358 - Tor now supports a new circuit extension handshake designed by Ian
6359 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
6360 circuit extension handshake, later called "TAP", was a bit slow
6361 (especially on the relay side), had a fragile security proof, and
6362 used weaker keys than we'd now prefer. The new circuit handshake
6363 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
6364 function, making it significantly more secure than the older
6365 handshake, and significantly faster. Tor can use one of two built-in
6366 pure-C curve25519-donna implementations by Adam Langley, or it
6367 can link against the "nacl" library for a tuned version if present.
6369 The built-in version is very fast for 64-bit systems when building
6370 with GCC. The built-in 32-bit version is still faster than the
6371 old TAP protocol, but using libnacl is better on most such hosts.
6373 Clients don't currently use this protocol by default, since
6374 comparatively few clients support it so far. To try it, set
6375 UseNTorHandshake to 1.
6377 Implements proposal 216; closes ticket 7202.
6379 o Major features (better link encryption):
6380 - Relays can now enable the ECDHE TLS ciphersuites when available
6381 and appropriate. These ciphersuites let us negotiate forward-secure
6382 TLS secret keys more safely and more efficiently than with our
6383 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
6384 public relays prefer the (faster) P224 group, and bridges prefer
6385 the (more common) P256 group; you can override this with the
6388 Enabling these ciphers was a little tricky, since for a long time,
6389 clients had been claiming to support them without actually doing
6390 so, in order to foil fingerprinting. But with the client-side
6391 implementation of proposal 198 in 0.2.3.17-beta, clients can now
6392 match the ciphers from recent Firefox versions *and* list the
6393 ciphers they actually mean, so relays can believe such clients
6394 when they advertise ECDHE support in their TLS ClientHello messages.
6396 This feature requires clients running 0.2.3.17-beta or later,
6397 and requires both sides to be running OpenSSL 1.0.0 or later
6398 with ECC support. OpenSSL 1.0.1, with the compile-time option
6399 "enable-ec_nistp_64_gcc_128", is highly recommended.
6401 Implements the relay side of proposal 198; closes ticket 7200.
6404 - Avoid crashing when, as a relay without IPv6-exit support, a
6405 client insists on getting an IPv6 address or nothing. Fixes bug
6406 7814; bugfix on 0.2.4.7-alpha.
6409 - Improve circuit build timeout handling for hidden services.
6410 In particular: adjust build timeouts more accurately depending
6411 upon the number of hop-RTTs that a particular circuit type
6412 undergoes. Additionally, launch intro circuits in parallel
6413 if they timeout, and take the first one to reply as valid.
6414 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
6415 separate error codes; or at least, don't break for that reason.
6416 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
6417 - Update to the January 2 2013 Maxmind GeoLite Country database.
6419 o Minor features (testing):
6420 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
6421 (P-256) Diffie-Hellman handshakes to src/or/bench.
6422 - Add benchmark functions to test onion handshake performance.
6424 o Minor features (path bias detection):
6425 - Alter the Path Bias log messages to be more descriptive in terms
6426 of reporting timeouts and other statistics.
6427 - Create three levels of Path Bias log messages, as opposed to just
6428 two. These are configurable via consensus as well as via the torrc
6429 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
6430 The default values are 0.70, 0.50, and 0.30 respectively.
6431 - Separate the log message levels from the decision to drop guards,
6432 which also is available via torrc option PathBiasDropGuards.
6433 PathBiasDropGuards still defaults to 0 (off).
6434 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
6435 in combination with PathBiasExtremeRate.
6436 - Increase the default values for PathBiasScaleThreshold and
6437 PathBiasCircThreshold from (200, 20) to (300, 150).
6438 - Add in circuit usage accounting to path bias. If we try to use a
6439 built circuit but fail for any reason, it counts as path bias.
6440 Certain classes of circuits where the adversary gets to pick your
6441 destination node are exempt from this accounting. Usage accounting
6442 can be specifically disabled via consensus parameter or torrc.
6443 - Convert all internal path bias state to double-precision floating
6444 point, to avoid roundoff error and other issues.
6445 - Only record path bias information for circuits that have completed
6446 *two* hops. Assuming end-to-end tagging is the attack vector, this
6447 makes us more resilient to ambient circuit failure without any
6448 detection capability loss.
6450 o Minor bugfixes (log messages):
6451 - Rate-limit the "No circuits are opened. Relaxed timeout for a
6452 circuit with channel state open..." message to once per hour to
6453 keep it from filling the notice logs. Mitigates bug 7799 but does
6454 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
6455 - Avoid spurious warnings when configuring multiple client ports of
6456 which only some are nonlocal. Previously, we had claimed that some
6457 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
6460 o Code simplifications and refactoring:
6461 - Get rid of a couple of harmless clang warnings, where we compared
6462 enums to ints. These warnings are newly introduced in clang 3.2.
6463 - Split the onion.c file into separate modules for the onion queue
6464 and the different handshakes it supports.
6465 - Remove the marshalling/unmarshalling code for sending requests to
6466 cpuworkers over a socket, and instead just send structs. The
6467 recipient will always be the same Tor binary as the sender, so
6468 any encoding is overkill.
6471 Changes in version 0.2.4.7-alpha - 2012-12-24
6472 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
6473 directory mirrors for more robust bootstrapping; fixes more issues where
6474 clients with changing network conditions refuse to make any circuits;
6475 adds initial support for exiting to IPv6 addresses; resumes being able
6476 to update our GeoIP database, and includes the geoip6 file this time;
6477 turns off the client-side DNS cache by default due to privacy risks;
6478 and fixes a variety of other issues.
6480 o Major features (client resilience):
6481 - Add a new "FallbackDir" torrc option to use when we can't use
6482 a directory mirror from the consensus (either because we lack a
6483 consensus, or because they're all down). Currently, all authorities
6484 are fallbacks by default, and there are no other default fallbacks,
6485 but that will change. This option will allow us to give clients a
6486 longer list of servers to try to get a consensus from when first
6487 connecting to the Tor network, and thereby reduce load on the
6488 directory authorities. Implements proposal 206, "Preconfigured
6489 directory sources for bootstrapping". We also removed the old
6490 "FallbackNetworkstatus" option, since we never got it working well
6491 enough to use it. Closes bug 572.
6492 - If we have no circuits open, use a relaxed timeout (the
6493 95-percentile cutoff) until a circuit succeeds. This heuristic
6494 should allow Tor to succeed at building circuits even when the
6495 network connection drastically changes. Should help with bug 3443.
6497 o Major features (IPv6):
6498 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
6499 connectivity, then set the IPv6Exit flag to 1. Also make sure your
6500 exit policy reads as you would like: the address * applies to all
6501 address families, whereas *4 is IPv4 address only, and *6 is IPv6
6502 addresses only. On the client side, you'll need to wait until the
6503 authorities have upgraded, wait for enough exits to support IPv6,
6504 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
6505 ticket 5547, implements proposal 117 as revised in proposal 208.
6507 We DO NOT recommend that clients with actual anonymity needs start
6508 using IPv6 over Tor yet, since not enough exits support it yet.
6510 o Major features (geoip database):
6511 - Maxmind began labelling Tor relays as being in country "A1",
6512 which breaks by-country node selection inside Tor. Now we use a
6513 script to replace "A1" ("Anonymous Proxy") entries in our geoip
6514 file with real country codes. This script fixes about 90% of "A1"
6515 entries automatically and uses manual country code assignments to
6516 fix the remaining 10%. See src/config/README.geoip for details.
6517 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
6518 Country database, as modified above.
6520 o Major bugfixes (client-side DNS):
6521 - Turn off the client-side DNS cache by default. Updating and using
6522 the DNS cache is now configurable on a per-client-port
6523 level. SOCKSPort, DNSPort, etc lines may now contain
6524 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
6525 cache these types of DNS answers when we receive them from an
6526 exit node in response to an application request on this port, and
6527 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
6528 cached DNS answers of these types, we shouldn't use them. It's
6529 potentially risky to use cached DNS answers at the client, since
6530 doing so can indicate to one exit what answers we've gotten
6531 for DNS lookups in the past. With IPv6, this becomes especially
6532 problematic. Using cached DNS answers for requests on the same
6533 circuit would present less linkability risk, since all traffic
6534 on a circuit is already linkable, but it would also provide
6535 little performance benefit: the exit node caches DNS replies
6536 too. Implements a simplified version of Proposal 205. Implements
6539 o Major bugfixes (other):
6540 - Alter circuit build timeout measurement to start at the point
6541 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
6542 initialization). This should make our timeout measurements more
6543 uniform. Previously, we were sometimes including ORconn setup time
6544 in our circuit build time measurements. Should resolve bug 3443.
6545 - Fix an assertion that could trigger in hibernate_go_dormant() when
6546 closing an or_connection_t: call channel_mark_for_close() rather
6547 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
6549 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
6550 7655; bugfix on 0.2.4.6-alpha.
6553 - Add a new torrc option "ServerTransportListenAddr" to let bridge
6554 operators select the address where their pluggable transports will
6555 listen for connections. Resolves ticket 7013.
6556 - Allow an optional $ before the node identity digest in the
6557 controller command GETINFO ns/id/<identity>, for consistency with
6558 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
6559 - Log packaged cell fullness as part of the heartbeat message.
6560 Diagnosis to try to determine the extent of bug 7743.
6562 o Minor features (IPv6):
6563 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
6564 prefer to hand out virtual IPv6 addresses, since there are more of
6565 them and we can't run out. To override this behavior and make IPv4
6566 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
6567 or DNSPort you're using for resolving. Implements ticket 7571.
6568 - AutomapHostsOnResolve responses are now randomized, to avoid
6569 annoying situations where Tor is restarted and applications
6570 connect to the wrong addresses.
6571 - Never try more than 1000 times to pick a new virtual address when
6572 AutomapHostsOnResolve is set. That's good enough so long as we
6573 aren't close to handing out our entire virtual address space;
6574 if you're getting there, it's best to switch to IPv6 virtual
6578 - The ADDRMAP command can no longer generate an ill-formed error
6579 code on a failed MAPADDRESS. It now says "internal" rather than
6580 an English sentence fragment with spaces in the middle. Bugfix on
6582 - Fix log messages and comments to avoid saying "GMT" when we mean
6583 "UTC". Fixes bug 6113.
6584 - Compile on win64 using mingw64. Fixes bug 7260; patches from
6586 - Fix a crash when debugging unit tests on Windows: deallocate a
6587 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
6588 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
6591 - The DirServer option is now DirAuthority, for consistency with
6592 current naming patterns. You can still use the old DirServer form.
6594 o Code simplification and refactoring:
6595 - Move the client-side address-map/virtual-address/DNS-cache code
6596 out of connection_edge.c into a new addressmap.c module.
6597 - Remove unused code for parsing v1 directories and "running routers"
6598 documents. Fixes bug 6887.
6601 Changes in version 0.2.3.25 - 2012-11-19
6602 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
6603 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
6604 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
6605 programmer, and friend. Unstinting in his dedication to the cause of
6606 freedom, he inspired and helped many of us as we began our work on
6607 anonymity, and inspires us still. Please honor his memory by writing
6608 software to protect people's freedoms, and by helping others to do so.
6610 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
6611 significantly reduced directory overhead (via microdescriptors),
6612 enormous crypto performance improvements for fast relays on new
6613 enough hardware, a new v3 TLS handshake protocol that can better
6614 resist fingerprinting, support for protocol obfuscation plugins (aka
6615 pluggable transports), better scalability for hidden services, IPv6
6616 support for bridges, performance improvements like allowing clients
6617 to skip the first round-trip on the circuit ("optimistic data") and
6618 refilling token buckets more often, a new "stream isolation" design
6619 to isolate different applications on different circuits, and many
6620 stability, security, and privacy fixes.
6623 - Tor tries to wipe potentially sensitive data after using it, so
6624 that if some subsequent security failure exposes Tor's memory,
6625 the damage will be limited. But we had a bug where the compiler
6626 was eliminating these wipe operations when it decided that the
6627 memory was no longer visible to a (correctly running) program,
6628 hence defeating our attempt at defense in depth. We fix that
6629 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6630 is unlikely to optimize away. Future versions of Tor may use
6631 a less ridiculously heavy approach for this. Fixes bug 7352.
6632 Reported in an article by Andrey Karpov.
6635 - Fix a harmless bug when opting against publishing a relay descriptor
6636 because DisableNetwork is set. Fixes bug 7464; bugfix on
6640 Changes in version 0.2.4.6-alpha - 2012-11-13
6641 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
6642 makes our defense-in-depth memory wiping more reliable, and begins to
6643 count IPv6 addresses in bridge statistics,
6646 - Fix an assertion failure that could occur when closing a connection
6647 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
6649 - Tor tries to wipe potentially sensitive data after using it, so
6650 that if some subsequent security failure exposes Tor's memory,
6651 the damage will be limited. But we had a bug where the compiler
6652 was eliminating these wipe operations when it decided that the
6653 memory was no longer visible to a (correctly running) program,
6654 hence defeating our attempt at defense in depth. We fix that
6655 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6656 is unlikely to optimize away. Future versions of Tor may use
6657 a less ridiculously heavy approach for this. Fixes bug 7352.
6658 Reported in an article by Andrey Karpov.
6661 - Add GeoIP database for IPv6 addresses. The new config option
6663 - Bridge statistics now count bridge clients connecting over IPv6:
6664 bridge statistics files now list "bridge-ip-versions" and
6665 extra-info documents list "geoip6-db-digest". The control protocol
6666 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
6667 implementation by "shkoo", addressing ticket 5055.
6670 - Warn when we are binding low ports when hibernation is enabled;
6671 previously we had warned when we were _advertising_ low ports with
6672 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
6673 - Fix a harmless bug when opting against publishing a relay descriptor
6674 because DisableNetwork is set. Fixes bug 7464; bugfix on
6676 - Add warning message when a managed proxy dies during configuration.
6677 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
6678 - Fix a linking error when building tor-fw-helper without miniupnp.
6679 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
6680 - Check for closing an or_connection_t without going through correct
6681 channel functions; emit a warning and then call
6682 connection_or_close_for_error() so we don't assert as in bugs 7212
6684 - Compile correctly on compilers without C99 designated initializer
6685 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
6686 - Avoid a possible assert that can occur when channel_send_destroy() is
6687 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
6688 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
6689 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
6690 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
6691 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
6693 o Code simplification and refactoring:
6694 - Start using OpenBSD's implementation of queue.h, so that we don't
6695 need to hand-roll our own pointer and list structures whenever we
6696 need them. (We can't rely on a sys/queue.h, since some operating
6697 systems don't have them, and the ones that do have them don't all
6698 present the same extensions.)
6701 Changes in version 0.2.4.5-alpha - 2012-10-25
6702 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
6703 two important security vulnerabilities that could lead to remotely
6704 triggerable relay crashes, fix a major bug that was preventing clients
6705 from choosing suitable exit nodes, and refactor some of our code.
6707 o Major bugfixes (security, also in 0.2.3.24-rc):
6708 - Fix a group of remotely triggerable assertion failures related to
6709 incorrect link protocol negotiation. Found, diagnosed, and fixed
6710 by "some guy from France". Fix for CVE-2012-2250; bugfix on
6712 - Fix a denial of service attack by which any directory authority
6713 could crash all the others, or by which a single v2 directory
6714 authority could crash everybody downloading v2 directory
6715 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
6717 o Major bugfixes (also in 0.2.3.24-rc):
6718 - When parsing exit policy summaries from microdescriptors, we had
6719 previously been ignoring the last character in each one, so that
6720 "accept 80,443,8080" would be treated by clients as indicating
6721 a node that allows access to ports 80, 443, and 808. That would
6722 lead to clients attempting connections that could never work,
6723 and ignoring exit nodes that would support their connections. Now
6724 clients parse these exit policy summaries correctly. Fixes bug 7192;
6725 bugfix on 0.2.3.1-alpha.
6727 o Minor bugfixes (also in 0.2.3.24-rc):
6728 - Clients now consider the ClientRejectInternalAddresses config option
6729 when using a microdescriptor consensus stanza to decide whether
6730 an exit relay would allow exiting to an internal address. Fixes
6731 bug 7190; bugfix on 0.2.3.1-alpha.
6734 - Only disable TLS session ticket support when running as a TLS
6735 server. Now clients will blend better with regular Firefox
6736 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
6738 o Code simplification and refactoring:
6739 - Start using OpenBSD's implementation of queue.h (originally by
6741 - Move the entry node code from circuitbuild.c to its own file.
6742 - Move the circuit build timeout tracking code from circuitbuild.c
6746 Changes in version 0.2.3.24-rc - 2012-10-25
6747 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
6748 could lead to remotely triggerable relay crashes, and fixes
6749 a major bug that was preventing clients from choosing suitable exit
6752 o Major bugfixes (security):
6753 - Fix a group of remotely triggerable assertion failures related to
6754 incorrect link protocol negotiation. Found, diagnosed, and fixed
6755 by "some guy from France". Fix for CVE-2012-2250; bugfix on
6757 - Fix a denial of service attack by which any directory authority
6758 could crash all the others, or by which a single v2 directory
6759 authority could crash everybody downloading v2 directory
6760 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
6763 - When parsing exit policy summaries from microdescriptors, we had
6764 previously been ignoring the last character in each one, so that
6765 "accept 80,443,8080" would be treated by clients as indicating
6766 a node that allows access to ports 80, 443, and 808. That would
6767 lead to clients attempting connections that could never work,
6768 and ignoring exit nodes that would support their connections. Now
6769 clients parse these exit policy summaries correctly. Fixes bug 7192;
6770 bugfix on 0.2.3.1-alpha.
6773 - Clients now consider the ClientRejectInternalAddresses config option
6774 when using a microdescriptor consensus stanza to decide whether
6775 an exit relay would allow exiting to an internal address. Fixes
6776 bug 7190; bugfix on 0.2.3.1-alpha.
6779 Changes in version 0.2.4.4-alpha - 2012-10-20
6780 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
6781 vulnerability introduced by a change in OpenSSL, fixes a remotely
6782 triggerable assert, and adds new channel_t and circuitmux_t abstractions
6783 that will make it easier to test new connection transport and cell
6784 scheduling algorithms.
6786 o New directory authorities (also in 0.2.3.23-rc):
6787 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6788 authority. Closes ticket 5749.
6790 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
6791 - Disable TLS session tickets. OpenSSL's implementation was giving
6792 our TLS session keys the lifetime of our TLS context objects, when
6793 perfect forward secrecy would want us to discard anything that
6794 could decrypt a link connection as soon as the link connection
6795 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6796 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6797 - Discard extraneous renegotiation attempts once the V3 link
6798 protocol has been initiated. Failure to do so left us open to
6799 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
6800 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
6802 o Internal abstraction features:
6803 - Introduce new channel_t abstraction between circuits and
6804 or_connection_t to allow for implementing alternate OR-to-OR
6805 transports. A channel_t is an abstract object which can either be a
6806 cell-bearing channel, which is responsible for authenticating and
6807 handshaking with the remote OR and transmitting cells to and from
6808 it, or a listening channel, which spawns new cell-bearing channels
6809 at the request of remote ORs. Implements part of ticket 6465.
6810 - Also new is the channel_tls_t subclass of channel_t, adapting it
6811 to the existing or_connection_t code. The V2/V3 protocol handshaking
6812 code which formerly resided in command.c has been moved below the
6813 channel_t abstraction layer and may be found in channeltls.c now.
6814 Implements the rest of ticket 6465.
6815 - Introduce new circuitmux_t storing the queue of circuits for
6816 a channel; this encapsulates and abstracts the queue logic and
6817 circuit selection policy, and allows the latter to be overridden
6818 easily by switching out a policy object. The existing EWMA behavior
6819 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
6821 o Required libraries:
6822 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
6823 strongly recommended.
6826 - Warn users who run hidden services on a Tor client with
6827 UseEntryGuards disabled that their hidden services will be
6828 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
6829 attack which motivated Tor to support entry guards in the first
6830 place). Resolves ticket 6889.
6831 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
6832 dhill. Resolves ticket 6982.
6833 - Option OutboundBindAddress can be specified multiple times and
6834 accepts IPv6 addresses. Resolves ticket 6876.
6836 o Minor bugfixes (also in 0.2.3.23-rc):
6837 - Don't serve or accept v2 hidden service descriptors over a
6838 relay's DirPort. It's never correct to do so, and disabling it
6839 might make it more annoying to exploit any bugs that turn up in the
6840 descriptor-parsing code. Fixes bug 7149.
6841 - Fix two cases in src/or/transports.c where we were calling
6842 fmt_addr() twice in a parameter list. Bug found by David
6843 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
6844 - Fix memory leaks whenever we logged any message about the "path
6845 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
6846 - When relays refuse a "create" cell because their queue of pending
6847 create cells is too big (typically because their cpu can't keep up
6848 with the arrival rate), send back reason "resource limit" rather
6849 than reason "internal", so network measurement scripts can get a
6850 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
6853 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
6854 - Free some more still-in-use memory at exit, to make hunting for
6855 memory leaks easier. Resolves bug 7029.
6856 - When a Tor client gets a "truncated" relay cell, the first byte of
6857 its payload specifies why the circuit was truncated. We were
6858 ignoring this 'reason' byte when tearing down the circuit, resulting
6859 in the controller not being told why the circuit closed. Now we
6860 pass the reason from the truncated cell to the controller. Bugfix
6861 on 0.1.2.3-alpha; fixes bug 7039.
6862 - Downgrade "Failed to hand off onionskin" messages to "debug"
6863 severity, since they're typically redundant with the "Your computer
6864 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
6865 - Make clients running with IPv6 bridges connect over IPv6 again,
6866 even without setting new config options ClientUseIPv6 and
6867 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
6868 - Use square brackets around IPv6 addresses in numerous places
6869 that needed them, including log messages, HTTPS CONNECT proxy
6870 requests, TransportProxy statefile entries, and pluggable transport
6871 extra-info lines. Fixes bug 7011; patch by David Fifield.
6873 o Code refactoring and cleanup:
6874 - Source files taken from other packages now reside in src/ext;
6875 previously they were scattered around the rest of Tor.
6876 - Avoid use of reserved identifiers in our C code. The C standard
6877 doesn't like us declaring anything that starts with an
6878 underscore, so let's knock it off before we get in trouble. Fix
6879 for bug 1031; bugfix on the first Tor commit.
6882 Changes in version 0.2.3.23-rc - 2012-10-20
6883 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
6884 vulnerability introduced by a change in OpenSSL, and fixes a variety
6885 of smaller bugs in preparation for the release.
6887 o New directory authorities:
6888 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6889 authority. Closes ticket 5749.
6891 o Major bugfixes (security/privacy):
6892 - Disable TLS session tickets. OpenSSL's implementation was giving
6893 our TLS session keys the lifetime of our TLS context objects, when
6894 perfect forward secrecy would want us to discard anything that
6895 could decrypt a link connection as soon as the link connection
6896 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6897 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6898 - Discard extraneous renegotiation attempts once the V3 link
6899 protocol has been initiated. Failure to do so left us open to
6900 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
6901 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
6904 - Fix a possible crash bug when checking for deactivated circuits
6905 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6906 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6908 o Minor bugfixes (on 0.2.3.x):
6909 - Fix two cases in src/or/transports.c where we were calling
6910 fmt_addr() twice in a parameter list. Bug found by David
6911 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
6912 - Convert an assert in the pathbias code to a log message. The assert
6913 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
6914 bugfix on 0.2.3.17-beta.
6915 - Fix memory leaks whenever we logged any message about the "path
6916 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
6918 o Minor bugfixes (on 0.2.2.x and earlier):
6919 - Don't serve or accept v2 hidden service descriptors over a relay's
6920 DirPort. It's never correct to do so, and disabling it might
6921 make it more annoying to exploit any bugs that turn up in the
6922 descriptor-parsing code. Fixes bug 7149.
6923 - When relays refuse a "create" cell because their queue of pending
6924 create cells is too big (typically because their cpu can't keep up
6925 with the arrival rate), send back reason "resource limit" rather
6926 than reason "internal", so network measurement scripts can get a
6927 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
6928 - Correct file sizes when reading binary files on Cygwin, to avoid
6929 a bug where Tor would fail to read its state file. Fixes bug 6844;
6930 bugfix on 0.1.2.7-alpha.
6931 - Avoid undefined behavior when parsing the list of supported
6932 rendezvous/introduction protocols in a hidden service descriptor.
6933 Previously, Tor would have confused (as-yet-unused) protocol version
6934 numbers greater than 32 with lower ones on many platforms. Fixes
6935 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
6937 o Documentation fixes:
6938 - Clarify that hidden services are TCP only. Fixes bug 6024.
6941 Changes in version 0.2.4.3-alpha - 2012-09-22
6942 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
6943 assertion, resumes letting relays test reachability of their DirPort,
6944 and cleans up a bunch of smaller bugs.
6947 - Fix an assertion failure in tor_timegm() that could be triggered
6948 by a badly formatted directory object. Bug found by fuzzing with
6949 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6952 - Fix a possible crash bug when checking for deactivated circuits
6953 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6954 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6955 - Allow routers to detect that their own DirPorts are running. When
6956 we removed support for versions_supports_begindir, we also
6957 accidentally removed the mechanism we used to self-test our
6958 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
6959 bugfix on 0.2.4.2-alpha.
6961 o Security features:
6962 - Switch to a completely time-invariant approach for picking nodes
6963 weighted by bandwidth. Our old approach would run through the
6964 part of the loop after it had made its choice slightly slower
6965 than it ran through the part of the loop before it had made its
6966 choice. Addresses ticket 6538.
6967 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
6968 by tor2web clients allows hidden services to identify tor2web
6969 clients through their repeated selection of the same rendezvous
6970 and introduction point circuit endpoints (their guards). Resolves
6974 - Enable Tor to read configuration, state, and key information from
6975 a FIFO. Previously Tor would only read from files with a positive
6976 stat.st_size. Code from meejah; fixes bug 6044.
6979 - Correct file sizes when reading binary files on Cygwin, to avoid
6980 a bug where Tor would fail to read its state file. Fixes bug 6844;
6981 bugfix on 0.1.2.7-alpha.
6982 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
6983 bugfix on 0.2.0.3-alpha.
6984 - When complaining about a client port on a public address, log
6985 which address we're complaining about. Fixes bug 4020; bugfix on
6986 0.2.3.3-alpha. Patch by Tom Fitzhenry.
6987 - Convert an assert in the pathbias code to a log message. The assert
6988 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
6989 bugfix on 0.2.3.17-beta.
6990 - Our new buildsystem was overzealous about rebuilding manpages: it
6991 would rebuild them all whenever any one of them changed. Now our
6992 dependency checking should be correct. Fixes bug 6843; bugfix on
6994 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
6995 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
6996 - Correct log printout about which address family is preferred
6997 when connecting to a bridge with both an IPv4 and IPv6 OR port.
6998 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
7000 o Minor bugfixes (code cleanliness):
7001 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
7002 with large values. This situation was untriggered, but nevertheless
7003 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
7004 - Reject consensus votes with more than 64 known-flags. We aren't even
7005 close to that limit yet, and our code doesn't handle it correctly.
7006 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
7007 - Avoid undefined behavior when parsing the list of supported
7008 rendezvous/introduction protocols in a hidden service descriptor.
7009 Previously, Tor would have confused (as-yet-unused) protocol version
7010 numbers greater than 32 with lower ones on many platforms. Fixes
7011 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
7012 - Fix handling of rendezvous client authorization types over 8.
7013 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
7014 - Fix building with older versions of GCC (2.95, for one) that don't
7015 like preprocessor directives inside macro arguments. Found by
7016 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
7017 - Switch weighted node selection rule from using a list of doubles
7018 to using a list of int64_t. This change should make the process
7019 slightly easier to debug and maintain. Needed to finish ticket 6538.
7021 o Code simplification and refactoring:
7022 - Move the generic "config" code into a new file, and have "config.c"
7023 hold only torrc- and state-related code. Resolves ticket 6823.
7024 - Move the core of our "choose a weighted element at random" logic
7025 into its own function, and give it unit tests. Now the logic is
7026 testable, and a little less fragile too.
7027 - Removed the testing_since field of node_t, which hasn't been used
7028 for anything since 0.2.0.9-alpha.
7030 o Documentation fixes:
7031 - Clarify that hidden services are TCP only. Fixes bug 6024.
7032 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
7036 Changes in version 0.2.3.22-rc - 2012-09-11
7037 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
7041 - Fix an assertion failure in tor_timegm() that could be triggered
7042 by a badly formatted directory object. Bug found by fuzzing with
7043 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
7046 - Avoid segfault when starting up having run with an extremely old
7047 version of Tor and parsing its state file. Fixes bug 6801; bugfix
7051 Changes in version 0.2.2.39 - 2012-09-11
7052 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
7056 - Fix an assertion failure in tor_timegm() that could be triggered
7057 by a badly formatted directory object. Bug found by fuzzing with
7058 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
7059 - Do not crash when comparing an address with port value 0 to an
7060 address policy. This bug could have been used to cause a remote
7061 assertion failure by or against directory authorities, or to
7062 allow some applications to crash clients. Fixes bug 6690; bugfix
7066 Changes in version 0.2.4.2-alpha - 2012-09-10
7067 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
7068 raises the default rate limiting even more, and makes the bootstrapping
7069 log messages less noisy.
7072 - Automatically forward the TCP ports of pluggable transport
7073 proxies using tor-fw-helper if PortForwarding is enabled. Implements
7077 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
7078 to 1GB/1GB. The previous defaults were intended to be "basically
7079 infinite", but it turns out they're now limiting our 100mbit+
7080 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
7081 last time we raised it).
7084 - Detect when we're running with a version of OpenSSL other than the
7085 one we compiled with. This has occasionally given people hard-to-
7087 - Log fewer lines at level "notice" about our OpenSSL and Libevent
7088 versions and capabilities when everything is going right. Resolves
7089 part of ticket 6736.
7090 - Directory authorities no long accept descriptors for any version of
7091 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
7092 These versions are insecure, unsupported, or both. Implements
7096 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
7097 to start with a triple-underscore so the controller won't touch it.
7098 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
7099 - Avoid segfault when starting up having run with an extremely old
7100 version of Tor and parsing its state file. Fixes bug 6801; bugfix
7102 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
7103 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
7104 - Don't follow the NULL pointer if microdescriptor generation fails.
7105 (This does not appear to be triggerable, but it's best to be safe.)
7106 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
7107 - Fix mis-declared dependencies on src/common/crypto.c and
7108 src/or/tor_main.c that could break out-of-tree builds under some
7109 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
7110 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
7111 6778; bugfix on 0.2.4.1-alpha.
7112 - Fix a harmless (in this case) build warning for implicitly
7113 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
7116 - Now that all versions before 0.2.2.x are disallowed, we no longer
7117 need to work around their missing features. Thus we can remove a
7118 bunch of compatibility code.
7121 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
7122 TCP ports to forward. In the past it only accepted two ports:
7123 the ORPort and the DirPort.
7126 Changes in version 0.2.4.1-alpha - 2012-09-05
7127 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
7128 bridgedb; lets relays use IPv6 addresses and directory authorities
7129 advertise them; and switches to a cleaner build interface.
7131 This is the first alpha release in a new series, so expect there to
7132 be bugs. Users who would rather test out a more stable branch should
7133 stay with 0.2.3.x for now.
7135 o Major features (bridges):
7136 - Bridges now report the pluggable transports they support to the
7137 bridge authority, so it can pass the supported transports on to
7138 bridgedb and/or eventually do reachability testing. Implements
7141 o Major features (IPv6):
7142 - Bridge authorities now accept IPv6 bridge addresses and include
7143 them in network status documents. Implements ticket 5534.
7144 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
7145 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
7146 to happen. Implements ticket 5535.
7147 - All kind of relays, not just bridges, can now advertise an IPv6
7148 OR port. Implements ticket 6362.
7149 - Directory authorities vote on IPv6 OR ports using the new consensus
7150 method 14. Implements ticket 6363.
7152 o Major features (build):
7153 - Switch to a nonrecursive Makefile structure. Now instead of each
7154 Makefile.am invoking other Makefile.am's, there is a master
7155 Makefile.am that includes the others. This change makes our build
7156 process slightly more maintainable, and improves parallelism for
7157 building with make -j. Original patch by Stewart Smith; various
7158 fixes by Jim Meyering.
7159 - Where available, we now use automake's "silent" make rules by
7160 default, so that warnings are easier to spot. You can get the old
7161 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
7163 o Minor features (code security and spec conformance):
7164 - Clear keys and key-derived material left on the stack in
7165 rendservice.c and rendclient.c. Check return value of
7166 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
7167 These fixes should make us more forward-secure against cold-boot
7168 attacks and the like. Fixes bug 2385.
7169 - Reject EXTEND cells sent to nonexistent streams. According to the
7170 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
7171 we were only checking for stream IDs that were currently in use.
7172 Found while hunting for more instances of bug 6271. Bugfix on
7173 0.0.2pre8, which introduced incremental circuit construction.
7175 o Minor features (streamlining);
7176 - No longer include the "opt" prefix when generating routerinfos
7177 or v2 directories: it has been needless since Tor 0.1.2. Closes
7179 - Remove some now-needless code that tried to aggressively flush
7180 OR connections as data was added to them. Since 0.2.0.1-alpha, our
7181 cell queue logic has saved us from the failure mode that this code
7182 was supposed to prevent. Removing this code will limit the number
7183 of baroque control flow paths through Tor's network logic. Reported
7184 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
7186 o Minor features (controller):
7187 - Add a "GETINFO signal/names" control port command. Implements
7189 - Provide default values for all options via "GETINFO config/defaults".
7190 Implements ticket 4971.
7192 o Minor features (IPv6):
7193 - New config option "AuthDirHasIPv6Connectivity 1" that directory
7194 authorities should set if they have IPv6 connectivity and want to
7195 do reachability tests for IPv6 relays. Implements feature 5974.
7196 - A relay with an IPv6 OR port now sends that address in NETINFO
7197 cells (in addition to its other address). Implements ticket 6364.
7199 o Minor features (log messages):
7200 - Omit the first heartbeat log message, because it never has anything
7201 useful to say, and it clutters up the bootstrapping messages.
7202 Resolves ticket 6758.
7203 - Don't log about reloading the microdescriptor cache at startup. Our
7204 bootstrap warnings are supposed to tell the user when there's a
7205 problem, and our bootstrap notices say when there isn't. Resolves
7206 ticket 6759; bugfix on 0.2.2.6-alpha.
7207 - Don't log "I learned some more directory information" when we're
7208 reading cached directory information. Reserve it for when new
7209 directory information arrives in response to a fetch. Resolves
7211 - Prevent rounding error in path bias counts when scaling
7212 them down, and use the correct scale factor default. Also demote
7213 some path bias related log messages down a level and make others
7214 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
7215 - We no longer warn so much when generating manpages from their
7218 o Code simplifications and refactoring:
7219 - Enhance our internal sscanf replacement so that we can eliminate
7220 the last remaining uses of the system sscanf. (Though those uses
7221 of sscanf were safe, sscanf itself is generally error prone, so
7222 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
7224 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
7225 - Move last_reachable and testing_since from routerinfo_t to node_t.
7226 Implements ticket 5529.
7227 - Add replaycache_t structure, functions and unit tests, then refactor
7228 rend_service_introduce() to be more clear to read, improve, debug,
7229 and test. Resolves bug 6177.
7230 - Finally remove support for malloc_good_size and malloc_usable_size.
7231 We had hoped that these functions would let us eke a little more
7232 memory out of our malloc implementation. Unfortunately, the only
7233 implementations that provided these functions are also ones that
7234 are already efficient about not overallocation: they never got us
7235 more than 7 or so bytes per allocation. Removing them saves us a
7236 little code complexity and a nontrivial amount of build complexity.
7239 - Tor maintainers now require Automake version 1.9 or later to build
7240 Tor from the Git repository. (Automake is not required when building
7241 from a source distribution.)
7244 Changes in version 0.2.3.21-rc - 2012-09-05
7245 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
7246 series. It fixes a trio of potential security bugs, fixes a bug where
7247 we were leaving some of the fast relays out of the microdescriptor
7248 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
7249 and cleans up other smaller issues.
7251 o Major bugfixes (security):
7252 - Tear down the circuit if we get an unexpected SENDME cell. Clients
7253 could use this trick to make their circuits receive cells faster
7254 than our flow control would have allowed, or to gum up the network,
7255 or possibly to do targeted memory denial-of-service attacks on
7256 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
7257 from July 2002, before the release of Tor 0.0.0. We had committed
7258 this patch previously, but we had to revert it because of bug 6271.
7259 Now that 6271 is fixed, this patch appears to work.
7260 - Reject any attempt to extend to an internal address. Without
7261 this fix, a router could be used to probe addresses on an internal
7262 network to see whether they were accepting connections. Fixes bug
7263 6710; bugfix on 0.0.8pre1.
7264 - Do not crash when comparing an address with port value 0 to an
7265 address policy. This bug could have been used to cause a remote
7266 assertion failure by or against directory authorities, or to
7267 allow some applications to crash clients. Fixes bug 6690; bugfix
7271 - Remove the upper bound on microdescriptor length. We were hitting
7272 the limit for routers with complex exit policies or family
7273 declarations, causing clients to not use them. Fixes the first
7274 piece of bug 6404; fix on 0.2.2.6-alpha.
7275 - Detect "ORPort 0" as meaning, uniformly, that we're not running
7276 as a relay. Previously, some of our code would treat the presence
7277 of any ORPort line as meaning that we should act like a relay,
7278 even though our new listener code would correctly not open any
7279 ORPorts for ORPort 0. Similar bugs in other Port options are also
7280 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
7283 - Avoid a pair of double-free and use-after-mark bugs that can
7284 occur with certain timings in canceled and re-received DNS
7285 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
7286 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
7287 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
7288 - Allow one-hop directory fetching circuits the full "circuit build
7289 timeout" period, rather than just half of it, before failing them
7290 and marking the relay down. This fix should help reduce cases where
7291 clients declare relays (or worse, bridges) unreachable because
7292 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
7293 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
7295 - Authorities no longer include any router in their microdescriptor
7296 consensuses for which they couldn't generate or agree on a
7297 microdescriptor. Fixes the second piece of bug 6404; fix on
7299 - Detect and reject attempts to specify both "FooPort" and
7300 "FooPort 0" in the same configuration domain. (It's still okay
7301 to have a FooPort in your configuration file, and use "FooPort 0"
7302 on the command line to disable it.) Fixes the second half of bug
7303 6507; bugfix on 0.2.3.3-alpha.
7304 - Make wildcarded addresses (that is, ones beginning with "*.") work
7305 when provided via the controller's MapAddress command. Previously,
7306 they were accepted, but we never actually noticed that they were
7307 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
7308 - Avoid crashing on a malformed state file where EntryGuardPathBias
7309 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
7310 - Add a (probably redundant) memory clear between iterations of
7311 the router status voting loop, to prevent future coding errors
7312 where data might leak between iterations of the loop. Resolves
7315 o Minor bugfixes (log messages):
7316 - Downgrade "set buildtimeout to low value" messages to "info"
7317 severity; they were never an actual problem, there was never
7318 anything reasonable to do about them, and they tended to spam logs
7319 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
7320 - Downgrade path-bias warning messages to "info". We'll try to get
7321 them working better in 0.2.4. Add internal circuit construction
7322 state to protect against the noisy warn message "Unexpectedly high
7323 circuit_successes". Also add some additional rate-limited notice
7324 messages to help determine the root cause of the warn. Fixes bug
7325 6475. Bugfix against 0.2.3.17-beta.
7326 - Move log message when unable to find a microdesc in a routerstatus
7327 entry to parse time. Previously we'd spam this warning every time
7328 we tried to figure out which microdescriptors to download. Fixes
7329 the third piece of bug 6404; fix on 0.2.3.18-rc.
7332 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
7333 change when the authority is deciding whether to accept a newly
7334 uploaded descriptor. Implements ticket 6423.
7335 - Add missing documentation for consensus and microdesc files.
7336 Resolves ticket 6732.
7339 Changes in version 0.2.2.38 - 2012-08-12
7340 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
7341 attack that could in theory leak path information.
7344 - Avoid an uninitialized memory read when reading a vote or consensus
7345 document that has an unrecognized flavor name. This read could
7346 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
7347 - Try to leak less information about what relays a client is
7348 choosing to a side-channel attacker. Previously, a Tor client would
7349 stop iterating through the list of available relays as soon as it
7350 had chosen one, thus finishing a little earlier when it picked
7351 a router earlier in the list. If an attacker can recover this
7352 timing information (nontrivial but not proven to be impossible),
7353 they could learn some coarse-grained information about which relays
7354 a client was picking (middle nodes in particular are likelier to
7355 be affected than exits). The timing attack might be mitigated by
7356 other factors (see bug 6537 for some discussion), but it's best
7357 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
7360 Changes in version 0.2.3.20-rc - 2012-08-05
7361 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
7362 series. It fixes a pair of code security bugs and a potential anonymity
7363 issue, updates our RPM spec files, and cleans up other smaller issues.
7366 - Avoid read-from-freed-memory and double-free bugs that could occur
7367 when a DNS request fails while launching it. Fixes bug 6480;
7368 bugfix on 0.2.0.1-alpha.
7369 - Avoid an uninitialized memory read when reading a vote or consensus
7370 document that has an unrecognized flavor name. This read could
7371 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
7372 - Try to leak less information about what relays a client is
7373 choosing to a side-channel attacker. Previously, a Tor client would
7374 stop iterating through the list of available relays as soon as it
7375 had chosen one, thus finishing a little earlier when it picked
7376 a router earlier in the list. If an attacker can recover this
7377 timing information (nontrivial but not proven to be impossible),
7378 they could learn some coarse-grained information about which relays
7379 a client was picking (middle nodes in particular are likelier to
7380 be affected than exits). The timing attack might be mitigated by
7381 other factors (see bug 6537 for some discussion), but it's best
7382 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
7385 - Try to make the warning when giving an obsolete SOCKSListenAddress
7386 a little more useful.
7387 - Terminate active server managed proxies if Tor stops being a
7388 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
7389 - Provide a better error message about possible OSX Asciidoc failure
7390 reasons. Fixes bug 6436.
7391 - Warn when Tor is configured to use accounting in a way that can
7392 link a hidden service to some other hidden service or public
7393 address. Resolves ticket 6490.
7396 - Check return value of fputs() when writing authority certificate
7397 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
7398 - Ignore ServerTransportPlugin lines when Tor is not configured as
7399 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
7400 - When disabling guards for having too high a proportion of failed
7401 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
7405 - Update our default RPM spec files to work with mock and rpmbuild
7406 on RHEL/Fedora. They have an updated set of dependencies and
7407 conflicts, a fix for an ancient typo when creating the "_tor"
7408 user, and better instructions. Thanks to Ondrej Mikle for the
7409 patch series. Fixes bug 6043.
7412 - Make it possible to set the TestingTorNetwork configuration
7413 option using AlternateDirAuthority and AlternateBridgeAuthority
7414 as an alternative to setting DirServer. Addresses ticket 6377.
7417 - Clarify the documentation for the Alternate*Authority options.
7419 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
7421 o Code simplification and refactoring:
7422 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
7423 10 lines. Also, don't nest them. Doing so in the past has
7424 led to hard-to-debug code. The new style is to use the
7425 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
7428 Changes in version 0.2.3.19-rc - 2012-07-06
7429 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
7430 series. It fixes the compile on Windows, reverts to a GeoIP database
7431 that isn't as broken, and fixes a flow control bug that has been around
7432 since the beginning of Tor.
7435 - Fix a bug handling SENDME cells on nonexistent streams that could
7436 result in bizarre window values. Report and patch contributed
7437 pseudonymously. Fixes part of bug 6271. This bug was introduced
7438 before the first Tor release, in svn commit r152.
7439 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
7440 June 2012 database, Maxmind marked many Tor relays as country "A1",
7441 which will cause risky behavior for clients that set EntryNodes
7442 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
7443 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
7444 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
7447 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
7448 bugfix on 0.2.1.10-alpha.
7451 Changes in version 0.2.3.18-rc - 2012-06-28
7452 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
7453 series. It fixes a few smaller bugs, but generally appears stable.
7454 Please test it and let us know whether it is!
7457 - Allow wildcarded mapaddress targets to be specified on the
7458 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
7459 - Make our linker option detection code more robust against linkers
7460 such as on FreeBSD 8, where a bad combination of options completes
7461 successfully but makes an unrunnable binary. Fixes bug 6173;
7462 bugfix on 0.2.3.17-beta.
7464 o Minor bugfixes (on 0.2.2.x and earlier):
7465 - Avoid a false positive in the util/threads unit test by increasing
7466 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
7467 - Replace "Sending publish request" log messages with "Launching
7468 upload", so that they no longer confusingly imply that we're
7469 sending something to a directory we might not even be connected
7470 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
7471 - Make sure to set *socket_error in all error cases in
7472 connection_connect(), so it can't produce a warning about
7473 errno being zero from errno_to_orconn_end_reason(). Bugfix on
7474 0.2.1.1-alpha; resolves ticket 6028.
7475 - Downgrade "Got a certificate, but we already have it" log messages
7476 from warning to info, except when we're a dirauth. Fixes bug 5238;
7477 bugfix on 0.2.1.7-alpha.
7478 - When checking for requested signatures on the latest consensus
7479 before serving it to a client, make sure to check the right
7480 consensus flavor. Bugfix on 0.2.2.6-alpha.
7481 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
7482 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
7484 o Minor bugfixes (on 0.2.3.x):
7485 - Make format_helper_exit_status() avoid unnecessary space padding
7486 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
7488 - Downgrade a message about cleaning the microdescriptor cache to
7489 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
7490 - Log a BUG message at severity INFO if we have a networkstatus with
7491 a missing entry for some microdescriptor. Continues on a patch
7493 - Improve the log message when a managed proxy fails to launch. Fixes
7494 bug 5099; bugfix on 0.2.3.6-alpha.
7495 - Don't do DNS lookups when parsing corrupted managed proxy protocol
7496 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
7497 - When formatting wildcarded address mappings for the controller,
7498 be sure to include "*." as appropriate. Partially fixes bug 6244;
7499 bugfix on 0.2.3.9-alpha.
7500 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
7501 Bugfix on 0.2.3.13-alpha.
7502 - Stop logging messages about running with circuit timeout learning
7503 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
7504 - Disable a spurious warning about reading on a marked and flushing
7505 connection. We shouldn't be doing that, but apparently we
7506 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
7507 - Fix a bug that stopped AllowDotExit from working on addresses
7508 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
7511 o Code simplification, refactoring, unit tests:
7512 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
7513 Libevent's notion of cached time when possible.
7514 - Remove duplicate code for invoking getrlimit() from control.c.
7515 - Add a unit test for the environment_variable_names_equal function.
7518 - Document the --defaults-torrc option, and the new (in 0.2.3)
7519 semantics for overriding, extending, and clearing lists of
7520 options. Closes bug 4748.
7523 Changes in version 0.2.3.17-beta - 2012-06-15
7524 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
7525 gets our TLS handshake back on track for being able to blend in with
7526 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
7527 with Vidalia, and otherwise continues to get us closer to a release
7531 - Enable gcc and ld hardening by default. Resolves ticket 5210.
7532 - Update TLS cipher list to match Firefox 8 and later. Resolves
7534 - Implement the client side of proposal 198: remove support for
7535 clients falsely claiming to support standard ciphersuites that
7536 they can actually provide. As of modern OpenSSL versions, it's not
7537 necessary to fake any standard ciphersuite, and doing so prevents
7538 us from using better ciphersuites in the future, since servers
7539 can't know whether an advertised ciphersuite is really supported or
7540 not. Some hosts -- notably, ones with very old versions of OpenSSL
7541 or where OpenSSL has been built with ECC disabled -- will stand
7542 out because of this change; TBB users should not be affected.
7545 - Change the default value for DynamicDHGroups (introduced in
7546 0.2.3.9-alpha) to 0. This feature can make Tor relays less
7547 identifiable by their use of the mod_ssl DH group, but at
7548 the cost of some usability (#4721) and bridge tracing (#6087)
7549 regressions. Resolves ticket 5598.
7550 - Send a CRLF at the end of each STATUS_* control protocol event. This
7551 bug tickled a bug in Vidalia which would make it freeze. Fixes
7552 bug 6094; bugfix on 0.2.3.16-alpha.
7555 - Disable writing on marked-for-close connections when they are
7556 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
7557 bug 5263; bugfix on 0.0.2pre13, where we first added a special
7558 case for flushing marked connections.
7559 - Detect SSL handshake even when the initial attempt to write the
7560 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
7561 - Change the AllowDotExit rules so they should actually work.
7562 We now enforce AllowDotExit only immediately after receiving an
7563 address via SOCKS or DNSPort: other sources are free to provide
7564 .exit addresses after the resolution occurs. Fixes bug 3940;
7565 bugfix on 0.2.2.1-alpha.
7566 - Fix a (harmless) integer overflow in cell statistics reported by
7567 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
7568 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
7569 right places and never depends on the consensus parameters or
7570 computes adaptive timeouts when it is disabled. Fixes bug 5049;
7571 bugfix on 0.2.2.14-alpha.
7572 - When building Tor on Windows with -DUNICODE (not default), ensure
7573 that error messages, filenames, and DNS server names are always
7574 NUL-terminated when we convert them to a single-byte encoding.
7575 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
7576 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
7577 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
7578 - Fix an edge case where TestingTorNetwork is set but the authorities
7579 and relays all have an uptime of zero, where the private Tor network
7580 could briefly lack support for hidden services. Fixes bug 3886;
7581 bugfix on 0.2.2.18-alpha.
7582 - Correct the manpage's descriptions for the default values of
7583 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
7585 - Fix the documentation for the --hush and --quiet command line
7586 options, which changed their behavior back in 0.2.3.3-alpha.
7587 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
7591 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
7592 more information to it, so that we can track it down in case it
7593 returns again. Mitigates bug 5235.
7594 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
7595 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
7596 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
7597 - Warn the user when HTTPProxy, but no other proxy type, is
7598 configured. This can cause surprising behavior: it doesn't send
7599 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
7600 directory traffic only. Resolves ticket 4663.
7601 - Issue a notice if a guard completes less than 40% of your circuits.
7602 Threshold is configurable by torrc option PathBiasNoticeRate and
7603 consensus parameter pb_noticepct. There is additional, off-by-
7604 default code to disable guards which fail too many circuits.
7605 Addresses ticket 5458.
7606 - Update to the June 6 2012 Maxmind GeoLite Country database.
7608 o Code simplifications and refactoring:
7609 - Remove validate_pluggable_transports_config(): its warning
7610 message is now handled by connection_or_connect().
7613 Changes in version 0.2.2.37 - 2012-06-06
7614 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
7615 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
7619 - Work around a bug in OpenSSL that broke renegotiation with TLS
7620 1.1 and TLS 1.2. Without this workaround, all attempts to speak
7621 the v2 Tor connection protocol when both sides were using OpenSSL
7622 1.0.1 would fail. Resolves ticket 6033.
7623 - When waiting for a client to renegotiate, don't allow it to add
7624 any bytes to the input buffer. This fixes a potential DoS issue.
7625 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
7626 - Fix an edge case where if we fetch or publish a hidden service
7627 descriptor, we might build a 4-hop circuit and then use that circuit
7628 for exiting afterwards -- even if the new last hop doesn't obey our
7629 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
7632 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
7633 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
7636 - Tell GCC and Clang to check for any errors in format strings passed
7637 to the tor_v*(print|scan)f functions.
7640 Changes in version 0.2.3.16-alpha - 2012-06-05
7641 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
7642 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
7643 currently). It also fixes a variety of smaller bugs and other cleanups
7644 that get us closer to a release candidate.
7646 o Major bugfixes (general):
7647 - Work around a bug in OpenSSL that broke renegotiation with TLS
7648 1.1 and TLS 1.2. Without this workaround, all attempts to speak
7649 the v2 Tor connection protocol when both sides were using OpenSSL
7650 1.0.1 would fail. Resolves ticket 6033.
7651 - When waiting for a client to renegotiate, don't allow it to add
7652 any bytes to the input buffer. This fixes a potential DoS issue.
7653 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
7654 - Pass correct OR address to managed proxies (like obfsproxy),
7655 even when ORListenAddress is used. Fixes bug 4865; bugfix on
7657 - The advertised platform of a router now includes only its operating
7658 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
7659 service pack level (for Windows) or its CPU architecture (for Unix).
7660 We also no longer include the "git-XYZ" tag in the version. Resolves
7663 o Major bugfixes (clients):
7664 - If we are unable to find any exit that supports our predicted ports,
7665 stop calling them predicted, so that we don't loop and build
7666 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
7667 which introduced predicted ports.
7668 - Fix an edge case where if we fetch or publish a hidden service
7669 descriptor, we might build a 4-hop circuit and then use that circuit
7670 for exiting afterwards -- even if the new last hop doesn't obey our
7671 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
7672 - Check at each new consensus whether our entry guards were picked
7673 long enough ago that we should rotate them. Previously, we only
7674 did this check at startup, which could lead to us holding a guard
7675 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
7676 - When fetching a bridge descriptor from a bridge authority,
7677 always do so anonymously, whether we have been able to open
7678 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
7679 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
7680 but we'll need to wait for bug 6010 before it's actually usable.
7682 o Major bugfixes (directory authorities):
7683 - When computing weight parameters, behave more robustly in the
7684 presence of a bad bwweightscale value. Previously, the authorities
7685 would crash if they agreed on a sufficiently broken weight_scale
7686 value: now, they use a reasonable default and carry on. Partial
7687 fix for 5786; bugfix on 0.2.2.17-alpha.
7688 - Check more thoroughly to prevent a rogue authority from
7689 double-voting on any consensus directory parameter. Previously,
7690 authorities would crash in this case if the total number of
7691 votes for any parameter exceeded the number of active voters,
7692 but would let it pass otherwise. Partial fix for bug 5786; bugfix
7696 - Rate-limit log messages when asked to connect anonymously to
7697 a private address. When these hit, they tended to hit fast and
7698 often. Also, don't bother trying to connect to addresses that we
7699 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
7700 reply makes us think we have been lied to, even when the address the
7701 client tried to connect to was "localhost." Resolves ticket 2822.
7702 - Allow packagers to insert an extra string in server descriptor
7703 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
7704 Resolves the rest of ticket 2988.
7705 - Raise the threshold of server descriptors needed (75%) and exit
7706 server descriptors needed (50%) before we will declare ourselves
7707 bootstrapped. This will make clients start building circuits a
7708 little later, but makes the initially constructed circuits less
7709 skewed and less in conflict with further directory fetches. Fixes
7711 - Close any connection that sends unrecognized junk before the
7712 handshake. Solves an issue noted in bug 4369.
7713 - Improve log messages about managed transports. Resolves ticket 5070.
7714 - Tag a bridge's descriptor as "never to be sent unencrypted".
7715 This shouldn't matter, since bridges don't open non-anonymous
7716 connections to the bridge authority and don't allow unencrypted
7717 directory connections from clients, but we might as well make
7718 sure. Closes bug 5139.
7719 - Expose our view of whether we have gone dormant to the controller,
7720 via a new "GETINFO dormant" value. Torbutton and other controllers
7721 can use this to avoid doing periodic requests through Tor while
7722 it's dormant (bug 4718). Fixes bug 5954.
7723 - Tell GCC and Clang to check for any errors in format strings passed
7724 to the tor_v*(print|scan)f functions.
7725 - Update to the May 1 2012 Maxmind GeoLite Country database.
7727 o Minor bugfixes (already included in 0.2.2.36):
7728 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7729 Fixes bug 5346; bugfix on 0.0.8pre3.
7730 - Correct parsing of certain date types in parse_http_time().
7731 Without this patch, If-Modified-Since would behave
7732 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7733 Esteban Manchado Velázques.
7734 - Make our number-parsing functions always treat too-large values
7735 as an error, even when those values exceed the width of the
7736 underlying type. Previously, if the caller provided these
7737 functions with minima or maxima set to the extreme values of the
7738 underlying integer type, these functions would return those
7739 values on overflow rather than treating overflow as an error.
7740 Fixes part of bug 5786; bugfix on 0.0.9.
7741 - If we hit the error case where routerlist_insert() replaces an
7742 existing (old) server descriptor, make sure to remove that
7743 server descriptor from the old_routers list. Fix related to bug
7744 1776. Bugfix on 0.2.2.18-alpha.
7745 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7746 circuits. Fixes issue 5259.
7748 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
7749 - Prevent a null-pointer dereference when receiving a data cell
7750 for a nonexistent stream when the circuit in question has an
7751 empty deliver window. We don't believe this is triggerable,
7752 since we don't currently allow deliver windows to become empty,
7753 but the logic is tricky enough that it's better to make the code
7754 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
7755 - Fix a memory leak when trying to launch a DNS request when the
7756 network is disabled or the nameservers are unconfigurable. Fixes
7757 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
7758 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
7759 - Don't hold a Windows file handle open for every file mapping;
7760 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
7762 - Avoid O(n^2) performance characteristics when parsing a large
7763 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
7764 - Format more doubles with %f, not %lf. Patch from grarpamp to make
7765 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
7767 - Make our replacement implementation of strtok_r() compatible with
7768 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
7769 bugfix on 0.2.2.1-alpha.
7770 - Fix a NULL-pointer dereference on a badly formed
7771 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
7772 bugfix on 0.2.2.9-alpha.
7773 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
7774 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
7775 - Defensively refactor rend_mid_rendezvous() so that protocol
7776 violations and length checks happen in the beginning. Fixes
7778 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
7779 that IPv6 stuff will compile on MSVC, and compilation issues
7780 will be easier to track down. Fixes bug 5861.
7782 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
7783 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
7784 resource exhaustion, so that clients can adjust their load to
7785 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
7786 started using END_STREAM_REASON_RESOURCELIMIT.
7787 - Don't check for whether the address we're using for outbound
7788 connections has changed until after the outbound connection has
7789 completed. On Windows, getsockname() doesn't succeed until the
7790 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
7791 - If the configuration tries to set MyFamily on a bridge, refuse to
7792 do so, and warn about the security implications. Fixes bug 4657;
7793 bugfix on 0.2.0.3-alpha.
7794 - If the client fails to set a reasonable set of ciphersuites
7795 during its v2 handshake renegotiation, allow the renegotiation to
7796 continue nevertheless (i.e. send all the required certificates).
7797 Fixes bug 4591; bugfix on 0.2.0.20-rc.
7798 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
7799 option is set to 0 (which Vidalia version 0.2.16 now does when
7800 a SAVECONF attempt fails), perform other actions that SIGHUP
7801 usually causes (like reopening the logs). Fixes bug 5095; bugfix
7803 - If we fail to write a microdescriptor to the disk cache, do not
7804 continue replacing the old microdescriptor file. Fixes bug 2954;
7805 bugfix on 0.2.2.6-alpha.
7806 - Exit nodes don't need to fetch certificates for authorities that
7807 they don't recognize; only directory authorities, bridges,
7808 and caches need to do that. Fixes part of bug 2297; bugfix on
7810 - Correctly handle checking the permissions on the parent
7811 directory of a control socket in the root directory. Bug found
7812 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
7814 - When told to add a bridge with the same digest as a preexisting
7815 bridge but a different addr:port, change the addr:port as
7816 requested. Previously we would not notice the change. Fixes half
7817 of bug 5603; fix on 0.2.2.26-beta.
7818 - End AUTHCHALLENGE error messages (in the control protocol) with
7819 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
7821 o Minor bugfixes (on 0.2.3.x):
7822 - Turn an assertion (that the number of handshakes received as a
7823 server is not < 1) into a warning. Fixes bug 4873; bugfix on
7825 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
7826 we had reversed them when the answer was cached.) Fixes bug
7827 5723; bugfix on 0.2.3.1-alpha.
7828 - Work correctly on Linux systems with accept4 support advertised in
7829 their headers, but without accept4 support in the kernel. Fix
7830 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
7831 - When told to add a bridge with the same addr:port as a preexisting
7832 bridge but a different transport, change the transport as
7833 requested. Previously we would not notice the change. Fixes half
7834 of bug 5603; fix on 0.2.3.2-alpha.
7835 - Avoid a "double-reply" warning when replying to a SOCKS request
7836 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
7837 bugfix on 0.2.3.4-alpha.
7838 - Fix a bug where a bridge authority crashes if it has seen no
7839 directory requests when it's time to write statistics to disk.
7840 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
7842 - Don't try to open non-control listeners when DisableNetwork is set.
7843 Previously, we'd open all listeners, then immediately close them.
7844 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
7845 - Don't abort the managed proxy protocol if the managed proxy
7846 sends us an unrecognized line; ignore it instead. Fixes bug
7847 5910; bugfix on 0.2.3.9-alpha.
7848 - Fix a compile warning in crypto.c when compiling with clang 3.1.
7849 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
7850 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
7851 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
7852 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
7853 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
7854 - Resolve numerous small warnings and build issues with MSVC. Resolves
7857 o Documentation fixes:
7858 - Improve the manual's documentation for the NT Service command-line
7859 options. Addresses ticket 3964.
7860 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
7861 - Document the changes to the ORPort and DirPort options, and the
7862 fact that {OR/Dir}ListenAddress is now unnecessary (and
7863 therefore deprecated). Resolves ticket 5597.
7866 - Remove the torrc.bridge file: we don't use it for anything, and
7867 it had become badly desynchronized from torrc.sample. Resolves
7871 Changes in version 0.2.2.36 - 2012-05-24
7872 Tor 0.2.2.36 updates the addresses for two of the eight directory
7873 authorities, fixes some potential anonymity and security issues,
7874 and fixes several crash bugs.
7876 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
7877 known flaws, and nobody should be using them. You should upgrade. If
7878 you're using a Linux or BSD and its packages are obsolete, stop using
7879 those packages and upgrade anyway.
7881 o Directory authority changes:
7882 - Change IP address for maatuska (v3 directory authority).
7883 - Change IP address for ides (v3 directory authority), and rename
7887 - When building or running with any version of OpenSSL earlier
7888 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7889 versions have a bug (CVE-2011-4576) in which their block cipher
7890 padding includes uninitialized data, potentially leaking sensitive
7891 information to any peer with whom they make a SSLv3 connection. Tor
7892 does not use SSL v3 by default, but a hostile client or server
7893 could force an SSLv3 connection in order to gain information that
7894 they shouldn't have been able to get. The best solution here is to
7895 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7896 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7897 to make sure that the bug can't happen.
7898 - Never use a bridge or a controller-supplied node as an exit, even
7899 if its exit policy allows it. Found by wanoskarnet. Fixes bug
7900 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
7901 and 0.2.0.3-alpha (for bridge-purpose descriptors).
7902 - Only build circuits if we have a sufficient threshold of the total
7903 descriptors that are marked in the consensus with the "Exit"
7904 flag. This mitigates an attack proposed by wanoskarnet, in which
7905 all of a client's bridges collude to restrict the exit nodes that
7906 the client knows about. Fixes bug 5343.
7907 - Provide controllers with a safer way to implement the cookie
7908 authentication mechanism. With the old method, if another locally
7909 running program could convince a controller that it was the Tor
7910 process, then that program could trick the controller into telling
7911 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
7912 authentication method uses a challenge-response approach to prevent
7913 this attack. Fixes bug 5185; implements proposal 193.
7916 - Avoid logging uninitialized data when unable to decode a hidden
7917 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
7918 - Avoid a client-side assertion failure when receiving an INTRODUCE2
7919 cell on a general purpose circuit. Fixes bug 5644; bugfix on
7921 - Fix builds when the path to sed, openssl, or sha1sum contains
7922 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
7924 - Correct our replacements for the timeradd() and timersub() functions
7925 on platforms that lack them (for example, Windows). The timersub()
7926 function is used when expiring circuits, while timeradd() is
7927 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7928 bugfix on 0.2.2.24-alpha.
7929 - Fix the SOCKET_OK test that we use to tell when socket
7930 creation fails so that it works on Win64. Fixes part of bug 4533;
7931 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7934 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7935 Fixes bug 5346; bugfix on 0.0.8pre3.
7936 - Make our number-parsing functions always treat too-large values
7937 as an error, even when those values exceed the width of the
7938 underlying type. Previously, if the caller provided these
7939 functions with minima or maxima set to the extreme values of the
7940 underlying integer type, these functions would return those
7941 values on overflow rather than treating overflow as an error.
7942 Fixes part of bug 5786; bugfix on 0.0.9.
7943 - Older Linux kernels erroneously respond to strange nmap behavior
7944 by having accept() return successfully with a zero-length
7945 socket. When this happens, just close the connection. Previously,
7946 we would try harder to learn the remote address: but there was
7947 no such remote address to learn, and our method for trying to
7948 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7949 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7950 - Correct parsing of certain date types in parse_http_time().
7951 Without this patch, If-Modified-Since would behave
7952 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7953 Esteban Manchado Velázques.
7954 - Change the BridgePassword feature (part of the "bridge community"
7955 design, which is not yet implemented) to use a time-independent
7956 comparison. The old behavior might have allowed an adversary
7957 to use timing to guess the BridgePassword value. Fixes bug 5543;
7958 bugfix on 0.2.0.14-alpha.
7959 - Detect and reject certain misformed escape sequences in
7960 configuration values. Previously, these values would cause us
7961 to crash if received in a torrc file or over an authenticated
7962 control port. Bug found by Esteban Manchado Velázquez, and
7963 independently by Robert Connolly from Matta Consulting who further
7964 noted that it allows a post-authentication heap overflow. Patch
7965 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7966 bugfix on 0.2.0.16-alpha.
7967 - Fix a compile warning when using the --enable-openbsd-malloc
7968 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7969 - During configure, detect when we're building with clang version
7970 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7971 CFLAGS. clang doesn't support them yet.
7972 - When sending an HTTP/1.1 proxy request, include a Host header.
7973 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7974 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
7975 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
7976 - If we hit the error case where routerlist_insert() replaces an
7977 existing (old) server descriptor, make sure to remove that
7978 server descriptor from the old_routers list. Fix related to bug
7979 1776. Bugfix on 0.2.2.18-alpha.
7981 o Minor bugfixes (documentation and log messages):
7982 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7983 Fixes bug 4856; bugfix on Tor 0.0.6.
7984 - Update "ClientOnly" man page entry to explain that there isn't
7985 really any point to messing with it. Resolves ticket 5005.
7986 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7987 directory authority option (introduced in Tor 0.2.2.34).
7988 - Downgrade the "We're missing a certificate" message from notice
7989 to info: people kept mistaking it for a real problem, whereas it
7990 is seldom the problem even when we are failing to bootstrap. Fixes
7991 bug 5067; bugfix on 0.2.0.10-alpha.
7992 - Correctly spell "connect" in a log message on failure to create a
7993 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
7994 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7995 circuits. Fixes issue 5259.
7998 - Directory authorities now reject versions of Tor older than
7999 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
8000 inclusive. These versions accounted for only a small fraction of
8001 the Tor network, and have numerous known security issues. Resolves
8003 - Update to the May 1 2012 Maxmind GeoLite Country database.
8006 - When sending or relaying a RELAY_EARLY cell, we used to convert
8007 it to a RELAY cell if the connection was using the v1 link
8008 protocol. This was a workaround for older versions of Tor, which
8009 didn't handle RELAY_EARLY cells properly. Now that all supported
8010 versions can handle RELAY_EARLY cells, and now that we're enforcing
8011 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
8012 remove this workaround. Addresses bug 4786.
8015 Changes in version 0.2.3.15-alpha - 2012-04-30
8016 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
8017 the development branch build on Windows again.
8019 o Minor bugfixes (on 0.2.2.x and earlier):
8020 - Make sure that there are no unhandled pending TLS errors before
8021 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
8022 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
8023 Bugfix on 0.1.0.5-rc; fixes bug 4528.
8024 - Fix an assert that directory authorities could trigger on sighup
8025 during some configuration state transitions. We now don't treat
8026 it as a fatal error when the new descriptor we just generated in
8027 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
8028 - After we pick a directory mirror, we would refuse to use it if
8029 it's in our ExcludeExitNodes list, resulting in mysterious failures
8030 to bootstrap for people who just wanted to avoid exiting from
8031 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
8032 - When building with --enable-static-tor on OpenBSD, do not
8033 erroneously attempt to link -lrt. Fixes bug 5103.
8035 o Minor bugfixes (on 0.2.3.x):
8036 - When Tor is built with kernel headers from a recent (last few
8037 years) Linux kernel, do not fail to run on older (pre-2.6.28
8038 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
8039 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
8041 - Fix compilation with miniupnpc version 1.6; patch from
8042 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
8043 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
8044 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
8045 - Fix compilation on platforms without unistd.h, or where environ
8046 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
8049 - Directory authorities are now a little more lenient at accepting
8050 older router descriptors, or newer router descriptors that don't
8051 make big changes. This should help ameliorate past and future
8052 issues where routers think they have uploaded valid descriptors,
8053 but the authorities don't think so. Fix for ticket 2479.
8054 - Make the code that clients use to detect an address change be
8055 IPv6-aware, so that it won't fill clients' logs with error
8056 messages when trying to get the IPv4 address of an IPv6
8057 connection. Implements ticket 5537.
8060 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
8061 authorities needed to use it for a while to keep the network working
8062 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
8063 that was six months ago. As of now, it should no longer be needed
8067 Changes in version 0.2.3.14-alpha - 2012-04-23
8068 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
8069 candidate. It also dramatically speeds up AES: fast relays should
8070 consider switching to the newer OpenSSL library.
8072 o Directory authority changes:
8073 - Change IP address for ides (v3 directory authority), and rename
8077 - Avoid logging uninitialized data when unable to decode a hidden
8078 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
8079 - Avoid a client-side assertion failure when receiving an INTRODUCE2
8080 cell on a general purpose circuit. Fixes bug 5644; bugfix on
8082 - If authorities are unable to get a v2 consensus document from other
8083 directory authorities, they no longer fall back to fetching
8084 them from regular directory caches. Fixes bug 5635; bugfix on
8085 0.2.2.26-beta, where routers stopped downloading v2 consensus
8087 - When we start a Tor client with a normal consensus already cached,
8088 be willing to download a microdescriptor consensus. Fixes bug 4011;
8089 fix on 0.2.3.1-alpha.
8091 o Major features (performance):
8092 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
8093 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
8094 vectorized AES implementations as appropriate. These can be much,
8095 much faster than other AES implementations.
8097 o Minor bugfixes (0.2.2.x and earlier):
8098 - Don't launch more than 10 service-side introduction-point circuits
8099 for a hidden service in five minutes. Previously, we would consider
8100 launching more introduction-point circuits if at least one second
8101 had passed without any introduction-point circuits failing. Fixes
8102 bug 4607; bugfix on 0.0.7pre1.
8103 - Change the BridgePassword feature (part of the "bridge community"
8104 design, which is not yet implemented) to use a time-independent
8105 comparison. The old behavior might have allowed an adversary
8106 to use timing to guess the BridgePassword value. Fixes bug 5543;
8107 bugfix on 0.2.0.14-alpha.
8108 - Enforce correct return behavior of tor_vsscanf() when the '%%'
8109 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
8110 - When sending an HTTP/1.1 proxy request, include a Host header.
8111 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
8112 - Don't log that we have "decided to publish new relay descriptor"
8113 unless we are actually publishing a descriptor. Fixes bug 3942;
8114 bugfix on 0.2.2.28-beta.
8116 o Minor bugfixes (0.2.3.x):
8117 - Fix a bug where a bridge authority crashes (on a failed assert)
8118 if it has seen no directory requests when it's time to write
8119 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
8120 - Fix bug stomping on ORPort option NoListen and ignoring option
8121 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
8122 - In the testsuite, provide a large enough buffer in the tor_sscanf
8123 unit test. Otherwise we'd overrun that buffer and crash during
8124 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
8126 - Make sure we create the keys directory if it doesn't exist and we're
8127 about to store the dynamic Diffie-Hellman parameters. Fixes bug
8128 5572; bugfix on 0.2.3.13-alpha.
8129 - Fix a small memory leak when trying to decode incorrect base16
8130 authenticator during SAFECOOKIE authentication. Found by
8131 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
8134 - Add more information to a log statement that might help track down
8135 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
8136 non-IP address" messages (or any Bug messages, for that matter!),
8137 please let us know about it.
8138 - Relays now understand an IPv6 address when they get one from a
8139 directory server. Resolves ticket 4875.
8140 - Resolve IPv6 addresses in bridge and entry statistics to country
8141 code "??" which means we at least count them. Resolves ticket 5053;
8142 improves on 0.2.3.9-alpha.
8143 - Update to the April 3 2012 Maxmind GeoLite Country database.
8144 - Begin a doc/state-contents.txt file to explain the contents of
8145 the Tor state file. Fixes bug 2987.
8147 o Default torrc changes:
8148 - Stop listing "socksport 9050" in torrc.sample. We open a socks
8149 port on 9050 by default anyway, so this should not change anything
8151 - Stop mentioning the deprecated *ListenAddress options in
8152 torrc.sample. Fixes bug 5438.
8153 - Document unit of bandwidth related options in sample torrc.
8157 - The "torify" script no longer supports the "tsocks" socksifier
8158 tool, since tsocks doesn't support DNS and UDP right for Tor.
8159 Everyone should be using torsocks instead. Fixes bugs 3530 and
8160 5180. Based on a patch by "ugh".
8163 - Change the symmetric cipher interface so that creating and
8164 initializing a stream cipher are no longer separate functions.
8165 - Remove all internal support for unpadded RSA. We never used it, and
8166 it would be a bad idea to start.
8169 Changes in version 0.2.3.13-alpha - 2012-03-26
8170 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
8171 in managed pluggable transports, as well as providing other cleanups
8172 that get us closer to a release candidate.
8174 o Directory authority changes:
8175 - Change IP address for maatuska (v3 directory authority).
8178 - Provide controllers with a safer way to implement the cookie
8179 authentication mechanism. With the old method, if another locally
8180 running program could convince a controller that it was the Tor
8181 process, then that program could trick the controller into telling
8182 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
8183 authentication method uses a challenge-response approach to prevent
8184 this attack. Fixes bug 5185, implements proposal 193.
8185 - Never use a bridge or a controller-supplied node as an exit, even
8186 if its exit policy allows it. Found by wanoskarnet. Fixes bug
8187 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
8188 and 0.2.0.3-alpha (for bridge-purpose descriptors).
8189 - Only build circuits if we have a sufficient threshold of the total
8190 descriptors that are marked in the consensus with the "Exit"
8191 flag. This mitigates an attack proposed by wanoskarnet, in which
8192 all of a client's bridges collude to restrict the exit nodes that
8193 the client knows about. Fixes bug 5343.
8195 o Major bugfixes (on Tor 0.2.3.x):
8196 - Avoid an assert when managed proxies like obfsproxy are configured,
8197 and we receive HUP signals or setconf attempts too rapidly. This
8198 situation happens most commonly when Vidalia tries to attach to
8199 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
8200 bugfix on 0.2.3.6-alpha.
8201 - Fix a relay-side pluggable transports bug where managed proxies were
8202 unreachable from the Internet, because Tor asked them to bind on
8203 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
8204 - Stop discarding command-line arguments when TestingTorNetwork
8205 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
8206 0.2.3.9-alpha, where task 4552 added support for two layers of
8208 - Resume allowing the unit tests to run in gdb. This was accidentally
8209 made impossible when the DisableDebuggerAttachment option was
8210 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
8211 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
8212 0.2.3.11-alpha. Reported by Anthony G. Basile.
8214 o Minor bugfixes (on 0.2.2.x and earlier):
8215 - Ensure we don't cannibalize circuits that are longer than three hops
8216 already, so we don't end up making circuits with 5 or more
8217 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
8218 0.1.0.1-rc which introduced cannibalization.
8219 - Detect and reject certain misformed escape sequences in
8220 configuration values. Previously, these values would cause us
8221 to crash if received in a torrc file or over an authenticated
8222 control port. Bug found by Esteban Manchado Velázquez, and
8223 independently by Robert Connolly from Matta Consulting who further
8224 noted that it allows a post-authentication heap overflow. Patch
8225 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
8226 bugfix on 0.2.0.16-alpha.
8227 - Fix a compile warning when using the --enable-openbsd-malloc
8228 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
8229 - Directory caches no longer refuse to clean out descriptors because
8230 of missing v2 networkstatus documents, unless they're configured
8231 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
8232 0.2.2.26-beta. Patch by Daniel Bryg.
8233 - Update to the latest version of the tinytest unit testing framework.
8234 This includes a couple of bugfixes that can be relevant for
8235 running forked unit tests on Windows, and removes all reserved
8238 o Minor bugfixes (on 0.2.3.x):
8239 - On a failed pipe() call, don't leak file descriptors. Fixes bug
8240 4296; bugfix on 0.2.3.1-alpha.
8241 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
8242 until after we have received a CERTS cell. Fixes bug 4361; bugfix
8243 on 0.2.3.6-alpha. Patch by "frosty".
8244 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
8245 option, so that the IP stack doesn't decide to use it for IPv4
8246 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
8247 - Ensure that variables set in Tor's environment cannot override
8248 environment variables that Tor passes to a managed
8249 pluggable-transport proxy. Previously, Tor would pass every
8250 variable in its environment to managed proxies along with the new
8251 ones, in such a way that on many operating systems, the inherited
8252 environment variables would override those which Tor tried to
8253 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
8254 bugfix on 0.2.3.9-alpha for Windows.
8257 - A wide variety of new unit tests by Esteban Manchado Velázquez.
8258 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
8259 - Update to the March 6 2012 Maxmind GeoLite Country database.
8262 Changes in version 0.2.3.12-alpha - 2012-02-13
8263 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
8264 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
8265 when Tor is configured to use a pluggable transport like obfsproxy.
8268 - Fix builds when the path to sed, openssl, or sha1sum contains
8269 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
8271 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
8272 connections. This change should allow busy exit relays to stop
8273 running out of available sockets as quickly. Fixes bug 4950;
8274 bugfix on 0.2.2.26-beta.
8275 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
8276 would ask the bridge for microdescriptors, which are only supported
8277 in 0.2.3.x, and then fail to bootstrap when it didn't get the
8278 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
8279 - Properly set up obfsproxy's environment when in managed mode. The
8280 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
8281 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
8282 5076 and 5082; bugfix on 0.2.3.6-alpha.
8285 - Use the dead_strip option when building Tor on OS X. This reduces
8286 binary size by almost 19% when linking openssl and libevent
8287 statically, which we do for Tor Browser Bundle.
8288 - Fix broken URLs in the sample torrc file, and tell readers about
8289 the OutboundBindAddress, ExitPolicyRejectPrivate, and
8290 PublishServerDescriptor options. Addresses bug 4652.
8291 - Update to the February 7 2012 Maxmind GeoLite Country database.
8294 - Downgrade the "We're missing a certificate" message from notice
8295 to info: people kept mistaking it for a real problem, whereas it
8296 is seldom the problem even when we are failing to bootstrap. Fixes
8297 bug 5067; bugfix on 0.2.0.10-alpha.
8298 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
8299 managed pluggable transport server proxy's environment.
8300 Previously, we would put it there, even though Tor doesn't
8301 implement an 'extended server port' yet, and even though Tor
8302 almost certainly isn't listening at that address. For now, we set
8303 it to an empty string to avoid crashing older obfsproxies. Bugfix
8305 - Log the heartbeat message every HeartbeatPeriod seconds, not every
8306 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
8307 0.2.3.1-alpha. Bug reported by Scott Bennett.
8308 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
8309 bugfix on 0.2.3.11-alpha.
8310 - Update "ClientOnly" man page entry to explain that there isn't
8311 really any point to messing with it. Resolves ticket 5005.
8312 - Use the correct CVE number for CVE-2011-4576 in our comments and
8313 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
8316 o Code simplifications and refactoring:
8317 - Use the _WIN32 macro throughout our code to detect Windows.
8318 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
8322 Changes in version 0.2.3.11-alpha - 2012-01-22
8323 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
8324 the last step of the plan to limit maximum circuit length, includes
8325 a wide variety of hidden service performance and correctness fixes,
8326 works around an OpenSSL security flaw if your distro is too stubborn
8327 to upgrade, and fixes a bunch of smaller issues.
8330 - Now that Tor 0.2.0.x is completely deprecated, enable the final
8331 part of "Proposal 110: Avoiding infinite length circuits" by
8332 refusing all circuit-extend requests that do not use a relay_early
8333 cell. This change helps Tor resist a class of denial-of-service
8334 attacks by limiting the maximum circuit length.
8335 - Adjust the number of introduction points that a hidden service
8336 will try to maintain based on how long its introduction points
8337 remain in use and how many introductions they handle. Fixes
8339 - Try to use system facilities for enumerating local interface
8340 addresses, before falling back to our old approach (which was
8341 binding a UDP socket, and calling getsockname() on it). That
8342 approach was scaring OS X users whose draconian firewall
8343 software warned about binding to UDP sockets, regardless of
8344 whether packets were sent. Now we try to use getifaddrs(),
8345 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
8346 system supports. Resolves ticket 1827.
8348 o Major security workaround:
8349 - When building or running with any version of OpenSSL earlier
8350 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
8351 versions have a bug (CVE-2011-4576) in which their block cipher
8352 padding includes uninitialized data, potentially leaking sensitive
8353 information to any peer with whom they make a SSLv3 connection. Tor
8354 does not use SSL v3 by default, but a hostile client or server
8355 could force an SSLv3 connection in order to gain information that
8356 they shouldn't have been able to get. The best solution here is to
8357 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
8358 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
8359 to make sure that the bug can't happen.
8362 - Fix the SOCKET_OK test that we use to tell when socket
8363 creation fails so that it works on Win64. Fixes part of bug 4533;
8364 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
8365 - Correct our replacements for the timeradd() and timersub() functions
8366 on platforms that lack them (for example, Windows). The timersub()
8367 function is used when expiring circuits, while timeradd() is
8368 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
8369 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
8370 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
8371 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
8372 bug at runtime, not compile time, because some distributions hack
8373 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
8374 on 0.2.3.9-alpha. Found by Pascal.
8376 o Minor features (controller):
8377 - Use absolute path names when reporting the torrc filename in the
8378 control protocol, so a controller can more easily find the torrc
8379 file. Resolves bug 1101.
8380 - Extend the control protocol to report flags that control a circuit's
8381 path selection in CIRC events and in replies to 'GETINFO
8382 circuit-status'. Implements part of ticket 2411.
8383 - Extend the control protocol to report the hidden service address
8384 and current state of a hidden-service-related circuit in CIRC
8385 events and in replies to 'GETINFO circuit-status'. Implements part
8387 - When reporting the path to the cookie file to the controller,
8388 give an absolute path. Resolves ticket 4881.
8389 - Allow controllers to request an event notification whenever a
8390 circuit is cannibalized or its purpose is changed. Implements
8391 part of ticket 3457.
8392 - Include the creation time of a circuit in CIRC and CIRC2
8393 control-port events and the list produced by the 'GETINFO
8394 circuit-status' control-port command.
8396 o Minor features (directory authorities):
8397 - Directory authorities now reject versions of Tor older than
8398 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
8399 inclusive. These versions accounted for only a small fraction of
8400 the Tor network, and have numerous known security issues. Resolves
8402 - Authority operators can now vote for all relays in a given
8403 set of countries to be BadDir/BadExit/Invalid/Rejected.
8404 - Provide two consensus parameters (FastFlagMinThreshold and
8405 FastFlagMaxThreshold) to control the range of allowable bandwidths
8406 for the Fast directory flag. These allow authorities to run
8407 experiments on appropriate requirements for being a "Fast" node.
8408 The AuthDirFastGuarantee config value still applies. Implements
8410 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
8411 directory authority option (introduced in Tor 0.2.2.34).
8413 o Minor features (other):
8414 - Don't disable the DirPort when we cannot exceed our AccountingMax
8415 limit during this interval because the effective bandwidthrate is
8416 low enough. This is useful in a situation where AccountMax is only
8417 used as an additional safeguard or to provide statistics.
8418 - Prepend an informative header to generated dynamic_dh_params files.
8419 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
8420 EntryNodes will have no effect. Resolves issue 2571.
8421 - Log more useful messages when we fail to disable debugger
8423 - Log which authority we're missing votes from when we go to fetch
8424 them from the other auths.
8425 - Log (at debug level) whenever a circuit's purpose is changed.
8426 - Add missing documentation for the MaxClientCircuitsPending,
8427 UseMicrodescriptors, UserspaceIOCPBuffers, and
8428 _UseFilteringSSLBufferevents options, all introduced during
8430 - Update to the January 3 2012 Maxmind GeoLite Country database.
8432 o Minor bugfixes (hidden services):
8433 - Don't close hidden service client circuits which have almost
8434 finished connecting to their destination when they reach
8435 the normal circuit-build timeout. Previously, we would close
8436 introduction circuits which are waiting for an acknowledgement
8437 from the introduction point, and rendezvous circuits which have
8438 been specified in an INTRODUCE1 cell sent to a hidden service,
8439 after the normal CBT. Now, we mark them as 'timed out', and launch
8440 another rendezvous attempt in parallel. This behavior change can
8441 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
8442 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
8443 - Don't close hidden-service-side rendezvous circuits when they
8444 reach the normal circuit-build timeout. This behavior change can
8445 be disabled using the new
8446 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
8447 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
8448 - Make sure we never mark the wrong rendezvous circuit as having
8449 had its introduction cell acknowleged by the introduction-point
8450 relay. Previously, when we received an INTRODUCE_ACK cell on a
8451 client-side hidden-service introduction circuit, we might have
8452 marked a rendezvous circuit other than the one we specified in
8453 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
8454 a warning message and interfered with the hidden service
8455 connection-establishment process. Fixes bug 4759; bugfix on
8456 0.2.3.3-alpha, when we added the stream-isolation feature which
8457 might cause Tor to open multiple rendezvous circuits for the same
8459 - Don't trigger an assertion failure when we mark a new client-side
8460 hidden-service introduction circuit for close during the process
8461 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
8464 o Minor bugfixes (log messages):
8465 - Correctly spell "connect" in a log message on failure to create a
8466 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
8468 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
8469 Fixes bug 4856; bugfix on Tor 0.0.6.
8470 - Fix the log message describing how we work around discovering
8471 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
8472 4837; bugfix on 0.2.2.9-alpha.
8473 - When logging about a disallowed .exit name, do not also call it
8474 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
8476 o Minor bugfixes (build fixes):
8477 - During configure, detect when we're building with clang version
8478 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
8479 CFLAGS. clang doesn't support them yet.
8480 - During configure, search for library containing cos function as
8481 libm lives in libcore on some platforms (BeOS/Haiku). Linking
8482 against libm was hard-coded before. Fixes the first part of bug
8483 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
8485 - Detect attempts to build Tor on (as yet hypothetical) versions
8486 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
8487 fix for bug 4533. Bugfix on 0.2.2.28-beta.
8488 - Preprocessor directives should not be put inside the arguments
8489 of a macro. This would break compilation with GCC releases prior
8490 to version 3.3. We would never recommend such an old GCC version,
8491 but it is apparently required for binary compatibility on some
8492 platforms (namely, certain builds of Haiku). Fixes the other part
8493 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
8496 o Minor bugfixes (other):
8497 - Older Linux kernels erroneously respond to strange nmap behavior
8498 by having accept() return successfully with a zero-length
8499 socket. When this happens, just close the connection. Previously,
8500 we would try harder to learn the remote address: but there was
8501 no such remote address to learn, and our method for trying to
8502 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
8503 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
8504 - Fix null-pointer access that could occur if TLS allocation failed.
8505 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
8506 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
8507 accidentally been reverted.
8508 - Fix our implementation of crypto_random_hostname() so it can't
8509 overflow on ridiculously large inputs. (No Tor version has ever
8510 provided this kind of bad inputs, but let's be correct in depth.)
8511 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
8512 - Find more places in the code that should have been testing for
8513 invalid sockets using the SOCKET_OK macro. Required for a fix
8514 for bug 4533. Bugfix on 0.2.2.28-beta.
8515 - Fix an assertion failure when, while running with bufferevents, a
8516 connection finishes connecting after it is marked for close, but
8517 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
8518 - test_util_spawn_background_ok() hardcoded the expected value
8519 for ENOENT to 2. This isn't portable as error numbers are
8520 platform specific, and particularly the hurd has ENOENT at
8521 0x40000002. Construct expected string at runtime, using the correct
8522 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
8523 - Reject attempts to disable DisableDebuggerAttachment while Tor is
8524 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
8525 - Use an appropriate-width type for sockets in tor-fw-helper on
8526 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
8529 - When sending or relaying a RELAY_EARLY cell, we used to convert
8530 it to a RELAY cell if the connection was using the v1 link
8531 protocol. This was a workaround for older versions of Tor, which
8532 didn't handle RELAY_EARLY cells properly. Now that all supported
8533 versions can handle RELAY_EARLY cells, and now that we're enforcing
8534 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
8535 remove this workaround. Addresses bug 4786.
8537 o Code simplifications and refactoring:
8538 - Use OpenSSL's built-in SSL_state_string_long() instead of our
8539 own homebrewed ssl_state_to_string() replacement. Patch from
8540 Emile Snyder. Fixes bug 4653.
8541 - Use macros to indicate OpenSSL versions, so we don't need to worry
8542 about accidental hexadecimal bit shifts.
8543 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
8545 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
8546 - Use the smartlist_add_asprintf() alias more consistently.
8547 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
8548 invalid value, rather than just -1.
8549 - Rename a handful of old identifiers, mostly related to crypto
8550 structures and crypto functions. By convention, our "create an
8551 object" functions are called "type_new()", our "free an object"
8552 functions are called "type_free()", and our types indicate that
8553 they are types only with a final "_t". But a handful of older
8554 types and functions broke these rules, with function names like
8555 "type_create" or "subsystem_op_type", or with type names like
8559 Changes in version 0.2.3.10-alpha - 2011-12-16
8560 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
8561 Tor's buffers code. Absolutely everybody should upgrade.
8563 The bug relied on an incorrect calculation when making data continuous
8564 in one of our IO buffers, if the first chunk of the buffer was
8565 misaligned by just the wrong amount. The miscalculation would allow an
8566 attacker to overflow a piece of heap-allocated memory. To mount this
8567 attack, the attacker would need to either open a SOCKS connection to
8568 Tor's SocksPort (usually restricted to localhost), or target a Tor
8569 instance configured to make its connections through a SOCKS proxy
8570 (which Tor does not do by default).
8572 Good security practice requires that all heap-overflow bugs should be
8573 presumed to be exploitable until proven otherwise, so we are treating
8574 this as a potential code execution attack. Please upgrade immediately!
8575 This bug does not affect bufferevents-based builds of Tor. Special
8576 thanks to "Vektor" for reporting this issue to us!
8578 This release also contains a few minor bugfixes for issues discovered
8582 - Fix a heap overflow bug that could occur when trying to pull
8583 data into the first chunk of a buffer, when that chunk had
8584 already had some data drained from it. Fixes CVE-2011-2778;
8585 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8588 - If we can't attach streams to a rendezvous circuit when we
8589 finish connecting to a hidden service, clear the rendezvous
8590 circuit's stream-isolation state and try to attach streams
8591 again. Previously, we cleared rendezvous circuits' isolation
8592 state either too early (if they were freshly built) or not at all
8593 (if they had been built earlier and were cannibalized). Bugfix on
8594 0.2.3.3-alpha; fixes bug 4655.
8595 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
8596 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
8597 - Fix an assertion failure when a relay with accounting enabled
8598 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
8601 - Update to the December 6 2011 Maxmind GeoLite Country database.
8604 Changes in version 0.2.2.35 - 2011-12-16
8605 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
8606 buffers code. Absolutely everybody should upgrade.
8608 The bug relied on an incorrect calculation when making data continuous
8609 in one of our IO buffers, if the first chunk of the buffer was
8610 misaligned by just the wrong amount. The miscalculation would allow an
8611 attacker to overflow a piece of heap-allocated memory. To mount this
8612 attack, the attacker would need to either open a SOCKS connection to
8613 Tor's SocksPort (usually restricted to localhost), or target a Tor
8614 instance configured to make its connections through a SOCKS proxy
8615 (which Tor does not do by default).
8617 Good security practice requires that all heap-overflow bugs should be
8618 presumed to be exploitable until proven otherwise, so we are treating
8619 this as a potential code execution attack. Please upgrade immediately!
8620 This bug does not affect bufferevents-based builds of Tor. Special
8621 thanks to "Vektor" for reporting this issue to us!
8623 Tor 0.2.2.35 also fixes several bugs in previous versions, including
8624 crash bugs for unusual configurations, and a long-term bug that
8625 would prevent Tor from starting on Windows machines with draconian
8628 With this release, we remind everyone that 0.2.0.x has reached its
8629 formal end-of-life. Those Tor versions have many known flaws, and
8630 nobody should be using them. You should upgrade -- ideally to the
8631 0.2.2.x series. If you're using a Linux or BSD and its packages are
8632 obsolete, stop using those packages and upgrade anyway.
8634 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
8635 longer receive support after some time in early 2012.
8638 - Fix a heap overflow bug that could occur when trying to pull
8639 data into the first chunk of a buffer, when that chunk had
8640 already had some data drained from it. Fixes CVE-2011-2778;
8641 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8642 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
8643 that it doesn't attempt to allocate a socketpair. This could cause
8644 some problems on Windows systems with overzealous firewalls. Fix for
8645 bug 4457; workaround for Libevent versions 2.0.1-alpha through
8647 - If we mark an OR connection for close based on a cell we process,
8648 don't process any further cells on it. We already avoid further
8649 reads on marked-for-close connections, but now we also discard the
8650 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
8651 which was the first version where we might mark a connection for
8652 close based on processing a cell on it.
8653 - Correctly sanity-check that we don't underflow on a memory
8654 allocation (and then assert) for hidden service introduction
8655 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8656 bugfix on 0.2.1.5-alpha.
8657 - Fix a memory leak when we check whether a hidden service
8658 descriptor has any usable introduction points left. Fixes bug
8659 4424. Bugfix on 0.2.2.25-alpha.
8660 - Don't crash when we're running as a relay and don't have a GeoIP
8661 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
8662 we've had in the 0.2.3.x branch already.
8663 - When running as a client, do not print a misleading (and plain
8664 wrong) log message that we're collecting "directory request"
8665 statistics: clients don't collect statistics. Also don't create a
8666 useless (because empty) stats file in the stats/ directory. Fixes
8667 bug 4353; bugfix on 0.2.2.34.
8670 - Detect failure to initialize Libevent. This fix provides better
8671 detection for future instances of bug 4457.
8672 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
8673 function. This was eating up hideously large amounts of time on some
8674 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
8675 - Resolve an integer overflow bug in smartlist_ensure_capacity().
8676 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
8678 - Don't warn about unused log_mutex in log.c when building with
8679 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
8680 0.1.0.6-rc which introduced --disable-threads.
8681 - When configuring, starting, or stopping an NT service, stop
8682 immediately after the service configuration attempt has succeeded
8683 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
8684 - When sending a NETINFO cell, include the original address
8685 received for the other side, not its canonical address. Found
8686 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
8687 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
8688 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
8689 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
8690 occurred when a client tried to fetch a descriptor for a bridge
8691 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
8692 - Backport fixes for a pair of compilation warnings on Windows.
8693 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
8694 - If we had ever tried to call tor_addr_to_str on an address of
8695 unknown type, we would have done a strdup on an uninitialized
8696 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
8697 Reported by "troll_un".
8698 - Correctly detect and handle transient lookup failures from
8699 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
8700 Reported by "troll_un".
8701 - Fix null-pointer access that could occur if TLS allocation failed.
8702 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
8703 - Use tor_socket_t type for listener argument to accept(). Fixes bug
8704 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
8707 - Add two new config options for directory authorities:
8708 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
8709 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
8710 that is always sufficient to satisfy the bandwidth requirement for
8711 the Guard flag. Now it will be easier for researchers to simulate
8712 Tor networks with different values. Resolves ticket 4484.
8713 - When Tor ignores a hidden service specified in its configuration,
8714 include the hidden service's directory in the warning message.
8715 Previously, we would only tell the user that some hidden service
8716 was ignored. Bugfix on 0.0.6; fixes bug 4426.
8717 - Update to the December 6 2011 Maxmind GeoLite Country database.
8719 o Packaging changes:
8720 - Make it easier to automate expert package builds on Windows,
8721 by removing an absolute path from makensis.exe command.
8724 Changes in version 0.2.1.32 - 2011-12-16
8725 Tor 0.2.1.32 backports important security and privacy fixes for
8726 oldstable. This release is intended only for package maintainers and
8727 others who cannot use the 0.2.2 stable series. All others should be
8728 using Tor 0.2.2.x or newer.
8730 The Tor 0.2.1.x series will reach formal end-of-life some time in
8731 early 2012; we will stop releasing patches for it then.
8733 o Major bugfixes (also included in 0.2.2.x):
8734 - Correctly sanity-check that we don't underflow on a memory
8735 allocation (and then assert) for hidden service introduction
8736 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8737 bugfix on 0.2.1.5-alpha.
8738 - Fix a heap overflow bug that could occur when trying to pull
8739 data into the first chunk of a buffer, when that chunk had
8740 already had some data drained from it. Fixes CVE-2011-2778;
8741 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8744 - Update to the December 6 2011 Maxmind GeoLite Country database.
8747 Changes in version 0.2.3.9-alpha - 2011-12-08
8748 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
8749 a "DisableNetwork" security feature that bundles can use to avoid
8750 touching the network until bridges are configured, moves forward on
8751 the pluggable transport design, fixes a flaw in the hidden service
8752 design that unnecessarily prevented clients with wrong clocks from
8753 reaching hidden services, and fixes a wide variety of other issues.
8756 - Clients can now connect to private bridges over IPv6. Bridges
8757 still need at least one IPv4 address in order to connect to
8758 other relays. Note that we don't yet handle the case where the
8759 user has two bridge lines for the same bridge (one IPv4, one
8760 IPv6). Implements parts of proposal 186.
8761 - New "DisableNetwork" config option to prevent Tor from launching any
8762 connections or accepting any connections except on a control port.
8763 Bundles and controllers can set this option before letting Tor talk
8764 to the rest of the network, for example to prevent any connections
8765 to a non-bridge address. Packages like Orbot can also use this
8766 option to instruct Tor to save power when the network is off.
8767 - Clients and bridges can now be configured to use a separate
8768 "transport" proxy. This approach makes the censorship arms race
8769 easier by allowing bridges to use protocol obfuscation plugins. It
8770 implements the "managed proxy" part of proposal 180 (ticket 3472).
8771 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
8772 implementation. It makes AES_CTR about 7% faster than our old one
8773 (which was about 10% faster than the one OpenSSL used to provide).
8774 Resolves ticket 4526.
8775 - Add a "tor2web mode" for clients that want to connect to hidden
8776 services non-anonymously (and possibly more quickly). As a safety
8777 measure to try to keep users from turning this on without knowing
8778 what they are doing, tor2web mode must be explicitly enabled at
8779 compile time, and a copy of Tor compiled to run in tor2web mode
8780 cannot be used as a normal Tor client. Implements feature 2553.
8781 - Add experimental support for running on Windows with IOCP and no
8782 kernel-space socket buffers. This feature is controlled by a new
8783 "UserspaceIOCPBuffers" config option (off by default), which has
8784 no effect unless Tor has been built with support for bufferevents,
8785 is running on Windows, and has enabled IOCP. This may, in the long
8786 run, help solve or mitigate bug 98.
8787 - Use a more secure consensus parameter voting algorithm. Now at
8788 least three directory authorities or a majority of them must
8789 vote on a given parameter before it will be included in the
8790 consensus. Implements proposal 178.
8793 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
8794 They used to check that the timestamp was within 30 minutes
8795 of their system clock, so they could cap the size of their
8796 replay-detection cache, but that approach unnecessarily refused
8797 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
8798 the v3 intro-point protocol (the first one which sent a timestamp
8799 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
8800 - Only use the EVP interface when AES acceleration is enabled,
8801 to avoid a 5-7% performance regression. Resolves issue 4525;
8802 bugfix on 0.2.3.8-alpha.
8804 o Privacy/anonymity features (bridge detection):
8805 - Make bridge SSL certificates a bit more stealthy by using random
8806 serial numbers, in the same fashion as OpenSSL when generating
8807 self-signed certificates. Implements ticket 4584.
8808 - Introduce a new config option "DynamicDHGroups", enabled by
8809 default, which provides each bridge with a unique prime DH modulus
8810 to be used during SSL handshakes. This option attempts to help
8811 against censors who might use the Apache DH modulus as a static
8812 identifier for bridges. Addresses ticket 4548.
8814 o Minor features (new/different config options):
8815 - New configuration option "DisableDebuggerAttachment" (on by default)
8816 to prevent basic debugging attachment attempts by other processes.
8817 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
8818 - Allow MapAddress directives to specify matches against super-domains,
8819 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
8820 Implements issue 933.
8821 - Slightly change behavior of "list" options (that is, config
8822 options that can appear more than once) when they appear both in
8823 torrc and on the command line. Previously, the command-line options
8824 would be appended to the ones from torrc. Now, the command-line
8825 options override the torrc options entirely. This new behavior
8826 allows the user to override list options (like exit policies and
8827 ports to listen on) from the command line, rather than simply
8828 appending to the list.
8829 - You can get the old (appending) command-line behavior for "list"
8830 options by prefixing the option name with a "+".
8831 - You can remove all the values for a "list" option from the command
8832 line without adding any new ones by prefixing the option name
8834 - Add experimental support for a "defaults" torrc file to be parsed
8835 before the regular torrc. Torrc options override the defaults file's
8836 options in the same way that the command line overrides the torrc.
8837 The SAVECONF controller command saves only those options which
8838 differ between the current configuration and the defaults file. HUP
8839 reloads both files. (Note: This is an experimental feature; its
8840 behavior will probably be refined in future 0.2.3.x-alpha versions
8841 to better meet packagers' needs.) Implements task 4552.
8844 - Try to make the introductory warning message that Tor prints on
8845 startup more useful for actually finding help and information.
8846 Resolves ticket 2474.
8847 - Running "make version" now displays the version of Tor that
8848 we're about to build. Idea from katmagic; resolves issue 4400.
8849 - Expire old or over-used hidden service introduction points.
8850 Required by fix for bug 3460.
8851 - Move the replay-detection cache for the RSA-encrypted parts of
8852 INTRODUCE2 cells to the introduction point data structures.
8853 Previously, we would use one replay-detection cache per hidden
8854 service. Required by fix for bug 3460.
8855 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
8856 public key replay-detection cache from 60 minutes to 5 minutes. This
8857 replay-detection cache is now used only to detect multiple
8858 INTRODUCE2 cells specifying the same rendezvous point, so we can
8859 avoid launching multiple simultaneous attempts to connect to it.
8861 o Minor bugfixes (on Tor 0.2.2.x and earlier):
8862 - Resolve an integer overflow bug in smartlist_ensure_capacity().
8863 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
8865 - Fix a minor formatting issue in one of tor-gencert's error messages.
8867 - Prevent a false positive from the check-spaces script, by disabling
8868 the "whitespace between function name and (" check for functions
8870 - Fix a log message suggesting that people contact a non-existent
8871 email address. Fixes bug 3448.
8872 - Fix null-pointer access that could occur if TLS allocation failed.
8873 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
8874 - Report a real bootstrap problem to the controller on router
8875 identity mismatch. Previously we just said "foo", which probably
8876 made a lot of sense at the time. Fixes bug 4169; bugfix on
8878 - If we had ever tried to call tor_addr_to_str() on an address of
8879 unknown type, we would have done a strdup() on an uninitialized
8880 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
8881 Reported by "troll_un".
8882 - Correctly detect and handle transient lookup failures from
8883 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
8884 Reported by "troll_un".
8885 - Use tor_socket_t type for listener argument to accept(). Fixes bug
8886 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
8887 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
8888 bug 4532; found by "troll_un".
8890 o Minor bugfixes (on Tor 0.2.3.x):
8891 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
8893 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
8894 circuit for use as a hidden service client's rendezvous point.
8895 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
8896 with help from wanoskarnet.
8897 - Restore behavior of overriding SocksPort, ORPort, and similar
8898 options from the command line. Bugfix on 0.2.3.3-alpha.
8901 - Properly handle the case where the build-tree is not the same
8902 as the source tree when generating src/common/common_sha1.i,
8903 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
8904 bugfix on 0.2.0.1-alpha.
8906 o Code simplifications, cleanups, and refactorings:
8907 - Remove the pure attribute from all functions that used it
8908 previously. In many cases we assigned it incorrectly, because the
8909 functions might assert or call impure functions, and we don't have
8910 evidence that keeping the pure attribute is worthwhile. Implements
8911 changes suggested in ticket 4421.
8912 - Remove some dead code spotted by coverity. Fixes cid 432.
8913 Bugfix on 0.2.3.1-alpha, closes bug 4637.
8916 Changes in version 0.2.3.8-alpha - 2011-11-22
8917 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
8918 socketpair-related bug that has been bothering Windows users. It adds
8919 support to serve microdescriptors to controllers, so Vidalia's network
8920 map can resume listing relays (once Vidalia implements its side),
8921 and adds better support for hardware AES acceleration. Finally, it
8922 starts the process of adjusting the bandwidth cutoff for getting the
8923 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
8924 that tiny relays harm performance more than they help network capacity.
8927 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
8928 that it doesn't attempt to allocate a socketpair. This could cause
8929 some problems on Windows systems with overzealous firewalls. Fix for
8930 bug 4457; workaround for Libevent versions 2.0.1-alpha through
8932 - Correctly sanity-check that we don't underflow on a memory
8933 allocation (and then assert) for hidden service introduction
8934 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8935 bugfix on 0.2.1.5-alpha.
8936 - Remove the artificially low cutoff of 20KB to guarantee the Fast
8937 flag. In the past few years the average relay speed has picked
8938 up, and while the "top 7/8 of the network get the Fast flag" and
8939 "all relays with 20KB or more of capacity get the Fast flag" rules
8940 used to have the same result, now the top 7/8 of the network has
8941 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
8942 - Fix a rare assertion failure when checking whether a v0 hidden
8943 service descriptor has any usable introduction points left, and
8944 we don't have enough information to build a circuit to the first
8945 intro point named in the descriptor. The HS client code in
8946 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
8947 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
8948 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
8949 - Make bridge authorities not crash when they are asked for their own
8950 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
8951 - When running as a client, do not print a misleading (and plain
8952 wrong) log message that we're collecting "directory request"
8953 statistics: clients don't collect statistics. Also don't create a
8954 useless (because empty) stats file in the stats/ directory. Fixes
8955 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
8958 - Allow Tor controllers like Vidalia to obtain the microdescriptor
8959 for a relay by identity digest or nickname. Previously,
8960 microdescriptors were only available by their own digests, so a
8961 controller would have to ask for and parse the whole microdescriptor
8962 consensus in order to look up a single relay's microdesc. Fixes
8963 bug 3832; bugfix on 0.2.3.1-alpha.
8964 - Use OpenSSL's EVP interface for AES encryption, so that all AES
8965 operations can use hardware acceleration (if present). Resolves
8968 o Minor bugfixes (on 0.2.2.x and earlier):
8969 - Detect failure to initialize Libevent. This fix provides better
8970 detection for future instances of bug 4457.
8971 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
8972 function. This was eating up hideously large amounts of time on some
8973 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
8974 - Don't warn about unused log_mutex in log.c when building with
8975 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
8976 0.1.0.6-rc which introduced --disable-threads.
8977 - Allow manual 'authenticate' commands to the controller interface
8978 from netcat (nc) as well as telnet. We were rejecting them because
8979 they didn't come with the expected whitespace at the end of the
8980 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
8981 - Fix some (not actually triggerable) buffer size checks in usage of
8982 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
8984 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
8985 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
8986 - When configuring, starting, or stopping an NT service, stop
8987 immediately after the service configuration attempt has succeeded
8988 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
8989 - When sending a NETINFO cell, include the original address
8990 received for the other side, not its canonical address. Found
8991 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
8992 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
8993 can pick them up when the tests aren't disabled. Bugfix on
8994 0.2.2.4-alpha which introduced tinytest.
8995 - Fix a memory leak when we check whether a hidden service
8996 descriptor has any usable introduction points left. Fixes bug
8997 4424. Bugfix on 0.2.2.25-alpha.
8998 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
8999 occurred when a client tried to fetch a descriptor for a bridge
9000 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
9002 o Minor bugfixes (on 0.2.3.x):
9003 - Make util unit tests build correctly with MSVC. Bugfix on
9004 0.2.3.3-alpha. Patch by Gisle Vanem.
9005 - Successfully detect AUTH_CHALLENGE cells with no recognized
9006 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
9008 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
9009 it should still send a NETINFO cell to allow the connection to
9010 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
9012 - Log less loudly when we get an invalid authentication certificate
9013 from a source other than a directory authority: it's not unusual
9014 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
9016 - Tolerate servers with more clock skew in their authentication
9017 certificates than previously. Fixes bug 4371; bugfix on
9019 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
9020 on 0.2.3.4-alpha and 0.2.3.6-alpha.
9023 - Add two new config options for directory authorities:
9024 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
9025 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
9026 that is always sufficient to satisfy the bandwidth requirement for
9027 the Guard flag. Now it will be easier for researchers to simulate
9028 Tor networks with different values. Resolves ticket 4484.
9029 - When Tor ignores a hidden service specified in its configuration,
9030 include the hidden service's directory in the warning message.
9031 Previously, we would only tell the user that some hidden service
9032 was ignored. Bugfix on 0.0.6; fixes bug 4426.
9033 - When we fail to initialize Libevent, retry with IOCP disabled so we
9034 don't need to turn on multi-threading support in Libevent, which in
9035 turn requires a working socketpair(). This is a workaround for bug
9036 4457, which affects Libevent versions from 2.0.1-alpha through
9038 - Detect when we try to build on a platform that doesn't define
9039 AF_UNSPEC to 0. We don't work there, so refuse to compile.
9040 - Update to the November 1 2011 Maxmind GeoLite Country database.
9042 o Packaging changes:
9043 - Make it easier to automate expert package builds on Windows,
9044 by removing an absolute path from makensis.exe command.
9046 o Code simplifications and refactoring:
9047 - Remove some redundant #include directives throughout the code.
9048 Patch from Andrea Gelmini.
9049 - Unconditionally use OpenSSL's AES implementation instead of our
9050 old built-in one. OpenSSL's AES has been better for a while, and
9051 relatively few servers should still be on any version of OpenSSL
9052 that doesn't have good optimized assembly AES.
9053 - Use the name "CERTS" consistently to refer to the new cell type;
9054 we were calling it CERT in some places and CERTS in others.
9057 - Numerous new unit tests for functions in util.c and address.c by
9059 - The long-disabled benchmark tests are now split into their own
9060 ./src/test/bench binary.
9061 - The benchmark tests can now use more accurate timers than
9062 gettimeofday() when such timers are available.
9065 Changes in version 0.2.3.7-alpha - 2011-10-30
9066 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
9067 the new v3 handshake. It also resolves yet another bridge address
9071 - If we mark an OR connection for close based on a cell we process,
9072 don't process any further cells on it. We already avoid further
9073 reads on marked-for-close connections, but now we also discard the
9074 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
9075 which was the first version where we might mark a connection for
9076 close based on processing a cell on it.
9077 - Fix a double-free bug that would occur when we received an invalid
9078 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
9079 bugfix on 0.2.3.6-alpha.
9080 - Bridges no longer include their address in NETINFO cells on outgoing
9081 OR connections, to allow them to blend in better with clients.
9082 Removes another avenue for enumerating bridges. Reported by
9083 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
9084 cells were introduced.
9087 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
9088 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
9091 Changes in version 0.2.3.6-alpha - 2011-10-26
9092 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
9093 anonymity vulnerability where an attacker can deanonymize Tor
9094 users. Everybody should upgrade.
9096 This release also features support for a new v3 connection handshake
9097 protocol, and fixes to make hidden service connections more robust.
9100 - Implement a new handshake protocol (v3) for authenticating Tors to
9101 each other over TLS. It should be more resistant to fingerprinting
9102 than previous protocols, and should require less TLS hacking for
9103 future Tor implementations. Implements proposal 176.
9104 - Allow variable-length padding cells to disguise the length of
9105 Tor's TLS records. Implements part of proposal 184.
9107 o Privacy/anonymity fixes (clients):
9108 - Clients and bridges no longer send TLS certificate chains on
9109 outgoing OR connections. Previously, each client or bridge would
9110 use the same cert chain for all outgoing OR connections until
9111 its IP address changes, which allowed any relay that the client
9112 or bridge contacted to determine which entry guards it is using.
9113 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
9114 - If a relay receives a CREATE_FAST cell on a TLS connection, it
9115 no longer considers that connection as suitable for satisfying a
9116 circuit EXTEND request. Now relays can protect clients from the
9117 CVE-2011-2768 issue even if the clients haven't upgraded yet.
9118 - Directory authorities no longer assign the Guard flag to relays
9119 that haven't upgraded to the above "refuse EXTEND requests
9120 to client connections" fix. Now directory authorities can
9121 protect clients from the CVE-2011-2768 issue even if neither
9122 the clients nor the relays have upgraded yet. There's a new
9123 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
9124 to let us transition smoothly, else tomorrow there would be no
9127 o Major bugfixes (hidden services):
9128 - Improve hidden service robustness: when an attempt to connect to
9129 a hidden service ends, be willing to refetch its hidden service
9130 descriptors from each of the HSDir relays responsible for them
9131 immediately. Previously, we would not consider refetching the
9132 service's descriptors from each HSDir for 15 minutes after the last
9133 fetch, which was inconvenient if the hidden service was not running
9134 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
9135 - When one of a hidden service's introduction points appears to be
9136 unreachable, stop trying it. Previously, we would keep trying
9137 to build circuits to the introduction point until we lost the
9138 descriptor, usually because the user gave up and restarted Tor.
9139 Partly fixes bug 3825.
9140 - Don't launch a useless circuit after failing to use one of a
9141 hidden service's introduction points. Previously, we would
9142 launch a new introduction circuit, but not set the hidden service
9143 which that circuit was intended to connect to, so it would never
9144 actually be used. A different piece of code would then create a
9145 new introduction circuit correctly. Bug reported by katmagic and
9146 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
9148 o Major bugfixes (other):
9149 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
9150 that they initiated. Relays could distinguish incoming bridge
9151 connections from client connections, creating another avenue for
9152 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
9153 Found by "frosty_un".
9154 - Don't update the AccountingSoftLimitHitAt state file entry whenever
9155 tor gets started. This prevents a wrong average bandwidth
9156 estimate, which would cause relays to always start a new accounting
9157 interval at the earliest possible moment. Fixes bug 2003; bugfix
9158 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
9159 immensely in tracking this bug down.
9160 - Fix a crash bug when changing node restrictions while a DNS lookup
9161 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
9164 o Minor bugfixes (on 0.2.2.x and earlier):
9165 - When a hidden service turns an extra service-side introduction
9166 circuit into a general-purpose circuit, free the rend_data and
9167 intro_key fields first, so we won't leak memory if the circuit
9168 is cannibalized for use as another service-side introduction
9169 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
9170 - Rephrase the log message emitted if the TestSocks check is
9171 successful. Patch from Fabian Keil; fixes bug 4094.
9172 - Bridges now skip DNS self-tests, to act a little more stealthily.
9173 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
9174 bridges. Patch by "warms0x".
9175 - Remove a confusing dollar sign from the example fingerprint in the
9176 man page, and also make the example fingerprint a valid one. Fixes
9177 bug 4309; bugfix on 0.2.1.3-alpha.
9178 - Fix internal bug-checking logic that was supposed to catch
9179 failures in digest generation so that it will fail more robustly
9180 if we ask for a nonexistent algorithm. Found by Coverity Scan.
9181 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
9182 - Report any failure in init_keys() calls launched because our
9183 IP address has changed. Spotted by Coverity Scan. Bugfix on
9184 0.1.1.4-alpha; fixes CID 484.
9186 o Minor bugfixes (on 0.2.3.x):
9187 - Fix a bug in configure.in that kept it from building a configure
9188 script with autoconf versions earlier than 2.61. Fixes bug 2430;
9189 bugfix on 0.2.3.1-alpha.
9190 - Don't warn users that they are exposing a client port to the
9191 Internet if they have specified an RFC1918 address. Previously,
9192 we would warn if the user had specified any non-loopback
9193 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
9194 - Fix memory leaks in the failing cases of the new SocksPort and
9195 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
9196 fixes coverity CIDs 485, 486, and 487.
9199 - When a hidden service's introduction point times out, consider
9200 trying it again during the next attempt to connect to the
9201 HS. Previously, we would not try it again unless a newly fetched
9202 descriptor contained it. Required by fixes for bugs 1297 and 3825.
9203 - The next version of Windows will be called Windows 8, and it has
9204 a major version of 6, minor version of 2. Correctly identify that
9205 version instead of calling it "Very recent version". Resolves
9206 ticket 4153; reported by funkstar.
9207 - The Bridge Authority now writes statistics on how many bridge
9208 descriptors it gave out in total, and how many unique descriptors
9209 it gave out. It also lists how often the most and least commonly
9210 fetched descriptors were given out, as well as the median and
9211 25th/75th percentile. Implements tickets 4200 and 4294.
9212 - Update to the October 4 2011 Maxmind GeoLite Country database.
9214 o Code simplifications and refactoring:
9215 - Remove some old code to remember statistics about which descriptors
9216 we've served as a directory mirror. The feature wasn't used and
9217 is outdated now that microdescriptors are around.
9218 - Rename Tor functions that turn strings into addresses, so that
9219 "parse" indicates that no hostname resolution occurs, and
9220 "lookup" indicates that hostname resolution may occur. This
9221 should help prevent mistakes in the future. Fixes bug 3512.
9224 Changes in version 0.2.2.34 - 2011-10-26
9225 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
9226 can deanonymize Tor users. Everybody should upgrade.
9228 The attack relies on four components: 1) Clients reuse their TLS cert
9229 when talking to different relays, so relays can recognize a user by
9230 the identity key in her cert. 2) An attacker who knows the client's
9231 identity key can probe each guard relay to see if that identity key
9232 is connected to that guard relay right now. 3) A variety of active
9233 attacks in the literature (starting from "Low-Cost Traffic Analysis
9234 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
9235 discover the guard relays that a Tor user visiting the website is using.
9236 4) Clients typically pick three guards at random, so the set of guards
9237 for a given user could well be a unique fingerprint for her. This
9238 release fixes components #1 and #2, which is enough to block the attack;
9239 the other two remain as open research problems. Special thanks to
9240 "frosty_un" for reporting the issue to us!
9242 Clients should upgrade so they are no longer recognizable by the TLS
9243 certs they present. Relays should upgrade so they no longer allow a
9244 remote attacker to probe them to test whether unpatched clients are
9245 currently connected to them.
9247 This release also fixes several vulnerabilities that allow an attacker
9248 to enumerate bridge relays. Some bridge enumeration attacks still
9249 remain; see for example proposal 188.
9251 o Privacy/anonymity fixes (clients):
9252 - Clients and bridges no longer send TLS certificate chains on
9253 outgoing OR connections. Previously, each client or bridge would
9254 use the same cert chain for all outgoing OR connections until
9255 its IP address changes, which allowed any relay that the client
9256 or bridge contacted to determine which entry guards it is using.
9257 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
9258 - If a relay receives a CREATE_FAST cell on a TLS connection, it
9259 no longer considers that connection as suitable for satisfying a
9260 circuit EXTEND request. Now relays can protect clients from the
9261 CVE-2011-2768 issue even if the clients haven't upgraded yet.
9262 - Directory authorities no longer assign the Guard flag to relays
9263 that haven't upgraded to the above "refuse EXTEND requests
9264 to client connections" fix. Now directory authorities can
9265 protect clients from the CVE-2011-2768 issue even if neither
9266 the clients nor the relays have upgraded yet. There's a new
9267 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
9268 to let us transition smoothly, else tomorrow there would be no
9271 o Privacy/anonymity fixes (bridge enumeration):
9272 - Bridge relays now do their directory fetches inside Tor TLS
9273 connections, like all the other clients do, rather than connecting
9274 directly to the DirPort like public relays do. Removes another
9275 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
9276 - Bridges relays now build circuits for themselves in a more similar
9277 way to how clients build them. Removes another avenue for
9278 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
9279 when bridges were introduced.
9280 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
9281 that they initiated. Relays could distinguish incoming bridge
9282 connections from client connections, creating another avenue for
9283 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
9284 Found by "frosty_un".
9287 - Fix a crash bug when changing node restrictions while a DNS lookup
9288 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
9290 - Don't launch a useless circuit after failing to use one of a
9291 hidden service's introduction points. Previously, we would
9292 launch a new introduction circuit, but not set the hidden service
9293 which that circuit was intended to connect to, so it would never
9294 actually be used. A different piece of code would then create a
9295 new introduction circuit correctly. Bug reported by katmagic and
9296 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
9299 - Change an integer overflow check in the OpenBSD_Malloc code so
9300 that GCC is less likely to eliminate it as impossible. Patch
9301 from Mansour Moufid. Fixes bug 4059.
9302 - When a hidden service turns an extra service-side introduction
9303 circuit into a general-purpose circuit, free the rend_data and
9304 intro_key fields first, so we won't leak memory if the circuit
9305 is cannibalized for use as another service-side introduction
9306 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
9307 - Bridges now skip DNS self-tests, to act a little more stealthily.
9308 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
9309 bridges. Patch by "warms0x".
9310 - Fix internal bug-checking logic that was supposed to catch
9311 failures in digest generation so that it will fail more robustly
9312 if we ask for a nonexistent algorithm. Found by Coverity Scan.
9313 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
9314 - Report any failure in init_keys() calls launched because our
9315 IP address has changed. Spotted by Coverity Scan. Bugfix on
9316 0.1.1.4-alpha; fixes CID 484.
9318 o Minor bugfixes (log messages and documentation):
9319 - Remove a confusing dollar sign from the example fingerprint in the
9320 man page, and also make the example fingerprint a valid one. Fixes
9321 bug 4309; bugfix on 0.2.1.3-alpha.
9322 - The next version of Windows will be called Windows 8, and it has
9323 a major version of 6, minor version of 2. Correctly identify that
9324 version instead of calling it "Very recent version". Resolves
9325 ticket 4153; reported by funkstar.
9326 - Downgrade log messages about circuit timeout calibration from
9327 "notice" to "info": they don't require or suggest any human
9328 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
9329 bugfix on 0.2.2.14-alpha.
9332 - Turn on directory request statistics by default and include them in
9333 extra-info descriptors. Don't break if we have no GeoIP database.
9334 Backported from 0.2.3.1-alpha; implements ticket 3951.
9335 - Update to the October 4 2011 Maxmind GeoLite Country database.
9338 Changes in version 0.2.1.31 - 2011-10-26
9339 Tor 0.2.1.31 backports important security and privacy fixes for
9340 oldstable. This release is intended only for package maintainers and
9341 others who cannot use the 0.2.2 stable series. All others should be
9342 using Tor 0.2.2.x or newer.
9344 o Security fixes (also included in 0.2.2.x):
9345 - Replace all potentially sensitive memory comparison operations
9346 with versions whose runtime does not depend on the data being
9347 compared. This will help resist a class of attacks where an
9348 adversary can use variations in timing information to learn
9349 sensitive data. Fix for one case of bug 3122. (Safe memcmp
9350 implementation by Robert Ransom based partially on code by DJB.)
9351 - Fix an assert in parsing router descriptors containing IPv6
9352 addresses. This one took down the directory authorities when
9353 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
9355 o Privacy/anonymity fixes (also included in 0.2.2.x):
9356 - Clients and bridges no longer send TLS certificate chains on
9357 outgoing OR connections. Previously, each client or bridge would
9358 use the same cert chain for all outgoing OR connections until
9359 its IP address changes, which allowed any relay that the client
9360 or bridge contacted to determine which entry guards it is using.
9361 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
9362 - If a relay receives a CREATE_FAST cell on a TLS connection, it
9363 no longer considers that connection as suitable for satisfying a
9364 circuit EXTEND request. Now relays can protect clients from the
9365 CVE-2011-2768 issue even if the clients haven't upgraded yet.
9366 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
9367 that they initiated. Relays could distinguish incoming bridge
9368 connections from client connections, creating another avenue for
9369 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
9370 Found by "frosty_un".
9371 - When receiving a hidden service descriptor, check that it is for
9372 the hidden service we wanted. Previously, Tor would store any
9373 hidden service descriptors that a directory gave it, whether it
9374 wanted them or not. This wouldn't have let an attacker impersonate
9375 a hidden service, but it did let directories pre-seed a client
9376 with descriptors that it didn't want. Bugfix on 0.0.6.
9377 - Avoid linkability based on cached hidden service descriptors: forget
9378 all hidden service descriptors cached as a client when processing a
9379 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
9380 - Make the bridge directory authority refuse to answer directory
9381 requests for "all" descriptors. It used to include bridge
9382 descriptors in its answer, which was a major information leak.
9383 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
9384 - Don't attach new streams to old rendezvous circuits after SIGNAL
9385 NEWNYM. Previously, we would keep using an existing rendezvous
9386 circuit if it remained open (i.e. if it were kept open by a
9387 long-lived stream, or if a new stream were attached to it before
9388 Tor could notice that it was old and no longer in use). Bugfix on
9389 0.1.1.15-rc; fixes bug 3375.
9391 o Minor bugfixes (also included in 0.2.2.x):
9392 - When we restart our relay, we might get a successful connection
9393 from the outside before we've started our reachability tests,
9394 triggering a warning: "ORPort found reachable, but I have no
9395 routerinfo yet. Failing to inform controller of success." This
9396 bug was harmless unless Tor is running under a controller
9397 like Vidalia, in which case the controller would never get a
9398 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
9400 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9401 enabled. Fixes bug 1526.
9402 - Remove undocumented option "-F" from tor-resolve: it hasn't done
9403 anything since 0.2.1.16-rc.
9404 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
9405 None of the cases where we did this before were wrong, but by making
9406 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
9407 - Fix a rare crash bug that could occur when a client was configured
9408 with a large number of bridges. Fixes bug 2629; bugfix on
9409 0.2.1.2-alpha. Bugfix by trac user "shitlei".
9410 - Correct the warning displayed when a rendezvous descriptor exceeds
9411 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
9413 - Fix an uncommon assertion failure when running with DNSPort under
9414 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
9415 - When warning about missing zlib development packages during compile,
9416 give the correct package names. Bugfix on 0.2.0.1-alpha.
9417 - Require that introduction point keys and onion keys have public
9418 exponent 65537. Bugfix on 0.2.0.10-alpha.
9419 - Do not crash when our configuration file becomes unreadable, for
9420 example due to a permissions change, between when we start up
9421 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
9423 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
9425 - Always NUL-terminate the sun_path field of a sockaddr_un before
9426 passing it to the kernel. (Not a security issue: kernels are
9427 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9428 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9429 - Don't stack-allocate the list of supplementary GIDs when we're
9430 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
9431 could take up to 256K, which is way too much stack. Found by
9432 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
9434 o Minor bugfixes (only in 0.2.1.x):
9435 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
9436 rely on them. Bugfix on 0.2.1.30.
9437 - Use git revisions instead of svn revisions when generating our
9438 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9440 o Minor features (also included in 0.2.2.x):
9441 - Adjust the expiration time on our SSL session certificates to
9442 better match SSL certs seen in the wild. Resolves ticket 4014.
9443 - Allow nameservers with IPv6 address. Resolves bug 2574.
9444 - Update to the October 4 2011 Maxmind GeoLite Country database.
9447 Changes in version 0.2.3.5-alpha - 2011-09-28
9448 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
9449 bridge relays; fixes an assertion error that many users started hitting
9450 today; and adds the ability to refill token buckets more often than
9451 once per second, allowing significant performance improvements.
9454 - Bridge relays now do their directory fetches inside Tor TLS
9455 connections, like all the other clients do, rather than connecting
9456 directly to the DirPort like public relays do. Removes another
9457 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
9458 - Bridges relays now build circuits for themselves in a more similar
9459 way to how clients build them. Removes another avenue for
9460 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
9461 when bridges were introduced.
9464 - Fix an "Assertion md->held_by_node == 1 failed" error that could
9465 occur when the same microdescriptor was referenced by two node_t
9466 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
9468 o Major features (networking):
9469 - Add a new TokenBucketRefillInterval option to refill token buckets
9470 more frequently than once per second. This should improve network
9471 performance, alleviate queueing problems, and make traffic less
9472 bursty. Implements proposal 183; closes ticket 3630. Design by
9473 Florian Tschorsch and Björn Scheuermann; implementation by
9477 - Change an integer overflow check in the OpenBSD_Malloc code so
9478 that GCC is less likely to eliminate it as impossible. Patch
9479 from Mansour Moufid. Fixes bug 4059.
9481 o Minor bugfixes (usability):
9482 - Downgrade log messages about circuit timeout calibration from
9483 "notice" to "info": they don't require or suggest any human
9484 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
9485 bugfix on 0.2.2.14-alpha.
9487 o Minor features (diagnostics):
9488 - When the system call to create a listener socket fails, log the
9489 error message explaining why. This may help diagnose bug 4027.
9492 Changes in version 0.2.3.4-alpha - 2011-09-13
9493 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
9494 tweak to Tor's TLS handshake that makes relays and bridges that run
9495 this new version reachable from Iran again. It also fixes a few new
9496 bugs in 0.2.3.x, and teaches relays to recognize when they're not
9497 listed in the network consensus and republish.
9499 o Major bugfixes (also part of 0.2.2.33):
9500 - Avoid an assertion failure when reloading a configuration with
9501 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
9502 3923; bugfix on 0.2.2.25-alpha.
9504 o Minor features (security, also part of 0.2.2.33):
9505 - Check for replays of the public-key encrypted portion of an
9506 INTRODUCE1 cell, in addition to the current check for replays of
9507 the g^x value. This prevents a possible class of active attacks
9508 by an attacker who controls both an introduction point and a
9509 rendezvous point, and who uses the malleability of AES-CTR to
9510 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
9511 that these attacks are infeasible (requiring the attacker to send
9512 on the order of zettabytes of altered cells in a short interval),
9513 but we'd rather block them off in case there are any classes of
9514 this attack that we missed. Reported by Willem Pinckaers.
9516 o Minor features (also part of 0.2.2.33):
9517 - Adjust the expiration time on our SSL session certificates to
9518 better match SSL certs seen in the wild. Resolves ticket 4014.
9519 - Change the default required uptime for a relay to be accepted as
9520 a HSDir (hidden service directory) from 24 hours to 25 hours.
9521 Improves on 0.2.0.10-alpha; resolves ticket 2649.
9522 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
9523 authorities to abstain from voting on assignment of the HSDir
9524 consensus flag. Related to bug 2649.
9525 - Update to the September 6 2011 Maxmind GeoLite Country database.
9527 o Minor bugfixes (also part of 0.2.2.33):
9528 - Demote the 'replay detected' log message emitted when a hidden
9529 service receives the same Diffie-Hellman public key in two different
9530 INTRODUCE2 cells to info level. A normal Tor client can cause that
9531 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
9532 fixes part of bug 2442.
9533 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
9534 level. There is nothing that a hidden service's operator can do
9535 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
9537 - Clarify a log message specifying the characters permitted in
9538 HiddenServiceAuthorizeClient client names. Previously, the log
9539 message said that "[A-Za-z0-9+-_]" were permitted; that could have
9540 given the impression that every ASCII character between "+" and "_"
9541 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
9543 o Build fixes (also part of 0.2.2.33):
9544 - Clean up some code issues that prevented Tor from building on older
9545 BSDs. Fixes bug 3894; reported by "grarpamp".
9546 - Search for a platform-specific version of "ar" when cross-compiling.
9547 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
9550 - Fix a bug where the SocksPort option (for example) would get
9551 ignored and replaced by the default if a SocksListenAddress
9552 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
9556 - Relays now try regenerating and uploading their descriptor more
9557 frequently if they are not listed in the consensus, or if the
9558 version of their descriptor listed in the consensus is too
9559 old. This fix should prevent situations where a server declines
9560 to re-publish itself because it has done so too recently, even
9561 though the authorities decided not to list its recent-enough
9562 descriptor. Fix for bug 3327.
9565 - Relays now include a reason for regenerating their descriptors
9566 in an HTTP header when uploading to the authorities. This will
9567 make it easier to debug descriptor-upload issues in the future.
9568 - When starting as root and then changing our UID via the User
9569 control option, and we have a ControlSocket configured, make sure
9570 that the ControlSocket is owned by the same account that Tor will
9571 run under. Implements ticket 3421; fix by Jérémy Bobbio.
9574 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
9575 utility function used in the control-port code). This shouldn't
9576 ever happen unless Tor is completely out of memory, but if it did
9577 happen and Tor somehow recovered from it, Tor could have sent a log
9578 message to a control port in the middle of a reply to a controller
9579 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
9580 - Make 'FetchUselessDescriptors' cause all descriptor types and
9581 all consensus types (including microdescriptors) to get fetched.
9582 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
9585 - Make a new "entry connection" struct as an internal subtype of "edge
9586 connection", to simplify the code and make exit connections smaller.
9589 Changes in version 0.2.2.33 - 2011-09-13
9590 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
9591 TLS handshake that makes relays and bridges that run this new version
9592 reachable from Iran again.
9595 - Avoid an assertion failure when reloading a configuration with
9596 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
9597 3923; bugfix on 0.2.2.25-alpha.
9599 o Minor features (security):
9600 - Check for replays of the public-key encrypted portion of an
9601 INTRODUCE1 cell, in addition to the current check for replays of
9602 the g^x value. This prevents a possible class of active attacks
9603 by an attacker who controls both an introduction point and a
9604 rendezvous point, and who uses the malleability of AES-CTR to
9605 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
9606 that these attacks are infeasible (requiring the attacker to send
9607 on the order of zettabytes of altered cells in a short interval),
9608 but we'd rather block them off in case there are any classes of
9609 this attack that we missed. Reported by Willem Pinckaers.
9612 - Adjust the expiration time on our SSL session certificates to
9613 better match SSL certs seen in the wild. Resolves ticket 4014.
9614 - Change the default required uptime for a relay to be accepted as
9615 a HSDir (hidden service directory) from 24 hours to 25 hours.
9616 Improves on 0.2.0.10-alpha; resolves ticket 2649.
9617 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
9618 authorities to abstain from voting on assignment of the HSDir
9619 consensus flag. Related to bug 2649.
9620 - Update to the September 6 2011 Maxmind GeoLite Country database.
9622 o Minor bugfixes (documentation and log messages):
9623 - Correct the man page to explain that HashedControlPassword and
9624 CookieAuthentication can both be set, in which case either method
9625 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
9626 when we decided to allow these config options to both be set. Issue
9628 - Demote the 'replay detected' log message emitted when a hidden
9629 service receives the same Diffie-Hellman public key in two different
9630 INTRODUCE2 cells to info level. A normal Tor client can cause that
9631 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
9632 fixes part of bug 2442.
9633 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
9634 level. There is nothing that a hidden service's operator can do
9635 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
9637 - Clarify a log message specifying the characters permitted in
9638 HiddenServiceAuthorizeClient client names. Previously, the log
9639 message said that "[A-Za-z0-9+-_]" were permitted; that could have
9640 given the impression that every ASCII character between "+" and "_"
9641 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
9644 - Provide a substitute implementation of lround() for MSVC, which
9645 apparently lacks it. Patch from Gisle Vanem.
9646 - Clean up some code issues that prevented Tor from building on older
9647 BSDs. Fixes bug 3894; reported by "grarpamp".
9648 - Search for a platform-specific version of "ar" when cross-compiling.
9649 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
9652 Changes in version 0.2.3.3-alpha - 2011-09-01
9653 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
9654 security, and provides client-side support for the microdescriptor
9655 and optimistic data features introduced earlier in the 0.2.3.x
9656 series. It also includes numerous critical bugfixes in the (optional)
9657 bufferevent-based networking backend.
9659 o Major features (stream isolation):
9660 - You can now configure Tor so that streams from different
9661 applications are isolated on different circuits, to prevent an
9662 attacker who sees your streams as they leave an exit node from
9663 linking your sessions to one another. To do this, choose some way
9664 to distinguish the applications: have them connect to different
9665 SocksPorts, or have one of them use SOCKS4 while the other uses
9666 SOCKS5, or have them pass different authentication strings to the
9667 SOCKS proxy. Then, use the new SocksPort syntax to configure the
9668 degree of isolation you need. This implements Proposal 171.
9669 - There's a new syntax for specifying multiple client ports (such as
9670 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
9671 multiple *Port entries with full addr:port syntax on each.
9672 The old *ListenAddress format is still supported, but you can't
9673 mix it with the new *Port syntax.
9675 o Major features (other):
9676 - Enable microdescriptor fetching by default for clients. This allows
9677 clients to download a much smaller amount of directory information.
9678 To disable it (and go back to the old-style consensus and
9679 descriptors), set "UseMicrodescriptors 0" in your torrc file.
9680 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
9681 "PortForwarding" config option), now supports Windows.
9682 - When using an exit relay running 0.2.3.x, clients can now
9683 "optimistically" send data before the exit relay reports that
9684 the stream has opened. This saves a round trip when starting
9685 connections where the client speaks first (such as web browsing).
9686 This behavior is controlled by a consensus parameter (currently
9687 disabled). To turn it on or off manually, use the "OptimisticData"
9688 torrc option. Implements proposal 181; code by Ian Goldberg.
9690 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
9691 - When using IOCP on Windows, we need to enable Libevent windows
9693 - The IOCP backend now works even when the user has not specified
9694 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
9695 Fixes part of bug 3752.
9696 - Correctly record the bytes we've read and written when using
9697 bufferevents, so that we can include them in our bandwidth history
9698 and advertised bandwidth. Fixes bug 3803.
9699 - Apply rate-limiting only at the bottom of a chain of filtering
9700 bufferevents. This prevents us from filling up internal read
9701 buffers and violating rate-limits when filtering bufferevents
9702 are enabled. Fixes part of bug 3804.
9703 - Add high-watermarks to the output buffers for filtered
9704 bufferevents. This prevents us from filling up internal write
9705 buffers and wasting CPU cycles when filtering bufferevents are
9706 enabled. Fixes part of bug 3804.
9707 - Correctly notice when data has been written from a bufferevent
9708 without flushing it completely. Fixes bug 3805.
9709 - Fix a bug where server-side tunneled bufferevent-based directory
9710 streams would get closed prematurely. Fixes bug 3814.
9711 - Fix a use-after-free error with per-connection rate-limiting
9712 buckets. Fixes bug 3888.
9714 o Major bugfixes (also part of 0.2.2.31-rc):
9715 - If we're configured to write our ControlPorts to disk, only write
9716 them after switching UID and creating the data directory. This way,
9717 we don't fail when starting up with a nonexistent DataDirectory
9718 and a ControlPortWriteToFile setting based on that directory. Fixes
9719 bug 3747; bugfix on Tor 0.2.2.26-beta.
9722 - Added a new CONF_CHANGED event so that controllers can be notified
9723 of any configuration changes made by other controllers, or by the
9724 user. Implements ticket 1692.
9725 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
9726 leak when using bufferevents, and lets Libevent worry about how to
9727 best copy data out of a buffer.
9728 - Replace files in stats/ rather than appending to them. Now that we
9729 include statistics in extra-info descriptors, it makes no sense to
9730 keep old statistics forever. Implements ticket 2930.
9732 o Minor features (build compatibility):
9733 - Limited, experimental support for building with nmake and MSVC.
9734 - Provide a substitute implementation of lround() for MSVC, which
9735 apparently lacks it. Patch from Gisle Vanem.
9737 o Minor features (also part of 0.2.2.31-rc):
9738 - Update to the August 2 2011 Maxmind GeoLite Country database.
9740 o Minor bugfixes (on 0.2.3.x-alpha):
9741 - Fix a spurious warning when parsing SOCKS requests with
9742 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
9743 - Get rid of a harmless warning that could happen on relays running
9744 with bufferevents. The warning was caused by someone doing an http
9745 request to a relay's orport. Also don't warn for a few related
9746 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
9748 o Minor bugfixes (on 2.2.x and earlier):
9749 - Correct the man page to explain that HashedControlPassword and
9750 CookieAuthentication can both be set, in which case either method
9751 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
9752 when we decided to allow these config options to both be set. Issue
9754 - The "--quiet" and "--hush" options now apply not only to Tor's
9755 behavior before logs are configured, but also to Tor's behavior in
9756 the absense of configured logs. Fixes bug 3550; bugfix on
9759 o Minor bugfixes (also part of 0.2.2.31-rc):
9760 - Write several files in text mode, on OSes that distinguish text
9761 mode from binary mode (namely, Windows). These files are:
9762 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
9763 that collect those statistics; 'client_keys' and 'hostname' for
9764 hidden services that use authentication; and (in the tor-gencert
9765 utility) newly generated identity and signing keys. Previously,
9766 we wouldn't specify text mode or binary mode, leading to an
9767 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
9768 the DirRecordUsageByCountry option which would have triggered
9769 the assertion failure was added), although this assertion failure
9770 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
9771 - Selectively disable deprecation warnings on OS X because Lion
9772 started deprecating the shipped copy of openssl. Fixes bug 3643.
9773 - Remove an extra pair of quotation marks around the error
9774 message in control-port STATUS_GENERAL BUG events. Bugfix on
9775 0.1.2.6-alpha; fixes bug 3732.
9776 - When unable to format an address as a string, report its value
9777 as "???" rather than reusing the last formatted address. Bugfix
9780 o Code simplifications and refactoring:
9781 - Rewrite the listener-selection logic so that parsing which ports
9782 we want to listen on is now separate from binding to the ports
9786 - Building Tor with bufferevent support now requires Libevent
9787 2.0.13-stable or later. Previous versions of Libevent had bugs in
9788 SSL-related bufferevents and related issues that would make Tor
9789 work badly with bufferevents. Requiring 2.0.13-stable also allows
9790 Tor with bufferevents to take advantage of Libevent APIs
9791 introduced after 2.0.8-rc.
9794 Changes in version 0.2.2.32 - 2011-08-27
9795 The Tor 0.2.2 release series is dedicated to the memory of Andreas
9796 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
9797 a founder of the PETS community, a leader in our field, a mentor,
9798 and a friend. He left us with these words: "I had the possibility
9799 to contribute to this world that is not as it should be. I hope I
9800 could help in some areas to make the world a better place, and that
9801 I could also encourage other people to be engaged in improving the
9802 world. Please, stay engaged. This world needs you, your love, your
9803 initiative -- now I cannot be part of that anymore."
9805 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
9806 ready. More than two years in the making, this release features improved
9807 client performance and hidden service reliability, better compatibility
9808 for Android, correct behavior for bridges that listen on more than
9809 one address, more extensible and flexible directory object handling,
9810 better reporting of network statistics, improved code security, and
9811 many many other features and bugfixes.
9814 Changes in version 0.2.2.31-rc - 2011-08-17
9815 Tor 0.2.2.31-rc is the second and hopefully final release candidate
9816 for the Tor 0.2.2.x series.
9819 - Remove an extra pair of quotation marks around the error
9820 message in control-port STATUS_GENERAL BUG events. Bugfix on
9821 0.1.2.6-alpha; fixes bug 3732.
9822 - If we're configured to write our ControlPorts to disk, only write
9823 them after switching UID and creating the data directory. This way,
9824 we don't fail when starting up with a nonexistent DataDirectory
9825 and a ControlPortWriteToFile setting based on that directory. Fixes
9826 bug 3747; bugfix on Tor 0.2.2.26-beta.
9829 - Update to the August 2 2011 Maxmind GeoLite Country database.
9832 - Allow GETINFO fingerprint to return a fingerprint even when
9833 we have not yet built a router descriptor. Fixes bug 3577;
9834 bugfix on 0.2.0.1-alpha.
9835 - Write several files in text mode, on OSes that distinguish text
9836 mode from binary mode (namely, Windows). These files are:
9837 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
9838 that collect those statistics; 'client_keys' and 'hostname' for
9839 hidden services that use authentication; and (in the tor-gencert
9840 utility) newly generated identity and signing keys. Previously,
9841 we wouldn't specify text mode or binary mode, leading to an
9842 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
9843 the DirRecordUsageByCountry option which would have triggered
9844 the assertion failure was added), although this assertion failure
9845 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
9846 - Selectively disable deprecation warnings on OS X because Lion
9847 started deprecating the shipped copy of openssl. Fixes bug 3643.
9848 - When unable to format an address as a string, report its value
9849 as "???" rather than reusing the last formatted address. Bugfix
9853 Changes in version 0.2.3.2-alpha - 2011-07-18
9854 Tor 0.2.3.2-alpha introduces two new experimental features:
9855 microdescriptors and pluggable transports. It also continues cleaning
9856 up a variety of recently introduced features.
9859 - Clients can now use microdescriptors instead of regular descriptors
9860 to build circuits. Microdescriptors are authority-generated
9861 summaries of regular descriptors' contents, designed to change
9862 very rarely (see proposal 158 for details). This feature is
9863 designed to save bandwidth, especially for clients on slow internet
9864 connections. It's off by default for now, since nearly no caches
9865 support it, but it will be on-by-default for clients in a future
9866 version. You can use the UseMicrodescriptors option to turn it on.
9867 - Tor clients using bridges can now be configured to use a separate
9868 'transport' proxy for each bridge. This approach helps to resist
9869 censorship by allowing bridges to use protocol obfuscation
9870 plugins. It implements part of proposal 180. Implements ticket 2841.
9871 - While we're trying to bootstrap, record how many TLS connections
9872 fail in each state, and report which states saw the most failures
9873 in response to any bootstrap failures. This feature may speed up
9874 diagnosis of censorship events. Implements ticket 3116.
9876 o Major bugfixes (on 0.2.3.1-alpha):
9877 - When configuring a large set of nodes in EntryNodes (as with
9878 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
9879 random subset to be guards, and choose them in random
9880 order. Fixes bug 2798.
9881 - Tor could crash when remembering a consensus in a non-used consensus
9882 flavor without having a current consensus set. Fixes bug 3361.
9883 - Comparing an unknown address to a microdescriptor's shortened exit
9884 policy would always give a "rejected" result. Fixes bug 3599.
9885 - Using microdescriptors as a client no longer prevents Tor from
9886 uploading and downloading hidden service descriptors. Fixes
9890 - Allow nameservers with IPv6 address. Resolves bug 2574.
9891 - Accept attempts to include a password authenticator in the
9892 handshake, as supported by SOCKS5. This handles SOCKS clients that
9893 don't know how to omit a password when authenticating. Resolves
9895 - When configuring a large set of nodes in EntryNodes, and there are
9896 enough of them listed as Guard so that we don't need to consider
9897 the non-guard entries, prefer the ones listed with the Guard flag.
9898 - Check for and recover from inconsistency in the microdescriptor
9899 cache. This will make it harder for us to accidentally free a
9900 microdescriptor without removing it from the appropriate data
9901 structures. Fixes issue 3135; issue noted by "wanoskarnet".
9902 - Log SSL state transitions at log level DEBUG, log domain
9903 HANDSHAKE. This can be useful for debugging censorship events.
9904 Implements ticket 3264.
9905 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
9906 implements ticket 3439.
9908 o Minor bugfixes (on 0.2.3.1-alpha):
9909 - Do not free all general-purpose regular descriptors just
9910 because microdescriptor use is enabled. Fixes bug 3113.
9911 - Correctly link libevent_openssl when --enable-static-libevent
9912 is passed to configure. Fixes bug 3118.
9913 - Bridges should not complain during their heartbeat log messages that
9914 they are unlisted in the consensus: that's more or less the point
9915 of being a bridge. Fixes bug 3183.
9916 - Report a SIGNAL event to controllers when acting on a delayed
9917 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
9918 event to the controller if we acted on a SIGNAL NEWNYM command
9919 immediately, and otherwise not report a SIGNAL event for the
9920 command at all. Fixes bug 3349.
9921 - Fix a crash when handling the SIGNAL controller command or
9922 reporting ERR-level status events with bufferevents enabled. Found
9923 by Robert Ransom. Fixes bug 3367.
9924 - Always ship the tor-fw-helper manpage in our release tarballs.
9925 Fixes bug 3389. Reported by Stephen Walker.
9926 - Fix a class of double-mark-for-close bugs when bufferevents
9927 are enabled. Fixes bug 3403.
9928 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
9929 - Add SIGNAL to the list returned by the 'GETINFO events/names'
9930 control-port command. Fixes part of bug 3465.
9931 - Prevent using negative indices during unit test runs when read_all()
9932 fails. Spotted by coverity.
9933 - Fix a rare memory leak when checking the nodelist without it being
9934 present. Found by coverity.
9935 - Only try to download a microdescriptor-flavored consensus from
9936 a directory cache that provides them.
9938 o Minor bugfixes (on 0.2.2.x and earlier):
9939 - Assert that hidden-service-related operations are not performed
9940 using single-hop circuits. Previously, Tor would assert that
9941 client-side streams are not attached to single-hop circuits,
9942 but not that other sensitive operations on the client and service
9943 side are not performed using single-hop circuits. Fixes bug 3332;
9945 - Don't publish a new relay descriptor when we reload our onion key,
9946 unless the onion key has actually changed. Fixes bug 3263 and
9947 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
9948 - Allow GETINFO fingerprint to return a fingerprint even when
9949 we have not yet built a router descriptor. Fixes bug 3577;
9950 bugfix on 0.2.0.1-alpha.
9951 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
9952 on 0.2.2.4-alpha; fixes bug 3427.
9954 o Code simplification and refactoring:
9955 - Use tor_sscanf() in place of scanf() in more places through the
9956 code. This makes us a little more locale-independent, and
9957 should help shut up code-analysis tools that can't tell
9958 a safe sscanf string from a dangerous one.
9959 - Use tt_assert(), not tor_assert(), for checking for test failures.
9960 This makes the unit tests more able to go on in the event that
9962 - Split connection_about_to_close() into separate functions for each
9966 - On Windows, we now define the _WIN32_WINNT macros only if they
9967 are not already defined. This lets the person building Tor decide,
9968 if they want, to require a later version of Windows.
9971 Changes in version 0.2.2.30-rc - 2011-07-07
9972 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
9973 series. It fixes a few smaller bugs, but generally appears stable.
9974 Please test it and let us know whether it is!
9977 - Send a SUCCEEDED stream event to the controller when a reverse
9978 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
9979 discovered by katmagic.
9980 - Always NUL-terminate the sun_path field of a sockaddr_un before
9981 passing it to the kernel. (Not a security issue: kernels are
9982 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9983 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9984 - Don't stack-allocate the list of supplementary GIDs when we're
9985 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
9986 could take up to 256K, which is way too much stack. Found by
9987 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
9988 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
9989 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
9990 fixes part of bug 3465.
9991 - Fix a memory leak when receiving a descriptor for a hidden
9992 service we didn't ask for. Found by Coverity; CID #30. Bugfix
9996 - Update to the July 1 2011 Maxmind GeoLite Country database.
9999 Changes in version 0.2.2.29-beta - 2011-06-20
10000 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
10001 have bridge lines in their torrc but don't want to use them; gets
10002 us closer to having the control socket feature working on Debian;
10003 and fixes a variety of smaller bugs.
10006 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
10007 When we changed the default behavior to "use bridges if any
10008 are listed in the torrc", we surprised users who had bridges
10009 in their torrc files but who didn't actually want to use them.
10010 Partial resolution for bug 3354.
10013 - Don't attach new streams to old rendezvous circuits after SIGNAL
10014 NEWNYM. Previously, we would keep using an existing rendezvous
10015 circuit if it remained open (i.e. if it were kept open by a
10016 long-lived stream, or if a new stream were attached to it before
10017 Tor could notice that it was old and no longer in use). Bugfix on
10018 0.1.1.15-rc; fixes bug 3375.
10021 - Fix a bug when using ControlSocketsGroupWritable with User. The
10022 directory's group would be checked against the current group, not
10023 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
10024 bugfix on 0.2.2.26-beta.
10025 - Make connection_printf_to_buf()'s behavior sane. Its callers
10026 expect it to emit a CRLF iff the format string ends with CRLF;
10027 it actually emitted a CRLF iff (a) the format string ended with
10028 CRLF or (b) the resulting string was over 1023 characters long or
10029 (c) the format string did not end with CRLF *and* the resulting
10030 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
10031 fixes part of bug 3407.
10032 - Make send_control_event_impl()'s behavior sane. Its callers
10033 expect it to always emit a CRLF at the end of the string; it
10034 might have emitted extra control characters as well. Bugfix on
10035 0.1.1.9-alpha; fixes another part of bug 3407.
10036 - Make crypto_rand_int() check the value of its input correctly.
10037 Previously, it accepted values up to UINT_MAX, but could return a
10038 negative number if given a value above INT_MAX+1. Found by George
10039 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
10040 - Avoid a segfault when reading a malformed circuit build state
10041 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
10043 - When asked about a DNS record type we don't support via a
10044 client DNSPort, reply with NOTIMPL rather than an empty
10045 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
10046 - Fix a rare memory leak during stats writing. Found by coverity.
10049 - Update to the June 1 2011 Maxmind GeoLite Country database.
10051 o Code simplifications and refactoring:
10052 - Remove some dead code as indicated by coverity.
10053 - Remove a few dead assignments during router parsing. Found by
10055 - Add some forgotten return value checks during unit tests. Found
10057 - Don't use 1-bit wide signed bit fields. Found by coverity.
10060 Changes in version 0.2.2.28-beta - 2011-06-04
10061 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
10062 fixed a big bug in whether relays stay in the consensus consistently,
10063 we moved closer to handling bridges and hidden services correctly,
10064 and we started the process of better handling the dreaded "my Vidalia
10065 died, and now my Tor demands a password when I try to reconnect to it"
10069 - Don't decide to make a new descriptor when receiving a HUP signal.
10070 This bug has caused a lot of 0.2.2.x relays to disappear from the
10071 consensus periodically. Fixes the most common case of triggering
10072 bug 1810; bugfix on 0.2.2.7-alpha.
10073 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
10074 - Don't try to build descriptors if "ORPort auto" is set and we
10075 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
10077 - Resolve a crash that occurred when setting BridgeRelay to 1 with
10078 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
10079 - Apply circuit timeouts to opened hidden-service-related circuits
10080 based on the correct start time. Previously, we would apply the
10081 circuit build timeout based on time since the circuit's creation;
10082 it was supposed to be applied based on time since the circuit
10083 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
10084 - Use the same circuit timeout for client-side introduction
10085 circuits as for other four-hop circuits, rather than the timeout
10086 for single-hop directory-fetch circuits; the shorter timeout may
10087 have been appropriate with the static circuit build timeout in
10088 0.2.1.x and earlier, but caused many hidden service access attempts
10089 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
10090 on 0.2.2.2-alpha; fixes another part of bug 1297.
10091 - In ticket 2511 we fixed a case where you could use an unconfigured
10092 bridge if you had configured it as a bridge the last time you ran
10093 Tor. Now fix another edge case: if you had configured it as a bridge
10094 but then switched to a different bridge via the controller, you
10095 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
10099 - Add an __OwningControllerProcess configuration option and a
10100 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
10101 that when it exits, Tor will shut down. Implements feature 3049.
10102 - If "UseBridges 1" is set and no bridges are configured, Tor will
10103 now refuse to build any circuits until some bridges are set.
10104 If "UseBridges auto" is set, Tor will use bridges if they are
10105 configured and we are not running as a server, but otherwise will
10106 make circuits as usual. The new default is "auto". Patch by anonym,
10107 so the Tails LiveCD can stop automatically revealing you as a Tor
10111 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
10112 - Remove a trailing asterisk from "exit-policy/default" in the
10113 output of the control port command "GETINFO info/names". Bugfix
10115 - Use a wide type to hold sockets when built for 64-bit Windows builds.
10117 - Warn when the user configures two HiddenServiceDir lines that point
10118 to the same directory. Bugfix on 0.0.6 (the version introducing
10119 HiddenServiceDir); fixes bug 3289.
10120 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
10121 part of bug 2748; bugfix on 0.2.0.10-alpha.
10122 - Log malformed requests for rendezvous descriptors as protocol
10123 warnings, not warnings. Also, use a more informative log message
10124 in case someone sees it at log level warning without prior
10125 info-level messages. Fixes the other part of bug 2748; bugfix
10127 - Clear the table recording the time of the last request for each
10128 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
10129 Previously, we would clear our HS descriptor cache on SIGNAL
10130 NEWNYM, but if we had previously retrieved a descriptor (or tried
10131 to) from every directory responsible for it, we would refuse to
10132 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
10134 - Fix a log message that said "bits" while displaying a value in
10135 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
10137 - When checking for 1024-bit keys, check for 1024 bits, not 128
10138 bytes. This allows Tor to correctly discard keys of length 1017
10139 through 1023. Bugfix on 0.0.9pre5.
10142 - Relays now log the reason for publishing a new relay descriptor,
10143 so we have a better chance of hunting down instances of bug 1810.
10144 Resolves ticket 3252.
10145 - Revise most log messages that refer to nodes by nickname to
10146 instead use the "$key=nickname at address" format. This should be
10147 more useful, especially since nicknames are less and less likely
10148 to be unique. Resolves ticket 3045.
10149 - Log (at info level) when purging pieces of hidden-service-client
10150 state because of SIGNAL NEWNYM.
10153 - Remove undocumented option "-F" from tor-resolve: it hasn't done
10154 anything since 0.2.1.16-rc.
10157 Changes in version 0.2.2.27-beta - 2011-05-18
10158 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
10159 release, and also adds a few more general bugfixes.
10162 - Fix a crash bug when changing bridges in a running Tor process.
10163 Fixes bug 3213; bugfix on 0.2.2.26-beta.
10164 - When the controller configures a new bridge, don't wait 10 to 60
10165 seconds before trying to fetch its descriptor. Bugfix on
10166 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
10169 - Require that onion keys have exponent 65537 in microdescriptors too.
10170 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
10171 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
10172 Changed the limit to 512 characters by removing base64 newlines.
10173 Fixes bug 2752. Fix by Michael Yakubovich.
10174 - When a client starts or stops using bridges, never use a circuit
10175 that was built before the configuration change. This behavior could
10176 put at risk a user who uses bridges to ensure that her traffic
10177 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
10181 Changes in version 0.2.2.26-beta - 2011-05-17
10182 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
10183 also introduces a new "socksport auto" approach that should make it
10184 easier to run multiple Tors on the same system, and does a lot of
10185 cleanup to get us closer to a release candidate.
10187 o Security/privacy fixes:
10188 - Replace all potentially sensitive memory comparison operations
10189 with versions whose runtime does not depend on the data being
10190 compared. This will help resist a class of attacks where an
10191 adversary can use variations in timing information to learn
10192 sensitive data. Fix for one case of bug 3122. (Safe memcmp
10193 implementation by Robert Ransom based partially on code by DJB.)
10194 - When receiving a hidden service descriptor, check that it is for
10195 the hidden service we wanted. Previously, Tor would store any
10196 hidden service descriptors that a directory gave it, whether it
10197 wanted them or not. This wouldn't have let an attacker impersonate
10198 a hidden service, but it did let directories pre-seed a client
10199 with descriptors that it didn't want. Bugfix on 0.0.6.
10200 - On SIGHUP, do not clear out all TrackHostExits mappings, client
10201 DNS cache entries, and virtual address mappings: that's what
10202 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
10205 - The options SocksPort, ControlPort, and so on now all accept a
10206 value "auto" that opens a socket on an OS-selected port. A
10207 new ControlPortWriteToFile option tells Tor to write its
10208 actual control port or ports to a chosen file. If the option
10209 ControlPortFileGroupReadable is set, the file is created as
10210 group-readable. Now users can run two Tor clients on the same
10211 system without needing to manually mess with parameters. Resolves
10212 part of ticket 3076.
10213 - Set SO_REUSEADDR on all sockets, not just listeners. This should
10214 help busy exit nodes avoid running out of useable ports just
10215 because all the ports have been used in the near past. Resolves
10219 - New "GETINFO net/listeners/(type)" controller command to return
10220 a list of addresses and ports that are bound for listeners for a
10221 given connection type. This is useful when the user has configured
10222 "SocksPort auto" and the controller needs to know which port got
10223 chosen. Resolves another part of ticket 3076.
10224 - Add a new ControlSocketsGroupWritable configuration option: when
10225 it is turned on, ControlSockets are group-writeable by the default
10226 group of the current user. Patch by Jérémy Bobbio; implements
10228 - Tor now refuses to create a ControlSocket in a directory that is
10229 world-readable (or group-readable if ControlSocketsGroupWritable
10230 is 0). This is necessary because some operating systems do not
10231 enforce permissions on an AF_UNIX sockets. Permissions on the
10232 directory holding the socket, however, seems to work everywhere.
10233 - Rate-limit a warning about failures to download v2 networkstatus
10234 documents. Resolves part of bug 1352.
10235 - Backport code from 0.2.3.x that allows directory authorities to
10236 clean their microdescriptor caches. Needed to resolve bug 2230.
10237 - When an HTTPS proxy reports "403 Forbidden", we now explain
10238 what it means rather than calling it an unexpected status code.
10239 Closes bug 2503. Patch from Michael Yakubovich.
10240 - Update to the May 1 2011 Maxmind GeoLite Country database.
10243 - Authorities now clean their microdesc cache periodically and when
10244 reading from disk initially, not only when adding new descriptors.
10245 This prevents a bug where we could lose microdescriptors. Bugfix
10246 on 0.2.2.6-alpha. Fixes bug 2230.
10247 - Do not crash when our configuration file becomes unreadable, for
10248 example due to a permissions change, between when we start up
10249 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
10251 - Avoid a bug that would keep us from replacing a microdescriptor
10252 cache on Windows. (We would try to replace the file while still
10253 holding it open. That's fine on Unix, but Windows doesn't let us
10254 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
10255 - Add missing explanations for the authority-related torrc options
10256 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
10257 man page. Resolves issue 2379.
10258 - As an authority, do not upload our own vote or signature set to
10259 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
10260 it would get flagged as a duplicate. Resolves bug 3026.
10261 - Accept hidden service descriptors if we think we might be a hidden
10262 service directory, regardless of what our consensus says. This
10263 helps robustness, since clients and hidden services can sometimes
10264 have a more up-to-date view of the network consensus than we do,
10265 and if they think that the directory authorities list us a HSDir,
10266 we might actually be one. Related to bug 2732; bugfix on
10268 - When a controller changes TrackHostExits, remove mappings for
10269 hosts that should no longer have their exits tracked. Bugfix on
10271 - When a controller changes VirtualAddrNetwork, remove any mappings
10272 for hosts that were automapped to the old network. Bugfix on
10274 - When a controller changes one of the AutomapHosts* options, remove
10275 any mappings for hosts that should no longer be automapped. Bugfix
10277 - Do not reset the bridge descriptor download status every time we
10278 re-parse our configuration or get a configuration change. Fixes
10279 bug 3019; bugfix on 0.2.0.3-alpha.
10281 o Minor bugfixes (code cleanup):
10282 - When loading the microdesc journal, remember its current size.
10283 In 0.2.2, this helps prevent the microdesc journal from growing
10284 without limit on authorities (who are the only ones to use it in
10285 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
10286 Fix posted by "cypherpunks."
10287 - The microdesc journal is supposed to get rebuilt only if it is
10288 at least _half_ the length of the store, not _twice_ the length
10289 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
10290 - Fix a potential null-pointer dereference while computing a
10291 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
10293 - Avoid a possible null-pointer dereference when rebuilding the mdesc
10294 cache without actually having any descriptors to cache. Bugfix on
10295 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
10296 - If we fail to compute the identity digest of a v3 legacy keypair,
10297 warn, and don't use a buffer-full of junk instead. Bugfix on
10298 0.2.1.1-alpha; fixes bug 3106.
10299 - Resolve an untriggerable issue in smartlist_string_num_isin(),
10300 where if the function had ever in the future been used to check
10301 for the presence of a too-large number, it would have given an
10302 incorrect result. (Fortunately, we only used it for 16-bit
10303 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
10304 - Require that introduction point keys and onion handshake keys
10305 have a public exponent of 65537. Starts to fix bug 3207; bugfix
10308 o Removed features:
10309 - Caches no longer download and serve v2 networkstatus documents
10310 unless FetchV2Networkstatus flag is set: these documents haven't
10311 haven't been used by clients or relays since 0.2.0.x. Resolves
10315 Changes in version 0.2.3.1-alpha - 2011-05-05
10316 Tor 0.2.3.1-alpha adds some new experimental features, including support
10317 for an improved network IO backend, IOCP networking on Windows,
10318 microdescriptor caching, "fast-start" support for streams, and automatic
10319 home router configuration. There are also numerous internal improvements
10320 to try to make the code easier for developers to work with.
10322 This is the first alpha release in a new series, so expect there to be
10323 bugs. Users who would rather test out a more stable branch should
10324 stay with 0.2.2.x for now.
10327 - Tor can now optionally build with the "bufferevents" buffered IO
10328 backend provided by Libevent 2. To use this feature, make sure you
10329 have the latest possible version of Libevent, and pass the
10330 --enable-bufferevents flag to configure when building Tor from
10331 source. This feature will make our networking code more flexible,
10332 let us stack layers on each other, and let us use more efficient
10333 zero-copy transports where available.
10334 - As an experimental feature, Tor can use IOCP for networking on Windows.
10335 Once this code is tuned and optimized, it promises much better
10336 performance than the select-based backend we've used in the past. To
10337 try this feature, you must build Tor with Libevent 2, configure Tor
10338 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
10339 your torrc. There are known bugs here: only try this if you can help
10340 debug it as it breaks.
10341 - The EntryNodes option can now include country codes like {de} or IP
10342 addresses or network masks. Previously we had disallowed these options
10343 because we didn't have an efficient way to keep the list up to
10344 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
10345 - Exit nodes now accept and queue data on not-yet-connected streams.
10346 Previously, the client wasn't allowed to send data until the stream was
10347 connected, which slowed down all connections. This change will enable
10348 clients to perform a "fast-start" on streams and send data without
10349 having to wait for a confirmation that the stream has opened. (Patch
10350 from Ian Goldberg; implements the server side of Proposal 174.)
10351 - Tor now has initial support for automatic port mapping on the many
10352 home routers that support NAT-PMP or UPnP. (Not yet supported on
10353 Windows). To build the support code, you'll need to have libnatpnp
10354 library and/or the libminiupnpc library, and you'll need to enable the
10355 feature specifically by passing "--enable-upnp" and/or
10356 "--enable-natpnp" to configure. To turn it on, use the new
10357 PortForwarding option.
10358 - Caches now download, cache, and serve multiple "flavors" of the
10359 consensus, including a flavor that describes microdescriptors.
10360 - Caches now download, cache, and serve microdescriptors -- small
10361 summaries of router descriptors that are authenticated by all of the
10362 directory authorities. Once enough caches are running this code,
10363 clients will be able to save significant amounts of directory bandwidth
10364 by downloading microdescriptors instead of router descriptors.
10367 - Make logging resolution configurable with a new LogTimeGranularity
10368 option, and change the default from 1 millisecond to 1 second.
10369 Implements enhancement 1668.
10370 - We log which torrc file we're using on startup. Implements ticket
10372 - Ordinarily, Tor does not count traffic from private addresses (like
10373 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
10374 There is now a new option, CountPrivateBandwidth, to disable this
10375 behavior. Patch from Daniel Cagara.
10376 - New --enable-static-tor configure option for building Tor as
10377 statically as possible. Idea, general hackery and thoughts from
10378 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
10380 - If you set the NumCPUs option to 0, Tor will now try to detect how
10381 many CPUs you have. This is the new default behavior.
10382 - Turn on directory request statistics by default and include them in
10383 extra-info descriptors. Don't break if we have no GeoIP database.
10384 - Relays that set "ConnDirectionStatistics 1" write statistics on the
10385 bidirectional use of connections to disk every 24 hours.
10386 - Add a GeoIP file digest to the extra-info descriptor. Implements
10388 - The NodeFamily option -- which let you declare that you want to
10389 consider nodes to be part of a family whether they list themselves
10390 that way or not -- now allows IP address ranges and country codes.
10391 - Add a new 'Heartbeat' log message type to periodically log a message
10392 describing Tor's status at level Notice. This feature is meant for
10393 operators who log at notice, and want to make sure that their Tor
10394 server is still working. Implementation by George Kadianakis.
10396 o Minor bugfixes (on 0.2.2.25-alpha):
10397 - When loading the microdesc journal, remember its current size.
10398 In 0.2.2, this helps prevent the microdesc journal from growing
10399 without limit on authorities (who are the only ones to use it in
10400 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
10401 Fix posted by "cypherpunks."
10402 - The microdesc journal is supposed to get rebuilt only if it is
10403 at least _half_ the length of the store, not _twice_ the length
10404 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
10405 - If as an authority we fail to compute the identity digest of a v3
10406 legacy keypair, warn, and don't use a buffer-full of junk instead.
10407 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
10408 - Authorities now clean their microdesc cache periodically and when
10409 reading from disk initially, not only when adding new descriptors.
10410 This prevents a bug where we could lose microdescriptors. Bugfix
10413 o Minor features (controller):
10414 - Add a new SIGNAL event to the controller interface so that
10415 controllers can be notified when Tor handles a signal. Resolves
10416 issue 1955. Patch by John Brooks.
10417 - Add a new GETINFO option to get total bytes read and written. Patch
10418 from pipe, revised by atagar. Resolves ticket 2345.
10419 - Implement some GETINFO controller fields to provide information about
10420 the Tor process's pid, euid, username, and resource limits.
10423 - Our build system requires automake 1.6 or later to create the
10424 Makefile.in files. Previously, you could have used 1.4.
10425 This only affects developers and people building Tor from git;
10426 people who build Tor from the source distribution without changing
10427 the Makefile.am files should be fine.
10428 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
10429 so on. This is more robust against some of the failure modes
10430 associated with running the autotools pieces on their own.
10432 o Minor packaging issues:
10433 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
10434 already created. Patch from Andreas Stieger. Fixes bug 2573.
10436 o Code simplifications and refactoring:
10437 - A major revision to our internal node-selecting and listing logic.
10438 Tor already had at least two major ways to look at the question of
10439 "which Tor servers do we know about": a list of router descriptors,
10440 and a list of entries in the current consensus. With
10441 microdescriptors, we're adding a third. Having so many systems
10442 without an abstraction layer over them was hurting the codebase.
10443 Now, we have a new "node_t" abstraction that presents a consistent
10444 interface to a client's view of a Tor node, and holds (nearly) all
10445 of the mutable state formerly in routerinfo_t and routerstatus_t.
10446 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
10447 no longer link against Libevent: they never used it, but
10448 our library structure used to force them to link it.
10450 o Removed features:
10451 - Remove some old code to work around even older versions of Tor that
10452 used forked processes to handle DNS requests. Such versions of Tor
10453 are no longer in use as servers.
10455 o Documentation fixes:
10456 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
10457 - Add missing documentation for the authority-related torrc options
10458 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
10462 Changes in version 0.2.2.25-alpha - 2011-04-29
10463 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
10464 robust, routers no longer overreport their bandwidth, Win7 should crash
10465 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
10466 now prevents hidden service-related activity from being linkable. It
10467 provides more information to Vidalia so you can see if your bridge is
10468 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
10469 StrictNodes configuration options to make them more reliable, more
10470 understandable, and more regularly applied. If you use those options,
10471 please see the revised documentation for them in the manual page.
10474 - Relays were publishing grossly inflated bandwidth values because
10475 they were writing their state files wrong--now they write the
10476 correct value. Also, resume reading bandwidth history from the
10477 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
10478 - Improve hidden service robustness: When we find that we have
10479 extended a hidden service's introduction circuit to a relay not
10480 listed as an introduction point in the HS descriptor we currently
10481 have, retry with an introduction point from the current
10482 descriptor. Previously we would just give up. Fixes bugs 1024 and
10483 1930; bugfix on 0.2.0.10-alpha.
10484 - Clients now stop trying to use an exit node associated with a given
10485 destination by TrackHostExits if they fail to reach that exit node.
10486 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
10487 - Fix crash bug on platforms where gmtime and localtime can return
10488 NULL. Windows 7 users were running into this one. Fixes part of bug
10489 2077. Bugfix on all versions of Tor. Found by boboper.
10491 o Security and stability fixes:
10492 - Don't double-free a parsable, but invalid, microdescriptor, even if
10493 it is followed in the blob we're parsing by an unparsable
10494 microdescriptor. Fixes an issue reported in a comment on bug 2954.
10495 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
10496 - If the Nickname configuration option isn't given, Tor would pick a
10497 nickname based on the local hostname as the nickname for a relay.
10498 Because nicknames are not very important in today's Tor and the
10499 "Unnamed" nickname has been implemented, this is now problematic
10500 behavior: It leaks information about the hostname without being
10501 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
10502 introduced the Unnamed nickname. Reported by tagnaq.
10503 - Fix an uncommon assertion failure when running with DNSPort under
10504 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
10505 - Avoid linkability based on cached hidden service descriptors: forget
10506 all hidden service descriptors cached as a client when processing a
10507 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
10510 - Export GeoIP information on bridge usage to controllers even if we
10511 have not yet been running for 24 hours. Now Vidalia bridge operators
10512 can get more accurate and immediate feedback about their
10513 contributions to the network.
10515 o Major features and bugfixes (node selection):
10516 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
10517 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
10518 options. Previously, we had been ambiguous in describing what
10519 counted as an "exit" node, and what operations exactly "StrictNodes
10520 0" would permit. This created confusion when people saw nodes built
10521 through unexpected circuits, and made it hard to tell real bugs from
10522 surprises. Now the intended behavior is:
10523 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
10524 a node that delivers user traffic outside the Tor network.
10525 . "Entry", in the context of EntryNodes, means a node used as the
10526 first hop of a multihop circuit. It doesn't include direct
10527 connections to directory servers.
10528 . "ExcludeNodes" applies to all nodes.
10529 . "StrictNodes" changes the behavior of ExcludeNodes only. When
10530 StrictNodes is set, Tor should avoid all nodes listed in
10531 ExcludeNodes, even when it will make user requests fail. When
10532 StrictNodes is *not* set, then Tor should follow ExcludeNodes
10533 whenever it can, except when it must use an excluded node to
10534 perform self-tests, connect to a hidden service, provide a
10535 hidden service, fulfill a .exit request, upload directory
10536 information, or fetch directory information.
10537 Collectively, the changes to implement the behavior fix bug 1090.
10538 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
10539 a node is listed in both, it's treated as excluded.
10540 - ExcludeNodes now applies to directory nodes -- as a preference if
10541 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
10542 Don't exclude all the directory authorities and set StrictNodes to 1
10543 unless you really want your Tor to break.
10544 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
10545 - ExcludeExitNodes now overrides .exit requests.
10546 - We don't use bridges listed in ExcludeNodes.
10547 - When StrictNodes is 1:
10548 . We now apply ExcludeNodes to hidden service introduction points
10549 and to rendezvous points selected by hidden service users. This
10550 can make your hidden service less reliable: use it with caution!
10551 . If we have used ExcludeNodes on ourself, do not try relay
10552 reachability self-tests.
10553 . If we have excluded all the directory authorities, we will not
10554 even try to upload our descriptor if we're a relay.
10555 . Do not honor .exit requests to an excluded node.
10556 - Remove a misfeature that caused us to ignore the Fast/Stable flags
10557 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
10558 - When the set of permitted nodes changes, we now remove any mappings
10559 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
10561 - We never cannibalize a circuit that had excluded nodes on it, even
10562 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
10563 - Revert a change where we would be laxer about attaching streams to
10564 circuits than when building the circuits. This was meant to prevent
10565 a set of bugs where streams were never attachable, but our improved
10566 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
10567 - Keep track of how many times we launch a new circuit to handle a
10568 given stream. Too many launches could indicate an inconsistency
10569 between our "launch a circuit to handle this stream" logic and our
10570 "attach this stream to one of the available circuits" logic.
10571 - Improve log messages related to excluded nodes.
10574 - Fix a spurious warning when moving from a short month to a long
10575 month on relays with month-based BandwidthAccounting. Bugfix on
10576 0.2.2.17-alpha; fixes bug 3020.
10577 - When a client finds that an origin circuit has run out of 16-bit
10578 stream IDs, we now mark it as unusable for new streams. Previously,
10579 we would try to close the entire circuit. Bugfix on 0.0.6.
10580 - Add a forgotten cast that caused a compile warning on OS X 10.6.
10581 Bugfix on 0.2.2.24-alpha.
10582 - Be more careful about reporting the correct error from a failed
10583 connect() system call. Under some circumstances, it was possible to
10584 look at an incorrect value for errno when sending the end reason.
10585 Bugfix on 0.1.0.1-rc.
10586 - Correctly handle an "impossible" overflow cases in connection byte
10587 counting, where we write or read more than 4GB on an edge connection
10588 in a single second. Bugfix on 0.1.2.8-beta.
10589 - Correct the warning displayed when a rendezvous descriptor exceeds
10590 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
10592 - Clients and hidden services now use HSDir-flagged relays for hidden
10593 service descriptor downloads and uploads even if the relays have no
10594 DirPort set and the client has disabled TunnelDirConns. This will
10595 eventually allow us to give the HSDir flag to relays with no
10596 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
10597 - Downgrade "no current certificates known for authority" message from
10598 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
10599 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
10600 2917. Bugfix on 0.1.1.1-alpha.
10601 - Only limit the lengths of single HS descriptors, even when multiple
10602 HS descriptors are published to an HSDir relay in a single POST
10603 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
10604 - Write the current time into the LastWritten line in our state file,
10605 rather than the time from the previous write attempt. Also, stop
10606 trying to use a time of -1 in our log statements. Fixes bug 3039;
10607 bugfix on 0.2.2.14-alpha.
10608 - Be more consistent in our treatment of file system paths. "~" should
10609 get expanded to the user's home directory in the Log config option.
10610 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
10611 feature for the -f and --DataDirectory options.
10614 - Make sure every relay writes a state file at least every 12 hours.
10615 Previously, a relay could go for weeks without writing its state
10616 file, and on a crash could lose its bandwidth history, capacity
10617 estimates, client country statistics, and so on. Addresses bug 3012.
10618 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
10619 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
10620 clients are already deprecated because of security bugs.
10621 - Don't allow v0 hidden service authorities to act as clients.
10622 Required by fix for bug 3000.
10623 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
10624 by fix for bug 3000.
10625 - Ensure that no empty [dirreq-](read|write)-history lines are added
10626 to an extrainfo document. Implements ticket 2497.
10628 o Code simplification and refactoring:
10629 - Remove workaround code to handle directory responses from servers
10630 that had bug 539 (they would send HTTP status 503 responses _and_
10631 send a body too). Since only server versions before
10632 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
10633 keep the workaround in place.
10634 - Remove the old 'fuzzy time' logic. It was supposed to be used for
10635 handling calculations where we have a known amount of clock skew and
10636 an allowed amount of unknown skew. But we only used it in three
10637 places, and we never adjusted the known/unknown skew values. This is
10638 still something we might want to do someday, but if we do, we'll
10639 want to do it differently.
10640 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
10641 None of the cases where we did this before were wrong, but by making
10642 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
10643 - Use GetTempDir to find the proper temporary directory location on
10644 Windows when generating temporary files for the unit tests. Patch by
10648 Changes in version 0.2.2.24-alpha - 2011-04-08
10649 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
10650 prevented Tor clients from effectively using "multihomed" bridges,
10651 that is, bridges that listen on multiple ports or IP addresses so users
10652 can continue to use some of their addresses even if others get blocked.
10655 - Fix a bug where bridge users who configure the non-canonical
10656 address of a bridge automatically switch to its canonical
10657 address. If a bridge listens at more than one address, it should be
10658 able to advertise those addresses independently and any non-blocked
10659 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
10661 - If you configured Tor to use bridge A, and then quit and
10662 configured Tor to use bridge B instead, it would happily continue
10663 to use bridge A if it's still reachable. While this behavior is
10664 a feature if your goal is connectivity, in some scenarios it's a
10665 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
10666 - Directory authorities now use data collected from their own
10667 uptime observations when choosing whether to assign the HSDir flag
10668 to relays, instead of trusting the uptime value the relay reports in
10669 its descriptor. This change helps prevent an attack where a small
10670 set of nodes with frequently-changing identity keys can blackhole
10671 a hidden service. (Only authorities need upgrade; others will be
10672 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
10675 - When we restart our relay, we might get a successful connection
10676 from the outside before we've started our reachability tests,
10677 triggering a warning: "ORPort found reachable, but I have no
10678 routerinfo yet. Failing to inform controller of success." This
10679 bug was harmless unless Tor is running under a controller
10680 like Vidalia, in which case the controller would never get a
10681 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
10683 - Make directory authorities more accurate at recording when
10684 relays that have failed several reachability tests became
10685 unreachable, so we can provide more accuracy at assigning Stable,
10686 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
10687 - Fix an issue that prevented static linking of libevent on
10688 some platforms (notably Linux). Fixes bug 2698; bugfix on
10689 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
10690 the --with-static-libevent configure option).
10691 - We now ask the other side of a stream (the client or the exit)
10692 for more data on that stream when the amount of queued data on
10693 that stream dips low enough. Previously, we wouldn't ask the
10694 other side for more data until either it sent us more data (which
10695 it wasn't supposed to do if it had exhausted its window!) or we
10696 had completely flushed all our queued data. This flow control fix
10697 should improve throughput. Fixes bug 2756; bugfix on the earliest
10698 released versions of Tor (svn commit r152).
10699 - Avoid a double-mark-for-free warning when failing to attach a
10700 transparent proxy connection. (We thought we had fixed this in
10701 0.2.2.23-alpha, but it turns out our fix was checking the wrong
10702 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
10703 bug) and 0.2.2.23-alpha (the incorrect fix).
10704 - When warning about missing zlib development packages during compile,
10705 give the correct package names. Bugfix on 0.2.0.1-alpha.
10708 - Directory authorities now log the source of a rejected POSTed v3
10709 networkstatus vote.
10710 - Make compilation with clang possible when using
10711 --enable-gcc-warnings by removing two warning options that clang
10712 hasn't implemented yet and by fixing a few warnings. Implements
10714 - When expiring circuits, use microsecond timers rather than
10715 one-second timers. This can avoid an unpleasant situation where a
10716 circuit is launched near the end of one second and expired right
10717 near the beginning of the next, and prevent fluctuations in circuit
10719 - Use computed circuit-build timeouts to decide when to launch
10720 parallel introduction circuits for hidden services. (Previously,
10721 we would retry after 15 seconds.)
10722 - Update to the April 1 2011 Maxmind GeoLite Country database.
10725 - Create the /var/run/tor directory on startup on OpenSUSE if it is
10726 not already created. Patch from Andreas Stieger. Fixes bug 2573.
10728 o Documentation changes:
10729 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
10730 - Resolve all doxygen warnings except those for missing documentation.
10732 - Add doxygen documentation for more functions, fields, and types.
10735 Changes in version 0.2.2.23-alpha - 2011-03-08
10736 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
10737 they restart they don't lose their bandwidth capacity estimate. This
10738 release also fixes a diverse set of user-facing bugs, ranging from
10739 relays overrunning their rate limiting to clients falsely warning about
10740 clock skew to bridge descriptor leaks by our bridge directory authority.
10743 - Stop sending a CLOCK_SKEW controller status event whenever
10744 we fetch directory information from a relay that has a wrong clock.
10745 Instead, only inform the controller when it's a trusted authority
10746 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
10747 the rest of bug 1074.
10748 - Fix an assert in parsing router descriptors containing IPv6
10749 addresses. This one took down the directory authorities when
10750 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
10751 - Make the bridge directory authority refuse to answer directory
10752 requests for "all" descriptors. It used to include bridge
10753 descriptors in its answer, which was a major information leak.
10754 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
10755 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
10756 Tor would ignore their RelayBandwidthBurst setting,
10757 potentially using more bandwidth than expected. Bugfix on
10758 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
10759 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
10760 hidserv" in her torrc. The 'hidserv' argument never controlled
10761 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
10764 - Relays now save observed peak bandwidth throughput rates to their
10765 state file (along with total usage, which was already saved)
10766 so that they can determine their correct estimated bandwidth on
10767 restart. Resolves bug 1863, where Tor relays would reset their
10768 estimated bandwidth to 0 after restarting.
10769 - Directory authorities now take changes in router IP address and
10770 ORPort into account when determining router stability. Previously,
10771 if a router changed its IP or ORPort, the authorities would not
10772 treat it as having any downtime for the purposes of stability
10773 calculation, whereas clients would experience downtime since the
10774 change could take a while to propagate to them. Resolves issue 1035.
10775 - Enable Address Space Layout Randomization (ASLR) and Data Execution
10776 Prevention (DEP) by default on Windows to make it harder for
10777 attackers to exploit vulnerabilities. Patch from John Brooks.
10779 o Minor bugfixes (on 0.2.1.x and earlier):
10780 - Fix a rare crash bug that could occur when a client was configured
10781 with a large number of bridges. Fixes bug 2629; bugfix on
10782 0.2.1.2-alpha. Bugfix by trac user "shitlei".
10783 - Avoid a double mark-for-free warning when failing to attach a
10784 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
10786 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
10787 found by "cypherpunks". This bug was introduced before the first
10788 Tor release, in svn commit r110.
10789 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
10790 don't mention them in the manpage. Fixes bug 2450; issue
10791 spotted by keb and G-Lo.
10792 - Fix a bug in bandwidth history state parsing that could have been
10793 triggered if a future version of Tor ever changed the timing
10794 granularity at which bandwidth history is measured. Bugfix on
10795 Tor 0.1.1.11-alpha.
10796 - When a relay decides that its DNS is too broken for it to serve
10797 as an exit server, it advertised itself as a non-exit, but
10798 continued to act as an exit. This could create accidental
10799 partitioning opportunities for users. Instead, if a relay is
10800 going to advertise reject *:* as its exit policy, it should
10801 really act with exit policy "reject *:*". Fixes bug 2366.
10802 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
10803 - In the special case where you configure a public exit relay as your
10804 bridge, Tor would be willing to use that exit relay as the last
10805 hop in your circuit as well. Now we fail that circuit instead.
10806 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
10807 - Fix a bug with our locking implementation on Windows that couldn't
10808 correctly detect when a file was already locked. Fixes bug 2504,
10809 bugfix on 0.2.1.6-alpha.
10810 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
10811 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
10813 - Set target port in get_interface_address6() correctly. Bugfix
10814 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
10815 - Directory authorities are now more robust to hops back in time
10816 when calculating router stability. Previously, if a run of uptime
10817 or downtime appeared to be negative, the calculation could give
10818 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
10820 - Fix an assert that got triggered when using the TestingTorNetwork
10821 configuration option and then issuing a GETINFO config-text control
10822 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
10824 o Minor bugfixes (on 0.2.2.x):
10825 - Clients should not weight BadExit nodes as Exits in their node
10826 selection. Similarly, directory authorities should not count BadExit
10827 bandwidth as Exit bandwidth when computing bandwidth-weights.
10828 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
10829 - Correctly clear our dir_read/dir_write history when there is an
10830 error parsing any bw history value from the state file. Bugfix on
10831 Tor 0.2.2.15-alpha.
10832 - Resolve a bug in verifying signatures of directory objects
10833 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
10834 Fixes bug 2409. Found by "piebeer".
10835 - Bridge authorities no longer crash on SIGHUP when they try to
10836 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
10840 - Log less aggressively about circuit timeout changes, and improve
10841 some other circuit timeout messages. Resolves bug 2004.
10842 - Log a little more clearly about the times at which we're no longer
10843 accepting new connections. Resolves bug 2181.
10844 - Reject attempts at the client side to open connections to private
10845 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
10846 a randomly chosen exit node. Attempts to do so are always
10847 ill-defined, generally prevented by exit policies, and usually
10848 in error. This will also help to detect loops in transparent
10849 proxy configurations. You can disable this feature by setting
10850 "ClientRejectInternalAddresses 0" in your torrc.
10851 - Always treat failure to allocate an RSA key as an unrecoverable
10853 - Update to the March 1 2011 Maxmind GeoLite Country database.
10855 o Minor features (log subsystem):
10856 - Add documentation for configuring logging at different severities in
10857 different log domains. We've had this feature since 0.2.1.1-alpha,
10858 but for some reason it never made it into the manpage. Fixes
10860 - Make it simpler to specify "All log domains except for A and B".
10861 Previously you needed to say "[*,~A,~B]". Now you can just say
10863 - Add a "LogMessageDomains 1" option to include the domains of log
10864 messages along with the messages. Without this, there's no way
10865 to use log domains without reading the source or doing a lot
10868 o Packaging changes:
10869 - Stop shipping the Tor specs files and development proposal documents
10870 in the tarball. They are now in a separate git repository at
10871 git://git.torproject.org/torspec.git
10874 Changes in version 0.2.1.30 - 2011-02-23
10875 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
10876 change is a slight tweak to Tor's TLS handshake that makes relays
10877 and bridges that run this new version reachable from Iran again.
10878 We don't expect this tweak will win the arms race long-term, but it
10879 buys us time until we roll out a better solution.
10882 - Stop sending a CLOCK_SKEW controller status event whenever
10883 we fetch directory information from a relay that has a wrong clock.
10884 Instead, only inform the controller when it's a trusted authority
10885 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
10886 the rest of bug 1074.
10887 - Fix a bounds-checking error that could allow an attacker to
10888 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
10889 Found by "piebeer".
10890 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
10891 Tor would ignore their RelayBandwidthBurst setting,
10892 potentially using more bandwidth than expected. Bugfix on
10893 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
10894 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
10895 hidserv" in her torrc. The 'hidserv' argument never controlled
10896 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
10899 - Adjust our TLS Diffie-Hellman parameters to match those used by
10901 - Update to the February 1 2011 Maxmind GeoLite Country database.
10904 - Check for and reject overly long directory certificates and
10905 directory tokens before they have a chance to hit any assertions.
10906 Bugfix on 0.2.1.28. Found by "doorss".
10907 - Bring the logic that gathers routerinfos and assesses the
10908 acceptability of circuits into line. This prevents a Tor OP from
10909 getting locked in a cycle of choosing its local OR as an exit for a
10910 path (due to a .exit request) and then rejecting the circuit because
10911 its OR is not listed yet. It also prevents Tor clients from using an
10912 OR running in the same instance as an exit (due to a .exit request)
10913 if the OR does not meet the same requirements expected of an OR
10914 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10916 o Packaging changes:
10917 - Stop shipping the Tor specs files and development proposal documents
10918 in the tarball. They are now in a separate git repository at
10919 git://git.torproject.org/torspec.git
10920 - Do not include Git version tags as though they are SVN tags when
10921 generating a tarball from inside a repository that has switched
10922 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
10925 Changes in version 0.2.2.22-alpha - 2011-01-25
10926 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
10927 main other change is a slight tweak to Tor's TLS handshake that makes
10928 relays and bridges that run this new version reachable from Iran again.
10929 We don't expect this tweak will win the arms race long-term, but it
10930 will buy us a bit more time until we roll out a better solution.
10933 - Fix a bounds-checking error that could allow an attacker to
10934 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
10935 Found by "piebeer".
10936 - Don't assert when changing from bridge to relay or vice versa
10937 via the controller. The assert happened because we didn't properly
10938 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
10939 bug 2433. Reported by bastik.
10942 - Adjust our TLS Diffie-Hellman parameters to match those used by
10944 - Provide a log message stating which geoip file we're parsing
10945 instead of just stating that we're parsing the geoip file.
10946 Implements ticket 2432.
10949 - Check for and reject overly long directory certificates and
10950 directory tokens before they have a chance to hit any assertions.
10951 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
10954 Changes in version 0.2.2.21-alpha - 2011-01-15
10955 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
10956 continues our recent code security audit work. The main fix resolves
10957 a remote heap overflow vulnerability that can allow remote code
10958 execution (CVE-2011-0427). Other fixes address a variety of assert
10959 and crash bugs, most of which we think are hard to exploit remotely.
10961 o Major bugfixes (security), also included in 0.2.1.29:
10962 - Fix a heap overflow bug where an adversary could cause heap
10963 corruption. This bug probably allows remote code execution
10964 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
10966 - Prevent a denial-of-service attack by disallowing any
10967 zlib-compressed data whose compression factor is implausibly
10968 high. Fixes part of bug 2324; reported by "doorss".
10969 - Zero out a few more keys in memory before freeing them. Fixes
10970 bug 2384 and part of bug 2385. These key instances found by
10971 "cypherpunks", based on Andrew Case's report about being able
10972 to find sensitive data in Tor's memory space if you have enough
10973 permissions. Bugfix on 0.0.2pre9.
10975 o Major bugfixes (crashes), also included in 0.2.1.29:
10976 - Prevent calls to Libevent from inside Libevent log handlers.
10977 This had potential to cause a nasty set of crashes, especially
10978 if running Libevent with debug logging enabled, and running
10979 Tor with a controller watching for low-severity log messages.
10980 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
10981 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
10982 underflow errors there too. Fixes the other part of bug 2324.
10983 - Fix a bug where we would assert if we ever had a
10984 cached-descriptors.new file (or another file read directly into
10985 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
10986 on 0.2.1.25. Found by doorss.
10987 - Fix some potential asserts and parsing issues with grossly
10988 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
10991 o Minor bugfixes (other), also included in 0.2.1.29:
10992 - Fix a bug with handling misformed replies to reverse DNS lookup
10993 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
10994 bug reported by doorss.
10995 - Fix compilation on mingw when a pthreads compatibility library
10996 has been installed. (We don't want to use it, so we shouldn't
10997 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
10998 - Fix a bug where we would declare that we had run out of virtual
10999 addresses when the address space was only half-exhausted. Bugfix
11001 - Correctly handle the case where AutomapHostsOnResolve is set but
11002 no virtual addresses are available. Fixes bug 2328; bugfix on
11003 0.1.2.1-alpha. Bug found by doorss.
11004 - Correctly handle wrapping around when we run out of virtual
11005 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
11007 o Minor features, also included in 0.2.1.29:
11008 - Update to the January 1 2011 Maxmind GeoLite Country database.
11009 - Introduce output size checks on all of our decryption functions.
11011 o Build changes, also included in 0.2.1.29:
11012 - Tor does not build packages correctly with Automake 1.6 and earlier;
11013 added a check to Makefile.am to make sure that we're building with
11014 Automake 1.7 or later.
11015 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
11016 because we built it with a too-old version of automake. Thus that
11017 release broke ./configure --enable-openbsd-malloc, which is popular
11018 among really fast exit relays on Linux.
11020 o Major bugfixes, new in 0.2.2.21-alpha:
11021 - Prevent crash/heap corruption when the cbtnummodes consensus
11022 parameter is set to 0 or large values. Fixes bug 2317; bugfix
11025 o Major features, new in 0.2.2.21-alpha:
11026 - Introduce minimum/maximum values that clients will believe
11027 from the consensus. Now we'll have a better chance to avoid crashes
11028 or worse when a consensus param has a weird value.
11030 o Minor features, new in 0.2.2.21-alpha:
11031 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
11032 used on bridges, and it makes bridge scanning somewhat easier.
11033 - If writing the state file to disk fails, wait up to an hour before
11034 retrying again, rather than trying again each second. Fixes bug
11035 2346; bugfix on Tor 0.1.1.3-alpha.
11036 - Make Libevent log messages get delivered to controllers later,
11037 and not from inside the Libevent log handler. This prevents unsafe
11038 reentrant Libevent calls while still letting the log messages
11040 - Detect platforms that brokenly use a signed size_t, and refuse to
11041 build there. Found and analyzed by doorss and rransom.
11042 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
11045 o Minor bugfixes, new in 0.2.2.21-alpha:
11046 - Handle SOCKS messages longer than 128 bytes long correctly, rather
11047 than waiting forever for them to finish. Fixes bug 2330; bugfix
11048 on 0.2.0.16-alpha. Found by doorss.
11049 - Add assertions to check for overflow in arguments to
11050 base32_encode() and base32_decode(); fix a signed-unsigned
11051 comparison there too. These bugs are not actually reachable in Tor,
11052 but it's good to prevent future errors too. Found by doorss.
11053 - Correctly detect failures to create DNS requests when using Libevent
11054 versions before v2. (Before Libevent 2, we used our own evdns
11055 implementation. Its return values for Libevent's evdns_resolve_*()
11056 functions are not consistent with those from Libevent.) Fixes bug
11057 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
11059 o Documentation, new in 0.2.2.21-alpha:
11060 - Document the default socks host and port (127.0.0.1:9050) for
11064 Changes in version 0.2.1.29 - 2011-01-15
11065 Tor 0.2.1.29 continues our recent code security audit work. The main
11066 fix resolves a remote heap overflow vulnerability that can allow remote
11067 code execution. Other fixes address a variety of assert and crash bugs,
11068 most of which we think are hard to exploit remotely.
11070 o Major bugfixes (security):
11071 - Fix a heap overflow bug where an adversary could cause heap
11072 corruption. This bug probably allows remote code execution
11073 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
11075 - Prevent a denial-of-service attack by disallowing any
11076 zlib-compressed data whose compression factor is implausibly
11077 high. Fixes part of bug 2324; reported by "doorss".
11078 - Zero out a few more keys in memory before freeing them. Fixes
11079 bug 2384 and part of bug 2385. These key instances found by
11080 "cypherpunks", based on Andrew Case's report about being able
11081 to find sensitive data in Tor's memory space if you have enough
11082 permissions. Bugfix on 0.0.2pre9.
11084 o Major bugfixes (crashes):
11085 - Prevent calls to Libevent from inside Libevent log handlers.
11086 This had potential to cause a nasty set of crashes, especially
11087 if running Libevent with debug logging enabled, and running
11088 Tor with a controller watching for low-severity log messages.
11089 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
11090 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
11091 underflow errors there too. Fixes the other part of bug 2324.
11092 - Fix a bug where we would assert if we ever had a
11093 cached-descriptors.new file (or another file read directly into
11094 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
11095 on 0.2.1.25. Found by doorss.
11096 - Fix some potential asserts and parsing issues with grossly
11097 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
11100 o Minor bugfixes (other):
11101 - Fix a bug with handling misformed replies to reverse DNS lookup
11102 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
11103 bug reported by doorss.
11104 - Fix compilation on mingw when a pthreads compatibility library
11105 has been installed. (We don't want to use it, so we shouldn't
11106 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
11107 - Fix a bug where we would declare that we had run out of virtual
11108 addresses when the address space was only half-exhausted. Bugfix
11110 - Correctly handle the case where AutomapHostsOnResolve is set but
11111 no virtual addresses are available. Fixes bug 2328; bugfix on
11112 0.1.2.1-alpha. Bug found by doorss.
11113 - Correctly handle wrapping around to when we run out of virtual
11114 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
11115 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
11116 because we built it with a too-old version of automake. Thus that
11117 release broke ./configure --enable-openbsd-malloc, which is popular
11118 among really fast exit relays on Linux.
11121 - Update to the January 1 2011 Maxmind GeoLite Country database.
11122 - Introduce output size checks on all of our decryption functions.
11125 - Tor does not build packages correctly with Automake 1.6 and earlier;
11126 added a check to Makefile.am to make sure that we're building with
11127 Automake 1.7 or later.
11130 Changes in version 0.2.2.20-alpha - 2010-12-17
11131 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
11132 exploitable bugs. We also fix a variety of other significant bugs,
11133 change the IP address for one of our directory authorities, and update
11134 the minimum version that Tor relays must run to join the network.
11137 - Fix a remotely exploitable bug that could be used to crash instances
11138 of Tor remotely by overflowing on the heap. Remote-code execution
11139 hasn't been confirmed, but can't be ruled out. Everyone should
11140 upgrade. Bugfix on the 0.1.1 series and later.
11141 - Fix a bug that could break accounting on 64-bit systems with large
11142 time_t values, making them hibernate for impossibly long intervals.
11143 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
11144 - Fix a logic error in directory_fetches_from_authorities() that
11145 would cause all _non_-exits refusing single-hop-like circuits
11146 to fetch from authorities, when we wanted to have _exits_ fetch
11147 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
11149 - Fix a stream fairness bug that would cause newer streams on a given
11150 circuit to get preference when reading bytes from the origin or
11151 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
11152 introduced before the first Tor release, in svn revision r152.
11154 o Directory authority changes:
11155 - Change IP address and ports for gabelmoo (v3 directory authority).
11158 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
11159 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
11160 - Fix an off-by-one error in calculating some controller command
11161 argument lengths. Fortunately, this mistake is harmless since
11162 the controller code does redundant NUL termination too. Found by
11163 boboper. Bugfix on 0.1.1.1-alpha.
11164 - Do not dereference NULL if a bridge fails to build its
11165 extra-info descriptor. Found by an anonymous commenter on
11166 Trac. Bugfix on 0.2.2.19-alpha.
11169 - Update to the December 1 2010 Maxmind GeoLite Country database.
11170 - Directory authorities now reject relays running any versions of
11171 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
11172 known bugs that keep RELAY_EARLY cells from working on rendezvous
11173 circuits. Followup to fix for bug 2081.
11174 - Directory authorities now reject relays running any version of Tor
11175 older than 0.2.0.26-rc. That version is the earliest that fetches
11176 current directory information correctly. Fixes bug 2156.
11177 - Report only the top 10 ports in exit-port stats in order not to
11178 exceed the maximum extra-info descriptor length of 50 KB. Implements
11182 Changes in version 0.2.1.28 - 2010-12-17
11183 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
11184 exploitable bugs. We also took this opportunity to change the IP address
11185 for one of our directory authorities, and to update the geoip database
11189 - Fix a remotely exploitable bug that could be used to crash instances
11190 of Tor remotely by overflowing on the heap. Remote-code execution
11191 hasn't been confirmed, but can't be ruled out. Everyone should
11192 upgrade. Bugfix on the 0.1.1 series and later.
11194 o Directory authority changes:
11195 - Change IP address and ports for gabelmoo (v3 directory authority).
11198 - Update to the December 1 2010 Maxmind GeoLite Country database.
11201 Changes in version 0.2.1.27 - 2010-11-23
11202 Yet another OpenSSL security patch broke its compatibility with Tor:
11203 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
11204 also took this opportunity to fix several crash bugs, integrate a new
11205 directory authority, and update the bundled GeoIP database.
11208 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
11209 No longer set the tlsext_host_name extension on server SSL objects;
11210 but continue to set it on client SSL objects. Our goal in setting
11211 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
11212 bugfix on 0.2.1.1-alpha.
11213 - Do not log messages to the controller while shrinking buffer
11214 freelists. Doing so would sometimes make the controller connection
11215 try to allocate a buffer chunk, which would mess up the internals
11216 of the freelist and cause an assertion failure. Fixes bug 1125;
11217 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
11218 - Learn our external IP address when we're a relay or bridge, even if
11219 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
11220 where we introduced bridge relays that don't need to publish to
11221 be useful. Fixes bug 2050.
11222 - Do even more to reject (and not just ignore) annotations on
11223 router descriptors received anywhere but from the cache. Previously
11224 we would ignore such annotations at first, but cache them to disk
11225 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
11226 - When you're using bridges and your network goes away and your
11227 bridges get marked as down, recover when you attempt a new socks
11228 connection (if the network is back), rather than waiting up to an
11229 hour to try fetching new descriptors for your bridges. Bugfix on
11230 0.2.0.3-alpha; fixes bug 1981.
11233 - Move to the November 2010 Maxmind GeoLite country db (rather
11234 than the June 2009 ip-to-country GeoIP db) for our statistics that
11235 count how many users relays are seeing from each country. Now we'll
11236 have more accurate data, especially for many African countries.
11238 o New directory authorities:
11239 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
11243 - Fix an assertion failure that could occur in directory caches or
11244 bridge users when using a very short voting interval on a testing
11245 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
11247 - Enforce multiplicity rules when parsing annotations. Bugfix on
11248 0.2.0.8-alpha. Found by piebeer.
11249 - Allow handshaking OR connections to take a full KeepalivePeriod
11250 seconds to handshake. Previously, we would close them after
11251 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
11252 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
11254 - When building with --enable-gcc-warnings on OpenBSD, disable
11255 warnings in system headers. This makes --enable-gcc-warnings
11256 pass on OpenBSD 4.8.
11259 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
11260 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
11261 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
11262 Servers can start sending this code when enough clients recognize
11263 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
11264 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
11265 Patch from mingw-san.
11268 - Remove the old debian/ directory from the main Tor distribution.
11269 The official Tor-for-debian git repository lives at the URL
11270 https://git.torproject.org/debian/tor.git
11271 - Stop shipping the old doc/website/ directory in the tarball. We
11272 changed the website format in late 2010, and what we shipped in
11273 0.2.1.26 really wasn't that useful anyway.
11276 Changes in version 0.2.2.19-alpha - 2010-11-22
11277 Yet another OpenSSL security patch broke its compatibility with Tor:
11278 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
11281 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
11282 No longer set the tlsext_host_name extension on server SSL objects;
11283 but continue to set it on client SSL objects. Our goal in setting
11284 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
11285 bugfix on 0.2.1.1-alpha.
11288 - Try harder not to exceed the maximum length of 50 KB when writing
11289 statistics to extra-info descriptors. This bug was triggered by very
11290 fast relays reporting exit-port, entry, and dirreq statistics.
11291 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
11292 - Publish a router descriptor even if generating an extra-info
11293 descriptor fails. Previously we would not publish a router
11294 descriptor without an extra-info descriptor; this can cause fast
11295 exit relays collecting exit-port statistics to drop from the
11296 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
11299 Changes in version 0.2.2.18-alpha - 2010-11-16
11300 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
11301 us lately, makes unpublished bridge relays able to detect their IP
11302 address, and fixes a wide variety of other bugs to get us much closer
11303 to a stable release.
11306 - Do even more to reject (and not just ignore) annotations on
11307 router descriptors received anywhere but from the cache. Previously
11308 we would ignore such annotations at first, but cache them to disk
11309 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
11310 - Do not log messages to the controller while shrinking buffer
11311 freelists. Doing so would sometimes make the controller connection
11312 try to allocate a buffer chunk, which would mess up the internals
11313 of the freelist and cause an assertion failure. Fixes bug 1125;
11314 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
11315 - Learn our external IP address when we're a relay or bridge, even if
11316 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
11317 where we introduced bridge relays that don't need to publish to
11318 be useful. Fixes bug 2050.
11319 - Maintain separate TLS contexts and certificates for incoming and
11320 outgoing connections in bridge relays. Previously we would use the
11321 same TLS contexts and certs for incoming and outgoing connections.
11322 Bugfix on 0.2.0.3-alpha; addresses bug 988.
11323 - Maintain separate identity keys for incoming and outgoing TLS
11324 contexts in bridge relays. Previously we would use the same
11325 identity keys for incoming and outgoing TLS contexts. Bugfix on
11326 0.2.0.3-alpha; addresses the other half of bug 988.
11327 - Avoid an assertion failure when we as an authority receive a
11328 duplicate upload of a router descriptor that we already have,
11329 but which we previously considered an obsolete descriptor.
11330 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
11331 - Avoid a crash bug triggered by looking at a dangling pointer while
11332 setting the network status consensus. Found by Robert Ransom.
11333 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
11334 - Fix a logic error where servers that _didn't_ act as exits would
11335 try to keep their server lists more aggressively up to date than
11336 exits, when it was supposed to be the other way around. Bugfix
11339 o Minor bugfixes (on Tor 0.2.1.x and earlier):
11340 - When we're trying to guess whether we know our IP address as
11341 a relay, we would log various ways that we failed to guess
11342 our address, but never log that we ended up guessing it
11343 successfully. Now add a log line to help confused and anxious
11344 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
11345 - Bring the logic that gathers routerinfos and assesses the
11346 acceptability of circuits into line. This prevents a Tor OP from
11347 getting locked in a cycle of choosing its local OR as an exit for a
11348 path (due to a .exit request) and then rejecting the circuit because
11349 its OR is not listed yet. It also prevents Tor clients from using an
11350 OR running in the same instance as an exit (due to a .exit request)
11351 if the OR does not meet the same requirements expected of an OR
11352 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
11353 - Correctly describe errors that occur when generating a TLS object.
11354 Previously we would attribute them to a failure while generating a
11355 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
11357 - Enforce multiplicity rules when parsing annotations. Bugfix on
11358 0.2.0.8-alpha. Found by piebeer.
11359 - Fix warnings that newer versions of autoconf produced during
11360 ./autogen.sh. These warnings appear to be harmless in our case,
11361 but they were extremely verbose. Fixes bug 2020.
11363 o Minor bugfixes (on Tor 0.2.2.x):
11364 - Enable protection of small arrays whenever we build with gcc
11365 hardening features, not only when also building with warnings
11366 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
11369 - Make hidden services work better in private Tor networks by not
11370 requiring any uptime to join the hidden service descriptor
11371 DHT. Implements ticket 2088.
11372 - Rate-limit the "your application is giving Tor only an IP address"
11373 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
11374 - When AllowSingleHopExits is set, print a warning to explain to the
11375 relay operator why most clients are avoiding her relay.
11376 - Update to the November 1 2010 Maxmind GeoLite Country database.
11378 o Code simplifications and refactoring:
11379 - When we fixed bug 1038 we had to put in a restriction not to send
11380 RELAY_EARLY cells on rend circuits. This was necessary as long
11381 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
11382 active. Now remove this obsolete check. Resolves bug 2081.
11383 - Some options used different conventions for uppercasing of acronyms
11384 when comparing manpage and source. Fix those in favor of the
11385 manpage, as it makes sense to capitalize acronyms.
11386 - Remove the torrc.complete file. It hasn't been kept up to date
11387 and users will have better luck checking out the manpage.
11388 - Remove the obsolete "NoPublish" option; it has been flagged
11389 as obsolete and has produced a warning since 0.1.1.18-rc.
11390 - Remove everything related to building the expert bundle for OS X.
11391 It has confused many users, doesn't work right on OS X 10.6,
11392 and is hard to get rid of once installed. Resolves bug 1274.
11395 Changes in version 0.2.2.17-alpha - 2010-09-30
11396 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
11397 to use one-hop circuits (which can put the exit relays at higher risk,
11398 plus unbalance the network); fixes a big bug in bandwidth accounting
11399 for relays that want to limit their monthly bandwidth use; fixes a
11400 big pile of bugs in how clients tolerate temporary network failure;
11401 and makes our adaptive circuit build timeout feature (which improves
11402 client performance if your network is fast while not breaking things
11403 if your network is slow) better handle bad networks.
11406 - Exit relays now try harder to block exit attempts from unknown
11407 relays, to make it harder for people to use them as one-hop proxies
11408 a la tortunnel. Controlled by the refuseunknownexits consensus
11409 parameter (currently enabled), or you can override it on your
11410 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
11412 o Major bugfixes (0.2.1.x and earlier):
11413 - Fix a bug in bandwidth accounting that could make us use twice
11414 the intended bandwidth when our interval start changes due to
11415 daylight saving time. Now we tolerate skew in stored vs computed
11416 interval starts: if the start of the period changes by no more than
11417 50% of the period's duration, we remember bytes that we transferred
11418 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
11419 - Always search the Windows system directory for system DLLs, and
11420 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
11421 - When you're using bridges and your network goes away and your
11422 bridges get marked as down, recover when you attempt a new socks
11423 connection (if the network is back), rather than waiting up to an
11424 hour to try fetching new descriptors for your bridges. Bugfix on
11425 0.2.0.3-alpha; fixes bug 1981.
11427 o Major bugfixes (on 0.2.2.x):
11428 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
11430 - Fix a segfault that could happen when operating a bridge relay with
11431 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
11432 - The consensus bandwidth-weights (used by clients to choose fast
11433 relays) entered an unexpected edge case in September where
11434 Exits were much scarcer than Guards, resulting in bad weight
11435 recommendations. Now we compute them using new constraints that
11436 should succeed in all cases. Also alter directory authorities to
11437 not include the bandwidth-weights line if they fail to produce
11438 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
11439 - When weighting bridges during path selection, we used to trust
11440 the bandwidths they provided in their descriptor, only capping them
11441 at 10MB/s. This turned out to be problematic for two reasons:
11442 Bridges could claim to handle a lot more traffic then they
11443 actually would, thus making more clients pick them and have a
11444 pretty effective DoS attack. The other issue is that new bridges
11445 that might not have a good estimate for their bw capacity yet
11446 would not get used at all unless no other bridges are available
11447 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
11449 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
11450 - Ignore cannibalized circuits when recording circuit build times.
11451 This should provide for a minor performance improvement for hidden
11452 service users using 0.2.2.14-alpha, and should remove two spurious
11453 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
11454 - Simplify the logic that causes us to decide if the network is
11455 unavailable for purposes of recording circuit build times. If we
11456 receive no cells whatsoever for the entire duration of a circuit's
11457 full measured lifetime, the network is probably down. Also ignore
11458 one-hop directory fetching circuit timeouts when calculating our
11459 circuit build times. These changes should hopefully reduce the
11460 cases where we see ridiculous circuit build timeouts for people
11461 with spotty wireless connections. Fixes part of bug 1772; bugfix
11463 - Prevent the circuit build timeout from becoming larger than
11464 the maximum build time we have ever seen. Also, prevent the time
11465 period for measurement circuits from becoming larger than twice that
11466 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
11469 - When we run out of directory information such that we can't build
11470 circuits, but then get enough that we can build circuits, log when
11471 we actually construct a circuit, so the user has a better chance of
11472 knowing what's going on. Fixes bug 1362.
11473 - Be more generous with how much bandwidth we'd use up (with
11474 accounting enabled) before entering "soft hibernation". Previously,
11475 we'd refuse new connections and circuits once we'd used up 95% of
11476 our allotment. Now, we use up 95% of our allotment, AND make sure
11477 that we have no more than 500MB (or 3 hours of expected traffic,
11478 whichever is lower) remaining before we enter soft hibernation.
11479 - If we've configured EntryNodes and our network goes away and/or all
11480 our entrynodes get marked down, optimistically retry them all when
11481 a new socks application request appears. Fixes bug 1882.
11482 - Add some more defensive programming for architectures that can't
11483 handle unaligned integer accesses. We don't know of any actual bugs
11484 right now, but that's the best time to fix them. Fixes bug 1943.
11485 - Support line continuations in the torrc config file. If a line
11486 ends with a single backslash character, the newline is ignored, and
11487 the configuration value is treated as continuing on the next line.
11490 o Minor bugfixes (on 0.2.1.x and earlier):
11491 - For bandwidth accounting, calculate our expected bandwidth rate
11492 based on the time during which we were active and not in
11493 soft-hibernation during the last interval. Previously, we were
11494 also considering the time spent in soft-hibernation. If this
11495 was a long time, we would wind up underestimating our bandwidth
11496 by a lot, and skewing our wakeup time towards the start of the
11497 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
11499 o Minor bugfixes (on 0.2.2.x):
11500 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
11501 which were disabled by the circuit build timeout changes in
11502 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
11503 - Make sure we don't warn about missing bandwidth weights when
11504 choosing bridges or other relays not in the consensus. Bugfix on
11505 0.2.2.10-alpha; fixes bug 1805.
11506 - In our logs, do not double-report signatures from unrecognized
11507 authorities both as "from unknown authority" and "not
11508 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
11511 Changes in version 0.2.2.16-alpha - 2010-09-17
11512 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
11513 evident at exit relays), and also continues to resolve all the little
11514 bugs that have been filling up trac lately.
11516 o Major bugfixes (stream-level fairness):
11517 - When receiving a circuit-level SENDME for a blocked circuit, try
11518 to package cells fairly from all the streams that had previously
11519 been blocked on that circuit. Previously, we had started with the
11520 oldest stream, and allowed each stream to potentially exhaust
11521 the circuit's package window. This gave older streams on any
11522 given circuit priority over newer ones. Fixes bug 1937. Detected
11523 originally by Camilo Viecco. This bug was introduced before the
11524 first Tor release, in svn commit r152: it is the new winner of
11525 the longest-lived bug prize.
11526 - When the exit relay got a circuit-level sendme cell, it started
11527 reading on the exit streams, even if had 500 cells queued in the
11528 circuit queue already, so the circuit queue just grew and grew in
11529 some cases. We fix this by not re-enabling reading on receipt of a
11530 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
11531 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
11533 - Newly created streams were allowed to read cells onto circuits,
11534 even if the circuit's cell queue was blocked and waiting to drain.
11535 This created potential unfairness, as older streams would be
11536 blocked, but newer streams would gladly fill the queue completely.
11537 We add code to detect this situation and prevent any stream from
11538 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
11542 - Update to the September 1 2010 Maxmind GeoLite Country database.
11543 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
11544 not. This would lead to a cookie that is still not group readable.
11545 Closes bug 1843. Suggested by katmagic.
11546 - When logging a rate-limited warning, we now mention how many messages
11547 got suppressed since the last warning.
11548 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
11549 do individual connection-level rate limiting of clients. The torrc
11550 config options with the same names trump the consensus params, if
11551 both are present. Replaces the old "bwconnrate" and "bwconnburst"
11552 consensus params which were broken from 0.2.2.7-alpha through
11553 0.2.2.14-alpha. Closes bug 1947.
11554 - When a router changes IP address or port, authorities now launch
11555 a new reachability test for it. Implements ticket 1899.
11556 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
11557 2 no signature, 4 required" messages about consensus signatures
11558 easier to read, and make sure they get logged at the same severity
11559 as the messages explaining which keys are which. Fixes bug 1290.
11560 - Don't warn when we have a consensus that we can't verify because
11561 of missing certificates, unless those certificates are ones
11562 that we have been trying and failing to download. Fixes bug 1145.
11563 - If you configure your bridge with a known identity fingerprint,
11564 and the bridge authority is unreachable (as it is in at least
11565 one country now), fall back to directly requesting the descriptor
11566 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
11568 - When building with --enable-gcc-warnings on OpenBSD, disable
11569 warnings in system headers. This makes --enable-gcc-warnings
11570 pass on OpenBSD 4.8.
11572 o Minor bugfixes (on 0.2.1.x and earlier):
11573 - Authorities will now attempt to download consensuses if their
11574 own efforts to make a live consensus have failed. This change
11575 means authorities that restart will fetch a valid consensus, and
11576 it means authorities that didn't agree with the current consensus
11577 will still fetch and serve it if it has enough signatures. Bugfix
11578 on 0.2.0.9-alpha; fixes bug 1300.
11579 - Ensure DNS requests launched by "RESOLVE" commands from the
11580 controller respect the __LeaveStreamsUnattached setconf options. The
11581 same goes for requests launched via DNSPort or transparent
11582 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
11583 - Allow handshaking OR connections to take a full KeepalivePeriod
11584 seconds to handshake. Previously, we would close them after
11585 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
11586 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
11588 - Rate-limit "Failed to hand off onionskin" warnings.
11589 - Never relay a cell for a circuit we have already destroyed.
11590 Between marking a circuit as closeable and finally closing it,
11591 it may have been possible for a few queued cells to get relayed,
11592 even though they would have been immediately dropped by the next
11593 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
11594 - Never queue a cell for a circuit that's already been marked
11596 - Never vote for a server as "Running" if we have a descriptor for
11597 it claiming to be hibernating, and that descriptor was published
11598 more recently than our last contact with the server. Bugfix on
11599 0.2.0.3-alpha; fixes bug 911.
11600 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
11603 o Minor bugfixes (on 0.2.2.x):
11604 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
11605 down if a directory fetch fails and you've configured either
11606 bridges or EntryNodes. The intent was to mark the relay as down
11607 _unless_ you're using bridges or EntryNodes, since if you are
11608 then you could quickly run out of entry points.
11609 - Fix the Windows directory-listing code. A bug introduced in
11610 0.2.2.14-alpha could make Windows directory servers forget to load
11611 some of their cached v2 networkstatus files.
11612 - Really allow clients to use relays as bridges. Fixes bug 1776;
11613 bugfix on 0.2.2.15-alpha.
11614 - Demote a warn to info that happens when the CellStatistics option
11615 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
11616 Reported by Moritz Bartl.
11617 - On Windows, build correctly either with or without Unicode support.
11618 This is necessary so that Tor can support fringe platforms like
11619 Windows 98 (which has no Unicode), or Windows CE (which has no
11620 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
11623 - Add a unit test for cross-platform directory-listing code.
11626 Changes in version 0.2.2.15-alpha - 2010-08-18
11627 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
11628 fixes a variety of other bugs that were preventing performance
11629 experiments from moving forward, fixes several bothersome memory leaks,
11630 and generally closes a lot of smaller bugs that have been filling up
11634 - Stop assigning the HSDir flag to relays that disable their
11635 DirPort (and thus will refuse to answer directory requests). This
11636 fix should dramatically improve the reachability of hidden services:
11637 hidden services and hidden service clients pick six HSDir relays
11638 to store and retrieve the hidden service descriptor, and currently
11639 about half of the HSDir relays will refuse to work. Bugfix on
11640 0.2.0.10-alpha; fixes part of bug 1693.
11641 - The PerConnBWRate and Burst config options, along with the
11642 bwconnrate and bwconnburst consensus params, initialized each conn's
11643 token bucket values only when the connection is established. Now we
11644 update them if the config options change, and update them every time
11645 we get a new consensus. Otherwise we can encounter an ugly edge
11646 case where we initialize an OR conn to client-level bandwidth,
11647 but then later the relay joins the consensus and we leave it
11648 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
11649 - Fix a regression that caused Tor to rebind its ports if it receives
11650 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
11653 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
11654 should give us approximately 40-50% more Guard-flagged nodes,
11655 improving the anonymity the Tor network can provide and also
11656 decreasing the dropoff in throughput that relays experience when
11657 they first get the Guard flag.
11658 - Allow enabling or disabling the *Statistics config options while
11662 - Update to the August 1 2010 Maxmind GeoLite Country database.
11663 - Have the controller interface give a more useful message than
11664 "Internal Error" in response to failed GETINFO requests.
11665 - Warn when the same option is provided more than once in a torrc
11666 file, on the command line, or in a single SETCONF statement, and
11667 the option is one that only accepts a single line. Closes bug 1384.
11668 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
11669 Patch from mingw-san.
11670 - Add support for the country code "{??}" in torrc options like
11671 ExcludeNodes, to indicate all routers of unknown country. Closes
11673 - Relays report the number of bytes spent on answering directory
11674 requests in extra-info descriptors similar to {read,write}-history.
11675 Implements enhancement 1790.
11677 o Minor bugfixes (on 0.2.1.x and earlier):
11678 - Complain if PublishServerDescriptor is given multiple arguments that
11679 include 0 or 1. This configuration will be rejected in the future.
11680 Bugfix on 0.2.0.1-alpha; closes bug 1107.
11681 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
11682 Bugfix on 0.2.0.13-alpha; closes bug 928.
11683 - Change "Application request when we're believed to be offline."
11684 notice to "Application request when we haven't used client
11685 functionality lately.", to clarify that it's not an error. Bugfix
11686 on 0.0.9.3; fixes bug 1222.
11687 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
11688 would return "551 Internal error" rather than "552 Unrecognized key
11689 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
11690 - Users can't configure a regular relay to be their bridge. It didn't
11691 work because when Tor fetched the bridge descriptor, it found
11692 that it already had it, and didn't realize that the purpose of the
11693 descriptor had changed. Now we replace routers with a purpose other
11694 than bridge with bridge descriptors when fetching them. Bugfix on
11695 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
11696 refetch the descriptor with router purpose 'general', disabling
11698 - Fix a rare bug in rend_fn unit tests: we would fail a test when
11699 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
11700 on 0.2.0.10-alpha; fixes bug 1808.
11701 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
11702 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
11703 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
11704 Servers can start sending this code when enough clients recognize
11705 it. Also update the spec to reflect this new reason. Bugfix on
11706 0.1.0.1-rc; fixes part of bug 1793.
11707 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
11708 when we switch from being a public relay to a bridge. Otherwise
11709 there will still be clients that see the relay in their consensus,
11710 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
11712 - Instead of giving an assertion failure on an internal mismatch
11713 on estimated freelist size, just log a BUG warning and try later.
11714 Mitigates but does not fix bug 1125.
11715 - Fix an assertion failure that could occur in caches or bridge users
11716 when using a very short voting interval on a testing network.
11717 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
11719 o Minor bugfixes (on 0.2.2.x):
11720 - Alter directory authorities to always consider Exit-flagged nodes
11721 as potential Guard nodes in their votes. The actual decision to
11722 use Exits as Guards is done in the consensus bandwidth weights.
11723 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
11724 - When the controller is reporting the purpose of circuits that
11725 didn't finish building before the circuit build timeout, it was
11726 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
11727 - Our libevent version parsing code couldn't handle versions like
11728 1.4.14b-stable and incorrectly warned the user about using an
11729 old and broken version of libevent. Treat 1.4.14b-stable like
11730 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
11732 - Don't use substitution references like $(VAR:MOD) when
11733 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
11734 '$(:x)' to 'x' rather than the empty string. This bites us in
11735 doc/ when configured with --disable-asciidoc. Bugfix on
11736 0.2.2.9-alpha; fixes bug 1773.
11737 - Remove a spurious hidden service server-side log notice about
11738 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
11740 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
11742 - Correctly report written bytes on linked connections. Found while
11743 implementing 1790. Bugfix on 0.2.2.4-alpha.
11744 - Fix three memory leaks: one in circuit_build_times_parse_state(),
11745 one in dirvote_add_signatures_to_pending_consensus(), and one every
11746 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
11747 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
11749 o Code simplifications and refactoring:
11750 - Take a first step towards making or.h smaller by splitting out
11751 function definitions for all source files in src/or/. Leave
11752 structures and defines in or.h for now.
11753 - Remove a bunch of unused function declarations as well as a block of
11754 #if 0'd code from the unit tests. Closes bug 1824.
11755 - New unit tests for exit-port history statistics; refactored exit
11756 statistics code to be more easily tested.
11757 - Remove the old debian/ directory from the main Tor distribution.
11758 The official Tor-for-debian git repository lives at the URL
11759 https://git.torproject.org/debian/tor.git
11762 Changes in version 0.2.2.14-alpha - 2010-07-12
11763 Tor 0.2.2.14-alpha greatly improves client-side handling of
11764 circuit build timeouts, which are used to estimate speed and improve
11765 performance. We also move to a much better GeoIP database, port Tor to
11766 Windows CE, introduce new compile flags that improve code security,
11767 add an eighth v3 directory authority, and address a lot of more
11771 - Tor directory authorities no longer crash when started with a
11772 cached-microdesc-consensus file in their data directory. Bugfix
11773 on 0.2.2.6-alpha; fixes bug 1532.
11774 - Treat an unset $HOME like an empty $HOME rather than triggering an
11775 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
11776 - Ignore negative and large circuit build timeout values that can
11777 happen during a suspend or hibernate. These values caused various
11778 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
11779 - Alter calculation of Pareto distribution parameter 'Xm' for
11780 Circuit Build Timeout learning to use the weighted average of the
11781 top N=3 modes (because we have three entry guards). Considering
11782 multiple modes should improve the timeout calculation in some cases,
11783 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
11785 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
11786 right censored distribution model. This approach improves over the
11787 synthetic timeout generation approach that was producing insanely
11788 high timeout values. Now we calculate build timeouts using truncated
11789 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
11790 - Do not close circuits that are under construction when they reach
11791 the circuit build timeout. Instead, leave them building (but do not
11792 use them) for up until the time corresponding to the 95th percentile
11793 on the Pareto CDF or 60 seconds, whichever is greater. This is done
11794 to provide better data for the new Pareto model. This percentile
11795 can be controlled by the consensus.
11798 - Move to the June 2010 Maxmind GeoLite country db (rather than the
11799 June 2009 ip-to-country GeoIP db) for our statistics that count
11800 how many users relays are seeing from each country. Now we have
11801 more accurate data for many African countries.
11802 - Port Tor to build and run correctly on Windows CE systems, using
11803 the wcecompat library. Contributed by Valerio Lupi.
11804 - New "--enable-gcc-hardening" ./configure flag (off by default)
11805 to turn on gcc compile time hardening options. It ensures
11806 that signed ints have defined behavior (-fwrapv), enables
11807 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
11808 with canaries (-fstack-protector-all), turns on ASLR protection if
11809 supported by the kernel (-fPIE, -pie), and adds additional security
11810 related warnings. Verified to work on Mac OS X and Debian Lenny.
11811 - New "--enable-linker-hardening" ./configure flag (off by default)
11812 to turn on ELF specific hardening features (relro, now). This does
11813 not work with Mac OS X or any other non-ELF binary format.
11815 o New directory authorities:
11816 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
11820 - New config option "WarnUnsafeSocks 0" disables the warning that
11821 occurs whenever Tor receives a socks handshake using a version of
11822 the socks protocol that can only provide an IP address (rather
11823 than a hostname). Setups that do DNS locally over Tor are fine,
11824 and we shouldn't spam the logs in that case.
11825 - Convert the HACKING file to asciidoc, and add a few new sections
11826 to it, explaining how we use Git, how we make changelogs, and
11827 what should go in a patch.
11828 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
11829 event, to give information on the current rate of circuit timeouts
11830 over our stored history.
11831 - Add ability to disable circuit build time learning via consensus
11832 parameter and via a LearnCircuitBuildTimeout config option. Also
11833 automatically disable circuit build time calculation if we are
11834 either a AuthoritativeDirectory, or if we fail to write our state
11835 file. Fixes bug 1296.
11836 - More gracefully handle corrupt state files, removing asserts
11837 in favor of saving a backup and resetting state.
11838 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
11842 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
11844 - When a2x fails, mention that the user could disable manpages instead
11845 of trying to fix their asciidoc installation.
11846 - Where available, use Libevent 2.0's periodic timers so that our
11847 once-per-second cleanup code gets called even more closely to
11848 once per second than it would otherwise. Fixes bug 943.
11849 - If you run a bridge that listens on multiple IP addresses, and
11850 some user configures a bridge address that uses a different IP
11851 address than your bridge writes in its router descriptor, and the
11852 user doesn't specify an identity key, their Tor would discard the
11853 descriptor because "it isn't one of our configured bridges", and
11854 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
11855 Bugfix on 0.2.0.3-alpha.
11856 - If OpenSSL fails to make a duplicate of a private or public key, log
11857 an error message and try to exit cleanly. May help with debugging
11858 if bug 1209 ever remanifests.
11859 - Save a couple bytes in memory allocation every time we escape
11860 certain characters in a string. Patch from Florian Zumbiehl.
11861 - Make it explicit that we don't cannibalize one-hop circuits. This
11862 happens in the wild, but doesn't turn out to be a problem because
11863 we fortunately don't use those circuits. Many thanks to outofwords
11864 for the initial analysis and to swissknife who confirmed that
11865 two-hop circuits are actually created.
11866 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
11867 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
11868 - Eliminate a case where a circuit build time warning was displayed
11869 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
11872 Changes in version 0.2.1.26 - 2010-05-02
11873 Tor 0.2.1.26 addresses the recent connection and memory overload
11874 problems we've been seeing on relays, especially relays with their
11875 DirPort open. If your relay has been crashing, or you turned it off
11876 because it used too many resources, give this release a try.
11878 This release also fixes yet another instance of broken OpenSSL libraries
11879 that was causing some relays to drop out of the consensus.
11882 - Teach relays to defend themselves from connection overload. Relays
11883 now close idle circuits early if it looks like they were intended
11884 for directory fetches. Relays are also more aggressive about closing
11885 TLS connections that have no circuits on them. Such circuits are
11886 unlikely to be re-used, and tens of thousands of them were piling
11887 up at the fast relays, causing the relays to run out of sockets
11888 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
11889 their directory fetches over TLS).
11890 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
11891 that claim to be earlier than 0.9.8m, but which have in reality
11892 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
11893 behavior. Possible fix for some cases of bug 1346.
11894 - Directory mirrors were fetching relay descriptors only from v2
11895 directory authorities, rather than v3 authorities like they should.
11896 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
11897 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
11900 - Finally get rid of the deprecated and now harmful notion of "clique
11901 mode", where directory authorities maintain TLS connections to
11905 - In the util/threads test, no longer free the test_mutex before all
11906 worker threads have finished. Bugfix on 0.2.1.6-alpha.
11907 - The master thread could starve the worker threads quite badly on
11908 certain systems, causing them to run only partially in the allowed
11909 window. This resulted in test failures. Now the master thread sleeps
11910 occasionally for a few microseconds while the two worker-threads
11911 compete for the mutex. Bugfix on 0.2.0.1-alpha.
11914 Changes in version 0.2.2.13-alpha - 2010-04-24
11915 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
11916 problems we've been seeing on relays, especially relays with their
11917 DirPort open. If your relay has been crashing, or you turned it off
11918 because it used too many resources, give this release a try.
11921 - Teach relays to defend themselves from connection overload. Relays
11922 now close idle circuits early if it looks like they were intended
11923 for directory fetches. Relays are also more aggressive about closing
11924 TLS connections that have no circuits on them. Such circuits are
11925 unlikely to be re-used, and tens of thousands of them were piling
11926 up at the fast relays, causing the relays to run out of sockets
11927 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
11928 their directory fetches over TLS).
11931 - Finally get rid of the deprecated and now harmful notion of "clique
11932 mode", where directory authorities maintain TLS connections to
11934 - Directory authorities now do an immediate reachability check as soon
11935 as they hear about a new relay. This change should slightly reduce
11936 the time between setting up a relay and getting listed as running
11937 in the consensus. It should also improve the time between setting
11938 up a bridge and seeing use by bridge users.
11939 - Directory authorities no longer launch a TLS connection to every
11940 relay as they startup. Now that we have 2k+ descriptors cached,
11941 the resulting network hiccup is becoming a burden. Besides,
11942 authorities already avoid voting about Running for the first half
11943 hour of their uptime.
11946 Changes in version 0.2.2.12-alpha - 2010-04-20
11947 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
11948 handle and vote on descriptors. It was causing relays to drop out of
11952 - Many relays have been falling out of the consensus lately because
11953 not enough authorities know about their descriptor for them to get
11954 a majority of votes. When we deprecated the v2 directory protocol,
11955 we got rid of the only way that v3 authorities can hear from each
11956 other about other descriptors. Now authorities examine every v3
11957 vote for new descriptors, and fetch them from that authority. Bugfix
11959 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
11960 and a warning in or.h related to bandwidth_weight_rule_t that
11961 prevented clean compile on OS X. Fixes bug 1363; bugfix on
11963 - Fix a segfault on relays when DirReqStatistics is enabled
11964 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
11968 - Demote a confusing TLS warning that relay operators might get when
11969 someone tries to talk to their OrPort. It is neither the operator's
11970 fault nor can they do anything about it. Fixes bug 1364; bugfix
11974 Changes in version 0.2.2.11-alpha - 2010-04-15
11975 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
11976 libraries that was causing some relays to drop out of the consensus.
11979 - Directory mirrors were fetching relay descriptors only from v2
11980 directory authorities, rather than v3 authorities like they should.
11981 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
11982 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
11983 - Fix a parsing error that made every possible value of
11984 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
11985 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
11986 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
11987 about the option without breaking older ones.
11988 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
11989 that claim to be earlier than 0.9.8m, but which have in reality
11990 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
11991 behavior. Possible fix for some cases of bug 1346.
11994 - Experiment with a more aggressive approach to preventing clients
11995 from making one-hop exit streams. Exit relays who want to try it
11996 out can set "RefuseUnknownExits 1" in their torrc, and then look
11997 for "Attempt by %s to open a stream" log messages. Let us know
11999 - Add support for statically linking zlib by specifying
12000 --enable-static-zlib, to go with our support for statically linking
12001 openssl and libevent. Resolves bug 1358.
12004 - Fix a segfault that happens whenever a Tor client that is using
12005 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
12007 - When we cleaned up the contrib/tor-exit-notice.html file, we left
12008 out the first line. Fixes bug 1295.
12009 - When building the manpage from a tarball, we required asciidoc, but
12010 the asciidoc -> roff/html conversion was already done for the
12011 tarball. Make 'make' complain only when we need asciidoc (either
12012 because we're compiling directly from git, or because we altered
12013 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
12014 - When none of the directory authorities vote on any params, Tor
12015 segfaulted when trying to make the consensus from the votes. We
12016 didn't trigger the bug in practice, because authorities do include
12017 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
12020 - In the util/threads test, no longer free the test_mutex before all
12021 worker threads have finished. Bugfix on 0.2.1.6-alpha.
12022 - The master thread could starve the worker threads quite badly on
12023 certain systems, causing them to run only partially in the allowed
12024 window. This resulted in test failures. Now the master thread sleeps
12025 occasionally for a few microseconds while the two worker-threads
12026 compete for the mutex. Bugfix on 0.2.0.1-alpha.
12029 Changes in version 0.2.2.10-alpha - 2010-03-07
12030 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
12031 could prevent relays from guessing their IP address correctly. It also
12032 starts the groundwork for another client-side performance boost, since
12033 currently we're not making efficient use of relays that have both the
12034 Guard flag and the Exit flag.
12037 - Fix a regression from our patch for bug 1244 that caused relays
12038 to guess their IP address incorrectly if they didn't set Address
12039 in their torrc and/or their address fails to resolve. Bugfix on
12040 0.2.2.9-alpha; fixes bug 1269.
12042 o Major features (performance):
12043 - Directory authorities now compute consensus weightings that instruct
12044 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
12045 and no flag. Clients that use these weightings will distribute
12046 network load more evenly across these different relay types. The
12047 weightings are in the consensus so we can change them globally in
12048 the future. Extra thanks to "outofwords" for finding some nasty
12049 security bugs in the first implementation of this feature.
12051 o Minor features (performance):
12052 - Always perform router selections using weighted relay bandwidth,
12053 even if we don't need a high capacity circuit at the time. Non-fast
12054 circuits now only differ from fast ones in that they can use relays
12055 not marked with the Fast flag. This "feature" could turn out to
12056 be a horrible bug; we should investigate more before it goes into
12060 - Allow disabling building of the manpages. Skipping the manpage
12061 speeds up the build considerably.
12063 o Minor bugfixes (on 0.2.2.x):
12064 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
12065 Bugfix on 0.2.2.9-alpha.
12066 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
12067 config option. Bugfix on 0.2.2.7-alpha.
12068 - Ship the asciidoc-helper file in the tarball, so that people can
12069 build from source if they want to, and touching the .1.txt files
12070 doesn't break the build. Bugfix on 0.2.2.9-alpha.
12072 o Minor bugfixes (on 0.2.1.x or earlier):
12073 - Fix a dereference-then-NULL-check sequence when publishing
12074 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
12076 - Fix another dereference-then-NULL-check sequence. Bugfix on
12077 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
12078 - Make sure we treat potentially not NUL-terminated strings correctly.
12079 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
12081 o Code simplifications and refactoring:
12082 - Fix some urls in the exit notice file and make it XHTML1.1 strict
12083 compliant. Based on a patch from Christian Kujau.
12084 - Don't use sed in asciidoc-helper anymore.
12085 - Make the build process fail if asciidoc cannot be found and
12086 building with asciidoc isn't disabled.
12089 Changes in version 0.2.2.9-alpha - 2010-02-22
12090 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
12091 location of a directory authority, and cleans up a bunch of small bugs.
12093 o Directory authority changes:
12094 - Change IP address for dannenberg (v3 directory authority), and
12095 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
12096 service directory authority) from the list.
12099 - Make Tor work again on the latest OS X: when deciding whether to
12100 use strange flags to turn TLS renegotiation on, detect the OpenSSL
12101 version at run-time, not compile time. We need to do this because
12102 Apple doesn't update its dev-tools headers when it updates its
12103 libraries in a security patch.
12104 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
12105 that could happen on 32-bit platforms with 64-bit time_t. Also fix
12106 a memory leak when requesting a hidden service descriptor we've
12107 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
12109 - Authorities could be tricked into giving out the Exit flag to relays
12110 that didn't allow exiting to any ports. This bug could screw
12111 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
12112 1238. Bug discovered by Martin Kowalczyk.
12113 - When freeing a session key, zero it out completely. We only zeroed
12114 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
12115 patched by ekir. Fixes bug 1254.
12118 - Fix static compilation by listing the openssl libraries in the right
12119 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
12120 - Resume handling .exit hostnames in a special way: originally we
12121 stripped the .exit part and used the requested exit relay. In
12122 0.2.2.1-alpha we stopped treating them in any special way, meaning
12123 if you use a .exit address then Tor will pass it on to the exit
12124 relay. Now we reject the .exit stream outright, since that behavior
12125 might be more expected by the user. Found and diagnosed by Scott
12126 Bennett and Downie on or-talk.
12127 - Don't spam the controller with events when we have no file
12128 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
12129 for log messages was already solved from bug 748.)
12130 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
12132 - Make the DNSPort option work with libevent 2.x. Don't alter the
12133 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
12134 - Emit a GUARD DROPPED controller event for a case we missed.
12135 - Make more fields in the controller protocol case-insensitive, since
12136 control-spec.txt said they were.
12137 - Refactor resolve_my_address() to not use gethostbyname() anymore.
12138 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
12139 - Fix a spec conformance issue: the network-status-version token
12140 must be the first token in a v3 consensus or vote. Discovered by
12141 parakeep. Bugfix on 0.2.0.3-alpha.
12143 o Code simplifications and refactoring:
12144 - Generate our manpage and HTML documentation using Asciidoc. This
12145 change should make it easier to maintain the documentation, and
12146 produce nicer HTML.
12147 - Remove the --enable-iphone option. According to reports from Marco
12148 Bonetti, Tor builds fine without any special tweaking on recent
12149 iPhone SDK versions.
12150 - Removed some unnecessary files from the source distribution. The
12151 AUTHORS file has now been merged into the people page on the
12152 website. The roadmaps and design doc can now be found in the
12153 projects directory in svn.
12154 - Enabled various circuit build timeout constants to be controlled
12155 by consensus parameters. Also set better defaults for these
12156 parameters based on experimentation on broadband and simulated
12157 high latency links.
12160 - The 'EXTENDCIRCUIT' control port command can now be used with
12161 a circ id of 0 and no path. This feature will cause Tor to build
12162 a new 'fast' general purpose circuit using its own path selection
12164 - Added a BUILDTIMEOUT_SET controller event to describe changes
12165 to the circuit build timeout.
12166 - Future-proof the controller protocol a bit by ignoring keyword
12167 arguments we do not recognize.
12168 - Expand homedirs passed to tor-checkkey. This should silence a
12169 coverity complaint about passing a user-supplied string into
12170 open() without checking it.
12173 Changes in version 0.2.1.25 - 2010-03-16
12174 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
12175 prevent relays from guessing their IP address correctly. It also fixes
12176 several minor potential security bugs.
12179 - Fix a regression from our patch for bug 1244 that caused relays
12180 to guess their IP address incorrectly if they didn't set Address
12181 in their torrc and/or their address fails to resolve. Bugfix on
12182 0.2.1.23; fixes bug 1269.
12183 - When freeing a session key, zero it out completely. We only zeroed
12184 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
12185 patched by ekir. Fixes bug 1254.
12188 - Fix a dereference-then-NULL-check sequence when publishing
12189 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
12191 - Fix another dereference-then-NULL-check sequence. Bugfix on
12192 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
12193 - Make sure we treat potentially not NUL-terminated strings correctly.
12194 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
12198 Changes in version 0.2.1.24 - 2010-02-21
12199 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
12203 - Work correctly out-of-the-box with even more vendor-patched versions
12204 of OpenSSL. In particular, make it so Debian and OS X don't need
12205 customized patches to run/build.
12208 Changes in version 0.2.1.23 - 2010-02-13
12209 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
12210 again on the latest OS X, and updates the location of a directory
12213 o Major bugfixes (performance):
12214 - We were selecting our guards uniformly at random, and then weighting
12215 which of our guards we'd use uniformly at random. This imbalance
12216 meant that Tor clients were severely limited on throughput (and
12217 probably latency too) by the first hop in their circuit. Now we
12218 select guards weighted by currently advertised bandwidth. We also
12219 automatically discard guards picked using the old algorithm. Fixes
12220 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
12223 - Make Tor work again on the latest OS X: when deciding whether to
12224 use strange flags to turn TLS renegotiation on, detect the OpenSSL
12225 version at run-time, not compile time. We need to do this because
12226 Apple doesn't update its dev-tools headers when it updates its
12227 libraries in a security patch.
12228 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
12229 that could happen on 32-bit platforms with 64-bit time_t. Also fix
12230 a memory leak when requesting a hidden service descriptor we've
12231 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
12234 o Directory authority changes:
12235 - Change IP address for dannenberg (v3 directory authority), and
12236 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
12237 service directory authority) from the list.
12240 - Refactor resolve_my_address() to not use gethostbyname() anymore.
12241 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
12244 - Avoid a mad rush at the beginning of each month when each client
12245 rotates half of its guards. Instead we spread the rotation out
12246 throughout the month, but we still avoid leaving a precise timestamp
12247 in the state file about when we first picked the guard. Improves
12248 over the behavior introduced in 0.1.2.17.
12251 Changes in version 0.2.2.8-alpha - 2010-01-26
12252 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
12253 causing bridge relays to disappear. If you're running a bridge,
12257 - Fix a memory corruption bug on bridges that occured during the
12258 inclusion of stats data in extra-info descriptors. Also fix the
12259 interface for geoip_get_bridge_stats* to prevent similar bugs in
12260 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
12261 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
12264 - Ignore OutboundBindAddress when connecting to localhost.
12265 Connections to localhost need to come _from_ localhost, or else
12266 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
12270 Changes in version 0.2.2.7-alpha - 2010-01-19
12271 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
12272 as laying the groundwork for further relay-side performance fixes. It
12273 also starts cleaning up client behavior with respect to the EntryNodes,
12274 ExitNodes, and StrictNodes config options.
12276 This release also rotates two directory authority keys, due to a
12277 security breach of some of the Torproject servers.
12279 o Directory authority changes:
12280 - Rotate keys (both v3 identity and relay identity) for moria1
12283 o Major features (performance):
12284 - We were selecting our guards uniformly at random, and then weighting
12285 which of our guards we'd use uniformly at random. This imbalance
12286 meant that Tor clients were severely limited on throughput (and
12287 probably latency too) by the first hop in their circuit. Now we
12288 select guards weighted by currently advertised bandwidth. We also
12289 automatically discard guards picked using the old algorithm. Fixes
12290 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
12291 - When choosing which cells to relay first, relays can now favor
12292 circuits that have been quiet recently, to provide lower latency
12293 for low-volume circuits. By default, relays enable or disable this
12294 feature based on a setting in the consensus. You can override
12295 this default by using the new "CircuitPriorityHalflife" config
12296 option. Design and code by Ian Goldberg, Can Tang, and Chris
12298 - Add separate per-conn write limiting to go with the per-conn read
12299 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
12300 but never per-conn write limits.
12301 - New consensus params "bwconnrate" and "bwconnburst" to let us
12302 rate-limit client connections as they enter the network. It's
12303 controlled in the consensus so we can turn it on and off for
12304 experiments. It's starting out off. Based on proposal 163.
12306 o Major features (relay selection options):
12307 - Switch to a StrictNodes config option, rather than the previous
12308 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
12309 "StrictExcludeNodes" option.
12310 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
12311 change during a config reload, mark and discard all our origin
12312 circuits. This fix should address edge cases where we change the
12313 config options and but then choose a circuit that we created before
12315 - If EntryNodes or ExitNodes are set, be more willing to use an
12316 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
12318 - Make EntryNodes config option much more aggressive even when
12319 StrictNodes is not set. Before it would prepend your requested
12320 entrynodes to your list of guard nodes, but feel free to use others
12321 after that. Now it chooses only from your EntryNodes if any of
12322 those are available, and only falls back to others if a) they're
12323 all down and b) StrictNodes is not set.
12324 - Now we refresh your entry guards from EntryNodes at each consensus
12325 fetch -- rather than just at startup and then they slowly rot as
12326 the network changes.
12329 - Stop bridge directory authorities from answering dbg-stability.txt
12330 directory queries, which would let people fetch a list of all
12331 bridge identities they track. Bugfix on 0.2.1.6-alpha.
12334 - Log a notice when we get a new control connection. Now it's easier
12335 for security-conscious users to recognize when a local application
12336 is knocking on their controller door. Suggested by bug 1196.
12337 - New config option "CircuitStreamTimeout" to override our internal
12338 timeout schedule for how many seconds until we detach a stream from
12339 a circuit and try a new circuit. If your network is particularly
12340 slow, you might want to set this to a number like 60.
12341 - New controller command "getinfo config-text". It returns the
12342 contents that Tor would write if you send it a SAVECONF command,
12343 so the controller can write the file to disk itself.
12344 - New options for SafeLogging to allow scrubbing only log messages
12345 generated while acting as a relay.
12346 - Ship the bridges spec file in the tarball too.
12347 - Avoid a mad rush at the beginning of each month when each client
12348 rotates half of its guards. Instead we spread the rotation out
12349 throughout the month, but we still avoid leaving a precise timestamp
12350 in the state file about when we first picked the guard. Improves
12351 over the behavior introduced in 0.1.2.17.
12353 o Minor bugfixes (compiling):
12354 - Fix compilation on OS X 10.3, which has a stub mlockall() but
12355 hides it. Bugfix on 0.2.2.6-alpha.
12356 - Fix compilation on Solaris by removing support for the
12357 DisableAllSwap config option. Solaris doesn't have an rlimit for
12358 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
12361 o Minor bugfixes (crashes):
12362 - Do not segfault when writing buffer stats when we haven't observed
12363 a single circuit to report about. Found by Fabian Lanze. Bugfix on
12365 - If we're in the pathological case where there's no exit bandwidth
12366 but there is non-exit bandwidth, or no guard bandwidth but there
12367 is non-guard bandwidth, don't crash during path selection. Bugfix
12369 - Fix an impossible-to-actually-trigger buffer overflow in relay
12370 descriptor generation. Bugfix on 0.1.0.15.
12372 o Minor bugfixes (privacy):
12373 - Fix an instance where a Tor directory mirror might accidentally
12374 log the IP address of a misbehaving Tor client. Bugfix on
12376 - Don't list Windows capabilities in relay descriptors. We never made
12377 use of them, and maybe it's a bad idea to publish them. Bugfix
12380 o Minor bugfixes (other):
12381 - Resolve an edge case in path weighting that could make us misweight
12382 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
12383 - Fix statistics on client numbers by country as seen by bridges that
12384 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
12385 intervals instead of variable 12-to-48-hour intervals.
12386 - After we free an internal connection structure, overwrite it
12387 with a different memory value than we use for overwriting a freed
12388 internal circuit structure. Should help with debugging. Suggested
12390 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
12393 o Removed features:
12394 - Remove the HSAuthorityRecordStats option that version 0 hidden
12395 service authorities could have used to track statistics of overall
12396 hidden service usage.
12399 Changes in version 0.2.1.22 - 2010-01-19
12400 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
12401 authorities -- it would tell you its whole history of bridge descriptors
12402 if you make the right directory request. This stable update also
12403 rotates two of the seven v3 directory authority keys and locations.
12405 o Directory authority changes:
12406 - Rotate keys (both v3 identity and relay identity) for moria1
12410 - Stop bridge directory authorities from answering dbg-stability.txt
12411 directory queries, which would let people fetch a list of all
12412 bridge identities they track. Bugfix on 0.2.1.6-alpha.
12415 Changes in version 0.2.1.21 - 2009-12-21
12416 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
12417 library. If you use Tor on Linux / Unix and you're getting SSL
12418 renegotiation errors, upgrading should help. We also recommend an
12419 upgrade if you're an exit relay.
12422 - Work around a security feature in OpenSSL 0.9.8l that prevents our
12423 handshake from working unless we explicitly tell OpenSSL that we
12424 are using SSL renegotiation safely. We are, of course, but OpenSSL
12425 0.9.8l won't work unless we say we are.
12426 - Avoid crashing if the client is trying to upload many bytes and the
12427 circuit gets torn down at the same time, or if the flip side
12428 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
12431 - Do not refuse to learn about authority certs and v2 networkstatus
12432 documents that are older than the latest consensus. This bug might
12433 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
12434 Spotted and fixed by xmux.
12435 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
12436 trigger platform-specific option misparsing case found by Coverity
12438 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
12439 trigger assert. Fixes bug 1173.
12442 Changes in version 0.2.2.6-alpha - 2009-11-19
12443 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
12444 support for the new lower-footprint "microdescriptor" directory design,
12445 future-proofing our consensus format against new hash functions or
12446 other changes, and an Android port. It also makes Tor compatible with
12447 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
12450 - Directory authorities can now create, vote on, and serve multiple
12451 parallel formats of directory data as part of their voting process.
12452 Partially implements Proposal 162: "Publish the consensus in
12454 - Directory authorities can now agree on and publish small summaries
12455 of router information that clients can use in place of regular
12456 server descriptors. This transition will eventually allow clients
12457 to use far less bandwidth for downloading information about the
12458 network. Begins the implementation of Proposal 158: "Clients
12459 download consensus + microdescriptors".
12460 - The directory voting system is now extensible to use multiple hash
12461 algorithms for signatures and resource selection. Newer formats
12462 are signed with SHA256, with a possibility for moving to a better
12463 hash algorithm in the future.
12464 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
12465 current and future memory pages via mlockall(). On supported
12466 platforms (modern Linux and probably BSD but not Windows or OS X),
12467 this should effectively disable any and all attempts to page out
12468 memory. This option requires that you start your Tor as root --
12469 if you use DisableAllSwap, please consider using the User option
12470 to properly reduce the privileges of your Tor.
12471 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
12472 to help Tor build correctly for Android phones.
12475 - Work around a security feature in OpenSSL 0.9.8l that prevents our
12476 handshake from working unless we explicitly tell OpenSSL that we
12477 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
12478 won't work unless we say we are.
12481 - Fix a crash bug when trying to initialize the evdns module in
12482 Libevent 2. Bugfix on 0.2.1.16-rc.
12483 - Stop logging at severity 'warn' when some other Tor client tries
12484 to establish a circuit with us using weak DH keys. It's a protocol
12485 violation, but that doesn't mean ordinary users need to hear about
12486 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
12487 - Do not refuse to learn about authority certs and v2 networkstatus
12488 documents that are older than the latest consensus. This bug might
12489 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
12490 Spotted and fixed by xmux.
12491 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
12492 - If all authorities restart at once right before a consensus vote,
12493 nobody will vote about "Running", and clients will get a consensus
12494 with no usable relays. Instead, authorities refuse to build a
12495 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
12496 - If your relay can't keep up with the number of incoming create
12497 cells, it would log one warning per failure into your logs. Limit
12498 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
12499 - Bridges now use "reject *:*" as their default exit policy. Bugfix
12500 on 0.2.0.3-alpha; fixes bug 1113.
12501 - Fix a memory leak on directory authorities during voting that was
12502 introduced in 0.2.2.1-alpha. Found via valgrind.
12505 Changes in version 0.2.1.20 - 2009-10-15
12506 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
12507 services at once, prepares for more performance improvements, and
12508 fixes a bunch of smaller bugs.
12510 The Windows and OS X bundles also include a more recent Vidalia,
12511 and switch from Privoxy to Polipo.
12513 The OS X installers are now drag and drop. It's best to un-install
12514 Tor/Vidalia and then install this new bundle, rather than upgrade. If
12515 you want to upgrade, you'll need to update the paths for Tor and Polipo
12516 in the Vidalia Settings window.
12519 - Send circuit or stream sendme cells when our window has decreased
12520 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
12521 by Karsten when testing the "reduce circuit window" performance
12522 patch. Bugfix on the 54th commit on Tor -- from July 2002,
12523 before the release of Tor 0.0.0. This is the new winner of the
12525 - Fix a remotely triggerable memory leak when a consensus document
12526 contains more than one signature from the same voter. Bugfix on
12528 - Avoid segfault in rare cases when finishing an introduction circuit
12529 as a client and finding out that we don't have an introduction key
12530 for it. Fixes bug 1073. Reported by Aaron Swartz.
12533 - Tor now reads the "circwindow" parameter out of the consensus,
12534 and uses that value for its circuit package window rather than the
12535 default of 1000 cells. Begins the implementation of proposal 168.
12537 o New directory authorities:
12538 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
12540 - Move moria1 and tonga to alternate IP addresses.
12543 - Fix a signed/unsigned compile warning in 0.2.1.19.
12544 - Fix possible segmentation fault on directory authorities. Bugfix on
12546 - Fix an extremely rare infinite recursion bug that could occur if
12547 we tried to log a message after shutting down the log subsystem.
12548 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
12549 - Fix an obscure bug where hidden services on 64-bit big-endian
12550 systems might mis-read the timestamp in v3 introduce cells, and
12551 refuse to connect back to the client. Discovered by "rotor".
12552 Bugfix on 0.2.1.6-alpha.
12553 - We were triggering a CLOCK_SKEW controller status event whenever
12554 we connect via the v2 connection protocol to any relay that has
12555 a wrong clock. Instead, we should only inform the controller when
12556 it's a trusted authority that claims our clock is wrong. Bugfix
12557 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
12558 - We were telling the controller about CHECKING_REACHABILITY and
12559 REACHABILITY_FAILED status events whenever we launch a testing
12560 circuit or notice that one has failed. Instead, only tell the
12561 controller when we want to inform the user of overall success or
12562 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
12564 - Don't warn when we're using a circuit that ends with a node
12565 excluded in ExcludeExitNodes, but the circuit is not used to access
12566 the outside world. This should help fix bug 1090. Bugfix on
12568 - Work around a small memory leak in some versions of OpenSSL that
12569 stopped the memory used by the hostname TLS extension from being
12573 - Add a "getinfo status/accepted-server-descriptor" controller
12574 command, which is the recommended way for controllers to learn
12575 whether our server descriptor has been successfully received by at
12576 least on directory authority. Un-recommend good-server-descriptor
12577 getinfo and status events until we have a better design for them.
12580 Changes in version 0.2.2.5-alpha - 2009-10-11
12581 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
12584 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
12586 o Directory authorities:
12587 - Temporarily (just for this release) move dizum to an alternate
12591 Changes in version 0.2.2.4-alpha - 2009-10-10
12592 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
12593 introduces a new unit test framework, shifts directry authority
12594 addresses around to reduce the impact from recent blocking events,
12595 and fixes a few smaller bugs.
12598 - Fix several more asserts in the circuit_build_times code, for
12599 example one that causes Tor to fail to start once we have
12600 accumulated 5000 build times in the state file. Bugfixes on
12601 0.2.2.2-alpha; fixes bug 1108.
12603 o New directory authorities:
12604 - Move moria1 and Tonga to alternate IP addresses.
12607 - Log SSL state transitions at debug level during handshake, and
12608 include SSL states in error messages. This may help debug future
12609 SSL handshake issues.
12610 - Add a new "Handshake" log domain for activities that happen
12611 during the TLS handshake.
12612 - Revert to the "June 3 2009" ip-to-country file. The September one
12613 seems to have removed most US IP addresses.
12614 - Directory authorities now reject Tor relays with versions less than
12615 0.1.2.14. This step cuts out four relays from the current network,
12616 none of which are very big.
12619 - Fix a couple of smaller issues with gathering statistics. Bugfixes
12621 - Fix two memory leaks in the error case of
12622 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
12623 - Don't count one-hop circuits when we're estimating how long it
12624 takes circuits to build on average. Otherwise we'll set our circuit
12625 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
12626 - Directory authorities no longer change their opinion of, or vote on,
12627 whether a router is Running, unless they have themselves been
12628 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
12631 o Code simplifications and refactoring:
12632 - Revise our unit tests to use the "tinytest" framework, so we
12633 can run tests in their own processes, have smarter setup/teardown
12634 code, and so on. The unit test code has moved to its own
12635 subdirectory, and has been split into multiple modules.
12638 Changes in version 0.2.2.3-alpha - 2009-09-23
12639 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
12642 - Fix an overzealous assert in our new circuit build timeout code.
12643 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
12646 - If the networkstatus consensus tells us that we should use a
12647 negative circuit package window, ignore it. Otherwise we'll
12648 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
12651 Changes in version 0.2.2.2-alpha - 2009-09-21
12652 Tor 0.2.2.2-alpha introduces our latest performance improvement for
12653 clients: Tor tracks the average time it takes to build a circuit, and
12654 avoids using circuits that take too long to build. For fast connections,
12655 this feature can cut your expected latency in half. For slow or flaky
12656 connections, it could ruin your Tor experience. Let us know if it does!
12659 - Tor now tracks how long it takes to build client-side circuits
12660 over time, and adapts its timeout to local network performance.
12661 Since a circuit that takes a long time to build will also provide
12662 bad performance, we get significant latency improvements by
12663 discarding the slowest 20% of circuits. Specifically, Tor creates
12664 circuits more aggressively than usual until it has enough data
12665 points for a good timeout estimate. Implements proposal 151.
12666 We are especially looking for reports (good and bad) from users with
12667 both EDGE and broadband connections that can move from broadband
12668 to EDGE and find out if the build-time data in the .tor/state gets
12669 reset without loss of Tor usability. You should also see a notice
12670 log message telling you that Tor has reset its timeout.
12671 - Directory authorities can now vote on arbitary integer values as
12672 part of the consensus process. This is designed to help set
12673 network-wide parameters. Implements proposal 167.
12674 - Tor now reads the "circwindow" parameter out of the consensus,
12675 and uses that value for its circuit package window rather than the
12676 default of 1000 cells. Begins the implementation of proposal 168.
12679 - Fix a remotely triggerable memory leak when a consensus document
12680 contains more than one signature from the same voter. Bugfix on
12684 - Fix an extremely rare infinite recursion bug that could occur if
12685 we tried to log a message after shutting down the log subsystem.
12686 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
12687 - Fix parsing for memory or time units given without a space between
12688 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
12689 - A networkstatus vote must contain exactly one signature. Spec
12690 conformance issue. Bugfix on 0.2.0.3-alpha.
12691 - Fix an obscure bug where hidden services on 64-bit big-endian
12692 systems might mis-read the timestamp in v3 introduce cells, and
12693 refuse to connect back to the client. Discovered by "rotor".
12694 Bugfix on 0.2.1.6-alpha.
12695 - We were triggering a CLOCK_SKEW controller status event whenever
12696 we connect via the v2 connection protocol to any relay that has
12697 a wrong clock. Instead, we should only inform the controller when
12698 it's a trusted authority that claims our clock is wrong. Bugfix
12699 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
12700 - We were telling the controller about CHECKING_REACHABILITY and
12701 REACHABILITY_FAILED status events whenever we launch a testing
12702 circuit or notice that one has failed. Instead, only tell the
12703 controller when we want to inform the user of overall success or
12704 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
12706 - Don't warn when we're using a circuit that ends with a node
12707 excluded in ExcludeExitNodes, but the circuit is not used to access
12708 the outside world. This should help fix bug 1090, but more problems
12709 remain. Bugfix on 0.2.1.6-alpha.
12710 - Work around a small memory leak in some versions of OpenSSL that
12711 stopped the memory used by the hostname TLS extension from being
12713 - Make our 'torify' script more portable; if we have only one of
12714 'torsocks' or 'tsocks' installed, don't complain to the user;
12715 and explain our warning about tsocks better.
12718 - Add a "getinfo status/accepted-server-descriptor" controller
12719 command, which is the recommended way for controllers to learn
12720 whether our server descriptor has been successfully received by at
12721 least on directory authority. Un-recommend good-server-descriptor
12722 getinfo and status events until we have a better design for them.
12723 - Update to the "September 4 2009" ip-to-country file.
12726 Changes in version 0.2.2.1-alpha - 2009-08-26
12727 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
12728 Tor clients to bootstrap on networks where only port 80 is reachable,
12729 makes it more straightforward to support hardware crypto accelerators,
12730 and starts the groundwork for gathering stats safely at relays.
12733 - Start the process of disabling ".exit" address notation, since it
12734 can be used for a variety of esoteric application-level attacks
12735 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
12738 o New directory authorities:
12739 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
12743 - New AccelName and AccelDir options add support for dynamic OpenSSL
12744 hardware crypto acceleration engines.
12745 - Tor now supports tunneling all of its outgoing connections over
12746 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
12747 configuration options. Code by Christopher Davis.
12750 - Send circuit or stream sendme cells when our window has decreased
12751 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
12752 by Karsten when testing the "reduce circuit window" performance
12753 patch. Bugfix on the 54th commit on Tor -- from July 2002,
12754 before the release of Tor 0.0.0. This is the new winner of the
12757 o New options for gathering stats safely:
12758 - Directory mirrors that set "DirReqStatistics 1" write statistics
12759 about directory requests to disk every 24 hours. As compared to the
12760 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
12761 1) stats are written to disk exactly every 24 hours; 2) estimated
12762 shares of v2 and v3 requests are determined as mean values, not at
12763 the end of a measurement period; 3) unresolved requests are listed
12764 with country code '??'; 4) directories also measure download times.
12765 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
12766 number of exit streams and transferred bytes per port to disk every
12768 - Relays that set "CellStatistics 1" write statistics on how long
12769 cells spend in their circuit queues to disk every 24 hours.
12770 - Entry nodes that set "EntryStatistics 1" write statistics on the
12771 rough number and origins of connecting clients to disk every 24
12773 - Relays that write any of the above statistics to disk and set
12774 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
12775 their extra-info documents.
12778 - New --digests command-line switch to output the digests of the
12779 source files Tor was built with.
12780 - The "torify" script now uses torsocks where available.
12781 - The memarea code now uses a sentinel value at the end of each area
12782 to make sure nothing writes beyond the end of an area. This might
12783 help debug some conceivable causes of bug 930.
12784 - Time and memory units in the configuration file can now be set to
12785 fractional units. For example, "2.5 GB" is now a valid value for
12787 - Certain Tor clients (such as those behind check.torproject.org) may
12788 want to fetch the consensus in an extra early manner. To enable this
12789 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
12790 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
12791 as only certain clients who must have this information sooner should
12793 - Instead of adding the svn revision to the Tor version string, report
12794 the git commit (when we're building from a git checkout).
12797 - If any of the v3 certs we download are unparseable, we should
12798 actually notice the failure so we don't retry indefinitely. Bugfix
12799 on 0.2.0.x; reported by "rotator".
12800 - If the cached cert file is unparseable, warn but don't exit.
12801 - Fix possible segmentation fault on directory authorities. Bugfix on
12803 - When Tor fails to parse a descriptor of any kind, dump it to disk.
12804 Might help diagnosing bug 1051.
12806 o Deprecated and removed features:
12807 - The controller no longer accepts the old obsolete "addr-mappings/"
12808 or "unregistered-servers-" GETINFO values.
12809 - Hidden services no longer publish version 0 descriptors, and clients
12810 do not request or use version 0 descriptors. However, the old hidden
12811 service authorities still accept and serve version 0 descriptors
12812 when contacted by older hidden services/clients.
12813 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
12814 always on; using them is necessary for correct forward-compatible
12816 - Remove support for .noconnect style addresses. Nobody was using
12817 them, and they provided another avenue for detecting Tor users
12818 via application-level web tricks.
12820 o Packaging changes:
12821 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
12822 installer bundles. See
12823 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
12824 for details of what's new in Vidalia 0.2.3.
12825 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
12826 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
12827 configuration file, rather than the old Privoxy.
12828 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
12829 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
12830 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
12831 better compatibility with OS X 10.6, aka Snow Leopard.
12832 - OS X Vidalia Bundle: The multi-package installer is now replaced
12833 by a simple drag and drop to the /Applications folder. This change
12834 occurred with the upgrade to Vidalia 0.2.3.
12837 Changes in version 0.2.1.19 - 2009-07-28
12838 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
12839 services on Tor 0.2.1.3-alpha through 0.2.1.18.
12842 - Make accessing hidden services on 0.2.1.x work right again.
12843 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
12844 part of patch provided by "optimist".
12847 - When a relay/bridge is writing out its identity key fingerprint to
12848 the "fingerprint" file and to its logs, write it without spaces. Now
12849 it will look like the fingerprints in our bridges documentation,
12850 and confuse fewer users.
12853 - Relays no longer publish a new server descriptor if they change
12854 their MaxAdvertisedBandwidth config option but it doesn't end up
12855 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
12856 fixes bug 1026. Patch from Sebastian.
12857 - Avoid leaking memory every time we get a create cell but we have
12858 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
12859 fixes bug 1034. Reported by BarkerJr.
12862 Changes in version 0.2.1.18 - 2009-07-24
12863 Tor 0.2.1.18 lays the foundations for performance improvements,
12864 adds status events to help users diagnose bootstrap problems, adds
12865 optional authentication/authorization for hidden services, fixes a
12866 variety of potential anonymity problems, and includes a huge pile of
12867 other features and bug fixes.
12870 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
12873 Changes in version 0.2.1.17-rc - 2009-07-07
12874 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
12875 candidate for the 0.2.1.x series. It lays the groundwork for further
12876 client performance improvements, and also fixes a big bug with directory
12877 authorities that were causing them to assign Guard and Stable flags
12880 The Windows bundles also finally include the geoip database that we
12881 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
12882 should actually install Torbutton rather than giving you a cryptic
12883 failure message (oops).
12886 - Clients now use the bandwidth values in the consensus, rather than
12887 the bandwidth values in each relay descriptor. This approach opens
12888 the door to more accurate bandwidth estimates once the directory
12889 authorities start doing active measurements. Implements more of
12893 - When Tor clients restart after 1-5 days, they discard all their
12894 cached descriptors as too old, but they still use the cached
12895 consensus document. This approach is good for robustness, but
12896 bad for performance: since they don't know any bandwidths, they
12897 end up choosing at random rather than weighting their choice by
12898 speed. Fixed by the above feature of putting bandwidths in the
12899 consensus. Bugfix on 0.2.0.x.
12900 - Directory authorities were neglecting to mark relays down in their
12901 internal histories if the relays fall off the routerlist without
12902 ever being found unreachable. So there were relays in the histories
12903 that haven't been seen for eight months, and are listed as being
12904 up for eight months. This wreaked havoc on the "median wfu"
12905 and "median mtbf" calculations, in turn making Guard and Stable
12906 flags very wrong, hurting network performance. Fixes bugs 696 and
12907 969. Bugfix on 0.2.0.6-alpha.
12910 - Serve the DirPortFrontPage page even when we have been approaching
12911 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
12912 - The control port would close the connection before flushing long
12913 replies, such as the network consensus, if a QUIT command was issued
12914 before the reply had completed. Now, the control port flushes all
12915 pending replies before closing the connection. Also fixed a spurious
12916 warning when a QUIT command is issued after a malformed or rejected
12917 AUTHENTICATE command, but before the connection was closed. Patch
12918 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
12919 - When we can't find an intro key for a v2 hidden service descriptor,
12920 fall back to the v0 hidden service descriptor and log a bug message.
12921 Workaround for bug 1024.
12922 - Fix a log message that did not respect the SafeLogging option.
12926 - If we're a relay and we change our IP address, be more verbose
12927 about the reason that made us change. Should help track down
12928 further bugs for relays on dynamic IP addresses.
12931 Changes in version 0.2.0.35 - 2009-06-24
12933 - Avoid crashing in the presence of certain malformed descriptors.
12934 Found by lark, and by automated fuzzing.
12935 - Fix an edge case where a malicious exit relay could convince a
12936 controller that the client's DNS question resolves to an internal IP
12937 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
12940 - Finally fix the bug where dynamic-IP relays disappear when their
12941 IP address changes: directory mirrors were mistakenly telling
12942 them their old address if they asked via begin_dir, so they
12943 never got an accurate answer about their new address, so they
12944 just vanished after a day. For belt-and-suspenders, relays that
12945 don't set Address in their config now avoid using begin_dir for
12946 all direct connections. Should fix bugs 827, 883, and 900.
12947 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
12948 that would occur on some exit nodes when DNS failures and timeouts
12949 occurred in certain patterns. Fix for bug 957.
12952 - When starting with a cache over a few days old, do not leak
12953 memory for the obsolete router descriptors in it. Bugfix on
12954 0.2.0.33; fixes bug 672.
12955 - Hidden service clients didn't use a cached service descriptor that
12956 was older than 15 minutes, but wouldn't fetch a new one either,
12957 because there was already one in the cache. Now, fetch a v2
12958 descriptor unless the same descriptor was added to the cache within
12959 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
12962 Changes in version 0.2.1.16-rc - 2009-06-20
12963 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
12964 a bunch of minor bugs.
12967 - Fix an edge case where a malicious exit relay could convince a
12968 controller that the client's DNS question resolves to an internal IP
12969 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
12971 o Major performance improvements (on 0.2.0.x):
12972 - Disable and refactor some debugging checks that forced a linear scan
12973 over the whole server-side DNS cache. These accounted for over 50%
12974 of CPU time on a relatively busy exit node's gprof profile. Found
12976 - Disable some debugging checks that appeared in exit node profile
12980 - Update to the "June 3 2009" ip-to-country file.
12981 - Do not have tor-resolve automatically refuse all .onion addresses;
12982 if AutomapHostsOnResolve is set in your torrc, this will work fine.
12984 o Minor bugfixes (on 0.2.0.x):
12985 - Log correct error messages for DNS-related network errors on
12987 - Fix a race condition that could cause crashes or memory corruption
12988 when running as a server with a controller listening for log
12990 - Avoid crashing when we have a policy specified in a DirPolicy or
12991 SocksPolicy or ReachableAddresses option with ports set on it,
12992 and we re-load the policy. May fix bug 996.
12993 - Hidden service clients didn't use a cached service descriptor that
12994 was older than 15 minutes, but wouldn't fetch a new one either,
12995 because there was already one in the cache. Now, fetch a v2
12996 descriptor unless the same descriptor was added to the cache within
12997 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
12999 o Minor bugfixes (on 0.2.1.x):
13000 - Don't warn users about low port and hibernation mix when they
13001 provide a *ListenAddress directive to fix that. Bugfix on
13003 - When switching back and forth between bridge mode, do not start
13004 gathering GeoIP data until two hours have passed.
13005 - Do not complain that the user has requested an excluded node as
13006 an exit when the node is not really an exit. This could happen
13007 because the circuit was for testing, or an introduction point.
13011 Changes in version 0.2.1.15-rc - 2009-05-25
13012 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
13013 series. It fixes a major bug on fast exit relays, as well as a variety
13014 of more minor bugs.
13016 o Major bugfixes (on 0.2.0.x):
13017 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
13018 that would occur on some exit nodes when DNS failures and timeouts
13019 occurred in certain patterns. Fix for bug 957.
13021 o Minor bugfixes (on 0.2.0.x):
13022 - Actually return -1 in the error case for read_bandwidth_usage().
13023 Harmless bug, since we currently don't care about the return value
13024 anywhere. Bugfix on 0.2.0.9-alpha.
13025 - Provide a more useful log message if bug 977 (related to buffer
13026 freelists) ever reappears, and do not crash right away.
13027 - Fix an assertion failure on 64-bit platforms when we allocated
13028 memory right up to the end of a memarea, then realigned the memory
13029 one step beyond the end. Fixes a possible cause of bug 930.
13030 - Protect the count of open sockets with a mutex, so we can't
13031 corrupt it when two threads are closing or opening sockets at once.
13032 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
13033 - Don't allow a bridge to publish its router descriptor to a
13034 non-bridge directory authority. Fixes part of bug 932.
13035 - When we change to or from being a bridge, reset our counts of
13036 client usage by country. Fixes bug 932.
13037 - Fix a bug that made stream bandwidth get misreported to the
13039 - Stop using malloc_usable_size() to use more area than we had
13040 actually allocated: it was safe, but made valgrind really unhappy.
13041 - Fix a memory leak when v3 directory authorities load their keys
13042 and cert from disk. Bugfix on 0.2.0.1-alpha.
13044 o Minor bugfixes (on 0.2.1.x):
13045 - Fix use of freed memory when deciding to mark a non-addable
13046 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
13049 Changes in version 0.2.1.14-rc - 2009-04-12
13050 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
13051 series. It begins fixing some major performance problems, and also
13052 finally addresses the bug that was causing relays on dynamic IP
13053 addresses to fall out of the directory.
13056 - Clients replace entry guards that were chosen more than a few months
13057 ago. This change should significantly improve client performance,
13058 especially once more people upgrade, since relays that have been
13059 a guard for a long time are currently overloaded.
13061 o Major bugfixes (on 0.2.0):
13062 - Finally fix the bug where dynamic-IP relays disappear when their
13063 IP address changes: directory mirrors were mistakenly telling
13064 them their old address if they asked via begin_dir, so they
13065 never got an accurate answer about their new address, so they
13066 just vanished after a day. For belt-and-suspenders, relays that
13067 don't set Address in their config now avoid using begin_dir for
13068 all direct connections. Should fix bugs 827, 883, and 900.
13069 - Relays were falling out of the networkstatus consensus for
13070 part of a day if they changed their local config but the
13071 authorities discarded their new descriptor as "not sufficiently
13072 different". Now directory authorities accept a descriptor as changed
13073 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
13074 patch by Sebastian.
13075 - Avoid crashing in the presence of certain malformed descriptors.
13076 Found by lark, and by automated fuzzing.
13079 - When generating circuit events with verbose nicknames for
13080 controllers, try harder to look up nicknames for routers on a
13081 circuit. (Previously, we would look in the router descriptors we had
13082 for nicknames, but not in the consensus.) Partial fix for bug 941.
13083 - If the bridge config line doesn't specify a port, assume 443.
13084 This makes bridge lines a bit smaller and easier for users to
13086 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
13087 bytes (aka 20KB/s), to match our documentation. Also update
13088 directory authorities so they always assign the Fast flag to relays
13089 with 20KB/s of capacity. Now people running relays won't suddenly
13090 find themselves not seeing any use, if the network gets faster
13092 - Update to the "April 3 2009" ip-to-country file.
13095 - Avoid trying to print raw memory to the logs when we decide to
13096 give up on downloading a given relay descriptor. Bugfix on
13098 - In tor-resolve, when the Tor client to use is specified by
13099 <hostname>:<port>, actually use the specified port rather than
13100 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
13101 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
13102 - When starting with a cache over a few days old, do not leak
13103 memory for the obsolete router descriptors in it. Bugfix on
13105 - Avoid double-free on list of successfully uploaded hidden
13106 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
13107 - Change memarea_strndup() implementation to work even when
13108 duplicating a string at the end of a page. This bug was
13109 harmless for now, but could have meant crashes later. Fix by
13110 lark. Bugfix on 0.2.1.1-alpha.
13111 - Limit uploaded directory documents to be 16M rather than 500K.
13112 The directory authorities were refusing v3 consensus votes from
13113 other authorities, since the votes are now 504K. Fixes bug 959;
13114 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
13115 - Directory authorities should never send a 503 "busy" response to
13116 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
13120 Changes in version 0.2.1.13-alpha - 2009-03-09
13121 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
13122 cleanups. We're finally getting close to a release candidate.
13125 - Correctly update the list of which countries we exclude as
13126 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
13127 lark. Bugfix on 0.2.1.6-alpha.
13129 o Minor bugfixes (on 0.2.0.x and earlier):
13130 - Automatically detect MacOSX versions earlier than 10.4.0, and
13131 disable kqueue from inside Tor when running with these versions.
13132 We previously did this from the startup script, but that was no
13133 help to people who didn't use the startup script. Resolves bug 863.
13134 - When we had picked an exit node for a connection, but marked it as
13135 "optional", and it turned out we had no onion key for the exit,
13136 stop wanting that exit and try again. This situation may not
13137 be possible now, but will probably become feasible with proposal
13138 158. Spotted by rovv. Fixes another case of bug 752.
13139 - Clients no longer cache certificates for authorities they do not
13140 recognize. Bugfix on 0.2.0.9-alpha.
13141 - When we can't transmit a DNS request due to a network error, retry
13142 it after a while, and eventually transmit a failing response to
13143 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
13144 - If the controller claimed responsibility for a stream, but that
13145 stream never finished making its connection, it would live
13146 forever in circuit_wait state. Now we close it after SocksTimeout
13147 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
13148 - Drop begin cells to a hidden service if they come from the middle
13149 of a circuit. Patch from lark.
13150 - When we erroneously receive two EXTEND cells for the same circuit
13151 ID on the same connection, drop the second. Patch from lark.
13152 - Fix a crash that occurs on exit nodes when a nameserver request
13153 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
13154 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
13156 - Do not assume that a stack-allocated character array will be
13157 64-bit aligned on platforms that demand that uint64_t access is
13158 aligned. Possible fix for bug 604.
13159 - Parse dates and IPv4 addresses in a locale- and libc-independent
13160 manner, to avoid platform-dependent behavior on malformed input.
13161 - Build correctly when configured to build outside the main source
13162 path. Patch from Michael Gold.
13163 - We were already rejecting relay begin cells with destination port
13164 of 0. Now also reject extend cells with destination port or address
13165 of 0. Suggested by lark.
13167 o Minor bugfixes (on 0.2.1.x):
13168 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
13169 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
13170 - If we're an exit node, scrub the IP address to which we are exiting
13171 in the logs. Bugfix on 0.2.1.8-alpha.
13174 - On Linux, use the prctl call to re-enable core dumps when the user
13176 - New controller event NEWCONSENSUS that lists the networkstatus
13177 lines for every recommended relay. Now controllers like Torflow
13178 can keep up-to-date on which relays they should be using.
13179 - Update to the "February 26 2009" ip-to-country file.
13182 Changes in version 0.2.0.34 - 2009-02-08
13183 Tor 0.2.0.34 features several more security-related fixes. You should
13184 upgrade, especially if you run an exit relay (remote crash) or a
13185 directory authority (remote infinite loop), or you're on an older
13186 (pre-XP) or not-recently-patched Windows (remote exploit).
13188 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
13189 have many known flaws, and nobody should be using them. You should
13190 upgrade. If you're using a Linux or BSD and its packages are obsolete,
13191 stop using those packages and upgrade anyway.
13194 - Fix an infinite-loop bug on handling corrupt votes under certain
13195 circumstances. Bugfix on 0.2.0.8-alpha.
13196 - Fix a temporary DoS vulnerability that could be performed by
13197 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
13198 - Avoid a potential crash on exit nodes when processing malformed
13199 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
13200 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
13201 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
13204 - Fix compilation on systems where time_t is a 64-bit integer.
13205 Patch from Matthias Drochner.
13206 - Don't consider expiring already-closed client connections. Fixes
13207 bug 893. Bugfix on 0.0.2pre20.
13210 Changes in version 0.2.1.12-alpha - 2009-02-08
13211 Tor 0.2.1.12-alpha features several more security-related fixes. You
13212 should upgrade, especially if you run an exit relay (remote crash) or
13213 a directory authority (remote infinite loop), or you're on an older
13214 (pre-XP) or not-recently-patched Windows (remote exploit). It also
13215 includes a big pile of minor bugfixes and cleanups.
13218 - Fix an infinite-loop bug on handling corrupt votes under certain
13219 circumstances. Bugfix on 0.2.0.8-alpha.
13220 - Fix a temporary DoS vulnerability that could be performed by
13221 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
13222 - Avoid a potential crash on exit nodes when processing malformed
13223 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
13226 - Let controllers actually ask for the "clients_seen" event for
13227 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
13228 reported by Matt Edman.
13229 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
13231 - Fix a bug in address parsing that was preventing bridges or hidden
13232 service targets from being at IPv6 addresses.
13233 - Solve a bug that kept hardware crypto acceleration from getting
13234 enabled when accounting was turned on. Fixes bug 907. Bugfix on
13236 - Remove a bash-ism from configure.in to build properly on non-Linux
13237 platforms. Bugfix on 0.2.1.1-alpha.
13238 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
13239 headers. Bugfix on 0.2.0.10-alpha.
13240 - Don't consider expiring already-closed client connections. Fixes
13241 bug 893. Bugfix on 0.0.2pre20.
13242 - Fix another interesting corner-case of bug 891 spotted by rovv:
13243 Previously, if two hosts had different amounts of clock drift, and
13244 one of them created a new connection with just the wrong timing,
13245 the other might decide to deprecate the new connection erroneously.
13246 Bugfix on 0.1.1.13-alpha.
13247 - Resolve a very rare crash bug that could occur when the user forced
13248 a nameserver reconfiguration during the middle of a nameserver
13249 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
13250 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
13251 Bugfix on 0.2.1.7-alpha.
13252 - If we're using bridges and our network goes away, be more willing
13253 to forgive our bridges and try again when we get an application
13254 request. Bugfix on 0.2.0.x.
13257 - Support platforms where time_t is 64 bits long. (Congratulations,
13258 NetBSD!) Patch from Matthias Drochner.
13259 - Add a 'getinfo status/clients-seen' controller command, in case
13260 controllers want to hear clients_seen events but connect late.
13263 - Disable GCC's strict alias optimization by default, to avoid the
13264 likelihood of its introducing subtle bugs whenever our code violates
13265 the letter of C99's alias rules.
13268 Changes in version 0.2.0.33 - 2009-01-21
13269 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
13270 useful to users. It also finally fixes a bug where a relay or client
13271 that's been off for many days would take a long time to bootstrap.
13273 This update also fixes an important security-related bug reported by
13274 Ilja van Sprundel. You should upgrade. (We'll send out more details
13275 about the bug once people have had some time to upgrade.)
13278 - Fix a heap-corruption bug that may be remotely triggerable on
13279 some platforms. Reported by Ilja van Sprundel.
13282 - When a stream at an exit relay is in state "resolving" or
13283 "connecting" and it receives an "end" relay cell, the exit relay
13284 would silently ignore the end cell and not close the stream. If
13285 the client never closes the circuit, then the exit relay never
13286 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
13287 reported by "wood".
13288 - When sending CREATED cells back for a given circuit, use a 64-bit
13289 connection ID to find the right connection, rather than an addr:port
13290 combination. Now that we can have multiple OR connections between
13291 the same ORs, it is no longer possible to use addr:port to uniquely
13292 identify a connection.
13293 - Bridge relays that had DirPort set to 0 would stop fetching
13294 descriptors shortly after startup, and then briefly resume
13295 after a new bandwidth test and/or after publishing a new bridge
13296 descriptor. Bridge users that try to bootstrap from them would
13297 get a recent networkstatus but would get descriptors from up to
13298 18 hours earlier, meaning most of the descriptors were obsolete
13299 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
13300 - Prevent bridge relays from serving their 'extrainfo' document
13301 to anybody who asks, now that extrainfo docs include potentially
13302 sensitive aggregated client geoip summaries. Bugfix on
13304 - If the cached networkstatus consensus is more than five days old,
13305 discard it rather than trying to use it. In theory it could be
13306 useful because it lists alternate directory mirrors, but in practice
13307 it just means we spend many minutes trying directory mirrors that
13308 are long gone from the network. Also discard router descriptors as
13309 we load them if they are more than five days old, since the onion
13310 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
13313 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
13314 could make gcc generate non-functional binary search code. Bugfix
13316 - Build correctly on platforms without socklen_t.
13317 - Compile without warnings on solaris.
13318 - Avoid potential crash on internal error during signature collection.
13319 Fixes bug 864. Patch from rovv.
13320 - Correct handling of possible malformed authority signing key
13321 certificates with internal signature types. Fixes bug 880.
13322 Bugfix on 0.2.0.3-alpha.
13323 - Fix a hard-to-trigger resource leak when logging credential status.
13325 - When we can't initialize DNS because the network is down, do not
13326 automatically stop Tor from starting. Instead, we retry failed
13327 dns_init() every 10 minutes, and change the exit policy to reject
13328 *:* until one succeeds. Fixes bug 691.
13329 - Use 64 bits instead of 32 bits for connection identifiers used with
13330 the controller protocol, to greatly reduce risk of identifier reuse.
13331 - When we're choosing an exit node for a circuit, and we have
13332 no pending streams, choose a good general exit rather than one that
13333 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
13334 - Fix another case of assuming, when a specific exit is requested,
13335 that we know more than the user about what hosts it allows.
13336 Fixes one case of bug 752. Patch from rovv.
13337 - Clip the MaxCircuitDirtiness config option to a minimum of 10
13338 seconds. Warn the user if lower values are given in the
13339 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
13340 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
13341 user if lower values are given in the configuration. Bugfix on
13342 0.1.1.17-rc. Patch by Sebastian.
13343 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
13344 the cache because we already had a v0 descriptor with the same ID.
13345 Bugfix on 0.2.0.18-alpha.
13346 - Fix a race condition when freeing keys shared between main thread
13347 and CPU workers that could result in a memory leak. Bugfix on
13348 0.1.0.1-rc. Fixes bug 889.
13349 - Send a valid END cell back when a client tries to connect to a
13350 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
13351 840. Patch from rovv.
13352 - Check which hops rendezvous stream cells are associated with to
13353 prevent possible guess-the-streamid injection attacks from
13354 intermediate hops. Fixes another case of bug 446. Based on patch
13356 - If a broken client asks a non-exit router to connect somewhere,
13357 do not even do the DNS lookup before rejecting the connection.
13358 Fixes another case of bug 619. Patch from rovv.
13359 - When a relay gets a create cell it can't decrypt (e.g. because it's
13360 using the wrong onion key), we were dropping it and letting the
13361 client time out. Now actually answer with a destroy cell. Fixes
13362 bug 904. Bugfix on 0.0.2pre8.
13364 o Minor bugfixes (hidden services):
13365 - Do not throw away existing introduction points on SIGHUP. Bugfix on
13366 0.0.6pre1. Patch by Karsten. Fixes bug 874.
13369 - Report the case where all signatures in a detached set are rejected
13370 differently than the case where there is an error handling the
13372 - When we realize that another process has modified our cached
13373 descriptors, print out a more useful error message rather than
13374 triggering an assertion. Fixes bug 885. Patch from Karsten.
13375 - Implement the 0x20 hack to better resist DNS poisoning: set the
13376 case on outgoing DNS requests randomly, and reject responses that do
13377 not match the case correctly. This logic can be disabled with the
13378 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
13379 of servers that do not reliably preserve case in replies. See
13380 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
13382 - Check DNS replies for more matching fields to better resist DNS
13384 - Never use OpenSSL compression: it wastes RAM and CPU trying to
13385 compress cells, which are basically all encrypted, compressed, or
13389 Changes in version 0.2.1.11-alpha - 2009-01-20
13390 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
13391 week it will take a long time to bootstrap again" bug. It also fixes
13392 an important security-related bug reported by Ilja van Sprundel. You
13393 should upgrade. (We'll send out more details about the bug once people
13394 have had some time to upgrade.)
13397 - Fix a heap-corruption bug that may be remotely triggerable on
13398 some platforms. Reported by Ilja van Sprundel.
13401 - Discard router descriptors as we load them if they are more than
13402 five days old. Otherwise if Tor is off for a long time and then
13403 starts with cached descriptors, it will try to use the onion
13404 keys in those obsolete descriptors when building circuits. Bugfix
13405 on 0.2.0.x. Fixes bug 887.
13408 - Try to make sure that the version of Libevent we're running with
13409 is binary-compatible with the one we built with. May address bug
13411 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
13412 for bug 905. Bugfix on 0.2.1.7-alpha.
13413 - Add a new --enable-local-appdata configuration switch to change
13414 the default location of the datadir on win32 from APPDATA to
13415 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
13416 entirely. Patch from coderman.
13419 - Make outbound DNS packets respect the OutboundBindAddress setting.
13420 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
13421 - When our circuit fails at the first hop (e.g. we get a destroy
13422 cell back), avoid using that OR connection anymore, and also
13423 tell all the one-hop directory requests waiting for it that they
13424 should fail. Bugfix on 0.2.1.3-alpha.
13425 - In the torify(1) manpage, mention that tsocks will leak your
13429 Changes in version 0.2.1.10-alpha - 2009-01-06
13430 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
13431 would make the bridge relay not so useful if it had DirPort set to 0,
13432 and one that could let an attacker learn a little bit of information
13433 about the bridge's users), and a bug that would cause your Tor relay
13434 to ignore a circuit create request it can't decrypt (rather than reply
13435 with an error). It also fixes a wide variety of other bugs.
13438 - If the cached networkstatus consensus is more than five days old,
13439 discard it rather than trying to use it. In theory it could
13440 be useful because it lists alternate directory mirrors, but in
13441 practice it just means we spend many minutes trying directory
13442 mirrors that are long gone from the network. Helps bug 887 a bit;
13444 - Bridge relays that had DirPort set to 0 would stop fetching
13445 descriptors shortly after startup, and then briefly resume
13446 after a new bandwidth test and/or after publishing a new bridge
13447 descriptor. Bridge users that try to bootstrap from them would
13448 get a recent networkstatus but would get descriptors from up to
13449 18 hours earlier, meaning most of the descriptors were obsolete
13450 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
13451 - Prevent bridge relays from serving their 'extrainfo' document
13452 to anybody who asks, now that extrainfo docs include potentially
13453 sensitive aggregated client geoip summaries. Bugfix on
13457 - New controller event "clients_seen" to report a geoip-based summary
13458 of which countries we've seen clients from recently. Now controllers
13459 like Vidalia can show bridge operators that they're actually making
13461 - Build correctly against versions of OpenSSL 0.9.8 or later built
13462 without support for deprecated functions.
13463 - Update to the "December 19 2008" ip-to-country file.
13465 o Minor bugfixes (on 0.2.0.x):
13466 - Authorities now vote for the Stable flag for any router whose
13467 weighted MTBF is at least 5 days, regardless of the mean MTBF.
13468 - Do not remove routers as too old if we do not have any consensus
13469 document. Bugfix on 0.2.0.7-alpha.
13470 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
13471 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
13472 - When an exit relay resolves a stream address to a local IP address,
13473 do not just keep retrying that same exit relay over and
13474 over. Instead, just close the stream. Addresses bug 872. Bugfix
13475 on 0.2.0.32. Patch from rovv.
13476 - If a hidden service sends us an END cell, do not consider
13477 retrying the connection; just close it. Patch from rovv.
13478 - When we made bridge authorities stop serving bridge descriptors over
13479 unencrypted links, we also broke DirPort reachability testing for
13480 bridges. So bridges with a non-zero DirPort were printing spurious
13481 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
13482 - When a relay gets a create cell it can't decrypt (e.g. because it's
13483 using the wrong onion key), we were dropping it and letting the
13484 client time out. Now actually answer with a destroy cell. Fixes
13485 bug 904. Bugfix on 0.0.2pre8.
13486 - Squeeze 2-5% out of client performance (according to oprofile) by
13487 improving the implementation of some policy-manipulation functions.
13489 o Minor bugfixes (on 0.2.1.x):
13490 - Make get_interface_address() function work properly again; stop
13491 guessing the wrong parts of our address as our address.
13492 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
13493 send on that circuit. Otherwise we might violate the proposal-110
13494 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
13496 - When we're sending non-EXTEND cells to the first hop in a circuit,
13497 for example to use an encrypted directory connection, we don't need
13498 to use RELAY_EARLY cells: the first hop knows what kind of cell
13499 it is, and nobody else can even see the cell type. Conserving
13500 RELAY_EARLY cells makes it easier to cannibalize circuits like
13502 - Stop logging nameserver addresses in reverse order.
13503 - If we are retrying a directory download slowly over and over, do
13504 not automatically give up after the 254th failure. Bugfix on
13506 - Resume reporting accurate "stream end" reasons to the local control
13507 port. They were lost in the changes for Proposal 148. Bugfix on
13510 o Deprecated and removed features:
13511 - The old "tor --version --version" command, which would print out
13512 the subversion "Id" of most of the source files, is now removed. It
13513 turned out to be less useful than we'd expected, and harder to
13516 o Code simplifications and refactoring:
13517 - Change our header file guard macros to be less likely to conflict
13518 with system headers. Adam Langley noticed that we were conflicting
13519 with log.h on Android.
13520 - Tool-assisted documentation cleanup. Nearly every function or
13521 static variable in Tor should have its own documentation now.
13524 Changes in version 0.2.1.9-alpha - 2008-12-25
13525 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
13527 o New directory authorities:
13528 - gabelmoo (the authority run by Karsten Loesing) now has a new
13532 - Never use a connection with a mismatched address to extend a
13533 circuit, unless that connection is canonical. A canonical
13534 connection is one whose address is authenticated by the router's
13535 identity key, either in a NETINFO cell or in a router descriptor.
13536 - Avoid a possible memory corruption bug when receiving hidden service
13537 descriptors. Bugfix on 0.2.1.6-alpha.
13540 - Fix a logic error that would automatically reject all but the first
13541 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
13542 part of bug 813/868. Bug spotted by coderman.
13543 - When a stream at an exit relay is in state "resolving" or
13544 "connecting" and it receives an "end" relay cell, the exit relay
13545 would silently ignore the end cell and not close the stream. If
13546 the client never closes the circuit, then the exit relay never
13547 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
13548 reported by "wood".
13549 - When we can't initialize DNS because the network is down, do not
13550 automatically stop Tor from starting. Instead, retry failed
13551 dns_init() every 10 minutes, and change the exit policy to reject
13552 *:* until one succeeds. Fixes bug 691.
13555 - Give a better error message when an overzealous init script says
13556 "sudo -u username tor --user username". Makes Bug 882 easier for
13558 - When a directory authority gives us a new guess for our IP address,
13559 log which authority we used. Hopefully this will help us debug
13560 the recent complaints about bad IP address guesses.
13561 - Detect svn revision properly when we're using git-svn.
13562 - Try not to open more than one descriptor-downloading connection
13563 to an authority at once. This should reduce load on directory
13564 authorities. Fixes bug 366.
13565 - Add cross-certification to newly generated certificates, so that
13566 a signing key is enough information to look up a certificate.
13567 Partial implementation of proposal 157.
13568 - Start serving certificates by <identity digest, signing key digest>
13569 pairs. Partial implementation of proposal 157.
13570 - Clients now never report any stream end reason except 'MISC'.
13571 Implements proposal 148.
13572 - On platforms with a maximum syslog string length, truncate syslog
13573 messages to that length ourselves, rather than relying on the
13574 system to do it for us.
13575 - Optimize out calls to time(NULL) that occur for every IO operation,
13576 or for every cell. On systems where time() is a slow syscall,
13577 this fix will be slightly helpful.
13578 - Exit servers can now answer resolve requests for ip6.arpa addresses.
13579 - When we download a descriptor that we then immediately (as
13580 a directory authority) reject, do not retry downloading it right
13581 away. Should save some bandwidth on authorities. Fix for bug
13582 888. Patch by Sebastian Hahn.
13583 - When a download gets us zero good descriptors, do not notify
13584 Tor that new directory information has arrived.
13585 - Avoid some nasty corner cases in the logic for marking connections
13586 as too old or obsolete or noncanonical for circuits. Partial
13589 o Minor features (controller):
13590 - New CONSENSUS_ARRIVED event to note when a new consensus has
13591 been fetched and validated.
13592 - When we realize that another process has modified our cached
13593 descriptors file, print out a more useful error message rather
13594 than triggering an assertion. Fixes bug 885. Patch from Karsten.
13595 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
13596 controllers to prevent SIGHUP from reloading the
13597 configuration. Fixes bug 856.
13600 - Resume using the correct "REASON=" stream when telling the
13601 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
13602 - When a canonical connection appears later in our internal list
13603 than a noncanonical one for a given OR ID, always use the
13604 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
13606 - Clip the MaxCircuitDirtiness config option to a minimum of 10
13607 seconds. Warn the user if lower values are given in the
13608 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
13609 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
13610 user if lower values are given in the configuration. Bugfix on
13611 0.1.1.17-rc. Patch by Sebastian.
13612 - Fix a race condition when freeing keys shared between main thread
13613 and CPU workers that could result in a memory leak. Bugfix on
13614 0.1.0.1-rc. Fixes bug 889.
13616 o Minor bugfixes (hidden services):
13617 - Do not throw away existing introduction points on SIGHUP (bugfix on
13618 0.0.6pre1); also, do not stall hidden services because we're
13619 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
13620 by John Brooks. Patch by Karsten. Fixes bug 874.
13621 - Fix a memory leak when we decline to add a v2 rendezvous
13622 descriptor to the cache because we already had a v0 descriptor
13623 with the same ID. Bugfix on 0.2.0.18-alpha.
13625 o Deprecated and removed features:
13626 - RedirectExits has been removed. It was deprecated since
13628 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
13629 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
13630 - Cell pools are now always enabled; --disable-cell-pools is ignored.
13632 o Code simplifications and refactoring:
13633 - Rename the confusing or_is_obsolete field to the more appropriate
13634 is_bad_for_new_circs, and move it to or_connection_t where it
13636 - Move edge-only flags from connection_t to edge_connection_t: not
13637 only is this better coding, but on machines of plausible alignment,
13638 it should save 4-8 bytes per connection_t. "Every little bit helps."
13639 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
13640 for consistency; keep old option working for backward compatibility.
13641 - Simplify the code for finding connections to use for a circuit.
13644 Changes in version 0.2.1.8-alpha - 2008-12-08
13645 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
13646 builds better on unusual platforms like Solaris and old OS X, and
13647 fixes a variety of other issues.
13650 - New DirPortFrontPage option that takes an html file and publishes
13651 it as "/" on the DirPort. Now relay operators can provide a
13652 disclaimer without needing to set up a separate webserver. There's
13653 a sample disclaimer in contrib/tor-exit-notice.html.
13656 - When the client is choosing entry guards, now it selects at most
13657 one guard from a given relay family. Otherwise we could end up with
13658 all of our entry points into the network run by the same operator.
13659 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
13662 - Fix a DOS opportunity during the voting signature collection process
13663 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
13664 - Fix a possible segfault when establishing an exit connection. Bugfix
13668 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
13670 - Made Tor a little less aggressive about deleting expired
13671 certificates. Partial fix for bug 854.
13672 - Stop doing unaligned memory access that generated bus errors on
13673 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
13674 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
13675 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
13676 - Make USR2 log-level switch take effect immediately. Bugfix on
13678 - If one win32 nameserver fails to get added, continue adding the
13679 rest, and don't automatically fail.
13680 - Use fcntl() for locking when flock() is not available. Should fix
13681 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
13682 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
13683 could make gcc generate non-functional binary search code. Bugfix
13685 - Build correctly on platforms without socklen_t.
13686 - Avoid potential crash on internal error during signature collection.
13687 Fixes bug 864. Patch from rovv.
13688 - Do not use C's stdio library for writing to log files. This will
13689 improve logging performance by a minute amount, and will stop
13690 leaking fds when our disk is full. Fixes bug 861.
13691 - Stop erroneous use of O_APPEND in cases where we did not in fact
13692 want to re-seek to the end of a file before every last write().
13693 - Correct handling of possible malformed authority signing key
13694 certificates with internal signature types. Fixes bug 880. Bugfix
13696 - Fix a hard-to-trigger resource leak when logging credential status.
13700 - Directory mirrors no longer fetch the v1 directory or
13701 running-routers files. They are obsolete, and nobody asks for them
13702 anymore. This is the first step to making v1 authorities obsolete.
13704 o Minor features (controller):
13705 - Return circuit purposes in response to GETINFO circuit-status. Fixes
13709 Changes in version 0.2.0.32 - 2008-11-20
13710 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
13711 packages (and maybe other packages) noticed by Theo de Raadt, fixes
13712 a smaller security flaw that might allow an attacker to access local
13713 services, further improves hidden service performance, and fixes a
13714 variety of other issues.
13717 - The "User" and "Group" config options did not clear the
13718 supplementary group entries for the Tor process. The "User" option
13719 is now more robust, and we now set the groups to the specified
13720 user's primary group. The "Group" option is now ignored. For more
13721 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
13722 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
13723 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
13724 - The "ClientDNSRejectInternalAddresses" config option wasn't being
13725 consistently obeyed: if an exit relay refuses a stream because its
13726 exit policy doesn't allow it, we would remember what IP address
13727 the relay said the destination address resolves to, even if it's
13728 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
13731 - Fix a DOS opportunity during the voting signature collection process
13732 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
13734 o Major bugfixes (hidden services):
13735 - When fetching v0 and v2 rendezvous service descriptors in parallel,
13736 we were failing the whole hidden service request when the v0
13737 descriptor fetch fails, even if the v2 fetch is still pending and
13738 might succeed. Similarly, if the last v2 fetch fails, we were
13739 failing the whole hidden service request even if a v0 fetch is
13740 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
13741 - When extending a circuit to a hidden service directory to upload a
13742 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
13743 requests failed, because the router descriptor has not been
13744 downloaded yet. In these cases, do not attempt to upload the
13745 rendezvous descriptor, but wait until the router descriptor is
13746 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
13747 descriptor from a hidden service directory for which the router
13748 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
13752 - Fix several infrequent memory leaks spotted by Coverity.
13753 - When testing for libevent functions, set the LDFLAGS variable
13754 correctly. Found by Riastradh.
13755 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
13756 bootstrapping with tunneled directory connections. Bugfix on
13757 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
13758 - When asked to connect to A.B.exit:80, if we don't know the IP for A
13759 and we know that server B rejects most-but-not all connections to
13760 port 80, we would previously reject the connection. Now, we assume
13761 the user knows what they were asking for. Fixes bug 752. Bugfix
13762 on 0.0.9rc5. Diagnosed by BarkerJr.
13763 - If we overrun our per-second write limits a little, count this as
13764 having used up our write allocation for the second, and choke
13765 outgoing directory writes. Previously, we had only counted this when
13766 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
13767 Bugfix on 0.2.0.x (??).
13768 - Remove the old v2 directory authority 'lefkada' from the default
13769 list. It has been gone for many months.
13770 - Stop doing unaligned memory access that generated bus errors on
13771 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
13772 - Make USR2 log-level switch take effect immediately. Bugfix on
13775 o Minor bugfixes (controller):
13776 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
13777 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
13780 Changes in version 0.2.1.7-alpha - 2008-11-08
13781 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
13782 packages (and maybe other packages) noticed by Theo de Raadt, fixes
13783 a smaller security flaw that might allow an attacker to access local
13784 services, adds better defense against DNS poisoning attacks on exit
13785 relays, further improves hidden service performance, and fixes a
13786 variety of other issues.
13789 - The "ClientDNSRejectInternalAddresses" config option wasn't being
13790 consistently obeyed: if an exit relay refuses a stream because its
13791 exit policy doesn't allow it, we would remember what IP address
13792 the relay said the destination address resolves to, even if it's
13793 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
13794 - The "User" and "Group" config options did not clear the
13795 supplementary group entries for the Tor process. The "User" option
13796 is now more robust, and we now set the groups to the specified
13797 user's primary group. The "Group" option is now ignored. For more
13798 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
13799 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
13800 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
13801 - Do not use or believe expired v3 authority certificates. Patch
13802 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
13805 - Now NodeFamily and MyFamily config options allow spaces in
13806 identity fingerprints, so it's easier to paste them in.
13807 Suggested by Lucky Green.
13808 - Implement the 0x20 hack to better resist DNS poisoning: set the
13809 case on outgoing DNS requests randomly, and reject responses that do
13810 not match the case correctly. This logic can be disabled with the
13811 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
13812 of servers that do not reliably preserve case in replies. See
13813 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
13815 - Preserve case in replies to DNSPort requests in order to support
13816 the 0x20 hack for resisting DNS poisoning attacks.
13818 o Hidden service performance improvements:
13819 - When the client launches an introduction circuit, retry with a
13820 new circuit after 30 seconds rather than 60 seconds.
13821 - Launch a second client-side introduction circuit in parallel
13822 after a delay of 15 seconds (based on work by Christian Wilms).
13823 - Hidden services start out building five intro circuits rather
13824 than three, and when the first three finish they publish a service
13825 descriptor using those. Now we publish our service descriptor much
13826 faster after restart.
13829 - Minor fix in the warning messages when you're having problems
13830 bootstrapping; also, be more forgiving of bootstrap problems when
13831 we're still making incremental progress on a given bootstrap phase.
13832 - When we're choosing an exit node for a circuit, and we have
13833 no pending streams, choose a good general exit rather than one that
13834 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
13835 - Send a valid END cell back when a client tries to connect to a
13836 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
13837 840. Patch from rovv.
13838 - If a broken client asks a non-exit router to connect somewhere,
13839 do not even do the DNS lookup before rejecting the connection.
13840 Fixes another case of bug 619. Patch from rovv.
13841 - Fix another case of assuming, when a specific exit is requested,
13842 that we know more than the user about what hosts it allows.
13843 Fixes another case of bug 752. Patch from rovv.
13844 - Check which hops rendezvous stream cells are associated with to
13845 prevent possible guess-the-streamid injection attacks from
13846 intermediate hops. Fixes another case of bug 446. Based on patch
13848 - Avoid using a negative right-shift when comparing 32-bit
13849 addresses. Possible fix for bug 845 and bug 811.
13850 - Make the assert_circuit_ok() function work correctly on circuits that
13851 have already been marked for close.
13852 - Fix read-off-the-end-of-string error in unit tests when decoding
13853 introduction points.
13854 - Fix uninitialized size field for memory area allocation: may improve
13855 memory performance during directory parsing.
13856 - Treat duplicate certificate fetches as failures, so that we do
13857 not try to re-fetch an expired certificate over and over and over.
13858 - Do not say we're fetching a certificate when we'll in fact skip it
13859 because of a pending download.
13862 Changes in version 0.2.1.6-alpha - 2008-09-30
13863 Tor 0.2.1.6-alpha further improves performance and robustness of
13864 hidden services, starts work on supporting per-country relay selection,
13865 and fixes a variety of smaller issues.
13868 - Implement proposal 121: make it possible to build hidden services
13869 that only certain clients are allowed to connect to. This is
13870 enforced at several points, so that unauthorized clients are unable
13871 to send INTRODUCE cells to the service, or even (depending on the
13872 type of authentication) to learn introduction points. This feature
13873 raises the bar for certain kinds of active attacks against hidden
13874 services. Code by Karsten Loesing.
13875 - Relays now store and serve v2 hidden service descriptors by default,
13876 i.e., the new default value for HidServDirectoryV2 is 1. This is
13877 the last step in proposal 114, which aims to make hidden service
13878 lookups more reliable.
13879 - Start work to allow node restrictions to include country codes. The
13880 syntax to exclude nodes in a country with country code XX is
13881 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
13882 refinement to decide what config options should take priority if
13883 you ask to both use a particular node and exclude it.
13884 - Allow ExitNodes list to include IP ranges and country codes, just
13885 like the Exclude*Nodes lists. Patch from Robert Hogan.
13888 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
13889 Tor to fail to start if you had it configured to use a bridge
13890 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
13891 - When extending a circuit to a hidden service directory to upload a
13892 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
13893 requests failed, because the router descriptor had not been
13894 downloaded yet. In these cases, we now wait until the router
13895 descriptor is downloaded, and then retry. Likewise, clients
13896 now skip over a hidden service directory if they don't yet have
13897 its router descriptor, rather than futilely requesting it and
13898 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
13900 - When fetching v0 and v2 rendezvous service descriptors in parallel,
13901 we were failing the whole hidden service request when the v0
13902 descriptor fetch fails, even if the v2 fetch is still pending and
13903 might succeed. Similarly, if the last v2 fetch fails, we were
13904 failing the whole hidden service request even if a v0 fetch is
13905 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
13906 - DNS replies need to have names matching their requests, but
13907 these names should be in the questions section, not necessarily
13908 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
13911 - Update to the "September 1 2008" ip-to-country file.
13912 - Allow ports 465 and 587 in the default exit policy again. We had
13913 rejected them in 0.1.0.15, because back in 2005 they were commonly
13914 misconfigured and ended up as spam targets. We hear they are better
13915 locked down these days.
13916 - Use a lockfile to make sure that two Tor processes are not
13917 simultaneously running with the same datadir.
13918 - Serve the latest v3 networkstatus consensus via the control
13919 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
13920 - Better logging about stability/reliability calculations on directory
13922 - Drop the requirement to have an open dir port for storing and
13923 serving v2 hidden service descriptors.
13924 - Directory authorities now serve a /tor/dbg-stability.txt URL to
13925 help debug WFU and MTBF calculations.
13926 - Implement most of Proposal 152: allow specialized servers to permit
13927 single-hop circuits, and clients to use those servers to build
13928 single-hop circuits when using a specialized controller. Patch
13929 from Josh Albrecht. Resolves feature request 768.
13930 - Add a -p option to tor-resolve for specifying the SOCKS port: some
13931 people find host:port too confusing.
13932 - Make TrackHostExit mappings expire a while after their last use, not
13933 after their creation. Patch from Robert Hogan.
13934 - Provide circuit purposes along with circuit events to the controller.
13937 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
13939 - Fixed some memory leaks -- some quite frequent, some almost
13940 impossible to trigger -- based on results from Coverity.
13941 - When testing for libevent functions, set the LDFLAGS variable
13942 correctly. Found by Riastradh.
13943 - Fix an assertion bug in parsing policy-related options; possible fix
13945 - Catch and report a few more bootstrapping failure cases when Tor
13946 fails to establish a TCP connection. Cleanup on 0.2.1.x.
13947 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
13948 bootstrapping with tunneled directory connections. Bugfix on
13949 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
13950 - When asked to connect to A.B.exit:80, if we don't know the IP for A
13951 and we know that server B rejects most-but-not all connections to
13952 port 80, we would previously reject the connection. Now, we assume
13953 the user knows what they were asking for. Fixes bug 752. Bugfix
13954 on 0.0.9rc5. Diagnosed by BarkerJr.
13955 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
13956 service directories if they have no advertised dir port. Bugfix
13958 - If we overrun our per-second write limits a little, count this as
13959 having used up our write allocation for the second, and choke
13960 outgoing directory writes. Previously, we had only counted this when
13961 we had met our limits precisely. Fixes bug 824. Patch by rovv.
13962 Bugfix on 0.2.0.x (??).
13963 - Avoid a "0 divided by 0" calculation when calculating router uptime
13964 at directory authorities. Bugfix on 0.2.0.8-alpha.
13965 - Make DNS resolved controller events into "CLOSED", not
13966 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
13968 - Fix a bug where an unreachable relay would establish enough
13969 reachability testing circuits to do a bandwidth test -- if
13970 we already have a connection to the middle hop of the testing
13971 circuit, then it could establish the last hop by using the existing
13972 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
13973 circuits no longer use entry guards in 0.2.1.3-alpha.
13974 - If we have correct permissions on $datadir, we complain to stdout
13975 and fail to start. But dangerous permissions on
13976 $datadir/cached-status/ would cause us to open a log and complain
13977 there. Now complain to stdout and fail to start in both cases. Fixes
13978 bug 820, reported by seeess.
13979 - Remove the old v2 directory authority 'lefkada' from the default
13980 list. It has been gone for many months.
13982 o Code simplifications and refactoring:
13983 - Revise the connection_new functions so that a more typesafe variant
13984 exists. This will work better with Coverity, and let us find any
13985 actual mistakes we're making here.
13986 - Refactor unit testing logic so that dmalloc can be used sensibly
13987 with unit tests to check for memory leaks.
13988 - Move all hidden-service related fields from connection and circuit
13989 structure to substructures: this way they won't eat so much memory.
13992 Changes in version 0.2.0.31 - 2008-09-03
13993 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
13994 a big bug we're seeing where in rare cases traffic from one Tor stream
13995 gets mixed into another stream, and fixes a variety of smaller issues.
13998 - Make sure that two circuits can never exist on the same connection
13999 with the same circuit ID, even if one is marked for close. This
14000 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
14001 - Relays now reject risky extend cells: if the extend cell includes
14002 a digest of all zeroes, or asks to extend back to the relay that
14003 sent the extend cell, tear down the circuit. Ideas suggested
14005 - If not enough of our entry guards are available so we add a new
14006 one, we might use the new one even if it overlapped with the
14007 current circuit's exit relay (or its family). Anonymity bugfix
14008 pointed out by rovv.
14011 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
14012 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
14013 - Correctly detect the presence of the linux/netfilter_ipv4.h header
14014 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
14015 - Pick size of default geoip filename string correctly on windows.
14016 Fixes bug 806. Bugfix on 0.2.0.30.
14017 - Make the autoconf script accept the obsolete --with-ssl-dir
14018 option as an alias for the actually-working --with-openssl-dir
14019 option. Fix the help documentation to recommend --with-openssl-dir.
14020 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
14021 - When using the TransPort option on OpenBSD, and using the User
14022 option to change UID and drop privileges, make sure to open
14023 /dev/pf before dropping privileges. Fixes bug 782. Patch from
14024 Christopher Davis. Bugfix on 0.1.2.1-alpha.
14025 - Try to attach connections immediately upon receiving a RENDEZVOUS2
14026 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
14027 on the client side when connecting to a hidden service. Bugfix
14028 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
14029 - When closing an application-side connection because its circuit is
14030 getting torn down, generate the stream event correctly. Bugfix on
14031 0.1.2.x. Anonymous patch.
14034 Changes in version 0.2.1.5-alpha - 2008-08-31
14035 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
14036 in a lot of the infrastructure for adding authorization to hidden
14037 services, lays the groundwork for having clients read their load
14038 balancing information out of the networkstatus consensus rather than
14039 the individual router descriptors, addresses two potential anonymity
14040 issues, and fixes a variety of smaller issues.
14043 - Convert many internal address representations to optionally hold
14045 - Generate and accept IPv6 addresses in many protocol elements.
14046 - Make resolver code handle nameservers located at ipv6 addresses.
14047 - Begin implementation of proposal 121 ("Client authorization for
14048 hidden services"): configure hidden services with client
14049 authorization, publish descriptors for them, and configure
14050 authorization data for hidden services at clients. The next
14051 step is to actually access hidden services that perform client
14053 - More progress toward proposal 141: Network status consensus
14054 documents and votes now contain bandwidth information for each
14055 router and a summary of that router's exit policy. Eventually this
14056 will be used by clients so that they do not have to download every
14057 known descriptor before building circuits.
14059 o Major bugfixes (on 0.2.0.x and before):
14060 - When sending CREATED cells back for a given circuit, use a 64-bit
14061 connection ID to find the right connection, rather than an addr:port
14062 combination. Now that we can have multiple OR connections between
14063 the same ORs, it is no longer possible to use addr:port to uniquely
14064 identify a connection.
14065 - Relays now reject risky extend cells: if the extend cell includes
14066 a digest of all zeroes, or asks to extend back to the relay that
14067 sent the extend cell, tear down the circuit. Ideas suggested
14069 - If not enough of our entry guards are available so we add a new
14070 one, we might use the new one even if it overlapped with the
14071 current circuit's exit relay (or its family). Anonymity bugfix
14072 pointed out by rovv.
14075 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
14076 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
14077 - When using the TransPort option on OpenBSD, and using the User
14078 option to change UID and drop privileges, make sure to open /dev/pf
14079 before dropping privileges. Fixes bug 782. Patch from Christopher
14080 Davis. Bugfix on 0.1.2.1-alpha.
14081 - Correctly detect the presence of the linux/netfilter_ipv4.h header
14082 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
14083 - Add a missing safe_str() call for a debug log message.
14084 - Use 64 bits instead of 32 bits for connection identifiers used with
14085 the controller protocol, to greatly reduce risk of identifier reuse.
14086 - Make the autoconf script accept the obsolete --with-ssl-dir
14087 option as an alias for the actually-working --with-openssl-dir
14088 option. Fix the help documentation to recommend --with-openssl-dir.
14089 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
14092 - Rate-limit too-many-sockets messages: when they happen, they happen
14093 a lot. Resolves bug 748.
14094 - Resist DNS poisoning a little better by making sure that names in
14095 answer sections match.
14096 - Print the SOCKS5 error message string as well as the error code
14097 when a tor-resolve request fails. Patch from Jacob.
14100 Changes in version 0.2.1.4-alpha - 2008-08-04
14101 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
14104 - The address part of exit policies was not correctly written
14105 to router descriptors. This generated router descriptors that failed
14106 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
14108 - Tor triggered a false assert when extending a circuit to a relay
14109 but we already have a connection open to that relay. Noticed by
14110 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
14113 - Fix a hidden service logging bug: in some edge cases, the router
14114 descriptor of a previously picked introduction point becomes
14115 obsolete and we need to give up on it rather than continually
14116 complaining that it has become obsolete. Observed by xiando. Bugfix
14119 o Removed features:
14120 - Take out the TestVia config option, since it was a workaround for
14121 a bug that was fixed in Tor 0.1.1.21.
14124 Changes in version 0.2.1.3-alpha - 2008-08-03
14125 Tor 0.2.1.3-alpha implements most of the pieces to prevent
14126 infinite-length circuit attacks (see proposal 110); fixes a bug that
14127 might cause exit relays to corrupt streams they send back; allows
14128 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
14129 ExcludeExitNodes config options; and fixes a big pile of bugs.
14131 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
14132 - Send a bootstrap problem "warn" event on the first problem if the
14133 reason is NO_ROUTE (that is, our network is down).
14136 - Implement most of proposal 110: The first K cells to be sent
14137 along a circuit are marked as special "early" cells; only K "early"
14138 cells will be allowed. Once this code is universal, we can block
14139 certain kinds of DOS attack by requiring that EXTEND commands must
14140 be sent using an "early" cell.
14143 - Try to attach connections immediately upon receiving a RENDEZVOUS2
14144 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
14145 on the client side when connecting to a hidden service. Bugfix
14146 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
14147 - Ensure that two circuits can never exist on the same connection
14148 with the same circuit ID, even if one is marked for close. This
14149 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
14152 - When relays do their initial bandwidth measurement, don't limit
14153 to just our entry guards for the test circuits. Otherwise we tend
14154 to have multiple test circuits going through a single entry guard,
14155 which makes our bandwidth test less accurate. Fixes part of bug 654;
14156 patch contributed by Josh Albrecht.
14157 - Add an ExcludeExitNodes option so users can list a set of nodes
14158 that should be be excluded from the exit node position, but
14159 allowed elsewhere. Implements proposal 151.
14160 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
14161 ExcludeNodes and ExcludeExitNodes lists.
14162 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
14163 be more efficient. Formerly it was quadratic in the number of
14164 servers; now it should be linear. Fixes bug 509.
14165 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
14166 and n_conn_id_digest fields into a separate structure that's
14167 only needed when the circuit has not yet attached to an n_conn.
14170 - Change the contrib/tor.logrotate script so it makes the new
14171 logs as "_tor:_tor" rather than the default, which is generally
14172 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
14173 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
14174 warnings (occasionally), but it can also cause the compiler to
14175 eliminate error-checking code. Suggested by Peter Gutmann.
14176 - When a hidden service is giving up on an introduction point candidate
14177 that was not included in the last published rendezvous descriptor,
14178 don't reschedule publication of the next descriptor. Fixes bug 763.
14180 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
14181 HiddenServiceExcludeNodes as obsolete: they never worked properly,
14182 and nobody claims to be using them. Fixes bug 754. Bugfix on
14183 0.1.0.1-rc. Patch from Christian Wilms.
14184 - Fix a small alignment and memory-wasting bug on buffer chunks.
14187 o Minor bugfixes (controller):
14188 - When closing an application-side connection because its circuit
14189 is getting torn down, generate the stream event correctly.
14190 Bugfix on 0.1.2.x. Anonymous patch.
14192 o Removed features:
14193 - Remove all backward-compatibility code to support relays running
14194 versions of Tor so old that they no longer work at all on the
14198 Changes in version 0.2.0.30 - 2008-07-15
14200 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
14201 warnings (occasionally), but it can also cause the compiler to
14202 eliminate error-checking code. Suggested by Peter Gutmann.
14205 Changes in version 0.2.0.29-rc - 2008-07-08
14206 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
14207 hidden-service performance bugs, and fixes a bunch of smaller bugs.
14210 - If you have more than one bridge but don't know their keys,
14211 you would only launch a request for the descriptor of the first one
14212 on your list. (Tor considered launching requests for the others, but
14213 found that it already had a connection on the way for $0000...0000
14214 so it didn't open another.) Bugfix on 0.2.0.x.
14215 - If you have more than one bridge but don't know their keys, and the
14216 connection to one of the bridges failed, you would cancel all
14217 pending bridge connections. (After all, they all have the same
14218 digest.) Bugfix on 0.2.0.x.
14219 - When a hidden service was trying to establish an introduction point,
14220 and Tor had built circuits preemptively for such purposes, we
14221 were ignoring all the preemptive circuits and launching a new one
14222 instead. Bugfix on 0.2.0.14-alpha.
14223 - When a hidden service was trying to establish an introduction point,
14224 and Tor *did* manage to reuse one of the preemptively built
14225 circuits, it didn't correctly remember which one it used,
14226 so it asked for another one soon after, until there were no
14227 more preemptive circuits, at which point it launched one from
14228 scratch. Bugfix on 0.0.9.x.
14229 - Make directory servers include the X-Your-Address-Is: http header in
14230 their responses even for begin_dir conns. Now clients who only
14231 ever use begin_dir connections still have a way to learn their IP
14232 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
14235 - Fix a macro/CPP interaction that was confusing some compilers:
14236 some GCCs don't like #if/#endif pairs inside macro arguments.
14238 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
14239 Fixes bug 704; fix from Steven Murdoch.
14240 - When opening /dev/null in finish_daemonize(), do not pass the
14241 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
14242 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
14243 - Correctly detect transparent proxy support on Linux hosts that
14244 require in.h to be included before netfilter_ipv4.h. Patch
14246 - Disallow session resumption attempts during the renegotiation
14247 stage of the v2 handshake protocol. Clients should never be trying
14248 session resumption at this point, but apparently some did, in
14249 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
14250 found by Geoff Goodell.
14253 Changes in version 0.2.1.2-alpha - 2008-06-20
14254 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
14255 make it easier to set up your own private Tor network; fixes several
14256 big bugs with using more than one bridge relay; fixes a big bug with
14257 offering hidden services quickly after Tor starts; and uses a better
14258 API for reporting potential bootstrapping problems to the controller.
14261 - New TestingTorNetwork config option to allow adjustment of
14262 previously constant values that, while reasonable, could slow
14263 bootstrapping. Implements proposal 135. Patch from Karsten.
14266 - If you have more than one bridge but don't know their digests,
14267 you would only learn a request for the descriptor of the first one
14268 on your list. (Tor considered launching requests for the others, but
14269 found that it already had a connection on the way for $0000...0000
14270 so it didn't open another.) Bugfix on 0.2.0.x.
14271 - If you have more than one bridge but don't know their digests,
14272 and the connection to one of the bridges failed, you would cancel
14273 all pending bridge connections. (After all, they all have the
14274 same digest.) Bugfix on 0.2.0.x.
14275 - When establishing a hidden service, introduction points that
14276 originate from cannibalized circuits are completely ignored and not
14277 included in rendezvous service descriptors. This might be another
14278 reason for delay in making a hidden service available. Bugfix
14279 from long ago (0.0.9.x?)
14282 - Allow OpenSSL to use dynamic locks if it wants.
14283 - When building a consensus, do not include routers that are down.
14284 This will cut down 30% to 40% on consensus size. Implements
14286 - In directory authorities' approved-routers files, allow
14287 fingerprints with or without space.
14288 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
14289 controller can query our current bootstrap state in case it attaches
14290 partway through and wants to catch up.
14291 - Send an initial "Starting" bootstrap status event, so we have a
14292 state to start out in.
14295 - Asking for a conditional consensus at .../consensus/<fingerprints>
14296 would crash a dirserver if it did not already have a
14297 consensus. Bugfix on 0.2.1.1-alpha.
14298 - Clean up some macro/CPP interactions: some GCC versions don't like
14299 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
14302 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
14303 - Directory authorities shouldn't complain about bootstrapping
14304 problems just because they do a lot of reachability testing and
14305 some of the connection attempts fail.
14306 - Start sending "count" and "recommendation" key/value pairs in
14307 bootstrap problem status events, so the controller can hear about
14308 problems even before Tor decides they're worth reporting for sure.
14309 - If you're using bridges, generate "bootstrap problem" warnings
14310 as soon as you run out of working bridges, rather than waiting
14311 for ten failures -- which will never happen if you have less than
14313 - If we close our OR connection because there's been a circuit
14314 pending on it for too long, we were telling our bootstrap status
14315 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
14318 Changes in version 0.2.1.1-alpha - 2008-06-13
14319 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
14320 were making the Tor process bloat especially on Linux; makes our TLS
14321 handshake blend in better; sends "bootstrap phase" status events to
14322 the controller, so it can keep the user informed of progress (and
14323 problems) fetching directory information and establishing circuits;
14324 and adds a variety of smaller features.
14327 - More work on making our TLS handshake blend in: modify the list
14328 of ciphers advertised by OpenSSL in client mode to even more
14329 closely resemble a common web browser. We cheat a little so that
14330 we can advertise ciphers that the locally installed OpenSSL doesn't
14332 - Start sending "bootstrap phase" status events to the controller,
14333 so it can keep the user informed of progress fetching directory
14334 information and establishing circuits. Also inform the controller
14335 if we think we're stuck at a particular bootstrap phase. Implements
14337 - Resume using OpenSSL's RAND_poll() for better (and more portable)
14338 cross-platform entropy collection again. We used to use it, then
14339 stopped using it because of a bug that could crash systems that
14340 called RAND_poll when they had a lot of fds open. It looks like the
14341 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
14342 at startup, and to call RAND_poll() when we reseed later only if
14343 we have a non-buggy OpenSSL version.
14346 - When we choose to abandon a new entry guard because we think our
14347 older ones might be better, close any circuits pending on that
14348 new entry guard connection. This fix should make us recover much
14349 faster when our network is down and then comes back. Bugfix on
14350 0.1.2.8-beta; found by lodger.
14352 o Memory fixes and improvements:
14353 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
14354 to avoid unused RAM in buffer chunks and memory pools.
14355 - Speed up parsing and cut down on memory fragmentation by using
14356 stack-style allocations for parsing directory objects. Previously,
14357 this accounted for over 40% of allocations from within Tor's code
14358 on a typical directory cache.
14359 - Use a Bloom filter rather than a digest-based set to track which
14360 descriptors we need to keep around when we're cleaning out old
14361 router descriptors. This speeds up the computation significantly,
14362 and may reduce fragmentation.
14363 - Reduce the default smartlist size from 32 to 16; it turns out that
14364 most smartlists hold around 8-12 elements tops.
14365 - Make dumpstats() log the fullness and size of openssl-internal
14367 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
14368 patch to their OpenSSL, turn it on to save memory on servers. This
14369 patch will (with any luck) get included in a mainline distribution
14371 - Never use OpenSSL compression: it wastes RAM and CPU trying to
14372 compress cells, which are basically all encrypted, compressed,
14376 - Stop reloading the router list from disk for no reason when we
14377 run out of reachable directory mirrors. Once upon a time reloading
14378 it would set the 'is_running' flag back to 1 for them. It hasn't
14379 done that for a long time.
14380 - In very rare situations new hidden service descriptors were
14381 published earlier than 30 seconds after the last change to the
14382 service. (We currently think that a hidden service descriptor
14383 that's been stable for 30 seconds is worth publishing.)
14386 - Allow separate log levels to be configured for different logging
14387 domains. For example, this allows one to log all notices, warnings,
14388 or errors, plus all memory management messages of level debug or
14389 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
14390 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
14391 and stop using a warning that had become unfixably verbose under
14393 - New --hush command-line option similar to --quiet. While --quiet
14394 disables all logging to the console on startup, --hush limits the
14395 output to messages of warning and error severity.
14396 - Servers support a new URL scheme for consensus downloads that
14397 allows the client to specify which authorities are trusted.
14398 The server then only sends the consensus if the client will trust
14399 it. Otherwise a 404 error is sent back. Clients use this
14400 new scheme when the server supports it (meaning it's running
14401 0.2.1.1-alpha or later). Implements proposal 134.
14402 - New configure/torrc options (--enable-geoip-stats,
14403 DirRecordUsageByCountry) to record how many IPs we've served
14404 directory info to in each country code, how many status documents
14405 total we've sent to each country code, and what share of the total
14406 directory requests we should expect to see.
14407 - Use the TLS1 hostname extension to more closely resemble browser
14409 - Lots of new unit tests.
14410 - Add a macro to implement the common pattern of iterating through
14411 two parallel lists in lockstep.
14414 Changes in version 0.2.0.28-rc - 2008-06-13
14415 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
14416 performance bug, and fixes a bunch of smaller bugs.
14419 - Fix a bug where, when we were choosing the 'end stream reason' to
14420 put in our relay end cell that we send to the exit relay, Tor
14421 clients on Windows were sometimes sending the wrong 'reason'. The
14422 anonymity problem is that exit relays may be able to guess whether
14423 the client is running Windows, thus helping partition the anonymity
14424 set. Down the road we should stop sending reasons to exit relays,
14425 or otherwise prevent future versions of this bug.
14428 - While setting up a hidden service, some valid introduction circuits
14429 were overlooked and abandoned. This might be the reason for
14430 the long delay in making a hidden service available. Bugfix on
14434 - Update to the "June 9 2008" ip-to-country file.
14435 - Run 'make test' as part of 'make dist', so we stop releasing so
14436 many development snapshots that fail their unit tests.
14439 - When we're checking if we have enough dir info for each relay
14440 to begin establishing circuits, make sure that we actually have
14441 the descriptor listed in the consensus, not just any descriptor.
14443 - Bridge relays no longer print "xx=0" in their extrainfo document
14444 for every single country code in the geoip db. Bugfix on
14446 - Only warn when we fail to load the geoip file if we were planning to
14447 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
14448 - If we change our MaxAdvertisedBandwidth and then reload torrc,
14449 Tor won't realize it should publish a new relay descriptor. Fixes
14450 bug 688, reported by mfr. Bugfix on 0.1.2.x.
14451 - When we haven't had any application requests lately, don't bother
14452 logging that we have expired a bunch of descriptors. Bugfix
14454 - Make relay cells written on a connection count as non-padding when
14455 tracking how long a connection has been in use. Bugfix on
14456 0.2.0.1-alpha. Spotted by lodger.
14457 - Fix unit tests in 0.2.0.27-rc.
14458 - Fix compile on Windows.
14461 Changes in version 0.2.0.27-rc - 2008-06-03
14462 Tor 0.2.0.27-rc adds a few features we left out of the earlier
14463 release candidates. In particular, we now include an IP-to-country
14464 GeoIP database, so controllers can easily look up what country a
14465 given relay is in, and so bridge relays can give us some sanitized
14466 summaries about which countries are making use of bridges. (See proposal
14467 126-geoip-fetching.txt for details.)
14470 - Include an IP-to-country GeoIP file in the tarball, so bridge
14471 relays can report sanitized summaries of the usage they're seeing.
14474 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
14475 Robert Hogan. Fixes the first part of bug 681.
14476 - Make bridge authorities never serve extrainfo docs.
14477 - Add support to detect Libevent versions in the 1.4.x series
14479 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
14480 - Include a new contrib/tor-exit-notice.html file that exit relay
14481 operators can put on their website to help reduce abuse queries.
14484 - When tunneling an encrypted directory connection, and its first
14485 circuit fails, do not leave it unattached and ask the controller
14486 to deal. Fixes the second part of bug 681.
14487 - Make bridge authorities correctly expire old extrainfo documents
14491 Changes in version 0.2.0.26-rc - 2008-05-13
14492 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
14493 in Debian's OpenSSL packages. All users running any 0.2.0.x version
14494 should upgrade, whether they're running Debian or not.
14496 o Major security fixes:
14497 - Use new V3 directory authority keys on the tor26, gabelmoo, and
14498 moria1 V3 directory authorities. The old keys were generated with
14499 a vulnerable version of Debian's OpenSSL package, and must be
14500 considered compromised. Other authorities' keys were not generated
14501 with an affected version of OpenSSL.
14504 - List authority signatures as "unrecognized" based on DirServer
14505 lines, not on cert cache. Bugfix on 0.2.0.x.
14508 - Add a new V3AuthUseLegacyKey option to make it easier for
14509 authorities to change their identity keys if they have to.
14512 Changes in version 0.2.0.25-rc - 2008-04-23
14513 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
14516 - Remember to initialize threading before initializing logging.
14517 Otherwise, many BSD-family implementations will crash hard on
14518 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
14521 - Authorities correctly free policies on bad servers on
14522 exit. Fixes bug 672. Bugfix on 0.2.0.x.
14525 Changes in version 0.2.0.24-rc - 2008-04-22
14526 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
14527 v3 directory authority, makes relays with dynamic IP addresses and no
14528 DirPort notice more quickly when their IP address changes, fixes a few
14529 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
14531 o New directory authorities:
14532 - Take lefkada out of the list of v3 directory authorities, since
14533 it has been down for months.
14534 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
14538 - Detect address changes more quickly on non-directory mirror
14539 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
14541 o Minor features (security):
14542 - Reject requests for reverse-dns lookup of names that are in
14543 a private address space. Patch from lodger.
14544 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
14547 o Minor bugfixes (crashes):
14548 - Avoid a rare assert that can trigger when Tor doesn't have much
14549 directory information yet and it tries to fetch a v2 hidden
14550 service descriptor. Fixes bug 651, reported by nwf.
14551 - Initialize log mutex before initializing dmalloc. Otherwise,
14552 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
14553 - Use recursive pthread mutexes in order to avoid deadlock when
14554 logging debug-level messages to a controller. Bug spotted by nwf,
14555 bugfix on 0.2.0.16-alpha.
14557 o Minor bugfixes (resource management):
14558 - Keep address policies from leaking memory: start their refcount
14559 at 1, not 2. Bugfix on 0.2.0.16-alpha.
14560 - Free authority certificates on exit, so they don't look like memory
14561 leaks. Bugfix on 0.2.0.19-alpha.
14562 - Free static hashtables for policy maps and for TLS connections on
14563 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
14564 - Avoid allocating extra space when computing consensuses on 64-bit
14565 platforms. Bug spotted by aakova.
14567 o Minor bugfixes (misc):
14568 - Do not read the configuration file when we've only been told to
14569 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
14570 based on patch from Sebastian Hahn.
14571 - Exit relays that are used as a client can now reach themselves
14572 using the .exit notation, rather than just launching an infinite
14573 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
14574 - When attempting to open a logfile fails, tell us why.
14575 - Fix a dumb bug that was preventing us from knowing that we should
14576 preemptively build circuits to handle expected directory requests.
14577 Fixes bug 660. Bugfix on 0.1.2.x.
14578 - Warn less verbosely about clock skew from netinfo cells from
14579 untrusted sources. Fixes bug 663.
14580 - Make controller stream events for DNS requests more consistent,
14581 by adding "new stream" events for DNS requests, and removing
14582 spurious "stream closed" events" for cached reverse resolves.
14583 Patch from mwenge. Fixes bug 646.
14584 - Correctly notify one-hop connections when a circuit build has
14585 failed. Possible fix for bug 669. Found by lodger.
14588 Changes in version 0.2.0.23-rc - 2008-03-24
14589 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
14590 makes bootstrapping faster if the first directory mirror you contact
14591 is down. The bundles also include the new Vidalia 0.1.2 release.
14594 - When a tunneled directory request is made to a directory server
14595 that's down, notice after 30 seconds rather than 120 seconds. Also,
14596 fail any begindir streams that are pending on it, so they can
14597 retry elsewhere. This was causing multi-minute delays on bootstrap.
14600 Changes in version 0.2.0.22-rc - 2008-03-18
14601 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
14602 enables encrypted directory connections by default for non-relays, fixes
14603 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
14604 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
14607 - Enable encrypted directory connections by default for non-relays,
14608 so censor tools that block Tor directory connections based on their
14609 plaintext patterns will no longer work. This means Tor works in
14610 certain censored countries by default again.
14613 - Make sure servers always request certificates from clients during
14614 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
14615 - Do not enter a CPU-eating loop when a connection is closed in
14616 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
14617 diagnosed by lodger; bugfix on 0.2.0.20-rc.
14618 - Fix assertion failure that could occur when a blocked circuit
14619 became unblocked, and it had pending client DNS requests. Bugfix
14620 on 0.2.0.1-alpha. Fixes bug 632.
14622 o Minor bugfixes (on 0.1.2.x):
14623 - Generate "STATUS_SERVER" events rather than misspelled
14624 "STATUS_SEVER" events. Caught by mwenge.
14625 - When counting the number of bytes written on a TLS connection,
14626 look at the BIO actually used for writing to the network, not
14627 at the BIO used (sometimes) to buffer data for the network.
14628 Looking at different BIOs could result in write counts on the
14629 order of ULONG_MAX. Fixes bug 614.
14630 - On Windows, correctly detect errors when listing the contents of
14631 a directory. Fix from lodger.
14633 o Minor bugfixes (on 0.2.0.x):
14634 - Downgrade "sslv3 alert handshake failure" message to INFO.
14635 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
14636 left BandwidthRate and BandwidthBurst at the default, we would be
14637 silently limited by those defaults. Now raise them to match the
14638 RelayBandwidth* values.
14639 - Fix the SVK version detection logic to work correctly on a branch.
14640 - Make --enable-openbsd-malloc work correctly on Linux with alpha
14641 CPUs. Fixes bug 625.
14642 - Logging functions now check that the passed severity is sane.
14643 - Use proper log levels in the testsuite call of
14644 get_interface_address6().
14645 - When using a nonstandard malloc, do not use the platform values for
14646 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
14647 - Make the openbsd malloc code use 8k pages on alpha CPUs and
14649 - Detect mismatched page sizes when using --enable-openbsd-malloc.
14650 - Avoid double-marked-for-close warning when certain kinds of invalid
14651 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
14652 for bug 617. Bugfix on 0.2.0.1-alpha.
14653 - Make sure that the "NULL-means-reject *:*" convention is followed by
14654 all the policy manipulation functions, avoiding some possible crash
14655 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
14656 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
14657 actually works, and doesn't warn about every single reverse lookup.
14658 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
14661 - Only log guard node status when guard node status has changed.
14662 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
14663 make "INFO" 75% less verbose.
14666 Changes in version 0.2.0.21-rc - 2008-03-02
14667 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
14668 makes Tor work well with Vidalia again, fixes a rare assert bug,
14669 and fixes a pair of more minor bugs. The bundles also include Vidalia
14670 0.1.0 and Torbutton 1.1.16.
14673 - The control port should declare that it requires password auth
14674 when HashedControlSessionPassword is set too. Patch from Matt Edman;
14675 bugfix on 0.2.0.20-rc. Fixes bug 615.
14676 - Downgrade assert in connection_buckets_decrement() to a log message.
14677 This may help us solve bug 614, and in any case will make its
14678 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
14679 - We were sometimes miscounting the number of bytes read from the
14680 network, causing our rate limiting to not be followed exactly.
14681 Bugfix on 0.2.0.16-alpha. Reported by lodger.
14684 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
14685 OpenSSL versions should have been working fine. Diagnosis and patch
14686 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
14687 Bugfix on 0.2.0.20-rc.
14690 Changes in version 0.2.0.20-rc - 2008-02-24
14691 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
14692 makes more progress towards normalizing Tor's TLS handshake, makes
14693 hidden services work better again, helps relays bootstrap if they don't
14694 know their IP address, adds optional support for linking in openbsd's
14695 allocator or tcmalloc, allows really fast relays to scale past 15000
14696 sockets, and fixes a bunch of minor bugs reported by Veracode.
14699 - Enable the revised TLS handshake based on the one designed by
14700 Steven Murdoch in proposal 124, as revised in proposal 130. It
14701 includes version negotiation for OR connections as described in
14702 proposal 105. The new handshake is meant to be harder for censors
14703 to fingerprint, and it adds the ability to detect certain kinds of
14704 man-in-the-middle traffic analysis attacks. The version negotiation
14705 feature will allow us to improve Tor's link protocol more safely
14707 - Choose which bridge to use proportional to its advertised bandwidth,
14708 rather than uniformly at random. This should speed up Tor for
14709 bridge users. Also do this for people who set StrictEntryNodes.
14710 - When a TrackHostExits-chosen exit fails too many times in a row,
14711 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
14714 - Resolved problems with (re-)fetching hidden service descriptors.
14715 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
14716 and 0.2.0.19-alpha.
14717 - If we only ever used Tor for hidden service lookups or posts, we
14718 would stop building circuits and start refusing connections after
14719 24 hours, since we falsely believed that Tor was dormant. Reported
14720 by nwf; bugfix on 0.1.2.x.
14721 - Servers that don't know their own IP address should go to the
14722 authorities for their first directory fetch, even if their DirPort
14723 is off or if they don't know they're reachable yet. This will help
14724 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
14725 - When counting the number of open sockets, count not only the number
14726 of sockets we have received from the socket() call, but also
14727 the number we've gotten from accept() and socketpair(). This bug
14728 made us fail to count all sockets that we were using for incoming
14729 connections. Bugfix on 0.2.0.x.
14730 - Fix code used to find strings within buffers, when those strings
14731 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
14732 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
14733 - Add a new __HashedControlSessionPassword option for controllers
14734 to use for one-off session password hashes that shouldn't get
14735 saved to disk by SAVECONF --- Vidalia users were accumulating a
14736 pile of HashedControlPassword lines in their torrc files, one for
14737 each time they had restarted Tor and then clicked Save. Make Tor
14738 automatically convert "HashedControlPassword" to this new option but
14739 only when it's given on the command line. Partial fix for bug 586.
14741 o Minor features (performance):
14742 - Tune parameters for cell pool allocation to minimize amount of
14744 - Add OpenBSD malloc code from phk as an optional malloc
14745 replacement on Linux: some glibc libraries do very poorly
14746 with Tor's memory allocation patterns. Pass
14747 --enable-openbsd-malloc to get the replacement malloc code.
14748 - Add a --with-tcmalloc option to the configure script to link
14749 against tcmalloc (if present). Does not yet search for
14750 non-system include paths.
14751 - Stop imposing an arbitrary maximum on the number of file descriptors
14752 used for busy servers. Bug reported by Olaf Selke; patch from
14755 o Minor features (other):
14756 - When SafeLogging is disabled, log addresses along with all TLS
14758 - When building with --enable-gcc-warnings, check for whether Apple's
14759 warning "-Wshorten-64-to-32" is available.
14760 - Add a --passphrase-fd argument to the tor-gencert command for
14763 o Minor bugfixes (memory leaks and code problems):
14764 - We were leaking a file descriptor if Tor started with a zero-length
14765 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
14766 - Detect size overflow in zlib code. Reported by Justin Ferguson and
14768 - We were comparing the raw BridgePassword entry with a base64'ed
14769 version of it, when handling a "/tor/networkstatus-bridges"
14770 directory request. Now compare correctly. Noticed by Veracode.
14771 - Recover from bad tracked-since value in MTBF-history file.
14772 Should fix bug 537.
14773 - Alter the code that tries to recover from unhandled write
14774 errors, to not try to flush onto a socket that's given us
14775 unhandled errors. Bugfix on 0.1.2.x.
14776 - Make Unix controlsockets work correctly on OpenBSD. Patch from
14777 tup. Bugfix on 0.2.0.3-alpha.
14779 o Minor bugfixes (other):
14780 - If we have an extra-info document for our server, always make
14781 it available on the control port, even if we haven't gotten
14782 a copy of it from an authority yet. Patch from mwenge.
14783 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
14784 - Directory mirrors no longer include a guess at the client's IP
14785 address if the connection appears to be coming from the same /24
14786 network; it was producing too many wrong guesses.
14787 - Make the new hidden service code respect the SafeLogging setting.
14788 Bugfix on 0.2.0.x. Patch from Karsten.
14789 - When starting as an authority, do not overwrite all certificates
14790 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
14791 - If we're trying to flush the last bytes on a connection (for
14792 example, when answering a directory request), reset the
14793 time-to-give-up timeout every time we manage to write something
14794 on the socket. Bugfix on 0.1.2.x.
14795 - Change the behavior of "getinfo status/good-server-descriptor"
14796 so it doesn't return failure when any authority disappears.
14797 - Even though the man page said that "TrackHostExits ." should
14798 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
14799 - Report TLS "zero return" case as a "clean close" and "IO error"
14800 as a "close". Stop calling closes "unexpected closes": existing
14801 Tors don't use SSL_close(), so having a connection close without
14802 the TLS shutdown handshake is hardly unexpected.
14803 - Send NAMESERVER_STATUS messages for a single failed nameserver
14806 o Code simplifications and refactoring:
14807 - Remove the tor_strpartition function: its logic was confused,
14808 and it was only used for one thing that could be implemented far
14812 Changes in version 0.2.0.19-alpha - 2008-02-09
14813 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
14814 handshake, makes path selection for relays more secure and IP address
14815 guessing more robust, and generally fixes a lot of bugs in preparation
14816 for calling the 0.2.0 branch stable.
14819 - Do not include recognizeable strings in the commonname part of
14820 Tor's x509 certificates.
14823 - If we're a relay, avoid picking ourselves as an introduction point,
14824 a rendezvous point, or as the final hop for internal circuits. Bug
14825 reported by taranis and lodger. Bugfix on 0.1.2.x.
14826 - Patch from "Andrew S. Lists" to catch when we contact a directory
14827 mirror at IP address X and he says we look like we're coming from
14828 IP address X. Bugfix on 0.1.2.x.
14830 o Minor features (security):
14831 - Be more paranoid about overwriting sensitive memory on free(),
14832 as a defensive programming tactic to ensure forward secrecy.
14834 o Minor features (directory authority):
14835 - Actually validate the options passed to AuthDirReject,
14836 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
14837 - Reject router descriptors with out-of-range bandwidthcapacity or
14838 bandwidthburst values.
14840 o Minor features (controller):
14841 - Reject controller commands over 1MB in length. This keeps rogue
14842 processes from running us out of memory.
14844 o Minor features (misc):
14845 - Give more descriptive well-formedness errors for out-of-range
14846 hidden service descriptor/protocol versions.
14847 - Make memory debugging information describe more about history
14848 of cell allocation, so we can help reduce our memory use.
14850 o Deprecated features (controller):
14851 - The status/version/num-versioning and status/version/num-concurring
14852 GETINFO options are no longer useful in the v3 directory protocol:
14853 treat them as deprecated, and warn when they're used.
14856 - When our consensus networkstatus has been expired for a while, stop
14857 being willing to build circuits using it. Fixes bug 401. Bugfix
14859 - Directory caches now fetch certificates from all authorities
14860 listed in a networkstatus consensus, even when they do not
14861 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
14862 - When connecting to a bridge without specifying its key, insert
14863 the connection into the identity-to-connection map as soon as
14864 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
14865 - Detect versions of OS X where malloc_good_size() is present in the
14866 library but never actually declared. Resolves bug 587. Bugfix
14868 - Stop incorrectly truncating zlib responses to directory authority
14869 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
14870 - Stop recommending that every server operator send mail to tor-ops.
14871 Resolves bug 597. Bugfix on 0.1.2.x.
14872 - Don't trigger an assert if we start a directory authority with a
14873 private IP address (like 127.0.0.1).
14874 - Avoid possible failures when generating a directory with routers
14875 with over-long versions strings, or too many flags set. Bugfix
14877 - If an attempt to launch a DNS resolve request over the control
14878 port fails because we have overrun the limit on the number of
14879 connections, tell the controller that the request has failed.
14880 - Avoid using too little bandwidth when our clock skips a few
14881 seconds. Bugfix on 0.1.2.x.
14882 - Fix shell error when warning about missing packages in configure
14883 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
14884 - Do not become confused when receiving a spurious VERSIONS-like
14885 cell from a confused v1 client. Bugfix on 0.2.0.x.
14886 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
14887 introduction points for a hidden service have failed. Patch from
14888 Karsten Loesing. Bugfix on 0.2.0.x.
14890 o Code simplifications and refactoring:
14891 - Remove some needless generality from cpuworker code, for improved
14893 - Stop overloading the circuit_t.onionskin field for both "onionskin
14894 from a CREATE cell that we are waiting for a cpuworker to be
14895 assigned" and "onionskin from an EXTEND cell that we are going to
14896 send to an OR as soon as we are connected". Might help with bug 600.
14897 - Add an in-place version of aes_crypt() so that we can avoid doing a
14898 needless memcpy() call on each cell payload.
14901 Changes in version 0.2.0.18-alpha - 2008-01-25
14902 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
14903 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
14904 that can warn or reject connections to ports generally associated with
14905 vulnerable-plaintext protocols.
14907 o New directory authorities:
14908 - Set up dannenberg (run by CCC) as the sixth v3 directory
14912 - Fix a major memory leak when attempting to use the v2 TLS
14913 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
14914 - We accidentally enabled the under-development v2 TLS handshake
14915 code, which was causing log entries like "TLS error while
14916 renegotiating handshake". Disable it again. Resolves bug 590.
14917 - We were computing the wrong Content-Length: header for directory
14918 responses that need to be compressed on the fly, causing clients
14919 asking for those items to always fail. Bugfix on 0.2.0.x; partially
14923 - Avoid going directly to the directory authorities even if you're a
14924 relay, if you haven't found yourself reachable yet or if you've
14925 decided not to advertise your dirport yet. Addresses bug 556.
14926 - If we've gone 12 hours since our last bandwidth check, and we
14927 estimate we have less than 50KB bandwidth capacity but we could
14928 handle more, do another bandwidth test.
14929 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
14930 Tor can warn and/or refuse connections to ports commonly used with
14931 vulnerable-plaintext protocols. Currently we warn on ports 23,
14932 109, 110, and 143, but we don't reject any.
14935 - When we setconf ClientOnly to 1, close any current OR and Dir
14936 listeners. Reported by mwenge.
14937 - When we get a consensus that's been signed by more people than
14938 we expect, don't log about it; it's not a big deal. Reported
14942 - Don't answer "/tor/networkstatus-bridges" directory requests if
14943 the request isn't encrypted.
14944 - Make "ClientOnly 1" config option disable directory ports too.
14945 - Patches from Karsten Loesing to make v2 hidden services more
14946 robust: work even when there aren't enough HSDir relays available;
14947 retry when a v2 rend desc fetch fails; but don't retry if we
14948 already have a usable v0 rend desc.
14951 Changes in version 0.2.0.17-alpha - 2008-01-17
14952 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
14955 - Make the tor-gencert man page get included correctly in the tarball.
14958 Changes in version 0.2.0.16-alpha - 2008-01-17
14959 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
14960 Loesing, and generally cleans up a lot of features and minor bugs.
14962 o New directory authorities:
14963 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
14966 o Major performance improvements:
14967 - Switch our old ring buffer implementation for one more like that
14968 used by free Unix kernels. The wasted space in a buffer with 1mb
14969 of data will now be more like 8k than 1mb. The new implementation
14970 also avoids realloc();realloc(); patterns that can contribute to
14971 memory fragmentation.
14974 - Configuration files now accept C-style strings as values. This
14975 helps encode characters not allowed in the current configuration
14976 file format, such as newline or #. Addresses bug 557.
14977 - Although we fixed bug 539 (where servers would send HTTP status 503
14978 responses _and_ send a body too), there are still servers out
14979 there that haven't upgraded. Therefore, make clients parse such
14980 bodies when they receive them.
14981 - When we're not serving v2 directory information, there is no reason
14982 to actually keep any around. Remove the obsolete files and directory
14983 on startup if they are very old and we aren't going to serve them.
14985 o Minor performance improvements:
14986 - Reference-count and share copies of address policy entries; only 5%
14987 of them were actually distinct.
14988 - Never walk through the list of logs if we know that no log is
14989 interested in a given message.
14992 - When an authority has not signed a consensus, do not try to
14993 download a nonexistent "certificate with key 00000000". Bugfix
14994 on 0.2.0.x. Fixes bug 569.
14995 - Fix a rare assert error when we're closing one of our threads:
14996 use a mutex to protect the list of logs, so we never write to the
14997 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
14998 bug 575, which is kind of the revenge of bug 222.
14999 - Patch from Karsten Loesing to complain less at both the client
15000 and the relay when a relay used to have the HSDir flag but doesn't
15001 anymore, and we try to upload a hidden service descriptor.
15002 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
15004 - Do not try to download missing certificates until we have tried
15005 to check our fallback consensus. Fixes bug 583.
15006 - Make bridges round reported GeoIP stats info up to the nearest
15007 estimate, not down. Now we can distinguish between "0 people from
15008 this country" and "1 person from this country".
15009 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
15010 - Avoid possible segfault if key generation fails in
15011 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
15012 - Avoid segfault in the case where a badly behaved v2 versioning
15013 directory sends a signed networkstatus with missing client-versions.
15015 - Avoid segfaults on certain complex invocations of
15016 router_get_by_hexdigest(). Bugfix on 0.1.2.
15017 - Correct bad index on array access in parse_http_time(). Bugfix
15019 - Fix possible bug in vote generation when server versions are present
15020 but client versions are not.
15021 - Fix rare bug on REDIRECTSTREAM control command when called with no
15022 port set: it could erroneously report an error when none had
15024 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
15025 compressing large objects and find ourselves with more than 4k
15026 left over. Bugfix on 0.2.0.
15027 - Fix a small memory leak when setting up a hidden service.
15028 - Fix a few memory leaks that could in theory happen under bizarre
15030 - Fix an assert if we post a general-purpose descriptor via the
15031 control port but that descriptor isn't mentioned in our current
15032 network consensus. Bug reported by Jon McLachlan; bugfix on
15035 o Minor features (controller):
15036 - Get NS events working again. Patch from tup.
15037 - The GETCONF command now escapes and quotes configuration values
15038 that don't otherwise fit into the torrc file.
15039 - The SETCONF command now handles quoted values correctly.
15041 o Minor features (directory authorities):
15042 - New configuration options to override default maximum number of
15043 servers allowed on a single IP address. This is important for
15044 running a test network on a single host.
15045 - Actually implement the -s option to tor-gencert.
15046 - Add a manual page for tor-gencert.
15048 o Minor features (bridges):
15049 - Bridge authorities no longer serve bridge descriptors over
15050 unencrypted connections.
15052 o Minor features (other):
15053 - Add hidden services and DNSPorts to the list of things that make
15054 Tor accept that it has running ports. Change starting Tor with no
15055 ports from a fatal error to a warning; we might change it back if
15056 this turns out to confuse anybody. Fixes bug 579.
15059 Changes in version 0.1.2.19 - 2008-01-17
15060 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
15061 exit policy a little bit more conservative so it's safer to run an
15062 exit relay on a home system, and fixes a variety of smaller issues.
15065 - Exit policies now reject connections that are addressed to a
15066 relay's public (external) IP address too, unless
15067 ExitPolicyRejectPrivate is turned off. We do this because too
15068 many relays are running nearby to services that trust them based
15069 on network address.
15072 - When the clock jumps forward a lot, do not allow the bandwidth
15073 buckets to become negative. Fixes bug 544.
15074 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
15075 on every successful resolve. Reported by Mike Perry.
15076 - Purge old entries from the "rephist" database and the hidden
15077 service descriptor database even when DirPort is zero.
15078 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
15079 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
15080 crashing or mis-answering these requests.
15081 - When we decide to send a 503 response to a request for servers, do
15082 not then also send the server descriptors: this defeats the whole
15083 purpose. Fixes bug 539.
15086 - Changing the ExitPolicyRejectPrivate setting should cause us to
15087 rebuild our server descriptor.
15088 - Fix handling of hex nicknames when answering controller requests for
15089 networkstatus by name, or when deciding whether to warn about
15090 unknown routers in a config option. (Patch from mwenge.)
15091 - Fix a couple of hard-to-trigger autoconf problems that could result
15092 in really weird results on platforms whose sys/types.h files define
15093 nonstandard integer types.
15094 - Don't try to create the datadir when running --verify-config or
15095 --hash-password. Resolves bug 540.
15096 - If we were having problems getting a particular descriptor from the
15097 directory caches, and then we learned about a new descriptor for
15098 that router, we weren't resetting our failure count. Reported
15100 - Although we fixed bug 539 (where servers would send HTTP status 503
15101 responses _and_ send a body too), there are still servers out there
15102 that haven't upgraded. Therefore, make clients parse such bodies
15103 when they receive them.
15104 - Run correctly on systems where rlim_t is larger than unsigned long.
15105 This includes some 64-bit systems.
15106 - Run correctly on platforms (like some versions of OS X 10.5) where
15107 the real limit for number of open files is OPEN_FILES, not rlim_max
15108 from getrlimit(RLIMIT_NOFILES).
15109 - Avoid a spurious free on base64 failure.
15110 - Avoid segfaults on certain complex invocations of
15111 router_get_by_hexdigest().
15112 - Fix rare bug on REDIRECTSTREAM control command when called with no
15113 port set: it could erroneously report an error when none had
15117 Changes in version 0.2.0.15-alpha - 2007-12-25
15118 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
15119 features added in 0.2.0.13-alpha.
15122 - Fix several remotely triggerable asserts based on DirPort requests
15123 for a v2 or v3 networkstatus object before we were prepared. This
15124 was particularly bad for 0.2.0.13 and later bridge relays, who
15125 would never have a v2 networkstatus and would thus always crash
15126 when used. Bugfixes on 0.2.0.x.
15127 - Estimate the v3 networkstatus size more accurately, rather than
15128 estimating it at zero bytes and giving it artificially high priority
15129 compared to other directory requests. Bugfix on 0.2.0.x.
15132 - Fix configure.in logic for cross-compilation.
15133 - When we load a bridge descriptor from the cache, and it was
15134 previously unreachable, mark it as retriable so we won't just
15135 ignore it. Also, try fetching a new copy immediately. Bugfixes
15137 - The bridge GeoIP stats were counting other relays, for example
15138 self-reachability and authority-reachability tests.
15141 - Support compilation to target iPhone; patch from cjacker huang.
15142 To build for iPhone, pass the --enable-iphone option to configure.
15145 Changes in version 0.2.0.14-alpha - 2007-12-23
15147 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
15148 without a datadirectory from a previous Tor install. Reported
15150 - Fix a crash when we fetch a descriptor that turns out to be
15151 unexpected (it used to be in our networkstatus when we started
15152 fetching it, but it isn't in our current networkstatus), and we
15153 aren't using bridges. Bugfix on 0.2.0.x.
15154 - Fix a crash when accessing hidden services: it would work the first
15155 time you use a given introduction point for your service, but
15156 on subsequent requests we'd be using garbage memory. Fixed by
15157 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
15158 - Fix a crash when we load a bridge descriptor from disk but we don't
15159 currently have a Bridge line for it in our torrc. Bugfix on
15163 - If bridge authorities set BridgePassword, they will serve a
15164 snapshot of known bridge routerstatuses from their DirPort to
15165 anybody who knows that password. Unset by default.
15168 - Make the unit tests build again.
15169 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
15170 - Make PublishServerDescriptor default to 1, so the default doesn't
15171 have to change as we invent new directory protocol versions.
15172 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
15173 be included unless sys/time.h is already included. Fixes
15174 bug 553. Bugfix on 0.2.0.x.
15175 - If we receive a general-purpose descriptor and then receive an
15176 identical bridge-purpose descriptor soon after, don't discard
15177 the next one as a duplicate.
15180 - If BridgeRelay is set to 1, then the default for
15181 PublishServerDescriptor is now "bridge" rather than "v2,v3".
15182 - If the user sets RelayBandwidthRate but doesn't set
15183 RelayBandwidthBurst, then make them equal rather than erroring out.
15186 Changes in version 0.2.0.13-alpha - 2007-12-21
15187 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
15188 Goodell, fixes many more bugs, and adds a lot of infrastructure for
15191 o New directory authorities:
15192 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
15196 - Only update guard status (usable / not usable) once we have
15197 enough directory information. This was causing us to always pick
15198 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
15199 causing us to discard all our guards on startup if we hadn't been
15200 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
15201 - Purge old entries from the "rephist" database and the hidden
15202 service descriptor databases even when DirPort is zero. Bugfix
15204 - We were ignoring our RelayBandwidthRate for the first 30 seconds
15205 after opening a circuit -- even a relayed circuit. Bugfix on
15207 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
15208 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
15209 crashing or mis-answering these types of requests.
15210 - Relays were publishing their server descriptor to v1 and v2
15211 directory authorities, but they didn't try publishing to v3-only
15212 authorities. Fix this; and also stop publishing to v1 authorities.
15214 - When we were reading router descriptors from cache, we were ignoring
15215 the annotations -- so for example we were reading in bridge-purpose
15216 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
15217 - When we decided to send a 503 response to a request for servers, we
15218 were then also sending the server descriptors: this defeats the
15219 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
15222 - Bridge relays now behave like clients with respect to time
15223 intervals for downloading new consensus documents -- otherwise they
15224 stand out. Bridge users now wait until the end of the interval,
15225 so their bridge relay will be sure to have a new consensus document.
15226 - Three new config options (AlternateDirAuthority,
15227 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
15228 user selectively replace the default directory authorities by type,
15229 rather than the all-or-nothing replacement that DirServer offers.
15230 - Tor can now be configured to read a GeoIP file from disk in one
15231 of two formats. This can be used by controllers to map IP addresses
15232 to countries. Eventually, it may support exit-by-country.
15233 - When possible, bridge relays remember which countries users
15234 are coming from, and report aggregate information in their
15235 extra-info documents, so that the bridge authorities can learn
15236 where Tor is blocked.
15237 - Bridge directory authorities now do reachability testing on the
15238 bridges they know. They provide router status summaries to the
15239 controller via "getinfo ns/purpose/bridge", and also dump summaries
15240 to a file periodically.
15241 - Stop fetching directory info so aggressively if your DirPort is
15242 on but your ORPort is off; stop fetching v2 dir info entirely.
15243 You can override these choices with the new FetchDirInfoEarly
15247 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
15248 consensus documents when there are too many relays at a single
15249 IP address. Now clear it in v2 network status documents too, and
15250 also clear it in routerinfo_t when the relay is no longer listed
15251 in the relevant networkstatus document.
15252 - Don't crash if we get an unexpected value for the
15253 PublishServerDescriptor config option. Reported by Matt Edman;
15254 bugfix on 0.2.0.9-alpha.
15255 - Our new v2 hidden service descriptor format allows descriptors
15256 that have no introduction points. But Tor crashed when we tried
15257 to build a descriptor with no intro points (and it would have
15258 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
15259 by Karsten Loesing.
15260 - Fix building with dmalloc 5.5.2 with glibc.
15261 - Reject uploaded descriptors and extrainfo documents if they're
15262 huge. Otherwise we'll cache them all over the network and it'll
15263 clog everything up. Reported by Aljosha Judmayer.
15264 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
15265 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
15266 - When the DANGEROUS_VERSION controller status event told us we're
15267 running an obsolete version, it used the string "OLD" to describe
15268 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
15269 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
15270 - If we can't expand our list of entry guards (e.g. because we're
15271 using bridges or we have StrictEntryNodes set), don't mark relays
15272 down when they fail a directory request. Otherwise we're too quick
15273 to mark all our entry points down. Bugfix on 0.1.2.x.
15274 - Fix handling of hex nicknames when answering controller requests for
15275 networkstatus by name, or when deciding whether to warn about unknown
15276 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
15277 - Fix a couple of hard-to-trigger autoconf problems that could result
15278 in really weird results on platforms whose sys/types.h files define
15279 nonstandard integer types. Bugfix on 0.1.2.x.
15280 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
15281 - Don't crash on name lookup when we have no current consensus. Fixes
15282 bug 538; bugfix on 0.2.0.x.
15283 - Only Tors that want to mirror the v2 directory info should
15284 create the "cached-status" directory in their datadir. (All Tors
15285 used to create it.) Bugfix on 0.2.0.9-alpha.
15286 - Directory authorities should only automatically download Extra Info
15287 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
15290 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
15291 consumers. (We already do this on HUP.)
15292 - Authorities and caches fetch the v2 networkstatus documents
15293 less often, now that v3 is encouraged.
15294 - Add a new config option BridgeRelay that specifies you want to
15295 be a bridge relay. Right now the only difference is that it makes
15296 you answer begin_dir requests, and it makes you cache dir info,
15297 even if your DirPort isn't on.
15298 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
15299 ask about source, timestamp of arrival, purpose, etc. We need
15300 something like this to help Vidalia not do GeoIP lookups on bridge
15302 - Allow multiple HashedControlPassword config lines, to support
15303 multiple controller passwords.
15304 - Authorities now decide whether they're authoritative for a given
15305 router based on the router's purpose.
15306 - New config options AuthDirBadDir and AuthDirListBadDirs for
15307 authorities to mark certain relays as "bad directories" in the
15308 networkstatus documents. Also supports the "!baddir" directive in
15309 the approved-routers file.
15312 Changes in version 0.2.0.12-alpha - 2007-11-16
15313 This twelfth development snapshot fixes some more build problems as
15314 well as a few minor bugs.
15317 - Make it build on OpenBSD again. Patch from tup.
15318 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
15319 package-building for Red Hat, OS X, etc.
15321 o Minor bugfixes (on 0.1.2.x):
15322 - Changing the ExitPolicyRejectPrivate setting should cause us to
15323 rebuild our server descriptor.
15325 o Minor bugfixes (on 0.2.0.x):
15326 - When we're lacking a consensus, don't try to perform rendezvous
15327 operations. Reported by Karsten Loesing.
15328 - Fix a small memory leak whenever we decide against using a
15329 newly picked entry guard. Reported by Mike Perry.
15330 - When authorities detected more than two relays running on the same
15331 IP address, they were clearing all the status flags but forgetting
15332 to clear the "hsdir" flag. So clients were being told that a
15333 given relay was the right choice for a v2 hsdir lookup, yet they
15334 never had its descriptor because it was marked as 'not running'
15336 - If we're trying to fetch a bridge descriptor and there's no way
15337 the bridge authority could help us (for example, we don't know
15338 a digest, or there is no bridge authority), don't be so eager to
15339 fall back to asking the bridge authority.
15340 - If we're using bridges or have strictentrynodes set, and our
15341 chosen exit is in the same family as all our bridges/entry guards,
15342 then be flexible about families.
15345 - When we negotiate a v2 link-layer connection (not yet implemented),
15346 accept RELAY_EARLY cells and turn them into RELAY cells if we've
15347 negotiated a v1 connection for their next step. Initial code for
15351 Changes in version 0.2.0.11-alpha - 2007-11-12
15352 This eleventh development snapshot fixes some build problems with
15353 the previous snapshot. It also includes a more secure-by-default exit
15354 policy for relays, fixes an enormous memory leak for exit relays, and
15355 fixes another bug where servers were falling out of the directory list.
15358 - Exit policies now reject connections that are addressed to a
15359 relay's public (external) IP address too, unless
15360 ExitPolicyRejectPrivate is turned off. We do this because too
15361 many relays are running nearby to services that trust them based
15362 on network address. Bugfix on 0.1.2.x.
15365 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
15366 on every successful resolve. Reported by Mike Perry; bugfix
15368 - On authorities, never downgrade to old router descriptors simply
15369 because they're listed in the consensus. This created a catch-22
15370 where we wouldn't list a new descriptor because there was an
15371 old one in the consensus, and we couldn't get the new one in the
15372 consensus because we wouldn't list it. Possible fix for bug 548.
15373 Also, this might cause bug 543 to appear on authorities; if so,
15374 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
15376 o Packaging fixes on 0.2.0.10-alpha:
15377 - We were including instructions about what to do with the
15378 src/config/fallback-consensus file, but we weren't actually
15379 including it in the tarball. Disable all of that for now.
15382 - Allow people to say PreferTunnelledDirConns rather than
15383 PreferTunneledDirConns, for those alternate-spellers out there.
15386 - Don't reevaluate all the information from our consensus document
15387 just because we've downloaded a v2 networkstatus that we intend
15388 to cache. Fixes bug 545; bugfix on 0.2.0.x.
15391 Changes in version 0.2.0.10-alpha - 2007-11-10
15392 This tenth development snapshot adds a third v3 directory authority
15393 run by Mike Perry, adds most of Karsten Loesing's new hidden service
15394 descriptor format, fixes a bad crash bug and new bridge bugs introduced
15395 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
15396 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
15397 addresses many more minor issues.
15399 o New directory authorities:
15400 - Set up ides (run by Mike Perry) as the third v3 directory authority.
15403 - Allow tunnelled directory connections to ask for an encrypted
15404 "begin_dir" connection or an anonymized "uses a full Tor circuit"
15405 connection independently. Now we can make anonymized begin_dir
15406 connections for (e.g.) more secure hidden service posting and
15408 - More progress on proposal 114: code from Karsten Loesing to
15409 implement new hidden service descriptor format.
15410 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
15411 accommodate the growing number of servers that use the default
15412 and are reaching it.
15413 - Directory authorities use a new formula for selecting which nodes
15414 to advertise as Guards: they must be in the top 7/8 in terms of
15415 how long we have known about them, and above the median of those
15416 nodes in terms of weighted fractional uptime.
15417 - Make "not enough dir info yet" warnings describe *why* Tor feels
15418 it doesn't have enough directory info yet.
15421 - Stop servers from crashing if they set a Family option (or
15422 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
15424 - Make bridge users work again -- the move to v3 directories in
15425 0.2.0.9-alpha had introduced a number of bugs that made bridges
15426 no longer work for clients.
15427 - When the clock jumps forward a lot, do not allow the bandwidth
15428 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
15430 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
15431 - When the consensus lists a router descriptor that we previously were
15432 mirroring, but that we considered non-canonical, reload the
15433 descriptor as canonical. This fixes bug 543 where Tor servers
15434 would start complaining after a few days that they don't have
15435 enough directory information to build a circuit.
15436 - Consider replacing the current consensus when certificates arrive
15437 that make the pending consensus valid. Previously, we were only
15438 considering replacement when the new certs _didn't_ help.
15439 - Fix an assert error on startup if we didn't already have the
15440 consensus and certs cached in our datadirectory: we were caching
15441 the consensus in consensus_waiting_for_certs but then free'ing it
15443 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
15444 Request) if we need more v3 certs but we've already got pending
15445 requests for all of them.
15446 - Correctly back off from failing certificate downloads. Fixes
15448 - Authorities don't vote on the Running flag if they have been running
15449 for less than 30 minutes themselves. Fixes bug 547, where a newly
15450 started authority would vote that everyone was down.
15452 o New requirements:
15453 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
15454 it, it had no AES, and it hasn't seen any security patches since
15458 - Clients now hold circuitless TLS connections open for 1.5 times
15459 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
15460 rebuild a new circuit over them within that timeframe. Previously,
15461 they held them open only for KeepalivePeriod (5 minutes).
15462 - Use "If-Modified-Since" to avoid retrieving consensus
15463 networkstatuses that we already have.
15464 - When we have no consensus, check FallbackNetworkstatusFile (defaults
15465 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
15466 we start knowing some directory caches.
15467 - When we receive a consensus from the future, warn about skew.
15468 - Improve skew reporting: try to give the user a better log message
15469 about how skewed they are, and how much this matters.
15470 - When we have a certificate for an authority, believe that
15471 certificate's claims about the authority's IP address.
15472 - New --quiet command-line option to suppress the default console log.
15473 Good in combination with --hash-password.
15474 - Authorities send back an X-Descriptor-Not-New header in response to
15475 an accepted-but-discarded descriptor upload. Partially implements
15477 - Make the log message for "tls error. breaking." more useful.
15478 - Better log messages about certificate downloads, to attempt to
15479 track down the second incarnation of bug 546.
15481 o Minor features (bridges):
15482 - If bridge users set UpdateBridgesFromAuthority, but the digest
15483 they ask for is a 404 from the bridge authority, they now fall
15484 back to trying the bridge directly.
15485 - Bridges now use begin_dir to publish their server descriptor to
15486 the bridge authority, even when they haven't set TunnelDirConns.
15488 o Minor features (controller):
15489 - When reporting clock skew, and we know that the clock is _at least
15490 as skewed_ as some value, but we don't know the actual value,
15491 report the value as a "minimum skew."
15494 - Update linux-tor-prio.sh script to allow QoS based on the uid of
15495 the Tor process. Patch from Marco Bonetti with tweaks from Mike
15499 - Refuse to start if both ORPort and UseBridges are set. Bugfix
15500 on 0.2.0.x, suggested by Matt Edman.
15501 - Don't stop fetching descriptors when FetchUselessDescriptors is
15502 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
15503 reported by tup and ioerror.
15504 - Better log message on vote from unknown authority.
15505 - Don't log "Launching 0 request for 0 router" message.
15507 o Minor bugfixes (memory leaks):
15508 - Stop leaking memory every time we parse a v3 certificate. Bugfix
15510 - Stop leaking memory every time we load a v3 certificate. Bugfix
15511 on 0.2.0.1-alpha. Fixes bug 536.
15512 - Stop leaking a cached networkstatus on exit. Bugfix on
15514 - Stop leaking voter information every time we free a consensus.
15515 Bugfix on 0.2.0.3-alpha.
15516 - Stop leaking signed data every time we check a voter signature.
15517 Bugfix on 0.2.0.3-alpha.
15518 - Stop leaking a signature every time we fail to parse a consensus or
15519 a vote. Bugfix on 0.2.0.3-alpha.
15520 - Stop leaking v2_download_status_map on shutdown. Bugfix on
15522 - Stop leaking conn->nickname every time we make a connection to a
15523 Tor relay without knowing its expected identity digest (e.g. when
15524 using bridges). Bugfix on 0.2.0.3-alpha.
15526 - Minor bugfixes (portability):
15527 - Run correctly on platforms where rlim_t is larger than unsigned
15528 long, and/or where the real limit for number of open files is
15529 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
15530 particular, these may be needed for OS X 10.5.
15533 Changes in version 0.1.2.18 - 2007-10-28
15534 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
15535 hidden service introduction that were causing huge delays, and a big
15536 bug that was causing some servers to disappear from the network status
15537 lists for a few hours each day.
15539 o Major bugfixes (crashes):
15540 - If a connection is shut down abruptly because of something that
15541 happened inside connection_flushed_some(), do not call
15542 connection_finished_flushing(). Should fix bug 451:
15543 "connection_stop_writing: Assertion conn->write_event failed"
15544 Bugfix on 0.1.2.7-alpha.
15545 - Fix possible segfaults in functions called from
15546 rend_process_relay_cell().
15548 o Major bugfixes (hidden services):
15549 - Hidden services were choosing introduction points uniquely by
15550 hexdigest, but when constructing the hidden service descriptor
15551 they merely wrote the (potentially ambiguous) nickname.
15552 - Clients now use the v2 intro format for hidden service
15553 connections: they specify their chosen rendezvous point by identity
15554 digest rather than by (potentially ambiguous) nickname. These
15555 changes could speed up hidden service connections dramatically.
15557 o Major bugfixes (other):
15558 - Stop publishing a new server descriptor just because we get a
15559 HUP signal. This led (in a roundabout way) to some servers getting
15560 dropped from the networkstatus lists for a few hours each day.
15561 - When looking for a circuit to cannibalize, consider family as well
15562 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
15563 circuit cannibalization).
15564 - When a router wasn't listed in a new networkstatus, we were leaving
15565 the flags for that router alone -- meaning it remained Named,
15566 Running, etc -- even though absence from the networkstatus means
15567 that it shouldn't be considered to exist at all anymore. Now we
15568 clear all the flags for routers that fall out of the networkstatus
15569 consensus. Fixes bug 529.
15572 - Don't try to access (or alter) the state file when running
15573 --list-fingerprint or --verify-config or --hash-password. Resolves
15575 - When generating information telling us how to extend to a given
15576 router, do not try to include the nickname if it is
15577 absent. Resolves bug 467.
15578 - Fix a user-triggerable segfault in expand_filename(). (There isn't
15579 a way to trigger this remotely.)
15580 - When sending a status event to the controller telling it that an
15581 OR address is reachable, set the port correctly. (Previously we
15582 were reporting the dir port.)
15583 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
15584 command. Bugfix on 0.1.2.17.
15585 - When loading bandwidth history, do not believe any information in
15586 the future. Fixes bug 434.
15587 - When loading entry guard information, do not believe any information
15589 - When we have our clock set far in the future and generate an
15590 onion key, then re-set our clock to be correct, we should not stop
15591 the onion key from getting rotated.
15592 - On some platforms, accept() can return a broken address. Detect
15593 this more quietly, and deal accordingly. Fixes bug 483.
15594 - It's not actually an error to find a non-pending entry in the DNS
15595 cache when canceling a pending resolve. Don't log unless stuff
15596 is fishy. Resolves bug 463.
15597 - Don't reset trusted dir server list when we set a configuration
15598 option. Patch from Robert Hogan.
15599 - Don't try to create the datadir when running --verify-config or
15600 --hash-password. Resolves bug 540.
15603 Changes in version 0.2.0.9-alpha - 2007-10-24
15604 This ninth development snapshot switches clients to the new v3 directory
15605 system; allows servers to be listed in the network status even when they
15606 have the same nickname as a registered server; and fixes many other
15607 bugs including a big one that was causing some servers to disappear
15608 from the network status lists for a few hours each day.
15610 o Major features (directory system):
15611 - Clients now download v3 consensus networkstatus documents instead
15612 of v2 networkstatus documents. Clients and caches now base their
15613 opinions about routers on these consensus documents. Clients only
15614 download router descriptors listed in the consensus.
15615 - Authorities now list servers who have the same nickname as
15616 a different named server, but list them with a new flag,
15617 "Unnamed". Now we can list servers that happen to pick the same
15618 nickname as a server that registered two years ago and then
15619 disappeared. Partially implements proposal 122.
15620 - If the consensus lists a router as "Unnamed", the name is assigned
15621 to a different router: do not identify the router by that name.
15622 Partially implements proposal 122.
15623 - Authorities can now come to a consensus on which method to use to
15624 compute the consensus. This gives us forward compatibility.
15627 - Stop publishing a new server descriptor just because we HUP or
15628 when we find our DirPort to be reachable but won't actually publish
15629 it. New descriptors without any real changes are dropped by the
15630 authorities, and can screw up our "publish every 18 hours" schedule.
15632 - When a router wasn't listed in a new networkstatus, we were leaving
15633 the flags for that router alone -- meaning it remained Named,
15634 Running, etc -- even though absence from the networkstatus means
15635 that it shouldn't be considered to exist at all anymore. Now we
15636 clear all the flags for routers that fall out of the networkstatus
15637 consensus. Fixes bug 529; bugfix on 0.1.2.x.
15638 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
15639 extrainfo documents and then discard them immediately for not
15640 matching the latest router. Bugfix on 0.2.0.1-alpha.
15642 o Minor features (v3 directory protocol):
15643 - Allow tor-gencert to generate a new certificate without replacing
15645 - Allow certificates to include an address.
15646 - When we change our directory-cache settings, reschedule all voting
15647 and download operations.
15648 - Reattempt certificate downloads immediately on failure, as long as
15649 we haven't failed a threshold number of times yet.
15650 - Delay retrying consensus downloads while we're downloading
15651 certificates to verify the one we just got. Also, count getting a
15652 consensus that we already have (or one that isn't valid) as a failure,
15653 and count failing to get the certificates after 20 minutes as a
15655 - Build circuits and download descriptors even if our consensus is a
15656 little expired. (This feature will go away once authorities are
15659 o Minor features (router descriptor cache):
15660 - If we find a cached-routers file that's been sitting around for more
15661 than 28 days unmodified, then most likely it's a leftover from
15662 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
15664 - When we (as a cache) download a descriptor because it was listed
15665 in a consensus, remember when the consensus was supposed to expire,
15666 and don't expire the descriptor until then.
15668 o Minor features (performance):
15669 - Call routerlist_remove_old_routers() much less often. This should
15670 speed startup, especially on directory caches.
15671 - Don't try to launch new descriptor downloads quite so often when we
15672 already have enough directory information to build circuits.
15673 - Base64 decoding was actually showing up on our profile when parsing
15674 the initial descriptor file; switch to an in-process all-at-once
15675 implementation that's about 3.5x times faster than calling out to
15678 o Minor features (compilation):
15679 - Detect non-ASCII platforms (if any still exist) and refuse to
15680 build there: some of our code assumes that 'A' is 65 and so on.
15682 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
15683 - Make the "next period" votes into "current period" votes immediately
15684 after publishing the consensus; avoid a heisenbug that made them
15685 stick around indefinitely.
15686 - When we discard a vote as a duplicate, do not report this as
15688 - Treat missing v3 keys or certificates as an error when running as a
15689 v3 directory authority.
15690 - When we're configured to be a v3 authority, but we're only listed
15691 as a non-v3 authority in our DirServer line for ourself, correct
15693 - If an authority doesn't have a qualified hostname, just put
15694 its address in the vote. This fixes the problem where we referred to
15695 "moria on moria:9031."
15696 - Distinguish between detached signatures for the wrong period, and
15697 detached signatures for a divergent vote.
15698 - Fix a small memory leak when computing a consensus.
15699 - When there's no concensus, we were forming a vote every 30
15700 minutes, but writing the "valid-after" line in our vote based
15701 on our configured V3AuthVotingInterval: so unless the intervals
15702 matched up, we immediately rejected our own vote because it didn't
15703 start at the voting interval that caused us to construct a vote.
15705 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
15706 - Delete unverified-consensus when the real consensus is set.
15707 - Consider retrying a consensus networkstatus fetch immediately
15708 after one fails: don't wait 60 seconds to notice.
15709 - When fetching a consensus as a cache, wait until a newer consensus
15710 should exist before trying to replace the current one.
15711 - Use a more forgiving schedule for retrying failed consensus
15712 downloads than for other types.
15714 o Minor bugfixes (other directory issues):
15715 - Correct the implementation of "download votes by digest." Bugfix on
15717 - Authorities no longer send back "400 you're unreachable please fix
15718 it" errors to Tor servers that aren't online all the time. We're
15719 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
15721 o Minor bugfixes (controller):
15722 - Don't reset trusted dir server list when we set a configuration
15723 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
15724 - Respond to INT and TERM SIGNAL commands before we execute the
15725 signal, in case the signal shuts us down. We had a patch in
15726 0.1.2.1-alpha that tried to do this by queueing the response on
15727 the connection's buffer before shutting down, but that really
15728 isn't the same thing at all. Bug located by Matt Edman.
15730 o Minor bugfixes (misc):
15731 - Correctly check for bad options to the "PublishServerDescriptor"
15732 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
15733 - Stop leaking memory on failing case of base32_decode, and make
15734 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
15735 - Don't try to download extrainfo documents when we're trying to
15736 fetch enough directory info to build a circuit: having enough
15737 info should get priority. Bugfix on 0.2.0.x.
15738 - Don't complain that "your server has not managed to confirm that its
15739 ports are reachable" if we haven't been able to build any circuits
15740 yet. Bug found by spending four hours without a v3 consensus. Bugfix
15742 - Detect the reason for failing to mmap a descriptor file we just
15743 wrote, and give a more useful log message. Fixes bug 533. Bugfix
15746 o Code simplifications and refactoring:
15747 - Remove support for the old bw_accounting file: we've been storing
15748 bandwidth accounting information in the state file since
15749 0.1.2.5-alpha. This may result in bandwidth accounting errors
15750 if you try to upgrade from 0.1.1.x or earlier, or if you try to
15751 downgrade to 0.1.1.x or earlier.
15752 - New convenience code to locate a file within the DataDirectory.
15753 - Move non-authority functionality out of dirvote.c.
15754 - Refactor the arguments for router_pick_{directory_|trusteddir}server
15755 so that they all take the same named flags.
15758 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
15759 Unix users an easy way to script their Tor process (e.g. by
15760 adjusting bandwidth based on the time of the day).
15763 Changes in version 0.2.0.8-alpha - 2007-10-12
15764 This eighth development snapshot fixes a crash bug that's been bothering
15765 us since February 2007, lets bridge authorities store a list of bridge
15766 descriptors they've seen, gets v3 directory voting closer to working,
15767 starts caching v3 directory consensus documents on directory mirrors,
15768 and fixes a variety of smaller issues including some minor memory leaks.
15770 o Major features (router descriptor cache):
15771 - Store routers in a file called cached-descriptors instead of in
15772 cached-routers. Initialize cached-descriptors from cached-routers
15773 if the old format is around. The new format allows us to store
15774 annotations along with descriptors.
15775 - Use annotations to record the time we received each descriptor, its
15776 source, and its purpose.
15777 - Disable the SETROUTERPURPOSE controller command: it is now
15779 - Controllers should now specify cache=no or cache=yes when using
15780 the +POSTDESCRIPTOR command.
15781 - Bridge authorities now write bridge descriptors to disk, meaning
15782 we can export them to other programs and begin distributing them
15785 o Major features (directory authorities):
15786 - When a v3 authority is missing votes or signatures, it now tries
15788 - Directory authorities track weighted fractional uptime as well as
15789 weighted mean-time-between failures. WFU is suitable for deciding
15790 whether a node is "usually up", while MTBF is suitable for deciding
15791 whether a node is "likely to stay up." We need both, because
15792 "usually up" is a good requirement for guards, while "likely to
15793 stay up" is a good requirement for long-lived connections.
15795 o Major features (v3 directory system):
15796 - Caches now download v3 network status documents as needed,
15797 and download the descriptors listed in them.
15798 - All hosts now attempt to download and keep fresh v3 authority
15799 certificates, and re-attempt after failures.
15800 - More internal-consistency checks for vote parsing.
15802 o Major bugfixes (crashes):
15803 - If a connection is shut down abruptly because of something that
15804 happened inside connection_flushed_some(), do not call
15805 connection_finished_flushing(). Should fix bug 451. Bugfix on
15808 o Major bugfixes (performance):
15809 - Fix really bad O(n^2) performance when parsing a long list of
15810 routers: Instead of searching the entire list for an "extra-info "
15811 string which usually wasn't there, once for every routerinfo
15812 we read, just scan lines forward until we find one we like.
15814 - When we add data to a write buffer in response to the data on that
15815 write buffer getting low because of a flush, do not consider the
15816 newly added data as a candidate for immediate flushing, but rather
15817 make it wait until the next round of writing. Otherwise, we flush
15818 and refill recursively, and a single greedy TLS connection can
15819 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
15821 o Minor features (v3 authority system):
15822 - Add more ways for tools to download the votes that lead to the
15824 - Send a 503 when low on bandwidth and a vote, consensus, or
15825 certificate is requested.
15826 - If-modified-since is now implemented properly for all kinds of
15827 certificate requests.
15829 o Minor bugfixes (network statuses):
15830 - Tweak the implementation of proposal 109 slightly: allow at most
15831 two Tor servers on the same IP address, except if it's the location
15832 of a directory authority, in which case allow five. Bugfix on
15835 o Minor bugfixes (controller):
15836 - When sending a status event to the controller telling it that an
15837 OR address is reachable, set the port correctly. (Previously we
15838 were reporting the dir port.) Bugfix on 0.1.2.x.
15840 o Minor bugfixes (v3 directory system):
15841 - Fix logic to look up a cert by its signing key digest. Bugfix on
15843 - Only change the reply to a vote to "OK" if it's not already
15844 set. This gets rid of annoying "400 OK" log messages, which may
15845 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
15846 - When we get a valid consensus, recompute the voting schedule.
15847 - Base the valid-after time of a vote on the consensus voting
15848 schedule, not on our preferred schedule.
15849 - Make the return values and messages from signature uploads and
15850 downloads more sensible.
15851 - Fix a memory leak when serving votes and consensus documents, and
15852 another when serving certificates.
15854 o Minor bugfixes (performance):
15855 - Use a slightly simpler string hashing algorithm (copying Python's
15856 instead of Java's) and optimize our digest hashing algorithm to take
15857 advantage of 64-bit platforms and to remove some possibly-costly
15859 - Fix a minor memory leak whenever we parse guards from our state
15860 file. Bugfix on 0.2.0.7-alpha.
15861 - Fix a minor memory leak whenever we write out a file. Bugfix on
15863 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
15864 command. Bugfix on 0.2.0.5-alpha.
15866 o Minor bugfixes (portability):
15867 - On some platforms, accept() can return a broken address. Detect
15868 this more quietly, and deal accordingly. Fixes bug 483.
15869 - Stop calling tor_strlower() on uninitialized memory in some cases.
15870 Bugfix in 0.2.0.7-alpha.
15872 o Minor bugfixes (usability):
15873 - Treat some 403 responses from directory servers as INFO rather than
15874 WARN-severity events.
15875 - It's not actually an error to find a non-pending entry in the DNS
15876 cache when canceling a pending resolve. Don't log unless stuff is
15877 fishy. Resolves bug 463.
15879 o Minor bugfixes (anonymity):
15880 - Never report that we've used more bandwidth than we're willing to
15881 relay: it leaks how much non-relay traffic we're using. Resolves
15883 - When looking for a circuit to cannibalize, consider family as well
15884 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
15885 circuit cannibalization).
15887 o Code simplifications and refactoring:
15888 - Make a bunch of functions static. Remove some dead code.
15889 - Pull out about a third of the really big routerlist.c; put it in a
15890 new module, networkstatus.c.
15891 - Merge the extra fields in local_routerstatus_t back into
15892 routerstatus_t: we used to need one routerstatus_t for each
15893 authority's opinion, plus a local_routerstatus_t for the locally
15894 computed consensus opinion. To save space, we put the locally
15895 modified fields into local_routerstatus_t, and only the common
15896 stuff into routerstatus_t. But once v3 directories are in use,
15897 clients and caches will no longer need to hold authority opinions;
15898 thus, the rationale for keeping the types separate is now gone.
15899 - Make the code used to reschedule and reattempt downloads more
15901 - Turn all 'Are we a directory server/mirror?' logic into a call to
15903 - Remove the code to generate the oldest (v1) directory format.
15904 The code has been disabled since 0.2.0.5-alpha.
15907 Changes in version 0.2.0.7-alpha - 2007-09-21
15908 This seventh development snapshot makes bridges work again, makes bridge
15909 authorities work for the first time, fixes two huge performance flaws
15910 in hidden services, and fixes a variety of minor issues.
15912 o New directory authorities:
15913 - Set up moria1 and tor26 as the first v3 directory authorities. See
15914 doc/spec/dir-spec.txt for details on the new directory design.
15916 o Major bugfixes (crashes):
15917 - Fix possible segfaults in functions called from
15918 rend_process_relay_cell(). Bugfix on 0.1.2.x.
15920 o Major bugfixes (bridges):
15921 - Fix a bug that made servers send a "404 Not found" in response to
15922 attempts to fetch their server descriptor. This caused Tor servers
15923 to take many minutes to establish reachability for their DirPort,
15924 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
15925 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
15926 users configure that and specify a bridge with an identity
15927 fingerprint, now they will lookup the bridge descriptor at the
15928 default bridge authority via a one-hop tunnel, but once circuits
15929 are established they will switch to a three-hop tunnel for later
15930 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
15932 o Major bugfixes (hidden services):
15933 - Hidden services were choosing introduction points uniquely by
15934 hexdigest, but when constructing the hidden service descriptor
15935 they merely wrote the (potentially ambiguous) nickname.
15936 - Clients now use the v2 intro format for hidden service
15937 connections: they specify their chosen rendezvous point by identity
15938 digest rather than by (potentially ambiguous) nickname. Both
15939 are bugfixes on 0.1.2.x, and they could speed up hidden service
15940 connections dramatically. Thanks to Karsten Loesing.
15942 o Minor features (security):
15943 - As a client, do not believe any server that tells us that an
15944 address maps to an internal address space.
15945 - Make it possible to enable HashedControlPassword and
15946 CookieAuthentication at the same time.
15948 o Minor features (guard nodes):
15949 - Tag every guard node in our state file with the version that
15950 we believe added it, or with our own version if we add it. This way,
15951 if a user temporarily runs an old version of Tor and then switches
15952 back to a new one, she doesn't automatically lose her guards.
15954 o Minor features (speed):
15955 - When implementing AES counter mode, update only the portions of the
15956 counter buffer that need to change, and don't keep separate
15957 network-order and host-order counters when they are the same (i.e.,
15958 on big-endian hosts.)
15960 o Minor features (controller):
15961 - Accept LF instead of CRLF on controller, since some software has a
15962 hard time generating real Internet newlines.
15963 - Add GETINFO values for the server status events
15964 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
15967 o Removed features:
15968 - Routers no longer include bandwidth-history lines in their
15969 descriptors; this information is already available in extra-info
15970 documents, and including it in router descriptors took up 60%
15971 (!) of compressed router descriptor downloads. Completes
15972 implementation of proposal 104.
15973 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
15974 and TorControl.py, as they use the old v0 controller protocol,
15975 and are obsoleted by TorFlow anyway.
15976 - Drop support for v1 rendezvous descriptors, since we never used
15977 them anyway, and the code has probably rotted by now. Based on
15978 patch from Karsten Loesing.
15979 - On OSX, stop warning the user that kqueue support in libevent is
15980 "experimental", since it seems to have worked fine for ages.
15983 - When generating information telling us how to extend to a given
15984 router, do not try to include the nickname if it is absent. Fixes
15985 bug 467. Bugfix on 0.2.0.3-alpha.
15986 - Fix a user-triggerable (but not remotely-triggerable) segfault
15987 in expand_filename(). Bugfix on 0.1.2.x.
15988 - Fix a memory leak when freeing incomplete requests from DNSPort.
15989 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
15990 - Don't try to access (or alter) the state file when running
15991 --list-fingerprint or --verify-config or --hash-password. (Resolves
15992 bug 499.) Bugfix on 0.1.2.x.
15993 - Servers used to decline to publish their DirPort if their
15994 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
15995 were below a threshold. Now they only look at BandwidthRate and
15996 RelayBandwidthRate. Bugfix on 0.1.2.x.
15997 - Remove an optimization in the AES counter-mode code that assumed
15998 that the counter never exceeded 2^68. When the counter can be set
15999 arbitrarily as an IV (as it is by Karsten's new hidden services
16000 code), this assumption no longer holds. Bugfix on 0.1.2.x.
16001 - Resume listing "AUTHORITY" flag for authorities in network status.
16002 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
16004 o Code simplifications and refactoring:
16005 - Revamp file-writing logic so we don't need to have the entire
16006 contents of a file in memory at once before we write to disk. Tor,
16008 - Turn "descriptor store" into a full-fledged type.
16009 - Move all NT services code into a separate source file.
16010 - Unify all code that computes medians, percentile elements, etc.
16011 - Get rid of a needless malloc when parsing address policies.
16014 Changes in version 0.1.2.17 - 2007-08-30
16015 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
16016 X bundles. Vidalia 0.0.14 makes authentication required for the
16017 ControlPort in the default configuration, which addresses important
16018 security risks. Everybody who uses Vidalia (or another controller)
16021 In addition, this Tor update fixes major load balancing problems with
16022 path selection, which should speed things up a lot once many people
16025 o Major bugfixes (security):
16026 - We removed support for the old (v0) control protocol. It has been
16027 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
16028 become more of a headache than it's worth.
16030 o Major bugfixes (load balancing):
16031 - When choosing nodes for non-guard positions, weight guards
16032 proportionally less, since they already have enough load. Patch
16034 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
16035 will allow fast Tor servers to get more attention.
16036 - When we're upgrading from an old Tor version, forget our current
16037 guards and pick new ones according to the new weightings. These
16038 three load balancing patches could raise effective network capacity
16039 by a factor of four. Thanks to Mike Perry for measurements.
16041 o Major bugfixes (stream expiration):
16042 - Expire not-yet-successful application streams in all cases if
16043 they've been around longer than SocksTimeout. Right now there are
16044 some cases where the stream will live forever, demanding a new
16045 circuit every 15 seconds. Fixes bug 454; reported by lodger.
16047 o Minor features (controller):
16048 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
16049 is valid before any authentication has been received. It tells
16050 a controller what kind of authentication is expected, and what
16051 protocol is spoken. Implements proposal 119.
16053 o Minor bugfixes (performance):
16054 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
16055 greatly speeding up loading cached-routers from disk on startup.
16056 - Disable sentinel-based debugging for buffer code: we squashed all
16057 the bugs that this was supposed to detect a long time ago, and now
16058 its only effect is to change our buffer sizes from nice powers of
16059 two (which platform mallocs tend to like) to values slightly over
16060 powers of two (which make some platform mallocs sad).
16062 o Minor bugfixes (misc):
16063 - If exit bandwidth ever exceeds one third of total bandwidth, then
16064 use the correct formula to weight exit nodes when choosing paths.
16065 Based on patch from Mike Perry.
16066 - Choose perfectly fairly among routers when choosing by bandwidth and
16067 weighting by fraction of bandwidth provided by exits. Previously, we
16068 would choose with only approximate fairness, and correct ourselves
16069 if we ran off the end of the list.
16070 - If we require CookieAuthentication but we fail to write the
16071 cookie file, we would warn but not exit, and end up in a state
16072 where no controller could authenticate. Now we exit.
16073 - If we require CookieAuthentication, stop generating a new cookie
16074 every time we change any piece of our config.
16075 - Refuse to start with certain directory authority keys, and
16076 encourage people using them to stop.
16077 - Terminate multi-line control events properly. Original patch
16079 - Fix a minor memory leak when we fail to find enough suitable
16080 servers to choose a circuit.
16081 - Stop leaking part of the descriptor when we run into a particularly
16082 unparseable piece of it.
16085 Changes in version 0.2.0.6-alpha - 2007-08-26
16086 This sixth development snapshot features a new Vidalia version in the
16087 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
16088 the ControlPort in the default configuration, which addresses important
16091 In addition, this snapshot fixes major load balancing problems
16092 with path selection, which should speed things up a lot once many
16093 people have upgraded. The directory authorities also use a new
16094 mean-time-between-failure approach to tracking which servers are stable,
16095 rather than just looking at the most recent uptime.
16097 o New directory authorities:
16098 - Set up Tonga as the default bridge directory authority.
16101 - Directory authorities now track servers by weighted
16102 mean-times-between-failures. When we have 4 or more days of data,
16103 use measured MTBF rather than declared uptime to decide whether
16104 to call a router Stable. Implements proposal 108.
16106 o Major bugfixes (load balancing):
16107 - When choosing nodes for non-guard positions, weight guards
16108 proportionally less, since they already have enough load. Patch
16110 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
16111 will allow fast Tor servers to get more attention.
16112 - When we're upgrading from an old Tor version, forget our current
16113 guards and pick new ones according to the new weightings. These
16114 three load balancing patches could raise effective network capacity
16115 by a factor of four. Thanks to Mike Perry for measurements.
16117 o Major bugfixes (descriptor parsing):
16118 - Handle unexpected whitespace better in malformed descriptors. Bug
16119 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
16122 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
16123 GETINFO for Torstat to use until it can switch to using extrainfos.
16124 - Optionally (if built with -DEXPORTMALLINFO) export the output
16125 of mallinfo via http, as tor/mallinfo.txt. Only accessible
16129 - Do not intermix bridge routers with controller-added
16130 routers. (Bugfix on 0.2.0.x)
16131 - Do not fail with an assert when accept() returns an unexpected
16132 address family. Addresses but does not wholly fix bug 483. (Bugfix
16134 - Let directory authorities startup even when they can't generate
16135 a descriptor immediately, e.g. because they don't know their
16137 - Stop putting the authentication cookie in a file called "0"
16138 in your working directory if you don't specify anything for the
16139 new CookieAuthFile option. Reported by Matt Edman.
16140 - Make it possible to read the PROTOCOLINFO response in a way that
16141 conforms to our control-spec. Reported by Matt Edman.
16142 - Fix a minor memory leak when we fail to find enough suitable
16143 servers to choose a circuit. Bugfix on 0.1.2.x.
16144 - Stop leaking part of the descriptor when we run into a particularly
16145 unparseable piece of it. Bugfix on 0.1.2.x.
16146 - Unmap the extrainfo cache file on exit.
16149 Changes in version 0.2.0.5-alpha - 2007-08-19
16150 This fifth development snapshot fixes compilation on Windows again;
16151 fixes an obnoxious client-side bug that slowed things down and put
16152 extra load on the network; gets us closer to using the v3 directory
16153 voting scheme; makes it easier for Tor controllers to use cookie-based
16154 authentication; and fixes a variety of other bugs.
16156 o Removed features:
16157 - Version 1 directories are no longer generated in full. Instead,
16158 authorities generate and serve "stub" v1 directories that list
16159 no servers. This will stop Tor versions 0.1.0.x and earlier from
16160 working, but (for security reasons) nobody should be running those
16163 o Major bugfixes (compilation, 0.2.0.x):
16164 - Try to fix Win32 compilation again: improve checking for IPv6 types.
16165 - Try to fix MSVC compilation: build correctly on platforms that do
16166 not define s6_addr16 or s6_addr32.
16167 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
16170 o Major bugfixes (stream expiration):
16171 - Expire not-yet-successful application streams in all cases if
16172 they've been around longer than SocksTimeout. Right now there are
16173 some cases where the stream will live forever, demanding a new
16174 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
16175 reported by lodger.
16177 o Minor features (directory servers):
16178 - When somebody requests a list of statuses or servers, and we have
16179 none of those, return a 404 rather than an empty 200.
16181 o Minor features (directory voting):
16182 - Store v3 consensus status consensuses on disk, and reload them
16185 o Minor features (security):
16186 - Warn about unsafe ControlPort configurations.
16187 - Refuse to start with certain directory authority keys, and
16188 encourage people using them to stop.
16190 o Minor features (controller):
16191 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
16192 is valid before any authentication has been received. It tells
16193 a controller what kind of authentication is expected, and what
16194 protocol is spoken. Implements proposal 119.
16195 - New config option CookieAuthFile to choose a new location for the
16196 cookie authentication file, and config option
16197 CookieAuthFileGroupReadable to make it group-readable.
16199 o Minor features (unit testing):
16200 - Add command-line arguments to unit-test executable so that we can
16201 invoke any chosen test from the command line rather than having
16202 to run the whole test suite at once; and so that we can turn on
16203 logging for the unit tests.
16205 o Minor bugfixes (on 0.1.2.x):
16206 - If we require CookieAuthentication but we fail to write the
16207 cookie file, we would warn but not exit, and end up in a state
16208 where no controller could authenticate. Now we exit.
16209 - If we require CookieAuthentication, stop generating a new cookie
16210 every time we change any piece of our config.
16211 - When loading bandwidth history, do not believe any information in
16212 the future. Fixes bug 434.
16213 - When loading entry guard information, do not believe any information
16215 - When we have our clock set far in the future and generate an
16216 onion key, then re-set our clock to be correct, we should not stop
16217 the onion key from getting rotated.
16218 - Clean up torrc sample config file.
16219 - Do not automatically run configure from autogen.sh. This
16220 non-standard behavior tended to annoy people who have built other
16223 o Minor bugfixes (on 0.2.0.x):
16224 - Fix a bug with AutomapHostsOnResolve that would always cause
16225 the second request to fail. Bug reported by Kate. Bugfix on
16227 - Fix a bug in ADDRMAP controller replies that would sometimes
16228 try to print a NULL. Patch from tup.
16229 - Read v3 directory authority keys from the right location.
16230 - Numerous bugfixes to directory voting code.
16233 Changes in version 0.1.2.16 - 2007-08-01
16234 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
16235 remote attacker in certain situations to rewrite the user's torrc
16236 configuration file. This can completely compromise anonymity of users
16237 in most configurations, including those running the Vidalia bundles,
16238 TorK, etc. Or worse.
16240 o Major security fixes:
16241 - Close immediately after missing authentication on control port;
16242 do not allow multiple authentication attempts.
16245 Changes in version 0.2.0.4-alpha - 2007-08-01
16246 This fourth development snapshot fixes a critical security vulnerability
16247 for most users, specifically those running Vidalia, TorK, etc. Everybody
16248 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
16250 o Major security fixes:
16251 - Close immediately after missing authentication on control port;
16252 do not allow multiple authentication attempts.
16254 o Major bugfixes (compilation):
16255 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
16258 o Minor features (performance):
16259 - Be even more aggressive about releasing RAM from small
16260 empty buffers. Thanks to our free-list code, this shouldn't be too
16261 performance-intensive.
16262 - Disable sentinel-based debugging for buffer code: we squashed all
16263 the bugs that this was supposed to detect a long time ago, and
16264 now its only effect is to change our buffer sizes from nice
16265 powers of two (which platform mallocs tend to like) to values
16266 slightly over powers of two (which make some platform mallocs sad).
16267 - Log malloc statistics from mallinfo() on platforms where it
16271 Changes in version 0.2.0.3-alpha - 2007-07-29
16272 This third development snapshot introduces new experimental
16273 blocking-resistance features and a preliminary version of the v3
16274 directory voting design, and includes many other smaller features
16278 - The first pieces of our "bridge" design for blocking-resistance
16279 are implemented. People can run bridge directory authorities;
16280 people can run bridges; and people can configure their Tor clients
16281 with a set of bridges to use as the first hop into the Tor network.
16282 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
16284 - Create listener connections before we setuid to the configured
16285 User and Group. Now non-Windows users can choose port values
16286 under 1024, start Tor as root, and have Tor bind those ports
16287 before it changes to another UID. (Windows users could already
16289 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
16290 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
16291 on "vserver" accounts. (Patch from coderman.)
16292 - Be even more aggressive about separating local traffic from relayed
16293 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
16295 o Major features (experimental):
16296 - First cut of code for "v3 dir voting": directory authorities will
16297 vote on a common network status document rather than each publishing
16298 their own opinion. This code needs more testing and more corner-case
16299 handling before it's ready for use.
16302 - Directory authorities now call routers Fast if their bandwidth is
16303 at least 100KB/s, and consider their bandwidth adequate to be a
16304 Guard if it is at least 250KB/s, no matter the medians. This fix
16305 complements proposal 107. [Bugfix on 0.1.2.x]
16306 - Directory authorities now never mark more than 3 servers per IP as
16307 Valid and Running. (Implements proposal 109, by Kevin Bauer and
16309 - Minor change to organizationName and commonName generation
16310 procedures in TLS certificates during Tor handshakes, to invalidate
16311 some earlier censorware approaches. This is not a long-term
16312 solution, but applying it will give us a bit of time to look into
16313 the epidemiology of countermeasures as they spread.
16315 o Major bugfixes (directory):
16316 - Rewrite directory tokenization code to never run off the end of
16317 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
16319 o Minor features (controller):
16320 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
16321 match requests to applications. (Patch from Robert Hogan.)
16322 - Report address and port correctly on connections to DNSPort. (Patch
16323 from Robert Hogan.)
16324 - Add a RESOLVE command to launch hostname lookups. (Original patch
16325 from Robert Hogan.)
16326 - Add GETINFO status/enough-dir-info to let controllers tell whether
16327 Tor has downloaded sufficient directory information. (Patch
16329 - You can now use the ControlSocket option to tell Tor to listen for
16330 controller connections on Unix domain sockets on systems that
16331 support them. (Patch from Peter Palfrader.)
16332 - STREAM NEW events are generated for DNSPort requests and for
16333 tunneled directory connections. (Patch from Robert Hogan.)
16334 - New "GETINFO address-mappings/*" command to get address mappings
16335 with expiry information. "addr-mappings/*" is now deprecated.
16338 o Minor features (misc):
16339 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
16341 - The tor-gencert tool for v3 directory authorities now creates all
16342 files as readable to the file creator only, and write-protects
16343 the authority identity key.
16344 - When dumping memory usage, list bytes used in buffer memory
16346 - When running with dmalloc, dump more stats on hup and on exit.
16347 - Directory authorities now fail quickly and (relatively) harmlessly
16348 if they generate a network status document that is somehow
16351 o Traffic load balancing improvements:
16352 - If exit bandwidth ever exceeds one third of total bandwidth, then
16353 use the correct formula to weight exit nodes when choosing paths.
16354 (Based on patch from Mike Perry.)
16355 - Choose perfectly fairly among routers when choosing by bandwidth and
16356 weighting by fraction of bandwidth provided by exits. Previously, we
16357 would choose with only approximate fairness, and correct ourselves
16358 if we ran off the end of the list. [Bugfix on 0.1.2.x]
16360 o Performance improvements:
16361 - Be more aggressive with freeing buffer RAM or putting it on the
16363 - Use Critical Sections rather than Mutexes for synchronizing threads
16364 on win32; Mutexes are heavier-weight, and designed for synchronizing
16367 o Deprecated and removed features:
16368 - RedirectExits is now deprecated.
16369 - Stop allowing address masks that do not correspond to bit prefixes.
16370 We have warned about these for a really long time; now it's time
16371 to reject them. (Patch from croup.)
16373 o Minor bugfixes (directory):
16374 - Fix another crash bug related to extra-info caching. (Bug found by
16375 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
16376 - Directories no longer return a "304 not modified" when they don't
16377 have the networkstatus the client asked for. Also fix a memory
16378 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
16379 - We had accidentally labelled 0.1.2.x directory servers as not
16380 suitable for begin_dir requests, and had labelled no directory
16381 servers as suitable for uploading extra-info documents. [Bugfix
16384 o Minor bugfixes (dns):
16385 - Fix a crash when DNSPort is set more than once. (Patch from Robert
16386 Hogan.) [Bugfix on 0.2.0.2-alpha]
16387 - Add DNSPort connections to the global connection list, so that we
16388 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
16390 - Fix a dangling reference that could lead to a crash when DNSPort is
16391 changed or closed (Patch from Robert Hogan.) [Bugfix on
16394 o Minor bugfixes (controller):
16395 - Provide DNS expiry times in GMT, not in local time. For backward
16396 compatibility, ADDRMAP events only provide GMT expiry in an extended
16397 field. "GETINFO address-mappings" always does the right thing.
16398 - Use CRLF line endings properly in NS events.
16399 - Terminate multi-line control events properly. (Original patch
16400 from tup.) [Bugfix on 0.1.2.x-alpha]
16401 - Do not include spaces in SOURCE_ADDR fields in STREAM
16402 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
16405 Changes in version 0.1.2.15 - 2007-07-17
16406 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
16407 problems, fixes compilation on BSD, and fixes a variety of other
16408 bugs. Everybody should upgrade.
16410 o Major bugfixes (compilation):
16411 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
16413 o Major bugfixes (crashes):
16414 - Try even harder not to dereference the first character after
16415 an mmap(). Reported by lodger.
16416 - Fix a crash bug in directory authorities when we re-number the
16417 routerlist while inserting a new router.
16418 - When the cached-routers file is an even multiple of the page size,
16419 don't run off the end and crash. (Fixes bug 455; based on idea
16421 - Fix eventdns.c behavior on Solaris: It is critical to include
16422 orconfig.h _before_ sys/types.h, so that we can get the expected
16423 definition of _FILE_OFFSET_BITS.
16425 o Major bugfixes (security):
16426 - Fix a possible buffer overrun when using BSD natd support. Bug
16428 - When sending destroy cells from a circuit's origin, don't include
16429 the reason for tearing down the circuit. The spec says we didn't,
16430 and now we actually don't. Reported by lodger.
16431 - Keep streamids from different exits on a circuit separate. This
16432 bug may have allowed other routers on a given circuit to inject
16433 cells into streams. Reported by lodger; fixes bug 446.
16434 - If there's a never-before-connected-to guard node in our list,
16435 never choose any guards past it. This way we don't expand our
16436 guard list unless we need to.
16438 o Minor bugfixes (guard nodes):
16439 - Weight guard selection by bandwidth, so that low-bandwidth nodes
16440 don't get overused as guards.
16442 o Minor bugfixes (directory):
16443 - Correctly count the number of authorities that recommend each
16444 version. Previously, we were under-counting by 1.
16445 - Fix a potential crash bug when we load many server descriptors at
16446 once and some of them make others of them obsolete. Fixes bug 458.
16448 o Minor bugfixes (hidden services):
16449 - Stop tearing down the whole circuit when the user asks for a
16450 connection to a port that the hidden service didn't configure.
16453 o Minor bugfixes (misc):
16454 - On Windows, we were preventing other processes from reading
16455 cached-routers while Tor was running. Reported by janbar.
16456 - Fix a possible (but very unlikely) bug in picking routers by
16457 bandwidth. Add a log message to confirm that it is in fact
16458 unlikely. Patch from lodger.
16459 - Backport a couple of memory leak fixes.
16460 - Backport miscellaneous cosmetic bugfixes.
16463 Changes in version 0.2.0.2-alpha - 2007-06-02
16464 o Major bugfixes on 0.2.0.1-alpha:
16465 - Fix an assertion failure related to servers without extra-info digests.
16466 Resolves bugs 441 and 442.
16468 o Minor features (directory):
16469 - Support "If-Modified-Since" when answering HTTP requests for
16470 directories, running-routers documents, and network-status documents.
16471 (There's no need to support it for router descriptors, since those
16472 are downloaded by descriptor digest.)
16474 o Minor build issues:
16475 - Clear up some MIPSPro compiler warnings.
16476 - When building from a tarball on a machine that happens to have SVK
16477 installed, report the micro-revision as whatever version existed
16478 in the tarball, not as "x".
16481 Changes in version 0.2.0.1-alpha - 2007-06-01
16482 This early development snapshot provides new features for people running
16483 Tor as both a client and a server (check out the new RelayBandwidth
16484 config options); lets Tor run as a DNS proxy; and generally moves us
16485 forward on a lot of fronts.
16487 o Major features, server usability:
16488 - New config options RelayBandwidthRate and RelayBandwidthBurst:
16489 a separate set of token buckets for relayed traffic. Right now
16490 relayed traffic is defined as answers to directory requests, and
16491 OR connections that don't have any local circuits on them.
16493 o Major features, client usability:
16494 - A client-side DNS proxy feature to replace the need for
16495 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
16496 for DNS requests on port 9999, use the Tor network to resolve them
16497 anonymously, and send the reply back like a regular DNS server.
16498 The code still only implements a subset of DNS.
16499 - Make PreferTunneledDirConns and TunnelDirConns work even when
16500 we have no cached directory info. This means Tor clients can now
16501 do all of their connections protected by TLS.
16503 o Major features, performance and efficiency:
16504 - Directory authorities accept and serve "extra info" documents for
16505 routers. These documents contain fields from router descriptors
16506 that aren't usually needed, and that use a lot of excess
16507 bandwidth. Once these fields are removed from router descriptors,
16508 the bandwidth savings should be about 60%. [Partially implements
16510 - Servers upload extra-info documents to any authority that accepts
16511 them. Authorities (and caches that have been configured to download
16512 extra-info documents) download them as needed. [Partially implements
16514 - Change the way that Tor buffers data that it is waiting to write.
16515 Instead of queueing data cells in an enormous ring buffer for each
16516 client->OR or OR->OR connection, we now queue cells on a separate
16517 queue for each circuit. This lets us use less slack memory, and
16518 will eventually let us be smarter about prioritizing different kinds
16520 - Use memory pools to allocate cells with better speed and memory
16521 efficiency, especially on platforms where malloc() is inefficient.
16522 - Stop reading on edge connections when their corresponding circuit
16523 buffers are full; start again as the circuits empty out.
16525 o Major features, other:
16526 - Add an HSAuthorityRecordStats option that hidden service authorities
16527 can use to track statistics of overall hidden service usage without
16528 logging information that would be very useful to an attacker.
16529 - Start work implementing multi-level keys for directory authorities:
16530 Add a standalone tool to generate key certificates. (Proposal 103.)
16533 - Directory authorities now call routers Stable if they have an
16534 uptime of at least 30 days, even if that's not the median uptime
16535 in the network. Implements proposal 107, suggested by Kevin Bauer
16538 o Minor fixes (resource management):
16539 - Count the number of open sockets separately from the number
16540 of active connection_t objects. This will let us avoid underusing
16541 our allocated connection limit.
16542 - We no longer use socket pairs to link an edge connection to an
16543 anonymous directory connection or a DirPort test connection.
16544 Instead, we track the link internally and transfer the data
16545 in-process. This saves two sockets per "linked" connection (at the
16546 client and at the server), and avoids the nasty Windows socketpair()
16548 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
16549 for every single inactive connection_t. Free items from the
16550 4k/16k-buffer free lists when they haven't been used for a while.
16552 o Minor features (build):
16553 - Make autoconf search for libevent, openssl, and zlib consistently.
16554 - Update deprecated macros in configure.in.
16555 - When warning about missing headers, tell the user to let us
16556 know if the compile succeeds anyway, so we can downgrade the
16558 - Include the current subversion revision as part of the version
16559 string: either fetch it directly if we're in an SVN checkout, do
16560 some magic to guess it if we're in an SVK checkout, or use
16561 the last-detected version if we're building from a .tar.gz.
16562 Use this version consistently in log messages.
16564 o Minor features (logging):
16565 - Always prepend "Bug: " to any log message about a bug.
16566 - Put a platform string (e.g. "Linux i686") in the startup log
16567 message, so when people paste just their logs, we know if it's
16568 OpenBSD or Windows or what.
16569 - When logging memory usage, break down memory used in buffers by
16572 o Minor features (directory system):
16573 - New config option V2AuthoritativeDirectory that all directory
16574 authorities should set. This will let future authorities choose
16575 not to serve V2 directory information.
16576 - Directory authorities allow multiple router descriptors and/or extra
16577 info documents to be uploaded in a single go. This will make
16578 implementing proposal 104 simpler.
16580 o Minor features (controller):
16581 - Add a new config option __DisablePredictedCircuits designed for
16582 use by the controller, when we don't want Tor to build any circuits
16584 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
16585 so we can exit from the middle of the circuit.
16586 - Implement "getinfo status/circuit-established".
16587 - Implement "getinfo status/version/..." so a controller can tell
16588 whether the current version is recommended, and whether any versions
16589 are good, and how many authorities agree. (Patch from shibz.)
16591 o Minor features (hidden services):
16592 - Allow multiple HiddenServicePort directives with the same virtual
16593 port; when they occur, the user is sent round-robin to one
16594 of the target ports chosen at random. Partially fixes bug 393 by
16595 adding limited ad-hoc round-robining.
16597 o Minor features (other):
16599 - Add a new AutomapHostsOnResolve option: when it is enabled, any
16600 resolve request for hosts matching a given pattern causes Tor to
16601 generate an internal virtual address mapping for that host. This
16602 allows DNSPort to work sensibly with hidden service users. By
16603 default, .exit and .onion addresses are remapped; the list of
16604 patterns can be reconfigured with AutomapHostsSuffixes.
16605 - Add an "-F" option to tor-resolve to force a resolve for a .onion
16606 address. Thanks to the AutomapHostsOnResolve option, this is no
16607 longer a completely silly thing to do.
16608 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
16609 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
16610 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
16611 minus 1 byte: the actual maximum declared bandwidth.
16613 o Removed features:
16614 - Removed support for the old binary "version 0" controller protocol.
16615 This has been deprecated since 0.1.1, and warnings have been issued
16616 since 0.1.2. When we encounter a v0 control message, we now send
16617 back an error and close the connection.
16618 - Remove the old "dns worker" server DNS code: it hasn't been default
16619 since 0.1.2.2-alpha, and all the servers seem to be using the new
16622 o Minor bugfixes (portability):
16623 - Even though Windows is equally happy with / and \ as path separators,
16624 try to use \ consistently on Windows and / consistently on Unix: it
16625 makes the log messages nicer.
16626 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
16627 - Read resolv.conf files correctly on platforms where read() returns
16628 partial results on small file reads.
16630 o Minor bugfixes (directory):
16631 - Correctly enforce that elements of directory objects do not appear
16632 more often than they are allowed to appear.
16633 - When we are reporting the DirServer line we just parsed, we were
16634 logging the second stanza of the key fingerprint, not the first.
16636 o Minor bugfixes (logging):
16637 - When we hit an EOF on a log (probably because we're shutting down),
16638 don't try to remove the log from the list: just mark it as
16639 unusable. (Bulletproofs against bug 222.)
16641 o Minor bugfixes (other):
16642 - In the exitlist script, only consider the most recently published
16643 server descriptor for each server. Also, when the user requests
16644 a list of servers that _reject_ connections to a given address,
16645 explicitly exclude the IPs that also have servers that accept
16646 connections to that address. (Resolves bug 405.)
16647 - Stop allowing hibernating servers to be "stable" or "fast".
16648 - On Windows, we were preventing other processes from reading
16649 cached-routers while Tor was running. (Reported by janbar)
16650 - Make the NodeFamilies config option work. (Reported by
16651 lodger -- it has never actually worked, even though we added it
16653 - Check return values from pthread_mutex functions.
16654 - Don't save non-general-purpose router descriptors to the disk cache,
16655 because we have no way of remembering what their purpose was when
16657 - Add even more asserts to hunt down bug 417.
16658 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
16659 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
16660 Add a log message to confirm that it is in fact unlikely.
16662 o Minor bugfixes (controller):
16663 - Make 'getinfo fingerprint' return a 551 error if we're not a
16664 server, so we match what the control spec claims we do. Reported
16666 - Fix a typo in an error message when extendcircuit fails that
16667 caused us to not follow the \r\n-based delimiter protocol. Reported
16670 o Code simplifications and refactoring:
16671 - Stop passing around circuit_t and crypt_path_t pointers that are
16672 implicit in other procedure arguments.
16673 - Drop the old code to choke directory connections when the
16674 corresponding OR connections got full: thanks to the cell queue
16675 feature, OR conns don't get full any more.
16676 - Make dns_resolve() handle attaching connections to circuits
16677 properly, so the caller doesn't have to.
16678 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
16679 - Keep the connection array as a dynamic smartlist_t, rather than as
16680 a fixed-sized array. This is important, as the number of connections
16681 is becoming increasingly decoupled from the number of sockets.
16684 Changes in version 0.1.2.14 - 2007-05-25
16685 Tor 0.1.2.14 changes the addresses of two directory authorities (this
16686 change especially affects those who serve or use hidden services),
16687 and fixes several other crash- and security-related bugs.
16689 o Directory authority changes:
16690 - Two directory authorities (moria1 and moria2) just moved to new
16691 IP addresses. This change will particularly affect those who serve
16692 or use hidden services.
16694 o Major bugfixes (crashes):
16695 - If a directory server runs out of space in the connection table
16696 as it's processing a begin_dir request, it will free the exit stream
16697 but leave it attached to the circuit, leading to unpredictable
16698 behavior. (Reported by seeess, fixes bug 425.)
16699 - Fix a bug in dirserv_remove_invalid() that would cause authorities
16700 to corrupt memory under some really unlikely scenarios.
16701 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
16702 - Avoid segfaults when reading from mmaped descriptor file. (Reported
16705 o Major bugfixes (security):
16706 - When choosing an entry guard for a circuit, avoid using guards
16707 that are in the same family as the chosen exit -- not just guards
16708 that are exactly the chosen exit. (Reported by lodger.)
16710 o Major bugfixes (resource management):
16711 - If a directory authority is down, skip it when deciding where to get
16712 networkstatus objects or descriptors. Otherwise we keep asking
16713 every 10 seconds forever. Fixes bug 384.
16714 - Count it as a failure if we fetch a valid network-status but we
16715 don't want to keep it. Otherwise we'll keep fetching it and keep
16716 not wanting to keep it. Fixes part of bug 422.
16717 - If all of our dirservers have given us bad or no networkstatuses
16718 lately, then stop hammering them once per minute even when we
16719 think they're failed. Fixes another part of bug 422.
16722 - Actually set the purpose correctly for descriptors inserted with
16723 purpose=controller.
16724 - When we have k non-v2 authorities in our DirServer config,
16725 we ignored the last k authorities in the list when updating our
16727 - Correctly back-off from requesting router descriptors that we are
16728 having a hard time downloading.
16729 - Read resolv.conf files correctly on platforms where read() returns
16730 partial results on small file reads.
16731 - Don't rebuild the entire router store every time we get 32K of
16732 routers: rebuild it when the journal gets very large, or when
16733 the gaps in the store get very large.
16736 - When routers publish SVN revisions in their router descriptors,
16737 authorities now include those versions correctly in networkstatus
16739 - Warn when using a version of libevent before 1.3b to run a server on
16740 OSX or BSD: these versions interact badly with userspace threads.
16743 Changes in version 0.1.2.13 - 2007-04-24
16744 This release features some major anonymity fixes, such as safer path
16745 selection; better client performance; faster bootstrapping, better
16746 address detection, and better DNS support for servers; write limiting as
16747 well as read limiting to make servers easier to run; and a huge pile of
16748 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
16750 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
16751 of the Freenode IRC network, remembering his patience and vision for
16752 free speech on the Internet.
16755 - Fix a memory leak when we ask for "all" networkstatuses and we
16756 get one we don't recognize.
16757 - Add more asserts to hunt down bug 417.
16758 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
16761 Changes in version 0.1.2.12-rc - 2007-03-16
16763 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
16764 directory information requested inside Tor connections (i.e. via
16765 begin_dir cells). It only triggered when the same connection was
16766 serving other data at the same time. Reported by seeess.
16769 - When creating a circuit via the controller, send a 'launched'
16770 event when we're done, so we follow the spec better.
16773 Changes in version 0.1.2.11-rc - 2007-03-15
16774 o Minor bugfixes (controller), reported by daejees:
16775 - Correct the control spec to match how the code actually responds
16776 to 'getinfo addr-mappings/*'.
16777 - The control spec described a GUARDS event, but the code
16778 implemented a GUARD event. Standardize on GUARD, but let people
16779 ask for GUARDS too.
16782 Changes in version 0.1.2.10-rc - 2007-03-07
16783 o Major bugfixes (Windows):
16784 - Do not load the NT services library functions (which may not exist)
16785 just to detect if we're a service trying to shut down. Now we run
16786 on Win98 and friends again.
16788 o Minor bugfixes (other):
16789 - Clarify a couple of log messages.
16790 - Fix a misleading socks5 error number.
16793 Changes in version 0.1.2.9-rc - 2007-03-02
16794 o Major bugfixes (Windows):
16795 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
16796 of the usual GCC "%llu". This prevents a bug when saving 64-bit
16797 int configuration values: the high-order 32 bits would get
16798 truncated. In particular, we were being bitten by the default
16799 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
16800 and maybe also bug 397.)
16802 o Minor bugfixes (performance):
16803 - Use OpenSSL's AES implementation on platforms where it's faster.
16804 This could save us as much as 10% CPU usage.
16806 o Minor bugfixes (server):
16807 - Do not rotate onion key immediately after setting it for the first
16810 o Minor bugfixes (directory authorities):
16811 - Stop calling servers that have been hibernating for a long time
16812 "stable". Also, stop letting hibernating or obsolete servers affect
16813 uptime and bandwidth cutoffs.
16814 - Stop listing hibernating servers in the v1 directory.
16816 o Minor bugfixes (hidden services):
16817 - Upload hidden service descriptors slightly less often, to reduce
16818 load on authorities.
16820 o Minor bugfixes (other):
16821 - Fix an assert that could trigger if a controller quickly set then
16822 cleared EntryNodes. Bug found by Udo van den Heuvel.
16823 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
16825 - Fix a potential race condition in the rpm installer. Found by
16827 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
16828 of 2 as indicating that the server is completely bad; it sometimes
16829 means that the server is just bad for the request in question. (may fix
16830 the last of bug 326.)
16831 - Disable encrypted directory connections when we don't have a server
16832 descriptor for the destination. We'll get this working again in
16836 Changes in version 0.1.2.8-beta - 2007-02-26
16837 o Major bugfixes (crashes):
16838 - Stop crashing when the controller asks us to resetconf more than
16839 one config option at once. (Vidalia 0.0.11 does this.)
16840 - Fix a crash that happened on Win98 when we're given command-line
16841 arguments: don't try to load NT service functions from advapi32.dll
16842 except when we need them. (Bug introduced in 0.1.2.7-alpha;
16844 - Fix a longstanding obscure crash bug that could occur when
16845 we run out of DNS worker processes. (Resolves bug 390.)
16847 o Major bugfixes (hidden services):
16848 - Correctly detect whether hidden service descriptor downloads are
16849 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
16851 o Major bugfixes (accounting):
16852 - When we start during an accounting interval before it's time to wake
16853 up, remember to wake up at the correct time. (May fix bug 342.)
16855 o Minor bugfixes (controller):
16856 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
16857 clear the corresponding on_circuit variable, and remember later
16858 that we don't need to send a redundant CLOSED event. Resolves part
16860 - Report events where a resolve succeeded or where we got a socks
16861 protocol error correctly, rather than calling both of them
16863 - Change reported stream target addresses to IP consistently when
16864 we finally get the IP from an exit node.
16865 - Send log messages to the controller even if they happen to be very
16868 o Minor bugfixes (other):
16869 - Display correct results when reporting which versions are
16870 recommended, and how recommended they are. (Resolves bug 383.)
16871 - Improve our estimates for directory bandwidth to be less random:
16872 guess that an unrecognized directory will have the average bandwidth
16873 from all known directories, not that it will have the average
16874 bandwidth from those directories earlier than it on the list.
16875 - If we start a server with ClientOnly 1, then set ClientOnly to 0
16876 and hup, stop triggering an assert based on an empty onion_key.
16877 - On platforms with no working mmap() equivalent, don't warn the
16878 user when cached-routers doesn't exist.
16879 - Warn the user when mmap() [or its equivalent] fails for some reason
16880 other than file-not-found.
16881 - Don't warn the user when cached-routers.new doesn't exist: that's
16882 perfectly fine when starting up for the first time.
16883 - When EntryNodes are configured, rebuild the guard list to contain,
16884 in order: the EntryNodes that were guards before; the rest of the
16885 EntryNodes; the nodes that were guards before.
16886 - Mask out all signals in sub-threads; only the libevent signal
16887 handler should be processing them. This should prevent some crashes
16888 on some machines using pthreads. (Patch from coderman.)
16889 - Fix switched arguments on memset in the implementation of
16890 tor_munmap() for systems with no mmap() call.
16891 - When Tor receives a router descriptor that it asked for, but
16892 no longer wants (because it has received fresh networkstatuses
16893 in the meantime), do not warn the user. Cache the descriptor if
16894 we're a cache; drop it if we aren't.
16895 - Make earlier entry guards _really_ get retried when the network
16897 - On a malformed DNS reply, always give an error to the corresponding
16899 - Build with recent libevents on platforms that do not define the
16900 nonstandard types "u_int8_t" and friends.
16902 o Minor features (controller):
16903 - Warn the user when an application uses the obsolete binary v0
16904 control protocol. We're planning to remove support for it during
16905 the next development series, so it's good to give people some
16907 - Add STREAM_BW events to report per-entry-stream bandwidth
16908 use. (Patch from Robert Hogan.)
16909 - Rate-limit SIGNEWNYM signals in response to controllers that
16910 impolitely generate them for every single stream. (Patch from
16911 mwenge; closes bug 394.)
16912 - Make REMAP stream events have a SOURCE (cache or exit), and
16913 make them generated in every case where we get a successful
16914 connected or resolved cell.
16916 o Minor bugfixes (performance):
16917 - Call router_have_min_dir_info half as often. (This is showing up in
16918 some profiles, but not others.)
16919 - When using GCC, make log_debug never get called at all, and its
16920 arguments never get evaluated, when no debug logs are configured.
16921 (This is showing up in some profiles, but not others.)
16924 - Remove some never-implemented options. Mark PathlenCoinWeight as
16926 - Implement proposal 106: Stop requiring clients to have well-formed
16927 certificates; stop checking nicknames in certificates. (Clients
16928 have certificates so that they can look like Tor servers, but in
16929 the future we might want to allow them to look like regular TLS
16930 clients instead. Nicknames in certificates serve no purpose other
16931 than making our protocol easier to recognize on the wire.)
16932 - Revise messages on handshake failure again to be even more clear about
16933 which are incoming connections and which are outgoing.
16934 - Discard any v1 directory info that's over 1 month old (for
16935 directories) or over 1 week old (for running-routers lists).
16936 - Do not warn when individual nodes in the configuration's EntryNodes,
16937 ExitNodes, etc are down: warn only when all possible nodes
16938 are down. (Fixes bug 348.)
16939 - Always remove expired routers and networkstatus docs before checking
16940 whether we have enough information to build circuits. (Fixes
16942 - Put a lower-bound on MaxAdvertisedBandwidth.
16945 Changes in version 0.1.2.7-alpha - 2007-02-06
16946 o Major bugfixes (rate limiting):
16947 - Servers decline directory requests much more aggressively when
16948 they're low on bandwidth. Otherwise they end up queueing more and
16949 more directory responses, which can't be good for latency.
16950 - But never refuse directory requests from local addresses.
16951 - Fix a memory leak when sending a 503 response for a networkstatus
16953 - Be willing to read or write on local connections (e.g. controller
16954 connections) even when the global rate limiting buckets are empty.
16955 - If our system clock jumps back in time, don't publish a negative
16956 uptime in the descriptor. Also, don't let the global rate limiting
16957 buckets go absurdly negative.
16958 - Flush local controller connection buffers periodically as we're
16959 writing to them, so we avoid queueing 4+ megabytes of data before
16962 o Major bugfixes (NT services):
16963 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
16964 command-line flag so that admins can override the default by saying
16965 "tor --service install --user "SomeUser"". This will not affect
16966 existing installed services. Also, warn the user that the service
16967 will look for its configuration file in the service user's
16968 %appdata% directory. (We can't do the 'hardwire the user's appdata
16969 directory' trick any more, since we may not have read access to that
16972 o Major bugfixes (other):
16973 - Previously, we would cache up to 16 old networkstatus documents
16974 indefinitely, if they came from nontrusted authorities. Now we
16975 discard them if they are more than 10 days old.
16976 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
16978 - Detect and reject malformed DNS responses containing circular
16980 - If exits are rare enough that we're not marking exits as guards,
16981 ignore exit bandwidth when we're deciding the required bandwidth
16983 - When we're handling a directory connection tunneled over Tor,
16984 don't fill up internal memory buffers with all the data we want
16985 to tunnel; instead, only add it if the OR connection that will
16986 eventually receive it has some room for it. (This can lead to
16987 slowdowns in tunneled dir connections; a better solution will have
16988 to wait for 0.2.0.)
16990 o Minor bugfixes (dns):
16991 - Add some defensive programming to eventdns.c in an attempt to catch
16992 possible memory-stomping bugs.
16993 - Detect and reject DNS replies containing IPv4 or IPv6 records with
16994 an incorrect number of bytes. (Previously, we would ignore the
16996 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
16997 in the correct order, and doesn't crash.
16998 - Free memory held in recently-completed DNS lookup attempts on exit.
16999 This was not a memory leak, but may have been hiding memory leaks.
17000 - Handle TTL values correctly on reverse DNS lookups.
17001 - Treat failure to parse resolv.conf as an error.
17003 o Minor bugfixes (other):
17004 - Fix crash with "tor --list-fingerprint" (reported by seeess).
17005 - When computing clock skew from directory HTTP headers, consider what
17006 time it was when we finished asking for the directory, not what
17008 - Expire socks connections if they spend too long waiting for the
17009 handshake to finish. Previously we would let them sit around for
17010 days, if the connecting application didn't close them either.
17011 - And if the socks handshake hasn't started, don't send a
17012 "DNS resolve socks failed" handshake reply; just close it.
17013 - Stop using C functions that OpenBSD's linker doesn't like.
17014 - Don't launch requests for descriptors unless we have networkstatuses
17015 from at least half of the authorities. This delays the first
17016 download slightly under pathological circumstances, but can prevent
17017 us from downloading a bunch of descriptors we don't need.
17018 - Do not log IPs with TLS failures for incoming TLS
17019 connections. (Fixes bug 382.)
17020 - If the user asks to use invalid exit nodes, be willing to use
17022 - Stop using the reserved ac_cv namespace in our configure script.
17023 - Call stat() slightly less often; use fstat() when possible.
17024 - Refactor the way we handle pending circuits when an OR connection
17025 completes or fails, in an attempt to fix a rare crash bug.
17026 - Only rewrite a conn's address based on X-Forwarded-For: headers
17027 if it's a parseable public IP address; and stop adding extra quotes
17028 to the resulting address.
17031 - Weight directory requests by advertised bandwidth. Now we can
17032 let servers enable write limiting but still allow most clients to
17033 succeed at their directory requests. (We still ignore weights when
17034 choosing a directory authority; I hope this is a feature.)
17037 - Create a new file ReleaseNotes which was the old ChangeLog. The
17038 new ChangeLog file now includes the summaries for all development
17040 - Check for addresses with invalid characters at the exit as well
17041 as at the client, and warn less verbosely when they fail. You can
17042 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
17043 - Adapt a patch from goodell to let the contrib/exitlist script
17044 take arguments rather than require direct editing.
17045 - Inform the server operator when we decide not to advertise a
17046 DirPort due to AccountingMax enabled or a low BandwidthRate. It
17047 was confusing Zax, so now we're hopefully more helpful.
17048 - Bring us one step closer to being able to establish an encrypted
17049 directory tunnel without knowing a descriptor first. Still not
17050 ready yet. As part of the change, now assume we can use a
17051 create_fast cell if we don't know anything about a router.
17052 - Allow exit nodes to use nameservers running on ports other than 53.
17053 - Servers now cache reverse DNS replies.
17054 - Add an --ignore-missing-torrc command-line option so that we can
17055 get the "use sensible defaults if the configuration file doesn't
17056 exist" behavior even when specifying a torrc location on the command
17059 o Minor features (controller):
17060 - Track reasons for OR connection failure; make these reasons
17061 available via the controller interface. (Patch from Mike Perry.)
17062 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
17063 can learn when clients are sending malformed hostnames to Tor.
17064 - Clean up documentation for controller status events.
17065 - Add a REMAP status to stream events to note that a stream's
17066 address has changed because of a cached address or a MapAddress
17070 Changes in version 0.1.2.6-alpha - 2007-01-09
17072 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
17073 connection handles more than 4 gigs in either direction, we crash.
17074 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
17075 advertised exit node, somebody might try to exit from us when
17076 we're bootstrapping and before we've built our descriptor yet.
17077 Refuse the connection rather than crashing.
17080 - Warn if we (as a server) find that we've resolved an address that we
17081 weren't planning to resolve.
17082 - Warn that using select() on any libevent version before 1.1 will be
17083 unnecessarily slow (even for select()).
17084 - Flush ERR-level controller status events just like we currently
17085 flush ERR-level log events, so that a Tor shutdown doesn't prevent
17086 the controller from learning about current events.
17088 o Minor features (more controller status events):
17089 - Implement EXTERNAL_ADDRESS server status event so controllers can
17090 learn when our address changes.
17091 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
17092 can learn when directories reject our descriptor.
17093 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
17094 can learn when a client application is speaking a non-socks protocol
17096 - Implement DANGEROUS_SOCKS client status event so controllers
17097 can learn when a client application is leaking DNS addresses.
17098 - Implement BUG general status event so controllers can learn when
17099 Tor is unhappy about its internal invariants.
17100 - Implement CLOCK_SKEW general status event so controllers can learn
17101 when Tor thinks the system clock is set incorrectly.
17102 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
17103 server status events so controllers can learn when their descriptors
17104 are accepted by a directory.
17105 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
17106 server status events so controllers can learn about Tor's progress in
17107 deciding whether it's reachable from the outside.
17108 - Implement BAD_LIBEVENT general status event so controllers can learn
17109 when we have a version/method combination in libevent that needs to
17111 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
17112 and DNS_USELESS server status events so controllers can learn
17113 about changes to DNS server status.
17115 o Minor features (directory):
17116 - Authorities no longer recommend exits as guards if this would shift
17117 too much load to the exit nodes.
17120 Changes in version 0.1.2.5-alpha - 2007-01-06
17122 - Enable write limiting as well as read limiting. Now we sacrifice
17123 capacity if we're pushing out lots of directory traffic, rather
17124 than overrunning the user's intended bandwidth limits.
17125 - Include TLS overhead when counting bandwidth usage; previously, we
17126 would count only the bytes sent over TLS, but not the bytes used
17128 - Support running the Tor service with a torrc not in the same
17129 directory as tor.exe and default to using the torrc located in
17130 the %appdata%\Tor\ of the user who installed the service. Patch
17132 - Servers now check for the case when common DNS requests are going to
17133 wildcarded addresses (i.e. all getting the same answer), and change
17134 their exit policy to reject *:* if it's happening.
17135 - Implement BEGIN_DIR cells, so we can connect to the directory
17136 server via TLS to do encrypted directory requests rather than
17137 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
17138 config options if you like.
17140 o Minor features (config and docs):
17141 - Start using the state file to store bandwidth accounting data:
17142 the bw_accounting file is now obsolete. We'll keep generating it
17143 for a while for people who are still using 0.1.2.4-alpha.
17144 - Try to batch changes to the state file so that we do as few
17145 disk writes as possible while still storing important things in
17147 - The state file and the bw_accounting file get saved less often when
17148 the AvoidDiskWrites config option is set.
17149 - Make PIDFile work on Windows (untested).
17150 - Add internal descriptions for a bunch of configuration options:
17151 accessible via controller interface and in comments in saved
17153 - Reject *:563 (NNTPS) in the default exit policy. We already reject
17154 NNTP by default, so this seems like a sensible addition.
17155 - Clients now reject hostnames with invalid characters. This should
17156 avoid some inadvertent info leaks. Add an option
17157 AllowNonRFC953Hostnames to disable this behavior, in case somebody
17158 is running a private network with hosts called @, !, and #.
17159 - Add a maintainer script to tell us which options are missing
17160 documentation: "make check-docs".
17161 - Add a new address-spec.txt document to describe our special-case
17162 addresses: .exit, .onion, and .noconnnect.
17164 o Minor features (DNS):
17165 - Ongoing work on eventdns infrastructure: now it has dns server
17166 and ipv6 support. One day Tor will make use of it.
17167 - Add client-side caching for reverse DNS lookups.
17168 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
17169 - When we change nameservers or IP addresses, reset and re-launch
17170 our tests for DNS hijacking.
17172 o Minor features (directory):
17173 - Authorities now specify server versions in networkstatus. This adds
17174 about 2% to the size of compressed networkstatus docs, and allows
17175 clients to tell which servers support BEGIN_DIR and which don't.
17176 The implementation is forward-compatible with a proposed future
17177 protocol version scheme not tied to Tor versions.
17178 - DirServer configuration lines now have an orport= option so
17179 clients can open encrypted tunnels to the authorities without
17180 having downloaded their descriptors yet. Enabled for moria1,
17181 moria2, tor26, and lefkada now in the default configuration.
17182 - Directory servers are more willing to send a 503 "busy" if they
17183 are near their write limit, especially for v1 directory requests.
17184 Now they can use their limited bandwidth for actual Tor traffic.
17185 - Clients track responses with status 503 from dirservers. After a
17186 dirserver has given us a 503, we try not to use it until an hour has
17187 gone by, or until we have no dirservers that haven't given us a 503.
17188 - When we get a 503 from a directory, and we're not a server, we don't
17189 count the failure against the total number of failures allowed
17190 for the thing we're trying to download.
17191 - Report X-Your-Address-Is correctly from tunneled directory
17192 connections; don't report X-Your-Address-Is when it's an internal
17193 address; and never believe reported remote addresses when they're
17195 - Protect against an unlikely DoS attack on directory servers.
17196 - Add a BadDirectory flag to network status docs so that authorities
17197 can (eventually) tell clients about caches they believe to be
17200 o Minor features (controller):
17201 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
17202 - Reimplement GETINFO so that info/names stays in sync with the
17204 - Implement "GETINFO fingerprint".
17205 - Implement "SETEVENTS GUARD" so controllers can get updates on
17206 entry guard status as it changes.
17208 o Minor features (clean up obsolete pieces):
17209 - Remove some options that have been deprecated since at least
17210 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
17211 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
17212 to set log options.
17213 - We no longer look for identity and onion keys in "identity.key" and
17214 "onion.key" -- these were replaced by secret_id_key and
17215 secret_onion_key in 0.0.8pre1.
17216 - We no longer require unrecognized directory entries to be
17219 o Major bugfixes (security):
17220 - Stop sending the HttpProxyAuthenticator string to directory
17221 servers when directory connections are tunnelled through Tor.
17222 - Clients no longer store bandwidth history in the state file.
17223 - Do not log introduction points for hidden services if SafeLogging
17225 - When generating bandwidth history, round down to the nearest
17226 1k. When storing accounting data, round up to the nearest 1k.
17227 - When we're running as a server, remember when we last rotated onion
17228 keys, so that we will rotate keys once they're a week old even if
17229 we never stay up for a week ourselves.
17231 o Major bugfixes (other):
17232 - Fix a longstanding bug in eventdns that prevented the count of
17233 timed-out resolves from ever being reset. This bug caused us to
17234 give up on a nameserver the third time it timed out, and try it
17235 10 seconds later... and to give up on it every time it timed out
17237 - Take out the '5 second' timeout from the connection retry
17238 schedule. Now the first connect attempt will wait a full 10
17239 seconds before switching to a new circuit. Perhaps this will help
17240 a lot. Based on observations from Mike Perry.
17241 - Fix a bug on the Windows implementation of tor_mmap_file() that
17242 would prevent the cached-routers file from ever loading. Reported
17246 - Fix an assert failure when a directory authority sets
17247 AuthDirRejectUnlisted and then receives a descriptor from an
17248 unlisted router. Reported by seeess.
17249 - Avoid a double-free when parsing malformed DirServer lines.
17250 - Fix a bug when a BSD-style PF socket is first used. Patch from
17252 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
17253 to resolve an address at a given exit node even when they ask for
17255 - Servers no longer ever list themselves in their "family" line,
17256 even if configured to do so. This makes it easier to configure
17257 family lists conveniently.
17258 - When running as a server, don't fall back to 127.0.0.1 when no
17259 nameservers are configured in /etc/resolv.conf; instead, make the
17260 user fix resolv.conf or specify nameservers explicitly. (Resolves
17262 - Stop accepting certain malformed ports in configured exit policies.
17263 - Don't re-write the fingerprint file every restart, unless it has
17265 - Stop warning when a single nameserver fails: only warn when _all_ of
17266 our nameservers have failed. Also, when we only have one nameserver,
17267 raise the threshold for deciding that the nameserver is dead.
17268 - Directory authorities now only decide that routers are reachable
17269 if their identity keys are as expected.
17270 - When the user uses bad syntax in the Log config line, stop
17271 suggesting other bad syntax as a replacement.
17272 - Correctly detect ipv6 DNS capability on OpenBSD.
17274 o Minor bugfixes (controller):
17275 - Report the circuit number correctly in STREAM CLOSED events. Bug
17276 reported by Mike Perry.
17277 - Do not report bizarre values for results of accounting GETINFOs
17278 when the last second's write or read exceeds the allotted bandwidth.
17279 - Report "unrecognized key" rather than an empty string when the
17280 controller tries to fetch a networkstatus that doesn't exist.
17283 Changes in version 0.1.1.26 - 2006-12-14
17284 o Security bugfixes:
17285 - Stop sending the HttpProxyAuthenticator string to directory
17286 servers when directory connections are tunnelled through Tor.
17287 - Clients no longer store bandwidth history in the state file.
17288 - Do not log introduction points for hidden services if SafeLogging
17292 - Fix an assert failure when a directory authority sets
17293 AuthDirRejectUnlisted and then receives a descriptor from an
17294 unlisted router (reported by seeess).
17297 Changes in version 0.1.2.4-alpha - 2006-12-03
17299 - Add support for using natd; this allows FreeBSDs earlier than
17300 5.1.2 to have ipfw send connections through Tor without using
17301 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
17304 - Make all connections to addresses of the form ".noconnect"
17305 immediately get closed. This lets application/controller combos
17306 successfully test whether they're talking to the same Tor by
17307 watching for STREAM events.
17308 - Make cross.sh cross-compilation script work even when autogen.sh
17309 hasn't been run. (Patch from Michael Mohr.)
17310 - Statistics dumped by -USR2 now include a breakdown of public key
17311 operations, for profiling.
17314 - Fix a major leak when directory authorities parse their
17315 approved-routers list, a minor memory leak when we fail to pick
17316 an exit node, and a few rare leaks on errors.
17317 - Handle TransPort connections even when the server sends data before
17318 the client sends data. Previously, the connection would just hang
17319 until the client sent data. (Patch from tup based on patch from
17321 - Avoid assert failure when our cached-routers file is empty on
17325 - Don't log spurious warnings when we see a circuit close reason we
17326 don't recognize; it's probably just from a newer version of Tor.
17327 - Have directory authorities allow larger amounts of drift in uptime
17328 without replacing the server descriptor: previously, a server that
17329 restarted every 30 minutes could have 48 "interesting" descriptors
17331 - Start linking to the Tor specification and Tor reference manual
17332 correctly in the Windows installer.
17333 - Add Vidalia to the OS X uninstaller script, so when we uninstall
17334 Tor/Privoxy we also uninstall Vidalia.
17335 - Resume building on Irix64, and fix a lot of warnings from its
17336 MIPSpro C compiler.
17337 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
17338 when we're running as a client.
17341 Changes in version 0.1.1.25 - 2006-11-04
17343 - When a client asks us to resolve (rather than connect to)
17344 an address, and we have a cached answer, give them the cached
17345 answer. Previously, we would give them no answer at all.
17346 - We were building exactly the wrong circuits when we predict
17347 hidden service requirements, meaning Tor would have to build all
17348 its circuits on demand.
17349 - If none of our live entry guards have a high uptime, but we
17350 require a guard with a high uptime, try adding a new guard before
17351 we give up on the requirement. This patch should make long-lived
17352 connections more stable on average.
17353 - When testing reachability of our DirPort, don't launch new
17354 tests when there's already one in progress -- unreachable
17355 servers were stacking up dozens of testing streams.
17357 o Security bugfixes:
17358 - When the user sends a NEWNYM signal, clear the client-side DNS
17359 cache too. Otherwise we continue to act on previous information.
17362 - Avoid a memory corruption bug when creating a hash table for
17364 - Avoid possibility of controller-triggered crash when misusing
17365 certain commands from a v0 controller on platforms that do not
17366 handle printf("%s",NULL) gracefully.
17367 - Avoid infinite loop on unexpected controller input.
17368 - Don't log spurious warnings when we see a circuit close reason we
17369 don't recognize; it's probably just from a newer version of Tor.
17370 - Add Vidalia to the OS X uninstaller script, so when we uninstall
17371 Tor/Privoxy we also uninstall Vidalia.
17374 Changes in version 0.1.2.3-alpha - 2006-10-29
17376 - Prepare for servers to publish descriptors less often: never
17377 discard a descriptor simply for being too old until either it is
17378 recommended by no authorities, or until we get a better one for
17379 the same router. Make caches consider retaining old recommended
17380 routers for even longer.
17381 - If most authorities set a BadExit flag for a server, clients
17382 don't think of it as a general-purpose exit. Clients only consider
17383 authorities that advertise themselves as listing bad exits.
17384 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
17385 headers for content, so that we can work better in the presence of
17386 caching HTTP proxies.
17387 - Allow authorities to list nodes as bad exits by fingerprint or by
17390 o Minor features, controller:
17391 - Add a REASON field to CIRC events; for backward compatibility, this
17392 field is sent only to controllers that have enabled the extended
17393 event format. Also, add additional reason codes to explain why
17394 a given circuit has been destroyed or truncated. (Patches from
17396 - Add a REMOTE_REASON field to extended CIRC events to tell the
17397 controller about why a remote OR told us to close a circuit.
17398 - Stream events also now have REASON and REMOTE_REASON fields,
17399 working much like those for circuit events.
17400 - There's now a GETINFO ns/... field so that controllers can ask Tor
17401 about the current status of a router.
17402 - A new event type "NS" to inform a controller when our opinion of
17403 a router's status has changed.
17404 - Add a GETINFO events/names and GETINFO features/names so controllers
17405 can tell which events and features are supported.
17406 - A new CLEARDNSCACHE signal to allow controllers to clear the
17407 client-side DNS cache without expiring circuits.
17409 o Security bugfixes:
17410 - When the user sends a NEWNYM signal, clear the client-side DNS
17411 cache too. Otherwise we continue to act on previous information.
17414 - Avoid sending junk to controllers or segfaulting when a controller
17415 uses EVENT_NEW_DESC with verbose nicknames.
17416 - Stop triggering asserts if the controller tries to extend hidden
17417 service circuits (reported by mwenge).
17418 - Avoid infinite loop on unexpected controller input.
17419 - When the controller does a "GETINFO network-status", tell it
17420 about even those routers whose descriptors are very old, and use
17421 long nicknames where appropriate.
17422 - Change NT service functions to be loaded on demand. This lets us
17423 build with MinGW without breaking Tor for Windows 98 users.
17424 - Do DirPort reachability tests less often, since a single test
17425 chews through many circuits before giving up.
17426 - In the hidden service example in torrc.sample, stop recommending
17427 esoteric and discouraged hidden service options.
17428 - When stopping an NT service, wait up to 10 sec for it to actually
17429 stop. Patch from Matt Edman; resolves bug 295.
17430 - Fix handling of verbose nicknames with ORCONN controller events:
17431 make them show up exactly when requested, rather than exactly when
17433 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
17434 printing a duplicate "$" in the keys we send (reported by mwenge).
17435 - Correctly set maximum connection limit on Cygwin. (This time
17437 - Try to detect Windows correctly when cross-compiling.
17438 - Detect the size of the routers file correctly even if it is
17439 corrupted (on systems without mmap) or not page-aligned (on systems
17440 with mmap). This bug was harmless.
17441 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
17442 to open a stream fails; now we do in more cases. This should
17443 make clients able to find a good exit faster in some cases, since
17444 unhandleable requests will now get an error rather than timing out.
17445 - Resolve two memory leaks when rebuilding the on-disk router cache
17446 (reported by fookoowa).
17447 - Clean up minor code warnings suggested by the MIPSpro C compiler,
17448 and reported by some Centos users.
17449 - Controller signals now work on non-Unix platforms that don't define
17450 SIGUSR1 and SIGUSR2 the way we expect.
17451 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
17452 values before failing, and always enables eventdns.
17453 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
17454 Try to fix this in configure.in by checking for most functions
17455 before we check for libevent.
17458 Changes in version 0.1.2.2-alpha - 2006-10-07
17460 - Make our async eventdns library on-by-default for Tor servers,
17461 and plan to deprecate the separate dnsworker threads.
17462 - Add server-side support for "reverse" DNS lookups (using PTR
17463 records so clients can determine the canonical hostname for a given
17464 IPv4 address). Only supported by servers using eventdns; servers
17465 now announce in their descriptors whether they support eventdns.
17466 - Specify and implement client-side SOCKS5 interface for reverse DNS
17467 lookups (see doc/socks-extensions.txt).
17468 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
17469 connect to directory servers through Tor. Previously, clients needed
17470 to find Tor exits to make private connections to directory servers.
17471 - Avoid choosing Exit nodes for entry or middle hops when the
17472 total bandwidth available from non-Exit nodes is much higher than
17473 the total bandwidth available from Exit nodes.
17474 - Workaround for name servers (like Earthlink's) that hijack failing
17475 DNS requests and replace the no-such-server answer with a "helpful"
17476 redirect to an advertising-driven search portal. Also work around
17477 DNS hijackers who "helpfully" decline to hijack known-invalid
17478 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
17479 lets you turn it off.
17480 - Send out a burst of long-range padding cells once we've established
17481 that we're reachable. Spread them over 4 circuits, so hopefully
17482 a few will be fast. This exercises our bandwidth and bootstraps
17483 us into the directory more quickly.
17485 o New/improved config options:
17486 - Add new config option "ResolvConf" to let the server operator
17487 choose an alternate resolve.conf file when using eventdns.
17488 - Add an "EnforceDistinctSubnets" option to control our "exclude
17489 servers on the same /16" behavior. It's still on by default; this
17490 is mostly for people who want to operate private test networks with
17491 all the machines on the same subnet.
17492 - If one of our entry guards is on the ExcludeNodes list, or the
17493 directory authorities don't think it's a good guard, treat it as
17494 if it were unlisted: stop using it as a guard, and throw it off
17495 the guards list if it stays that way for a long time.
17496 - Allow directory authorities to be marked separately as authorities
17497 for the v1 directory protocol, the v2 directory protocol, and
17498 as hidden service directories, to make it easier to retire old
17499 authorities. V1 authorities should set "HSAuthoritativeDir 1"
17500 to continue being hidden service authorities too.
17501 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
17503 o Minor features, controller:
17504 - Fix CIRC controller events so that controllers can learn the
17505 identity digests of non-Named servers used in circuit paths.
17506 - Let controllers ask for more useful identifiers for servers. Instead
17507 of learning identity digests for un-Named servers and nicknames
17508 for Named servers, the new identifiers include digest, nickname,
17509 and indication of Named status. Off by default; see control-spec.txt
17510 for more information.
17511 - Add a "getinfo address" controller command so it can display Tor's
17512 best guess to the user.
17513 - New controller event to alert the controller when our server
17514 descriptor has changed.
17515 - Give more meaningful errors on controller authentication failure.
17517 o Minor features, other:
17518 - When asked to resolve a hostname, don't use non-exit servers unless
17519 requested to do so. This allows servers with broken DNS to be
17520 useful to the network.
17521 - Divide eventdns log messages into warn and info messages.
17522 - Reserve the nickname "Unnamed" for routers that can't pick
17523 a hostname: any router can call itself Unnamed; directory
17524 authorities will never allocate Unnamed to any particular router;
17525 clients won't believe that any router is the canonical Unnamed.
17526 - Only include function names in log messages for info/debug messages.
17527 For notice/warn/err, the content of the message should be clear on
17528 its own, and printing the function name only confuses users.
17529 - Avoid some false positives during reachability testing: don't try
17530 to test via a server that's on the same /24 as us.
17531 - If we fail to build a circuit to an intended enclave, and it's
17532 not mandatory that we use that enclave, stop wanting it.
17533 - When eventdns is enabled, allow multithreaded builds on NetBSD and
17534 OpenBSD. (We had previously disabled threads on these platforms
17535 because they didn't have working thread-safe resolver functions.)
17537 o Major bugfixes, anonymity/security:
17538 - If a client asked for a server by name, and there's a named server
17539 in our network-status but we don't have its descriptor yet, we
17540 could return an unnamed server instead.
17541 - Fix NetBSD bug that could allow someone to force uninitialized RAM
17542 to be sent to a server's DNS resolver. This only affects NetBSD
17543 and other platforms that do not bounds-check tolower().
17544 - Reject (most) attempts to use Tor circuits with length one. (If
17545 many people start using Tor as a one-hop proxy, exit nodes become
17546 a more attractive target for compromise.)
17547 - Just because your DirPort is open doesn't mean people should be
17548 able to remotely teach you about hidden service descriptors. Now
17549 only accept rendezvous posts if you've got HSAuthoritativeDir set.
17551 o Major bugfixes, other:
17552 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
17553 - When a client asks the server to resolve (not connect to)
17554 an address, and it has a cached answer, give them the cached answer.
17555 Previously, the server would give them no answer at all.
17556 - Allow really slow clients to not hang up five minutes into their
17557 directory downloads (suggested by Adam J. Richter).
17558 - We were building exactly the wrong circuits when we anticipated
17559 hidden service requirements, meaning Tor would have to build all
17560 its circuits on demand.
17561 - Avoid crashing when we mmap a router cache file of size 0.
17562 - When testing reachability of our DirPort, don't launch new
17563 tests when there's already one in progress -- unreachable
17564 servers were stacking up dozens of testing streams.
17566 o Minor bugfixes, correctness:
17567 - If we're a directory mirror and we ask for "all" network status
17568 documents, we would discard status documents from authorities
17569 we don't recognize.
17570 - Avoid a memory corruption bug when creating a hash table for
17572 - Avoid controller-triggered crash when misusing certain commands
17573 from a v0 controller on platforms that do not handle
17574 printf("%s",NULL) gracefully.
17575 - Don't crash when a controller sends a third argument to an
17576 "extendcircuit" request.
17577 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
17578 response; fix error code when "getinfo dir/status/" fails.
17579 - Avoid crash when telling controller stream-status and a stream
17581 - Patch from Adam Langley to fix assert() in eventdns.c.
17582 - Fix a debug log message in eventdns to say "X resolved to Y"
17583 instead of "X resolved to X".
17584 - Make eventdns give strings for DNS errors, not just error numbers.
17585 - Track unreachable entry guards correctly: don't conflate
17586 'unreachable by us right now' with 'listed as down by the directory
17587 authorities'. With the old code, if a guard was unreachable by
17588 us but listed as running, it would clog our guard list forever.
17589 - Behave correctly in case we ever have a network with more than
17590 2GB/s total advertised capacity.
17591 - Make TrackExitHosts case-insensitive, and fix the behavior of
17592 ".suffix" TrackExitHosts items to avoid matching in the middle of
17594 - Finally fix the openssl warnings from newer gccs that believe that
17595 ignoring a return value is okay, but casting a return value and
17596 then ignoring it is a sign of madness.
17597 - Prevent the contrib/exitlist script from printing the same
17598 result more than once.
17599 - Patch from Steve Hildrey: Generate network status correctly on
17600 non-versioning dirservers.
17601 - Don't listen to the X-Your-Address-Is hint if you did the lookup
17602 via Tor; otherwise you'll think you're the exit node's IP address.
17604 o Minor bugfixes, performance:
17605 - Two small performance improvements on parsing descriptors.
17606 - Major performance improvement on inserting descriptors: change
17607 algorithm from O(n^2) to O(n).
17608 - Make the common memory allocation path faster on machines where
17609 malloc(0) returns a pointer.
17610 - Start remembering X-Your-Address-Is directory hints even if you're
17611 a client, so you can become a server more smoothly.
17612 - Avoid duplicate entries on MyFamily line in server descriptor.
17614 o Packaging, features:
17615 - Remove architecture from OS X builds. The official builds are
17616 now universal binaries.
17617 - The Debian package now uses --verify-config when (re)starting,
17618 to distinguish configuration errors from other errors.
17619 - Update RPMs to require libevent 1.1b.
17621 o Packaging, bugfixes:
17622 - Patches so Tor builds with MinGW on Windows.
17623 - Patches so Tor might run on Cygwin again.
17624 - Resume building on non-gcc compilers and ancient gcc. Resume
17625 building with the -O0 compile flag. Resume building cleanly on
17627 - Run correctly on OS X platforms with case-sensitive filesystems.
17628 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
17629 - Add autoconf checks so Tor can build on Solaris x86 again.
17632 - Documented (and renamed) ServerDNSSearchDomains and
17633 ServerDNSResolvConfFile options.
17634 - Be clearer that the *ListenAddress directives can be repeated
17638 Changes in version 0.1.1.24 - 2006-09-29
17640 - Allow really slow clients to not hang up five minutes into their
17641 directory downloads (suggested by Adam J. Richter).
17642 - Fix major performance regression from 0.1.0.x: instead of checking
17643 whether we have enough directory information every time we want to
17644 do something, only check when the directory information has changed.
17645 This should improve client CPU usage by 25-50%.
17646 - Don't crash if, after a server has been running for a while,
17647 it can't resolve its hostname.
17650 - Allow Tor to start when RunAsDaemon is set but no logs are set.
17651 - Don't crash when the controller receives a third argument to an
17652 "extendcircuit" request.
17653 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
17654 response; fix error code when "getinfo dir/status/" fails.
17655 - Fix configure.in to not produce broken configure files with
17656 more recent versions of autoconf. Thanks to Clint for his auto*
17658 - Fix security bug on NetBSD that could allow someone to force
17659 uninitialized RAM to be sent to a server's DNS resolver. This
17660 only affects NetBSD and other platforms that do not bounds-check
17662 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
17663 methods: these are known to be buggy.
17664 - If we're a directory mirror and we ask for "all" network status
17665 documents, we would discard status documents from authorities
17666 we don't recognize.
17669 Changes in version 0.1.2.1-alpha - 2006-08-27
17671 - Add "eventdns" async dns library from Adam Langley, tweaked to
17672 build on OSX and Windows. Only enabled if you pass the
17673 --enable-eventdns argument to configure.
17674 - Allow servers with no hostname or IP address to learn their
17675 IP address by asking the directory authorities. This code only
17676 kicks in when you would normally have exited with a "no address"
17677 error. Nothing's authenticated, so use with care.
17678 - Rather than waiting a fixed amount of time between retrying
17679 application connections, we wait only 5 seconds for the first,
17680 10 seconds for the second, and 15 seconds for each retry after
17681 that. Hopefully this will improve the expected user experience.
17682 - Patch from Tup to add support for transparent AP connections:
17683 this basically bundles the functionality of trans-proxy-tor
17684 into the Tor mainline. Now hosts with compliant pf/netfilter
17685 implementations can redirect TCP connections straight to Tor
17686 without diverting through SOCKS. Needs docs.
17687 - Busy directory servers save lots of memory by spooling server
17688 descriptors, v1 directories, and v2 networkstatus docs to buffers
17689 as needed rather than en masse. Also mmap the cached-routers
17690 files, so we don't need to keep the whole thing in memory too.
17691 - Automatically avoid picking more than one node from the same
17692 /16 network when constructing a circuit.
17693 - Revise and clean up the torrc.sample that we ship with; add
17694 a section for BandwidthRate and BandwidthBurst.
17697 - Split circuit_t into origin_circuit_t and or_circuit_t, and
17698 split connection_t into edge, or, dir, control, and base structs.
17699 These will save quite a bit of memory on busy servers, and they'll
17700 also help us track down bugs in the code and bugs in the spec.
17701 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
17702 or later. Log when we are doing this, so we can diagnose it when
17703 it fails. (Also, recommend libevent 1.1b for kqueue and
17704 win32 methods; deprecate libevent 1.0b harder; make libevent
17705 recommendation system saner.)
17706 - Start being able to build universal binaries on OS X (thanks
17708 - Export the default exit policy via the control port, so controllers
17709 don't need to guess what it is / will be later.
17710 - Add a man page entry for ProtocolWarnings.
17711 - Add TestVia config option to the man page.
17712 - Remove even more protocol-related warnings from Tor server logs,
17713 such as bad TLS handshakes and malformed begin cells.
17714 - Stop fetching descriptors if you're not a dir mirror and you
17715 haven't tried to establish any circuits lately. [This currently
17716 causes some dangerous behavior, because when you start up again
17717 you'll use your ancient server descriptors.]
17718 - New DirPort behavior: if you have your dirport set, you download
17719 descriptors aggressively like a directory mirror, whether or not
17720 your ORPort is set.
17721 - Get rid of the router_retry_connections notion. Now routers
17722 no longer try to rebuild long-term connections to directory
17723 authorities, and directory authorities no longer try to rebuild
17724 long-term connections to all servers. We still don't hang up
17725 connections in these two cases though -- we need to look at it
17726 more carefully to avoid flapping, and we likely need to wait til
17727 0.1.1.x is obsolete.
17728 - Drop compatibility with obsolete Tors that permit create cells
17729 to have the wrong circ_id_type.
17730 - Re-enable per-connection rate limiting. Get rid of the "OP
17731 bandwidth" concept. Lay groundwork for "bandwidth classes" --
17732 separate global buckets that apply depending on what sort of conn
17734 - Start publishing one minute or so after we find our ORPort
17735 to be reachable. This will help reduce the number of descriptors
17736 we have for ourselves floating around, since it's quite likely
17737 other things (e.g. DirPort) will change during that minute too.
17738 - Fork the v1 directory protocol into its own spec document,
17739 and mark dir-spec.txt as the currently correct (v2) spec.
17742 - When we find our DirPort to be reachable, publish a new descriptor
17743 so we'll tell the world (reported by pnx).
17744 - Publish a new descriptor after we hup/reload. This is important
17745 if our config has changed such that we'll want to start advertising
17746 our DirPort now, etc.
17747 - Allow Tor to start when RunAsDaemon is set but no logs are set.
17748 - When we have a state file we cannot parse, tell the user and
17749 move it aside. Now we avoid situations where the user starts
17750 Tor in 1904, Tor writes a state file with that timestamp in it,
17751 the user fixes her clock, and Tor refuses to start.
17752 - Fix configure.in to not produce broken configure files with
17753 more recent versions of autoconf. Thanks to Clint for his auto*
17755 - "tor --verify-config" now exits with -1(255) or 0 depending on
17756 whether the config options are bad or good.
17757 - Resolve bug 321 when using dnsworkers: append a period to every
17758 address we resolve at the exit node, so that we do not accidentally
17759 pick up local addresses, and so that failing searches are retried
17760 in the resolver search domains. (This is already solved for
17761 eventdns.) (This breaks Blossom servers for now.)
17762 - If we are using an exit enclave and we can't connect, e.g. because
17763 its webserver is misconfigured to not listen on localhost, then
17764 back off and try connecting from somewhere else before we fail.
17767 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
17768 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
17769 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
17770 when the IP address is mapped through MapAddress to a hostname.
17771 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
17772 useless IPv6 DNS resolves.
17773 - Patch suggested by Karsten Loesing: respond to SIGNAL command
17774 before we execute the signal, in case the signal shuts us down.
17775 - Clean up AllowInvalidNodes man page entry.
17776 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
17777 - Add more asserts to track down an assert error on a windows Tor
17778 server with connection_add being called with socket == -1.
17779 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
17780 - Fix misleading log messages: an entry guard that is "unlisted",
17781 as well as not known to be "down" (because we've never heard
17782 of it), is not therefore "up".
17783 - Remove code to special-case "-cvs" ending, since it has not
17784 actually mattered since 0.0.9.
17785 - Make our socks5 handling more robust to broken socks clients:
17786 throw out everything waiting on the buffer in between socks
17787 handshake phases, since they can't possibly (so the theory
17788 goes) have predicted what we plan to respond to them.
17791 Changes in version 0.1.1.23 - 2006-07-30
17793 - Fast Tor servers, especially exit nodes, were triggering asserts
17794 due to a bug in handling the list of pending DNS resolves. Some
17795 bugs still remain here; we're hunting them.
17796 - Entry guards could crash clients by sending unexpected input.
17797 - More fixes on reachability testing: if you find yourself reachable,
17798 then don't ever make any client requests (so you stop predicting
17799 circuits), then hup or have your clock jump, then later your IP
17800 changes, you won't think circuits are working, so you won't try to
17801 test reachability, so you won't publish.
17804 - Avoid a crash if the controller does a resetconf firewallports
17805 and then a setconf fascistfirewall=1.
17806 - Avoid an integer underflow when the dir authority decides whether
17807 a router is stable: we might wrongly label it stable, and compute
17808 a slightly wrong median stability, when a descriptor is published
17810 - Fix a place where we might trigger an assert if we can't build our
17811 own server descriptor yet.
17814 Changes in version 0.1.1.22 - 2006-07-05
17816 - Fix a big bug that was causing servers to not find themselves
17817 reachable if they changed IP addresses. Since only 0.1.1.22+
17818 servers can do reachability testing correctly, now we automatically
17819 make sure to test via one of these.
17820 - Fix to allow clients and mirrors to learn directory info from
17821 descriptor downloads that get cut off partway through.
17822 - Directory authorities had a bug in deciding if a newly published
17823 descriptor was novel enough to make everybody want a copy -- a few
17824 servers seem to be publishing new descriptors many times a minute.
17826 - Fix a rare bug that was causing some servers to complain about
17827 "closing wedged cpuworkers" and skip some circuit create requests.
17828 - Make the Exit flag in directory status documents actually work.
17831 Changes in version 0.1.1.21 - 2006-06-10
17832 o Crash and assert fixes from 0.1.1.20:
17833 - Fix a rare crash on Tor servers that have enabled hibernation.
17834 - Fix a seg fault on startup for Tor networks that use only one
17835 directory authority.
17836 - Fix an assert from a race condition that occurs on Tor servers
17837 while exiting, where various threads are trying to log that they're
17838 exiting, and delete the logs, at the same time.
17839 - Make our unit tests pass again on certain obscure platforms.
17842 - Add support for building SUSE RPM packages.
17843 - Speed up initial bootstrapping for clients: if we are making our
17844 first ever connection to any entry guard, then don't mark it down
17846 - When only one Tor server in the network is labelled as a guard,
17847 and we've already picked him, we would cycle endlessly picking him
17848 again, being unhappy about it, etc. Now we specifically exclude
17849 current guards when picking a new guard.
17850 - Servers send create cells more reliably after the TLS connection
17851 is established: we were sometimes forgetting to send half of them
17852 when we had more than one pending.
17853 - If we get a create cell that asks us to extend somewhere, but the
17854 Tor server there doesn't match the expected digest, we now send
17855 a destroy cell back, rather than silently doing nothing.
17856 - Make options->RedirectExit work again.
17857 - Make cookie authentication for the controller work again.
17858 - Stop being picky about unusual characters in the arguments to
17859 mapaddress. It's none of our business.
17860 - Add a new config option "TestVia" that lets you specify preferred
17861 middle hops to use for test circuits. Perhaps this will let me
17862 debug the reachability problems better.
17864 o Log / documentation fixes:
17865 - If we're a server and some peer has a broken TLS certificate, don't
17866 log about it unless ProtocolWarnings is set, i.e., we want to hear
17867 about protocol violations by others.
17868 - Fix spelling of VirtualAddrNetwork in man page.
17869 - Add a better explanation at the top of the autogenerated torrc file
17870 about what happened to our old torrc.
17873 Changes in version 0.1.1.20 - 2006-05-23
17875 - Downgrade a log severity where servers complain that they're
17877 - Avoid a compile warning on FreeBSD.
17878 - Remove string size limit on NEWDESC messages; solve bug 291.
17879 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
17880 more thoroughly when we're running on windows.
17883 Changes in version 0.1.1.19-rc - 2006-05-03
17885 - Regenerate our local descriptor if it's dirty and we try to use
17886 it locally (e.g. if it changes during reachability detection).
17887 - If we setconf our ORPort to 0, we continued to listen on the
17888 old ORPort and receive connections.
17889 - Avoid a second warning about machine/limits.h on Debian
17891 - Be willing to add our own routerinfo into the routerlist.
17892 Now authorities will include themselves in their directories
17893 and network-statuses.
17894 - Stop trying to upload rendezvous descriptors to every
17895 directory authority: only try the v1 authorities.
17896 - Servers no longer complain when they think they're not
17897 registered with the directory authorities. There were too many
17899 - Backport dist-rpm changes so rpms can be built without errors.
17902 - Implement an option, VirtualAddrMask, to set which addresses
17903 get handed out in response to mapaddress requests. This works
17904 around a bug in tsocks where 127.0.0.0/8 is never socksified.
17907 Changes in version 0.1.1.18-rc - 2006-04-10
17909 - Work harder to download live network-statuses from all the
17910 directory authorities we know about. Improve the threshold
17911 decision logic so we're more robust to edge cases.
17912 - When fetching rendezvous descriptors, we were willing to ask
17913 v2 authorities too, which would always return 404.
17916 - Stop listing down or invalid nodes in the v1 directory. This will
17917 reduce its bulk by about 1/3, and reduce load on directory
17919 - When deciding whether a router is Fast or Guard-worthy, consider
17920 his advertised BandwidthRate and not just the BandwidthCapacity.
17921 - No longer ship INSTALL and README files -- they are useless now.
17922 - Force rpmbuild to behave and honor target_cpu.
17923 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
17924 - Start to include translated versions of the tor-doc-*.html
17925 files, along with the screenshots. Still needs more work.
17926 - Start sending back 512 and 451 errors if mapaddress fails,
17927 rather than not sending anything back at all.
17928 - When we fail to bind or listen on an incoming or outgoing
17929 socket, we should close it before failing. otherwise we just
17930 leak it. (thanks to weasel for finding.)
17931 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
17932 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
17933 - Make NoPublish (even though deprecated) work again.
17934 - Fix a minor security flaw where a versioning auth dirserver
17935 could list a recommended version many times in a row to make
17936 clients more convinced that it's recommended.
17937 - Fix crash bug if there are two unregistered servers running
17938 with the same nickname, one of them is down, and you ask for
17939 them by nickname in your EntryNodes or ExitNodes. Also, try
17940 to pick the one that's running rather than an arbitrary one.
17941 - Fix an infinite loop we could hit if we go offline for too long.
17942 - Complain when we hit WSAENOBUFS on recv() or write() too.
17943 Perhaps this will help us hunt the bug.
17944 - If you're not a versioning dirserver, don't put the string
17945 "client-versions \nserver-versions \n" in your network-status.
17946 - Lower the minimum required number of file descriptors to 1000,
17947 so we can have some overhead for Valgrind on Linux, where the
17948 default ulimit -n is 1024.
17951 - Add tor.dizum.com as the fifth authoritative directory server.
17952 - Add a new config option FetchUselessDescriptors, off by default,
17953 for when you plan to run "exitlist" on your client and you want
17954 to know about even the non-running descriptors.
17957 Changes in version 0.1.1.17-rc - 2006-03-28
17959 - Clients and servers since 0.1.1.10-alpha have been expiring
17960 connections whenever they are idle for 5 minutes and they *do*
17961 have circuits on them. Oops. With this new version, clients will
17962 discard their previous entry guard choices and avoid choosing
17963 entry guards running these flawed versions.
17964 - Fix memory leak when uncompressing concatenated zlib streams. This
17965 was causing substantial leaks over time on Tor servers.
17966 - The v1 directory was including servers as much as 48 hours old,
17967 because that's how the new routerlist->routers works. Now only
17968 include them if they're 20 hours old or less.
17971 - Resume building on irix64, netbsd 2.0, etc.
17972 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
17974 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
17975 and it is confusing some users.
17976 - Mirrors stop caching the v1 directory so often.
17977 - Make the max number of old descriptors that a cache will hold
17978 rise with the number of directory authorities, so we can scale.
17979 - Change our win32 uname() hack to be more forgiving about what
17980 win32 versions it thinks it's found.
17983 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
17985 - When the controller's *setconf commands fail, collect an error
17986 message in a string and hand it back to the controller.
17987 - Make the v2 dir's "Fast" flag based on relative capacity, just
17988 like "Stable" is based on median uptime. Name everything in the
17989 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
17990 - Log server fingerprint on startup, so new server operators don't
17991 have to go hunting around their filesystem for it.
17992 - Return a robots.txt on our dirport to discourage google indexing.
17993 - Let the controller ask for GETINFO dir/status/foo so it can ask
17994 directly rather than connecting to the dir port. Only works when
17995 dirport is set for now.
17997 o New config options rather than constants in the code:
17998 - SocksTimeout: How long do we let a socks connection wait
17999 unattached before we fail it?
18000 - CircuitBuildTimeout: Cull non-open circuits that were born
18001 at least this many seconds ago.
18002 - CircuitIdleTimeout: Cull open clean circuits that were born
18003 at least this many seconds ago.
18006 Changes in version 0.1.1.16-rc - 2006-03-18
18007 o Bugfixes on 0.1.1.15-rc:
18008 - Fix assert when the controller asks to attachstream a connect-wait
18009 or resolve-wait stream.
18010 - Now do address rewriting when the controller asks us to attach
18011 to a particular circuit too. This will let Blossom specify
18012 "moria2.exit" without having to learn what moria2's IP address is.
18013 - Make the "tor --verify-config" command-line work again, so people
18014 can automatically check if their torrc will parse.
18015 - Authoritative dirservers no longer require an open connection from
18016 a server to consider him "reachable". We need this change because
18017 when we add new auth dirservers, old servers won't know not to
18019 - Let Tor build on Sun CC again.
18020 - Fix an off-by-one buffer size in dirserv.c that magically never
18021 hit our three authorities but broke sjmurdoch's own tor network.
18022 - If we as a directory mirror don't know of any v1 directory
18023 authorities, then don't try to cache any v1 directories.
18024 - Stop warning about unknown servers in our family when they are
18025 given as hex digests.
18026 - Stop complaining as quickly to the server operator that he
18027 hasn't registered his nickname/key binding.
18028 - Various cleanups so we can add new V2 Auth Dirservers.
18029 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
18030 reflect the updated flags in our v2 dir protocol.
18031 - Resume allowing non-printable characters for exit streams (both
18032 for connecting and for resolving). Now we tolerate applications
18033 that don't follow the RFCs. But continue to block malformed names
18036 o Bugfixes on 0.1.0.x:
18037 - Fix assert bug in close_logs(): when we close and delete logs,
18038 remove them all from the global "logfiles" list.
18039 - Fix minor integer overflow in calculating when we expect to use up
18040 our bandwidth allocation before hibernating.
18041 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
18042 there are multiple SSLs installed with different versions.
18043 - When we try to be a server and Address is not explicitly set and
18044 our hostname resolves to a private IP address, try to use an
18045 interface address if it has a public address. Now Windows machines
18046 that think of themselves as localhost can work by default.
18049 - Let the controller ask for GETINFO dir/server/foo so it can ask
18050 directly rather than connecting to the dir port.
18051 - Let the controller tell us about certain router descriptors
18052 that it doesn't want Tor to use in circuits. Implement
18053 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
18054 - New config option SafeSocks to reject all application connections
18055 using unsafe socks protocols. Defaults to off.
18058 Changes in version 0.1.1.15-rc - 2006-03-11
18059 o Bugfixes and cleanups:
18060 - When we're printing strings from the network, don't try to print
18061 non-printable characters. This protects us against shell escape
18062 sequence exploits, and also against attacks to fool humans into
18063 misreading their logs.
18064 - Fix a bug where Tor would fail to establish any connections if you
18065 left it off for 24 hours and then started it: we were happy with
18066 the obsolete network statuses, but they all referred to router
18067 descriptors that were too old to fetch, so we ended up with no
18068 valid router descriptors.
18069 - Fix a seg fault in the controller's "getinfo orconn-status"
18070 command while listing status on incoming handshaking connections.
18071 Introduce a status name "NEW" for these connections.
18072 - If we get a linelist or linelist_s config option from the torrc
18073 (e.g. ExitPolicy) and it has no value, warn and skip rather than
18074 silently resetting it to its default.
18075 - Don't abandon entry guards until they've been down or gone for
18077 - Cleaner and quieter log messages.
18080 - New controller signal NEWNYM that makes new application requests
18081 use clean circuits.
18082 - Add a new circuit purpose 'controller' to let the controller ask
18083 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
18084 controller command to let you specify the purpose if you're
18085 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
18086 command to let you change a circuit's purpose after it's been
18088 - Accept "private:*" in routerdesc exit policies; not generated yet
18089 because older Tors do not understand it.
18090 - Add BSD-style contributed startup script "rc.subr" from Peter
18094 Changes in version 0.1.1.14-alpha - 2006-02-20
18095 o Bugfixes on 0.1.1.x:
18096 - Don't die if we ask for a stdout or stderr log (even implicitly)
18097 and we're set to RunAsDaemon -- just warn.
18098 - We still had a few bugs in the OR connection rotation code that
18099 caused directory servers to slowly aggregate connections to other
18100 fast Tor servers. This time for sure!
18101 - Make log entries on Win32 include the name of the function again.
18102 - We were treating a pair of exit policies if they were equal even
18103 if one said accept and the other said reject -- causing us to
18104 not always publish a new descriptor since we thought nothing
18106 - Retry pending server downloads as well as pending networkstatus
18107 downloads when we unexpectedly get a socks request.
18108 - We were ignoring the IS_FAST flag in the directory status,
18109 meaning we were willing to pick trivial-bandwidth nodes for "fast"
18111 - If the controller's SAVECONF command fails (e.g. due to file
18112 permissions), let the controller know that it failed.
18115 - If we're trying to be a Tor server and running Windows 95/98/ME
18116 as a server, explain that we'll likely crash.
18117 - When we're a server, a client asks for an old-style directory,
18118 and our write bucket is empty, don't give it to him. This way
18119 small servers can continue to serve the directory *sometimes*,
18120 without getting overloaded.
18121 - Compress exit policies even more -- look for duplicate lines
18123 - Clients now honor the "guard" flag in the router status when
18124 picking entry guards, rather than looking at is_fast or is_stable.
18125 - Retain unrecognized lines in $DATADIR/state file, so that we can
18126 be forward-compatible.
18127 - Generate 18.0.0.0/8 address policy format in descs when we can;
18128 warn when the mask is not reducible to a bit-prefix.
18129 - Let the user set ControlListenAddress in the torrc. This can be
18130 dangerous, but there are some cases (like a secured LAN) where it
18132 - Split ReachableAddresses into ReachableDirAddresses and
18133 ReachableORAddresses, so we can restrict Dir conns to port 80
18134 and OR conns to port 443.
18135 - Now we can target arch and OS in rpm builds (contributed by
18136 Phobos). Also make the resulting dist-rpm filename match the
18138 - New config options to help controllers: FetchServerDescriptors
18139 and FetchHidServDescriptors for whether to fetch server
18140 info and hidserv info or let the controller do it, and
18141 PublishServerDescriptor and PublishHidServDescriptors.
18142 - Also let the controller set the __AllDirActionsPrivate config
18143 option if you want all directory fetches/publishes to happen via
18144 Tor (it assumes your controller bootstraps your circuits).
18147 Changes in version 0.1.0.17 - 2006-02-17
18148 o Crash bugfixes on 0.1.0.x:
18149 - When servers with a non-zero DirPort came out of hibernation,
18150 sometimes they would trigger an assert.
18152 o Other important bugfixes:
18153 - On platforms that don't have getrlimit (like Windows), we were
18154 artificially constraining ourselves to a max of 1024
18155 connections. Now just assume that we can handle as many as 15000
18156 connections. Hopefully this won't cause other problems.
18158 o Backported features:
18159 - When we're a server, a client asks for an old-style directory,
18160 and our write bucket is empty, don't give it to him. This way
18161 small servers can continue to serve the directory *sometimes*,
18162 without getting overloaded.
18163 - Whenever you get a 503 in response to a directory fetch, try
18164 once more. This will become important once servers start sending
18165 503's whenever they feel busy.
18166 - Fetch a new directory every 120 minutes, not every 40 minutes.
18167 Now that we have hundreds of thousands of users running the old
18168 directory algorithm, it's starting to hurt a lot.
18169 - Bump up the period for forcing a hidden service descriptor upload
18170 from 20 minutes to 1 hour.
18173 Changes in version 0.1.1.13-alpha - 2006-02-09
18174 o Crashes in 0.1.1.x:
18175 - When you tried to setconf ORPort via the controller, Tor would
18176 crash. So people using TorCP to become a server were sad.
18177 - Solve (I hope) the stack-smashing bug that we were seeing on fast
18178 servers. The problem appears to be something do with OpenSSL's
18179 random number generation, or how we call it, or something. Let me
18180 know if the crashes continue.
18181 - Turn crypto hardware acceleration off by default, until we find
18182 somebody smart who can test it for us. (It appears to produce
18183 seg faults in at least some cases.)
18184 - Fix a rare assert error when we've tried all intro points for
18185 a hidden service and we try fetching the service descriptor again:
18186 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
18189 - Fix a major load balance bug: we were round-robining in 16 KB
18190 chunks, and servers with bandwidthrate of 20 KB, while downloading
18191 a 600 KB directory, would starve their other connections. Now we
18192 try to be a bit more fair.
18193 - Dir authorities and mirrors were never expiring the newest
18194 descriptor for each server, causing memory and directory bloat.
18195 - Fix memory-bloating and connection-bloating bug on servers: We
18196 were never closing any connection that had ever had a circuit on
18197 it, because we were checking conn->n_circuits == 0, yet we had a
18198 bug that let it go negative.
18199 - Make Tor work using squid as your http proxy again -- squid
18200 returns an error if you ask for a URL that's too long, and it uses
18201 a really generic error message. Plus, many people are behind a
18202 transparent squid so they don't even realize it.
18203 - On platforms that don't have getrlimit (like Windows), we were
18204 artificially constraining ourselves to a max of 1024
18205 connections. Now just assume that we can handle as many as 15000
18206 connections. Hopefully this won't cause other problems.
18207 - Add a new config option ExitPolicyRejectPrivate which defaults to
18208 1. This means all exit policies will begin with rejecting private
18209 addresses, unless the server operator explicitly turns it off.
18212 - Clients no longer download descriptors for non-running
18214 - Before we add new directory authorities, we should make it
18215 clear that only v1 authorities should receive/publish hidden
18216 service descriptors.
18219 - As soon as we've fetched some more directory info, immediately
18220 try to download more server descriptors. This way we don't have
18221 a 10 second pause during initial bootstrapping.
18222 - Remove even more loud log messages that the server operator can't
18224 - When we're running an obsolete or un-recommended version, make
18225 the log message more clear about what the problem is and what
18226 versions *are* still recommended.
18227 - Provide a more useful warn message when our onion queue gets full:
18228 the CPU is too slow or the exit policy is too liberal.
18229 - Don't warn when we receive a 503 from a dirserver/cache -- this
18230 will pave the way for them being able to refuse if they're busy.
18231 - When we fail to bind a listener, try to provide a more useful
18232 log message: e.g., "Is Tor already running?"
18233 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
18234 Goldberg can prove things about our handshake protocol more
18236 - MaxConn has been obsolete for a while now. Document the ConnLimit
18237 config option, which is a *minimum* number of file descriptors
18238 that must be available else Tor refuses to start.
18239 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
18240 if you log to syslog and want something other than LOG_DAEMON.
18241 - Make dirservers generate a separate "guard" flag to mean,
18242 "would make a good entry guard". Make clients parse it and vote
18243 on it. Not used by clients yet.
18244 - Implement --with-libevent-dir option to ./configure. Also, improve
18245 search techniques to find libevent, and use those for openssl too.
18246 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
18247 - Only start testing reachability once we've established a
18248 circuit. This will make startup on dirservers less noisy.
18249 - Don't try to upload hidden service descriptors until we have
18250 established a circuit.
18251 - Fix the controller's "attachstream 0" command to treat conn like
18252 it just connected, doing address remapping, handling .exit and
18253 .onion idioms, and so on. Now we're more uniform in making sure
18254 that the controller hears about new and closing connections.
18257 Changes in version 0.1.1.12-alpha - 2006-01-11
18258 o Bugfixes on 0.1.1.x:
18259 - The fix to close duplicate server connections was closing all
18260 Tor client connections if they didn't establish a circuit
18261 quickly enough. Oops.
18262 - Fix minor memory issue (double-free) that happened on exit.
18264 o Bugfixes on 0.1.0.x:
18265 - Tor didn't warn when it failed to open a log file.
18268 Changes in version 0.1.1.11-alpha - 2006-01-10
18269 o Crashes in 0.1.1.x:
18270 - Include all the assert/crash fixes from 0.1.0.16.
18271 - If you start Tor and then quit very quickly, there were some
18272 races that tried to free things that weren't allocated yet.
18273 - Fix a rare memory stomp if you're running hidden services.
18274 - Fix segfault when specifying DirServer in config without nickname.
18275 - Fix a seg fault when you finish connecting to a server but at
18276 that moment you dump his server descriptor.
18277 - Extendcircuit and Attachstream controller commands would
18278 assert/crash if you don't give them enough arguments.
18279 - Fix an assert error when we're out of space in the connection_list
18280 and we try to post a hidden service descriptor (reported by weasel).
18281 - If you specify a relative torrc path and you set RunAsDaemon in
18282 your torrc, then it chdir()'s to the new directory. If you HUP,
18283 it tries to load the new torrc location, fails, and exits.
18284 The fix: no longer allow a relative path to torrc using -f.
18287 - Implement "entry guards": automatically choose a handful of entry
18288 nodes and stick with them for all circuits. Only pick new guards
18289 when the ones you have are unsuitable, and if the old guards
18290 become suitable again, switch back. This will increase security
18291 dramatically against certain end-point attacks. The EntryNodes
18292 config option now provides some hints about which entry guards you
18293 want to use most; and StrictEntryNodes means to only use those.
18294 - New directory logic: download by descriptor digest, not by
18295 fingerprint. Caches try to download all listed digests from
18296 authorities; clients try to download "best" digests from caches.
18297 This avoids partitioning and isolating attacks better.
18298 - Make the "stable" router flag in network-status be the median of
18299 the uptimes of running valid servers, and make clients pay
18300 attention to the network-status flags. Thus the cutoff adapts
18301 to the stability of the network as a whole, making IRC, IM, etc
18302 connections more reliable.
18305 - Tor servers with dynamic IP addresses were needing to wait 18
18306 hours before they could start doing reachability testing using
18307 the new IP address and ports. This is because they were using
18308 the internal descriptor to learn what to test, yet they were only
18309 rebuilding the descriptor once they decided they were reachable.
18310 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
18311 to download certain server descriptors, throw them away, and then
18312 fetch them again after 30 minutes. Now mirrors throw away these
18313 server descriptors so clients can't get them.
18314 - We were leaving duplicate connections to other ORs open for a week,
18315 rather than closing them once we detect a duplicate. This only
18316 really affected authdirservers, but it affected them a lot.
18317 - Spread the authdirservers' reachability testing over the entire
18318 testing interval, so we don't try to do 500 TLS's at once every
18322 - If the network is down, and we try to connect to a conn because
18323 we have a circuit in mind, and we timeout (30 seconds) because the
18324 network never answers, we were expiring the circuit, but we weren't
18325 obsoleting the connection or telling the entry_guards functions.
18326 - Some Tor servers process billions of cells per day. These statistics
18327 need to be uint64_t's.
18328 - Check for integer overflows in more places, when adding elements
18329 to smartlists. This could possibly prevent a buffer overflow
18330 on malicious huge inputs. I don't see any, but I haven't looked
18332 - ReachableAddresses kept growing new "reject *:*" lines on every
18334 - When you "setconf log" via the controller, it should remove all
18335 logs. We were automatically adding back in a "log notice stdout".
18336 - Newly bootstrapped Tor networks couldn't establish hidden service
18337 circuits until they had nodes with high uptime. Be more tolerant.
18338 - We were marking servers down when they could not answer every piece
18339 of the directory request we sent them. This was far too harsh.
18340 - Fix the torify (tsocks) config file to not use Tor for localhost
18342 - Directory authorities now go to the proper authority when asking for
18343 a networkstatus, even when they want a compressed one.
18344 - Fix a harmless bug that was causing Tor servers to log
18345 "Got an end because of misc error, but we're not an AP. Closing."
18346 - Authorities were treating their own descriptor changes as cosmetic,
18347 meaning the descriptor available in the network-status and the
18348 descriptor that clients downloaded were different.
18349 - The OS X installer was adding a symlink for tor_resolve but
18350 the binary was called tor-resolve (reported by Thomas Hardly).
18351 - Workaround a problem with some http proxies where they refuse GET
18352 requests that specify "Content-Length: 0" (reported by Adrian).
18353 - Fix wrong log message when you add a "HiddenServiceNodes" config
18354 line without any HiddenServiceDir line (reported by Chris Thomas).
18357 - Write the TorVersion into the state file so we have a prayer of
18358 keeping forward and backward compatibility.
18359 - Revive the FascistFirewall config option rather than eliminating it:
18360 now it's a synonym for ReachableAddresses *:80,*:443.
18361 - Clients choose directory servers from the network status lists,
18362 not from their internal list of router descriptors. Now they can
18363 go to caches directly rather than needing to go to authorities
18365 - Directory authorities ignore router descriptors that have only
18366 cosmetic differences: do this for 0.1.0.x servers now too.
18367 - Add a new flag to network-status indicating whether the server
18368 can answer v2 directory requests too.
18369 - Authdirs now stop whining so loudly about bad descriptors that
18370 they fetch from other dirservers. So when there's a log complaint,
18371 it's for sure from a freshly uploaded descriptor.
18372 - Reduce memory requirements in our structs by changing the order
18374 - There used to be two ways to specify your listening ports in a
18375 server descriptor: on the "router" line and with a separate "ports"
18376 line. Remove support for the "ports" line.
18377 - New config option "AuthDirRejectUnlisted" for auth dirservers as
18378 a panic button: if we get flooded with unusable servers we can
18379 revert to only listing servers in the approved-routers file.
18380 - Auth dir servers can now mark a fingerprint as "!reject" or
18381 "!invalid" in the approved-routers file (as its nickname), to
18382 refuse descriptors outright or include them but marked as invalid.
18383 - Servers store bandwidth history across restarts/crashes.
18384 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
18385 get a better idea of why their circuits failed. Not used yet.
18386 - Directory mirrors now cache up to 16 unrecognized network-status
18387 docs. Now we can add new authdirservers and they'll be cached too.
18388 - When picking a random directory, prefer non-authorities if any
18390 - New controller option "getinfo desc/all-recent" to fetch the
18391 latest server descriptor for every router that Tor knows about.
18394 Changes in version 0.1.0.16 - 2006-01-02
18395 o Crash bugfixes on 0.1.0.x:
18396 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
18397 corrupting the heap, losing FDs, or crashing when we need to resize
18398 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
18399 - It turns out sparc64 platforms crash on unaligned memory access
18400 too -- so detect and avoid this.
18401 - Handle truncated compressed data correctly (by detecting it and
18403 - Fix possible-but-unlikely free(NULL) in control.c.
18404 - When we were closing connections, there was a rare case that
18405 stomped on memory, triggering seg faults and asserts.
18406 - Avoid potential infinite recursion when building a descriptor. (We
18407 don't know that it ever happened, but better to fix it anyway.)
18408 - We were neglecting to unlink marked circuits from soon-to-close OR
18409 connections, which caused some rare scribbling on freed memory.
18410 - Fix a memory stomping race bug when closing the joining point of two
18411 rendezvous circuits.
18412 - Fix an assert in time parsing found by Steven Murdoch.
18414 o Other bugfixes on 0.1.0.x:
18415 - When we're doing reachability testing, provide more useful log
18416 messages so the operator knows what to expect.
18417 - Do not check whether DirPort is reachable when we are suppressing
18418 advertising it because of hibernation.
18419 - When building with -static or on Solaris, we sometimes needed -ldl.
18420 - When we're deciding whether a stream has enough circuits around
18421 that can handle it, count the freshly dirty ones and not the ones
18422 that are so dirty they won't be able to handle it.
18423 - When we're expiring old circuits, we had a logic error that caused
18424 us to close new rendezvous circuits rather than old ones.
18425 - Give a more helpful log message when you try to change ORPort via
18426 the controller: you should upgrade Tor if you want that to work.
18427 - We were failing to parse Tor versions that start with "Tor ".
18428 - Tolerate faulty streams better: when a stream fails for reason
18429 exitpolicy, stop assuming that the router is lying about his exit
18430 policy. When a stream fails for reason misc, allow it to retry just
18431 as if it was resolvefailed. When a stream has failed three times,
18432 reset its failure count so we can try again and get all three tries.
18435 Changes in version 0.1.1.10-alpha - 2005-12-11
18436 o Correctness bugfixes on 0.1.0.x:
18437 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
18438 corrupting the heap, losing FDs, or crashing when we need to resize
18439 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
18440 - Stop doing the complex voodoo overkill checking for insecure
18441 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
18442 - When we were closing connections, there was a rare case that
18443 stomped on memory, triggering seg faults and asserts.
18444 - We were neglecting to unlink marked circuits from soon-to-close OR
18445 connections, which caused some rare scribbling on freed memory.
18446 - When we're deciding whether a stream has enough circuits around
18447 that can handle it, count the freshly dirty ones and not the ones
18448 that are so dirty they won't be able to handle it.
18449 - Recover better from TCP connections to Tor servers that are
18450 broken but don't tell you (it happens!); and rotate TLS
18451 connections once a week.
18452 - When we're expiring old circuits, we had a logic error that caused
18453 us to close new rendezvous circuits rather than old ones.
18454 - Fix a scary-looking but apparently harmless bug where circuits
18455 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
18456 servers, and never switch to state CIRCUIT_STATE_OPEN.
18457 - When building with -static or on Solaris, we sometimes needed to
18459 - Give a useful message when people run Tor as the wrong user,
18460 rather than telling them to start chowning random directories.
18461 - We were failing to inform the controller about new .onion streams.
18463 o Security bugfixes on 0.1.0.x:
18464 - Refuse server descriptors if the fingerprint line doesn't match
18465 the included identity key. Tor doesn't care, but other apps (and
18466 humans) might actually be trusting the fingerprint line.
18467 - We used to kill the circuit when we receive a relay command we
18468 don't recognize. Now we just drop it.
18469 - Start obeying our firewall options more rigorously:
18470 . If we can't get to a dirserver directly, try going via Tor.
18471 . Don't ever try to connect (as a client) to a place our
18472 firewall options forbid.
18473 . If we specify a proxy and also firewall options, obey the
18474 firewall options even when we're using the proxy: some proxies
18475 can only proxy to certain destinations.
18476 - Fix a bug found by Lasse Overlier: when we were making internal
18477 circuits (intended to be cannibalized later for rendezvous and
18478 introduction circuits), we were picking them so that they had
18479 useful exit nodes. There was no need for this, and it actually
18480 aids some statistical attacks.
18481 - Start treating internal circuits and exit circuits separately.
18482 It's important to keep them separate because internal circuits
18483 have their last hops picked like middle hops, rather than like
18484 exit hops. So exiting on them will break the user's expectations.
18486 o Bugfixes on 0.1.1.x:
18487 - Take out the mis-feature where we tried to detect IP address
18488 flapping for people with DynDNS, and chose not to upload a new
18489 server descriptor sometimes.
18490 - Try to be compatible with OpenSSL 0.9.6 again.
18491 - Log fix: when the controller is logging about .onion addresses,
18492 sometimes it didn't include the ".onion" part of the address.
18493 - Don't try to modify options->DirServers internally -- if the
18494 user didn't specify any, just add the default ones directly to
18495 the trusted dirserver list. This fixes a bug where people running
18496 controllers would use SETCONF on some totally unrelated config
18497 option, and Tor would start yelling at them about changing their
18499 - Let the controller's redirectstream command specify a port, in
18500 case the controller wants to change that too.
18501 - When we requested a pile of server descriptors, we sometimes
18502 accidentally launched a duplicate request for the first one.
18503 - Bugfix for trackhostexits: write down the fingerprint of the
18504 chosen exit, not its nickname, because the chosen exit might not
18506 - When parsing foo.exit, if foo is unknown, and we are leaving
18507 circuits unattached, set the chosen_exit field and leave the
18508 address empty. This matters because controllers got confused
18510 - Directory authorities no longer try to download server
18511 descriptors that they know they will reject.
18513 o Features and updates:
18514 - Replace balanced trees with hash tables: this should make stuff
18515 significantly faster.
18516 - Resume using the AES counter-mode implementation that we ship,
18517 rather than OpenSSL's. Ours is significantly faster.
18518 - Many other CPU and memory improvements.
18519 - Add a new config option FastFirstHopPK (on by default) so clients
18520 do a trivial crypto handshake for their first hop, since TLS has
18521 already taken care of confidentiality and authentication.
18522 - Add a new config option TestSocks so people can see if their
18523 applications are using socks4, socks4a, socks5-with-ip, or
18524 socks5-with-hostname. This way they don't have to keep mucking
18525 with tcpdump and wondering if something got cached somewhere.
18526 - Warn when listening on a public address for socks. I suspect a
18527 lot of people are setting themselves up as open socks proxies,
18528 and they have no idea that jerks on the Internet are using them,
18529 since they simply proxy the traffic into the Tor network.
18530 - Add "private:*" as an alias in configuration for policies. Now
18531 you can simplify your exit policy rather than needing to list
18532 every single internal or nonroutable network space.
18533 - Add a new controller event type that allows controllers to get
18534 all server descriptors that were uploaded to a router in its role
18535 as authoritative dirserver.
18536 - Start shipping socks-extensions.txt, tor-doc-unix.html,
18537 tor-doc-server.html, and stylesheet.css in the tarball.
18538 - Stop shipping tor-doc.html in the tarball.
18541 Changes in version 0.1.1.9-alpha - 2005-11-15
18542 o Usability improvements:
18543 - Start calling it FooListenAddress rather than FooBindAddress,
18544 since few of our users know what it means to bind an address
18546 - Reduce clutter in server logs. We're going to try to make
18547 them actually usable now. New config option ProtocolWarnings that
18548 lets you hear about how _other Tors_ are breaking the protocol. Off
18550 - Divide log messages into logging domains. Once we put some sort
18551 of interface on this, it will let people looking at more verbose
18552 log levels specify the topics they want to hear more about.
18553 - Make directory servers return better http 404 error messages
18554 instead of a generic "Servers unavailable".
18555 - Check for even more Windows version flags when writing the platform
18556 string in server descriptors, and note any we don't recognize.
18557 - Clean up more of the OpenSSL memory when exiting, so we can detect
18558 memory leaks better.
18559 - Make directory authorities be non-versioning, non-naming by
18560 default. Now we can add new directory servers without requiring
18561 their operators to pay close attention.
18562 - When logging via syslog, include the pid whenever we provide
18563 a log entry. Suggested by Todd Fries.
18565 o Performance improvements:
18566 - Directory servers now silently throw away new descriptors that
18567 haven't changed much if the timestamps are similar. We do this to
18568 tolerate older Tor servers that upload a new descriptor every 15
18569 minutes. (It seemed like a good idea at the time.)
18570 - Inline bottleneck smartlist functions; use fast versions by default.
18571 - Add a "Map from digest to void*" abstraction digestmap_t so we
18572 can do less hex encoding/decoding. Use it in router_get_by_digest()
18573 to resolve a performance bottleneck.
18574 - Allow tor_gzip_uncompress to extract as much as possible from
18575 truncated compressed data. Try to extract as many
18576 descriptors as possible from truncated http responses (when
18577 DIR_PURPOSE_FETCH_ROUTERDESC).
18578 - Make circ->onionskin a pointer, not a static array. moria2 was using
18579 125000 circuit_t's after it had been up for a few weeks, which
18580 translates to 20+ megs of wasted space.
18581 - The private half of our EDH handshake keys are now chosen out
18582 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
18584 o Security improvements:
18585 - Start making directory caches retain old routerinfos, so soon
18586 clients can start asking by digest of descriptor rather than by
18587 fingerprint of server.
18588 - Add half our entropy from RAND_poll in OpenSSL. This knows how
18589 to use egd (if present), openbsd weirdness (if present), vms/os2
18590 weirdness (if we ever port there), and more in the future.
18592 o Bugfixes on 0.1.0.x:
18593 - Do round-robin writes of at most 16 kB per write. This might be
18594 more fair on loaded Tor servers, and it might resolve our Windows
18595 crash bug. It might also slow things down.
18596 - Our TLS handshakes were generating a single public/private
18597 keypair for the TLS context, rather than making a new one for
18598 each new connections. Oops. (But we were still rotating them
18599 periodically, so it's not so bad.)
18600 - When we were cannibalizing a circuit with a particular exit
18601 node in mind, we weren't checking to see if that exit node was
18602 already present earlier in the circuit. Oops.
18603 - When a Tor server's IP changes (e.g. from a dyndns address),
18604 upload a new descriptor so clients will learn too.
18605 - Really busy servers were keeping enough circuits open on stable
18606 connections that they were wrapping around the circuit_id
18607 space. (It's only two bytes.) This exposed a bug where we would
18608 feel free to reuse a circuit_id even if it still exists but has
18609 been marked for close. Try to fix this bug. Some bug remains.
18610 - If we would close a stream early (e.g. it asks for a .exit that
18611 we know would refuse it) but the LeaveStreamsUnattached config
18612 option is set by the controller, then don't close it.
18614 o Bugfixes on 0.1.1.8-alpha:
18615 - Fix a big pile of memory leaks, some of them serious.
18616 - Do not try to download a routerdesc if we would immediately reject
18618 - Resume inserting a newline between all router descriptors when
18619 generating (old style) signed directories, since our spec says
18621 - When providing content-type application/octet-stream for
18622 server descriptors using .z, we were leaving out the
18623 content-encoding header. Oops. (Everything tolerated this just
18624 fine, but that doesn't mean we need to be part of the problem.)
18625 - Fix a potential seg fault in getconf and getinfo using version 1
18626 of the controller protocol.
18627 - Avoid crash: do not check whether DirPort is reachable when we
18628 are suppressing it because of hibernation.
18629 - Make --hash-password not crash on exit.
18632 Changes in version 0.1.1.8-alpha - 2005-10-07
18633 o New features (major):
18634 - Clients don't download or use the directory anymore. Now they
18635 download and use network-statuses from the trusted dirservers,
18636 and fetch individual server descriptors as needed from mirrors.
18637 See dir-spec.txt for all the gory details.
18638 - Be more conservative about whether to advertise our DirPort.
18639 The main change is to not advertise if we're running at capacity
18640 and either a) we could hibernate or b) our capacity is low and
18641 we're using a default DirPort.
18642 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
18644 o New features (minor):
18645 - Try to be smart about when to retry network-status and
18646 server-descriptor fetches. Still needs some tuning.
18647 - Stop parsing, storing, or using running-routers output (but
18648 mirrors still cache and serve it).
18649 - Consider a threshold of versioning dirservers (dirservers who have
18650 an opinion about which Tor versions are still recommended) before
18651 deciding whether to warn the user that he's obsolete.
18652 - Dirservers can now reject/invalidate by key and IP, with the
18653 config options "AuthDirInvalid" and "AuthDirReject". This is
18654 useful since currently we automatically list servers as running
18655 and usable even if we know they're jerks.
18656 - Provide dire warnings to any users who set DirServer; move it out
18657 of torrc.sample and into torrc.complete.
18658 - Add MyFamily to torrc.sample in the server section.
18659 - Add nicknames to the DirServer line, so we can refer to them
18660 without requiring all our users to memorize their IP addresses.
18661 - When we get an EOF or a timeout on a directory connection, note
18662 how many bytes of serverdesc we are dropping. This will help
18663 us determine whether it is smart to parse incomplete serverdesc
18665 - Add a new function to "change pseudonyms" -- that is, to stop
18666 using any currently-dirty circuits for new streams, so we don't
18667 link new actions to old actions. Currently it's only called on
18668 HUP (or SIGNAL RELOAD).
18669 - On sighup, if UseHelperNodes changed to 1, use new circuits.
18670 - Start using RAND_bytes rather than RAND_pseudo_bytes from
18671 OpenSSL. Also, reseed our entropy every hour, not just at
18672 startup. And entropy in 512-bit chunks, not 160-bit chunks.
18674 o Fixes on 0.1.1.7-alpha:
18675 - Nobody ever implemented EVENT_ADDRMAP for control protocol
18676 version 0, so don't let version 0 controllers ask for it.
18677 - If you requested something with too many newlines via the
18678 v1 controller protocol, you could crash tor.
18679 - Fix a number of memory leaks, including some pretty serious ones.
18680 - Re-enable DirPort testing again, so Tor servers will be willing
18681 to advertise their DirPort if it's reachable.
18682 - On TLS handshake, only check the other router's nickname against
18683 its expected nickname if is_named is set.
18685 o Fixes forward-ported from 0.1.0.15:
18686 - Don't crash when we don't have any spare file descriptors and we
18687 try to spawn a dns or cpu worker.
18688 - Make the numbers in read-history and write-history into uint64s,
18689 so they don't overflow and publish negatives in the descriptor.
18691 o Fixes on 0.1.0.x:
18692 - For the OS X package's modified privoxy config file, comment
18693 out the "logfile" line so we don't log everything passed
18695 - We were whining about using socks4 or socks5-with-local-lookup
18696 even when it's an IP in the "virtual" range we designed exactly
18698 - We were leaking some memory every time the client changes IPs.
18699 - Never call free() on tor_malloc()d memory. This will help us
18700 use dmalloc to detect memory leaks.
18701 - Check for named servers when looking them up by nickname;
18702 warn when we'recalling a non-named server by its nickname;
18703 don't warn twice about the same name.
18704 - Try to list MyFamily elements by key, not by nickname, and warn
18705 if we've not heard of the server.
18706 - Make windows platform detection (uname equivalent) smarter.
18707 - It turns out sparc64 doesn't like unaligned access either.
18710 Changes in version 0.1.0.15 - 2005-09-23
18711 o Bugfixes on 0.1.0.x:
18712 - Reject ports 465 and 587 (spam targets) in default exit policy.
18713 - Don't crash when we don't have any spare file descriptors and we
18714 try to spawn a dns or cpu worker.
18715 - Get rid of IgnoreVersion undocumented config option, and make us
18716 only warn, never exit, when we're running an obsolete version.
18717 - Don't try to print a null string when your server finds itself to
18718 be unreachable and the Address config option is empty.
18719 - Make the numbers in read-history and write-history into uint64s,
18720 so they don't overflow and publish negatives in the descriptor.
18721 - Fix a minor memory leak in smartlist_string_remove().
18722 - We were only allowing ourselves to upload a server descriptor at
18723 most every 20 minutes, even if it changed earlier than that.
18724 - Clean up log entries that pointed to old URLs.
18727 Changes in version 0.1.1.7-alpha - 2005-09-14
18728 o Fixes on 0.1.1.6-alpha:
18729 - Exit servers were crashing when people asked them to make a
18730 connection to an address not in their exit policy.
18731 - Looking up a non-existent stream for a v1 control connection would
18733 - Fix a seg fault if we ask a dirserver for a descriptor by
18734 fingerprint but he doesn't know about him.
18735 - SETCONF was appending items to linelists, not clearing them.
18736 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
18737 out and refuse the setconf if it would fail.
18738 - Downgrade the dirserver log messages when whining about
18742 - Add Peter Palfrader's check-tor script to tor/contrib/
18743 It lets you easily check whether a given server (referenced by
18744 nickname) is reachable by you.
18745 - Numerous changes to move towards client-side v2 directories. Not
18748 o Fixes on 0.1.0.x:
18749 - If the user gave tor an odd number of command-line arguments,
18750 we were silently ignoring the last one. Now we complain and fail.
18751 [This wins the oldest-bug prize -- this bug has been present since
18752 November 2002, as released in Tor 0.0.0.]
18753 - Do not use unaligned memory access on alpha, mips, or mipsel.
18754 It *works*, but is very slow, so we treat them as if it doesn't.
18755 - Retry directory requests if we fail to get an answer we like
18756 from a given dirserver (we were retrying before, but only if
18757 we fail to connect).
18758 - When writing the RecommendedVersions line, sort them first.
18759 - When the client asked for a rendezvous port that the hidden
18760 service didn't want to provide, we were sending an IP address
18761 back along with the end cell. Fortunately, it was zero. But stop
18763 - Correct "your server is reachable" log entries to indicate that
18764 it was self-testing that told us so.
18767 Changes in version 0.1.1.6-alpha - 2005-09-09
18768 o Fixes on 0.1.1.5-alpha:
18769 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
18770 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
18771 - Fix bug with tor_memmem finding a match at the end of the string.
18772 - Make unit tests run without segfaulting.
18773 - Resolve some solaris x86 compile warnings.
18774 - Handle duplicate lines in approved-routers files without warning.
18775 - Fix bug where as soon as a server refused any requests due to his
18776 exit policy (e.g. when we ask for localhost and he tells us that's
18777 127.0.0.1 and he won't do it), we decided he wasn't obeying his
18778 exit policy using him for any exits.
18779 - Only do openssl hardware accelerator stuff if openssl version is
18782 o New controller features/fixes:
18783 - Add a "RESETCONF" command so you can set config options like
18784 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
18785 a config option in the torrc with no value, then it clears it
18786 entirely (rather than setting it to its default).
18787 - Add a "GETINFO config-file" to tell us where torrc is.
18788 - Avoid sending blank lines when GETINFO replies should be empty.
18789 - Add a QUIT command for the controller (for using it manually).
18790 - Fix a bug in SAVECONF that was adding default dirservers and
18791 other redundant entries to the torrc file.
18793 o Start on the new directory design:
18794 - Generate, publish, cache, serve new network-status format.
18795 - Publish individual descriptors (by fingerprint, by "all", and by
18797 - Publish client and server recommended versions separately.
18798 - Allow tor_gzip_uncompress() to handle multiple concatenated
18799 compressed strings. Serve compressed groups of router
18800 descriptors. The compression logic here could be more
18802 - Distinguish v1 authorities (all currently trusted directories)
18803 from v2 authorities (all trusted directories).
18804 - Change DirServers config line to note which dirs are v1 authorities.
18805 - Add configuration option "V1AuthoritativeDirectory 1" which
18806 moria1, moria2, and tor26 should set.
18807 - Remove option when getting directory cache to see whether they
18808 support running-routers; they all do now. Replace it with one
18809 to see whether caches support v2 stuff.
18812 - Dirservers now do their own external reachability testing of each
18813 Tor server, and only list them as running if they've been found to
18814 be reachable. We also send back warnings to the server's logs if
18815 it uploads a descriptor that we already believe is unreachable.
18816 - Implement exit enclaves: if we know an IP address for the
18817 destination, and there's a running Tor server at that address
18818 which allows exit to the destination, then extend the circuit to
18819 that exit first. This provides end-to-end encryption and end-to-end
18820 authentication. Also, if the user wants a .exit address or enclave,
18821 use 4 hops rather than 3, and cannibalize a general circ for it
18823 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
18824 controller. Also, rotate dns and cpu workers if the controller
18825 changes options that will affect them; and initialize the dns
18826 worker cache tree whether or not we start out as a server.
18827 - Only upload a new server descriptor when options change, 18
18828 hours have passed, uptime is reset, or bandwidth changes a lot.
18829 - Check [X-]Forwarded-For headers in HTTP requests when generating
18830 log messages. This lets people run dirservers (and caches) behind
18831 Apache but still know which IP addresses are causing warnings.
18833 o Config option changes:
18834 - Replace (Fascist)Firewall* config options with a new
18835 ReachableAddresses option that understands address policies.
18836 For example, "ReachableAddresses *:80,*:443"
18837 - Get rid of IgnoreVersion undocumented config option, and make us
18838 only warn, never exit, when we're running an obsolete version.
18839 - Make MonthlyAccountingStart config option truly obsolete now.
18841 o Fixes on 0.1.0.x:
18842 - Reject ports 465 and 587 in the default exit policy, since
18843 people have started using them for spam too.
18844 - It turns out we couldn't bootstrap a network since we added
18845 reachability detection in 0.1.0.1-rc. Good thing the Tor network
18846 has never gone down. Add an AssumeReachable config option to let
18847 servers and dirservers bootstrap. When we're trying to build a
18848 high-uptime or high-bandwidth circuit but there aren't enough
18849 suitable servers, try being less picky rather than simply failing.
18850 - Our logic to decide if the OR we connected to was the right guy
18851 was brittle and maybe open to a mitm for unverified routers.
18852 - We weren't cannibalizing circuits correctly for
18853 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
18854 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
18855 build those from scratch. This should make hidden services faster.
18856 - Predict required circuits better, with an eye toward making hidden
18857 services faster on the service end.
18858 - Retry streams if the exit node sends back a 'misc' failure. This
18859 should result in fewer random failures. Also, after failing
18860 from resolve failed or misc, reset the num failures, so we give
18861 it a fair shake next time we try.
18862 - Clean up the rendezvous warn log msgs, and downgrade some to info.
18863 - Reduce severity on logs about dns worker spawning and culling.
18864 - When we're shutting down and we do something like try to post a
18865 server descriptor or rendezvous descriptor, don't complain that
18866 we seem to be unreachable. Of course we are, we're shutting down.
18867 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
18868 We don't use them yet, but maybe one day our DNS resolver will be
18869 able to discover them.
18870 - Make ContactInfo mandatory for authoritative directory servers.
18871 - Require server descriptors to list IPv4 addresses -- hostnames
18872 are no longer allowed. This also fixes some potential security
18873 problems with people providing hostnames as their address and then
18874 preferentially resolving them to partition users.
18875 - Change log line for unreachability to explicitly suggest /etc/hosts
18876 as the culprit. Also make it clearer what IP address and ports we're
18877 testing for reachability.
18878 - Put quotes around user-supplied strings when logging so users are
18879 more likely to realize if they add bad characters (like quotes)
18881 - Let auth dir servers start without specifying an Address config
18883 - Make unit tests (and other invocations that aren't the real Tor)
18884 run without launching listeners, creating subdirectories, and so on.
18887 Changes in version 0.1.1.5-alpha - 2005-08-08
18888 o Bugfixes included in 0.1.0.14.
18890 o Bugfixes on 0.1.0.x:
18891 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
18892 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
18893 it would silently using ignore the 6668.
18896 Changes in version 0.1.0.14 - 2005-08-08
18897 o Bugfixes on 0.1.0.x:
18898 - Fix the other half of the bug with crypto handshakes
18900 - Fix an assert trigger if you send a 'signal term' via the
18901 controller when it's listening for 'event info' messages.
18904 Changes in version 0.1.1.4-alpha - 2005-08-04
18905 o Bugfixes included in 0.1.0.13.
18908 - Improve tor_gettimeofday() granularity on windows.
18909 - Make clients regenerate their keys when their IP address changes.
18910 - Implement some more GETINFO goodness: expose helper nodes, config
18911 options, getinfo keys.
18914 Changes in version 0.1.0.13 - 2005-08-04
18915 o Bugfixes on 0.1.0.x:
18916 - Fix a critical bug in the security of our crypto handshakes.
18917 - Fix a size_t underflow in smartlist_join_strings2() that made
18918 it do bad things when you hand it an empty smartlist.
18919 - Fix Windows installer to ship Tor license (thanks to Aphex for
18920 pointing out this oversight) and put a link to the doc directory
18922 - Explicitly set no-unaligned-access for sparc: it turns out the
18923 new gcc's let you compile broken code, but that doesn't make it
18927 Changes in version 0.1.1.3-alpha - 2005-07-23
18928 o Bugfixes on 0.1.1.2-alpha:
18929 - Fix a bug in handling the controller's "post descriptor"
18931 - Fix several bugs in handling the controller's "extend circuit"
18933 - Fix a bug in handling the controller's "stream status" event.
18934 - Fix an assert failure if we have a controller listening for
18935 circuit events and we go offline.
18936 - Re-allow hidden service descriptors to publish 0 intro points.
18937 - Fix a crash when generating your hidden service descriptor if
18938 you don't have enough intro points already.
18940 o New features on 0.1.1.2-alpha:
18941 - New controller function "getinfo accounting", to ask how
18942 many bytes we've used in this time period.
18943 - Experimental support for helper nodes: a lot of the risk from
18944 a small static adversary comes because users pick new random
18945 nodes every time they rebuild a circuit. Now users will try to
18946 stick to the same small set of entry nodes if they can. Not
18947 enabled by default yet.
18949 o Bugfixes on 0.1.0.12:
18950 - If you're an auth dir server, always publish your dirport,
18951 even if you haven't yet found yourself to be reachable.
18952 - Fix a size_t underflow in smartlist_join_strings2() that made
18953 it do bad things when you hand it an empty smartlist.
18956 Changes in version 0.1.0.12 - 2005-07-18
18957 o New directory servers:
18958 - tor26 has changed IP address.
18960 o Bugfixes on 0.1.0.x:
18961 - Fix a possible double-free in tor_gzip_uncompress().
18962 - When --disable-threads is set, do not search for or link against
18963 pthreads libraries.
18964 - Don't trigger an assert if an authoritative directory server
18965 claims its dirport is 0.
18966 - Fix bug with removing Tor as an NT service: some people were
18967 getting "The service did not return an error." Thanks to Matt
18971 Changes in version 0.1.1.2-alpha - 2005-07-15
18972 o New directory servers:
18973 - tor26 has changed IP address.
18975 o Bugfixes on 0.1.0.x, crashes/leaks:
18976 - Port the servers-not-obeying-their-exit-policies fix from
18978 - Fix an fd leak in start_daemon().
18979 - On Windows, you can't always reopen a port right after you've
18980 closed it. So change retry_listeners() to only close and re-open
18981 ports that have changed.
18982 - Fix a possible double-free in tor_gzip_uncompress().
18984 o Bugfixes on 0.1.0.x, usability:
18985 - When tor_socketpair() fails in Windows, give a reasonable
18986 Windows-style errno back.
18987 - Let people type "tor --install" as well as "tor -install" when
18989 want to make it an NT service.
18990 - NT service patch from Matt Edman to improve error messages.
18991 - When the controller asks for a config option with an abbreviated
18992 name, give the full name in our response.
18993 - Correct the man page entry on TrackHostExitsExpire.
18994 - Looks like we were never delivering deflated (i.e. compressed)
18995 running-routers lists, even when asked. Oops.
18996 - When --disable-threads is set, do not search for or link against
18997 pthreads libraries.
18999 o Bugfixes on 0.1.1.x:
19000 - Fix a seg fault with autodetecting which controller version is
19004 - New hidden service descriptor format: put a version in it, and
19005 let people specify introduction/rendezvous points that aren't
19006 in "the directory" (which is subjective anyway).
19007 - Allow the DEBUG controller event to work again. Mark certain log
19008 entries as "don't tell this to controllers", so we avoid cycles.
19011 Changes in version 0.1.0.11 - 2005-06-30
19012 o Bugfixes on 0.1.0.x:
19013 - Fix major security bug: servers were disregarding their
19014 exit policies if clients behaved unexpectedly.
19015 - Make OS X init script check for missing argument, so we don't
19016 confuse users who invoke it incorrectly.
19017 - Fix a seg fault in "tor --hash-password foo".
19018 - The MAPADDRESS control command was broken.
19021 Changes in version 0.1.1.1-alpha - 2005-06-29
19023 - Make OS X init script check for missing argument, so we don't
19024 confuse users who invoke it incorrectly.
19025 - Fix a seg fault in "tor --hash-password foo".
19026 - Fix a possible way to DoS dirservers.
19027 - When we complain that your exit policy implicitly allows local or
19028 private address spaces, name them explicitly so operators can
19030 - Make the log message less scary when all the dirservers are
19031 temporarily unreachable.
19032 - We were printing the number of idle dns workers incorrectly when
19036 - Revised controller protocol (version 1) that uses ascii rather
19037 than binary. Add supporting libraries in python and java so you
19038 can use the controller from your applications without caring how
19039 our protocol works.
19040 - Spiffy new support for crypto hardware accelerators. Can somebody
19044 Changes in version 0.0.9.10 - 2005-06-16
19045 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
19046 - Refuse relay cells that claim to have a length larger than the
19047 maximum allowed. This prevents a potential attack that could read
19048 arbitrary memory (e.g. keys) from an exit server's process
19052 Changes in version 0.1.0.10 - 2005-06-14
19053 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
19054 libevent before 1.1a.
19057 Changes in version 0.1.0.9-rc - 2005-06-09
19059 - Reset buf->highwater every time buf_shrink() is called, not just on
19060 a successful shrink. This was causing significant memory bloat.
19061 - Fix buffer overflow when checking hashed passwords.
19062 - Security fix: if seeding the RNG on Win32 fails, quit.
19063 - Allow seeding the RNG on Win32 even when you're not running as
19065 - Disable threading on Solaris too. Something is wonky with it,
19066 cpuworkers, and reentrant libs.
19067 - Reenable the part of the code that tries to flush as soon as an
19068 OR outbuf has a full TLS record available. Perhaps this will make
19069 OR outbufs not grow as huge except in rare cases, thus saving lots
19070 of CPU time plus memory.
19071 - Reject malformed .onion addresses rather then passing them on as
19072 normal web requests.
19073 - Adapt patch from Adam Langley: fix possible memory leak in
19074 tor_lookup_hostname().
19075 - Initialize libevent later in the startup process, so the logs are
19076 already established by the time we start logging libevent warns.
19077 - Use correct errno on win32 if libevent fails.
19078 - Check and warn about known-bad/slow libevent versions.
19079 - Pay more attention to the ClientOnly config option.
19080 - Have torctl.in/tor.sh.in check for location of su binary (needed
19082 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
19083 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
19084 HttpProxyAuthenticator
19085 - Stop warning about sigpipes in the logs. We're going to
19086 pretend that getting these occassionally is normal and fine.
19087 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
19089 installer screens; and don't put stuff into StartupItems unless
19090 the user asks you to.
19091 - Require servers that use the default dirservers to have public IP
19092 addresses. We have too many servers that are configured with private
19093 IPs and their admins never notice the log entries complaining that
19094 their descriptors are being rejected.
19095 - Add OSX uninstall instructions. An actual uninstall script will
19099 Changes in version 0.1.0.8-rc - 2005-05-23
19101 - It turns out that kqueue on OS X 10.3.9 was causing kernel
19102 panics. Disable kqueue on all OS X Tors.
19103 - Fix RPM: remove duplicate line accidentally added to the rpm
19105 - Disable threads on openbsd too, since its gethostaddr is not
19107 - Tolerate libevent 0.8 since it still works, even though it's
19109 - Enable building on Red Hat 9.0 again.
19110 - Allow the middle hop of the testing circuit to be running any
19111 version, now that most of them have the bugfix to let them connect
19112 to unknown servers. This will allow reachability testing to work
19113 even when 0.0.9.7-0.0.9.9 become obsolete.
19114 - Handle relay cells with rh.length too large. This prevents
19115 a potential attack that could read arbitrary memory (maybe even
19116 keys) from the exit server's process.
19117 - We screwed up the dirport reachability testing when we don't yet
19118 have a cached version of the directory. Hopefully now fixed.
19119 - Clean up router_load_single_router() (used by the controller),
19120 so it doesn't seg fault on error.
19121 - Fix a minor memory leak when somebody establishes an introduction
19122 point at your Tor server.
19123 - If a socks connection ends because read fails, don't warn that
19124 you're not sending a socks reply back.
19127 - Add HttpProxyAuthenticator config option too, that works like
19128 the HttpsProxyAuthenticator config option.
19129 - Encode hashed controller passwords in hex instead of base64,
19130 to make it easier to write controllers.
19133 Changes in version 0.1.0.7-rc - 2005-05-17
19135 - Fix a bug in the OS X package installer that prevented it from
19136 installing on Tiger.
19137 - Fix a script bug in the OS X package installer that made it
19138 complain during installation.
19139 - Find libevent even if it's hiding in /usr/local/ and your
19140 CFLAGS and LDFLAGS don't tell you to look there.
19141 - Be able to link with libevent as a shared library (the default
19142 after 1.0d), even if it's hiding in /usr/local/lib and even
19143 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
19144 assuming you're running gcc. Otherwise fail and give a useful
19146 - Fix a bug in the RPM packager: set home directory for _tor to
19147 something more reasonable when first installing.
19148 - Free a minor amount of memory that is still reachable on exit.
19151 Changes in version 0.1.0.6-rc - 2005-05-14
19153 - Implement --disable-threads configure option. Disable threads on
19154 netbsd by default, because it appears to have no reentrant resolver
19156 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
19157 release (1.1) detects and disables kqueue if it's broken.
19158 - Append default exit policy before checking for implicit internal
19159 addresses. Now we don't log a bunch of complaints on startup
19160 when using the default exit policy.
19161 - Some people were putting "Address " in their torrc, and they had
19162 a buggy resolver that resolved " " to 0.0.0.0. Oops.
19163 - If DataDir is ~/.tor, and that expands to /.tor, then default to
19164 LOCALSTATEDIR/tor instead.
19165 - Fix fragmented-message bug in TorControl.py.
19166 - Resolve a minor bug which would prevent unreachable dirports
19167 from getting suppressed in the published descriptor.
19168 - When the controller gave us a new descriptor, we weren't resolving
19169 it immediately, so Tor would think its address was 0.0.0.0 until
19170 we fetched a new directory.
19171 - Fix an uppercase/lowercase case error in suppressing a bogus
19172 libevent warning on some Linuxes.
19175 - Begin scrubbing sensitive strings from logs by default. Turn off
19176 the config option SafeLogging if you need to do debugging.
19177 - Switch to a new buffer management algorithm, which tries to avoid
19178 reallocing and copying quite as much. In first tests it looks like
19179 it uses *more* memory on average, but less cpu.
19180 - First cut at support for "create-fast" cells. Clients can use
19181 these when extending to their first hop, since the TLS already
19182 provides forward secrecy and authentication. Not enabled on
19184 - When dirservers refuse a router descriptor, we now log its
19185 contactinfo, platform, and the poster's IP address.
19186 - Call tor_free_all instead of connections_free_all after forking, to
19187 save memory on systems that need to fork.
19188 - Whine at you if you're a server and you don't set your contactinfo.
19189 - Implement --verify-config command-line option to check if your torrc
19190 is valid without actually launching Tor.
19191 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
19192 rather than just rejecting it.
19195 Changes in version 0.1.0.5-rc - 2005-04-27
19197 - Stop trying to print a null pointer if an OR conn fails because
19198 we didn't like its cert.
19200 - Switch our internal buffers implementation to use a ring buffer,
19201 to hopefully improve performance for fast servers a lot.
19202 - Add HttpsProxyAuthenticator support (basic auth only), based
19203 on patch from Adam Langley.
19204 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
19205 the fast servers that have been joining lately.
19206 - Give hidden service accesses extra time on the first attempt,
19207 since 60 seconds is often only barely enough. This might improve
19209 - Improve performance for dirservers: stop re-parsing the whole
19210 directory every time you regenerate it.
19211 - Add more debugging info to help us find the weird dns freebsd
19212 pthreads bug; cleaner debug messages to help track future issues.
19215 Changes in version 0.0.9.9 - 2005-04-23
19216 o Bugfixes on 0.0.9.x:
19217 - If unofficial Tor clients connect and send weird TLS certs, our
19218 Tor server triggers an assert. This release contains a minimal
19219 backport from the broader fix that we put into 0.1.0.4-rc.
19222 Changes in version 0.1.0.4-rc - 2005-04-23
19224 - If unofficial Tor clients connect and send weird TLS certs, our
19225 Tor server triggers an assert. Stop asserting, and start handling
19226 TLS errors better in other situations too.
19227 - When the controller asks us to tell it about all the debug-level
19228 logs, it turns out we were generating debug-level logs while
19229 telling it about them, which turns into a bad loop. Now keep
19230 track of whether you're sending a debug log to the controller,
19231 and don't log when you are.
19232 - Fix the "postdescriptor" feature of the controller interface: on
19233 non-complete success, only say "done" once.
19235 - Clients are now willing to load balance over up to 2mB, not 1mB,
19236 of advertised bandwidth capacity.
19237 - Add a NoPublish config option, so you can be a server (e.g. for
19238 testing running Tor servers in other Tor networks) without
19239 publishing your descriptor to the primary dirservers.
19242 Changes in version 0.1.0.3-rc - 2005-04-08
19243 o Improvements on 0.1.0.2-rc:
19244 - Client now retries when streams end early for 'hibernating' or
19245 'resource limit' reasons, rather than failing them.
19246 - More automated handling for dirserver operators:
19247 - Automatically approve nodes running 0.1.0.2-rc or later,
19248 now that the the reachability detection stuff is working.
19249 - Now we allow two unverified servers with the same nickname
19250 but different keys. But if a nickname is verified, only that
19251 nickname+key are allowed.
19252 - If you're an authdirserver connecting to an address:port,
19253 and it's not the OR you were expecting, forget about that
19254 descriptor. If he *was* the one you were expecting, then forget
19255 about all other descriptors for that address:port.
19256 - Allow servers to publish descriptors from 12 hours in the future.
19257 Corollary: only whine about clock skew from the dirserver if
19258 he's a trusted dirserver (since now even verified servers could
19259 have quite wrong clocks).
19260 - Adjust maximum skew and age for rendezvous descriptors: let skew
19261 be 48 hours rather than 90 minutes.
19262 - Efficiency improvements:
19263 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
19264 it much faster to look up a circuit for each relay cell.
19265 - Remove most calls to assert_all_pending_dns_resolves_ok(),
19266 since they're eating our cpu on exit nodes.
19267 - Stop wasting time doing a case insensitive comparison for every
19268 dns name every time we do any lookup. Canonicalize the names to
19269 lowercase and be done with it.
19270 - Start sending 'truncated' cells back rather than destroy cells,
19271 if the circuit closes in front of you. This means we won't have
19272 to abandon partially built circuits.
19273 - Only warn once per nickname from add_nickname_list_to_smartlist
19274 per failure, so an entrynode or exitnode choice that's down won't
19276 - Put a note in the torrc about abuse potential with the default
19278 - Revise control spec and implementation to allow all log messages to
19279 be sent to controller with their severities intact (suggested by
19280 Matt Edman). Update TorControl to handle new log event types.
19281 - Provide better explanation messages when controller's POSTDESCRIPTOR
19283 - Stop putting nodename in the Platform string in server descriptors.
19284 It doesn't actually help, and it is confusing/upsetting some people.
19286 o Bugfixes on 0.1.0.2-rc:
19287 - We were printing the host mask wrong in exit policies in server
19288 descriptors. This isn't a critical bug though, since we were still
19289 obeying the exit policy internally.
19290 - Fix Tor when compiled with libevent but without pthreads: move
19291 connection_unregister() from _connection_free() to
19293 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
19294 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
19295 when we look through the connection array, we'll find any of the
19296 cpu/dnsworkers. This is no good.
19298 o Bugfixes on 0.0.9.8:
19299 - Fix possible bug on threading platforms (e.g. win32) which was
19300 leaking a file descriptor whenever a cpuworker or dnsworker died.
19301 - When using preferred entry or exit nodes, ignore whether the
19302 circuit wants uptime or capacity. They asked for the nodes, they
19304 - chdir() to your datadirectory at the *end* of the daemonize process,
19305 not the beginning. This was a problem because the first time you
19306 run tor, if your datadir isn't there, and you have runasdaemon set
19307 to 1, it will try to chdir to it before it tries to create it. Oops.
19308 - Handle changed router status correctly when dirserver reloads
19309 fingerprint file. We used to be dropping all unverified descriptors
19310 right then. The bug was hidden because we would immediately
19311 fetch a directory from another dirserver, which would include the
19312 descriptors we just dropped.
19313 - When we're connecting to an OR and he's got a different nickname/key
19314 than we were expecting, only complain loudly if we're an OP or a
19315 dirserver. Complaining loudly to the OR admins just confuses them.
19316 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
19317 artificially capped at 500kB.
19320 Changes in version 0.0.9.8 - 2005-04-07
19321 o Bugfixes on 0.0.9.x:
19322 - We have a bug that I haven't found yet. Sometimes, very rarely,
19323 cpuworkers get stuck in the 'busy' state, even though the cpuworker
19324 thinks of itself as idle. This meant that no new circuits ever got
19325 established. Here's a workaround to kill any cpuworker that's been
19326 busy for more than 100 seconds.
19329 Changes in version 0.1.0.2-rc - 2005-04-01
19330 o Bugfixes on 0.1.0.1-rc:
19331 - Fixes on reachability detection:
19332 - Don't check for reachability while hibernating.
19333 - If ORPort is reachable but DirPort isn't, still publish the
19334 descriptor, but zero out DirPort until it's found reachable.
19335 - When building testing circs for ORPort testing, use only
19336 high-bandwidth nodes, so fewer circuits fail.
19337 - Complain about unreachable ORPort separately from unreachable
19338 DirPort, so the user knows what's going on.
19339 - Make sure we only conclude ORPort reachability if we didn't
19340 initiate the conn. Otherwise we could falsely conclude that
19341 we're reachable just because we connected to the guy earlier
19342 and he used that same pipe to extend to us.
19343 - Authdirservers shouldn't do ORPort reachability detection,
19344 since they're in clique mode, so it will be rare to find a
19345 server not already connected to them.
19346 - When building testing circuits, always pick middle hops running
19347 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
19348 bug. (This is a kludge; it will go away when 0.0.9.x becomes
19350 - When we decide we're reachable, actually publish our descriptor
19352 - Fix bug in redirectstream in the controller.
19353 - Fix the state descriptor strings so logs don't claim edge streams
19354 are in a different state than they actually are.
19355 - Use recent libevent features when possible (this only really affects
19356 win32 and osx right now, because the new libevent with these
19357 features hasn't been released yet). Add code to suppress spurious
19359 - Prevent possible segfault in connection_close_unattached_ap().
19360 - Fix newlines on torrc in win32.
19361 - Improve error msgs when tor-resolve fails.
19363 o Improvements on 0.0.9.x:
19364 - New experimental script tor/contrib/ExerciseServer.py (needs more
19365 work) that uses the controller interface to build circuits and
19366 fetch pages over them. This will help us bootstrap servers that
19367 have lots of capacity but haven't noticed it yet.
19368 - New experimental script tor/contrib/PathDemo.py (needs more work)
19369 that uses the controller interface to let you choose whole paths
19371 "<hostname>.<path,separated by dots>.<length of path>.path"
19372 - When we've connected to an OR and handshaked but didn't like
19373 the result, we were closing the conn without sending destroy
19374 cells back for pending circuits. Now send those destroys.
19377 Changes in version 0.0.9.7 - 2005-04-01
19378 o Bugfixes on 0.0.9.x:
19379 - Fix another race crash bug (thanks to Glenn Fink for reporting).
19380 - Compare identity to identity, not to nickname, when extending to
19381 a router not already in the directory. This was preventing us from
19382 extending to unknown routers. Oops.
19383 - Make sure to create OS X Tor user in <500 range, so we aren't
19384 creating actual system users.
19385 - Note where connection-that-hasn't-sent-end was marked, and fix
19386 a few really loud instances of this harmless bug (it's fixed more
19390 Changes in version 0.1.0.1-rc - 2005-03-28
19392 - Add reachability testing. Your Tor server will automatically try
19393 to see if its ORPort and DirPort are reachable from the outside,
19394 and it won't upload its descriptor until it decides they are.
19395 - Handle unavailable hidden services better. Handle slow or busy
19396 hidden services better.
19397 - Add support for CONNECTing through https proxies, with "HttpsProxy"
19399 - New exit policy: accept most low-numbered ports, rather than
19400 rejecting most low-numbered ports.
19401 - More Tor controller support (still experimental). See
19402 http://tor.eff.org/doc/control-spec.txt for all the new features,
19403 including signals to emulate unix signals from any platform;
19404 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
19405 closestream; closecircuit; etc.
19406 - Make nt services work and start on startup on win32 (based on
19407 patch by Matt Edman).
19408 - Add a new AddressMap config directive to rewrite incoming socks
19409 addresses. This lets you, for example, declare an implicit
19410 required exit node for certain sites.
19411 - Add a new TrackHostExits config directive to trigger addressmaps
19412 for certain incoming socks addresses -- for sites that break when
19413 your exit keeps changing (based on patch by Mike Perry).
19414 - Redo the client-side dns cache so it's just an addressmap too.
19415 - Notice when our IP changes, and reset stats/uptime/reachability.
19416 - When an application is using socks5, give him the whole variety of
19417 potential socks5 responses (connect refused, host unreachable, etc),
19418 rather than just "success" or "failure".
19419 - A more sane version numbering system. See
19420 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
19421 - New contributed script "exitlist": a simple python script to
19422 parse directories and find Tor nodes that exit to listed
19424 - New contributed script "privoxy-tor-toggle" to toggle whether
19425 Privoxy uses Tor. Seems to be configured for Debian by default.
19426 - Report HTTP reasons to client when getting a response from directory
19427 servers -- so you can actually know what went wrong.
19428 - New config option MaxAdvertisedBandwidth which lets you advertise
19429 a low bandwidthrate (to not attract as many circuits) while still
19430 allowing a higher bandwidthrate in reality.
19432 o Robustness/stability fixes:
19433 - Make Tor use Niels Provos's libevent instead of its current
19434 poll-but-sometimes-select mess. This will let us use faster async
19435 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
19437 - pthread support now too. This was forced because when we forked,
19438 we ended up wasting a lot of duplicate ram over time. Also switch
19439 to foo_r versions of some library calls to allow reentry and
19441 - Better handling for heterogeneous / unreliable nodes:
19442 - Annotate circuits w/ whether they aim to contain high uptime nodes
19443 and/or high capacity nodes. When building circuits, choose
19445 - This means that every single node in an intro rend circuit,
19446 not just the last one, will have a minimum uptime.
19447 - New config option LongLivedPorts to indicate application streams
19448 that will want high uptime circuits.
19449 - Servers reset uptime when a dir fetch entirely fails. This
19450 hopefully reflects stability of the server's network connectivity.
19451 - If somebody starts his tor server in Jan 2004 and then fixes his
19452 clock, don't make his published uptime be a year.
19453 - Reset published uptime when you wake up from hibernation.
19454 - Introduce a notion of 'internal' circs, which are chosen without
19455 regard to the exit policy of the last hop. Intro and rendezvous
19456 circs must be internal circs, to avoid leaking information. Resolve
19457 and connect streams can use internal circs if they want.
19458 - New circuit pooling algorithm: make sure to have enough circs around
19459 to satisfy any predicted ports, and also make sure to have 2 internal
19460 circs around if we've required internal circs lately (and with high
19461 uptime if we've seen that lately too).
19462 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
19463 which describes how often we retry making new circuits if current
19464 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
19465 how long we're willing to make use of an already-dirty circuit.
19466 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
19467 circ as necessary, if there are any completed ones lying around
19468 when we try to launch one.
19469 - Make hidden services try to establish a rendezvous for 30 seconds,
19470 rather than for n (where n=3) attempts to build a circuit.
19471 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
19472 "ShutdownWaitLength".
19473 - Try to be more zealous about calling connection_edge_end when
19474 things go bad with edge conns in connection.c.
19475 - Revise tor-spec to add more/better stream end reasons.
19476 - Revise all calls to connection_edge_end to avoid sending "misc",
19477 and to take errno into account where possible.
19480 - Fix a race condition that can trigger an assert, when we have a
19481 pending create cell and an OR connection fails right then.
19482 - Fix several double-mark-for-close bugs, e.g. where we were finding
19483 a conn for a cell even if that conn is already marked for close.
19484 - Make sequence of log messages when starting on win32 with no config
19485 file more reasonable.
19486 - When choosing an exit node for a new non-internal circ, don't take
19487 into account whether it'll be useful for any pending x.onion
19488 addresses -- it won't.
19489 - Turn addr_policy_compare from a tristate to a quadstate; this should
19490 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
19491 for google.com" problem.
19492 - Make "platform" string in descriptor more accurate for Win32 servers,
19493 so it's not just "unknown platform".
19494 - Fix an edge case in parsing config options (thanks weasel).
19495 If they say "--" on the commandline, it's not an option.
19496 - Reject odd-looking addresses at the client (e.g. addresses that
19497 contain a colon), rather than having the server drop them because
19499 - tor-resolve requests were ignoring .exit if there was a working circuit
19500 they could use instead.
19501 - REUSEADDR on normal platforms means you can rebind to the port
19502 right after somebody else has let it go. But REUSEADDR on win32
19503 means to let you bind to the port _even when somebody else
19504 already has it bound_! So, don't do that on Win32.
19505 - Change version parsing logic: a version is "obsolete" if it is not
19506 recommended and (1) there is a newer recommended version in the
19507 same series, or (2) there are no recommended versions in the same
19508 series, but there are some recommended versions in a newer series.
19509 A version is "new" if it is newer than any recommended version in
19511 - Stop most cases of hanging up on a socks connection without sending
19515 - Require BandwidthRate to be at least 20kB/s for servers.
19516 - When a dirserver causes you to give a warn, mention which dirserver
19518 - New config option DirAllowPrivateAddresses for authdirservers.
19519 Now by default they refuse router descriptors that have non-IP or
19520 private-IP addresses.
19521 - Stop publishing socksport in the directory, since it's not
19522 actually meant to be public. For compatibility, publish a 0 there
19524 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
19525 smart" value, that is low for servers and high for clients.
19526 - If our clock jumps forward by 100 seconds or more, assume something
19527 has gone wrong with our network and abandon all not-yet-used circs.
19528 - Warn when exit policy implicitly allows local addresses.
19529 - If we get an incredibly skewed timestamp from a dirserver mirror
19530 that isn't a verified OR, don't warn -- it's probably him that's
19532 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
19533 cookies to disk and doesn't log each web request to disk. (Thanks
19534 to Brett Carrington for pointing this out.)
19535 - When a client asks us for a dir mirror and we don't have one,
19536 launch an attempt to get a fresh one.
19537 - If we're hibernating and we get a SIGINT, exit immediately.
19538 - Add --with-dmalloc ./configure option, to track memory leaks.
19539 - And try to free all memory on closing, so we can detect what
19541 - Cache local dns resolves correctly even when they're .exit
19543 - Give a better warning when some other server advertises an
19544 ORPort that is actually an apache running ssl.
19545 - Add "opt hibernating 1" to server descriptor to make it clearer
19546 whether the server is hibernating.
19549 Changes in version 0.0.9.6 - 2005-03-24
19550 o Bugfixes on 0.0.9.x (crashes and asserts):
19551 - Add new end stream reasons to maintainance branch. Fix bug where
19552 reason (8) could trigger an assert. Prevent bug from recurring.
19553 - Apparently win32 stat wants paths to not end with a slash.
19554 - Fix assert triggers in assert_cpath_layer_ok(), where we were
19555 blowing away the circuit that conn->cpath_layer points to, then
19556 checking to see if the circ is well-formed. Backport check to make
19557 sure we dont use the cpath on a closed connection.
19558 - Prevent circuit_resume_edge_reading_helper() from trying to package
19559 inbufs for marked-for-close streams.
19560 - Don't crash on hup if your options->address has become unresolvable.
19561 - Some systems (like OS X) sometimes accept() a connection and tell
19562 you the remote host is 0.0.0.0:0. If this happens, due to some
19563 other mis-features, we get confused; so refuse the conn for now.
19565 o Bugfixes on 0.0.9.x (other):
19566 - Fix harmless but scary "Unrecognized content encoding" warn message.
19567 - Add new stream error reason: TORPROTOCOL reason means "you are not
19568 speaking a version of Tor I understand; say bye-bye to your stream."
19569 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
19570 into the future, now that we are more tolerant of skew. This
19571 resolves a bug where a Tor server would refuse to cache a directory
19572 because all the directories it gets are too far in the future;
19573 yet the Tor server never logs any complaints about clock skew.
19574 - Mac packaging magic: make man pages useable, and do not overwrite
19575 existing torrc files.
19576 - Make OS X log happily to /var/log/tor/tor.log
19579 Changes in version 0.0.9.5 - 2005-02-22
19580 o Bugfixes on 0.0.9.x:
19581 - Fix an assert race at exit nodes when resolve requests fail.
19582 - Stop picking unverified dir mirrors--it only leads to misery.
19583 - Patch from Matt Edman to make NT services work better. Service
19584 support is still not compiled into the executable by default.
19585 - Patch from Dmitri Bely so the Tor service runs better under
19586 the win32 SYSTEM account.
19587 - Make tor-resolve actually work (?) on Win32.
19588 - Fix a sign bug when getrlimit claims to have 4+ billion
19589 file descriptors available.
19590 - Stop refusing to start when bandwidthburst == bandwidthrate.
19591 - When create cells have been on the onion queue more than five
19592 seconds, just send back a destroy and take them off the list.
19595 Changes in version 0.0.9.4 - 2005-02-03
19596 o Bugfixes on 0.0.9:
19597 - Fix an assert bug that took down most of our servers: when
19598 a server claims to have 1 GB of bandwidthburst, don't
19600 - Don't crash as badly if we have spawned the max allowed number
19601 of dnsworkers, or we're out of file descriptors.
19602 - Block more file-sharing ports in the default exit policy.
19603 - MaxConn is now automatically set to the hard limit of max
19604 file descriptors we're allowed (ulimit -n), minus a few for
19606 - Give a clearer message when servers need to raise their
19607 ulimit -n when they start running out of file descriptors.
19608 - SGI Compatibility patches from Jan Schaumann.
19609 - Tolerate a corrupt cached directory better.
19610 - When a dirserver hasn't approved your server, list which one.
19611 - Go into soft hibernation after 95% of the bandwidth is used,
19612 not 99%. This is especially important for daily hibernators who
19613 have a small accounting max. Hopefully it will result in fewer
19614 cut connections when the hard hibernation starts.
19615 - Load-balance better when using servers that claim more than
19616 800kB/s of capacity.
19617 - Make NT services work (experimental, only used if compiled in).
19620 Changes in version 0.0.9.3 - 2005-01-21
19621 o Bugfixes on 0.0.9:
19622 - Backport the cpu use fixes from main branch, so busy servers won't
19623 need as much processor time.
19624 - Work better when we go offline and then come back, or when we
19625 run Tor at boot before the network is up. We do this by
19626 optimistically trying to fetch a new directory whenever an
19627 application request comes in and we think we're offline -- the
19628 human is hopefully a good measure of when the network is back.
19629 - Backport some minimal hidserv bugfixes: keep rend circuits open as
19630 long as you keep using them; actually publish hidserv descriptors
19631 shortly after they change, rather than waiting 20-40 minutes.
19632 - Enable Mac startup script by default.
19633 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
19634 - When you update AllowUnverifiedNodes or FirewallPorts via the
19635 controller's setconf feature, we were always appending, never
19637 - When you update HiddenServiceDir via setconf, it was screwing up
19638 the order of reading the lines, making it fail.
19639 - Do not rewrite a cached directory back to the cache; otherwise we
19640 will think it is recent and not fetch a newer one on startup.
19641 - Workaround for webservers that lie about Content-Encoding: Tor
19642 now tries to autodetect compressed directories and compression
19643 itself. This lets us Proxypass dir fetches through apache.
19646 Changes in version 0.0.9.2 - 2005-01-04
19647 o Bugfixes on 0.0.9 (crashes and asserts):
19648 - Fix an assert on startup when the disk is full and you're logging
19650 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
19651 style address, then we'd crash.
19652 - Fix an assert trigger when the running-routers string we get from
19653 a dirserver is broken.
19654 - Make worker threads start and run on win32. Now win32 servers
19656 - Bandaid (not actually fix, but now it doesn't crash) an assert
19657 where the dns worker dies mysteriously and the main Tor process
19658 doesn't remember anything about the address it was resolving.
19660 o Bugfixes on 0.0.9 (Win32):
19661 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
19662 name out of the warning/assert messages.
19663 - Fix a superficial "unhandled error on read" bug on win32.
19664 - The win32 installer no longer requires a click-through for our
19665 license, since our Free Software license grants rights but does not
19667 - Win32: When connecting to a dirserver fails, try another one
19668 immediately. (This was already working for non-win32 Tors.)
19669 - Stop trying to parse $HOME on win32 when hunting for default
19671 - Make tor-resolve.c work on win32 by calling network_init().
19673 o Bugfixes on 0.0.9 (other):
19674 - Make 0.0.9.x build on Solaris again.
19675 - Due to a fencepost error, we were blowing away the \n when reporting
19676 confvalue items in the controller. So asking for multiple config
19677 values at once couldn't work.
19678 - When listing circuits that are pending on an opening OR connection,
19679 if we're an OR we were listing circuits that *end* at us as
19680 being pending on every listener, dns/cpu worker, etc. Stop that.
19681 - Dirservers were failing to create 'running-routers' or 'directory'
19682 strings if we had more than some threshold of routers. Fix them so
19683 they can handle any number of routers.
19684 - Fix a superficial "Duplicate mark for close" bug.
19685 - Stop checking for clock skew for OR connections, even for servers.
19686 - Fix a fencepost error that was chopping off the last letter of any
19687 nickname that is the maximum allowed nickname length.
19688 - Update URLs in log messages so they point to the new website.
19689 - Fix a potential problem in mangling server private keys while
19690 writing to disk (not triggered yet, as far as we know).
19691 - Include the licenses for other free software we include in Tor,
19692 now that we're shipping binary distributions more regularly.
19695 Changes in version 0.0.9.1 - 2004-12-15
19696 o Bugfixes on 0.0.9:
19697 - Make hibernation actually work.
19698 - Make HashedControlPassword config option work.
19699 - When we're reporting event circuit status to a controller,
19700 don't use the stream status code.
19703 Changes in version 0.0.9 - 2004-12-12
19705 - Clean up manpage and torrc.sample file.
19706 - Clean up severities and text of log warnings.
19708 - Make servers trigger an assert when they enter hibernation.
19711 Changes in version 0.0.9rc7 - 2004-12-08
19712 o Bugfixes on 0.0.9rc:
19713 - Fix a stack-trashing crash when an exit node begins hibernating.
19714 - Avoid looking at unallocated memory while considering which
19715 ports we need to build circuits to cover.
19716 - Stop a sigpipe: when an 'end' cell races with eof from the app,
19717 we shouldn't hold-open-until-flush if the eof arrived first.
19718 - Fix a bug with init_cookie_authentication() in the controller.
19719 - When recommending new-format log lines, if the upper bound is
19720 LOG_ERR, leave it implicit.
19722 o Bugfixes on 0.0.8.1:
19723 - Fix a whole slew of memory leaks.
19724 - Fix isspace() and friends so they still make Solaris happy
19725 but also so they don't trigger asserts on win32.
19726 - Fix parse_iso_time on platforms without strptime (eg win32).
19727 - win32: tolerate extra "readable" events better.
19728 - win32: when being multithreaded, leave parent fdarray open.
19729 - Make unit tests work on win32.
19732 Changes in version 0.0.9rc6 - 2004-12-06
19733 o Bugfixes on 0.0.9pre:
19734 - Clean up some more integer underflow opportunities (not exploitable
19736 - While hibernating, hup should not regrow our listeners.
19737 - Send an end to the streams we close when we hibernate, rather
19738 than just chopping them off.
19739 - React to eof immediately on non-open edge connections.
19741 o Bugfixes on 0.0.8.1:
19742 - Calculate timeout for waiting for a connected cell from the time
19743 we sent the begin cell, not from the time the stream started. If
19744 it took a long time to establish the circuit, we would time out
19745 right after sending the begin cell.
19746 - Fix router_compare_addr_to_addr_policy: it was not treating a port
19747 of * as always matching, so we were picking reject *:* nodes as
19748 exit nodes too. Oops.
19751 - New circuit building strategy: keep a list of ports that we've
19752 used in the past 6 hours, and always try to have 2 circuits open
19753 or on the way that will handle each such port. Seed us with port
19754 80 so web users won't complain that Tor is "slow to start up".
19755 - Make kill -USR1 dump more useful stats about circuits.
19756 - When warning about retrying or giving up, print the address, so
19757 the user knows which one it's talking about.
19758 - If you haven't used a clean circuit in an hour, throw it away,
19759 just to be on the safe side. (This means after 6 hours a totally
19760 unused Tor client will have no circuits open.)
19763 Changes in version 0.0.9rc5 - 2004-12-01
19764 o Bugfixes on 0.0.8.1:
19765 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
19766 - Let resolve conns retry/expire also, rather than sticking around
19768 - If we are using select, make sure we stay within FD_SETSIZE.
19770 o Bugfixes on 0.0.9pre:
19771 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
19772 but doesn't seem to be currently; thanks to Ilja van Sprundel for
19774 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
19775 instead. Impose minima and maxima for all *Period options; impose
19776 even tighter maxima for fetching if we are a caching dirserver.
19777 Clip rather than rejecting.
19778 - Fetch cached running-routers from servers that serve it (that is,
19779 authdirservers and servers running 0.0.9rc5-cvs or later.)
19782 - Accept *:706 (silc) in default exit policy.
19783 - Implement new versioning format for post 0.1.
19784 - Support "foo.nickname.exit" addresses, to let Alice request the
19785 address "foo" as viewed by exit node "nickname". Based on a patch
19787 - Make tor --version --version dump the cvs Id of every file.
19790 Changes in version 0.0.9rc4 - 2004-11-28
19791 o Bugfixes on 0.0.8.1:
19792 - Make windows sockets actually non-blocking (oops), and handle
19793 win32 socket errors better.
19795 o Bugfixes on 0.0.9rc1:
19796 - Actually catch the -USR2 signal.
19799 Changes in version 0.0.9rc3 - 2004-11-25
19800 o Bugfixes on 0.0.8.1:
19801 - Flush the log file descriptor after we print "Tor opening log file",
19802 so we don't see those messages days later.
19804 o Bugfixes on 0.0.9rc1:
19805 - Make tor-resolve work again.
19806 - Avoid infinite loop in tor-resolve if tor hangs up on it.
19807 - Fix an assert trigger for clients/servers handling resolves.
19810 Changes in version 0.0.9rc2 - 2004-11-24
19811 o Bugfixes on 0.0.9rc1:
19812 - I broke socks5 support while fixing the eof bug.
19813 - Allow unitless bandwidths and intervals; they default to bytes
19815 - New servers don't start out hibernating; they are active until
19816 they run out of bytes, so they have a better estimate of how
19817 long it takes, and so their operators can know they're working.
19820 Changes in version 0.0.9rc1 - 2004-11-23
19821 o Bugfixes on 0.0.8.1:
19822 - Finally fix a bug that's been plaguing us for a year:
19823 With high load, circuit package window was reaching 0. Whenever
19824 we got a circuit-level sendme, we were reading a lot on each
19825 socket, but only writing out a bit. So we would eventually reach
19826 eof. This would be noticed and acted on even when there were still
19827 bytes sitting in the inbuf.
19828 - When poll() is interrupted, we shouldn't believe the revents values.
19830 o Bugfixes on 0.0.9pre6:
19831 - Fix hibernate bug that caused pre6 to be broken.
19832 - Don't keep rephist info for routers that haven't had activity for
19833 24 hours. (This matters now that clients have keys, since we track
19835 - Never call close_temp_logs while validating log options.
19836 - Fix backslash-escaping on tor.sh.in and torctl.in.
19839 - Implement weekly/monthly/daily accounting: now you specify your
19840 hibernation properties by
19841 AccountingMax N bytes|KB|MB|GB|TB
19842 AccountingStart day|week|month [day] HH:MM
19843 Defaults to "month 1 0:00".
19844 - Let bandwidth and interval config options be specified as 5 bytes,
19845 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
19846 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
19847 get back to normal.)
19848 - If your requested entry or exit node has advertised bandwidth 0,
19850 - Be more greedy about filling up relay cells -- we try reading again
19851 once we've processed the stuff we read, in case enough has arrived
19852 to fill the last cell completely.
19853 - Apply NT service patch from Osamu Fujino. Still needs more work.
19856 Changes in version 0.0.9pre6 - 2004-11-15
19857 o Bugfixes on 0.0.8.1:
19858 - Fix assert failure on malformed socks4a requests.
19859 - Use identity comparison, not nickname comparison, to choose which
19860 half of circuit-ID-space each side gets to use. This is needed
19861 because sometimes we think of a router as a nickname, and sometimes
19862 as a hex ID, and we can't predict what the other side will do.
19863 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
19864 write() call will fail and we handle it there.
19865 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
19866 and smartlist_len, which are two major profiling offenders.
19868 o Bugfixes on 0.0.9pre5:
19869 - Fix a bug in read_all that was corrupting config files on windows.
19870 - When we're raising the max number of open file descriptors to
19871 'unlimited', don't log that we just raised it to '-1'.
19872 - Include event code with events, as required by control-spec.txt.
19873 - Don't give a fingerprint when clients do --list-fingerprint:
19874 it's misleading, because it will never be the same again.
19875 - Stop using strlcpy in tor_strndup, since it was slowing us
19877 - Remove warn on startup about missing cached-directory file.
19878 - Make kill -USR1 work again.
19879 - Hibernate if we start tor during the "wait for wakeup-time" phase
19880 of an accounting interval. Log our hibernation plans better.
19881 - Authoritative dirservers now also cache their directory, so they
19882 have it on start-up.
19885 - Fetch running-routers; cache running-routers; compress
19886 running-routers; serve compressed running-routers.z
19887 - Add NSI installer script contributed by J Doe.
19888 - Commit VC6 and VC7 workspace/project files.
19889 - Commit a tor.spec for making RPM files, with help from jbash.
19890 - Add contrib/torctl.in contributed by Glenn Fink.
19891 - Implement the control-spec's SAVECONF command, to write your
19892 configuration to torrc.
19893 - Get cookie authentication for the controller closer to working.
19894 - Include control-spec.txt in the tarball.
19895 - When set_conf changes our server descriptor, upload a new copy.
19896 But don't upload it too often if there are frequent changes.
19897 - Document authentication config in man page, and document signals
19899 - Clean up confusing parts of man page and torrc.sample.
19900 - Make expand_filename handle ~ and ~username.
19901 - Use autoconf to enable largefile support where necessary. Use
19902 ftello where available, since ftell can fail at 2GB.
19903 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
19904 log more informatively.
19905 - Give a slightly more useful output for "tor -h".
19906 - Refuse application socks connections to port 0.
19907 - Check clock skew for verified servers, but allow unverified
19908 servers and clients to have any clock skew.
19909 - Break DirFetchPostPeriod into:
19910 - DirFetchPeriod for fetching full directory,
19911 - StatusFetchPeriod for fetching running-routers,
19912 - DirPostPeriod for posting server descriptor,
19913 - RendPostPeriod for posting hidden service descriptors.
19914 - Make sure the hidden service descriptors are at a random offset
19915 from each other, to hinder linkability.
19918 Changes in version 0.0.9pre5 - 2004-11-09
19919 o Bugfixes on 0.0.9pre4:
19920 - Fix a seg fault in unit tests (doesn't affect main program).
19921 - Fix an assert bug where a hidden service provider would fail if
19922 the first hop of his rendezvous circuit was down.
19923 - Hidden service operators now correctly handle version 1 style
19924 INTRODUCE1 cells (nobody generates them still, so not a critical
19926 - If do_hup fails, actually notice.
19927 - Handle more errnos from accept() without closing the listener.
19928 Some OpenBSD machines were closing their listeners because
19929 they ran out of file descriptors.
19930 - Send resolve cells to exit routers that are running a new
19931 enough version of the resolve code to work right.
19932 - Better handling of winsock includes on non-MSV win32 compilers.
19933 - Some people had wrapped their tor client/server in a script
19934 that would restart it whenever it died. This did not play well
19935 with our "shut down if your version is obsolete" code. Now people
19936 don't fetch a new directory if their local cached version is
19938 - Make our autogen.sh work on ksh as well as bash.
19941 - Hibernation: New config option "AccountingMaxKB" lets you
19942 set how many KBytes per month you want to allow your server to
19943 consume. Rather than spreading those bytes out evenly over the
19944 month, we instead hibernate for some of the month and pop up
19945 at a deterministic time, work until the bytes are consumed, then
19946 hibernate again. Config option "MonthlyAccountingStart" lets you
19947 specify which day of the month your billing cycle starts on.
19948 - Control interface: a separate program can now talk to your
19949 client/server over a socket, and get/set config options, receive
19950 notifications of circuits and streams starting/finishing/dying,
19951 bandwidth used, etc. The next step is to get some GUIs working.
19952 Let us know if you want to help out. See doc/control-spec.txt .
19953 - Ship a contrib/tor-control.py as an example script to interact
19954 with the control port.
19955 - "tor --hash-password zzyxz" will output a salted password for
19956 use in authenticating to the control interface.
19957 - New log format in config:
19958 "Log minsev[-maxsev] stdout|stderr|syslog" or
19959 "Log minsev[-maxsev] file /var/foo"
19962 - DirPolicy config option, to let people reject incoming addresses
19963 from their dirserver.
19964 - "tor --list-fingerprint" will list your identity key fingerprint
19966 - Add "pass" target for RedirectExit, to make it easier to break
19967 out of a sequence of RedirectExit rules.
19968 - Clients now generate a TLS cert too, in preparation for having
19969 them act more like real nodes.
19970 - Ship src/win32/ in the tarball, so people can use it to build.
19971 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
19973 - New "router-status" line in directory, to better bind each verified
19974 nickname to its identity key.
19975 - Deprecate unofficial config option abbreviations, and abbreviations
19976 not on the command line.
19977 - Add a pure-C tor-resolve implementation.
19978 - Use getrlimit and friends to ensure we can reach MaxConn (currently
19979 1024) file descriptors.
19981 o Code security improvements, inspired by Ilja:
19982 - Replace sprintf with snprintf. (I think they were all safe, but
19984 - Replace strcpy/strncpy with strlcpy in more places.
19985 - Avoid strcat; use snprintf or strlcat instead.
19986 - snprintf wrapper with consistent (though not C99) overflow behavior.
19989 Changes in version 0.0.9pre4 - 2004-10-17
19990 o Bugfixes on 0.0.9pre3:
19991 - If the server doesn't specify an exit policy, use the real default
19992 exit policy, not reject *:*.
19993 - Ignore fascistfirewall when uploading/downloading hidden service
19994 descriptors, since we go through Tor for those; and when using
19995 an HttpProxy, since we assume it can reach them all.
19996 - When looking for an authoritative dirserver, use only the ones
19997 configured at boot. Don't bother looking in the directory.
19998 - The rest of the fix for get_default_conf_file() on older win32.
19999 - Make 'Routerfile' config option obsolete.
20002 - New 'MyFamily nick1,...' config option for a server to
20003 specify other servers that shouldn't be used in the same circuit
20004 with it. Only believed if nick1 also specifies us.
20005 - New 'NodeFamily nick1,nick2,...' config option for a client to
20006 specify nodes that it doesn't want to use in the same circuit.
20007 - New 'Redirectexit pattern address:port' config option for a
20008 server to redirect exit connections, e.g. to a local squid.
20011 Changes in version 0.0.9pre3 - 2004-10-13
20012 o Bugfixes on 0.0.8.1:
20013 - Better torrc example lines for dirbindaddress and orbindaddress.
20014 - Improved bounds checking on parsed ints (e.g. config options and
20015 the ones we find in directories.)
20016 - Better handling of size_t vs int, so we're more robust on 64
20018 - Fix the rest of the bug where a newly started OR would appear
20019 as unverified even after we've added his fingerprint and hupped
20021 - Fix a bug from 0.0.7: when read() failed on a stream, we would
20022 close it without sending back an end. So 'connection refused'
20023 would simply be ignored and the user would get no response.
20025 o Bugfixes on 0.0.9pre2:
20026 - Serving the cached-on-disk directory to people is bad. We now
20027 provide no directory until we've fetched a fresh one.
20028 - Workaround for bug on windows where cached-directories get crlf
20030 - Make get_default_conf_file() work on older windows too.
20031 - If we write a *:* exit policy line in the descriptor, don't write
20032 any more exit policy lines.
20035 - Use only 0.0.9pre1 and later servers for resolve cells.
20036 - Make the dirservers file obsolete.
20037 - Include a dir-signing-key token in directories to tell the
20038 parsing entity which key is being used to sign.
20039 - Remove the built-in bulky default dirservers string.
20040 - New config option "Dirserver %s:%d [fingerprint]", which can be
20041 repeated as many times as needed. If no dirservers specified,
20042 default to moria1,moria2,tor26.
20043 - Make moria2 advertise a dirport of 80, so people behind firewalls
20044 will be able to get a directory.
20045 - Http proxy support
20046 - Dirservers translate requests for http://%s:%d/x to /x
20047 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
20048 be routed through this host.
20049 - Clients ask for /tor/x rather than /x for new enough dirservers.
20050 This way we can one day coexist peacefully with apache.
20051 - Clients specify a "Host: %s%d" http header, to be compatible
20052 with more proxies, and so running squid on an exit node can work.
20055 Changes in version 0.0.8.1 - 2004-10-13
20057 - Fix a seg fault that can be triggered remotely for Tor
20058 clients/servers with an open dirport.
20059 - Fix a rare assert trigger, where routerinfos for entries in
20060 our cpath would expire while we're building the path.
20061 - Fix a bug in OutboundBindAddress so it (hopefully) works.
20062 - Fix a rare seg fault for people running hidden services on
20063 intermittent connections.
20064 - Fix a bug in parsing opt keywords with objects.
20065 - Fix a stale pointer assert bug when a stream detaches and
20067 - Fix a string format vulnerability (probably not exploitable)
20068 in reporting stats locally.
20069 - Fix an assert trigger: sometimes launching circuits can fail
20070 immediately, e.g. because too many circuits have failed recently.
20071 - Fix a compile warning on 64 bit platforms.
20074 Changes in version 0.0.9pre2 - 2004-10-03
20076 - Make fetching a cached directory work for 64-bit platforms too.
20077 - Make zlib.h a required header, not an optional header.
20080 Changes in version 0.0.9pre1 - 2004-10-01
20082 - Stop using separate defaults for no-config-file and
20083 empty-config-file. Now you have to explicitly turn off SocksPort,
20084 if you don't want it open.
20085 - Fix a bug in OutboundBindAddress so it (hopefully) works.
20086 - Improve man page to mention more of the 0.0.8 features.
20087 - Fix a rare seg fault for people running hidden services on
20088 intermittent connections.
20089 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
20091 - Fix more dns related bugs: send back resolve_failed and end cells
20092 more reliably when the resolve fails, rather than closing the
20093 circuit and then trying to send the cell. Also attach dummy resolve
20094 connections to a circuit *before* calling dns_resolve(), to fix
20095 a bug where cached answers would never be sent in RESOLVED cells.
20096 - When we run out of disk space, or other log writing error, don't
20097 crash. Just stop logging to that log and continue.
20098 - We were starting to daemonize before we opened our logs, so if
20099 there were any problems opening logs, we would complain to stderr,
20100 which wouldn't work, and then mysteriously exit.
20101 - Fix a rare bug where sometimes a verified OR would connect to us
20102 before he'd uploaded his descriptor, which would cause us to
20103 assign conn->nickname as though he's unverified. Now we look through
20104 the fingerprint list to see if he's there.
20105 - Fix a rare assert trigger, where routerinfos for entries in
20106 our cpath would expire while we're building the path.
20109 - Clients can ask dirservers for /dir.z to get a compressed version
20110 of the directory. Only works for servers running 0.0.9, of course.
20111 - Make clients cache directories and use them to seed their router
20112 lists at startup. This means clients have a datadir again.
20113 - Configuration infrastructure support for warning on obsolete
20115 - Respond to content-encoding headers by trying to uncompress as
20117 - Reply with a deflated directory when a client asks for "dir.z".
20118 We could use allow-encodings instead, but allow-encodings isn't
20119 specified in HTTP 1.0.
20120 - Raise the max dns workers from 50 to 100.
20121 - Discourage people from setting their dirfetchpostperiod more often
20122 than once per minute.
20123 - Protect dirservers from overzealous descriptor uploading -- wait
20124 10 seconds after directory gets dirty, before regenerating.
20127 Changes in version 0.0.8 - 2004-08-25
20128 o Port it to SunOS 5.9 / Athena
20131 Changes in version 0.0.8rc2 - 2004-08-20
20132 o Make it compile on cygwin again.
20133 o When picking unverified routers, skip those with low uptime and/or
20134 low bandwidth, depending on what properties you care about.
20137 Changes in version 0.0.8rc1 - 2004-08-18
20138 o Changes from 0.0.7.3:
20140 - Fix assert triggers: if the other side returns an address 0.0.0.0,
20141 don't put it into the client dns cache.
20142 - If a begin failed due to exit policy, but we believe the IP address
20143 should have been allowed, switch that router to exitpolicy reject *:*
20144 until we get our next directory.
20146 - Clients choose nodes proportional to advertised bandwidth.
20147 - Avoid using nodes with low uptime as introduction points.
20148 - Handle servers with dynamic IP addresses: don't replace
20149 options->Address with the resolved one at startup, and
20150 detect our address right before we make a routerinfo each time.
20151 - 'FascistFirewall' option to pick dirservers and ORs on specific
20152 ports; plus 'FirewallPorts' config option to tell FascistFirewall
20153 which ports are open. (Defaults to 80,443)
20154 - Be more aggressive about trying to make circuits when the network
20155 has changed (e.g. when you unsuspend your laptop).
20156 - Check for time skew on http headers; report date in response to
20158 - If the entrynode config line has only one node, don't pick it as
20160 - Add strict{entry|exit}nodes config options. If set to 1, then
20161 we refuse to build circuits that don't include the specified entry
20163 - OutboundBindAddress config option, to bind to a specific
20164 IP address for outgoing connect()s.
20165 - End truncated log entries (e.g. directories) with "[truncated]".
20167 o Patches to 0.0.8preX:
20169 - Patches to compile and run on win32 again (maybe)?
20170 - Fix crash when looking for ~/.torrc with no $HOME set.
20171 - Fix a race bug in the unit tests.
20172 - Handle verified/unverified name collisions better when new
20173 routerinfo's arrive in a directory.
20174 - Sometimes routers were getting entered into the stats before
20175 we'd assigned their identity_digest. Oops.
20176 - Only pick and establish intro points after we've gotten a
20179 - AllowUnverifiedNodes config option to let circuits choose no-name
20180 routers in entry,middle,exit,introduction,rendezvous positions.
20181 Allow middle and rendezvous positions by default.
20182 - Add a man page for tor-resolve.
20185 Changes in version 0.0.7.3 - 2004-08-12
20186 o Stop dnsworkers from triggering an assert failure when you
20187 ask them to resolve the host "".
20190 Changes in version 0.0.8pre3 - 2004-08-09
20191 o Changes from 0.0.7.2:
20192 - Allow multiple ORs with same nickname in routerlist -- now when
20193 people give us one identity key for a nickname, then later
20194 another, we don't constantly complain until the first expires.
20195 - Remember used bandwidth (both in and out), and publish 15-minute
20196 snapshots for the past day into our descriptor.
20197 - You can now fetch $DIRURL/running-routers to get just the
20198 running-routers line, not the whole descriptor list. (But
20199 clients don't use this yet.)
20200 - When people mistakenly use Tor as an http proxy, point them
20201 at the tor-doc.html rather than the INSTALL.
20202 - Remove our mostly unused -- and broken -- hex_encode()
20203 function. Use base16_encode() instead. (Thanks to Timo Lindfors
20204 for pointing out this bug.)
20205 - Rotate onion keys every 12 hours, not every 2 hours, so we have
20206 fewer problems with people using the wrong key.
20207 - Change the default exit policy to reject the default edonkey,
20208 kazaa, gnutella ports.
20209 - Add replace_file() to util.[ch] to handle win32's rename().
20211 o Changes from 0.0.8preX:
20212 - Fix two bugs in saving onion keys to disk when rotating, so
20213 hopefully we'll get fewer people using old onion keys.
20214 - Fix an assert error that was making SocksPolicy not work.
20215 - Be willing to expire routers that have an open dirport -- it's
20216 just the authoritative dirservers we want to not forget.
20217 - Reject tor-resolve requests for .onion addresses early, so we
20218 don't build a whole rendezvous circuit and then fail.
20219 - When you're warning a server that he's unverified, don't cry
20220 wolf unpredictably.
20221 - Fix a race condition: don't try to extend onto a connection
20222 that's still handshaking.
20223 - For servers in clique mode, require the conn to be open before
20224 you'll choose it for your path.
20225 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
20226 end relay cell, etc.
20227 - Measure bandwidth capacity over the last 24 hours, not just 12
20228 - Bugfix: authoritative dirservers were making and signing a new
20229 directory for each client, rather than reusing the cached one.
20232 Changes in version 0.0.8pre2 - 2004-08-04
20233 o Changes from 0.0.7.2:
20235 - Check directory signature _before_ you decide whether you're
20236 you're running an obsolete version and should exit.
20237 - Check directory signature _before_ you parse the running-routers
20238 list to decide who's running or verified.
20239 - Bugfixes and features:
20240 - Check return value of fclose while writing to disk, so we don't
20241 end up with broken files when servers run out of disk space.
20242 - Log a warning if the user uses an unsafe socks variant, so people
20243 are more likely to learn about privoxy or socat.
20244 - Dirservers now include RFC1123-style dates in the HTTP headers,
20245 which one day we will use to better detect clock skew.
20247 o Changes from 0.0.8pre1:
20248 - Make it compile without warnings again on win32.
20249 - Log a warning if you're running an unverified server, to let you
20250 know you might want to get it verified.
20251 - Only pick a default nickname if you plan to be a server.
20254 Changes in version 0.0.8pre1 - 2004-07-23
20256 - Made our unit tests compile again on OpenBSD 3.5, and tor
20257 itself compile again on OpenBSD on a sparc64.
20258 - We were neglecting milliseconds when logging on win32, so
20259 everything appeared to happen at the beginning of each second.
20261 o Protocol changes:
20262 - 'Extend' relay cell payloads now include the digest of the
20263 intended next hop's identity key. Now we can verify that we're
20264 extending to the right router, and also extend to routers we
20265 hadn't heard of before.
20268 - Tor nodes can now act as relays (with an advertised ORPort)
20269 without being manually verified by the dirserver operators.
20270 - Uploaded descriptors of unverified routers are now accepted
20271 by the dirservers, and included in the directory.
20272 - Verified routers are listed by nickname in the running-routers
20273 list; unverified routers are listed as "$<fingerprint>".
20274 - We now use hash-of-identity-key in most places rather than
20275 nickname or addr:port, for improved security/flexibility.
20276 - To avoid Sybil attacks, paths still use only verified servers.
20277 But now we have a chance to play around with hybrid approaches.
20278 - Nodes track bandwidth usage to estimate capacity (not used yet).
20279 - ClientOnly option for nodes that never want to become servers.
20280 - Directory caching.
20281 - "AuthoritativeDir 1" option for the official dirservers.
20282 - Now other nodes (clients and servers) will cache the latest
20283 directory they've pulled down.
20284 - They can enable their DirPort to serve it to others.
20285 - Clients will pull down a directory from any node with an open
20286 DirPort, and check the signature/timestamp correctly.
20287 - Authoritative dirservers now fetch directories from other
20288 authdirservers, to stay better synced.
20289 - Running-routers list tells who's down also, along with noting
20290 if they're verified (listed by nickname) or unverified (listed
20292 - Allow dirservers to serve running-router list separately.
20293 This isn't used yet.
20294 - ORs connect-on-demand to other ORs
20295 - If you get an extend cell to an OR you're not connected to,
20296 connect, handshake, and forward the create cell.
20297 - The authoritative dirservers stay connected to everybody,
20298 and everybody stays connected to 0.0.7 servers, but otherwise
20299 clients/servers expire unused connections after 5 minutes.
20300 - When servers get a sigint, they delay 30 seconds (refusing new
20301 connections) then exit. A second sigint causes immediate exit.
20302 - File and name management:
20303 - Look for .torrc if no CONFDIR "torrc" is found.
20304 - If no datadir is defined, then choose, make, and secure ~/.tor
20306 - If torrc not found, exitpolicy reject *:*.
20307 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
20308 - If no nickname is defined, derive default from hostname.
20309 - Rename secret key files, e.g. identity.key -> secret_id_key,
20310 to discourage people from mailing their identity key to tor-ops.
20311 - Refuse to build a circuit before the directory has arrived --
20312 it won't work anyway, since you won't know the right onion keys
20314 - Try other dirservers immediately if the one you try is down. This
20315 should tolerate down dirservers better now.
20316 - Parse tor version numbers so we can do an is-newer-than check
20317 rather than an is-in-the-list check.
20318 - New socks command 'resolve', to let us shim gethostbyname()
20320 - A 'tor_resolve' script to access the socks resolve functionality.
20321 - A new socks-extensions.txt doc file to describe our
20322 interpretation and extensions to the socks protocols.
20323 - Add a ContactInfo option, which gets published in descriptor.
20324 - Publish OR uptime in descriptor (and thus in directory) too.
20325 - Write tor version at the top of each log file
20326 - New docs in the tarball:
20328 - Document that you should proxy your SSL traffic too.
20331 Changes in version 0.0.7.2 - 2004-07-07
20332 o A better fix for the 0.0.0.0 problem, that will hopefully
20333 eliminate the remaining related assertion failures.
20336 Changes in version 0.0.7.1 - 2004-07-04
20337 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
20338 since internally we use 0.0.0.0 to signify "not yet resolved".
20341 Changes in version 0.0.7 - 2004-06-07
20342 o Updated the man page to reflect the new features.
20345 Changes in version 0.0.7rc2 - 2004-06-06
20346 o Changes from 0.0.7rc1:
20347 - Make it build on Win32 again.
20348 o Changes from 0.0.6.2:
20349 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
20353 Changes in version 0.0.7rc1 - 2004-06-02
20355 - On sighup, we were adding another log without removing the first
20356 one. So log messages would get duplicated n times for n sighups.
20357 - Several cases of using a connection after we'd freed it. The
20358 problem was that connections that are pending resolve are in both
20359 the pending_resolve tree, and also the circuit's resolving_streams
20360 list. When you want to remove one, you must remove it from both.
20361 - Fix a double-mark-for-close where an end cell arrived for a
20362 resolving stream, and then the resolve failed.
20363 - Check directory signatures based on name of signer, not on whom
20364 we got the directory from. This will let us cache directories more
20367 - Crank up some of our constants to handle more users.
20370 Changes in version 0.0.7pre1 - 2004-06-02
20371 o Fixes for crashes and other obnoxious bugs:
20372 - Fix an epipe bug: sometimes when directory connections failed
20373 to connect, we would give them a chance to flush before closing
20375 - When we detached from a circuit because of resolvefailed, we
20376 would immediately try the same circuit twice more, and then
20377 give up on the resolve thinking we'd tried three different
20379 - Limit the number of intro circuits we'll attempt to build for a
20380 hidden service per 15-minute period.
20381 - Check recommended-software string *early*, before actually parsing
20382 the directory. Thus we can detect an obsolete version and exit,
20383 even if the new directory format doesn't parse.
20384 o Fixes for security bugs:
20385 - Remember which nodes are dirservers when you startup, and if a
20386 random OR enables his dirport, don't automatically assume he's
20387 a trusted dirserver.
20389 - Directory connections were asking the wrong poll socket to
20390 start writing, and not asking themselves to start writing.
20391 - When we detached from a circuit because we sent a begin but
20392 didn't get a connected, we would use it again the first time;
20393 but after that we would correctly switch to a different one.
20394 - Stop warning when the first onion decrypt attempt fails; they
20395 will sometimes legitimately fail now that we rotate keys.
20396 - Override unaligned-access-ok check when $host_cpu is ia64 or
20397 arm. Apparently they allow it but the kernel whines.
20398 - Dirservers try to reconnect periodically too, in case connections
20400 - Fix some memory leaks in directory servers.
20401 - Allow backslash in Win32 filenames.
20402 - Made Tor build complain-free on FreeBSD, hopefully without
20403 breaking other BSD builds. We'll see.
20405 - Doxygen markup on all functions and global variables.
20406 - Make directory functions update routerlist, not replace it. So
20407 now directory disagreements are not so critical a problem.
20408 - Remove the upper limit on number of descriptors in a dirserver's
20409 directory (not that we were anywhere close).
20410 - Allow multiple logfiles at different severity ranges.
20411 - Allow *BindAddress to specify ":port" rather than setting *Port
20412 separately. Allow multiple instances of each BindAddress config
20413 option, so you can bind to multiple interfaces if you want.
20414 - Allow multiple exit policy lines, which are processed in order.
20415 Now we don't need that huge line with all the commas in it.
20416 - Enable accept/reject policies on SOCKS connections, so you can bind
20417 to 0.0.0.0 but still control who can use your OP.
20420 Changes in version 0.0.6.2 - 2004-05-16
20421 o Our integrity-checking digest was checking only the most recent cell,
20422 not the previous cells like we'd thought.
20423 Thanks to Stefan Mark for finding the flaw!
20426 Changes in version 0.0.6.1 - 2004-05-06
20427 o Fix two bugs in our AES counter-mode implementation (this affected
20428 onion-level stream encryption, but not TLS-level). It turns
20429 out we were doing something much more akin to a 16-character
20430 polyalphabetic cipher. Oops.
20431 Thanks to Stefan Mark for finding the flaw!
20432 o Retire moria3 as a directory server, and add tor26 as a directory
20436 Changes in version 0.0.6 - 2004-05-02
20437 [version bump only]
20440 Changes in version 0.0.6rc4 - 2004-05-01
20441 o Update the built-in dirservers list to use the new directory format
20442 o Fix a rare seg fault: if a node offering a hidden service attempts
20443 to build a circuit to Alice's rendezvous point and fails before it
20444 reaches the last hop, it retries with a different circuit, but
20446 o Handle windows socket errors correctly.
20449 Changes in version 0.0.6rc3 - 2004-04-28
20450 o Don't expire non-general excess circuits (if we had enough
20451 circuits open, we were expiring rendezvous circuits -- even
20452 when they had a stream attached. oops.)
20453 o Fetch randomness from /dev/urandom better (not via fopen/fread)
20454 o Better debugging for tls errors
20455 o Some versions of openssl have an SSL_pending function that erroneously
20456 returns bytes when there is a non-application record pending.
20457 o Set Content-Type on the directory and hidserv descriptor.
20458 o Remove IVs from cipher code, since AES-ctr has none.
20459 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
20460 o We were using an array of length zero in a few places.
20461 o win32's gethostbyname can't resolve an IP to an IP.
20462 o win32's close can't close a socket.
20465 Changes in version 0.0.6rc2 - 2004-04-26
20466 o Fix a bug where we were closing tls connections intermittently.
20467 It turns out openssl keeps its errors around -- so if an error
20468 happens, and you don't ask about it, and then another openssl
20469 operation happens and succeeds, and you ask if there was an error,
20470 it tells you about the first error. Fun fun.
20471 o Fix a bug that's been lurking since 27 may 03 (!)
20472 When passing back a destroy cell, we would use the wrong circ id.
20473 'Mostly harmless', but still worth fixing.
20474 o Since we don't support truncateds much, don't bother sending them;
20475 just close the circ.
20476 o check for <machine/limits.h> so we build on NetBSD again (I hope).
20477 o don't crash if a conn that sent a begin has suddenly lost its circuit
20478 (this was quite rare).
20481 Changes in version 0.0.6rc1 - 2004-04-25
20482 o We now rotate link (tls context) keys and onion keys.
20483 o CREATE cells now include oaep padding, so you can tell
20484 if you decrypted them correctly.
20485 o Add bandwidthburst to server descriptor.
20486 o Directories now say which dirserver signed them.
20487 o Use a tor_assert macro that logs failed assertions too.
20490 Changes in version 0.0.6pre5 - 2004-04-18
20491 o changes from 0.0.6pre4:
20492 - make tor build on broken freebsd 5.2 installs
20493 - fix a failed assert when you try an intro point, get a nack, and try
20494 a second one and it works.
20495 - when alice uses a port that the hidden service doesn't accept,
20496 it now sends back an end cell (denied by exit policy). otherwise
20497 alice would just have to wait to time out.
20498 - fix another rare bug: when we had tried all the intro
20499 points for a hidden service, we fetched the descriptor
20500 again, but we left our introcirc thinking it had already
20501 sent an intro, so it kept waiting for a response...
20502 - bugfix: when you sleep your hidden-service laptop, as soon
20503 as it wakes up it tries to upload a service descriptor, but
20504 socketpair fails for some reason (localhost not up yet?).
20505 now we simply give up on that upload, and we'll try again later.
20506 i'd still like to find the bug though.
20507 - if an intro circ waiting for an ack dies before getting one, then
20509 - we were reusing stale service descriptors and refetching usable
20513 Changes in version 0.0.6pre4 - 2004-04-14
20514 o changes from 0.0.6pre3:
20515 - when bob fails to connect to the rendezvous point, and his
20516 circ didn't fail because of the rendezvous point itself, then
20517 he retries a couple of times
20518 - we expire introduction and rendezvous circs more thoroughly
20519 (sometimes they were hanging around forever)
20520 - we expire unattached rendezvous streams that have been around
20521 too long (they were sticking around forever).
20522 - fix a measly fencepost error that was crashing everybody with
20526 Changes in version 0.0.6pre3 - 2004-04-14
20527 o changes from 0.0.6pre2:
20528 - make hup work again
20529 - fix some memory leaks for dirservers
20530 - allow more skew in rendezvous descriptor timestamps, to help
20531 handle people like blanu who don't know what time it is
20532 - normal circs are 3 hops, but some rend/intro circs are 4, if
20533 the initiator doesn't get to choose the last hop
20534 - send acks for introductions, so alice can know whether to try
20536 - bob publishes intro points more correctly
20537 o changes from 0.0.5:
20538 - fix an assert trigger that's been plaguing us since the days
20539 of 0.0.2prexx (thanks weasel!)
20540 - retry stream correctly when we fail to connect because of
20541 exit-policy-reject (should try another) or can't-resolve-address
20542 (also should try another, because dns on random internet servers
20544 - when we hup a dirserver and we've *removed* a server from the
20545 approved-routers list, now we remove that server from the
20546 in-memory directories too
20549 Changes in version 0.0.6pre2 - 2004-04-08
20550 o We fixed our base32 implementation. Now it works on all architectures.
20553 Changes in version 0.0.6pre1 - 2004-04-08
20555 - Hidden services and rendezvous points are implemented. Go to
20556 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
20557 hidden services. (This only works via a socks4a proxy such as
20558 Privoxy, and currently it's quite slow.)
20561 Changes in version 0.0.5 - 2004-03-30
20562 [version bump only]
20565 Changes in version 0.0.5rc3 - 2004-03-29
20566 o Install torrc as torrc.sample -- we no longer clobber your
20568 o Re-enable recommendedversion checking (we broke it in rc2, oops)
20569 o Add in a 'notice' log level for things the operator should hear
20570 but that aren't warnings
20573 Changes in version 0.0.5rc2 - 2004-03-29
20574 o Hold socks connection open until reply is flushed (if possible)
20575 o Make exit nodes resolve IPs to IPs immediately, rather than asking
20576 the dns farm to do it.
20577 o Fix c99 aliasing warnings in rephist.c
20578 o Don't include server descriptors that are older than 24 hours in the
20580 o Give socks 'reject' replies their whole 15s to attempt to flush,
20581 rather than seeing the 60s timeout and assuming the flush had failed.
20582 o Clean automake droppings from the cvs repository
20585 Changes in version 0.0.5rc1 - 2004-03-28
20586 o Fix mangled-state bug in directory fetching (was causing sigpipes).
20587 o Only build circuits after we've fetched the directory: clients were
20588 using only the directory servers before they'd fetched a directory.
20589 This also means longer startup time; so it goes.
20590 o Fix an assert trigger where an OP would fail to handshake, and we'd
20591 expect it to have a nickname.
20592 o Work around a tsocks bug: do a socks reject when AP connection dies
20593 early, else tsocks goes into an infinite loop.
20596 Changes in version 0.0.4 - 2004-03-26
20597 o When connecting to a dirserver or OR and the network is down,
20601 Changes in version 0.0.3 - 2004-03-26
20602 o Warn and fail if server chose a nickname with illegal characters
20603 o Port to Solaris and Sparc:
20604 - include missing header fcntl.h
20605 - have autoconf find -lsocket -lnsl automatically
20606 - deal with hardware word alignment
20607 - make uname() work (solaris has a different return convention)
20608 - switch from using signal() to sigaction()
20609 o Preliminary work on reputation system:
20610 - Keep statistics on success/fail of connect attempts; they're published
20611 by kill -USR1 currently.
20612 - Add a RunTesting option to try to learn link state by creating test
20613 circuits, even when SocksPort is off.
20614 - Remove unused open circuits when there are too many.
20617 Changes in version 0.0.2 - 2004-03-19
20618 - Include strlcpy and strlcat for safer string ops
20619 - define INADDR_NONE so we compile (but still not run) on solaris
20622 Changes in version 0.0.2pre27 - 2004-03-14
20624 - Allow internal tor networks (we were rejecting internal IPs,
20625 now we allow them if they're set explicitly).
20626 - And fix a few endian issues.
20629 Changes in version 0.0.2pre26 - 2004-03-14
20631 - If a stream times out after 15s without a connected cell, don't
20632 try that circuit again: try a new one.
20633 - Retry streams at most 4 times. Then give up.
20634 - When a dirserver gets a descriptor from an unknown router, it
20635 logs its fingerprint (so the dirserver operator can choose to
20636 accept it even without mail from the server operator).
20637 - Inform unapproved servers when we reject their descriptors.
20638 - Make tor build on Windows again. It works as a client, who knows
20640 - Clearer instructions in the torrc for how to set up a server.
20641 - Be more efficient about reading fd's when our global token bucket
20642 (used for rate limiting) becomes empty.
20644 - Stop asserting that computers always go forward in time. It's
20646 - When we sent a cell (e.g. destroy) and then marked an OR connection
20647 expired, we might close it before finishing a flush if the other
20648 side isn't reading right then.
20649 - Don't allow dirservers to start if they haven't defined
20650 RecommendedVersions
20651 - We were caching transient dns failures. Oops.
20652 - Prevent servers from publishing an internal IP as their address.
20653 - Address a strcat vulnerability in circuit.c
20656 Changes in version 0.0.2pre25 - 2004-03-04
20658 - Put the OR's IP in its router descriptor, not its fqdn. That way
20659 we'll stop being stalled by gethostbyname for nodes with flaky dns,
20662 - If the user typed in an address that didn't resolve, the server
20666 Changes in version 0.0.2pre24 - 2004-03-03
20668 - Fix an assertion failure in dns.c, where we were trying to dequeue
20669 a pending dns resolve even if it wasn't pending
20670 - Fix a spurious socks5 warning about still trying to write after the
20671 connection is finished.
20672 - Hold certain marked_for_close connections open until they're finished
20673 flushing, rather than losing bytes by closing them too early.
20674 - Correctly report the reason for ending a stream
20675 - Remove some duplicate calls to connection_mark_for_close
20676 - Put switch_id and start_daemon earlier in the boot sequence, so it
20677 will actually try to chdir() to options.DataDirectory
20678 - Make 'make test' exit(1) if a test fails; fix some unit tests
20679 - Make tor fail when you use a config option it doesn't know about,
20680 rather than warn and continue.
20681 - Make --version work
20682 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
20685 Changes in version 0.0.2pre23 - 2004-02-29
20687 - Print a statement when the first circ is finished, so the user
20688 knows it's working.
20689 - If a relay cell is unrecognized at the end of the circuit,
20690 send back a destroy. (So attacks to mutate cells are more
20692 - New config option 'excludenodes' to avoid certain nodes for circuits.
20693 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
20694 so you can collect coredumps there.
20696 - Fix a bug in tls flushing where sometimes data got wedged and
20697 didn't flush until more data got sent. Hopefully this bug was
20698 a big factor in the random delays we were seeing.
20699 - Make 'connected' cells include the resolved IP, so the client
20700 dns cache actually gets populated.
20701 - Disallow changing from ORPort=0 to ORPort>0 on hup.
20702 - When we time-out on a stream and detach from the circuit, send an
20703 end cell down it first.
20704 - Only warn about an unknown router (in exitnodes, entrynodes,
20705 excludenodes) after we've fetched a directory.
20708 Changes in version 0.0.2pre22 - 2004-02-26
20710 - Servers publish less revealing uname information in descriptors.
20711 - More memory tracking and assertions, to crash more usefully when
20713 - If the default torrc isn't there, just use some default defaults.
20714 Plus provide an internal dirservers file if they don't have one.
20715 - When the user tries to use Tor as an http proxy, give them an http
20716 501 failure explaining that we're a socks proxy.
20717 - Dump a new router.desc on hup, to help confused people who change
20718 their exit policies and then wonder why router.desc doesn't reflect
20720 - Clean up the generic tor.sh init script that we ship with.
20722 - If the exit stream is pending on the resolve, and a destroy arrives,
20723 then the stream wasn't getting removed from the pending list. I
20724 think this was the one causing recent server crashes.
20725 - Use a more robust poll on OSX 10.3, since their poll is flaky.
20726 - When it couldn't resolve any dirservers, it was useless from then on.
20727 Now it reloads the RouterFile (or default dirservers) if it has no
20729 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
20730 many users don't even *have* a /usr/local/sbin/.
20733 Changes in version 0.0.2pre21 - 2004-02-18
20735 - There's a ChangeLog file that actually reflects the changelog.
20736 - There's a 'torify' wrapper script, with an accompanying
20737 tor-tsocks.conf, that simplifies the process of using tsocks for
20738 tor. It even has a man page.
20739 - The tor binary gets installed to sbin rather than bin now.
20740 - Retry streams where the connected cell hasn't arrived in 15 seconds
20741 - Clean up exit policy handling -- get the default out of the torrc,
20742 so we can update it without forcing each server operator to fix
20744 - Allow imaps and pop3s in default exit policy
20746 - Prevent picking middleman nodes as the last node in the circuit
20749 Changes in version 0.0.2pre20 - 2004-01-30
20751 - We now have a deb package, and it's in debian unstable. Go to
20752 it, apt-getters. :)
20753 - I've split the TotalBandwidth option into BandwidthRate (how many
20754 bytes per second you want to allow, long-term) and
20755 BandwidthBurst (how many bytes you will allow at once before the cap
20756 kicks in). This better token bucket approach lets you, say, set
20757 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
20758 performance while not exceeding your monthly bandwidth quota.
20759 - Push out a tls record's worth of data once you've got it, rather
20760 than waiting until you've read everything waiting to be read. This
20761 may improve performance by pipelining better. We'll see.
20762 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
20763 from failed circuits (if they haven't been connected yet) and attach
20765 - Expire old streams that haven't managed to connect. Some day we'll
20766 have them reattach to new circuits instead.
20769 - Fix several memory leaks that were causing servers to become bloated
20771 - Fix a few very rare assert triggers. A few more remain.
20772 - Setuid to User _before_ complaining about running as root.
20775 Changes in version 0.0.2pre19 - 2004-01-07
20777 - Fix deadlock condition in dns farm. We were telling a child to die by
20778 closing the parent's file descriptor to him. But newer children were
20779 inheriting the open file descriptor from the parent, and since they
20780 weren't closing it, the socket never closed, so the child never read
20781 eof, so he never knew to exit. Similarly, dns workers were holding
20782 open other sockets, leading to all sorts of chaos.
20783 - New cleaner daemon() code for forking and backgrounding.
20784 - If you log to a file, it now prints an entry at the top of the
20785 logfile so you know it's working.
20786 - The onionskin challenge length was 30 bytes longer than necessary.
20787 - Started to patch up the spec so it's not quite so out of date.
20790 Changes in version 0.0.2pre18 - 2004-01-02
20792 - Fix endian issues with the 'integrity' field in the relay header.
20793 - Fix a potential bug where connections in state
20794 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
20797 Changes in version 0.0.2pre17 - 2003-12-30
20799 - Made --debuglogfile (or any second log file, actually) work.
20800 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
20801 adversary could force us into an infinite loop.
20804 - Each onionskin handshake now includes a hash of the computed key,
20805 to prove the server's identity and help perfect forward secrecy.
20806 - Changed cell size from 256 to 512 bytes (working toward compatibility
20808 - Changed cell length to 2 bytes, and moved it to the relay header.
20809 - Implemented end-to-end integrity checking for the payloads of
20811 - Separated streamid from 'recognized' (otherwise circuits will get
20812 messed up when we try to have streams exit from the middle). We
20813 use the integrity-checking to confirm that a cell is addressed to
20815 - Randomize the initial circid and streamid values, so an adversary who
20816 breaks into a node can't learn how many circuits or streams have
20820 Changes in version 0.0.2pre16 - 2003-12-14
20822 - Fixed a bug that made HUP trigger an assert
20823 - Fixed a bug where a circuit that immediately failed wasn't being
20824 counted as a failed circuit in counting retries.
20827 - Now we close the circuit when we get a truncated cell: otherwise we're
20828 open to an anonymity attack where a bad node in the path truncates
20829 the circuit and then we open streams at him.
20830 - Add port ranges to exit policies
20831 - Add a conservative default exit policy
20832 - Warn if you're running tor as root
20833 - on HUP, retry OR connections and close/rebind listeners
20834 - options.EntryNodes: try these nodes first when picking the first node
20835 - options.ExitNodes: if your best choices happen to include any of
20836 your preferred exit nodes, you choose among just those preferred
20838 - options.ExcludedNodes: nodes that are never picked in path building
20841 Changes in version 0.0.2pre15 - 2003-12-03
20842 o Robustness and bugfixes:
20843 - Sometimes clients would cache incorrect DNS resolves, which would
20844 really screw things up.
20845 - An OP that goes offline would slowly leak all its sockets and stop
20847 - A wide variety of bugfixes in exit node selection, exit policy
20848 handling, and processing pending streams when a new circuit is
20850 - Pick nodes for a path only from those the directory says are up
20851 - Choose randomly from all running dirservers, not always the first one
20852 - Increase allowed http header size for directory fetch.
20853 - Stop writing to stderr (if we're daemonized it will be closed).
20854 - Enable -g always, so cores will be more useful to me.
20855 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
20858 - Wrote a man page. It lists commonly used options.
20861 - Change default loglevel to warn.
20862 - Make PidFile default to null rather than littering in your CWD.
20863 - OnionRouter config option is now obsolete. Instead it just checks
20865 - Moved to a single unified torrc file for both clients and servers.
20868 Changes in version 0.0.2pre14 - 2003-11-29
20869 o Robustness and bugfixes:
20870 - Force the admin to make the DataDirectory himself
20871 - to get ownership/permissions right
20872 - so clients no longer make a DataDirectory and then never use it
20873 - fix bug where a client who was offline for 45 minutes would never
20874 pull down a directory again
20875 - fix (or at least hide really well) the dns assert bug that was
20876 causing server crashes
20877 - warnings and improved robustness wrt clockskew for certs
20878 - use the native daemon(3) to daemonize, when available
20879 - exit if bind() fails
20880 - exit if neither socksport nor orport is defined
20881 - include our own tor_timegm (Win32 doesn't have its own)
20882 - bugfix for win32 with lots of connections
20883 - fix minor bias in PRNG
20884 - make dirserver more robust to corrupt cached directory
20887 - Wrote the design document (woo)
20889 o Circuit building and exit policies:
20890 - Circuits no longer try to use nodes that the directory has told them
20892 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
20893 bitcounts (18.0.0.0/8).
20894 - Make AP connections standby for a circuit if no suitable circuit
20895 exists, rather than failing
20896 - Circuits choose exit node based on addr/port, exit policies, and
20897 which AP connections are standing by
20898 - Bump min pathlen from 2 to 3
20899 - Relay end cells have a payload to describe why the stream ended.
20900 - If the stream failed because of exit policy, try again with a new
20902 - Clients have a dns cache to remember resolved addresses.
20903 - Notice more quickly when we have no working circuits
20906 - APPort is now called SocksPort
20907 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
20909 - RecommendedVersions is now a config variable rather than
20910 hardcoded (for dirservers)
20911 - Reloads config on HUP
20912 - Usage info on -h or --help
20913 - If you set User and Group config vars, it'll setu/gid to them.
20916 Changes in version 0.0.2pre13 - 2003-10-19
20917 o General stability:
20918 - SSL_write no longer fails when it returns WANTWRITE and the number
20919 of bytes in the buf has changed by the next SSL_write call.
20920 - Fix segfault fetching directory when network is down
20921 - Fix a variety of minor memory leaks
20922 - Dirservers reload the fingerprints file on HUP, so I don't have
20923 to take down the network when I approve a new router
20924 - Default server config file has explicit Address line to specify fqdn
20927 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
20928 - Make listener connections not ever alloc bufs
20930 o Autoconf improvements:
20931 - don't clobber an external CFLAGS in ./configure
20932 - Make install now works
20933 - create var/lib/tor on make install
20934 - autocreate a tor.sh initscript to help distribs
20935 - autocreate the torrc and sample-server-torrc with correct paths
20937 o Log files and Daemonizing now work:
20938 - If --DebugLogFile is specified, log to it at -l debug
20939 - If --LogFile is specified, use it instead of commandline
20940 - If --RunAsDaemon is set, tor forks and backgrounds on startup