1 Changes in version 0.2.1.1-alpha - 2008-??-??
3 - Downgrade assert in connection_buckets_decrement() to a log message.
4 This may help us solve bug 614, and in any case will make its symptoms
5 less severe. Bugfix on 0.2.0.20-rc.
6 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
7 OpenSSL versions should have been working fine. Diagnosis and patch
8 from lodger, Karsten Loesing and Sebastian Hahn. Fixes bug 616.
10 - Generate "STATUS_SERVER" events rather than misspelled "STATUS_SEVER"
11 events. Caught by mwenge; bugfix on 0.1.2.x.
12 - Fix the SVK version detection logic to work correctly on a branch.
14 - Make sure servers always request certificates from clients during
15 TLS renegotiation. Bugfix on 0.2.0.x.
16 - When counting the number of bytes written on a TLS connection, look at
17 the BIO actually used for writing to the network, not at the BIO used
18 (sometimes) to buffer data for the network. Looking at different BIOs
19 could result in write counts on the order of ULONG_MAX. Fix for bug
20 614. Bugfix on 0.1.2.x.
23 - Allow separate log levels to be configured for different logging
24 domains. For example, this allows one to log all notices, warnings, or
25 errors, plus all memory management messages of level debug or higher,
26 with: Log [MM] debug-err [*] notice-err file /var/log/tor.
29 Changes in version 0.2.0.21-rc - 2008-03-02
31 - The control port should declare that it requires password auth
32 when HashedControlSessionPassword is set too. Patch from Matt Edman;
33 bugfix on 0.2.0.20-rc. Fixes bug 615.
34 - Downgrade assert in connection_buckets_decrement() to a log message.
35 This may help us solve bug 614, and in any case will make its
36 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
37 - We were sometimes miscounting the number of bytes read from the
38 network, causing our rate limiting to not be followed exactly.
39 Bugfix on 0.2.0.16-alpha. Reported by lodger.
42 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
43 OpenSSL versions should have been working fine. Diagnosis and patch
44 from lodger, Karsten Loesing and Sebastian Hahn. Fixes bug 616.
45 Bugfix on 0.2.0.20-rc.
48 Changes in version 0.2.0.20-rc - 2008-02-24
49 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
50 makes more progress towards normalizing Tor's TLS handshake, makes
51 hidden services work better again, helps relays bootstrap if they don't
52 know their IP address, adds optional support for linking in openbsd's
53 allocator or tcmalloc, allows really fast relays to scale past 15000
54 sockets, and fixes a bunch of minor bugs reported by Veracode.
57 - Enable the revised TLS handshake based on the one designed by
58 Steven Murdoch in proposal 124, as revised in proposal 130. It
59 includes version negotiation for OR connections as described in
60 proposal 105. The new handshake is meant to be harder for censors
61 to fingerprint, and it adds the ability to detect certain kinds of
62 man-in-the-middle traffic analysis attacks. The version negotiation
63 feature will allow us to improve Tor's link protocol more safely
65 - Choose which bridge to use proportional to its advertised bandwidth,
66 rather than uniformly at random. This should speed up Tor for
67 bridge users. Also do this for people who set StrictEntryNodes.
68 - When a TrackHostExits-chosen exit fails too many times in a row,
69 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
72 - Resolved problems with (re-)fetching hidden service descriptors.
73 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
75 - If we only ever used Tor for hidden service lookups or posts, we
76 would stop building circuits and start refusing connections after
77 24 hours, since we falsely believed that Tor was dormant. Reported
78 by nwf; bugfix on 0.1.2.x.
79 - Servers that don't know their own IP address should go to the
80 authorities for their first directory fetch, even if their DirPort
81 is off or if they don't know they're reachable yet. This will help
82 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
83 - When counting the number of open sockets, count not only the number
84 of sockets we have received from the socket() call, but also
85 the number we've gotten from accept() and socketpair(). This bug
86 made us fail to count all sockets that we were using for incoming
87 connections. Bugfix on 0.2.0.x.
88 - Fix code used to find strings within buffers, when those strings
89 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
90 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
91 - Add a new __HashedControlSessionPassword option for controllers
92 to use for one-off session password hashes that shouldn't get
93 saved to disk by SAVECONF --- Vidalia users were accumulating a
94 pile of HashedControlPassword lines in their torrc files, one for
95 each time they had restarted Tor and then clicked Save. Make Tor
96 automatically convert "HashedControlPassword" to this new option but
97 only when it's given on the command line. Partial fix for bug 586.
99 o Minor features (performance):
100 - Tune parameters for cell pool allocation to minimize amount of
102 - Add OpenBSD malloc code from phk as an optional malloc
103 replacement on Linux: some glibc libraries do very poorly
104 with Tor's memory allocation patterns. Pass
105 --enable-openbsd-malloc to get the replacement malloc code.
106 - Add a --with-tcmalloc option to the configure script to link
107 against tcmalloc (if present). Does not yet search for
108 non-system include paths.
109 - Stop imposing an arbitrary maximum on the number of file descriptors
110 used for busy servers. Bug reported by Olaf Selke; patch from
113 o Minor features (other):
114 - When SafeLogging is disabled, log addresses along with all TLS
116 - When building with --enable-gcc-warnings, check for whether Apple's
117 warning "-Wshorten-64-to-32" is available.
118 - Add a --passphrase-fd argument to the tor-gencert command for
121 o Minor bugfixes (memory leaks and code problems):
122 - We were leaking a file descriptor if Tor started with a zero-length
123 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
124 - Detect size overflow in zlib code. Reported by Justin Ferguson and
126 - We were comparing the raw BridgePassword entry with a base64'ed
127 version of it, when handling a "/tor/networkstatus-bridges"
128 directory request. Now compare correctly. Noticed by Veracode.
129 - Recover from bad tracked-since value in MTBF-history file.
131 - Alter the code that tries to recover from unhandled write
132 errors, to not try to flush onto a socket that's given us
133 unhandled errors. Bugfix on 0.1.2.x.
134 - Make Unix controlsockets work correctly on OpenBSD. Patch from
135 tup. Bugfix on 0.2.0.3-alpha.
137 o Minor bugfixes (other):
138 - If we have an extra-info document for our server, always make
139 it available on the control port, even if we haven't gotten
140 a copy of it from an authority yet. Patch from mwenge.
141 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
142 - Directory mirrors no longer include a guess at the client's IP
143 address if the connection appears to be coming from the same /24
144 network; it was producing too many wrong guesses.
145 - Make the new hidden service code respect the SafeLogging setting.
146 Bugfix on 0.2.0.x. Patch from Karsten.
147 - When starting as an authority, do not overwrite all certificates
148 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
149 - If we're trying to flush the last bytes on a connection (for
150 example, when answering a directory request), reset the
151 time-to-give-up timeout every time we manage to write something
152 on the socket. Bugfix on 0.1.2.x.
153 - Change the behavior of "getinfo status/good-server-descriptor"
154 so it doesn't return failure when any authority disappears.
155 - Even though the man page said that "TrackHostExits ." should
156 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
157 - Report TLS "zero return" case as a "clean close" and "IO error"
158 as a "close". Stop calling closes "unexpected closes": existing
159 Tors don't use SSL_close(), so having a connection close without
160 the TLS shutdown handshake is hardly unexpected.
161 - Send NAMESERVER_STATUS messages for a single failed nameserver
164 o Code simplifications and refactoring:
165 - Remove the tor_strpartition function: its logic was confused,
166 and it was only used for one thing that could be implemented far
170 Changes in version 0.2.0.19-alpha - 2008-02-09
171 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
172 handshake, makes path selection for relays more secure and IP address
173 guessing more robust, and generally fixes a lot of bugs in preparation
174 for calling the 0.2.0 branch stable.
177 - Do not include recognizeable strings in the commonname part of
178 Tor's x509 certificates.
181 - If we're a relay, avoid picking ourselves as an introduction point,
182 a rendezvous point, or as the final hop for internal circuits. Bug
183 reported by taranis and lodger. Bugfix on 0.1.2.x.
184 - Patch from "Andrew S. Lists" to catch when we contact a directory
185 mirror at IP address X and he says we look like we're coming from
186 IP address X. Bugfix on 0.1.2.x.
188 o Minor features (security):
189 - Be more paranoid about overwriting sensitive memory on free(),
190 as a defensive programming tactic to ensure forward secrecy.
192 o Minor features (directory authority):
193 - Actually validate the options passed to AuthDirReject,
194 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
195 - Reject router descriptors with out-of-range bandwidthcapacity or
196 bandwidthburst values.
198 o Minor features (controller):
199 - Reject controller commands over 1MB in length. This keeps rogue
200 processes from running us out of memory.
202 o Minor features (misc):
203 - Give more descriptive well-formedness errors for out-of-range
204 hidden service descriptor/protocol versions.
205 - Make memory debugging information describe more about history
206 of cell allocation, so we can help reduce our memory use.
208 o Deprecated features (controller):
209 - The status/version/num-versioning and status/version/num-concurring
210 GETINFO options are no longer useful in the v3 directory protocol:
211 treat them as deprecated, and warn when they're used.
214 - When our consensus networkstatus has been expired for a while, stop
215 being willing to build circuits using it. Fixes bug 401. Bugfix
217 - Directory caches now fetch certificates from all authorities
218 listed in a networkstatus consensus, even when they do not
219 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
220 - When connecting to a bridge without specifying its key, insert
221 the connection into the identity-to-connection map as soon as
222 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
223 - Detect versions of OS X where malloc_good_size() is present in the
224 library but never actually declared. Resolves bug 587. Bugfix
226 - Stop incorrectly truncating zlib responses to directory authority
227 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
228 - Stop recommending that every server operator send mail to tor-ops.
229 Resolves bug 597. Bugfix on 0.1.2.x.
230 - Don't trigger an assert if we start a directory authority with a
231 private IP address (like 127.0.0.1).
232 - Avoid possible failures when generating a directory with routers
233 with over-long versions strings, or too many flags set. Bugfix
235 - If an attempt to launch a DNS resolve request over the control
236 port fails because we have overrun the limit on the number of
237 connections, tell the controller that the request has failed.
238 - Avoid using too little bandwidth when our clock skips a few
239 seconds. Bugfix on 0.1.2.x.
240 - Fix shell error when warning about missing packages in configure
241 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
242 - Do not become confused when receiving a spurious VERSIONS-like
243 cell from a confused v1 client. Bugfix on 0.2.0.x.
244 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
245 introduction points for a hidden service have failed. Patch from
246 Karsten Loesing. Bugfix on 0.2.0.x.
248 o Code simplifications and refactoring:
249 - Remove some needless generality from cpuworker code, for improved
251 - Stop overloading the circuit_t.onionskin field for both "onionskin
252 from a CREATE cell that we are waiting for a cpuworker to be
253 assigned" and "onionskin from an EXTEND cell that we are going to
254 send to an OR as soon as we are connected". Might help with bug 600.
255 - Add an in-place version of aes_crypt() so that we can avoid doing a
256 needless memcpy() call on each cell payload.
259 Changes in version 0.2.0.18-alpha - 2008-01-25
260 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
261 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
262 that can warn or reject connections to ports generally associated with
263 vulnerable-plaintext protocols.
265 o New directory authorities:
266 - Set up dannenberg (run by CCC) as the sixth v3 directory
270 - Fix a major memory leak when attempting to use the v2 TLS
271 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
272 - We accidentally enabled the under-development v2 TLS handshake
273 code, which was causing log entries like "TLS error while
274 renegotiating handshake". Disable it again. Resolves bug 590.
275 - We were computing the wrong Content-Length: header for directory
276 responses that need to be compressed on the fly, causing clients
277 asking for those items to always fail. Bugfix on 0.2.0.x; partially
281 - Avoid going directly to the directory authorities even if you're a
282 relay, if you haven't found yourself reachable yet or if you've
283 decided not to advertise your dirport yet. Addresses bug 556.
284 - If we've gone 12 hours since our last bandwidth check, and we
285 estimate we have less than 50KB bandwidth capacity but we could
286 handle more, do another bandwidth test.
287 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
288 Tor can warn and/or refuse connections to ports commonly used with
289 vulnerable-plaintext protocols. Currently we warn on ports 23,
290 109, 110, and 143, but we don't reject any.
293 - When we setconf ClientOnly to 1, close any current OR and Dir
294 listeners. Reported by mwenge.
295 - When we get a consensus that's been signed by more people than
296 we expect, don't log about it; it's not a big deal. Reported
300 - Don't answer "/tor/networkstatus-bridges" directory requests if
301 the request isn't encrypted.
302 - Make "ClientOnly 1" config option disable directory ports too.
303 - Patches from Karsten Loesing to make v2 hidden services more
304 robust: work even when there aren't enough HSDir relays available;
305 retry when a v2 rend desc fetch fails; but don't retry if we
306 already have a usable v0 rend desc.
309 Changes in version 0.2.0.17-alpha - 2008-01-17
310 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
313 - Make the tor-gencert man page get included correctly in the tarball.
316 Changes in version 0.2.0.16-alpha - 2008-01-17
317 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
318 Loesing, and generally cleans up a lot of features and minor bugs.
320 o New directory authorities:
321 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
324 o Major performance improvements:
325 - Switch our old ring buffer implementation for one more like that
326 used by free Unix kernels. The wasted space in a buffer with 1mb
327 of data will now be more like 8k than 1mb. The new implementation
328 also avoids realloc();realloc(); patterns that can contribute to
329 memory fragmentation.
332 - Configuration files now accept C-style strings as values. This
333 helps encode characters not allowed in the current configuration
334 file format, such as newline or #. Addresses bug 557.
335 - Although we fixed bug 539 (where servers would send HTTP status 503
336 responses _and_ send a body too), there are still servers out
337 there that haven't upgraded. Therefore, make clients parse such
338 bodies when they receive them.
339 - When we're not serving v2 directory information, there is no reason
340 to actually keep any around. Remove the obsolete files and directory
341 on startup if they are very old and we aren't going to serve them.
343 o Minor performance improvements:
344 - Reference-count and share copies of address policy entries; only 5%
345 of them were actually distinct.
346 - Never walk through the list of logs if we know that no log is
347 interested in a given message.
350 - When an authority has not signed a consensus, do not try to
351 download a nonexistent "certificate with key 00000000". Bugfix
352 on 0.2.0.x. Fixes bug 569.
353 - Fix a rare assert error when we're closing one of our threads:
354 use a mutex to protect the list of logs, so we never write to the
355 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
356 bug 575, which is kind of the revenge of bug 222.
357 - Patch from Karsten Loesing to complain less at both the client
358 and the relay when a relay used to have the HSDir flag but doesn't
359 anymore, and we try to upload a hidden service descriptor.
360 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
362 - Do not try to download missing certificates until we have tried
363 to check our fallback consensus. Fixes bug 583.
364 - Make bridges round reported GeoIP stats info up to the nearest
365 estimate, not down. Now we can distinguish between "0 people from
366 this country" and "1 person from this country".
367 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
368 - Avoid possible segfault if key generation fails in
369 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
370 - Avoid segfault in the case where a badly behaved v2 versioning
371 directory sends a signed networkstatus with missing client-versions.
373 - Avoid segfaults on certain complex invocations of
374 router_get_by_hexdigest(). Bugfix on 0.1.2.
375 - Correct bad index on array access in parse_http_time(). Bugfix
377 - Fix possible bug in vote generation when server versions are present
378 but client versions are not.
379 - Fix rare bug on REDIRECTSTREAM control command when called with no
380 port set: it could erroneously report an error when none had
382 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
383 compressing large objects and find ourselves with more than 4k
384 left over. Bugfix on 0.2.0.
385 - Fix a small memory leak when setting up a hidden service.
386 - Fix a few memory leaks that could in theory happen under bizarre
388 - Fix an assert if we post a general-purpose descriptor via the
389 control port but that descriptor isn't mentioned in our current
390 network consensus. Bug reported by Jon McLachlan; bugfix on
393 o Minor features (controller):
394 - Get NS events working again. Patch from tup.
395 - The GETCONF command now escapes and quotes configuration values
396 that don't otherwise fit into the torrc file.
397 - The SETCONF command now handles quoted values correctly.
399 o Minor features (directory authorities):
400 - New configuration options to override default maximum number of
401 servers allowed on a single IP address. This is important for
402 running a test network on a single host.
403 - Actually implement the -s option to tor-gencert.
404 - Add a manual page for tor-gencert.
406 o Minor features (bridges):
407 - Bridge authorities no longer serve bridge descriptors over
408 unencrypted connections.
410 o Minor features (other):
411 - Add hidden services and DNSPorts to the list of things that make
412 Tor accept that it has running ports. Change starting Tor with no
413 ports from a fatal error to a warning; we might change it back if
414 this turns out to confuse anybody. Fixes bug 579.
417 Changes in version 0.1.2.19 - 2008-01-17
418 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
419 exit policy a little bit more conservative so it's safer to run an
420 exit relay on a home system, and fixes a variety of smaller issues.
423 - Exit policies now reject connections that are addressed to a
424 relay's public (external) IP address too, unless
425 ExitPolicyRejectPrivate is turned off. We do this because too
426 many relays are running nearby to services that trust them based
430 - When the clock jumps forward a lot, do not allow the bandwidth
431 buckets to become negative. Fixes bug 544.
432 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
433 on every successful resolve. Reported by Mike Perry.
434 - Purge old entries from the "rephist" database and the hidden
435 service descriptor database even when DirPort is zero.
436 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
437 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
438 crashing or mis-answering these requests.
439 - When we decide to send a 503 response to a request for servers, do
440 not then also send the server descriptors: this defeats the whole
441 purpose. Fixes bug 539.
444 - Changing the ExitPolicyRejectPrivate setting should cause us to
445 rebuild our server descriptor.
446 - Fix handling of hex nicknames when answering controller requests for
447 networkstatus by name, or when deciding whether to warn about
448 unknown routers in a config option. (Patch from mwenge.)
449 - Fix a couple of hard-to-trigger autoconf problems that could result
450 in really weird results on platforms whose sys/types.h files define
451 nonstandard integer types.
452 - Don't try to create the datadir when running --verify-config or
453 --hash-password. Resolves bug 540.
454 - If we were having problems getting a particular descriptor from the
455 directory caches, and then we learned about a new descriptor for
456 that router, we weren't resetting our failure count. Reported
458 - Although we fixed bug 539 (where servers would send HTTP status 503
459 responses _and_ send a body too), there are still servers out there
460 that haven't upgraded. Therefore, make clients parse such bodies
461 when they receive them.
462 - Run correctly on systems where rlim_t is larger than unsigned long.
463 This includes some 64-bit systems.
464 - Run correctly on platforms (like some versions of OS X 10.5) where
465 the real limit for number of open files is OPEN_FILES, not rlim_max
466 from getrlimit(RLIMIT_NOFILES).
467 - Avoid a spurious free on base64 failure.
468 - Avoid segfaults on certain complex invocations of
469 router_get_by_hexdigest().
470 - Fix rare bug on REDIRECTSTREAM control command when called with no
471 port set: it could erroneously report an error when none had
475 Changes in version 0.2.0.15-alpha - 2007-12-25
476 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
477 features added in 0.2.0.13-alpha.
480 - Fix several remotely triggerable asserts based on DirPort requests
481 for a v2 or v3 networkstatus object before we were prepared. This
482 was particularly bad for 0.2.0.13 and later bridge relays, who
483 would never have a v2 networkstatus and would thus always crash
484 when used. Bugfixes on 0.2.0.x.
485 - Estimate the v3 networkstatus size more accurately, rather than
486 estimating it at zero bytes and giving it artificially high priority
487 compared to other directory requests. Bugfix on 0.2.0.x.
490 - Fix configure.in logic for cross-compilation.
491 - When we load a bridge descriptor from the cache, and it was
492 previously unreachable, mark it as retriable so we won't just
493 ignore it. Also, try fetching a new copy immediately. Bugfixes
495 - The bridge GeoIP stats were counting other relays, for example
496 self-reachability and authority-reachability tests.
499 - Support compilation to target iPhone; patch from cjacker huang.
500 To build for iPhone, pass the --enable-iphone option to configure.
503 Changes in version 0.2.0.14-alpha - 2007-12-23
505 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
506 without a datadirectory from a previous Tor install. Reported
508 - Fix a crash when we fetch a descriptor that turns out to be
509 unexpected (it used to be in our networkstatus when we started
510 fetching it, but it isn't in our current networkstatus), and we
511 aren't using bridges. Bugfix on 0.2.0.x.
512 - Fix a crash when accessing hidden services: it would work the first
513 time you use a given introduction point for your service, but
514 on subsequent requests we'd be using garbage memory. Fixed by
515 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
516 - Fix a crash when we load a bridge descriptor from disk but we don't
517 currently have a Bridge line for it in our torrc. Bugfix on
521 - If bridge authorities set BridgePassword, they will serve a
522 snapshot of known bridge routerstatuses from their DirPort to
523 anybody who knows that password. Unset by default.
526 - Make the unit tests build again.
527 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
528 - Make PublishServerDescriptor default to 1, so the default doesn't
529 have to change as we invent new directory protocol versions.
530 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
531 be included unless sys/time.h is already included. Fixes
532 bug 553. Bugfix on 0.2.0.x.
533 - If we receive a general-purpose descriptor and then receive an
534 identical bridge-purpose descriptor soon after, don't discard
535 the next one as a duplicate.
538 - If BridgeRelay is set to 1, then the default for
539 PublishServerDescriptor is now "bridge" rather than "v2,v3".
540 - If the user sets RelayBandwidthRate but doesn't set
541 RelayBandwidthBurst, then make them equal rather than erroring out.
544 Changes in version 0.2.0.13-alpha - 2007-12-21
545 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
546 Goodell, fixes many more bugs, and adds a lot of infrastructure for
549 o New directory authorities:
550 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
554 - Only update guard status (usable / not usable) once we have
555 enough directory information. This was causing us to always pick
556 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
557 causing us to discard all our guards on startup if we hadn't been
558 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
559 - Purge old entries from the "rephist" database and the hidden
560 service descriptor databases even when DirPort is zero. Bugfix
562 - We were ignoring our RelayBandwidthRate for the first 30 seconds
563 after opening a circuit -- even a relayed circuit. Bugfix on
565 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
566 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
567 crashing or mis-answering these types of requests.
568 - Relays were publishing their server descriptor to v1 and v2
569 directory authorities, but they didn't try publishing to v3-only
570 authorities. Fix this; and also stop publishing to v1 authorities.
572 - When we were reading router descriptors from cache, we were ignoring
573 the annotations -- so for example we were reading in bridge-purpose
574 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
575 - When we decided to send a 503 response to a request for servers, we
576 were then also sending the server descriptors: this defeats the
577 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
580 - Bridge relays now behave like clients with respect to time
581 intervals for downloading new consensus documents -- otherwise they
582 stand out. Bridge users now wait until the end of the interval,
583 so their bridge relay will be sure to have a new consensus document.
584 - Three new config options (AlternateDirAuthority,
585 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
586 user selectively replace the default directory authorities by type,
587 rather than the all-or-nothing replacement that DirServer offers.
588 - Tor can now be configured to read a GeoIP file from disk in one
589 of two formats. This can be used by controllers to map IP addresses
590 to countries. Eventually, it may support exit-by-country.
591 - When possible, bridge relays remember which countries users
592 are coming from, and report aggregate information in their
593 extra-info documents, so that the bridge authorities can learn
594 where Tor is blocked.
595 - Bridge directory authorities now do reachability testing on the
596 bridges they know. They provide router status summaries to the
597 controller via "getinfo ns/purpose/bridge", and also dump summaries
598 to a file periodically.
599 - Stop fetching directory info so aggressively if your DirPort is
600 on but your ORPort is off; stop fetching v2 dir info entirely.
601 You can override these choices with the new FetchDirInfoEarly
605 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
606 consensus documents when there are too many relays at a single
607 IP address. Now clear it in v2 network status documents too, and
608 also clear it in routerinfo_t when the relay is no longer listed
609 in the relevant networkstatus document.
610 - Don't crash if we get an unexpected value for the
611 PublishServerDescriptor config option. Reported by Matt Edman;
612 bugfix on 0.2.0.9-alpha.
613 - Our new v2 hidden service descriptor format allows descriptors
614 that have no introduction points. But Tor crashed when we tried
615 to build a descriptor with no intro points (and it would have
616 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
618 - Fix building with dmalloc 5.5.2 with glibc.
619 - Reject uploaded descriptors and extrainfo documents if they're
620 huge. Otherwise we'll cache them all over the network and it'll
621 clog everything up. Reported by Aljosha Judmayer.
622 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
623 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
624 - When the DANGEROUS_VERSION controller status event told us we're
625 running an obsolete version, it used the string "OLD" to describe
626 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
627 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
628 - If we can't expand our list of entry guards (e.g. because we're
629 using bridges or we have StrictEntryNodes set), don't mark relays
630 down when they fail a directory request. Otherwise we're too quick
631 to mark all our entry points down. Bugfix on 0.1.2.x.
632 - Fix handling of hex nicknames when answering controller requests for
633 networkstatus by name, or when deciding whether to warn about unknown
634 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
635 - Fix a couple of hard-to-trigger autoconf problems that could result
636 in really weird results on platforms whose sys/types.h files define
637 nonstandard integer types. Bugfix on 0.1.2.x.
638 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
639 - Don't crash on name lookup when we have no current consensus. Fixes
640 bug 538; bugfix on 0.2.0.x.
641 - Only Tors that want to mirror the v2 directory info should
642 create the "cached-status" directory in their datadir. (All Tors
643 used to create it.) Bugfix on 0.2.0.9-alpha.
644 - Directory authorities should only automatically download Extra Info
645 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
648 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
649 consumers. (We already do this on HUP.)
650 - Authorities and caches fetch the v2 networkstatus documents
651 less often, now that v3 is encouraged.
652 - Add a new config option BridgeRelay that specifies you want to
653 be a bridge relay. Right now the only difference is that it makes
654 you answer begin_dir requests, and it makes you cache dir info,
655 even if your DirPort isn't on.
656 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
657 ask about source, timestamp of arrival, purpose, etc. We need
658 something like this to help Vidalia not do GeoIP lookups on bridge
660 - Allow multiple HashedControlPassword config lines, to support
661 multiple controller passwords.
662 - Authorities now decide whether they're authoritative for a given
663 router based on the router's purpose.
664 - New config options AuthDirBadDir and AuthDirListBadDirs for
665 authorities to mark certain relays as "bad directories" in the
666 networkstatus documents. Also supports the "!baddir" directive in
667 the approved-routers file.
670 Changes in version 0.2.0.12-alpha - 2007-11-16
671 This twelfth development snapshot fixes some more build problems as
672 well as a few minor bugs.
675 - Make it build on OpenBSD again. Patch from tup.
676 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
677 package-building for Red Hat, OS X, etc.
679 o Minor bugfixes (on 0.1.2.x):
680 - Changing the ExitPolicyRejectPrivate setting should cause us to
681 rebuild our server descriptor.
683 o Minor bugfixes (on 0.2.0.x):
684 - When we're lacking a consensus, don't try to perform rendezvous
685 operations. Reported by Karsten Loesing.
686 - Fix a small memory leak whenever we decide against using a
687 newly picked entry guard. Reported by Mike Perry.
688 - When authorities detected more than two relays running on the same
689 IP address, they were clearing all the status flags but forgetting
690 to clear the "hsdir" flag. So clients were being told that a
691 given relay was the right choice for a v2 hsdir lookup, yet they
692 never had its descriptor because it was marked as 'not running'
694 - If we're trying to fetch a bridge descriptor and there's no way
695 the bridge authority could help us (for example, we don't know
696 a digest, or there is no bridge authority), don't be so eager to
697 fall back to asking the bridge authority.
698 - If we're using bridges or have strictentrynodes set, and our
699 chosen exit is in the same family as all our bridges/entry guards,
700 then be flexible about families.
703 - When we negotiate a v2 link-layer connection (not yet implemented),
704 accept RELAY_EARLY cells and turn them into RELAY cells if we've
705 negotiated a v1 connection for their next step. Initial code for
709 Changes in version 0.2.0.11-alpha - 2007-11-12
710 This eleventh development snapshot fixes some build problems with
711 the previous snapshot. It also includes a more secure-by-default exit
712 policy for relays, fixes an enormous memory leak for exit relays, and
713 fixes another bug where servers were falling out of the directory list.
716 - Exit policies now reject connections that are addressed to a
717 relay's public (external) IP address too, unless
718 ExitPolicyRejectPrivate is turned off. We do this because too
719 many relays are running nearby to services that trust them based
720 on network address. Bugfix on 0.1.2.x.
723 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
724 on every successful resolve. Reported by Mike Perry; bugfix
726 - On authorities, never downgrade to old router descriptors simply
727 because they're listed in the consensus. This created a catch-22
728 where we wouldn't list a new descriptor because there was an
729 old one in the consensus, and we couldn't get the new one in the
730 consensus because we wouldn't list it. Possible fix for bug 548.
731 Also, this might cause bug 543 to appear on authorities; if so,
732 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
734 o Packaging fixes on 0.2.0.10-alpha:
735 - We were including instructions about what to do with the
736 src/config/fallback-consensus file, but we weren't actually
737 including it in the tarball. Disable all of that for now.
740 - Allow people to say PreferTunnelledDirConns rather than
741 PreferTunneledDirConns, for those alternate-spellers out there.
744 - Don't reevaluate all the information from our consensus document
745 just because we've downloaded a v2 networkstatus that we intend
746 to cache. Fixes bug 545; bugfix on 0.2.0.x.
749 Changes in version 0.2.0.10-alpha - 2007-11-10
750 This tenth development snapshot adds a third v3 directory authority
751 run by Mike Perry, adds most of Karsten Loesing's new hidden service
752 descriptor format, fixes a bad crash bug and new bridge bugs introduced
753 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
754 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
755 addresses many more minor issues.
757 o New directory authorities:
758 - Set up ides (run by Mike Perry) as the third v3 directory authority.
761 - Allow tunnelled directory connections to ask for an encrypted
762 "begin_dir" connection or an anonymized "uses a full Tor circuit"
763 connection independently. Now we can make anonymized begin_dir
764 connections for (e.g.) more secure hidden service posting and
766 - More progress on proposal 114: code from Karsten Loesing to
767 implement new hidden service descriptor format.
768 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
769 accommodate the growing number of servers that use the default
771 - Directory authorities use a new formula for selecting which nodes
772 to advertise as Guards: they must be in the top 7/8 in terms of
773 how long we have known about them, and above the median of those
774 nodes in terms of weighted fractional uptime.
775 - Make "not enough dir info yet" warnings describe *why* Tor feels
776 it doesn't have enough directory info yet.
779 - Stop servers from crashing if they set a Family option (or
780 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
782 - Make bridge users work again -- the move to v3 directories in
783 0.2.0.9-alpha had introduced a number of bugs that made bridges
784 no longer work for clients.
785 - When the clock jumps forward a lot, do not allow the bandwidth
786 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
788 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
789 - When the consensus lists a router descriptor that we previously were
790 mirroring, but that we considered non-canonical, reload the
791 descriptor as canonical. This fixes bug 543 where Tor servers
792 would start complaining after a few days that they don't have
793 enough directory information to build a circuit.
794 - Consider replacing the current consensus when certificates arrive
795 that make the pending consensus valid. Previously, we were only
796 considering replacement when the new certs _didn't_ help.
797 - Fix an assert error on startup if we didn't already have the
798 consensus and certs cached in our datadirectory: we were caching
799 the consensus in consensus_waiting_for_certs but then free'ing it
801 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
802 Request) if we need more v3 certs but we've already got pending
803 requests for all of them.
804 - Correctly back off from failing certificate downloads. Fixes
806 - Authorities don't vote on the Running flag if they have been running
807 for less than 30 minutes themselves. Fixes bug 547, where a newly
808 started authority would vote that everyone was down.
811 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
812 it, it had no AES, and it hasn't seen any security patches since
816 - Clients now hold circuitless TLS connections open for 1.5 times
817 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
818 rebuild a new circuit over them within that timeframe. Previously,
819 they held them open only for KeepalivePeriod (5 minutes).
820 - Use "If-Modified-Since" to avoid retrieving consensus
821 networkstatuses that we already have.
822 - When we have no consensus, check FallbackNetworkstatusFile (defaults
823 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
824 we start knowing some directory caches.
825 - When we receive a consensus from the future, warn about skew.
826 - Improve skew reporting: try to give the user a better log message
827 about how skewed they are, and how much this matters.
828 - When we have a certificate for an authority, believe that
829 certificate's claims about the authority's IP address.
830 - New --quiet command-line option to suppress the default console log.
831 Good in combination with --hash-password.
832 - Authorities send back an X-Descriptor-Not-New header in response to
833 an accepted-but-discarded descriptor upload. Partially implements
835 - Make the log message for "tls error. breaking." more useful.
836 - Better log messages about certificate downloads, to attempt to
837 track down the second incarnation of bug 546.
839 o Minor features (bridges):
840 - If bridge users set UpdateBridgesFromAuthority, but the digest
841 they ask for is a 404 from the bridge authority, they now fall
842 back to trying the bridge directly.
843 - Bridges now use begin_dir to publish their server descriptor to
844 the bridge authority, even when they haven't set TunnelDirConns.
846 o Minor features (controller):
847 - When reporting clock skew, and we know that the clock is _at least
848 as skewed_ as some value, but we don't know the actual value,
849 report the value as a "minimum skew."
852 - Update linux-tor-prio.sh script to allow QoS based on the uid of
853 the Tor process. Patch from Marco Bonetti with tweaks from Mike
857 - Refuse to start if both ORPort and UseBridges are set. Bugfix
858 on 0.2.0.x, suggested by Matt Edman.
859 - Don't stop fetching descriptors when FetchUselessDescriptors is
860 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
861 reported by tup and ioerror.
862 - Better log message on vote from unknown authority.
863 - Don't log "Launching 0 request for 0 router" message.
865 o Minor bugfixes (memory leaks):
866 - Stop leaking memory every time we parse a v3 certificate. Bugfix
868 - Stop leaking memory every time we load a v3 certificate. Bugfix
869 on 0.2.0.1-alpha. Fixes Bug 536.
870 - Stop leaking a cached networkstatus on exit. Bugfix on
872 - Stop leaking voter information every time we free a consensus.
873 Bugfix on 0.2.0.3-alpha.
874 - Stop leaking signed data every time we check a voter signature.
875 Bugfix on 0.2.0.3-alpha.
876 - Stop leaking a signature every time we fail to parse a consensus or
877 a vote. Bugfix on 0.2.0.3-alpha.
878 - Stop leaking v2_download_status_map on shutdown. Bugfix on
880 - Stop leaking conn->nickname every time we make a connection to a
881 Tor relay without knowing its expected identity digest (e.g. when
882 using bridges). Bugfix on 0.2.0.3-alpha.
884 - Minor bugfixes (portability):
885 - Run correctly on platforms where rlim_t is larger than unsigned
886 long, and/or where the real limit for number of open files is
887 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
888 particular, these may be needed for OS X 10.5.
891 Changes in version 0.1.2.18 - 2007-10-28
892 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
893 hidden service introduction that were causing huge delays, and a big
894 bug that was causing some servers to disappear from the network status
895 lists for a few hours each day.
897 o Major bugfixes (crashes):
898 - If a connection is shut down abruptly because of something that
899 happened inside connection_flushed_some(), do not call
900 connection_finished_flushing(). Should fix bug 451:
901 "connection_stop_writing: Assertion conn->write_event failed"
902 Bugfix on 0.1.2.7-alpha.
903 - Fix possible segfaults in functions called from
904 rend_process_relay_cell().
906 o Major bugfixes (hidden services):
907 - Hidden services were choosing introduction points uniquely by
908 hexdigest, but when constructing the hidden service descriptor
909 they merely wrote the (potentially ambiguous) nickname.
910 - Clients now use the v2 intro format for hidden service
911 connections: they specify their chosen rendezvous point by identity
912 digest rather than by (potentially ambiguous) nickname. These
913 changes could speed up hidden service connections dramatically.
915 o Major bugfixes (other):
916 - Stop publishing a new server descriptor just because we get a
917 HUP signal. This led (in a roundabout way) to some servers getting
918 dropped from the networkstatus lists for a few hours each day.
919 - When looking for a circuit to cannibalize, consider family as well
920 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
921 circuit cannibalization).
922 - When a router wasn't listed in a new networkstatus, we were leaving
923 the flags for that router alone -- meaning it remained Named,
924 Running, etc -- even though absence from the networkstatus means
925 that it shouldn't be considered to exist at all anymore. Now we
926 clear all the flags for routers that fall out of the networkstatus
927 consensus. Fixes bug 529.
930 - Don't try to access (or alter) the state file when running
931 --list-fingerprint or --verify-config or --hash-password. Resolves
933 - When generating information telling us how to extend to a given
934 router, do not try to include the nickname if it is
935 absent. Resolves bug 467.
936 - Fix a user-triggerable segfault in expand_filename(). (There isn't
937 a way to trigger this remotely.)
938 - When sending a status event to the controller telling it that an
939 OR address is readable, set the port correctly. (Previously we
940 were reporting the dir port.)
941 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
942 command. Bugfix on 0.1.2.17.
943 - When loading bandwidth history, do not believe any information in
944 the future. Fixes bug 434.
945 - When loading entry guard information, do not believe any information
947 - When we have our clock set far in the future and generate an
948 onion key, then re-set our clock to be correct, we should not stop
949 the onion key from getting rotated.
950 - On some platforms, accept() can return a broken address. Detect
951 this more quietly, and deal accordingly. Fixes bug 483.
952 - It's not actually an error to find a non-pending entry in the DNS
953 cache when canceling a pending resolve. Don't log unless stuff
954 is fishy. Resolves bug 463.
955 - Don't reset trusted dir server list when we set a configuration
956 option. Patch from Robert Hogan.
957 - Don't try to create the datadir when running --verify-config or
958 --hash-password. Resolves bug 540.
961 Changes in version 0.2.0.9-alpha - 2007-10-24
962 This ninth development snapshot switches clients to the new v3 directory
963 system; allows servers to be listed in the network status even when they
964 have the same nickname as a registered server; and fixes many other
965 bugs including a big one that was causing some servers to disappear
966 from the network status lists for a few hours each day.
968 o Major features (directory system):
969 - Clients now download v3 consensus networkstatus documents instead
970 of v2 networkstatus documents. Clients and caches now base their
971 opinions about routers on these consensus documents. Clients only
972 download router descriptors listed in the consensus.
973 - Authorities now list servers who have the same nickname as
974 a different named server, but list them with a new flag,
975 "Unnamed". Now we can list servers that happen to pick the same
976 nickname as a server that registered two years ago and then
977 disappeared. Partially implements proposal 122.
978 - If the consensus list a router as "Unnamed", the name is assigned
979 to a different router: do not identify the router by that name.
980 Partially implements proposal 122.
981 - Authorities can now come to a consensus on which method to use to
982 compute the consensus. This gives us forward compatibility.
985 - Stop publishing a new server descriptor just because we HUP or
986 when we find our DirPort to be reachable but won't actually publish
987 it. New descriptors without any real changes are dropped by the
988 authorities, and can screw up our "publish every 18 hours" schedule.
990 - When a router wasn't listed in a new networkstatus, we were leaving
991 the flags for that router alone -- meaning it remained Named,
992 Running, etc -- even though absence from the networkstatus means
993 that it shouldn't be considered to exist at all anymore. Now we
994 clear all the flags for routers that fall out of the networkstatus
995 consensus. Fixes bug 529; bugfix on 0.1.2.x.
996 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
997 extrainfo documents and then discard them immediately for not
998 matching the latest router. Bugfix on 0.2.0.1-alpha.
1000 o Minor features (v3 directory protocol):
1001 - Allow tor-gencert to generate a new certificate without replacing
1003 - Allow certificates to include an address.
1004 - When we change our directory-cache settings, reschedule all voting
1005 and download operations.
1006 - Reattempt certificate downloads immediately on failure, as long as
1007 we haven't failed a threshold number of times yet.
1008 - Delay retrying consensus downloads while we're downloading
1009 certificates to verify the one we just got. Also, count getting a
1010 consensus that we already have (or one that isn't valid) as a failure,
1011 and count failing to get the certificates after 20 minutes as a
1013 - Build circuits and download descriptors even if our consensus is a
1014 little expired. (This feature will go away once authorities are
1017 o Minor features (router descriptor cache):
1018 - If we find a cached-routers file that's been sitting around for more
1019 than 28 days unmodified, then most likely it's a leftover from
1020 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
1022 - When we (as a cache) download a descriptor because it was listed
1023 in a consensus, remember when the consensus was supposed to expire,
1024 and don't expire the descriptor until then.
1026 o Minor features (performance):
1027 - Call routerlist_remove_old_routers() much less often. This should
1028 speed startup, especially on directory caches.
1029 - Don't try to launch new descriptor downloads quite so often when we
1030 already have enough directory information to build circuits.
1031 - Base64 decoding was actually showing up on our profile when parsing
1032 the initial descriptor file; switch to an in-process all-at-once
1033 implementation that's about 3.5x times faster than calling out to
1036 o Minor features (compilation):
1037 - Detect non-ASCII platforms (if any still exist) and refuse to
1038 build there: some of our code assumes that 'A' is 65 and so on.
1040 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
1041 - Make the "next period" votes into "current period" votes immediately
1042 after publishing the consensus; avoid a heisenbug that made them
1043 stick around indefinitely.
1044 - When we discard a vote as a duplicate, do not report this as
1046 - Treat missing v3 keys or certificates as an error when running as a
1047 v3 directory authority.
1048 - When we're configured to be a v3 authority, but we're only listed
1049 as a non-v3 authority in our DirServer line for ourself, correct
1051 - If an authority doesn't have a qualified hostname, just put
1052 its address in the vote. This fixes the problem where we referred to
1053 "moria on moria:9031."
1054 - Distinguish between detached signatures for the wrong period, and
1055 detached signatures for a divergent vote.
1056 - Fix a small memory leak when computing a consensus.
1057 - When there's no concensus, we were forming a vote every 30
1058 minutes, but writing the "valid-after" line in our vote based
1059 on our configured V3AuthVotingInterval: so unless the intervals
1060 matched up, we immediately rejected our own vote because it didn't
1061 start at the voting interval that caused us to construct a vote.
1063 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
1064 - Delete unverified-consensus when the real consensus is set.
1065 - Consider retrying a consensus networkstatus fetch immediately
1066 after one fails: don't wait 60 seconds to notice.
1067 - When fetching a consensus as a cache, wait until a newer consensus
1068 should exist before trying to replace the current one.
1069 - Use a more forgiving schedule for retrying failed consensus
1070 downloads than for other types.
1072 o Minor bugfixes (other directory issues):
1073 - Correct the implementation of "download votes by digest." Bugfix on
1075 - Authorities no longer send back "400 you're unreachable please fix
1076 it" errors to Tor servers that aren't online all the time. We're
1077 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
1079 o Minor bugfixes (controller):
1080 - Don't reset trusted dir server list when we set a configuration
1081 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
1082 - Respond to INT and TERM SIGNAL commands before we execute the
1083 signal, in case the signal shuts us down. We had a patch in
1084 0.1.2.1-alpha that tried to do this by queueing the response on
1085 the connection's buffer before shutting down, but that really
1086 isn't the same thing at all. Bug located by Matt Edman.
1088 o Minor bugfixes (misc):
1089 - Correctly check for bad options to the "PublishServerDescriptor"
1090 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
1091 - Stop leaking memory on failing case of base32_decode, and make
1092 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
1093 - Don't try to download extrainfo documents when we're trying to
1094 fetch enough directory info to build a circuit: having enough
1095 info should get priority. Bugfix on 0.2.0.x.
1096 - Don't complain that "your server has not managed to confirm that its
1097 ports are reachable" if we haven't been able to build any circuits
1098 yet. Bug found by spending four hours without a v3 consensus. Bugfix
1100 - Detect the reason for failing to mmap a descriptor file we just
1101 wrote, and give a more useful log message. Fixes bug 533. Bugfix
1104 o Code simplifications and refactoring:
1105 - Remove support for the old bw_accounting file: we've been storing
1106 bandwidth accounting information in the state file since
1107 0.1.2.5-alpha. This may result in bandwidth accounting errors
1108 if you try to upgrade from 0.1.1.x or earlier, or if you try to
1109 downgrade to 0.1.1.x or earlier.
1110 - New convenience code to locate a file within the DataDirectory.
1111 - Move non-authority functionality out of dirvote.c.
1112 - Refactor the arguments for router_pick_{directory_|trusteddir}server
1113 so that they all take the same named flags.
1116 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
1117 Unix users an easy way to script their Tor process (e.g. by
1118 adjusting bandwidth based on the time of the day).
1121 Changes in version 0.2.0.8-alpha - 2007-10-12
1122 This eighth development snapshot fixes a crash bug that's been bothering
1123 us since February 2007, lets bridge authorities store a list of bridge
1124 descriptors they've seen, gets v3 directory voting closer to working,
1125 starts caching v3 directory consensus documents on directory mirrors,
1126 and fixes a variety of smaller issues including some minor memory leaks.
1128 o Major features (router descriptor cache):
1129 - Store routers in a file called cached-descriptors instead of in
1130 cached-routers. Initialize cached-descriptors from cached-routers
1131 if the old format is around. The new format allows us to store
1132 annotations along with descriptors.
1133 - Use annotations to record the time we received each descriptor, its
1134 source, and its purpose.
1135 - Disable the SETROUTERPURPOSE controller command: it is now
1137 - Controllers should now specify cache=no or cache=yes when using
1138 the +POSTDESCRIPTOR command.
1139 - Bridge authorities now write bridge descriptors to disk, meaning
1140 we can export them to other programs and begin distributing them
1143 o Major features (directory authorities):
1144 - When a v3 authority is missing votes or signatures, it now tries
1146 - Directory authorities track weighted fractional uptime as well as
1147 weighted mean-time-between failures. WFU is suitable for deciding
1148 whether a node is "usually up", while MTBF is suitable for deciding
1149 whether a node is "likely to stay up." We need both, because
1150 "usually up" is a good requirement for guards, while "likely to
1151 stay up" is a good requirement for long-lived connections.
1153 o Major features (v3 directory system):
1154 - Caches now download v3 network status documents as needed,
1155 and download the descriptors listed in them.
1156 - All hosts now attempt to download and keep fresh v3 authority
1157 certificates, and re-attempt after failures.
1158 - More internal-consistency checks for vote parsing.
1160 o Major bugfixes (crashes):
1161 - If a connection is shut down abruptly because of something that
1162 happened inside connection_flushed_some(), do not call
1163 connection_finished_flushing(). Should fix bug 451. Bugfix on
1166 o Major bugfixes (performance):
1167 - Fix really bad O(n^2) performance when parsing a long list of
1168 routers: Instead of searching the entire list for an "extra-info "
1169 string which usually wasn't there, once for every routerinfo
1170 we read, just scan lines forward until we find one we like.
1172 - When we add data to a write buffer in response to the data on that
1173 write buffer getting low because of a flush, do not consider the
1174 newly added data as a candidate for immediate flushing, but rather
1175 make it wait until the next round of writing. Otherwise, we flush
1176 and refill recursively, and a single greedy TLS connection can
1177 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
1179 o Minor features (v3 authority system):
1180 - Add more ways for tools to download the votes that lead to the
1182 - Send a 503 when low on bandwidth and a vote, consensus, or
1183 certificate is requested.
1184 - If-modified-since is now implemented properly for all kinds of
1185 certificate requests.
1187 o Minor bugfixes (network statuses):
1188 - Tweak the implementation of proposal 109 slightly: allow at most
1189 two Tor servers on the same IP address, except if it's the location
1190 of a directory authority, in which case allow five. Bugfix on
1193 o Minor bugfixes (controller):
1194 - When sending a status event to the controller telling it that an
1195 OR address is reachable, set the port correctly. (Previously we
1196 were reporting the dir port.) Bugfix on 0.1.2.x.
1198 o Minor bugfixes (v3 directory system):
1199 - Fix logic to look up a cert by its signing key digest. Bugfix on
1201 - Only change the reply to a vote to "OK" if it's not already
1202 set. This gets rid of annoying "400 OK" log messages, which may
1203 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
1204 - When we get a valid consensus, recompute the voting schedule.
1205 - Base the valid-after time of a vote on the consensus voting
1206 schedule, not on our preferred schedule.
1207 - Make the return values and messages from signature uploads and
1208 downloads more sensible.
1209 - Fix a memory leak when serving votes and consensus documents, and
1210 another when serving certificates.
1212 o Minor bugfixes (performance):
1213 - Use a slightly simpler string hashing algorithm (copying Python's
1214 instead of Java's) and optimize our digest hashing algorithm to take
1215 advantage of 64-bit platforms and to remove some possibly-costly
1217 - Fix a minor memory leak whenever we parse guards from our state
1218 file. Bugfix on 0.2.0.7-alpha.
1219 - Fix a minor memory leak whenever we write out a file. Bugfix on
1221 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
1222 command. Bugfix on 0.2.0.5-alpha.
1224 o Minor bugfixes (portability):
1225 - On some platforms, accept() can return a broken address. Detect
1226 this more quietly, and deal accordingly. Fixes bug 483.
1227 - Stop calling tor_strlower() on uninitialized memory in some cases.
1228 Bugfix in 0.2.0.7-alpha.
1230 o Minor bugfixes (usability):
1231 - Treat some 403 responses from directory servers as INFO rather than
1232 WARN-severity events.
1233 - It's not actually an error to find a non-pending entry in the DNS
1234 cache when canceling a pending resolve. Don't log unless stuff is
1235 fishy. Resolves bug 463.
1237 o Minor bugfixes (anonymity):
1238 - Never report that we've used more bandwidth than we're willing to
1239 relay: it leaks how much non-relay traffic we're using. Resolves
1241 - When looking for a circuit to cannibalize, consider family as well
1242 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
1243 circuit cannibalization).
1245 o Code simplifications and refactoring:
1246 - Make a bunch of functions static. Remove some dead code.
1247 - Pull out about a third of the really big routerlist.c; put it in a
1248 new module, networkstatus.c.
1249 - Merge the extra fields in local_routerstatus_t back into
1250 routerstatus_t: we used to need one routerstatus_t for each
1251 authority's opinion, plus a local_routerstatus_t for the locally
1252 computed consensus opinion. To save space, we put the locally
1253 modified fields into local_routerstatus_t, and only the common
1254 stuff into routerstatus_t. But once v3 directories are in use,
1255 clients and caches will no longer need to hold authority opinions;
1256 thus, the rationale for keeping the types separate is now gone.
1257 - Make the code used to reschedule and reattempt downloads more
1259 - Turn all 'Are we a directory server/mirror?' logic into a call to
1261 - Remove the code to generate the oldest (v1) directory format.
1262 The code has been disabled since 0.2.0.5-alpha.
1265 Changes in version 0.2.0.7-alpha - 2007-09-21
1266 This seventh development snapshot makes bridges work again, makes bridge
1267 authorities work for the first time, fixes two huge performance flaws
1268 in hidden services, and fixes a variety of minor issues.
1270 o New directory authorities:
1271 - Set up moria1 and tor26 as the first v3 directory authorities. See
1272 doc/spec/dir-spec.txt for details on the new directory design.
1274 o Major bugfixes (crashes):
1275 - Fix possible segfaults in functions called from
1276 rend_process_relay_cell(). Bugfix on 0.1.2.x.
1278 o Major bugfixes (bridges):
1279 - Fix a bug that made servers send a "404 Not found" in response to
1280 attempts to fetch their server descriptor. This caused Tor servers
1281 to take many minutes to establish reachability for their DirPort,
1282 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
1283 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
1284 users configure that and specify a bridge with an identity
1285 fingerprint, now they will lookup the bridge descriptor at the
1286 default bridge authority via a one-hop tunnel, but once circuits
1287 are established they will switch to a three-hop tunnel for later
1288 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
1290 o Major bugfixes (hidden services):
1291 - Hidden services were choosing introduction points uniquely by
1292 hexdigest, but when constructing the hidden service descriptor
1293 they merely wrote the (potentially ambiguous) nickname.
1294 - Clients now use the v2 intro format for hidden service
1295 connections: they specify their chosen rendezvous point by identity
1296 digest rather than by (potentially ambiguous) nickname. Both
1297 are bugfixes on 0.1.2.x, and they could speed up hidden service
1298 connections dramatically. Thanks to Karsten Loesing.
1300 o Minor features (security):
1301 - As a client, do not believe any server that tells us that an
1302 address maps to an internal address space.
1303 - Make it possible to enable HashedControlPassword and
1304 CookieAuthentication at the same time.
1306 o Minor features (guard nodes):
1307 - Tag every guard node in our state file with the version that
1308 we believe added it, or with our own version if we add it. This way,
1309 if a user temporarily runs an old version of Tor and then switches
1310 back to a new one, she doesn't automatically lose her guards.
1312 o Minor features (speed):
1313 - When implementing AES counter mode, update only the portions of the
1314 counter buffer that need to change, and don't keep separate
1315 network-order and host-order counters when they are the same (i.e.,
1316 on big-endian hosts.)
1318 o Minor features (controller):
1319 - Accept LF instead of CRLF on controller, since some software has a
1320 hard time generating real Internet newlines.
1321 - Add GETINFO values for the server status events
1322 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
1326 - Routers no longer include bandwidth-history lines in their
1327 descriptors; this information is already available in extra-info
1328 documents, and including it in router descriptors took up 60%
1329 (!) of compressed router descriptor downloads. Completes
1330 implementation of proposal 104.
1331 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
1332 and TorControl.py, as they use the old v0 controller protocol,
1333 and are obsoleted by TorFlow anyway.
1334 - Drop support for v1 rendezvous descriptors, since we never used
1335 them anyway, and the code has probably rotted by now. Based on
1336 patch from Karsten Loesing.
1337 - On OSX, stop warning the user that kqueue support in libevent is
1338 "experimental", since it seems to have worked fine for ages.
1341 - When generating information telling us how to extend to a given
1342 router, do not try to include the nickname if it is absent. Fixes
1343 bug 467. Bugfix on 0.2.0.3-alpha.
1344 - Fix a user-triggerable (but not remotely-triggerable) segfault
1345 in expand_filename(). Bugfix on 0.1.2.x.
1346 - Fix a memory leak when freeing incomplete requests from DNSPort.
1347 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
1348 - Don't try to access (or alter) the state file when running
1349 --list-fingerprint or --verify-config or --hash-password. (Resolves
1350 bug 499.) Bugfix on 0.1.2.x.
1351 - Servers used to decline to publish their DirPort if their
1352 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
1353 were below a threshold. Now they only look at BandwidthRate and
1354 RelayBandwidthRate. Bugfix on 0.1.2.x.
1355 - Remove an optimization in the AES counter-mode code that assumed
1356 that the counter never exceeded 2^68. When the counter can be set
1357 arbitrarily as an IV (as it is by Karsten's new hidden services
1358 code), this assumption no longer holds. Bugfix on 0.1.2.x.
1359 - Resume listing "AUTHORITY" flag for authorities in network status.
1360 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
1362 o Code simplifications and refactoring:
1363 - Revamp file-writing logic so we don't need to have the entire
1364 contents of a file in memory at once before we write to disk. Tor,
1366 - Turn "descriptor store" into a full-fledged type.
1367 - Move all NT services code into a separate source file.
1368 - Unify all code that computes medians, percentile elements, etc.
1369 - Get rid of a needless malloc when parsing address policies.
1372 Changes in version 0.1.2.17 - 2007-08-30
1373 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
1374 X bundles. Vidalia 0.0.14 makes authentication required for the
1375 ControlPort in the default configuration, which addresses important
1376 security risks. Everybody who uses Vidalia (or another controller)
1379 In addition, this Tor update fixes major load balancing problems with
1380 path selection, which should speed things up a lot once many people
1383 o Major bugfixes (security):
1384 - We removed support for the old (v0) control protocol. It has been
1385 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
1386 become more of a headache than it's worth.
1388 o Major bugfixes (load balancing):
1389 - When choosing nodes for non-guard positions, weight guards
1390 proportionally less, since they already have enough load. Patch
1392 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
1393 will allow fast Tor servers to get more attention.
1394 - When we're upgrading from an old Tor version, forget our current
1395 guards and pick new ones according to the new weightings. These
1396 three load balancing patches could raise effective network capacity
1397 by a factor of four. Thanks to Mike Perry for measurements.
1399 o Major bugfixes (stream expiration):
1400 - Expire not-yet-successful application streams in all cases if
1401 they've been around longer than SocksTimeout. Right now there are
1402 some cases where the stream will live forever, demanding a new
1403 circuit every 15 seconds. Fixes bug 454; reported by lodger.
1405 o Minor features (controller):
1406 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
1407 is valid before any authentication has been received. It tells
1408 a controller what kind of authentication is expected, and what
1409 protocol is spoken. Implements proposal 119.
1411 o Minor bugfixes (performance):
1412 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
1413 greatly speeding up loading cached-routers from disk on startup.
1414 - Disable sentinel-based debugging for buffer code: we squashed all
1415 the bugs that this was supposed to detect a long time ago, and now
1416 its only effect is to change our buffer sizes from nice powers of
1417 two (which platform mallocs tend to like) to values slightly over
1418 powers of two (which make some platform mallocs sad).
1420 o Minor bugfixes (misc):
1421 - If exit bandwidth ever exceeds one third of total bandwidth, then
1422 use the correct formula to weight exit nodes when choosing paths.
1423 Based on patch from Mike Perry.
1424 - Choose perfectly fairly among routers when choosing by bandwidth and
1425 weighting by fraction of bandwidth provided by exits. Previously, we
1426 would choose with only approximate fairness, and correct ourselves
1427 if we ran off the end of the list.
1428 - If we require CookieAuthentication but we fail to write the
1429 cookie file, we would warn but not exit, and end up in a state
1430 where no controller could authenticate. Now we exit.
1431 - If we require CookieAuthentication, stop generating a new cookie
1432 every time we change any piece of our config.
1433 - Refuse to start with certain directory authority keys, and
1434 encourage people using them to stop.
1435 - Terminate multi-line control events properly. Original patch
1437 - Fix a minor memory leak when we fail to find enough suitable
1438 servers to choose a circuit.
1439 - Stop leaking part of the descriptor when we run into a particularly
1440 unparseable piece of it.
1443 Changes in version 0.2.0.6-alpha - 2007-08-26
1444 This sixth development snapshot features a new Vidalia version in the
1445 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
1446 the ControlPort in the default configuration, which addresses important
1449 In addition, this snapshot fixes major load balancing problems
1450 with path selection, which should speed things up a lot once many
1451 people have upgraded. The directory authorities also use a new
1452 mean-time-between-failure approach to tracking which servers are stable,
1453 rather than just looking at the most recent uptime.
1455 o New directory authorities:
1456 - Set up Tonga as the default bridge directory authority.
1459 - Directory authorities now track servers by weighted
1460 mean-times-between-failures. When we have 4 or more days of data,
1461 use measured MTBF rather than declared uptime to decide whether
1462 to call a router Stable. Implements proposal 108.
1464 o Major bugfixes (load balancing):
1465 - When choosing nodes for non-guard positions, weight guards
1466 proportionally less, since they already have enough load. Patch
1468 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
1469 will allow fast Tor servers to get more attention.
1470 - When we're upgrading from an old Tor version, forget our current
1471 guards and pick new ones according to the new weightings. These
1472 three load balancing patches could raise effective network capacity
1473 by a factor of four. Thanks to Mike Perry for measurements.
1475 o Major bugfixes (descriptor parsing):
1476 - Handle unexpected whitespace better in malformed descriptors. Bug
1477 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
1480 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
1481 GETINFO for Torstat to use until it can switch to using extrainfos.
1482 - Optionally (if built with -DEXPORTMALLINFO) export the output
1483 of mallinfo via http, as tor/mallinfo.txt. Only accessible
1487 - Do not intermix bridge routers with controller-added
1488 routers. (Bugfix on 0.2.0.x)
1489 - Do not fail with an assert when accept() returns an unexpected
1490 address family. Addresses but does not wholly fix bug 483. (Bugfix
1492 - Let directory authorities startup even when they can't generate
1493 a descriptor immediately, e.g. because they don't know their
1495 - Stop putting the authentication cookie in a file called "0"
1496 in your working directory if you don't specify anything for the
1497 new CookieAuthFile option. Reported by Matt Edman.
1498 - Make it possible to read the PROTOCOLINFO response in a way that
1499 conforms to our control-spec. Reported by Matt Edman.
1500 - Fix a minor memory leak when we fail to find enough suitable
1501 servers to choose a circuit. Bugfix on 0.1.2.x.
1502 - Stop leaking part of the descriptor when we run into a particularly
1503 unparseable piece of it. Bugfix on 0.1.2.x.
1504 - Unmap the extrainfo cache file on exit.
1507 Changes in version 0.2.0.5-alpha - 2007-08-19
1508 This fifth development snapshot fixes compilation on Windows again;
1509 fixes an obnoxious client-side bug that slowed things down and put
1510 extra load on the network; gets us closer to using the v3 directory
1511 voting scheme; makes it easier for Tor controllers to use cookie-based
1512 authentication; and fixes a variety of other bugs.
1515 - Version 1 directories are no longer generated in full. Instead,
1516 authorities generate and serve "stub" v1 directories that list
1517 no servers. This will stop Tor versions 0.1.0.x and earlier from
1518 working, but (for security reasons) nobody should be running those
1521 o Major bugfixes (compilation, 0.2.0.x):
1522 - Try to fix Win32 compilation again: improve checking for IPv6 types.
1523 - Try to fix MSVC compilation: build correctly on platforms that do
1524 not define s6_addr16 or s6_addr32.
1525 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
1528 o Major bugfixes (stream expiration):
1529 - Expire not-yet-successful application streams in all cases if
1530 they've been around longer than SocksTimeout. Right now there are
1531 some cases where the stream will live forever, demanding a new
1532 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
1535 o Minor features (directory servers):
1536 - When somebody requests a list of statuses or servers, and we have
1537 none of those, return a 404 rather than an empty 200.
1539 o Minor features (directory voting):
1540 - Store v3 consensus status consensuses on disk, and reload them
1543 o Minor features (security):
1544 - Warn about unsafe ControlPort configurations.
1545 - Refuse to start with certain directory authority keys, and
1546 encourage people using them to stop.
1548 o Minor features (controller):
1549 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
1550 is valid before any authentication has been received. It tells
1551 a controller what kind of authentication is expected, and what
1552 protocol is spoken. Implements proposal 119.
1553 - New config option CookieAuthFile to choose a new location for the
1554 cookie authentication file, and config option
1555 CookieAuthFileGroupReadable to make it group-readable.
1557 o Minor features (unit testing):
1558 - Add command-line arguments to unit-test executable so that we can
1559 invoke any chosen test from the command line rather than having
1560 to run the whole test suite at once; and so that we can turn on
1561 logging for the unit tests.
1563 o Minor bugfixes (on 0.1.2.x):
1564 - If we require CookieAuthentication but we fail to write the
1565 cookie file, we would warn but not exit, and end up in a state
1566 where no controller could authenticate. Now we exit.
1567 - If we require CookieAuthentication, stop generating a new cookie
1568 every time we change any piece of our config.
1569 - When loading bandwidth history, do not believe any information in
1570 the future. Fixes bug 434.
1571 - When loading entry guard information, do not believe any information
1573 - When we have our clock set far in the future and generate an
1574 onion key, then re-set our clock to be correct, we should not stop
1575 the onion key from getting rotated.
1576 - Clean up torrc sample config file.
1577 - Do not automatically run configure from autogen.sh. This
1578 non-standard behavior tended to annoy people who have built other
1581 o Minor bugfixes (on 0.2.0.x):
1582 - Fix a bug with AutomapHostsOnResolve that would always cause
1583 the second request to fail. Bug reported by Kate. Bugfix on
1585 - Fix a bug in ADDRMAP controller replies that would sometimes
1586 try to print a NULL. Patch from tup.
1587 - Read v3 directory authority keys from the right location.
1588 - Numerous bugfixes to directory voting code.
1591 Changes in version 0.1.2.16 - 2007-08-01
1592 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
1593 remote attacker in certain situations to rewrite the user's torrc
1594 configuration file. This can completely compromise anonymity of users
1595 in most configurations, including those running the Vidalia bundles,
1596 TorK, etc. Or worse.
1598 o Major security fixes:
1599 - Close immediately after missing authentication on control port;
1600 do not allow multiple authentication attempts.
1603 Changes in version 0.2.0.4-alpha - 2007-08-01
1604 This fourth development snapshot fixes a critical security vulnerability
1605 for most users, specifically those running Vidalia, TorK, etc. Everybody
1606 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
1608 o Major security fixes:
1609 - Close immediately after missing authentication on control port;
1610 do not allow multiple authentication attempts.
1612 o Major bugfixes (compilation):
1613 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
1616 o Minor features (performance):
1617 - Be even more aggressive about releasing RAM from small
1618 empty buffers. Thanks to our free-list code, this shouldn't be too
1619 performance-intensive.
1620 - Disable sentinel-based debugging for buffer code: we squashed all
1621 the bugs that this was supposed to detect a long time ago, and
1622 now its only effect is to change our buffer sizes from nice
1623 powers of two (which platform mallocs tend to like) to values
1624 siightly over powers of two (which make some platform mallocs sad).
1625 - Log malloc statistics from mallinfo() on platforms where it
1629 Changes in version 0.2.0.3-alpha - 2007-07-29
1630 This third development snapshot introduces new experimental
1631 blocking-resistance features and a preliminary version of the v3
1632 directory voting design, and includes many other smaller features
1636 - The first pieces of our "bridge" design for blocking-resistance
1637 are implemented. People can run bridge directory authorities;
1638 people can run bridges; and people can configure their Tor clients
1639 with a set of bridges to use as the first hop into the Tor network.
1640 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
1642 - Create listener connections before we setuid to the configured
1643 User and Group. Now non-Windows users can choose port values
1644 under 1024, start Tor as root, and have Tor bind those ports
1645 before it changes to another UID. (Windows users could already
1647 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
1648 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
1649 on "vserver" accounts. (Patch from coderman.)
1650 - Be even more aggressive about separating local traffic from relayed
1651 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
1653 o Major features (experimental):
1654 - First cut of code for "v3 dir voting": directory authorities will
1655 vote on a common network status document rather than each publishing
1656 their own opinion. This code needs more testing and more corner-case
1657 handling before it's ready for use.
1660 - Directory authorities now call routers Fast if their bandwidth is
1661 at least 100KB/s, and consider their bandwidth adequate to be a
1662 Guard if it is at least 250KB/s, no matter the medians. This fix
1663 complements proposal 107. [Bugfix on 0.1.2.x]
1664 - Directory authorities now never mark more than 3 servers per IP as
1665 Valid and Running. (Implements proposal 109, by Kevin Bauer and
1667 - Minor change to organizationName and commonName generation
1668 procedures in TLS certificates during Tor handshakes, to invalidate
1669 some earlier censorware approaches. This is not a long-term
1670 solution, but applying it will give us a bit of time to look into
1671 the epidemiology of countermeasures as they spread.
1673 o Major bugfixes (directory):
1674 - Rewrite directory tokenization code to never run off the end of
1675 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
1677 o Minor features (controller):
1678 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
1679 match requests to applications. (Patch from Robert Hogan.)
1680 - Report address and port correctly on connections to DNSPort. (Patch
1682 - Add a RESOLVE command to launch hostname lookups. (Original patch
1684 - Add GETINFO status/enough-dir-info to let controllers tell whether
1685 Tor has downloaded sufficient directory information. (Patch
1687 - You can now use the ControlSocket option to tell Tor to listen for
1688 controller connections on Unix domain sockets on systems that
1689 support them. (Patch from Peter Palfrader.)
1690 - STREAM NEW events are generated for DNSPort requests and for
1691 tunneled directory connections. (Patch from Robert Hogan.)
1692 - New "GETINFO address-mappings/*" command to get address mappings
1693 with expiry information. "addr-mappings/*" is now deprecated.
1696 o Minor features (misc):
1697 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
1699 - The tor-gencert tool for v3 directory authorities now creates all
1700 files as readable to the file creator only, and write-protects
1701 the authority identity key.
1702 - When dumping memory usage, list bytes used in buffer memory
1704 - When running with dmalloc, dump more stats on hup and on exit.
1705 - Directory authorities now fail quickly and (relatively) harmlessly
1706 if they generate a network status document that is somehow
1709 o Traffic load balancing improvements:
1710 - If exit bandwidth ever exceeds one third of total bandwidth, then
1711 use the correct formula to weight exit nodes when choosing paths.
1712 (Based on patch from Mike Perry.)
1713 - Choose perfectly fairly among routers when choosing by bandwidth and
1714 weighting by fraction of bandwidth provided by exits. Previously, we
1715 would choose with only approximate fairness, and correct ourselves
1716 if we ran off the end of the list. [Bugfix on 0.1.2.x]
1718 o Performance improvements:
1719 - Be more aggressive with freeing buffer RAM or putting it on the
1721 - Use Critical Sections rather than Mutexes for synchronizing threads
1722 on win32; Mutexes are heavier-weight, and designed for synchronizing
1725 o Deprecated and removed features:
1726 - RedirectExits is now deprecated.
1727 - Stop allowing address masks that do not correspond to bit prefixes.
1728 We have warned about these for a really long time; now it's time
1729 to reject them. (Patch from croup.)
1731 o Minor bugfixes (directory):
1732 - Fix another crash bug related to extra-info caching. (Bug found by
1733 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
1734 - Directories no longer return a "304 not modified" when they don't
1735 have the networkstatus the client asked for. Also fix a memory
1736 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
1737 - We had accidentally labelled 0.1.2.x directory servers as not
1738 suitable for begin_dir requests, and had labelled no directory
1739 servers as suitable for uploading extra-info documents. [Bugfix
1742 o Minor bugfixes (dns):
1743 - Fix a crash when DNSPort is set more than once. (Patch from Robert
1744 Hogan.) [Bugfix on 0.2.0.2-alpha]
1745 - Add DNSPort connections to the global connection list, so that we
1746 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
1748 - Fix a dangling reference that could lead to a crash when DNSPort is
1749 changed or closed (Patch from Robert Hogan.) [Bugfix on
1752 o Minor bugfixes (controller):
1753 - Provide DNS expiry times in GMT, not in local time. For backward
1754 compatibility, ADDRMAP events only provide GMT expiry in an extended
1755 field. "GETINFO address-mappings" always does the right thing.
1756 - Use CRLF line endings properly in NS events.
1757 - Terminate multi-line control events properly. (Original patch
1758 from tup.) [Bugfix on 0.1.2.x-alpha]
1759 - Do not include spaces in SOURCE_ADDR fields in STREAM
1760 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
1763 Changes in version 0.1.2.15 - 2007-07-17
1764 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
1765 problems, fixes compilation on BSD, and fixes a variety of other
1766 bugs. Everybody should upgrade.
1768 o Major bugfixes (compilation):
1769 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
1771 o Major bugfixes (crashes):
1772 - Try even harder not to dereference the first character after
1773 an mmap(). Reported by lodger.
1774 - Fix a crash bug in directory authorities when we re-number the
1775 routerlist while inserting a new router.
1776 - When the cached-routers file is an even multiple of the page size,
1777 don't run off the end and crash. (Fixes bug 455; based on idea
1779 - Fix eventdns.c behavior on Solaris: It is critical to include
1780 orconfig.h _before_ sys/types.h, so that we can get the expected
1781 definition of _FILE_OFFSET_BITS.
1783 o Major bugfixes (security):
1784 - Fix a possible buffer overrun when using BSD natd support. Bug
1786 - When sending destroy cells from a circuit's origin, don't include
1787 the reason for tearing down the circuit. The spec says we didn't,
1788 and now we actually don't. Reported by lodger.
1789 - Keep streamids from different exits on a circuit separate. This
1790 bug may have allowed other routers on a given circuit to inject
1791 cells into streams. Reported by lodger; fixes bug 446.
1792 - If there's a never-before-connected-to guard node in our list,
1793 never choose any guards past it. This way we don't expand our
1794 guard list unless we need to.
1796 o Minor bugfixes (guard nodes):
1797 - Weight guard selection by bandwidth, so that low-bandwidth nodes
1798 don't get overused as guards.
1800 o Minor bugfixes (directory):
1801 - Correctly count the number of authorities that recommend each
1802 version. Previously, we were under-counting by 1.
1803 - Fix a potential crash bug when we load many server descriptors at
1804 once and some of them make others of them obsolete. Fixes bug 458.
1806 o Minor bugfixes (hidden services):
1807 - Stop tearing down the whole circuit when the user asks for a
1808 connection to a port that the hidden service didn't configure.
1811 o Minor bugfixes (misc):
1812 - On Windows, we were preventing other processes from reading
1813 cached-routers while Tor was running. Reported by janbar.
1814 - Fix a possible (but very unlikely) bug in picking routers by
1815 bandwidth. Add a log message to confirm that it is in fact
1816 unlikely. Patch from lodger.
1817 - Backport a couple of memory leak fixes.
1818 - Backport miscellaneous cosmetic bugfixes.
1821 Changes in version 0.2.0.2-alpha - 2007-06-02
1822 o Major bugfixes on 0.2.0.1-alpha:
1823 - Fix an assertion failure related to servers without extra-info digests.
1824 Resolves bugs 441 and 442.
1826 o Minor features (directory):
1827 - Support "If-Modified-Since" when answering HTTP requests for
1828 directories, running-routers documents, and network-status documents.
1829 (There's no need to support it for router descriptors, since those
1830 are downloaded by descriptor digest.)
1832 o Minor build issues:
1833 - Clear up some MIPSPro compiler warnings.
1834 - When building from a tarball on a machine that happens to have SVK
1835 installed, report the micro-revision as whatever version existed
1836 in the tarball, not as "x".
1839 Changes in version 0.2.0.1-alpha - 2007-06-01
1840 This early development snapshot provides new features for people running
1841 Tor as both a client and a server (check out the new RelayBandwidth
1842 config options); lets Tor run as a DNS proxy; and generally moves us
1843 forward on a lot of fronts.
1845 o Major features, server usability:
1846 - New config options RelayBandwidthRate and RelayBandwidthBurst:
1847 a separate set of token buckets for relayed traffic. Right now
1848 relayed traffic is defined as answers to directory requests, and
1849 OR connections that don't have any local circuits on them.
1851 o Major features, client usability:
1852 - A client-side DNS proxy feature to replace the need for
1853 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
1854 for DNS requests on port 9999, use the Tor network to resolve them
1855 anonymously, and send the reply back like a regular DNS server.
1856 The code still only implements a subset of DNS.
1857 - Make PreferTunneledDirConns and TunnelDirConns work even when
1858 we have no cached directory info. This means Tor clients can now
1859 do all of their connections protected by TLS.
1861 o Major features, performance and efficiency:
1862 - Directory authorities accept and serve "extra info" documents for
1863 routers. These documents contain fields from router descriptors
1864 that aren't usually needed, and that use a lot of excess
1865 bandwidth. Once these fields are removed from router descriptors,
1866 the bandwidth savings should be about 60%. [Partially implements
1868 - Servers upload extra-info documents to any authority that accepts
1869 them. Authorities (and caches that have been configured to download
1870 extra-info documents) download them as needed. [Partially implements
1872 - Change the way that Tor buffers data that it is waiting to write.
1873 Instead of queueing data cells in an enormous ring buffer for each
1874 client->OR or OR->OR connection, we now queue cells on a separate
1875 queue for each circuit. This lets us use less slack memory, and
1876 will eventually let us be smarter about prioritizing different kinds
1878 - Use memory pools to allocate cells with better speed and memory
1879 efficiency, especially on platforms where malloc() is inefficient.
1880 - Stop reading on edge connections when their corresponding circuit
1881 buffers are full; start again as the circuits empty out.
1883 o Major features, other:
1884 - Add an HSAuthorityRecordStats option that hidden service authorities
1885 can use to track statistics of overall hidden service usage without
1886 logging information that would be very useful to an attacker.
1887 - Start work implementing multi-level keys for directory authorities:
1888 Add a standalone tool to generate key certificates. (Proposal 103.)
1891 - Directory authorities now call routers Stable if they have an
1892 uptime of at least 30 days, even if that's not the median uptime
1893 in the network. Implements proposal 107, suggested by Kevin Bauer
1896 o Minor fixes (resource management):
1897 - Count the number of open sockets separately from the number
1898 of active connection_t objects. This will let us avoid underusing
1899 our allocated connection limit.
1900 - We no longer use socket pairs to link an edge connection to an
1901 anonymous directory connection or a DirPort test connection.
1902 Instead, we track the link internally and transfer the data
1903 in-process. This saves two sockets per "linked" connection (at the
1904 client and at the server), and avoids the nasty Windows socketpair()
1906 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
1907 for every single inactive connection_t. Free items from the
1908 4k/16k-buffer free lists when they haven't been used for a while.
1910 o Minor features (build):
1911 - Make autoconf search for libevent, openssl, and zlib consistently.
1912 - Update deprecated macros in configure.in.
1913 - When warning about missing headers, tell the user to let us
1914 know if the compile succeeds anyway, so we can downgrade the
1916 - Include the current subversion revision as part of the version
1917 string: either fetch it directly if we're in an SVN checkout, do
1918 some magic to guess it if we're in an SVK checkout, or use
1919 the last-detected version if we're building from a .tar.gz.
1920 Use this version consistently in log messages.
1922 o Minor features (logging):
1923 - Always prepend "Bug: " to any log message about a bug.
1924 - Put a platform string (e.g. "Linux i686") in the startup log
1925 message, so when people paste just their logs, we know if it's
1926 OpenBSD or Windows or what.
1927 - When logging memory usage, break down memory used in buffers by
1930 o Minor features (directory system):
1931 - New config option V2AuthoritativeDirectory that all directory
1932 authorities should set. This will let future authorities choose
1933 not to serve V2 directory information.
1934 - Directory authorities allow multiple router descriptors and/or extra
1935 info documents to be uploaded in a single go. This will make
1936 implementing proposal 104 simpler.
1938 o Minor features (controller):
1939 - Add a new config option __DisablePredictedCircuits designed for
1940 use by the controller, when we don't want Tor to build any circuits
1942 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
1943 so we can exit from the middle of the circuit.
1944 - Implement "getinfo status/circuit-established".
1945 - Implement "getinfo status/version/..." so a controller can tell
1946 whether the current version is recommended, and whether any versions
1947 are good, and how many authorities agree. (Patch from shibz.)
1949 o Minor features (hidden services):
1950 - Allow multiple HiddenServicePort directives with the same virtual
1951 port; when they occur, the user is sent round-robin to one
1952 of the target ports chosen at random. Partially fixes bug 393 by
1953 adding limited ad-hoc round-robining.
1955 o Minor features (other):
1957 - Add a new AutomapHostsOnResolve option: when it is enabled, any
1958 resolve request for hosts matching a given pattern causes Tor to
1959 generate an internal virtual address mapping for that host. This
1960 allows DNSPort to work sensibly with hidden service users. By
1961 default, .exit and .onion addresses are remapped; the list of
1962 patterns can be reconfigured with AutomapHostsSuffixes.
1963 - Add an "-F" option to tor-resolve to force a resolve for a .onion
1964 address. Thanks to the AutomapHostsOnResolve option, this is no
1965 longer a completely silly thing to do.
1966 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
1967 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
1968 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
1969 minus 1 byte: the actual maximum declared bandwidth.
1972 - Removed support for the old binary "version 0" controller protocol.
1973 This has been deprecated since 0.1.1, and warnings have been issued
1974 since 0.1.2. When we encounter a v0 control message, we now send
1975 back an error and close the connection.
1976 - Remove the old "dns worker" server DNS code: it hasn't been default
1977 since 0.1.2.2-alpha, and all the servers seem to be using the new
1980 o Minor bugfixes (portability):
1981 - Even though Windows is equally happy with / and \ as path separators,
1982 try to use \ consistently on Windows and / consistently on Unix: it
1983 makes the log messages nicer.
1984 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
1985 - Read resolv.conf files correctly on platforms where read() returns
1986 partial results on small file reads.
1988 o Minor bugfixes (directory):
1989 - Correctly enforce that elements of directory objects do not appear
1990 more often than they are allowed to appear.
1991 - When we are reporting the DirServer line we just parsed, we were
1992 logging the second stanza of the key fingerprint, not the first.
1994 o Minor bugfixes (logging):
1995 - When we hit an EOF on a log (probably because we're shutting down),
1996 don't try to remove the log from the list: just mark it as
1997 unusable. (Bulletproofs against bug 222.)
1999 o Minor bugfixes (other):
2000 - In the exitlist script, only consider the most recently published
2001 server descriptor for each server. Also, when the user requests
2002 a list of servers that _reject_ connections to a given address,
2003 explicitly exclude the IPs that also have servers that accept
2004 connections to that address. (Resolves bug 405.)
2005 - Stop allowing hibernating servers to be "stable" or "fast".
2006 - On Windows, we were preventing other processes from reading
2007 cached-routers while Tor was running. (Reported by janbar)
2008 - Make the NodeFamilies config option work. (Reported by
2009 lodger -- it has never actually worked, even though we added it
2011 - Check return values from pthread_mutex functions.
2012 - Don't save non-general-purpose router descriptors to the disk cache,
2013 because we have no way of remembering what their purpose was when
2015 - Add even more asserts to hunt down bug 417.
2016 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
2017 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
2018 Add a log message to confirm that it is in fact unlikely.
2020 o Minor bugfixes (controller):
2021 - Make 'getinfo fingerprint' return a 551 error if we're not a
2022 server, so we match what the control spec claims we do. Reported
2024 - Fix a typo in an error message when extendcircuit fails that
2025 caused us to not follow the \r\n-based delimiter protocol. Reported
2028 o Code simplifications and refactoring:
2029 - Stop passing around circuit_t and crypt_path_t pointers that are
2030 implicit in other procedure arguments.
2031 - Drop the old code to choke directory connections when the
2032 corresponding OR connections got full: thanks to the cell queue
2033 feature, OR conns don't get full any more.
2034 - Make dns_resolve() handle attaching connections to circuits
2035 properly, so the caller doesn't have to.
2036 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
2037 - Keep the connection array as a dynamic smartlist_t, rather than as
2038 a fixed-sized array. This is important, as the number of connections
2039 is becoming increasingly decoupled from the number of sockets.
2042 Changes in version 0.1.2.14 - 2007-05-25
2043 Tor 0.1.2.14 changes the addresses of two directory authorities (this
2044 change especially affects those who serve or use hidden services),
2045 and fixes several other crash- and security-related bugs.
2047 o Directory authority changes:
2048 - Two directory authorities (moria1 and moria2) just moved to new
2049 IP addresses. This change will particularly affect those who serve
2050 or use hidden services.
2052 o Major bugfixes (crashes):
2053 - If a directory server runs out of space in the connection table
2054 as it's processing a begin_dir request, it will free the exit stream
2055 but leave it attached to the circuit, leading to unpredictable
2056 behavior. (Reported by seeess, fixes bug 425.)
2057 - Fix a bug in dirserv_remove_invalid() that would cause authorities
2058 to corrupt memory under some really unlikely scenarios.
2059 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
2060 - Avoid segfaults when reading from mmaped descriptor file. (Reported
2063 o Major bugfixes (security):
2064 - When choosing an entry guard for a circuit, avoid using guards
2065 that are in the same family as the chosen exit -- not just guards
2066 that are exactly the chosen exit. (Reported by lodger.)
2068 o Major bugfixes (resource management):
2069 - If a directory authority is down, skip it when deciding where to get
2070 networkstatus objects or descriptors. Otherwise we keep asking
2071 every 10 seconds forever. Fixes bug 384.
2072 - Count it as a failure if we fetch a valid network-status but we
2073 don't want to keep it. Otherwise we'll keep fetching it and keep
2074 not wanting to keep it. Fixes part of bug 422.
2075 - If all of our dirservers have given us bad or no networkstatuses
2076 lately, then stop hammering them once per minute even when we
2077 think they're failed. Fixes another part of bug 422.
2080 - Actually set the purpose correctly for descriptors inserted with
2082 - When we have k non-v2 authorities in our DirServer config,
2083 we ignored the last k authorities in the list when updating our
2085 - Correctly back-off from requesting router descriptors that we are
2086 having a hard time downloading.
2087 - Read resolv.conf files correctly on platforms where read() returns
2088 partial results on small file reads.
2089 - Don't rebuild the entire router store every time we get 32K of
2090 routers: rebuild it when the journal gets very large, or when
2091 the gaps in the store get very large.
2094 - When routers publish SVN revisions in their router descriptors,
2095 authorities now include those versions correctly in networkstatus
2097 - Warn when using a version of libevent before 1.3b to run a server on
2098 OSX or BSD: these versions interact badly with userspace threads.
2101 Changes in version 0.1.2.13 - 2007-04-24
2102 This release features some major anonymity fixes, such as safer path
2103 selection; better client performance; faster bootstrapping, better
2104 address detection, and better DNS support for servers; write limiting as
2105 well as read limiting to make servers easier to run; and a huge pile of
2106 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
2108 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
2109 of the Freenode IRC network, remembering his patience and vision for
2110 free speech on the Internet.
2113 - Fix a memory leak when we ask for "all" networkstatuses and we
2114 get one we don't recognize.
2115 - Add more asserts to hunt down bug 417.
2116 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
2119 Changes in version 0.1.2.12-rc - 2007-03-16
2121 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
2122 directory information requested inside Tor connections (i.e. via
2123 begin_dir cells). It only triggered when the same connection was
2124 serving other data at the same time. Reported by seeess.
2127 - When creating a circuit via the controller, send a 'launched'
2128 event when we're done, so we follow the spec better.
2131 Changes in version 0.1.2.11-rc - 2007-03-15
2132 o Minor bugfixes (controller), reported by daejees:
2133 - Correct the control spec to match how the code actually responds
2134 to 'getinfo addr-mappings/*'.
2135 - The control spec described a GUARDS event, but the code
2136 implemented a GUARD event. Standardize on GUARD, but let people
2140 Changes in version 0.1.2.10-rc - 2007-03-07
2141 o Major bugfixes (Windows):
2142 - Do not load the NT services library functions (which may not exist)
2143 just to detect if we're a service trying to shut down. Now we run
2144 on Win98 and friends again.
2146 o Minor bugfixes (other):
2147 - Clarify a couple of log messages.
2148 - Fix a misleading socks5 error number.
2151 Changes in version 0.1.2.9-rc - 2007-03-02
2152 o Major bugfixes (Windows):
2153 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
2154 of the usual GCC "%llu". This prevents a bug when saving 64-bit
2155 int configuration values: the high-order 32 bits would get
2156 truncated. In particular, we were being bitten by the default
2157 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
2158 and maybe also bug 397.)
2160 o Minor bugfixes (performance):
2161 - Use OpenSSL's AES implementation on platforms where it's faster.
2162 This could save us as much as 10% CPU usage.
2164 o Minor bugfixes (server):
2165 - Do not rotate onion key immediately after setting it for the first
2168 o Minor bugfixes (directory authorities):
2169 - Stop calling servers that have been hibernating for a long time
2170 "stable". Also, stop letting hibernating or obsolete servers affect
2171 uptime and bandwidth cutoffs.
2172 - Stop listing hibernating servers in the v1 directory.
2174 o Minor bugfixes (hidden services):
2175 - Upload hidden service descriptors slightly less often, to reduce
2176 load on authorities.
2178 o Minor bugfixes (other):
2179 - Fix an assert that could trigger if a controller quickly set then
2180 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
2181 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
2183 - Fix a potential race condition in the rpm installer. Found by
2185 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
2186 of 2 as indicating that the server is completely bad; it sometimes
2187 means that the server is just bad for the request in question. (may fix
2188 the last of bug 326.)
2189 - Disable encrypted directory connections when we don't have a server
2190 descriptor for the destination. We'll get this working again in
2194 Changes in version 0.1.2.8-beta - 2007-02-26
2195 o Major bugfixes (crashes):
2196 - Stop crashing when the controller asks us to resetconf more than
2197 one config option at once. (Vidalia 0.0.11 does this.)
2198 - Fix a crash that happened on Win98 when we're given command-line
2199 arguments: don't try to load NT service functions from advapi32.dll
2200 except when we need them. (Bug introduced in 0.1.2.7-alpha;
2202 - Fix a longstanding obscure crash bug that could occur when
2203 we run out of DNS worker processes. (Resolves bug 390.)
2205 o Major bugfixes (hidden services):
2206 - Correctly detect whether hidden service descriptor downloads are
2207 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
2209 o Major bugfixes (accounting):
2210 - When we start during an accounting interval before it's time to wake
2211 up, remember to wake up at the correct time. (May fix bug 342.)
2213 o Minor bugfixes (controller):
2214 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
2215 clear the corresponding on_circuit variable, and remember later
2216 that we don't need to send a redundant CLOSED event. (Resolves part
2218 - Report events where a resolve succeeded or where we got a socks
2219 protocol error correctly, rather than calling both of them
2221 - Change reported stream target addresses to IP consistently when
2222 we finally get the IP from an exit node.
2223 - Send log messages to the controller even if they happen to be very
2226 o Minor bugfixes (other):
2227 - Display correct results when reporting which versions are
2228 recommended, and how recommended they are. (Resolves bug 383.)
2229 - Improve our estimates for directory bandwidth to be less random:
2230 guess that an unrecognized directory will have the average bandwidth
2231 from all known directories, not that it will have the average
2232 bandwidth from those directories earlier than it on the list.
2233 - If we start a server with ClientOnly 1, then set ClientOnly to 0
2234 and hup, stop triggering an assert based on an empty onion_key.
2235 - On platforms with no working mmap() equivalent, don't warn the
2236 user when cached-routers doesn't exist.
2237 - Warn the user when mmap() [or its equivalent] fails for some reason
2238 other than file-not-found.
2239 - Don't warn the user when cached-routers.new doesn't exist: that's
2240 perfectly fine when starting up for the first time.
2241 - When EntryNodes are configured, rebuild the guard list to contain,
2242 in order: the EntryNodes that were guards before; the rest of the
2243 EntryNodes; the nodes that were guards before.
2244 - Mask out all signals in sub-threads; only the libevent signal
2245 handler should be processing them. This should prevent some crashes
2246 on some machines using pthreads. (Patch from coderman.)
2247 - Fix switched arguments on memset in the implementation of
2248 tor_munmap() for systems with no mmap() call.
2249 - When Tor receives a router descriptor that it asked for, but
2250 no longer wants (because it has received fresh networkstatuses
2251 in the meantime), do not warn the user. Cache the descriptor if
2252 we're a cache; drop it if we aren't.
2253 - Make earlier entry guards _really_ get retried when the network
2255 - On a malformed DNS reply, always give an error to the corresponding
2257 - Build with recent libevents on platforms that do not define the
2258 nonstandard types "u_int8_t" and friends.
2260 o Minor features (controller):
2261 - Warn the user when an application uses the obsolete binary v0
2262 control protocol. We're planning to remove support for it during
2263 the next development series, so it's good to give people some
2265 - Add STREAM_BW events to report per-entry-stream bandwidth
2266 use. (Patch from Robert Hogan.)
2267 - Rate-limit SIGNEWNYM signals in response to controllers that
2268 impolitely generate them for every single stream. (Patch from
2269 mwenge; closes bug 394.)
2270 - Make REMAP stream events have a SOURCE (cache or exit), and
2271 make them generated in every case where we get a successful
2272 connected or resolved cell.
2274 o Minor bugfixes (performance):
2275 - Call router_have_min_dir_info half as often. (This is showing up in
2276 some profiles, but not others.)
2277 - When using GCC, make log_debug never get called at all, and its
2278 arguments never get evaluated, when no debug logs are configured.
2279 (This is showing up in some profiles, but not others.)
2282 - Remove some never-implemented options. Mark PathlenCoinWeight as
2284 - Implement proposal 106: Stop requiring clients to have well-formed
2285 certificates; stop checking nicknames in certificates. (Clients
2286 have certificates so that they can look like Tor servers, but in
2287 the future we might want to allow them to look like regular TLS
2288 clients instead. Nicknames in certificates serve no purpose other
2289 than making our protocol easier to recognize on the wire.)
2290 - Revise messages on handshake failure again to be even more clear about
2291 which are incoming connections and which are outgoing.
2292 - Discard any v1 directory info that's over 1 month old (for
2293 directories) or over 1 week old (for running-routers lists).
2294 - Do not warn when individual nodes in the configuration's EntryNodes,
2295 ExitNodes, etc are down: warn only when all possible nodes
2296 are down. (Fixes bug 348.)
2297 - Always remove expired routers and networkstatus docs before checking
2298 whether we have enough information to build circuits. (Fixes
2300 - Put a lower-bound on MaxAdvertisedBandwidth.
2303 Changes in version 0.1.2.7-alpha - 2007-02-06
2304 o Major bugfixes (rate limiting):
2305 - Servers decline directory requests much more aggressively when
2306 they're low on bandwidth. Otherwise they end up queueing more and
2307 more directory responses, which can't be good for latency.
2308 - But never refuse directory requests from local addresses.
2309 - Fix a memory leak when sending a 503 response for a networkstatus
2311 - Be willing to read or write on local connections (e.g. controller
2312 connections) even when the global rate limiting buckets are empty.
2313 - If our system clock jumps back in time, don't publish a negative
2314 uptime in the descriptor. Also, don't let the global rate limiting
2315 buckets go absurdly negative.
2316 - Flush local controller connection buffers periodically as we're
2317 writing to them, so we avoid queueing 4+ megabytes of data before
2320 o Major bugfixes (NT services):
2321 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
2322 command-line flag so that admins can override the default by saying
2323 "tor --service install --user "SomeUser"". This will not affect
2324 existing installed services. Also, warn the user that the service
2325 will look for its configuration file in the service user's
2326 %appdata% directory. (We can't do the 'hardwire the user's appdata
2327 directory' trick any more, since we may not have read access to that
2330 o Major bugfixes (other):
2331 - Previously, we would cache up to 16 old networkstatus documents
2332 indefinitely, if they came from nontrusted authorities. Now we
2333 discard them if they are more than 10 days old.
2334 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
2336 - Detect and reject malformed DNS responses containing circular
2338 - If exits are rare enough that we're not marking exits as guards,
2339 ignore exit bandwidth when we're deciding the required bandwidth
2341 - When we're handling a directory connection tunneled over Tor,
2342 don't fill up internal memory buffers with all the data we want
2343 to tunnel; instead, only add it if the OR connection that will
2344 eventually receive it has some room for it. (This can lead to
2345 slowdowns in tunneled dir connections; a better solution will have
2348 o Minor bugfixes (dns):
2349 - Add some defensive programming to eventdns.c in an attempt to catch
2350 possible memory-stomping bugs.
2351 - Detect and reject DNS replies containing IPv4 or IPv6 records with
2352 an incorrect number of bytes. (Previously, we would ignore the
2354 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
2355 in the correct order, and doesn't crash.
2356 - Free memory held in recently-completed DNS lookup attempts on exit.
2357 This was not a memory leak, but may have been hiding memory leaks.
2358 - Handle TTL values correctly on reverse DNS lookups.
2359 - Treat failure to parse resolv.conf as an error.
2361 o Minor bugfixes (other):
2362 - Fix crash with "tor --list-fingerprint" (reported by seeess).
2363 - When computing clock skew from directory HTTP headers, consider what
2364 time it was when we finished asking for the directory, not what
2366 - Expire socks connections if they spend too long waiting for the
2367 handshake to finish. Previously we would let them sit around for
2368 days, if the connecting application didn't close them either.
2369 - And if the socks handshake hasn't started, don't send a
2370 "DNS resolve socks failed" handshake reply; just close it.
2371 - Stop using C functions that OpenBSD's linker doesn't like.
2372 - Don't launch requests for descriptors unless we have networkstatuses
2373 from at least half of the authorities. This delays the first
2374 download slightly under pathological circumstances, but can prevent
2375 us from downloading a bunch of descriptors we don't need.
2376 - Do not log IPs with TLS failures for incoming TLS
2377 connections. (Fixes bug 382.)
2378 - If the user asks to use invalid exit nodes, be willing to use
2380 - Stop using the reserved ac_cv namespace in our configure script.
2381 - Call stat() slightly less often; use fstat() when possible.
2382 - Refactor the way we handle pending circuits when an OR connection
2383 completes or fails, in an attempt to fix a rare crash bug.
2384 - Only rewrite a conn's address based on X-Forwarded-For: headers
2385 if it's a parseable public IP address; and stop adding extra quotes
2386 to the resulting address.
2389 - Weight directory requests by advertised bandwidth. Now we can
2390 let servers enable write limiting but still allow most clients to
2391 succeed at their directory requests. (We still ignore weights when
2392 choosing a directory authority; I hope this is a feature.)
2395 - Create a new file ReleaseNotes which was the old ChangeLog. The
2396 new ChangeLog file now includes the summaries for all development
2398 - Check for addresses with invalid characters at the exit as well
2399 as at the client, and warn less verbosely when they fail. You can
2400 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
2401 - Adapt a patch from goodell to let the contrib/exitlist script
2402 take arguments rather than require direct editing.
2403 - Inform the server operator when we decide not to advertise a
2404 DirPort due to AccountingMax enabled or a low BandwidthRate. It
2405 was confusing Zax, so now we're hopefully more helpful.
2406 - Bring us one step closer to being able to establish an encrypted
2407 directory tunnel without knowing a descriptor first. Still not
2408 ready yet. As part of the change, now assume we can use a
2409 create_fast cell if we don't know anything about a router.
2410 - Allow exit nodes to use nameservers running on ports other than 53.
2411 - Servers now cache reverse DNS replies.
2412 - Add an --ignore-missing-torrc command-line option so that we can
2413 get the "use sensible defaults if the configuration file doesn't
2414 exist" behavior even when specifying a torrc location on the command
2417 o Minor features (controller):
2418 - Track reasons for OR connection failure; make these reasons
2419 available via the controller interface. (Patch from Mike Perry.)
2420 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
2421 can learn when clients are sending malformed hostnames to Tor.
2422 - Clean up documentation for controller status events.
2423 - Add a REMAP status to stream events to note that a stream's
2424 address has changed because of a cached address or a MapAddress
2428 Changes in version 0.1.2.6-alpha - 2007-01-09
2430 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
2431 connection handles more than 4 gigs in either direction, we crash.
2432 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
2433 advertised exit node, somebody might try to exit from us when
2434 we're bootstrapping and before we've built our descriptor yet.
2435 Refuse the connection rather than crashing.
2438 - Warn if we (as a server) find that we've resolved an address that we
2439 weren't planning to resolve.
2440 - Warn that using select() on any libevent version before 1.1 will be
2441 unnecessarily slow (even for select()).
2442 - Flush ERR-level controller status events just like we currently
2443 flush ERR-level log events, so that a Tor shutdown doesn't prevent
2444 the controller from learning about current events.
2446 o Minor features (more controller status events):
2447 - Implement EXTERNAL_ADDRESS server status event so controllers can
2448 learn when our address changes.
2449 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
2450 can learn when directories reject our descriptor.
2451 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
2452 can learn when a client application is speaking a non-socks protocol
2454 - Implement DANGEROUS_SOCKS client status event so controllers
2455 can learn when a client application is leaking DNS addresses.
2456 - Implement BUG general status event so controllers can learn when
2457 Tor is unhappy about its internal invariants.
2458 - Implement CLOCK_SKEW general status event so controllers can learn
2459 when Tor thinks the system clock is set incorrectly.
2460 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
2461 server status events so controllers can learn when their descriptors
2462 are accepted by a directory.
2463 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
2464 server status events so controllers can learn about Tor's progress in
2465 deciding whether it's reachable from the outside.
2466 - Implement BAD_LIBEVENT general status event so controllers can learn
2467 when we have a version/method combination in libevent that needs to
2469 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
2470 and DNS_USELESS server status events so controllers can learn
2471 about changes to DNS server status.
2473 o Minor features (directory):
2474 - Authorities no longer recommend exits as guards if this would shift
2475 too much load to the exit nodes.
2478 Changes in version 0.1.2.5-alpha - 2007-01-06
2480 - Enable write limiting as well as read limiting. Now we sacrifice
2481 capacity if we're pushing out lots of directory traffic, rather
2482 than overrunning the user's intended bandwidth limits.
2483 - Include TLS overhead when counting bandwidth usage; previously, we
2484 would count only the bytes sent over TLS, but not the bytes used
2486 - Support running the Tor service with a torrc not in the same
2487 directory as tor.exe and default to using the torrc located in
2488 the %appdata%\Tor\ of the user who installed the service. Patch
2490 - Servers now check for the case when common DNS requests are going to
2491 wildcarded addresses (i.e. all getting the same answer), and change
2492 their exit policy to reject *:* if it's happening.
2493 - Implement BEGIN_DIR cells, so we can connect to the directory
2494 server via TLS to do encrypted directory requests rather than
2495 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
2496 config options if you like.
2498 o Minor features (config and docs):
2499 - Start using the state file to store bandwidth accounting data:
2500 the bw_accounting file is now obsolete. We'll keep generating it
2501 for a while for people who are still using 0.1.2.4-alpha.
2502 - Try to batch changes to the state file so that we do as few
2503 disk writes as possible while still storing important things in
2505 - The state file and the bw_accounting file get saved less often when
2506 the AvoidDiskWrites config option is set.
2507 - Make PIDFile work on Windows (untested).
2508 - Add internal descriptions for a bunch of configuration options:
2509 accessible via controller interface and in comments in saved
2511 - Reject *:563 (NNTPS) in the default exit policy. We already reject
2512 NNTP by default, so this seems like a sensible addition.
2513 - Clients now reject hostnames with invalid characters. This should
2514 avoid some inadvertent info leaks. Add an option
2515 AllowNonRFC953Hostnames to disable this behavior, in case somebody
2516 is running a private network with hosts called @, !, and #.
2517 - Add a maintainer script to tell us which options are missing
2518 documentation: "make check-docs".
2519 - Add a new address-spec.txt document to describe our special-case
2520 addresses: .exit, .onion, and .noconnnect.
2522 o Minor features (DNS):
2523 - Ongoing work on eventdns infrastructure: now it has dns server
2524 and ipv6 support. One day Tor will make use of it.
2525 - Add client-side caching for reverse DNS lookups.
2526 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
2527 - When we change nameservers or IP addresses, reset and re-launch
2528 our tests for DNS hijacking.
2530 o Minor features (directory):
2531 - Authorities now specify server versions in networkstatus. This adds
2532 about 2% to the size of compressed networkstatus docs, and allows
2533 clients to tell which servers support BEGIN_DIR and which don't.
2534 The implementation is forward-compatible with a proposed future
2535 protocol version scheme not tied to Tor versions.
2536 - DirServer configuration lines now have an orport= option so
2537 clients can open encrypted tunnels to the authorities without
2538 having downloaded their descriptors yet. Enabled for moria1,
2539 moria2, tor26, and lefkada now in the default configuration.
2540 - Directory servers are more willing to send a 503 "busy" if they
2541 are near their write limit, especially for v1 directory requests.
2542 Now they can use their limited bandwidth for actual Tor traffic.
2543 - Clients track responses with status 503 from dirservers. After a
2544 dirserver has given us a 503, we try not to use it until an hour has
2545 gone by, or until we have no dirservers that haven't given us a 503.
2546 - When we get a 503 from a directory, and we're not a server, we don't
2547 count the failure against the total number of failures allowed
2548 for the thing we're trying to download.
2549 - Report X-Your-Address-Is correctly from tunneled directory
2550 connections; don't report X-Your-Address-Is when it's an internal
2551 address; and never believe reported remote addresses when they're
2553 - Protect against an unlikely DoS attack on directory servers.
2554 - Add a BadDirectory flag to network status docs so that authorities
2555 can (eventually) tell clients about caches they believe to be
2558 o Minor features (controller):
2559 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
2560 - Reimplement GETINFO so that info/names stays in sync with the
2562 - Implement "GETINFO fingerprint".
2563 - Implement "SETEVENTS GUARD" so controllers can get updates on
2564 entry guard status as it changes.
2566 o Minor features (clean up obsolete pieces):
2567 - Remove some options that have been deprecated since at least
2568 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
2569 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
2571 - We no longer look for identity and onion keys in "identity.key" and
2572 "onion.key" -- these were replaced by secret_id_key and
2573 secret_onion_key in 0.0.8pre1.
2574 - We no longer require unrecognized directory entries to be
2577 o Major bugfixes (security):
2578 - Stop sending the HttpProxyAuthenticator string to directory
2579 servers when directory connections are tunnelled through Tor.
2580 - Clients no longer store bandwidth history in the state file.
2581 - Do not log introduction points for hidden services if SafeLogging
2583 - When generating bandwidth history, round down to the nearest
2584 1k. When storing accounting data, round up to the nearest 1k.
2585 - When we're running as a server, remember when we last rotated onion
2586 keys, so that we will rotate keys once they're a week old even if
2587 we never stay up for a week ourselves.
2589 o Major bugfixes (other):
2590 - Fix a longstanding bug in eventdns that prevented the count of
2591 timed-out resolves from ever being reset. This bug caused us to
2592 give up on a nameserver the third time it timed out, and try it
2593 10 seconds later... and to give up on it every time it timed out
2595 - Take out the '5 second' timeout from the connection retry
2596 schedule. Now the first connect attempt will wait a full 10
2597 seconds before switching to a new circuit. Perhaps this will help
2598 a lot. Based on observations from Mike Perry.
2599 - Fix a bug on the Windows implementation of tor_mmap_file() that
2600 would prevent the cached-routers file from ever loading. Reported
2604 - Fix an assert failure when a directory authority sets
2605 AuthDirRejectUnlisted and then receives a descriptor from an
2606 unlisted router. Reported by seeess.
2607 - Avoid a double-free when parsing malformed DirServer lines.
2608 - Fix a bug when a BSD-style PF socket is first used. Patch from
2610 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
2611 to resolve an address at a given exit node even when they ask for
2613 - Servers no longer ever list themselves in their "family" line,
2614 even if configured to do so. This makes it easier to configure
2615 family lists conveniently.
2616 - When running as a server, don't fall back to 127.0.0.1 when no
2617 nameservers are configured in /etc/resolv.conf; instead, make the
2618 user fix resolv.conf or specify nameservers explicitly. (Resolves
2620 - Stop accepting certain malformed ports in configured exit policies.
2621 - Don't re-write the fingerprint file every restart, unless it has
2623 - Stop warning when a single nameserver fails: only warn when _all_ of
2624 our nameservers have failed. Also, when we only have one nameserver,
2625 raise the threshold for deciding that the nameserver is dead.
2626 - Directory authorities now only decide that routers are reachable
2627 if their identity keys are as expected.
2628 - When the user uses bad syntax in the Log config line, stop
2629 suggesting other bad syntax as a replacement.
2630 - Correctly detect ipv6 DNS capability on OpenBSD.
2632 o Minor bugfixes (controller):
2633 - Report the circuit number correctly in STREAM CLOSED events. Bug
2634 reported by Mike Perry.
2635 - Do not report bizarre values for results of accounting GETINFOs
2636 when the last second's write or read exceeds the allotted bandwidth.
2637 - Report "unrecognized key" rather than an empty string when the
2638 controller tries to fetch a networkstatus that doesn't exist.
2641 Changes in version 0.1.1.26 - 2006-12-14
2642 o Security bugfixes:
2643 - Stop sending the HttpProxyAuthenticator string to directory
2644 servers when directory connections are tunnelled through Tor.
2645 - Clients no longer store bandwidth history in the state file.
2646 - Do not log introduction points for hidden services if SafeLogging
2650 - Fix an assert failure when a directory authority sets
2651 AuthDirRejectUnlisted and then receives a descriptor from an
2652 unlisted router (reported by seeess).
2655 Changes in version 0.1.2.4-alpha - 2006-12-03
2657 - Add support for using natd; this allows FreeBSDs earlier than
2658 5.1.2 to have ipfw send connections through Tor without using
2659 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
2662 - Make all connections to addresses of the form ".noconnect"
2663 immediately get closed. This lets application/controller combos
2664 successfully test whether they're talking to the same Tor by
2665 watching for STREAM events.
2666 - Make cross.sh cross-compilation script work even when autogen.sh
2667 hasn't been run. (Patch from Michael Mohr.)
2668 - Statistics dumped by -USR2 now include a breakdown of public key
2669 operations, for profiling.
2672 - Fix a major leak when directory authorities parse their
2673 approved-routers list, a minor memory leak when we fail to pick
2674 an exit node, and a few rare leaks on errors.
2675 - Handle TransPort connections even when the server sends data before
2676 the client sends data. Previously, the connection would just hang
2677 until the client sent data. (Patch from tup based on patch from
2679 - Avoid assert failure when our cached-routers file is empty on
2683 - Don't log spurious warnings when we see a circuit close reason we
2684 don't recognize; it's probably just from a newer version of Tor.
2685 - Have directory authorities allow larger amounts of drift in uptime
2686 without replacing the server descriptor: previously, a server that
2687 restarted every 30 minutes could have 48 "interesting" descriptors
2689 - Start linking to the Tor specification and Tor reference manual
2690 correctly in the Windows installer.
2691 - Add Vidalia to the OS X uninstaller script, so when we uninstall
2692 Tor/Privoxy we also uninstall Vidalia.
2693 - Resume building on Irix64, and fix a lot of warnings from its
2695 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
2696 when we're running as a client.
2699 Changes in version 0.1.1.25 - 2006-11-04
2701 - When a client asks us to resolve (rather than connect to)
2702 an address, and we have a cached answer, give them the cached
2703 answer. Previously, we would give them no answer at all.
2704 - We were building exactly the wrong circuits when we predict
2705 hidden service requirements, meaning Tor would have to build all
2706 its circuits on demand.
2707 - If none of our live entry guards have a high uptime, but we
2708 require a guard with a high uptime, try adding a new guard before
2709 we give up on the requirement. This patch should make long-lived
2710 connections more stable on average.
2711 - When testing reachability of our DirPort, don't launch new
2712 tests when there's already one in progress -- unreachable
2713 servers were stacking up dozens of testing streams.
2715 o Security bugfixes:
2716 - When the user sends a NEWNYM signal, clear the client-side DNS
2717 cache too. Otherwise we continue to act on previous information.
2720 - Avoid a memory corruption bug when creating a hash table for
2722 - Avoid possibility of controller-triggered crash when misusing
2723 certain commands from a v0 controller on platforms that do not
2724 handle printf("%s",NULL) gracefully.
2725 - Avoid infinite loop on unexpected controller input.
2726 - Don't log spurious warnings when we see a circuit close reason we
2727 don't recognize; it's probably just from a newer version of Tor.
2728 - Add Vidalia to the OS X uninstaller script, so when we uninstall
2729 Tor/Privoxy we also uninstall Vidalia.
2732 Changes in version 0.1.2.3-alpha - 2006-10-29
2734 - Prepare for servers to publish descriptors less often: never
2735 discard a descriptor simply for being too old until either it is
2736 recommended by no authorities, or until we get a better one for
2737 the same router. Make caches consider retaining old recommended
2738 routers for even longer.
2739 - If most authorities set a BadExit flag for a server, clients
2740 don't think of it as a general-purpose exit. Clients only consider
2741 authorities that advertise themselves as listing bad exits.
2742 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
2743 headers for content, so that we can work better in the presence of
2744 caching HTTP proxies.
2745 - Allow authorities to list nodes as bad exits by fingerprint or by
2748 o Minor features, controller:
2749 - Add a REASON field to CIRC events; for backward compatibility, this
2750 field is sent only to controllers that have enabled the extended
2751 event format. Also, add additional reason codes to explain why
2752 a given circuit has been destroyed or truncated. (Patches from
2754 - Add a REMOTE_REASON field to extended CIRC events to tell the
2755 controller about why a remote OR told us to close a circuit.
2756 - Stream events also now have REASON and REMOTE_REASON fields,
2757 working much like those for circuit events.
2758 - There's now a GETINFO ns/... field so that controllers can ask Tor
2759 about the current status of a router.
2760 - A new event type "NS" to inform a controller when our opinion of
2761 a router's status has changed.
2762 - Add a GETINFO events/names and GETINFO features/names so controllers
2763 can tell which events and features are supported.
2764 - A new CLEARDNSCACHE signal to allow controllers to clear the
2765 client-side DNS cache without expiring circuits.
2767 o Security bugfixes:
2768 - When the user sends a NEWNYM signal, clear the client-side DNS
2769 cache too. Otherwise we continue to act on previous information.
2772 - Avoid sending junk to controllers or segfaulting when a controller
2773 uses EVENT_NEW_DESC with verbose nicknames.
2774 - Stop triggering asserts if the controller tries to extend hidden
2775 service circuits (reported by mwenge).
2776 - Avoid infinite loop on unexpected controller input.
2777 - When the controller does a "GETINFO network-status", tell it
2778 about even those routers whose descriptors are very old, and use
2779 long nicknames where appropriate.
2780 - Change NT service functions to be loaded on demand. This lets us
2781 build with MinGW without breaking Tor for Windows 98 users.
2782 - Do DirPort reachability tests less often, since a single test
2783 chews through many circuits before giving up.
2784 - In the hidden service example in torrc.sample, stop recommending
2785 esoteric and discouraged hidden service options.
2786 - When stopping an NT service, wait up to 10 sec for it to actually
2787 stop. (Patch from Matt Edman; resolves bug 295.)
2788 - Fix handling of verbose nicknames with ORCONN controller events:
2789 make them show up exactly when requested, rather than exactly when
2791 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
2792 printing a duplicate "$" in the keys we send (reported by mwenge).
2793 - Correctly set maximum connection limit on Cygwin. (This time
2795 - Try to detect Windows correctly when cross-compiling.
2796 - Detect the size of the routers file correctly even if it is
2797 corrupted (on systems without mmap) or not page-aligned (on systems
2798 with mmap). This bug was harmless.
2799 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
2800 to open a stream fails; now we do in more cases. This should
2801 make clients able to find a good exit faster in some cases, since
2802 unhandleable requests will now get an error rather than timing out.
2803 - Resolve two memory leaks when rebuilding the on-disk router cache
2804 (reported by fookoowa).
2805 - Clean up minor code warnings suggested by the MIPSpro C compiler,
2806 and reported by some Centos users.
2807 - Controller signals now work on non-Unix platforms that don't define
2808 SIGUSR1 and SIGUSR2 the way we expect.
2809 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
2810 values before failing, and always enables eventdns.
2811 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
2812 Try to fix this in configure.in by checking for most functions
2813 before we check for libevent.
2816 Changes in version 0.1.2.2-alpha - 2006-10-07
2818 - Make our async eventdns library on-by-default for Tor servers,
2819 and plan to deprecate the separate dnsworker threads.
2820 - Add server-side support for "reverse" DNS lookups (using PTR
2821 records so clients can determine the canonical hostname for a given
2822 IPv4 address). Only supported by servers using eventdns; servers
2823 now announce in their descriptors whether they support eventdns.
2824 - Specify and implement client-side SOCKS5 interface for reverse DNS
2825 lookups (see doc/socks-extensions.txt).
2826 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
2827 connect to directory servers through Tor. Previously, clients needed
2828 to find Tor exits to make private connections to directory servers.
2829 - Avoid choosing Exit nodes for entry or middle hops when the
2830 total bandwidth available from non-Exit nodes is much higher than
2831 the total bandwidth available from Exit nodes.
2832 - Workaround for name servers (like Earthlink's) that hijack failing
2833 DNS requests and replace the no-such-server answer with a "helpful"
2834 redirect to an advertising-driven search portal. Also work around
2835 DNS hijackers who "helpfully" decline to hijack known-invalid
2836 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
2837 lets you turn it off.
2838 - Send out a burst of long-range padding cells once we've established
2839 that we're reachable. Spread them over 4 circuits, so hopefully
2840 a few will be fast. This exercises our bandwidth and bootstraps
2841 us into the directory more quickly.
2843 o New/improved config options:
2844 - Add new config option "ResolvConf" to let the server operator
2845 choose an alternate resolve.conf file when using eventdns.
2846 - Add an "EnforceDistinctSubnets" option to control our "exclude
2847 servers on the same /16" behavior. It's still on by default; this
2848 is mostly for people who want to operate private test networks with
2849 all the machines on the same subnet.
2850 - If one of our entry guards is on the ExcludeNodes list, or the
2851 directory authorities don't think it's a good guard, treat it as
2852 if it were unlisted: stop using it as a guard, and throw it off
2853 the guards list if it stays that way for a long time.
2854 - Allow directory authorities to be marked separately as authorities
2855 for the v1 directory protocol, the v2 directory protocol, and
2856 as hidden service directories, to make it easier to retire old
2857 authorities. V1 authorities should set "HSAuthoritativeDir 1"
2858 to continue being hidden service authorities too.
2859 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
2861 o Minor features, controller:
2862 - Fix CIRC controller events so that controllers can learn the
2863 identity digests of non-Named servers used in circuit paths.
2864 - Let controllers ask for more useful identifiers for servers. Instead
2865 of learning identity digests for un-Named servers and nicknames
2866 for Named servers, the new identifiers include digest, nickname,
2867 and indication of Named status. Off by default; see control-spec.txt
2868 for more information.
2869 - Add a "getinfo address" controller command so it can display Tor's
2870 best guess to the user.
2871 - New controller event to alert the controller when our server
2872 descriptor has changed.
2873 - Give more meaningful errors on controller authentication failure.
2875 o Minor features, other:
2876 - When asked to resolve a hostname, don't use non-exit servers unless
2877 requested to do so. This allows servers with broken DNS to be
2878 useful to the network.
2879 - Divide eventdns log messages into warn and info messages.
2880 - Reserve the nickname "Unnamed" for routers that can't pick
2881 a hostname: any router can call itself Unnamed; directory
2882 authorities will never allocate Unnamed to any particular router;
2883 clients won't believe that any router is the canonical Unnamed.
2884 - Only include function names in log messages for info/debug messages.
2885 For notice/warn/err, the content of the message should be clear on
2886 its own, and printing the function name only confuses users.
2887 - Avoid some false positives during reachability testing: don't try
2888 to test via a server that's on the same /24 as us.
2889 - If we fail to build a circuit to an intended enclave, and it's
2890 not mandatory that we use that enclave, stop wanting it.
2891 - When eventdns is enabled, allow multithreaded builds on NetBSD and
2892 OpenBSD. (We had previously disabled threads on these platforms
2893 because they didn't have working thread-safe resolver functions.)
2895 o Major bugfixes, anonymity/security:
2896 - If a client asked for a server by name, and there's a named server
2897 in our network-status but we don't have its descriptor yet, we
2898 could return an unnamed server instead.
2899 - Fix NetBSD bug that could allow someone to force uninitialized RAM
2900 to be sent to a server's DNS resolver. This only affects NetBSD
2901 and other platforms that do not bounds-check tolower().
2902 - Reject (most) attempts to use Tor circuits with length one. (If
2903 many people start using Tor as a one-hop proxy, exit nodes become
2904 a more attractive target for compromise.)
2905 - Just because your DirPort is open doesn't mean people should be
2906 able to remotely teach you about hidden service descriptors. Now
2907 only accept rendezvous posts if you've got HSAuthoritativeDir set.
2909 o Major bugfixes, other:
2910 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
2911 - When a client asks the server to resolve (not connect to)
2912 an address, and it has a cached answer, give them the cached answer.
2913 Previously, the server would give them no answer at all.
2914 - Allow really slow clients to not hang up five minutes into their
2915 directory downloads (suggested by Adam J. Richter).
2916 - We were building exactly the wrong circuits when we anticipated
2917 hidden service requirements, meaning Tor would have to build all
2918 its circuits on demand.
2919 - Avoid crashing when we mmap a router cache file of size 0.
2920 - When testing reachability of our DirPort, don't launch new
2921 tests when there's already one in progress -- unreachable
2922 servers were stacking up dozens of testing streams.
2924 o Minor bugfixes, correctness:
2925 - If we're a directory mirror and we ask for "all" network status
2926 documents, we would discard status documents from authorities
2928 - Avoid a memory corruption bug when creating a hash table for
2930 - Avoid controller-triggered crash when misusing certain commands
2931 from a v0 controller on platforms that do not handle
2932 printf("%s",NULL) gracefully.
2933 - Don't crash when a controller sends a third argument to an
2934 "extendcircuit" request.
2935 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
2936 response; fix error code when "getinfo dir/status/" fails.
2937 - Avoid crash when telling controller stream-status and a stream
2939 - Patch from Adam Langley to fix assert() in eventdns.c.
2940 - Fix a debug log message in eventdns to say "X resolved to Y"
2941 instead of "X resolved to X".
2942 - Make eventdns give strings for DNS errors, not just error numbers.
2943 - Track unreachable entry guards correctly: don't conflate
2944 'unreachable by us right now' with 'listed as down by the directory
2945 authorities'. With the old code, if a guard was unreachable by
2946 us but listed as running, it would clog our guard list forever.
2947 - Behave correctly in case we ever have a network with more than
2948 2GB/s total advertised capacity.
2949 - Make TrackExitHosts case-insensitive, and fix the behavior of
2950 ".suffix" TrackExitHosts items to avoid matching in the middle of
2952 - Finally fix the openssl warnings from newer gccs that believe that
2953 ignoring a return value is okay, but casting a return value and
2954 then ignoring it is a sign of madness.
2955 - Prevent the contrib/exitlist script from printing the same
2956 result more than once.
2957 - Patch from Steve Hildrey: Generate network status correctly on
2958 non-versioning dirservers.
2959 - Don't listen to the X-Your-Address-Is hint if you did the lookup
2960 via Tor; otherwise you'll think you're the exit node's IP address.
2962 o Minor bugfixes, performance:
2963 - Two small performance improvements on parsing descriptors.
2964 - Major performance improvement on inserting descriptors: change
2965 algorithm from O(n^2) to O(n).
2966 - Make the common memory allocation path faster on machines where
2967 malloc(0) returns a pointer.
2968 - Start remembering X-Your-Address-Is directory hints even if you're
2969 a client, so you can become a server more smoothly.
2970 - Avoid duplicate entries on MyFamily line in server descriptor.
2972 o Packaging, features:
2973 - Remove architecture from OS X builds. The official builds are
2974 now universal binaries.
2975 - The Debian package now uses --verify-config when (re)starting,
2976 to distinguish configuration errors from other errors.
2977 - Update RPMs to require libevent 1.1b.
2979 o Packaging, bugfixes:
2980 - Patches so Tor builds with MinGW on Windows.
2981 - Patches so Tor might run on Cygwin again.
2982 - Resume building on non-gcc compilers and ancient gcc. Resume
2983 building with the -O0 compile flag. Resume building cleanly on
2985 - Run correctly on OS X platforms with case-sensitive filesystems.
2986 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
2987 - Add autoconf checks so Tor can build on Solaris x86 again.
2990 - Documented (and renamed) ServerDNSSearchDomains and
2991 ServerDNSResolvConfFile options.
2992 - Be clearer that the *ListenAddress directives can be repeated
2996 Changes in version 0.1.1.24 - 2006-09-29
2998 - Allow really slow clients to not hang up five minutes into their
2999 directory downloads (suggested by Adam J. Richter).
3000 - Fix major performance regression from 0.1.0.x: instead of checking
3001 whether we have enough directory information every time we want to
3002 do something, only check when the directory information has changed.
3003 This should improve client CPU usage by 25-50%.
3004 - Don't crash if, after a server has been running for a while,
3005 it can't resolve its hostname.
3008 - Allow Tor to start when RunAsDaemon is set but no logs are set.
3009 - Don't crash when the controller receives a third argument to an
3010 "extendcircuit" request.
3011 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
3012 response; fix error code when "getinfo dir/status/" fails.
3013 - Fix configure.in to not produce broken configure files with
3014 more recent versions of autoconf. Thanks to Clint for his auto*
3016 - Fix security bug on NetBSD that could allow someone to force
3017 uninitialized RAM to be sent to a server's DNS resolver. This
3018 only affects NetBSD and other platforms that do not bounds-check
3020 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
3021 methods: these are known to be buggy.
3022 - If we're a directory mirror and we ask for "all" network status
3023 documents, we would discard status documents from authorities
3027 Changes in version 0.1.2.1-alpha - 2006-08-27
3029 - Add "eventdns" async dns library from Adam Langley, tweaked to
3030 build on OSX and Windows. Only enabled if you pass the
3031 --enable-eventdns argument to configure.
3032 - Allow servers with no hostname or IP address to learn their
3033 IP address by asking the directory authorities. This code only
3034 kicks in when you would normally have exited with a "no address"
3035 error. Nothing's authenticated, so use with care.
3036 - Rather than waiting a fixed amount of time between retrying
3037 application connections, we wait only 5 seconds for the first,
3038 10 seconds for the second, and 15 seconds for each retry after
3039 that. Hopefully this will improve the expected user experience.
3040 - Patch from Tup to add support for transparent AP connections:
3041 this basically bundles the functionality of trans-proxy-tor
3042 into the Tor mainline. Now hosts with compliant pf/netfilter
3043 implementations can redirect TCP connections straight to Tor
3044 without diverting through SOCKS. Needs docs.
3045 - Busy directory servers save lots of memory by spooling server
3046 descriptors, v1 directories, and v2 networkstatus docs to buffers
3047 as needed rather than en masse. Also mmap the cached-routers
3048 files, so we don't need to keep the whole thing in memory too.
3049 - Automatically avoid picking more than one node from the same
3050 /16 network when constructing a circuit.
3051 - Revise and clean up the torrc.sample that we ship with; add
3052 a section for BandwidthRate and BandwidthBurst.
3055 - Split circuit_t into origin_circuit_t and or_circuit_t, and
3056 split connection_t into edge, or, dir, control, and base structs.
3057 These will save quite a bit of memory on busy servers, and they'll
3058 also help us track down bugs in the code and bugs in the spec.
3059 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
3060 or later. Log when we are doing this, so we can diagnose it when
3061 it fails. (Also, recommend libevent 1.1b for kqueue and
3062 win32 methods; deprecate libevent 1.0b harder; make libevent
3063 recommendation system saner.)
3064 - Start being able to build universal binaries on OS X (thanks
3066 - Export the default exit policy via the control port, so controllers
3067 don't need to guess what it is / will be later.
3068 - Add a man page entry for ProtocolWarnings.
3069 - Add TestVia config option to the man page.
3070 - Remove even more protocol-related warnings from Tor server logs,
3071 such as bad TLS handshakes and malformed begin cells.
3072 - Stop fetching descriptors if you're not a dir mirror and you
3073 haven't tried to establish any circuits lately. [This currently
3074 causes some dangerous behavior, because when you start up again
3075 you'll use your ancient server descriptors.]
3076 - New DirPort behavior: if you have your dirport set, you download
3077 descriptors aggressively like a directory mirror, whether or not
3079 - Get rid of the router_retry_connections notion. Now routers
3080 no longer try to rebuild long-term connections to directory
3081 authorities, and directory authorities no longer try to rebuild
3082 long-term connections to all servers. We still don't hang up
3083 connections in these two cases though -- we need to look at it
3084 more carefully to avoid flapping, and we likely need to wait til
3085 0.1.1.x is obsolete.
3086 - Drop compatibility with obsolete Tors that permit create cells
3087 to have the wrong circ_id_type.
3088 - Re-enable per-connection rate limiting. Get rid of the "OP
3089 bandwidth" concept. Lay groundwork for "bandwidth classes" --
3090 separate global buckets that apply depending on what sort of conn
3092 - Start publishing one minute or so after we find our ORPort
3093 to be reachable. This will help reduce the number of descriptors
3094 we have for ourselves floating around, since it's quite likely
3095 other things (e.g. DirPort) will change during that minute too.
3096 - Fork the v1 directory protocol into its own spec document,
3097 and mark dir-spec.txt as the currently correct (v2) spec.
3100 - When we find our DirPort to be reachable, publish a new descriptor
3101 so we'll tell the world (reported by pnx).
3102 - Publish a new descriptor after we hup/reload. This is important
3103 if our config has changed such that we'll want to start advertising
3104 our DirPort now, etc.
3105 - Allow Tor to start when RunAsDaemon is set but no logs are set.
3106 - When we have a state file we cannot parse, tell the user and
3107 move it aside. Now we avoid situations where the user starts
3108 Tor in 1904, Tor writes a state file with that timestamp in it,
3109 the user fixes her clock, and Tor refuses to start.
3110 - Fix configure.in to not produce broken configure files with
3111 more recent versions of autoconf. Thanks to Clint for his auto*
3113 - "tor --verify-config" now exits with -1(255) or 0 depending on
3114 whether the config options are bad or good.
3115 - Resolve bug 321 when using dnsworkers: append a period to every
3116 address we resolve at the exit node, so that we do not accidentally
3117 pick up local addresses, and so that failing searches are retried
3118 in the resolver search domains. (This is already solved for
3119 eventdns.) (This breaks Blossom servers for now.)
3120 - If we are using an exit enclave and we can't connect, e.g. because
3121 its webserver is misconfigured to not listen on localhost, then
3122 back off and try connecting from somewhere else before we fail.
3125 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
3126 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
3127 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
3128 when the IP address is mapped through MapAddress to a hostname.
3129 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
3130 useless IPv6 DNS resolves.
3131 - Patch suggested by Karsten Loesing: respond to SIGNAL command
3132 before we execute the signal, in case the signal shuts us down.
3133 - Clean up AllowInvalidNodes man page entry.
3134 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
3135 - Add more asserts to track down an assert error on a windows Tor
3136 server with connection_add being called with socket == -1.
3137 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
3138 - Fix misleading log messages: an entry guard that is "unlisted",
3139 as well as not known to be "down" (because we've never heard
3140 of it), is not therefore "up".
3141 - Remove code to special-case "-cvs" ending, since it has not
3142 actually mattered since 0.0.9.
3143 - Make our socks5 handling more robust to broken socks clients:
3144 throw out everything waiting on the buffer in between socks
3145 handshake phases, since they can't possibly (so the theory
3146 goes) have predicted what we plan to respond to them.
3149 Changes in version 0.1.1.23 - 2006-07-30
3151 - Fast Tor servers, especially exit nodes, were triggering asserts
3152 due to a bug in handling the list of pending DNS resolves. Some
3153 bugs still remain here; we're hunting them.
3154 - Entry guards could crash clients by sending unexpected input.
3155 - More fixes on reachability testing: if you find yourself reachable,
3156 then don't ever make any client requests (so you stop predicting
3157 circuits), then hup or have your clock jump, then later your IP
3158 changes, you won't think circuits are working, so you won't try to
3159 test reachability, so you won't publish.
3162 - Avoid a crash if the controller does a resetconf firewallports
3163 and then a setconf fascistfirewall=1.
3164 - Avoid an integer underflow when the dir authority decides whether
3165 a router is stable: we might wrongly label it stable, and compute
3166 a slightly wrong median stability, when a descriptor is published
3168 - Fix a place where we might trigger an assert if we can't build our
3169 own server descriptor yet.
3172 Changes in version 0.1.1.22 - 2006-07-05
3174 - Fix a big bug that was causing servers to not find themselves
3175 reachable if they changed IP addresses. Since only 0.1.1.22+
3176 servers can do reachability testing correctly, now we automatically
3177 make sure to test via one of these.
3178 - Fix to allow clients and mirrors to learn directory info from
3179 descriptor downloads that get cut off partway through.
3180 - Directory authorities had a bug in deciding if a newly published
3181 descriptor was novel enough to make everybody want a copy -- a few
3182 servers seem to be publishing new descriptors many times a minute.
3184 - Fix a rare bug that was causing some servers to complain about
3185 "closing wedged cpuworkers" and skip some circuit create requests.
3186 - Make the Exit flag in directory status documents actually work.
3189 Changes in version 0.1.1.21 - 2006-06-10
3190 o Crash and assert fixes from 0.1.1.20:
3191 - Fix a rare crash on Tor servers that have enabled hibernation.
3192 - Fix a seg fault on startup for Tor networks that use only one
3193 directory authority.
3194 - Fix an assert from a race condition that occurs on Tor servers
3195 while exiting, where various threads are trying to log that they're
3196 exiting, and delete the logs, at the same time.
3197 - Make our unit tests pass again on certain obscure platforms.
3200 - Add support for building SUSE RPM packages.
3201 - Speed up initial bootstrapping for clients: if we are making our
3202 first ever connection to any entry guard, then don't mark it down
3204 - When only one Tor server in the network is labelled as a guard,
3205 and we've already picked him, we would cycle endlessly picking him
3206 again, being unhappy about it, etc. Now we specifically exclude
3207 current guards when picking a new guard.
3208 - Servers send create cells more reliably after the TLS connection
3209 is established: we were sometimes forgetting to send half of them
3210 when we had more than one pending.
3211 - If we get a create cell that asks us to extend somewhere, but the
3212 Tor server there doesn't match the expected digest, we now send
3213 a destroy cell back, rather than silently doing nothing.
3214 - Make options->RedirectExit work again.
3215 - Make cookie authentication for the controller work again.
3216 - Stop being picky about unusual characters in the arguments to
3217 mapaddress. It's none of our business.
3218 - Add a new config option "TestVia" that lets you specify preferred
3219 middle hops to use for test circuits. Perhaps this will let me
3220 debug the reachability problems better.
3222 o Log / documentation fixes:
3223 - If we're a server and some peer has a broken TLS certificate, don't
3224 log about it unless ProtocolWarnings is set, i.e., we want to hear
3225 about protocol violations by others.
3226 - Fix spelling of VirtualAddrNetwork in man page.
3227 - Add a better explanation at the top of the autogenerated torrc file
3228 about what happened to our old torrc.
3231 Changes in version 0.1.1.20 - 2006-05-23
3233 - Downgrade a log severity where servers complain that they're
3235 - Avoid a compile warning on FreeBSD.
3236 - Remove string size limit on NEWDESC messages; solve bug 291.
3237 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
3238 more thoroughly when we're running on windows.
3241 Changes in version 0.1.1.19-rc - 2006-05-03
3243 - Regenerate our local descriptor if it's dirty and we try to use
3244 it locally (e.g. if it changes during reachability detection).
3245 - If we setconf our ORPort to 0, we continued to listen on the
3246 old ORPort and receive connections.
3247 - Avoid a second warning about machine/limits.h on Debian
3249 - Be willing to add our own routerinfo into the routerlist.
3250 Now authorities will include themselves in their directories
3251 and network-statuses.
3252 - Stop trying to upload rendezvous descriptors to every
3253 directory authority: only try the v1 authorities.
3254 - Servers no longer complain when they think they're not
3255 registered with the directory authorities. There were too many
3257 - Backport dist-rpm changes so rpms can be built without errors.
3260 - Implement an option, VirtualAddrMask, to set which addresses
3261 get handed out in response to mapaddress requests. This works
3262 around a bug in tsocks where 127.0.0.0/8 is never socksified.
3265 Changes in version 0.1.1.18-rc - 2006-04-10
3267 - Work harder to download live network-statuses from all the
3268 directory authorities we know about. Improve the threshold
3269 decision logic so we're more robust to edge cases.
3270 - When fetching rendezvous descriptors, we were willing to ask
3271 v2 authorities too, which would always return 404.
3274 - Stop listing down or invalid nodes in the v1 directory. This will
3275 reduce its bulk by about 1/3, and reduce load on directory
3277 - When deciding whether a router is Fast or Guard-worthy, consider
3278 his advertised BandwidthRate and not just the BandwidthCapacity.
3279 - No longer ship INSTALL and README files -- they are useless now.
3280 - Force rpmbuild to behave and honor target_cpu.
3281 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
3282 - Start to include translated versions of the tor-doc-*.html
3283 files, along with the screenshots. Still needs more work.
3284 - Start sending back 512 and 451 errors if mapaddress fails,
3285 rather than not sending anything back at all.
3286 - When we fail to bind or listen on an incoming or outgoing
3287 socket, we should close it before failing. otherwise we just
3288 leak it. (thanks to weasel for finding.)
3289 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
3290 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
3291 - Make NoPublish (even though deprecated) work again.
3292 - Fix a minor security flaw where a versioning auth dirserver
3293 could list a recommended version many times in a row to make
3294 clients more convinced that it's recommended.
3295 - Fix crash bug if there are two unregistered servers running
3296 with the same nickname, one of them is down, and you ask for
3297 them by nickname in your EntryNodes or ExitNodes. Also, try
3298 to pick the one that's running rather than an arbitrary one.
3299 - Fix an infinite loop we could hit if we go offline for too long.
3300 - Complain when we hit WSAENOBUFS on recv() or write() too.
3301 Perhaps this will help us hunt the bug.
3302 - If you're not a versioning dirserver, don't put the string
3303 "client-versions \nserver-versions \n" in your network-status.
3304 - Lower the minimum required number of file descriptors to 1000,
3305 so we can have some overhead for Valgrind on Linux, where the
3306 default ulimit -n is 1024.
3309 - Add tor.dizum.com as the fifth authoritative directory server.
3310 - Add a new config option FetchUselessDescriptors, off by default,
3311 for when you plan to run "exitlist" on your client and you want
3312 to know about even the non-running descriptors.
3315 Changes in version 0.1.1.17-rc - 2006-03-28
3317 - Clients and servers since 0.1.1.10-alpha have been expiring
3318 connections whenever they are idle for 5 minutes and they *do*
3319 have circuits on them. Oops. With this new version, clients will
3320 discard their previous entry guard choices and avoid choosing
3321 entry guards running these flawed versions.
3322 - Fix memory leak when uncompressing concatenated zlib streams. This
3323 was causing substantial leaks over time on Tor servers.
3324 - The v1 directory was including servers as much as 48 hours old,
3325 because that's how the new routerlist->routers works. Now only
3326 include them if they're 20 hours old or less.
3329 - Resume building on irix64, netbsd 2.0, etc.
3330 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
3332 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
3333 and it is confusing some users.
3334 - Mirrors stop caching the v1 directory so often.
3335 - Make the max number of old descriptors that a cache will hold
3336 rise with the number of directory authorities, so we can scale.
3337 - Change our win32 uname() hack to be more forgiving about what
3338 win32 versions it thinks it's found.
3341 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
3343 - When the controller's *setconf commands fail, collect an error
3344 message in a string and hand it back to the controller.
3345 - Make the v2 dir's "Fast" flag based on relative capacity, just
3346 like "Stable" is based on median uptime. Name everything in the
3347 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
3348 - Log server fingerprint on startup, so new server operators don't
3349 have to go hunting around their filesystem for it.
3350 - Return a robots.txt on our dirport to discourage google indexing.
3351 - Let the controller ask for GETINFO dir/status/foo so it can ask
3352 directly rather than connecting to the dir port. Only works when
3353 dirport is set for now.
3355 o New config options rather than constants in the code:
3356 - SocksTimeout: How long do we let a socks connection wait
3357 unattached before we fail it?
3358 - CircuitBuildTimeout: Cull non-open circuits that were born
3359 at least this many seconds ago.
3360 - CircuitIdleTimeout: Cull open clean circuits that were born
3361 at least this many seconds ago.
3364 Changes in version 0.1.1.16-rc - 2006-03-18
3365 o Bugfixes on 0.1.1.15-rc:
3366 - Fix assert when the controller asks to attachstream a connect-wait
3367 or resolve-wait stream.
3368 - Now do address rewriting when the controller asks us to attach
3369 to a particular circuit too. This will let Blossom specify
3370 "moria2.exit" without having to learn what moria2's IP address is.
3371 - Make the "tor --verify-config" command-line work again, so people
3372 can automatically check if their torrc will parse.
3373 - Authoritative dirservers no longer require an open connection from
3374 a server to consider him "reachable". We need this change because
3375 when we add new auth dirservers, old servers won't know not to
3377 - Let Tor build on Sun CC again.
3378 - Fix an off-by-one buffer size in dirserv.c that magically never
3379 hit our three authorities but broke sjmurdoch's own tor network.
3380 - If we as a directory mirror don't know of any v1 directory
3381 authorities, then don't try to cache any v1 directories.
3382 - Stop warning about unknown servers in our family when they are
3383 given as hex digests.
3384 - Stop complaining as quickly to the server operator that he
3385 hasn't registered his nickname/key binding.
3386 - Various cleanups so we can add new V2 Auth Dirservers.
3387 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
3388 reflect the updated flags in our v2 dir protocol.
3389 - Resume allowing non-printable characters for exit streams (both
3390 for connecting and for resolving). Now we tolerate applications
3391 that don't follow the RFCs. But continue to block malformed names
3394 o Bugfixes on 0.1.0.x:
3395 - Fix assert bug in close_logs(): when we close and delete logs,
3396 remove them all from the global "logfiles" list.
3397 - Fix minor integer overflow in calculating when we expect to use up
3398 our bandwidth allocation before hibernating.
3399 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
3400 there are multiple SSLs installed with different versions.
3401 - When we try to be a server and Address is not explicitly set and
3402 our hostname resolves to a private IP address, try to use an
3403 interface address if it has a public address. Now Windows machines
3404 that think of themselves as localhost can work by default.
3407 - Let the controller ask for GETINFO dir/server/foo so it can ask
3408 directly rather than connecting to the dir port.
3409 - Let the controller tell us about certain router descriptors
3410 that it doesn't want Tor to use in circuits. Implement
3411 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
3412 - New config option SafeSocks to reject all application connections
3413 using unsafe socks protocols. Defaults to off.
3416 Changes in version 0.1.1.15-rc - 2006-03-11
3417 o Bugfixes and cleanups:
3418 - When we're printing strings from the network, don't try to print
3419 non-printable characters. This protects us against shell escape
3420 sequence exploits, and also against attacks to fool humans into
3421 misreading their logs.
3422 - Fix a bug where Tor would fail to establish any connections if you
3423 left it off for 24 hours and then started it: we were happy with
3424 the obsolete network statuses, but they all referred to router
3425 descriptors that were too old to fetch, so we ended up with no
3426 valid router descriptors.
3427 - Fix a seg fault in the controller's "getinfo orconn-status"
3428 command while listing status on incoming handshaking connections.
3429 Introduce a status name "NEW" for these connections.
3430 - If we get a linelist or linelist_s config option from the torrc
3431 (e.g. ExitPolicy) and it has no value, warn and skip rather than
3432 silently resetting it to its default.
3433 - Don't abandon entry guards until they've been down or gone for
3435 - Cleaner and quieter log messages.
3438 - New controller signal NEWNYM that makes new application requests
3440 - Add a new circuit purpose 'controller' to let the controller ask
3441 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
3442 controller command to let you specify the purpose if you're
3443 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
3444 command to let you change a circuit's purpose after it's been
3446 - Accept "private:*" in routerdesc exit policies; not generated yet
3447 because older Tors do not understand it.
3448 - Add BSD-style contributed startup script "rc.subr" from Peter
3452 Changes in version 0.1.1.14-alpha - 2006-02-20
3453 o Bugfixes on 0.1.1.x:
3454 - Don't die if we ask for a stdout or stderr log (even implicitly)
3455 and we're set to RunAsDaemon -- just warn.
3456 - We still had a few bugs in the OR connection rotation code that
3457 caused directory servers to slowly aggregate connections to other
3458 fast Tor servers. This time for sure!
3459 - Make log entries on Win32 include the name of the function again.
3460 - We were treating a pair of exit policies if they were equal even
3461 if one said accept and the other said reject -- causing us to
3462 not always publish a new descriptor since we thought nothing
3464 - Retry pending server downloads as well as pending networkstatus
3465 downloads when we unexpectedly get a socks request.
3466 - We were ignoring the IS_FAST flag in the directory status,
3467 meaning we were willing to pick trivial-bandwidth nodes for "fast"
3469 - If the controller's SAVECONF command fails (e.g. due to file
3470 permissions), let the controller know that it failed.
3473 - If we're trying to be a Tor server and running Windows 95/98/ME
3474 as a server, explain that we'll likely crash.
3475 - When we're a server, a client asks for an old-style directory,
3476 and our write bucket is empty, don't give it to him. This way
3477 small servers can continue to serve the directory *sometimes*,
3478 without getting overloaded.
3479 - Compress exit policies even more -- look for duplicate lines
3481 - Clients now honor the "guard" flag in the router status when
3482 picking entry guards, rather than looking at is_fast or is_stable.
3483 - Retain unrecognized lines in $DATADIR/state file, so that we can
3484 be forward-compatible.
3485 - Generate 18.0.0.0/8 address policy format in descs when we can;
3486 warn when the mask is not reducible to a bit-prefix.
3487 - Let the user set ControlListenAddress in the torrc. This can be
3488 dangerous, but there are some cases (like a secured LAN) where it
3490 - Split ReachableAddresses into ReachableDirAddresses and
3491 ReachableORAddresses, so we can restrict Dir conns to port 80
3492 and OR conns to port 443.
3493 - Now we can target arch and OS in rpm builds (contributed by
3494 Phobos). Also make the resulting dist-rpm filename match the
3496 - New config options to help controllers: FetchServerDescriptors
3497 and FetchHidServDescriptors for whether to fetch server
3498 info and hidserv info or let the controller do it, and
3499 PublishServerDescriptor and PublishHidServDescriptors.
3500 - Also let the controller set the __AllDirActionsPrivate config
3501 option if you want all directory fetches/publishes to happen via
3502 Tor (it assumes your controller bootstraps your circuits).
3505 Changes in version 0.1.0.17 - 2006-02-17
3506 o Crash bugfixes on 0.1.0.x:
3507 - When servers with a non-zero DirPort came out of hibernation,
3508 sometimes they would trigger an assert.
3510 o Other important bugfixes:
3511 - On platforms that don't have getrlimit (like Windows), we were
3512 artificially constraining ourselves to a max of 1024
3513 connections. Now just assume that we can handle as many as 15000
3514 connections. Hopefully this won't cause other problems.
3516 o Backported features:
3517 - When we're a server, a client asks for an old-style directory,
3518 and our write bucket is empty, don't give it to him. This way
3519 small servers can continue to serve the directory *sometimes*,
3520 without getting overloaded.
3521 - Whenever you get a 503 in response to a directory fetch, try
3522 once more. This will become important once servers start sending
3523 503's whenever they feel busy.
3524 - Fetch a new directory every 120 minutes, not every 40 minutes.
3525 Now that we have hundreds of thousands of users running the old
3526 directory algorithm, it's starting to hurt a lot.
3527 - Bump up the period for forcing a hidden service descriptor upload
3528 from 20 minutes to 1 hour.
3531 Changes in version 0.1.1.13-alpha - 2006-02-09
3532 o Crashes in 0.1.1.x:
3533 - When you tried to setconf ORPort via the controller, Tor would
3534 crash. So people using TorCP to become a server were sad.
3535 - Solve (I hope) the stack-smashing bug that we were seeing on fast
3536 servers. The problem appears to be something do with OpenSSL's
3537 random number generation, or how we call it, or something. Let me
3538 know if the crashes continue.
3539 - Turn crypto hardware acceleration off by default, until we find
3540 somebody smart who can test it for us. (It appears to produce
3541 seg faults in at least some cases.)
3542 - Fix a rare assert error when we've tried all intro points for
3543 a hidden service and we try fetching the service descriptor again:
3544 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
3547 - Fix a major load balance bug: we were round-robining in 16 KB
3548 chunks, and servers with bandwidthrate of 20 KB, while downloading
3549 a 600 KB directory, would starve their other connections. Now we
3550 try to be a bit more fair.
3551 - Dir authorities and mirrors were never expiring the newest
3552 descriptor for each server, causing memory and directory bloat.
3553 - Fix memory-bloating and connection-bloating bug on servers: We
3554 were never closing any connection that had ever had a circuit on
3555 it, because we were checking conn->n_circuits == 0, yet we had a
3556 bug that let it go negative.
3557 - Make Tor work using squid as your http proxy again -- squid
3558 returns an error if you ask for a URL that's too long, and it uses
3559 a really generic error message. Plus, many people are behind a
3560 transparent squid so they don't even realize it.
3561 - On platforms that don't have getrlimit (like Windows), we were
3562 artificially constraining ourselves to a max of 1024
3563 connections. Now just assume that we can handle as many as 15000
3564 connections. Hopefully this won't cause other problems.
3565 - Add a new config option ExitPolicyRejectPrivate which defaults to
3566 1. This means all exit policies will begin with rejecting private
3567 addresses, unless the server operator explicitly turns it off.
3570 - Clients no longer download descriptors for non-running
3572 - Before we add new directory authorities, we should make it
3573 clear that only v1 authorities should receive/publish hidden
3574 service descriptors.
3577 - As soon as we've fetched some more directory info, immediately
3578 try to download more server descriptors. This way we don't have
3579 a 10 second pause during initial bootstrapping.
3580 - Remove even more loud log messages that the server operator can't
3582 - When we're running an obsolete or un-recommended version, make
3583 the log message more clear about what the problem is and what
3584 versions *are* still recommended.
3585 - Provide a more useful warn message when our onion queue gets full:
3586 the CPU is too slow or the exit policy is too liberal.
3587 - Don't warn when we receive a 503 from a dirserver/cache -- this
3588 will pave the way for them being able to refuse if they're busy.
3589 - When we fail to bind a listener, try to provide a more useful
3590 log message: e.g., "Is Tor already running?"
3591 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
3592 Goldberg can prove things about our handshake protocol more
3594 - MaxConn has been obsolete for a while now. Document the ConnLimit
3595 config option, which is a *minimum* number of file descriptors
3596 that must be available else Tor refuses to start.
3597 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
3598 if you log to syslog and want something other than LOG_DAEMON.
3599 - Make dirservers generate a separate "guard" flag to mean,
3600 "would make a good entry guard". Make clients parse it and vote
3601 on it. Not used by clients yet.
3602 - Implement --with-libevent-dir option to ./configure. Also, improve
3603 search techniques to find libevent, and use those for openssl too.
3604 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
3605 - Only start testing reachability once we've established a
3606 circuit. This will make startup on dirservers less noisy.
3607 - Don't try to upload hidden service descriptors until we have
3608 established a circuit.
3609 - Fix the controller's "attachstream 0" command to treat conn like
3610 it just connected, doing address remapping, handling .exit and
3611 .onion idioms, and so on. Now we're more uniform in making sure
3612 that the controller hears about new and closing connections.
3615 Changes in version 0.1.1.12-alpha - 2006-01-11
3616 o Bugfixes on 0.1.1.x:
3617 - The fix to close duplicate server connections was closing all
3618 Tor client connections if they didn't establish a circuit
3619 quickly enough. Oops.
3620 - Fix minor memory issue (double-free) that happened on exit.
3622 o Bugfixes on 0.1.0.x:
3623 - Tor didn't warn when it failed to open a log file.
3626 Changes in version 0.1.1.11-alpha - 2006-01-10
3627 o Crashes in 0.1.1.x:
3628 - Include all the assert/crash fixes from 0.1.0.16.
3629 - If you start Tor and then quit very quickly, there were some
3630 races that tried to free things that weren't allocated yet.
3631 - Fix a rare memory stomp if you're running hidden services.
3632 - Fix segfault when specifying DirServer in config without nickname.
3633 - Fix a seg fault when you finish connecting to a server but at
3634 that moment you dump his server descriptor.
3635 - Extendcircuit and Attachstream controller commands would
3636 assert/crash if you don't give them enough arguments.
3637 - Fix an assert error when we're out of space in the connection_list
3638 and we try to post a hidden service descriptor (reported by weasel).
3639 - If you specify a relative torrc path and you set RunAsDaemon in
3640 your torrc, then it chdir()'s to the new directory. If you HUP,
3641 it tries to load the new torrc location, fails, and exits.
3642 The fix: no longer allow a relative path to torrc using -f.
3645 - Implement "entry guards": automatically choose a handful of entry
3646 nodes and stick with them for all circuits. Only pick new guards
3647 when the ones you have are unsuitable, and if the old guards
3648 become suitable again, switch back. This will increase security
3649 dramatically against certain end-point attacks. The EntryNodes
3650 config option now provides some hints about which entry guards you
3651 want to use most; and StrictEntryNodes means to only use those.
3652 - New directory logic: download by descriptor digest, not by
3653 fingerprint. Caches try to download all listed digests from
3654 authorities; clients try to download "best" digests from caches.
3655 This avoids partitioning and isolating attacks better.
3656 - Make the "stable" router flag in network-status be the median of
3657 the uptimes of running valid servers, and make clients pay
3658 attention to the network-status flags. Thus the cutoff adapts
3659 to the stability of the network as a whole, making IRC, IM, etc
3660 connections more reliable.
3663 - Tor servers with dynamic IP addresses were needing to wait 18
3664 hours before they could start doing reachability testing using
3665 the new IP address and ports. This is because they were using
3666 the internal descriptor to learn what to test, yet they were only
3667 rebuilding the descriptor once they decided they were reachable.
3668 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
3669 to download certain server descriptors, throw them away, and then
3670 fetch them again after 30 minutes. Now mirrors throw away these
3671 server descriptors so clients can't get them.
3672 - We were leaving duplicate connections to other ORs open for a week,
3673 rather than closing them once we detect a duplicate. This only
3674 really affected authdirservers, but it affected them a lot.
3675 - Spread the authdirservers' reachability testing over the entire
3676 testing interval, so we don't try to do 500 TLS's at once every
3680 - If the network is down, and we try to connect to a conn because
3681 we have a circuit in mind, and we timeout (30 seconds) because the
3682 network never answers, we were expiring the circuit, but we weren't
3683 obsoleting the connection or telling the entry_guards functions.
3684 - Some Tor servers process billions of cells per day. These statistics
3685 need to be uint64_t's.
3686 - Check for integer overflows in more places, when adding elements
3687 to smartlists. This could possibly prevent a buffer overflow
3688 on malicious huge inputs. I don't see any, but I haven't looked
3690 - ReachableAddresses kept growing new "reject *:*" lines on every
3692 - When you "setconf log" via the controller, it should remove all
3693 logs. We were automatically adding back in a "log notice stdout".
3694 - Newly bootstrapped Tor networks couldn't establish hidden service
3695 circuits until they had nodes with high uptime. Be more tolerant.
3696 - We were marking servers down when they could not answer every piece
3697 of the directory request we sent them. This was far too harsh.
3698 - Fix the torify (tsocks) config file to not use Tor for localhost
3700 - Directory authorities now go to the proper authority when asking for
3701 a networkstatus, even when they want a compressed one.
3702 - Fix a harmless bug that was causing Tor servers to log
3703 "Got an end because of misc error, but we're not an AP. Closing."
3704 - Authorities were treating their own descriptor changes as cosmetic,
3705 meaning the descriptor available in the network-status and the
3706 descriptor that clients downloaded were different.
3707 - The OS X installer was adding a symlink for tor_resolve but
3708 the binary was called tor-resolve (reported by Thomas Hardly).
3709 - Workaround a problem with some http proxies where they refuse GET
3710 requests that specify "Content-Length: 0" (reported by Adrian).
3711 - Fix wrong log message when you add a "HiddenServiceNodes" config
3712 line without any HiddenServiceDir line (reported by Chris Thomas).
3715 - Write the TorVersion into the state file so we have a prayer of
3716 keeping forward and backward compatibility.
3717 - Revive the FascistFirewall config option rather than eliminating it:
3718 now it's a synonym for ReachableAddresses *:80,*:443.
3719 - Clients choose directory servers from the network status lists,
3720 not from their internal list of router descriptors. Now they can
3721 go to caches directly rather than needing to go to authorities
3723 - Directory authorities ignore router descriptors that have only
3724 cosmetic differences: do this for 0.1.0.x servers now too.
3725 - Add a new flag to network-status indicating whether the server
3726 can answer v2 directory requests too.
3727 - Authdirs now stop whining so loudly about bad descriptors that
3728 they fetch from other dirservers. So when there's a log complaint,
3729 it's for sure from a freshly uploaded descriptor.
3730 - Reduce memory requirements in our structs by changing the order
3732 - There used to be two ways to specify your listening ports in a
3733 server descriptor: on the "router" line and with a separate "ports"
3734 line. Remove support for the "ports" line.
3735 - New config option "AuthDirRejectUnlisted" for auth dirservers as
3736 a panic button: if we get flooded with unusable servers we can
3737 revert to only listing servers in the approved-routers file.
3738 - Auth dir servers can now mark a fingerprint as "!reject" or
3739 "!invalid" in the approved-routers file (as its nickname), to
3740 refuse descriptors outright or include them but marked as invalid.
3741 - Servers store bandwidth history across restarts/crashes.
3742 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
3743 get a better idea of why their circuits failed. Not used yet.
3744 - Directory mirrors now cache up to 16 unrecognized network-status
3745 docs. Now we can add new authdirservers and they'll be cached too.
3746 - When picking a random directory, prefer non-authorities if any
3748 - New controller option "getinfo desc/all-recent" to fetch the
3749 latest server descriptor for every router that Tor knows about.
3752 Changes in version 0.1.0.16 - 2006-01-02
3753 o Crash bugfixes on 0.1.0.x:
3754 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
3755 corrupting the heap, losing FDs, or crashing when we need to resize
3756 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
3757 - It turns out sparc64 platforms crash on unaligned memory access
3758 too -- so detect and avoid this.
3759 - Handle truncated compressed data correctly (by detecting it and
3761 - Fix possible-but-unlikely free(NULL) in control.c.
3762 - When we were closing connections, there was a rare case that
3763 stomped on memory, triggering seg faults and asserts.
3764 - Avoid potential infinite recursion when building a descriptor. (We
3765 don't know that it ever happened, but better to fix it anyway.)
3766 - We were neglecting to unlink marked circuits from soon-to-close OR
3767 connections, which caused some rare scribbling on freed memory.
3768 - Fix a memory stomping race bug when closing the joining point of two
3769 rendezvous circuits.
3770 - Fix an assert in time parsing found by Steven Murdoch.
3772 o Other bugfixes on 0.1.0.x:
3773 - When we're doing reachability testing, provide more useful log
3774 messages so the operator knows what to expect.
3775 - Do not check whether DirPort is reachable when we are suppressing
3776 advertising it because of hibernation.
3777 - When building with -static or on Solaris, we sometimes needed -ldl.
3778 - When we're deciding whether a stream has enough circuits around
3779 that can handle it, count the freshly dirty ones and not the ones
3780 that are so dirty they won't be able to handle it.
3781 - When we're expiring old circuits, we had a logic error that caused
3782 us to close new rendezvous circuits rather than old ones.
3783 - Give a more helpful log message when you try to change ORPort via
3784 the controller: you should upgrade Tor if you want that to work.
3785 - We were failing to parse Tor versions that start with "Tor ".
3786 - Tolerate faulty streams better: when a stream fails for reason
3787 exitpolicy, stop assuming that the router is lying about his exit
3788 policy. When a stream fails for reason misc, allow it to retry just
3789 as if it was resolvefailed. When a stream has failed three times,
3790 reset its failure count so we can try again and get all three tries.
3793 Changes in version 0.1.1.10-alpha - 2005-12-11
3794 o Correctness bugfixes on 0.1.0.x:
3795 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
3796 corrupting the heap, losing FDs, or crashing when we need to resize
3797 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
3798 - Stop doing the complex voodoo overkill checking for insecure
3799 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
3800 - When we were closing connections, there was a rare case that
3801 stomped on memory, triggering seg faults and asserts.
3802 - We were neglecting to unlink marked circuits from soon-to-close OR
3803 connections, which caused some rare scribbling on freed memory.
3804 - When we're deciding whether a stream has enough circuits around
3805 that can handle it, count the freshly dirty ones and not the ones
3806 that are so dirty they won't be able to handle it.
3807 - Recover better from TCP connections to Tor servers that are
3808 broken but don't tell you (it happens!); and rotate TLS
3809 connections once a week.
3810 - When we're expiring old circuits, we had a logic error that caused
3811 us to close new rendezvous circuits rather than old ones.
3812 - Fix a scary-looking but apparently harmless bug where circuits
3813 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
3814 servers, and never switch to state CIRCUIT_STATE_OPEN.
3815 - When building with -static or on Solaris, we sometimes needed to
3817 - Give a useful message when people run Tor as the wrong user,
3818 rather than telling them to start chowning random directories.
3819 - We were failing to inform the controller about new .onion streams.
3821 o Security bugfixes on 0.1.0.x:
3822 - Refuse server descriptors if the fingerprint line doesn't match
3823 the included identity key. Tor doesn't care, but other apps (and
3824 humans) might actually be trusting the fingerprint line.
3825 - We used to kill the circuit when we receive a relay command we
3826 don't recognize. Now we just drop it.
3827 - Start obeying our firewall options more rigorously:
3828 . If we can't get to a dirserver directly, try going via Tor.
3829 . Don't ever try to connect (as a client) to a place our
3830 firewall options forbid.
3831 . If we specify a proxy and also firewall options, obey the
3832 firewall options even when we're using the proxy: some proxies
3833 can only proxy to certain destinations.
3834 - Fix a bug found by Lasse Overlier: when we were making internal
3835 circuits (intended to be cannibalized later for rendezvous and
3836 introduction circuits), we were picking them so that they had
3837 useful exit nodes. There was no need for this, and it actually
3838 aids some statistical attacks.
3839 - Start treating internal circuits and exit circuits separately.
3840 It's important to keep them separate because internal circuits
3841 have their last hops picked like middle hops, rather than like
3842 exit hops. So exiting on them will break the user's expectations.
3844 o Bugfixes on 0.1.1.x:
3845 - Take out the mis-feature where we tried to detect IP address
3846 flapping for people with DynDNS, and chose not to upload a new
3847 server descriptor sometimes.
3848 - Try to be compatible with OpenSSL 0.9.6 again.
3849 - Log fix: when the controller is logging about .onion addresses,
3850 sometimes it didn't include the ".onion" part of the address.
3851 - Don't try to modify options->DirServers internally -- if the
3852 user didn't specify any, just add the default ones directly to
3853 the trusted dirserver list. This fixes a bug where people running
3854 controllers would use SETCONF on some totally unrelated config
3855 option, and Tor would start yelling at them about changing their
3857 - Let the controller's redirectstream command specify a port, in
3858 case the controller wants to change that too.
3859 - When we requested a pile of server descriptors, we sometimes
3860 accidentally launched a duplicate request for the first one.
3861 - Bugfix for trackhostexits: write down the fingerprint of the
3862 chosen exit, not its nickname, because the chosen exit might not
3864 - When parsing foo.exit, if foo is unknown, and we are leaving
3865 circuits unattached, set the chosen_exit field and leave the
3866 address empty. This matters because controllers got confused
3868 - Directory authorities no longer try to download server
3869 descriptors that they know they will reject.
3871 o Features and updates:
3872 - Replace balanced trees with hash tables: this should make stuff
3873 significantly faster.
3874 - Resume using the AES counter-mode implementation that we ship,
3875 rather than OpenSSL's. Ours is significantly faster.
3876 - Many other CPU and memory improvements.
3877 - Add a new config option FastFirstHopPK (on by default) so clients
3878 do a trivial crypto handshake for their first hop, since TLS has
3879 already taken care of confidentiality and authentication.
3880 - Add a new config option TestSocks so people can see if their
3881 applications are using socks4, socks4a, socks5-with-ip, or
3882 socks5-with-hostname. This way they don't have to keep mucking
3883 with tcpdump and wondering if something got cached somewhere.
3884 - Warn when listening on a public address for socks. I suspect a
3885 lot of people are setting themselves up as open socks proxies,
3886 and they have no idea that jerks on the Internet are using them,
3887 since they simply proxy the traffic into the Tor network.
3888 - Add "private:*" as an alias in configuration for policies. Now
3889 you can simplify your exit policy rather than needing to list
3890 every single internal or nonroutable network space.
3891 - Add a new controller event type that allows controllers to get
3892 all server descriptors that were uploaded to a router in its role
3893 as authoritative dirserver.
3894 - Start shipping socks-extensions.txt, tor-doc-unix.html,
3895 tor-doc-server.html, and stylesheet.css in the tarball.
3896 - Stop shipping tor-doc.html in the tarball.
3899 Changes in version 0.1.1.9-alpha - 2005-11-15
3900 o Usability improvements:
3901 - Start calling it FooListenAddress rather than FooBindAddress,
3902 since few of our users know what it means to bind an address
3904 - Reduce clutter in server logs. We're going to try to make
3905 them actually usable now. New config option ProtocolWarnings that
3906 lets you hear about how _other Tors_ are breaking the protocol. Off
3908 - Divide log messages into logging domains. Once we put some sort
3909 of interface on this, it will let people looking at more verbose
3910 log levels specify the topics they want to hear more about.
3911 - Make directory servers return better http 404 error messages
3912 instead of a generic "Servers unavailable".
3913 - Check for even more Windows version flags when writing the platform
3914 string in server descriptors, and note any we don't recognize.
3915 - Clean up more of the OpenSSL memory when exiting, so we can detect
3916 memory leaks better.
3917 - Make directory authorities be non-versioning, non-naming by
3918 default. Now we can add new directory servers without requiring
3919 their operators to pay close attention.
3920 - When logging via syslog, include the pid whenever we provide
3921 a log entry. Suggested by Todd Fries.
3923 o Performance improvements:
3924 - Directory servers now silently throw away new descriptors that
3925 haven't changed much if the timestamps are similar. We do this to
3926 tolerate older Tor servers that upload a new descriptor every 15
3927 minutes. (It seemed like a good idea at the time.)
3928 - Inline bottleneck smartlist functions; use fast versions by default.
3929 - Add a "Map from digest to void*" abstraction digestmap_t so we
3930 can do less hex encoding/decoding. Use it in router_get_by_digest()
3931 to resolve a performance bottleneck.
3932 - Allow tor_gzip_uncompress to extract as much as possible from
3933 truncated compressed data. Try to extract as many
3934 descriptors as possible from truncated http responses (when
3935 DIR_PURPOSE_FETCH_ROUTERDESC).
3936 - Make circ->onionskin a pointer, not a static array. moria2 was using
3937 125000 circuit_t's after it had been up for a few weeks, which
3938 translates to 20+ megs of wasted space.
3939 - The private half of our EDH handshake keys are now chosen out
3940 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
3942 o Security improvements:
3943 - Start making directory caches retain old routerinfos, so soon
3944 clients can start asking by digest of descriptor rather than by
3945 fingerprint of server.
3946 - Add half our entropy from RAND_poll in OpenSSL. This knows how
3947 to use egd (if present), openbsd weirdness (if present), vms/os2
3948 weirdness (if we ever port there), and more in the future.
3950 o Bugfixes on 0.1.0.x:
3951 - Do round-robin writes of at most 16 kB per write. This might be
3952 more fair on loaded Tor servers, and it might resolve our Windows
3953 crash bug. It might also slow things down.
3954 - Our TLS handshakes were generating a single public/private
3955 keypair for the TLS context, rather than making a new one for
3956 each new connections. Oops. (But we were still rotating them
3957 periodically, so it's not so bad.)
3958 - When we were cannibalizing a circuit with a particular exit
3959 node in mind, we weren't checking to see if that exit node was
3960 already present earlier in the circuit. Oops.
3961 - When a Tor server's IP changes (e.g. from a dyndns address),
3962 upload a new descriptor so clients will learn too.
3963 - Really busy servers were keeping enough circuits open on stable
3964 connections that they were wrapping around the circuit_id
3965 space. (It's only two bytes.) This exposed a bug where we would
3966 feel free to reuse a circuit_id even if it still exists but has
3967 been marked for close. Try to fix this bug. Some bug remains.
3968 - If we would close a stream early (e.g. it asks for a .exit that
3969 we know would refuse it) but the LeaveStreamsUnattached config
3970 option is set by the controller, then don't close it.
3972 o Bugfixes on 0.1.1.8-alpha:
3973 - Fix a big pile of memory leaks, some of them serious.
3974 - Do not try to download a routerdesc if we would immediately reject
3976 - Resume inserting a newline between all router descriptors when
3977 generating (old style) signed directories, since our spec says
3979 - When providing content-type application/octet-stream for
3980 server descriptors using .z, we were leaving out the
3981 content-encoding header. Oops. (Everything tolerated this just
3982 fine, but that doesn't mean we need to be part of the problem.)
3983 - Fix a potential seg fault in getconf and getinfo using version 1
3984 of the controller protocol.
3985 - Avoid crash: do not check whether DirPort is reachable when we
3986 are suppressing it because of hibernation.
3987 - Make --hash-password not crash on exit.
3990 Changes in version 0.1.1.8-alpha - 2005-10-07
3991 o New features (major):
3992 - Clients don't download or use the directory anymore. Now they
3993 download and use network-statuses from the trusted dirservers,
3994 and fetch individual server descriptors as needed from mirrors.
3995 See dir-spec.txt for all the gory details.
3996 - Be more conservative about whether to advertise our DirPort.
3997 The main change is to not advertise if we're running at capacity
3998 and either a) we could hibernate or b) our capacity is low and
3999 we're using a default DirPort.
4000 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
4002 o New features (minor):
4003 - Try to be smart about when to retry network-status and
4004 server-descriptor fetches. Still needs some tuning.
4005 - Stop parsing, storing, or using running-routers output (but
4006 mirrors still cache and serve it).
4007 - Consider a threshold of versioning dirservers (dirservers who have
4008 an opinion about which Tor versions are still recommended) before
4009 deciding whether to warn the user that he's obsolete.
4010 - Dirservers can now reject/invalidate by key and IP, with the
4011 config options "AuthDirInvalid" and "AuthDirReject". This is
4012 useful since currently we automatically list servers as running
4013 and usable even if we know they're jerks.
4014 - Provide dire warnings to any users who set DirServer; move it out
4015 of torrc.sample and into torrc.complete.
4016 - Add MyFamily to torrc.sample in the server section.
4017 - Add nicknames to the DirServer line, so we can refer to them
4018 without requiring all our users to memorize their IP addresses.
4019 - When we get an EOF or a timeout on a directory connection, note
4020 how many bytes of serverdesc we are dropping. This will help
4021 us determine whether it is smart to parse incomplete serverdesc
4023 - Add a new function to "change pseudonyms" -- that is, to stop
4024 using any currently-dirty circuits for new streams, so we don't
4025 link new actions to old actions. Currently it's only called on
4026 HUP (or SIGNAL RELOAD).
4027 - On sighup, if UseHelperNodes changed to 1, use new circuits.
4028 - Start using RAND_bytes rather than RAND_pseudo_bytes from
4029 OpenSSL. Also, reseed our entropy every hour, not just at
4030 startup. And entropy in 512-bit chunks, not 160-bit chunks.
4032 o Fixes on 0.1.1.7-alpha:
4033 - Nobody ever implemented EVENT_ADDRMAP for control protocol
4034 version 0, so don't let version 0 controllers ask for it.
4035 - If you requested something with too many newlines via the
4036 v1 controller protocol, you could crash tor.
4037 - Fix a number of memory leaks, including some pretty serious ones.
4038 - Re-enable DirPort testing again, so Tor servers will be willing
4039 to advertise their DirPort if it's reachable.
4040 - On TLS handshake, only check the other router's nickname against
4041 its expected nickname if is_named is set.
4043 o Fixes forward-ported from 0.1.0.15:
4044 - Don't crash when we don't have any spare file descriptors and we
4045 try to spawn a dns or cpu worker.
4046 - Make the numbers in read-history and write-history into uint64s,
4047 so they don't overflow and publish negatives in the descriptor.
4050 - For the OS X package's modified privoxy config file, comment
4051 out the "logfile" line so we don't log everything passed
4053 - We were whining about using socks4 or socks5-with-local-lookup
4054 even when it's an IP in the "virtual" range we designed exactly
4056 - We were leaking some memory every time the client changes IPs.
4057 - Never call free() on tor_malloc()d memory. This will help us
4058 use dmalloc to detect memory leaks.
4059 - Check for named servers when looking them up by nickname;
4060 warn when we'recalling a non-named server by its nickname;
4061 don't warn twice about the same name.
4062 - Try to list MyFamily elements by key, not by nickname, and warn
4063 if we've not heard of the server.
4064 - Make windows platform detection (uname equivalent) smarter.
4065 - It turns out sparc64 doesn't like unaligned access either.
4068 Changes in version 0.1.0.15 - 2005-09-23
4069 o Bugfixes on 0.1.0.x:
4070 - Reject ports 465 and 587 (spam targets) in default exit policy.
4071 - Don't crash when we don't have any spare file descriptors and we
4072 try to spawn a dns or cpu worker.
4073 - Get rid of IgnoreVersion undocumented config option, and make us
4074 only warn, never exit, when we're running an obsolete version.
4075 - Don't try to print a null string when your server finds itself to
4076 be unreachable and the Address config option is empty.
4077 - Make the numbers in read-history and write-history into uint64s,
4078 so they don't overflow and publish negatives in the descriptor.
4079 - Fix a minor memory leak in smartlist_string_remove().
4080 - We were only allowing ourselves to upload a server descriptor at
4081 most every 20 minutes, even if it changed earlier than that.
4082 - Clean up log entries that pointed to old URLs.
4085 Changes in version 0.1.1.7-alpha - 2005-09-14
4086 o Fixes on 0.1.1.6-alpha:
4087 - Exit servers were crashing when people asked them to make a
4088 connection to an address not in their exit policy.
4089 - Looking up a non-existent stream for a v1 control connection would
4091 - Fix a seg fault if we ask a dirserver for a descriptor by
4092 fingerprint but he doesn't know about him.
4093 - SETCONF was appending items to linelists, not clearing them.
4094 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
4095 out and refuse the setconf if it would fail.
4096 - Downgrade the dirserver log messages when whining about
4100 - Add Peter Palfrader's check-tor script to tor/contrib/
4101 It lets you easily check whether a given server (referenced by
4102 nickname) is reachable by you.
4103 - Numerous changes to move towards client-side v2 directories. Not
4107 - If the user gave tor an odd number of command-line arguments,
4108 we were silently ignoring the last one. Now we complain and fail.
4109 [This wins the oldest-bug prize -- this bug has been present since
4110 November 2002, as released in Tor 0.0.0.]
4111 - Do not use unaligned memory access on alpha, mips, or mipsel.
4112 It *works*, but is very slow, so we treat them as if it doesn't.
4113 - Retry directory requests if we fail to get an answer we like
4114 from a given dirserver (we were retrying before, but only if
4115 we fail to connect).
4116 - When writing the RecommendedVersions line, sort them first.
4117 - When the client asked for a rendezvous port that the hidden
4118 service didn't want to provide, we were sending an IP address
4119 back along with the end cell. Fortunately, it was zero. But stop
4121 - Correct "your server is reachable" log entries to indicate that
4122 it was self-testing that told us so.
4125 Changes in version 0.1.1.6-alpha - 2005-09-09
4126 o Fixes on 0.1.1.5-alpha:
4127 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
4128 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
4129 - Fix bug with tor_memmem finding a match at the end of the string.
4130 - Make unit tests run without segfaulting.
4131 - Resolve some solaris x86 compile warnings.
4132 - Handle duplicate lines in approved-routers files without warning.
4133 - Fix bug where as soon as a server refused any requests due to his
4134 exit policy (e.g. when we ask for localhost and he tells us that's
4135 127.0.0.1 and he won't do it), we decided he wasn't obeying his
4136 exit policy using him for any exits.
4137 - Only do openssl hardware accelerator stuff if openssl version is
4140 o New controller features/fixes:
4141 - Add a "RESETCONF" command so you can set config options like
4142 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
4143 a config option in the torrc with no value, then it clears it
4144 entirely (rather than setting it to its default).
4145 - Add a "GETINFO config-file" to tell us where torrc is.
4146 - Avoid sending blank lines when GETINFO replies should be empty.
4147 - Add a QUIT command for the controller (for using it manually).
4148 - Fix a bug in SAVECONF that was adding default dirservers and
4149 other redundant entries to the torrc file.
4151 o Start on the new directory design:
4152 - Generate, publish, cache, serve new network-status format.
4153 - Publish individual descriptors (by fingerprint, by "all", and by
4155 - Publish client and server recommended versions separately.
4156 - Allow tor_gzip_uncompress() to handle multiple concatenated
4157 compressed strings. Serve compressed groups of router
4158 descriptors. The compression logic here could be more
4160 - Distinguish v1 authorities (all currently trusted directories)
4161 from v2 authorities (all trusted directories).
4162 - Change DirServers config line to note which dirs are v1 authorities.
4163 - Add configuration option "V1AuthoritativeDirectory 1" which
4164 moria1, moria2, and tor26 should set.
4165 - Remove option when getting directory cache to see whether they
4166 support running-routers; they all do now. Replace it with one
4167 to see whether caches support v2 stuff.
4170 - Dirservers now do their own external reachability testing of each
4171 Tor server, and only list them as running if they've been found to
4172 be reachable. We also send back warnings to the server's logs if
4173 it uploads a descriptor that we already believe is unreachable.
4174 - Implement exit enclaves: if we know an IP address for the
4175 destination, and there's a running Tor server at that address
4176 which allows exit to the destination, then extend the circuit to
4177 that exit first. This provides end-to-end encryption and end-to-end
4178 authentication. Also, if the user wants a .exit address or enclave,
4179 use 4 hops rather than 3, and cannibalize a general circ for it
4181 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
4182 controller. Also, rotate dns and cpu workers if the controller
4183 changes options that will affect them; and initialize the dns
4184 worker cache tree whether or not we start out as a server.
4185 - Only upload a new server descriptor when options change, 18
4186 hours have passed, uptime is reset, or bandwidth changes a lot.
4187 - Check [X-]Forwarded-For headers in HTTP requests when generating
4188 log messages. This lets people run dirservers (and caches) behind
4189 Apache but still know which IP addresses are causing warnings.
4191 o Config option changes:
4192 - Replace (Fascist)Firewall* config options with a new
4193 ReachableAddresses option that understands address policies.
4194 For example, "ReachableAddresses *:80,*:443"
4195 - Get rid of IgnoreVersion undocumented config option, and make us
4196 only warn, never exit, when we're running an obsolete version.
4197 - Make MonthlyAccountingStart config option truly obsolete now.
4200 - Reject ports 465 and 587 in the default exit policy, since
4201 people have started using them for spam too.
4202 - It turns out we couldn't bootstrap a network since we added
4203 reachability detection in 0.1.0.1-rc. Good thing the Tor network
4204 has never gone down. Add an AssumeReachable config option to let
4205 servers and dirservers bootstrap. When we're trying to build a
4206 high-uptime or high-bandwidth circuit but there aren't enough
4207 suitable servers, try being less picky rather than simply failing.
4208 - Our logic to decide if the OR we connected to was the right guy
4209 was brittle and maybe open to a mitm for unverified routers.
4210 - We weren't cannibalizing circuits correctly for
4211 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
4212 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
4213 build those from scratch. This should make hidden services faster.
4214 - Predict required circuits better, with an eye toward making hidden
4215 services faster on the service end.
4216 - Retry streams if the exit node sends back a 'misc' failure. This
4217 should result in fewer random failures. Also, after failing
4218 from resolve failed or misc, reset the num failures, so we give
4219 it a fair shake next time we try.
4220 - Clean up the rendezvous warn log msgs, and downgrade some to info.
4221 - Reduce severity on logs about dns worker spawning and culling.
4222 - When we're shutting down and we do something like try to post a
4223 server descriptor or rendezvous descriptor, don't complain that
4224 we seem to be unreachable. Of course we are, we're shutting down.
4225 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
4226 We don't use them yet, but maybe one day our DNS resolver will be
4227 able to discover them.
4228 - Make ContactInfo mandatory for authoritative directory servers.
4229 - Require server descriptors to list IPv4 addresses -- hostnames
4230 are no longer allowed. This also fixes some potential security
4231 problems with people providing hostnames as their address and then
4232 preferentially resolving them to partition users.
4233 - Change log line for unreachability to explicitly suggest /etc/hosts
4234 as the culprit. Also make it clearer what IP address and ports we're
4235 testing for reachability.
4236 - Put quotes around user-supplied strings when logging so users are
4237 more likely to realize if they add bad characters (like quotes)
4239 - Let auth dir servers start without specifying an Address config
4241 - Make unit tests (and other invocations that aren't the real Tor)
4242 run without launching listeners, creating subdirectories, and so on.
4245 Changes in version 0.1.1.5-alpha - 2005-08-08
4246 o Bugfixes included in 0.1.0.14.
4248 o Bugfixes on 0.1.0.x:
4249 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
4250 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
4251 it would silently using ignore the 6668.
4254 Changes in version 0.1.0.14 - 2005-08-08
4255 o Bugfixes on 0.1.0.x:
4256 - Fix the other half of the bug with crypto handshakes
4258 - Fix an assert trigger if you send a 'signal term' via the
4259 controller when it's listening for 'event info' messages.
4262 Changes in version 0.1.1.4-alpha - 2005-08-04
4263 o Bugfixes included in 0.1.0.13.
4266 - Improve tor_gettimeofday() granularity on windows.
4267 - Make clients regenerate their keys when their IP address changes.
4268 - Implement some more GETINFO goodness: expose helper nodes, config
4269 options, getinfo keys.
4272 Changes in version 0.1.0.13 - 2005-08-04
4273 o Bugfixes on 0.1.0.x:
4274 - Fix a critical bug in the security of our crypto handshakes.
4275 - Fix a size_t underflow in smartlist_join_strings2() that made
4276 it do bad things when you hand it an empty smartlist.
4277 - Fix Windows installer to ship Tor license (thanks to Aphex for
4278 pointing out this oversight) and put a link to the doc directory
4280 - Explicitly set no-unaligned-access for sparc: it turns out the
4281 new gcc's let you compile broken code, but that doesn't make it
4285 Changes in version 0.1.1.3-alpha - 2005-07-23
4286 o Bugfixes on 0.1.1.2-alpha:
4287 - Fix a bug in handling the controller's "post descriptor"
4289 - Fix several bugs in handling the controller's "extend circuit"
4291 - Fix a bug in handling the controller's "stream status" event.
4292 - Fix an assert failure if we have a controller listening for
4293 circuit events and we go offline.
4294 - Re-allow hidden service descriptors to publish 0 intro points.
4295 - Fix a crash when generating your hidden service descriptor if
4296 you don't have enough intro points already.
4298 o New features on 0.1.1.2-alpha:
4299 - New controller function "getinfo accounting", to ask how
4300 many bytes we've used in this time period.
4301 - Experimental support for helper nodes: a lot of the risk from
4302 a small static adversary comes because users pick new random
4303 nodes every time they rebuild a circuit. Now users will try to
4304 stick to the same small set of entry nodes if they can. Not
4305 enabled by default yet.
4307 o Bugfixes on 0.1.0.12:
4308 - If you're an auth dir server, always publish your dirport,
4309 even if you haven't yet found yourself to be reachable.
4310 - Fix a size_t underflow in smartlist_join_strings2() that made
4311 it do bad things when you hand it an empty smartlist.
4314 Changes in version 0.1.0.12 - 2005-07-18
4315 o New directory servers:
4316 - tor26 has changed IP address.
4318 o Bugfixes on 0.1.0.x:
4319 - Fix a possible double-free in tor_gzip_uncompress().
4320 - When --disable-threads is set, do not search for or link against
4322 - Don't trigger an assert if an authoritative directory server
4323 claims its dirport is 0.
4324 - Fix bug with removing Tor as an NT service: some people were
4325 getting "The service did not return an error." Thanks to Matt
4329 Changes in version 0.1.1.2-alpha - 2005-07-15
4330 o New directory servers:
4331 - tor26 has changed IP address.
4333 o Bugfixes on 0.1.0.x, crashes/leaks:
4334 - Port the servers-not-obeying-their-exit-policies fix from
4336 - Fix an fd leak in start_daemon().
4337 - On Windows, you can't always reopen a port right after you've
4338 closed it. So change retry_listeners() to only close and re-open
4339 ports that have changed.
4340 - Fix a possible double-free in tor_gzip_uncompress().
4342 o Bugfixes on 0.1.0.x, usability:
4343 - When tor_socketpair() fails in Windows, give a reasonable
4344 Windows-style errno back.
4345 - Let people type "tor --install" as well as "tor -install" when
4347 want to make it an NT service.
4348 - NT service patch from Matt Edman to improve error messages.
4349 - When the controller asks for a config option with an abbreviated
4350 name, give the full name in our response.
4351 - Correct the man page entry on TrackHostExitsExpire.
4352 - Looks like we were never delivering deflated (i.e. compressed)
4353 running-routers lists, even when asked. Oops.
4354 - When --disable-threads is set, do not search for or link against
4357 o Bugfixes on 0.1.1.x:
4358 - Fix a seg fault with autodetecting which controller version is
4362 - New hidden service descriptor format: put a version in it, and
4363 let people specify introduction/rendezvous points that aren't
4364 in "the directory" (which is subjective anyway).
4365 - Allow the DEBUG controller event to work again. Mark certain log
4366 entries as "don't tell this to controllers", so we avoid cycles.
4369 Changes in version 0.1.0.11 - 2005-06-30
4370 o Bugfixes on 0.1.0.x:
4371 - Fix major security bug: servers were disregarding their
4372 exit policies if clients behaved unexpectedly.
4373 - Make OS X init script check for missing argument, so we don't
4374 confuse users who invoke it incorrectly.
4375 - Fix a seg fault in "tor --hash-password foo".
4376 - The MAPADDRESS control command was broken.
4379 Changes in version 0.1.1.1-alpha - 2005-06-29
4381 - Make OS X init script check for missing argument, so we don't
4382 confuse users who invoke it incorrectly.
4383 - Fix a seg fault in "tor --hash-password foo".
4384 - Fix a possible way to DoS dirservers.
4385 - When we complain that your exit policy implicitly allows local or
4386 private address spaces, name them explicitly so operators can
4388 - Make the log message less scary when all the dirservers are
4389 temporarily unreachable.
4390 - We were printing the number of idle dns workers incorrectly when
4394 - Revised controller protocol (version 1) that uses ascii rather
4395 than binary. Add supporting libraries in python and java so you
4396 can use the controller from your applications without caring how
4398 - Spiffy new support for crypto hardware accelerators. Can somebody
4402 Changes in version 0.0.9.10 - 2005-06-16
4403 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
4404 - Refuse relay cells that claim to have a length larger than the
4405 maximum allowed. This prevents a potential attack that could read
4406 arbitrary memory (e.g. keys) from an exit server's process
4410 Changes in version 0.1.0.10 - 2005-06-14
4411 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
4412 libevent before 1.1a.
4415 Changes in version 0.1.0.9-rc - 2005-06-09
4417 - Reset buf->highwater every time buf_shrink() is called, not just on
4418 a successful shrink. This was causing significant memory bloat.
4419 - Fix buffer overflow when checking hashed passwords.
4420 - Security fix: if seeding the RNG on Win32 fails, quit.
4421 - Allow seeding the RNG on Win32 even when you're not running as
4423 - Disable threading on Solaris too. Something is wonky with it,
4424 cpuworkers, and reentrant libs.
4425 - Reenable the part of the code that tries to flush as soon as an
4426 OR outbuf has a full TLS record available. Perhaps this will make
4427 OR outbufs not grow as huge except in rare cases, thus saving lots
4428 of CPU time plus memory.
4429 - Reject malformed .onion addresses rather then passing them on as
4430 normal web requests.
4431 - Adapt patch from Adam Langley: fix possible memory leak in
4432 tor_lookup_hostname().
4433 - Initialize libevent later in the startup process, so the logs are
4434 already established by the time we start logging libevent warns.
4435 - Use correct errno on win32 if libevent fails.
4436 - Check and warn about known-bad/slow libevent versions.
4437 - Pay more attention to the ClientOnly config option.
4438 - Have torctl.in/tor.sh.in check for location of su binary (needed
4440 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
4441 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
4442 HttpProxyAuthenticator
4443 - Stop warning about sigpipes in the logs. We're going to
4444 pretend that getting these occassionally is normal and fine.
4445 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
4447 installer screens; and don't put stuff into StartupItems unless
4448 the user asks you to.
4449 - Require servers that use the default dirservers to have public IP
4450 addresses. We have too many servers that are configured with private
4451 IPs and their admins never notice the log entries complaining that
4452 their descriptors are being rejected.
4453 - Add OSX uninstall instructions. An actual uninstall script will
4457 Changes in version 0.1.0.8-rc - 2005-05-23
4459 - It turns out that kqueue on OS X 10.3.9 was causing kernel
4460 panics. Disable kqueue on all OS X Tors.
4461 - Fix RPM: remove duplicate line accidentally added to the rpm
4463 - Disable threads on openbsd too, since its gethostaddr is not
4465 - Tolerate libevent 0.8 since it still works, even though it's
4467 - Enable building on Red Hat 9.0 again.
4468 - Allow the middle hop of the testing circuit to be running any
4469 version, now that most of them have the bugfix to let them connect
4470 to unknown servers. This will allow reachability testing to work
4471 even when 0.0.9.7-0.0.9.9 become obsolete.
4472 - Handle relay cells with rh.length too large. This prevents
4473 a potential attack that could read arbitrary memory (maybe even
4474 keys) from the exit server's process.
4475 - We screwed up the dirport reachability testing when we don't yet
4476 have a cached version of the directory. Hopefully now fixed.
4477 - Clean up router_load_single_router() (used by the controller),
4478 so it doesn't seg fault on error.
4479 - Fix a minor memory leak when somebody establishes an introduction
4480 point at your Tor server.
4481 - If a socks connection ends because read fails, don't warn that
4482 you're not sending a socks reply back.
4485 - Add HttpProxyAuthenticator config option too, that works like
4486 the HttpsProxyAuthenticator config option.
4487 - Encode hashed controller passwords in hex instead of base64,
4488 to make it easier to write controllers.
4491 Changes in version 0.1.0.7-rc - 2005-05-17
4493 - Fix a bug in the OS X package installer that prevented it from
4494 installing on Tiger.
4495 - Fix a script bug in the OS X package installer that made it
4496 complain during installation.
4497 - Find libevent even if it's hiding in /usr/local/ and your
4498 CFLAGS and LDFLAGS don't tell you to look there.
4499 - Be able to link with libevent as a shared library (the default
4500 after 1.0d), even if it's hiding in /usr/local/lib and even
4501 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
4502 assuming you're running gcc. Otherwise fail and give a useful
4504 - Fix a bug in the RPM packager: set home directory for _tor to
4505 something more reasonable when first installing.
4506 - Free a minor amount of memory that is still reachable on exit.
4509 Changes in version 0.1.0.6-rc - 2005-05-14
4511 - Implement --disable-threads configure option. Disable threads on
4512 netbsd by default, because it appears to have no reentrant resolver
4514 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
4515 release (1.1) detects and disables kqueue if it's broken.
4516 - Append default exit policy before checking for implicit internal
4517 addresses. Now we don't log a bunch of complaints on startup
4518 when using the default exit policy.
4519 - Some people were putting "Address " in their torrc, and they had
4520 a buggy resolver that resolved " " to 0.0.0.0. Oops.
4521 - If DataDir is ~/.tor, and that expands to /.tor, then default to
4522 LOCALSTATEDIR/tor instead.
4523 - Fix fragmented-message bug in TorControl.py.
4524 - Resolve a minor bug which would prevent unreachable dirports
4525 from getting suppressed in the published descriptor.
4526 - When the controller gave us a new descriptor, we weren't resolving
4527 it immediately, so Tor would think its address was 0.0.0.0 until
4528 we fetched a new directory.
4529 - Fix an uppercase/lowercase case error in suppressing a bogus
4530 libevent warning on some Linuxes.
4533 - Begin scrubbing sensitive strings from logs by default. Turn off
4534 the config option SafeLogging if you need to do debugging.
4535 - Switch to a new buffer management algorithm, which tries to avoid
4536 reallocing and copying quite as much. In first tests it looks like
4537 it uses *more* memory on average, but less cpu.
4538 - First cut at support for "create-fast" cells. Clients can use
4539 these when extending to their first hop, since the TLS already
4540 provides forward secrecy and authentication. Not enabled on
4542 - When dirservers refuse a router descriptor, we now log its
4543 contactinfo, platform, and the poster's IP address.
4544 - Call tor_free_all instead of connections_free_all after forking, to
4545 save memory on systems that need to fork.
4546 - Whine at you if you're a server and you don't set your contactinfo.
4547 - Implement --verify-config command-line option to check if your torrc
4548 is valid without actually launching Tor.
4549 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
4550 rather than just rejecting it.
4553 Changes in version 0.1.0.5-rc - 2005-04-27
4555 - Stop trying to print a null pointer if an OR conn fails because
4556 we didn't like its cert.
4558 - Switch our internal buffers implementation to use a ring buffer,
4559 to hopefully improve performance for fast servers a lot.
4560 - Add HttpsProxyAuthenticator support (basic auth only), based
4561 on patch from Adam Langley.
4562 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
4563 the fast servers that have been joining lately.
4564 - Give hidden service accesses extra time on the first attempt,
4565 since 60 seconds is often only barely enough. This might improve
4567 - Improve performance for dirservers: stop re-parsing the whole
4568 directory every time you regenerate it.
4569 - Add more debugging info to help us find the weird dns freebsd
4570 pthreads bug; cleaner debug messages to help track future issues.
4573 Changes in version 0.0.9.9 - 2005-04-23
4574 o Bugfixes on 0.0.9.x:
4575 - If unofficial Tor clients connect and send weird TLS certs, our
4576 Tor server triggers an assert. This release contains a minimal
4577 backport from the broader fix that we put into 0.1.0.4-rc.
4580 Changes in version 0.1.0.4-rc - 2005-04-23
4582 - If unofficial Tor clients connect and send weird TLS certs, our
4583 Tor server triggers an assert. Stop asserting, and start handling
4584 TLS errors better in other situations too.
4585 - When the controller asks us to tell it about all the debug-level
4586 logs, it turns out we were generating debug-level logs while
4587 telling it about them, which turns into a bad loop. Now keep
4588 track of whether you're sending a debug log to the controller,
4589 and don't log when you are.
4590 - Fix the "postdescriptor" feature of the controller interface: on
4591 non-complete success, only say "done" once.
4593 - Clients are now willing to load balance over up to 2mB, not 1mB,
4594 of advertised bandwidth capacity.
4595 - Add a NoPublish config option, so you can be a server (e.g. for
4596 testing running Tor servers in other Tor networks) without
4597 publishing your descriptor to the primary dirservers.
4600 Changes in version 0.1.0.3-rc - 2005-04-08
4601 o Improvements on 0.1.0.2-rc:
4602 - Client now retries when streams end early for 'hibernating' or
4603 'resource limit' reasons, rather than failing them.
4604 - More automated handling for dirserver operators:
4605 - Automatically approve nodes running 0.1.0.2-rc or later,
4606 now that the the reachability detection stuff is working.
4607 - Now we allow two unverified servers with the same nickname
4608 but different keys. But if a nickname is verified, only that
4609 nickname+key are allowed.
4610 - If you're an authdirserver connecting to an address:port,
4611 and it's not the OR you were expecting, forget about that
4612 descriptor. If he *was* the one you were expecting, then forget
4613 about all other descriptors for that address:port.
4614 - Allow servers to publish descriptors from 12 hours in the future.
4615 Corollary: only whine about clock skew from the dirserver if
4616 he's a trusted dirserver (since now even verified servers could
4617 have quite wrong clocks).
4618 - Adjust maximum skew and age for rendezvous descriptors: let skew
4619 be 48 hours rather than 90 minutes.
4620 - Efficiency improvements:
4621 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
4622 it much faster to look up a circuit for each relay cell.
4623 - Remove most calls to assert_all_pending_dns_resolves_ok(),
4624 since they're eating our cpu on exit nodes.
4625 - Stop wasting time doing a case insensitive comparison for every
4626 dns name every time we do any lookup. Canonicalize the names to
4627 lowercase and be done with it.
4628 - Start sending 'truncated' cells back rather than destroy cells,
4629 if the circuit closes in front of you. This means we won't have
4630 to abandon partially built circuits.
4631 - Only warn once per nickname from add_nickname_list_to_smartlist
4632 per failure, so an entrynode or exitnode choice that's down won't
4634 - Put a note in the torrc about abuse potential with the default
4636 - Revise control spec and implementation to allow all log messages to
4637 be sent to controller with their severities intact (suggested by
4638 Matt Edman). Update TorControl to handle new log event types.
4639 - Provide better explanation messages when controller's POSTDESCRIPTOR
4641 - Stop putting nodename in the Platform string in server descriptors.
4642 It doesn't actually help, and it is confusing/upsetting some people.
4644 o Bugfixes on 0.1.0.2-rc:
4645 - We were printing the host mask wrong in exit policies in server
4646 descriptors. This isn't a critical bug though, since we were still
4647 obeying the exit policy internally.
4648 - Fix Tor when compiled with libevent but without pthreads: move
4649 connection_unregister() from _connection_free() to
4651 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
4652 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
4653 when we look through the connection array, we'll find any of the
4654 cpu/dnsworkers. This is no good.
4656 o Bugfixes on 0.0.9.8:
4657 - Fix possible bug on threading platforms (e.g. win32) which was
4658 leaking a file descriptor whenever a cpuworker or dnsworker died.
4659 - When using preferred entry or exit nodes, ignore whether the
4660 circuit wants uptime or capacity. They asked for the nodes, they
4662 - chdir() to your datadirectory at the *end* of the daemonize process,
4663 not the beginning. This was a problem because the first time you
4664 run tor, if your datadir isn't there, and you have runasdaemon set
4665 to 1, it will try to chdir to it before it tries to create it. Oops.
4666 - Handle changed router status correctly when dirserver reloads
4667 fingerprint file. We used to be dropping all unverified descriptors
4668 right then. The bug was hidden because we would immediately
4669 fetch a directory from another dirserver, which would include the
4670 descriptors we just dropped.
4671 - When we're connecting to an OR and he's got a different nickname/key
4672 than we were expecting, only complain loudly if we're an OP or a
4673 dirserver. Complaining loudly to the OR admins just confuses them.
4674 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
4675 artificially capped at 500kB.
4678 Changes in version 0.0.9.8 - 2005-04-07
4679 o Bugfixes on 0.0.9.x:
4680 - We have a bug that I haven't found yet. Sometimes, very rarely,
4681 cpuworkers get stuck in the 'busy' state, even though the cpuworker
4682 thinks of itself as idle. This meant that no new circuits ever got
4683 established. Here's a workaround to kill any cpuworker that's been
4684 busy for more than 100 seconds.
4687 Changes in version 0.1.0.2-rc - 2005-04-01
4688 o Bugfixes on 0.1.0.1-rc:
4689 - Fixes on reachability detection:
4690 - Don't check for reachability while hibernating.
4691 - If ORPort is reachable but DirPort isn't, still publish the
4692 descriptor, but zero out DirPort until it's found reachable.
4693 - When building testing circs for ORPort testing, use only
4694 high-bandwidth nodes, so fewer circuits fail.
4695 - Complain about unreachable ORPort separately from unreachable
4696 DirPort, so the user knows what's going on.
4697 - Make sure we only conclude ORPort reachability if we didn't
4698 initiate the conn. Otherwise we could falsely conclude that
4699 we're reachable just because we connected to the guy earlier
4700 and he used that same pipe to extend to us.
4701 - Authdirservers shouldn't do ORPort reachability detection,
4702 since they're in clique mode, so it will be rare to find a
4703 server not already connected to them.
4704 - When building testing circuits, always pick middle hops running
4705 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
4706 bug. (This is a kludge; it will go away when 0.0.9.x becomes
4708 - When we decide we're reachable, actually publish our descriptor
4710 - Fix bug in redirectstream in the controller.
4711 - Fix the state descriptor strings so logs don't claim edge streams
4712 are in a different state than they actually are.
4713 - Use recent libevent features when possible (this only really affects
4714 win32 and osx right now, because the new libevent with these
4715 features hasn't been released yet). Add code to suppress spurious
4717 - Prevent possible segfault in connection_close_unattached_ap().
4718 - Fix newlines on torrc in win32.
4719 - Improve error msgs when tor-resolve fails.
4721 o Improvements on 0.0.9.x:
4722 - New experimental script tor/contrib/ExerciseServer.py (needs more
4723 work) that uses the controller interface to build circuits and
4724 fetch pages over them. This will help us bootstrap servers that
4725 have lots of capacity but haven't noticed it yet.
4726 - New experimental script tor/contrib/PathDemo.py (needs more work)
4727 that uses the controller interface to let you choose whole paths
4729 "<hostname>.<path,separated by dots>.<length of path>.path"
4730 - When we've connected to an OR and handshaked but didn't like
4731 the result, we were closing the conn without sending destroy
4732 cells back for pending circuits. Now send those destroys.
4735 Changes in version 0.0.9.7 - 2005-04-01
4736 o Bugfixes on 0.0.9.x:
4737 - Fix another race crash bug (thanks to Glenn Fink for reporting).
4738 - Compare identity to identity, not to nickname, when extending to
4739 a router not already in the directory. This was preventing us from
4740 extending to unknown routers. Oops.
4741 - Make sure to create OS X Tor user in <500 range, so we aren't
4742 creating actual system users.
4743 - Note where connection-that-hasn't-sent-end was marked, and fix
4744 a few really loud instances of this harmless bug (it's fixed more
4748 Changes in version 0.1.0.1-rc - 2005-03-28
4750 - Add reachability testing. Your Tor server will automatically try
4751 to see if its ORPort and DirPort are reachable from the outside,
4752 and it won't upload its descriptor until it decides they are.
4753 - Handle unavailable hidden services better. Handle slow or busy
4754 hidden services better.
4755 - Add support for CONNECTing through https proxies, with "HttpsProxy"
4757 - New exit policy: accept most low-numbered ports, rather than
4758 rejecting most low-numbered ports.
4759 - More Tor controller support (still experimental). See
4760 http://tor.eff.org/doc/control-spec.txt for all the new features,
4761 including signals to emulate unix signals from any platform;
4762 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
4763 closestream; closecircuit; etc.
4764 - Make nt services work and start on startup on win32 (based on
4765 patch by Matt Edman).
4766 - Add a new AddressMap config directive to rewrite incoming socks
4767 addresses. This lets you, for example, declare an implicit
4768 required exit node for certain sites.
4769 - Add a new TrackHostExits config directive to trigger addressmaps
4770 for certain incoming socks addresses -- for sites that break when
4771 your exit keeps changing (based on patch by Mike Perry).
4772 - Redo the client-side dns cache so it's just an addressmap too.
4773 - Notice when our IP changes, and reset stats/uptime/reachability.
4774 - When an application is using socks5, give him the whole variety of
4775 potential socks5 responses (connect refused, host unreachable, etc),
4776 rather than just "success" or "failure".
4777 - A more sane version numbering system. See
4778 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
4779 - New contributed script "exitlist": a simple python script to
4780 parse directories and find Tor nodes that exit to listed
4782 - New contributed script "privoxy-tor-toggle" to toggle whether
4783 Privoxy uses Tor. Seems to be configured for Debian by default.
4784 - Report HTTP reasons to client when getting a response from directory
4785 servers -- so you can actually know what went wrong.
4786 - New config option MaxAdvertisedBandwidth which lets you advertise
4787 a low bandwidthrate (to not attract as many circuits) while still
4788 allowing a higher bandwidthrate in reality.
4790 o Robustness/stability fixes:
4791 - Make Tor use Niels Provos's libevent instead of its current
4792 poll-but-sometimes-select mess. This will let us use faster async
4793 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
4795 - pthread support now too. This was forced because when we forked,
4796 we ended up wasting a lot of duplicate ram over time. Also switch
4797 to foo_r versions of some library calls to allow reentry and
4799 - Better handling for heterogeneous / unreliable nodes:
4800 - Annotate circuits w/ whether they aim to contain high uptime nodes
4801 and/or high capacity nodes. When building circuits, choose
4803 - This means that every single node in an intro rend circuit,
4804 not just the last one, will have a minimum uptime.
4805 - New config option LongLivedPorts to indicate application streams
4806 that will want high uptime circuits.
4807 - Servers reset uptime when a dir fetch entirely fails. This
4808 hopefully reflects stability of the server's network connectivity.
4809 - If somebody starts his tor server in Jan 2004 and then fixes his
4810 clock, don't make his published uptime be a year.
4811 - Reset published uptime when you wake up from hibernation.
4812 - Introduce a notion of 'internal' circs, which are chosen without
4813 regard to the exit policy of the last hop. Intro and rendezvous
4814 circs must be internal circs, to avoid leaking information. Resolve
4815 and connect streams can use internal circs if they want.
4816 - New circuit pooling algorithm: make sure to have enough circs around
4817 to satisfy any predicted ports, and also make sure to have 2 internal
4818 circs around if we've required internal circs lately (and with high
4819 uptime if we've seen that lately too).
4820 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
4821 which describes how often we retry making new circuits if current
4822 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
4823 how long we're willing to make use of an already-dirty circuit.
4824 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
4825 circ as necessary, if there are any completed ones lying around
4826 when we try to launch one.
4827 - Make hidden services try to establish a rendezvous for 30 seconds,
4828 rather than for n (where n=3) attempts to build a circuit.
4829 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
4830 "ShutdownWaitLength".
4831 - Try to be more zealous about calling connection_edge_end when
4832 things go bad with edge conns in connection.c.
4833 - Revise tor-spec to add more/better stream end reasons.
4834 - Revise all calls to connection_edge_end to avoid sending "misc",
4835 and to take errno into account where possible.
4838 - Fix a race condition that can trigger an assert, when we have a
4839 pending create cell and an OR connection fails right then.
4840 - Fix several double-mark-for-close bugs, e.g. where we were finding
4841 a conn for a cell even if that conn is already marked for close.
4842 - Make sequence of log messages when starting on win32 with no config
4843 file more reasonable.
4844 - When choosing an exit node for a new non-internal circ, don't take
4845 into account whether it'll be useful for any pending x.onion
4846 addresses -- it won't.
4847 - Turn addr_policy_compare from a tristate to a quadstate; this should
4848 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
4849 for google.com" problem.
4850 - Make "platform" string in descriptor more accurate for Win32 servers,
4851 so it's not just "unknown platform".
4852 - Fix an edge case in parsing config options (thanks weasel).
4853 If they say "--" on the commandline, it's not an option.
4854 - Reject odd-looking addresses at the client (e.g. addresses that
4855 contain a colon), rather than having the server drop them because
4857 - tor-resolve requests were ignoring .exit if there was a working circuit
4858 they could use instead.
4859 - REUSEADDR on normal platforms means you can rebind to the port
4860 right after somebody else has let it go. But REUSEADDR on win32
4861 means to let you bind to the port _even when somebody else
4862 already has it bound_! So, don't do that on Win32.
4863 - Change version parsing logic: a version is "obsolete" if it is not
4864 recommended and (1) there is a newer recommended version in the
4865 same series, or (2) there are no recommended versions in the same
4866 series, but there are some recommended versions in a newer series.
4867 A version is "new" if it is newer than any recommended version in
4869 - Stop most cases of hanging up on a socks connection without sending
4873 - Require BandwidthRate to be at least 20kB/s for servers.
4874 - When a dirserver causes you to give a warn, mention which dirserver
4876 - New config option DirAllowPrivateAddresses for authdirservers.
4877 Now by default they refuse router descriptors that have non-IP or
4878 private-IP addresses.
4879 - Stop publishing socksport in the directory, since it's not
4880 actually meant to be public. For compatibility, publish a 0 there
4882 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
4883 smart" value, that is low for servers and high for clients.
4884 - If our clock jumps forward by 100 seconds or more, assume something
4885 has gone wrong with our network and abandon all not-yet-used circs.
4886 - Warn when exit policy implicitly allows local addresses.
4887 - If we get an incredibly skewed timestamp from a dirserver mirror
4888 that isn't a verified OR, don't warn -- it's probably him that's
4890 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
4891 cookies to disk and doesn't log each web request to disk. (Thanks
4892 to Brett Carrington for pointing this out.)
4893 - When a client asks us for a dir mirror and we don't have one,
4894 launch an attempt to get a fresh one.
4895 - If we're hibernating and we get a SIGINT, exit immediately.
4896 - Add --with-dmalloc ./configure option, to track memory leaks.
4897 - And try to free all memory on closing, so we can detect what
4899 - Cache local dns resolves correctly even when they're .exit
4901 - Give a better warning when some other server advertises an
4902 ORPort that is actually an apache running ssl.
4903 - Add "opt hibernating 1" to server descriptor to make it clearer
4904 whether the server is hibernating.
4907 Changes in version 0.0.9.6 - 2005-03-24
4908 o Bugfixes on 0.0.9.x (crashes and asserts):
4909 - Add new end stream reasons to maintainance branch. Fix bug where
4910 reason (8) could trigger an assert. Prevent bug from recurring.
4911 - Apparently win32 stat wants paths to not end with a slash.
4912 - Fix assert triggers in assert_cpath_layer_ok(), where we were
4913 blowing away the circuit that conn->cpath_layer points to, then
4914 checking to see if the circ is well-formed. Backport check to make
4915 sure we dont use the cpath on a closed connection.
4916 - Prevent circuit_resume_edge_reading_helper() from trying to package
4917 inbufs for marked-for-close streams.
4918 - Don't crash on hup if your options->address has become unresolvable.
4919 - Some systems (like OS X) sometimes accept() a connection and tell
4920 you the remote host is 0.0.0.0:0. If this happens, due to some
4921 other mis-features, we get confused; so refuse the conn for now.
4923 o Bugfixes on 0.0.9.x (other):
4924 - Fix harmless but scary "Unrecognized content encoding" warn message.
4925 - Add new stream error reason: TORPROTOCOL reason means "you are not
4926 speaking a version of Tor I understand; say bye-bye to your stream."
4927 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
4928 into the future, now that we are more tolerant of skew. This
4929 resolves a bug where a Tor server would refuse to cache a directory
4930 because all the directories it gets are too far in the future;
4931 yet the Tor server never logs any complaints about clock skew.
4932 - Mac packaging magic: make man pages useable, and do not overwrite
4933 existing torrc files.
4934 - Make OS X log happily to /var/log/tor/tor.log
4937 Changes in version 0.0.9.5 - 2005-02-22
4938 o Bugfixes on 0.0.9.x:
4939 - Fix an assert race at exit nodes when resolve requests fail.
4940 - Stop picking unverified dir mirrors--it only leads to misery.
4941 - Patch from Matt Edman to make NT services work better. Service
4942 support is still not compiled into the executable by default.
4943 - Patch from Dmitri Bely so the Tor service runs better under
4944 the win32 SYSTEM account.
4945 - Make tor-resolve actually work (?) on Win32.
4946 - Fix a sign bug when getrlimit claims to have 4+ billion
4947 file descriptors available.
4948 - Stop refusing to start when bandwidthburst == bandwidthrate.
4949 - When create cells have been on the onion queue more than five
4950 seconds, just send back a destroy and take them off the list.
4953 Changes in version 0.0.9.4 - 2005-02-03
4954 o Bugfixes on 0.0.9:
4955 - Fix an assert bug that took down most of our servers: when
4956 a server claims to have 1 GB of bandwidthburst, don't
4958 - Don't crash as badly if we have spawned the max allowed number
4959 of dnsworkers, or we're out of file descriptors.
4960 - Block more file-sharing ports in the default exit policy.
4961 - MaxConn is now automatically set to the hard limit of max
4962 file descriptors we're allowed (ulimit -n), minus a few for
4964 - Give a clearer message when servers need to raise their
4965 ulimit -n when they start running out of file descriptors.
4966 - SGI Compatibility patches from Jan Schaumann.
4967 - Tolerate a corrupt cached directory better.
4968 - When a dirserver hasn't approved your server, list which one.
4969 - Go into soft hibernation after 95% of the bandwidth is used,
4970 not 99%. This is especially important for daily hibernators who
4971 have a small accounting max. Hopefully it will result in fewer
4972 cut connections when the hard hibernation starts.
4973 - Load-balance better when using servers that claim more than
4974 800kB/s of capacity.
4975 - Make NT services work (experimental, only used if compiled in).
4978 Changes in version 0.0.9.3 - 2005-01-21
4979 o Bugfixes on 0.0.9:
4980 - Backport the cpu use fixes from main branch, so busy servers won't
4981 need as much processor time.
4982 - Work better when we go offline and then come back, or when we
4983 run Tor at boot before the network is up. We do this by
4984 optimistically trying to fetch a new directory whenever an
4985 application request comes in and we think we're offline -- the
4986 human is hopefully a good measure of when the network is back.
4987 - Backport some minimal hidserv bugfixes: keep rend circuits open as
4988 long as you keep using them; actually publish hidserv descriptors
4989 shortly after they change, rather than waiting 20-40 minutes.
4990 - Enable Mac startup script by default.
4991 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
4992 - When you update AllowUnverifiedNodes or FirewallPorts via the
4993 controller's setconf feature, we were always appending, never
4995 - When you update HiddenServiceDir via setconf, it was screwing up
4996 the order of reading the lines, making it fail.
4997 - Do not rewrite a cached directory back to the cache; otherwise we
4998 will think it is recent and not fetch a newer one on startup.
4999 - Workaround for webservers that lie about Content-Encoding: Tor
5000 now tries to autodetect compressed directories and compression
5001 itself. This lets us Proxypass dir fetches through apache.
5004 Changes in version 0.0.9.2 - 2005-01-04
5005 o Bugfixes on 0.0.9 (crashes and asserts):
5006 - Fix an assert on startup when the disk is full and you're logging
5008 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
5009 style address, then we'd crash.
5010 - Fix an assert trigger when the running-routers string we get from
5011 a dirserver is broken.
5012 - Make worker threads start and run on win32. Now win32 servers
5014 - Bandaid (not actually fix, but now it doesn't crash) an assert
5015 where the dns worker dies mysteriously and the main Tor process
5016 doesn't remember anything about the address it was resolving.
5018 o Bugfixes on 0.0.9 (Win32):
5019 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
5020 name out of the warning/assert messages.
5021 - Fix a superficial "unhandled error on read" bug on win32.
5022 - The win32 installer no longer requires a click-through for our
5023 license, since our Free Software license grants rights but does not
5025 - Win32: When connecting to a dirserver fails, try another one
5026 immediately. (This was already working for non-win32 Tors.)
5027 - Stop trying to parse $HOME on win32 when hunting for default
5029 - Make tor-resolve.c work on win32 by calling network_init().
5031 o Bugfixes on 0.0.9 (other):
5032 - Make 0.0.9.x build on Solaris again.
5033 - Due to a fencepost error, we were blowing away the \n when reporting
5034 confvalue items in the controller. So asking for multiple config
5035 values at once couldn't work.
5036 - When listing circuits that are pending on an opening OR connection,
5037 if we're an OR we were listing circuits that *end* at us as
5038 being pending on every listener, dns/cpu worker, etc. Stop that.
5039 - Dirservers were failing to create 'running-routers' or 'directory'
5040 strings if we had more than some threshold of routers. Fix them so
5041 they can handle any number of routers.
5042 - Fix a superficial "Duplicate mark for close" bug.
5043 - Stop checking for clock skew for OR connections, even for servers.
5044 - Fix a fencepost error that was chopping off the last letter of any
5045 nickname that is the maximum allowed nickname length.
5046 - Update URLs in log messages so they point to the new website.
5047 - Fix a potential problem in mangling server private keys while
5048 writing to disk (not triggered yet, as far as we know).
5049 - Include the licenses for other free software we include in Tor,
5050 now that we're shipping binary distributions more regularly.
5053 Changes in version 0.0.9.1 - 2004-12-15
5054 o Bugfixes on 0.0.9:
5055 - Make hibernation actually work.
5056 - Make HashedControlPassword config option work.
5057 - When we're reporting event circuit status to a controller,
5058 don't use the stream status code.
5061 Changes in version 0.0.9 - 2004-12-12
5063 - Clean up manpage and torrc.sample file.
5064 - Clean up severities and text of log warnings.
5066 - Make servers trigger an assert when they enter hibernation.
5069 Changes in version 0.0.9rc7 - 2004-12-08
5070 o Bugfixes on 0.0.9rc:
5071 - Fix a stack-trashing crash when an exit node begins hibernating.
5072 - Avoid looking at unallocated memory while considering which
5073 ports we need to build circuits to cover.
5074 - Stop a sigpipe: when an 'end' cell races with eof from the app,
5075 we shouldn't hold-open-until-flush if the eof arrived first.
5076 - Fix a bug with init_cookie_authentication() in the controller.
5077 - When recommending new-format log lines, if the upper bound is
5078 LOG_ERR, leave it implicit.
5080 o Bugfixes on 0.0.8.1:
5081 - Fix a whole slew of memory leaks.
5082 - Fix isspace() and friends so they still make Solaris happy
5083 but also so they don't trigger asserts on win32.
5084 - Fix parse_iso_time on platforms without strptime (eg win32).
5085 - win32: tolerate extra "readable" events better.
5086 - win32: when being multithreaded, leave parent fdarray open.
5087 - Make unit tests work on win32.
5090 Changes in version 0.0.9rc6 - 2004-12-06
5091 o Bugfixes on 0.0.9pre:
5092 - Clean up some more integer underflow opportunities (not exploitable
5094 - While hibernating, hup should not regrow our listeners.
5095 - Send an end to the streams we close when we hibernate, rather
5096 than just chopping them off.
5097 - React to eof immediately on non-open edge connections.
5099 o Bugfixes on 0.0.8.1:
5100 - Calculate timeout for waiting for a connected cell from the time
5101 we sent the begin cell, not from the time the stream started. If
5102 it took a long time to establish the circuit, we would time out
5103 right after sending the begin cell.
5104 - Fix router_compare_addr_to_addr_policy: it was not treating a port
5105 of * as always matching, so we were picking reject *:* nodes as
5106 exit nodes too. Oops.
5109 - New circuit building strategy: keep a list of ports that we've
5110 used in the past 6 hours, and always try to have 2 circuits open
5111 or on the way that will handle each such port. Seed us with port
5112 80 so web users won't complain that Tor is "slow to start up".
5113 - Make kill -USR1 dump more useful stats about circuits.
5114 - When warning about retrying or giving up, print the address, so
5115 the user knows which one it's talking about.
5116 - If you haven't used a clean circuit in an hour, throw it away,
5117 just to be on the safe side. (This means after 6 hours a totally
5118 unused Tor client will have no circuits open.)
5121 Changes in version 0.0.9rc5 - 2004-12-01
5122 o Bugfixes on 0.0.8.1:
5123 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
5124 - Let resolve conns retry/expire also, rather than sticking around
5126 - If we are using select, make sure we stay within FD_SETSIZE.
5128 o Bugfixes on 0.0.9pre:
5129 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
5130 but doesn't seem to be currently; thanks to Ilja van Sprundel for
5132 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
5133 instead. Impose minima and maxima for all *Period options; impose
5134 even tighter maxima for fetching if we are a caching dirserver.
5135 Clip rather than rejecting.
5136 - Fetch cached running-routers from servers that serve it (that is,
5137 authdirservers and servers running 0.0.9rc5-cvs or later.)
5140 - Accept *:706 (silc) in default exit policy.
5141 - Implement new versioning format for post 0.1.
5142 - Support "foo.nickname.exit" addresses, to let Alice request the
5143 address "foo" as viewed by exit node "nickname". Based on a patch
5145 - Make tor --version --version dump the cvs Id of every file.
5148 Changes in version 0.0.9rc4 - 2004-11-28
5149 o Bugfixes on 0.0.8.1:
5150 - Make windows sockets actually non-blocking (oops), and handle
5151 win32 socket errors better.
5153 o Bugfixes on 0.0.9rc1:
5154 - Actually catch the -USR2 signal.
5157 Changes in version 0.0.9rc3 - 2004-11-25
5158 o Bugfixes on 0.0.8.1:
5159 - Flush the log file descriptor after we print "Tor opening log file",
5160 so we don't see those messages days later.
5162 o Bugfixes on 0.0.9rc1:
5163 - Make tor-resolve work again.
5164 - Avoid infinite loop in tor-resolve if tor hangs up on it.
5165 - Fix an assert trigger for clients/servers handling resolves.
5168 Changes in version 0.0.9rc2 - 2004-11-24
5169 o Bugfixes on 0.0.9rc1:
5170 - I broke socks5 support while fixing the eof bug.
5171 - Allow unitless bandwidths and intervals; they default to bytes
5173 - New servers don't start out hibernating; they are active until
5174 they run out of bytes, so they have a better estimate of how
5175 long it takes, and so their operators can know they're working.
5178 Changes in version 0.0.9rc1 - 2004-11-23
5179 o Bugfixes on 0.0.8.1:
5180 - Finally fix a bug that's been plaguing us for a year:
5181 With high load, circuit package window was reaching 0. Whenever
5182 we got a circuit-level sendme, we were reading a lot on each
5183 socket, but only writing out a bit. So we would eventually reach
5184 eof. This would be noticed and acted on even when there were still
5185 bytes sitting in the inbuf.
5186 - When poll() is interrupted, we shouldn't believe the revents values.
5188 o Bugfixes on 0.0.9pre6:
5189 - Fix hibernate bug that caused pre6 to be broken.
5190 - Don't keep rephist info for routers that haven't had activity for
5191 24 hours. (This matters now that clients have keys, since we track
5193 - Never call close_temp_logs while validating log options.
5194 - Fix backslash-escaping on tor.sh.in and torctl.in.
5197 - Implement weekly/monthly/daily accounting: now you specify your
5198 hibernation properties by
5199 AccountingMax N bytes|KB|MB|GB|TB
5200 AccountingStart day|week|month [day] HH:MM
5201 Defaults to "month 1 0:00".
5202 - Let bandwidth and interval config options be specified as 5 bytes,
5203 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
5204 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
5205 get back to normal.)
5206 - If your requested entry or exit node has advertised bandwidth 0,
5208 - Be more greedy about filling up relay cells -- we try reading again
5209 once we've processed the stuff we read, in case enough has arrived
5210 to fill the last cell completely.
5211 - Apply NT service patch from Osamu Fujino. Still needs more work.
5214 Changes in version 0.0.9pre6 - 2004-11-15
5215 o Bugfixes on 0.0.8.1:
5216 - Fix assert failure on malformed socks4a requests.
5217 - Use identity comparison, not nickname comparison, to choose which
5218 half of circuit-ID-space each side gets to use. This is needed
5219 because sometimes we think of a router as a nickname, and sometimes
5220 as a hex ID, and we can't predict what the other side will do.
5221 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
5222 write() call will fail and we handle it there.
5223 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
5224 and smartlist_len, which are two major profiling offenders.
5226 o Bugfixes on 0.0.9pre5:
5227 - Fix a bug in read_all that was corrupting config files on windows.
5228 - When we're raising the max number of open file descriptors to
5229 'unlimited', don't log that we just raised it to '-1'.
5230 - Include event code with events, as required by control-spec.txt.
5231 - Don't give a fingerprint when clients do --list-fingerprint:
5232 it's misleading, because it will never be the same again.
5233 - Stop using strlcpy in tor_strndup, since it was slowing us
5235 - Remove warn on startup about missing cached-directory file.
5236 - Make kill -USR1 work again.
5237 - Hibernate if we start tor during the "wait for wakeup-time" phase
5238 of an accounting interval. Log our hibernation plans better.
5239 - Authoritative dirservers now also cache their directory, so they
5240 have it on start-up.
5243 - Fetch running-routers; cache running-routers; compress
5244 running-routers; serve compressed running-routers.z
5245 - Add NSI installer script contributed by J Doe.
5246 - Commit VC6 and VC7 workspace/project files.
5247 - Commit a tor.spec for making RPM files, with help from jbash.
5248 - Add contrib/torctl.in contributed by Glenn Fink.
5249 - Implement the control-spec's SAVECONF command, to write your
5250 configuration to torrc.
5251 - Get cookie authentication for the controller closer to working.
5252 - Include control-spec.txt in the tarball.
5253 - When set_conf changes our server descriptor, upload a new copy.
5254 But don't upload it too often if there are frequent changes.
5255 - Document authentication config in man page, and document signals
5257 - Clean up confusing parts of man page and torrc.sample.
5258 - Make expand_filename handle ~ and ~username.
5259 - Use autoconf to enable largefile support where necessary. Use
5260 ftello where available, since ftell can fail at 2GB.
5261 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
5262 log more informatively.
5263 - Give a slightly more useful output for "tor -h".
5264 - Refuse application socks connections to port 0.
5265 - Check clock skew for verified servers, but allow unverified
5266 servers and clients to have any clock skew.
5267 - Break DirFetchPostPeriod into:
5268 - DirFetchPeriod for fetching full directory,
5269 - StatusFetchPeriod for fetching running-routers,
5270 - DirPostPeriod for posting server descriptor,
5271 - RendPostPeriod for posting hidden service descriptors.
5272 - Make sure the hidden service descriptors are at a random offset
5273 from each other, to hinder linkability.
5276 Changes in version 0.0.9pre5 - 2004-11-09
5277 o Bugfixes on 0.0.9pre4:
5278 - Fix a seg fault in unit tests (doesn't affect main program).
5279 - Fix an assert bug where a hidden service provider would fail if
5280 the first hop of his rendezvous circuit was down.
5281 - Hidden service operators now correctly handle version 1 style
5282 INTRODUCE1 cells (nobody generates them still, so not a critical
5284 - If do_hup fails, actually notice.
5285 - Handle more errnos from accept() without closing the listener.
5286 Some OpenBSD machines were closing their listeners because
5287 they ran out of file descriptors.
5288 - Send resolve cells to exit routers that are running a new
5289 enough version of the resolve code to work right.
5290 - Better handling of winsock includes on non-MSV win32 compilers.
5291 - Some people had wrapped their tor client/server in a script
5292 that would restart it whenever it died. This did not play well
5293 with our "shut down if your version is obsolete" code. Now people
5294 don't fetch a new directory if their local cached version is
5296 - Make our autogen.sh work on ksh as well as bash.
5299 - Hibernation: New config option "AccountingMaxKB" lets you
5300 set how many KBytes per month you want to allow your server to
5301 consume. Rather than spreading those bytes out evenly over the
5302 month, we instead hibernate for some of the month and pop up
5303 at a deterministic time, work until the bytes are consumed, then
5304 hibernate again. Config option "MonthlyAccountingStart" lets you
5305 specify which day of the month your billing cycle starts on.
5306 - Control interface: a separate program can now talk to your
5307 client/server over a socket, and get/set config options, receive
5308 notifications of circuits and streams starting/finishing/dying,
5309 bandwidth used, etc. The next step is to get some GUIs working.
5310 Let us know if you want to help out. See doc/control-spec.txt .
5311 - Ship a contrib/tor-control.py as an example script to interact
5312 with the control port.
5313 - "tor --hash-password zzyxz" will output a salted password for
5314 use in authenticating to the control interface.
5315 - New log format in config:
5316 "Log minsev[-maxsev] stdout|stderr|syslog" or
5317 "Log minsev[-maxsev] file /var/foo"
5320 - DirPolicy config option, to let people reject incoming addresses
5321 from their dirserver.
5322 - "tor --list-fingerprint" will list your identity key fingerprint
5324 - Add "pass" target for RedirectExit, to make it easier to break
5325 out of a sequence of RedirectExit rules.
5326 - Clients now generate a TLS cert too, in preparation for having
5327 them act more like real nodes.
5328 - Ship src/win32/ in the tarball, so people can use it to build.
5329 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
5331 - New "router-status" line in directory, to better bind each verified
5332 nickname to its identity key.
5333 - Deprecate unofficial config option abbreviations, and abbreviations
5334 not on the command line.
5335 - Add a pure-C tor-resolve implementation.
5336 - Use getrlimit and friends to ensure we can reach MaxConn (currently
5337 1024) file descriptors.
5339 o Code security improvements, inspired by Ilja:
5340 - Replace sprintf with snprintf. (I think they were all safe, but
5342 - Replace strcpy/strncpy with strlcpy in more places.
5343 - Avoid strcat; use snprintf or strlcat instead.
5344 - snprintf wrapper with consistent (though not C99) overflow behavior.
5347 Changes in version 0.0.9pre4 - 2004-10-17
5348 o Bugfixes on 0.0.9pre3:
5349 - If the server doesn't specify an exit policy, use the real default
5350 exit policy, not reject *:*.
5351 - Ignore fascistfirewall when uploading/downloading hidden service
5352 descriptors, since we go through Tor for those; and when using
5353 an HttpProxy, since we assume it can reach them all.
5354 - When looking for an authoritative dirserver, use only the ones
5355 configured at boot. Don't bother looking in the directory.
5356 - The rest of the fix for get_default_conf_file() on older win32.
5357 - Make 'Routerfile' config option obsolete.
5360 - New 'MyFamily nick1,...' config option for a server to
5361 specify other servers that shouldn't be used in the same circuit
5362 with it. Only believed if nick1 also specifies us.
5363 - New 'NodeFamily nick1,nick2,...' config option for a client to
5364 specify nodes that it doesn't want to use in the same circuit.
5365 - New 'Redirectexit pattern address:port' config option for a
5366 server to redirect exit connections, e.g. to a local squid.
5369 Changes in version 0.0.9pre3 - 2004-10-13
5370 o Bugfixes on 0.0.8.1:
5371 - Better torrc example lines for dirbindaddress and orbindaddress.
5372 - Improved bounds checking on parsed ints (e.g. config options and
5373 the ones we find in directories.)
5374 - Better handling of size_t vs int, so we're more robust on 64
5376 - Fix the rest of the bug where a newly started OR would appear
5377 as unverified even after we've added his fingerprint and hupped
5379 - Fix a bug from 0.0.7: when read() failed on a stream, we would
5380 close it without sending back an end. So 'connection refused'
5381 would simply be ignored and the user would get no response.
5383 o Bugfixes on 0.0.9pre2:
5384 - Serving the cached-on-disk directory to people is bad. We now
5385 provide no directory until we've fetched a fresh one.
5386 - Workaround for bug on windows where cached-directories get crlf
5388 - Make get_default_conf_file() work on older windows too.
5389 - If we write a *:* exit policy line in the descriptor, don't write
5390 any more exit policy lines.
5393 - Use only 0.0.9pre1 and later servers for resolve cells.
5394 - Make the dirservers file obsolete.
5395 - Include a dir-signing-key token in directories to tell the
5396 parsing entity which key is being used to sign.
5397 - Remove the built-in bulky default dirservers string.
5398 - New config option "Dirserver %s:%d [fingerprint]", which can be
5399 repeated as many times as needed. If no dirservers specified,
5400 default to moria1,moria2,tor26.
5401 - Make moria2 advertise a dirport of 80, so people behind firewalls
5402 will be able to get a directory.
5403 - Http proxy support
5404 - Dirservers translate requests for http://%s:%d/x to /x
5405 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
5406 be routed through this host.
5407 - Clients ask for /tor/x rather than /x for new enough dirservers.
5408 This way we can one day coexist peacefully with apache.
5409 - Clients specify a "Host: %s%d" http header, to be compatible
5410 with more proxies, and so running squid on an exit node can work.
5413 Changes in version 0.0.8.1 - 2004-10-13
5415 - Fix a seg fault that can be triggered remotely for Tor
5416 clients/servers with an open dirport.
5417 - Fix a rare assert trigger, where routerinfos for entries in
5418 our cpath would expire while we're building the path.
5419 - Fix a bug in OutboundBindAddress so it (hopefully) works.
5420 - Fix a rare seg fault for people running hidden services on
5421 intermittent connections.
5422 - Fix a bug in parsing opt keywords with objects.
5423 - Fix a stale pointer assert bug when a stream detaches and
5425 - Fix a string format vulnerability (probably not exploitable)
5426 in reporting stats locally.
5427 - Fix an assert trigger: sometimes launching circuits can fail
5428 immediately, e.g. because too many circuits have failed recently.
5429 - Fix a compile warning on 64 bit platforms.
5432 Changes in version 0.0.9pre2 - 2004-10-03
5434 - Make fetching a cached directory work for 64-bit platforms too.
5435 - Make zlib.h a required header, not an optional header.
5438 Changes in version 0.0.9pre1 - 2004-10-01
5440 - Stop using separate defaults for no-config-file and
5441 empty-config-file. Now you have to explicitly turn off SocksPort,
5442 if you don't want it open.
5443 - Fix a bug in OutboundBindAddress so it (hopefully) works.
5444 - Improve man page to mention more of the 0.0.8 features.
5445 - Fix a rare seg fault for people running hidden services on
5446 intermittent connections.
5447 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
5449 - Fix more dns related bugs: send back resolve_failed and end cells
5450 more reliably when the resolve fails, rather than closing the
5451 circuit and then trying to send the cell. Also attach dummy resolve
5452 connections to a circuit *before* calling dns_resolve(), to fix
5453 a bug where cached answers would never be sent in RESOLVED cells.
5454 - When we run out of disk space, or other log writing error, don't
5455 crash. Just stop logging to that log and continue.
5456 - We were starting to daemonize before we opened our logs, so if
5457 there were any problems opening logs, we would complain to stderr,
5458 which wouldn't work, and then mysteriously exit.
5459 - Fix a rare bug where sometimes a verified OR would connect to us
5460 before he'd uploaded his descriptor, which would cause us to
5461 assign conn->nickname as though he's unverified. Now we look through
5462 the fingerprint list to see if he's there.
5463 - Fix a rare assert trigger, where routerinfos for entries in
5464 our cpath would expire while we're building the path.
5467 - Clients can ask dirservers for /dir.z to get a compressed version
5468 of the directory. Only works for servers running 0.0.9, of course.
5469 - Make clients cache directories and use them to seed their router
5470 lists at startup. This means clients have a datadir again.
5471 - Configuration infrastructure support for warning on obsolete
5473 - Respond to content-encoding headers by trying to uncompress as
5475 - Reply with a deflated directory when a client asks for "dir.z".
5476 We could use allow-encodings instead, but allow-encodings isn't
5477 specified in HTTP 1.0.
5478 - Raise the max dns workers from 50 to 100.
5479 - Discourage people from setting their dirfetchpostperiod more often
5480 than once per minute.
5481 - Protect dirservers from overzealous descriptor uploading -- wait
5482 10 seconds after directory gets dirty, before regenerating.
5485 Changes in version 0.0.8 - 2004-08-25
5486 o Port it to SunOS 5.9 / Athena
5489 Changes in version 0.0.8rc2 - 2004-08-20
5490 o Make it compile on cygwin again.
5491 o When picking unverified routers, skip those with low uptime and/or
5492 low bandwidth, depending on what properties you care about.
5495 Changes in version 0.0.8rc1 - 2004-08-18
5496 o Changes from 0.0.7.3:
5498 - Fix assert triggers: if the other side returns an address 0.0.0.0,
5499 don't put it into the client dns cache.
5500 - If a begin failed due to exit policy, but we believe the IP address
5501 should have been allowed, switch that router to exitpolicy reject *:*
5502 until we get our next directory.
5504 - Clients choose nodes proportional to advertised bandwidth.
5505 - Avoid using nodes with low uptime as introduction points.
5506 - Handle servers with dynamic IP addresses: don't replace
5507 options->Address with the resolved one at startup, and
5508 detect our address right before we make a routerinfo each time.
5509 - 'FascistFirewall' option to pick dirservers and ORs on specific
5510 ports; plus 'FirewallPorts' config option to tell FascistFirewall
5511 which ports are open. (Defaults to 80,443)
5512 - Be more aggressive about trying to make circuits when the network
5513 has changed (e.g. when you unsuspend your laptop).
5514 - Check for time skew on http headers; report date in response to
5516 - If the entrynode config line has only one node, don't pick it as
5518 - Add strict{entry|exit}nodes config options. If set to 1, then
5519 we refuse to build circuits that don't include the specified entry
5521 - OutboundBindAddress config option, to bind to a specific
5522 IP address for outgoing connect()s.
5523 - End truncated log entries (e.g. directories) with "[truncated]".
5525 o Patches to 0.0.8preX:
5527 - Patches to compile and run on win32 again (maybe)?
5528 - Fix crash when looking for ~/.torrc with no $HOME set.
5529 - Fix a race bug in the unit tests.
5530 - Handle verified/unverified name collisions better when new
5531 routerinfo's arrive in a directory.
5532 - Sometimes routers were getting entered into the stats before
5533 we'd assigned their identity_digest. Oops.
5534 - Only pick and establish intro points after we've gotten a
5537 - AllowUnverifiedNodes config option to let circuits choose no-name
5538 routers in entry,middle,exit,introduction,rendezvous positions.
5539 Allow middle and rendezvous positions by default.
5540 - Add a man page for tor-resolve.
5543 Changes in version 0.0.7.3 - 2004-08-12
5544 o Stop dnsworkers from triggering an assert failure when you
5545 ask them to resolve the host "".
5548 Changes in version 0.0.8pre3 - 2004-08-09
5549 o Changes from 0.0.7.2:
5550 - Allow multiple ORs with same nickname in routerlist -- now when
5551 people give us one identity key for a nickname, then later
5552 another, we don't constantly complain until the first expires.
5553 - Remember used bandwidth (both in and out), and publish 15-minute
5554 snapshots for the past day into our descriptor.
5555 - You can now fetch $DIRURL/running-routers to get just the
5556 running-routers line, not the whole descriptor list. (But
5557 clients don't use this yet.)
5558 - When people mistakenly use Tor as an http proxy, point them
5559 at the tor-doc.html rather than the INSTALL.
5560 - Remove our mostly unused -- and broken -- hex_encode()
5561 function. Use base16_encode() instead. (Thanks to Timo Lindfors
5562 for pointing out this bug.)
5563 - Rotate onion keys every 12 hours, not every 2 hours, so we have
5564 fewer problems with people using the wrong key.
5565 - Change the default exit policy to reject the default edonkey,
5566 kazaa, gnutella ports.
5567 - Add replace_file() to util.[ch] to handle win32's rename().
5569 o Changes from 0.0.8preX:
5570 - Fix two bugs in saving onion keys to disk when rotating, so
5571 hopefully we'll get fewer people using old onion keys.
5572 - Fix an assert error that was making SocksPolicy not work.
5573 - Be willing to expire routers that have an open dirport -- it's
5574 just the authoritative dirservers we want to not forget.
5575 - Reject tor-resolve requests for .onion addresses early, so we
5576 don't build a whole rendezvous circuit and then fail.
5577 - When you're warning a server that he's unverified, don't cry
5579 - Fix a race condition: don't try to extend onto a connection
5580 that's still handshaking.
5581 - For servers in clique mode, require the conn to be open before
5582 you'll choose it for your path.
5583 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
5584 end relay cell, etc.
5585 - Measure bandwidth capacity over the last 24 hours, not just 12
5586 - Bugfix: authoritative dirservers were making and signing a new
5587 directory for each client, rather than reusing the cached one.
5590 Changes in version 0.0.8pre2 - 2004-08-04
5591 o Changes from 0.0.7.2:
5593 - Check directory signature _before_ you decide whether you're
5594 you're running an obsolete version and should exit.
5595 - Check directory signature _before_ you parse the running-routers
5596 list to decide who's running or verified.
5597 - Bugfixes and features:
5598 - Check return value of fclose while writing to disk, so we don't
5599 end up with broken files when servers run out of disk space.
5600 - Log a warning if the user uses an unsafe socks variant, so people
5601 are more likely to learn about privoxy or socat.
5602 - Dirservers now include RFC1123-style dates in the HTTP headers,
5603 which one day we will use to better detect clock skew.
5605 o Changes from 0.0.8pre1:
5606 - Make it compile without warnings again on win32.
5607 - Log a warning if you're running an unverified server, to let you
5608 know you might want to get it verified.
5609 - Only pick a default nickname if you plan to be a server.
5612 Changes in version 0.0.8pre1 - 2004-07-23
5614 - Made our unit tests compile again on OpenBSD 3.5, and tor
5615 itself compile again on OpenBSD on a sparc64.
5616 - We were neglecting milliseconds when logging on win32, so
5617 everything appeared to happen at the beginning of each second.
5620 - 'Extend' relay cell payloads now include the digest of the
5621 intended next hop's identity key. Now we can verify that we're
5622 extending to the right router, and also extend to routers we
5623 hadn't heard of before.
5626 - Tor nodes can now act as relays (with an advertised ORPort)
5627 without being manually verified by the dirserver operators.
5628 - Uploaded descriptors of unverified routers are now accepted
5629 by the dirservers, and included in the directory.
5630 - Verified routers are listed by nickname in the running-routers
5631 list; unverified routers are listed as "$<fingerprint>".
5632 - We now use hash-of-identity-key in most places rather than
5633 nickname or addr:port, for improved security/flexibility.
5634 - To avoid Sybil attacks, paths still use only verified servers.
5635 But now we have a chance to play around with hybrid approaches.
5636 - Nodes track bandwidth usage to estimate capacity (not used yet).
5637 - ClientOnly option for nodes that never want to become servers.
5638 - Directory caching.
5639 - "AuthoritativeDir 1" option for the official dirservers.
5640 - Now other nodes (clients and servers) will cache the latest
5641 directory they've pulled down.
5642 - They can enable their DirPort to serve it to others.
5643 - Clients will pull down a directory from any node with an open
5644 DirPort, and check the signature/timestamp correctly.
5645 - Authoritative dirservers now fetch directories from other
5646 authdirservers, to stay better synced.
5647 - Running-routers list tells who's down also, along with noting
5648 if they're verified (listed by nickname) or unverified (listed
5650 - Allow dirservers to serve running-router list separately.
5651 This isn't used yet.
5652 - ORs connect-on-demand to other ORs
5653 - If you get an extend cell to an OR you're not connected to,
5654 connect, handshake, and forward the create cell.
5655 - The authoritative dirservers stay connected to everybody,
5656 and everybody stays connected to 0.0.7 servers, but otherwise
5657 clients/servers expire unused connections after 5 minutes.
5658 - When servers get a sigint, they delay 30 seconds (refusing new
5659 connections) then exit. A second sigint causes immediate exit.
5660 - File and name management:
5661 - Look for .torrc if no CONFDIR "torrc" is found.
5662 - If no datadir is defined, then choose, make, and secure ~/.tor
5664 - If torrc not found, exitpolicy reject *:*.
5665 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
5666 - If no nickname is defined, derive default from hostname.
5667 - Rename secret key files, e.g. identity.key -> secret_id_key,
5668 to discourage people from mailing their identity key to tor-ops.
5669 - Refuse to build a circuit before the directory has arrived --
5670 it won't work anyway, since you won't know the right onion keys
5672 - Try other dirservers immediately if the one you try is down. This
5673 should tolerate down dirservers better now.
5674 - Parse tor version numbers so we can do an is-newer-than check
5675 rather than an is-in-the-list check.
5676 - New socks command 'resolve', to let us shim gethostbyname()
5678 - A 'tor_resolve' script to access the socks resolve functionality.
5679 - A new socks-extensions.txt doc file to describe our
5680 interpretation and extensions to the socks protocols.
5681 - Add a ContactInfo option, which gets published in descriptor.
5682 - Publish OR uptime in descriptor (and thus in directory) too.
5683 - Write tor version at the top of each log file
5684 - New docs in the tarball:
5686 - Document that you should proxy your SSL traffic too.
5689 Changes in version 0.0.7.2 - 2004-07-07
5690 o A better fix for the 0.0.0.0 problem, that will hopefully
5691 eliminate the remaining related assertion failures.
5694 Changes in version 0.0.7.1 - 2004-07-04
5695 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
5696 since internally we use 0.0.0.0 to signify "not yet resolved".
5699 Changes in version 0.0.7 - 2004-06-07
5700 o Updated the man page to reflect the new features.
5703 Changes in version 0.0.7rc2 - 2004-06-06
5704 o Changes from 0.0.7rc1:
5705 - Make it build on Win32 again.
5706 o Changes from 0.0.6.2:
5707 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
5711 Changes in version 0.0.7rc1 - 2004-06-02
5713 - On sighup, we were adding another log without removing the first
5714 one. So log messages would get duplicated n times for n sighups.
5715 - Several cases of using a connection after we'd freed it. The
5716 problem was that connections that are pending resolve are in both
5717 the pending_resolve tree, and also the circuit's resolving_streams
5718 list. When you want to remove one, you must remove it from both.
5719 - Fix a double-mark-for-close where an end cell arrived for a
5720 resolving stream, and then the resolve failed.
5721 - Check directory signatures based on name of signer, not on whom
5722 we got the directory from. This will let us cache directories more
5725 - Crank up some of our constants to handle more users.
5728 Changes in version 0.0.7pre1 - 2004-06-02
5729 o Fixes for crashes and other obnoxious bugs:
5730 - Fix an epipe bug: sometimes when directory connections failed
5731 to connect, we would give them a chance to flush before closing
5733 - When we detached from a circuit because of resolvefailed, we
5734 would immediately try the same circuit twice more, and then
5735 give up on the resolve thinking we'd tried three different
5737 - Limit the number of intro circuits we'll attempt to build for a
5738 hidden service per 15-minute period.
5739 - Check recommended-software string *early*, before actually parsing
5740 the directory. Thus we can detect an obsolete version and exit,
5741 even if the new directory format doesn't parse.
5742 o Fixes for security bugs:
5743 - Remember which nodes are dirservers when you startup, and if a
5744 random OR enables his dirport, don't automatically assume he's
5745 a trusted dirserver.
5747 - Directory connections were asking the wrong poll socket to
5748 start writing, and not asking themselves to start writing.
5749 - When we detached from a circuit because we sent a begin but
5750 didn't get a connected, we would use it again the first time;
5751 but after that we would correctly switch to a different one.
5752 - Stop warning when the first onion decrypt attempt fails; they
5753 will sometimes legitimately fail now that we rotate keys.
5754 - Override unaligned-access-ok check when $host_cpu is ia64 or
5755 arm. Apparently they allow it but the kernel whines.
5756 - Dirservers try to reconnect periodically too, in case connections
5758 - Fix some memory leaks in directory servers.
5759 - Allow backslash in Win32 filenames.
5760 - Made Tor build complain-free on FreeBSD, hopefully without
5761 breaking other BSD builds. We'll see.
5763 - Doxygen markup on all functions and global variables.
5764 - Make directory functions update routerlist, not replace it. So
5765 now directory disagreements are not so critical a problem.
5766 - Remove the upper limit on number of descriptors in a dirserver's
5767 directory (not that we were anywhere close).
5768 - Allow multiple logfiles at different severity ranges.
5769 - Allow *BindAddress to specify ":port" rather than setting *Port
5770 separately. Allow multiple instances of each BindAddress config
5771 option, so you can bind to multiple interfaces if you want.
5772 - Allow multiple exit policy lines, which are processed in order.
5773 Now we don't need that huge line with all the commas in it.
5774 - Enable accept/reject policies on SOCKS connections, so you can bind
5775 to 0.0.0.0 but still control who can use your OP.
5778 Changes in version 0.0.6.2 - 2004-05-16
5779 o Our integrity-checking digest was checking only the most recent cell,
5780 not the previous cells like we'd thought.
5781 Thanks to Stefan Mark for finding the flaw!
5784 Changes in version 0.0.6.1 - 2004-05-06
5785 o Fix two bugs in our AES counter-mode implementation (this affected
5786 onion-level stream encryption, but not TLS-level). It turns
5787 out we were doing something much more akin to a 16-character
5788 polyalphabetic cipher. Oops.
5789 Thanks to Stefan Mark for finding the flaw!
5790 o Retire moria3 as a directory server, and add tor26 as a directory
5794 Changes in version 0.0.6 - 2004-05-02
5798 Changes in version 0.0.6rc4 - 2004-05-01
5799 o Update the built-in dirservers list to use the new directory format
5800 o Fix a rare seg fault: if a node offering a hidden service attempts
5801 to build a circuit to Alice's rendezvous point and fails before it
5802 reaches the last hop, it retries with a different circuit, but
5804 o Handle windows socket errors correctly.
5807 Changes in version 0.0.6rc3 - 2004-04-28
5808 o Don't expire non-general excess circuits (if we had enough
5809 circuits open, we were expiring rendezvous circuits -- even
5810 when they had a stream attached. oops.)
5811 o Fetch randomness from /dev/urandom better (not via fopen/fread)
5812 o Better debugging for tls errors
5813 o Some versions of openssl have an SSL_pending function that erroneously
5814 returns bytes when there is a non-application record pending.
5815 o Set Content-Type on the directory and hidserv descriptor.
5816 o Remove IVs from cipher code, since AES-ctr has none.
5817 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
5818 o We were using an array of length zero in a few places.
5819 o win32's gethostbyname can't resolve an IP to an IP.
5820 o win32's close can't close a socket.
5823 Changes in version 0.0.6rc2 - 2004-04-26
5824 o Fix a bug where we were closing tls connections intermittently.
5825 It turns out openssl keeps its errors around -- so if an error
5826 happens, and you don't ask about it, and then another openssl
5827 operation happens and succeeds, and you ask if there was an error,
5828 it tells you about the first error. Fun fun.
5829 o Fix a bug that's been lurking since 27 may 03 (!)
5830 When passing back a destroy cell, we would use the wrong circ id.
5831 'Mostly harmless', but still worth fixing.
5832 o Since we don't support truncateds much, don't bother sending them;
5833 just close the circ.
5834 o check for <machine/limits.h> so we build on NetBSD again (I hope).
5835 o don't crash if a conn that sent a begin has suddenly lost its circuit
5836 (this was quite rare).
5839 Changes in version 0.0.6rc1 - 2004-04-25
5840 o We now rotate link (tls context) keys and onion keys.
5841 o CREATE cells now include oaep padding, so you can tell
5842 if you decrypted them correctly.
5843 o Add bandwidthburst to server descriptor.
5844 o Directories now say which dirserver signed them.
5845 o Use a tor_assert macro that logs failed assertions too.
5848 Changes in version 0.0.6pre5 - 2004-04-18
5849 o changes from 0.0.6pre4:
5850 - make tor build on broken freebsd 5.2 installs
5851 - fix a failed assert when you try an intro point, get a nack, and try
5852 a second one and it works.
5853 - when alice uses a port that the hidden service doesn't accept,
5854 it now sends back an end cell (denied by exit policy). otherwise
5855 alice would just have to wait to time out.
5856 - fix another rare bug: when we had tried all the intro
5857 points for a hidden service, we fetched the descriptor
5858 again, but we left our introcirc thinking it had already
5859 sent an intro, so it kept waiting for a response...
5860 - bugfix: when you sleep your hidden-service laptop, as soon
5861 as it wakes up it tries to upload a service descriptor, but
5862 socketpair fails for some reason (localhost not up yet?).
5863 now we simply give up on that upload, and we'll try again later.
5864 i'd still like to find the bug though.
5865 - if an intro circ waiting for an ack dies before getting one, then
5867 - we were reusing stale service descriptors and refetching usable
5871 Changes in version 0.0.6pre4 - 2004-04-14
5872 o changes from 0.0.6pre3:
5873 - when bob fails to connect to the rendezvous point, and his
5874 circ didn't fail because of the rendezvous point itself, then
5875 he retries a couple of times
5876 - we expire introduction and rendezvous circs more thoroughly
5877 (sometimes they were hanging around forever)
5878 - we expire unattached rendezvous streams that have been around
5879 too long (they were sticking around forever).
5880 - fix a measly fencepost error that was crashing everybody with
5884 Changes in version 0.0.6pre3 - 2004-04-14
5885 o changes from 0.0.6pre2:
5886 - make hup work again
5887 - fix some memory leaks for dirservers
5888 - allow more skew in rendezvous descriptor timestamps, to help
5889 handle people like blanu who don't know what time it is
5890 - normal circs are 3 hops, but some rend/intro circs are 4, if
5891 the initiator doesn't get to choose the last hop
5892 - send acks for introductions, so alice can know whether to try
5894 - bob publishes intro points more correctly
5895 o changes from 0.0.5:
5896 - fix an assert trigger that's been plaguing us since the days
5897 of 0.0.2prexx (thanks weasel!)
5898 - retry stream correctly when we fail to connect because of
5899 exit-policy-reject (should try another) or can't-resolve-address
5900 (also should try another, because dns on random internet servers
5902 - when we hup a dirserver and we've *removed* a server from the
5903 approved-routers list, now we remove that server from the
5904 in-memory directories too
5907 Changes in version 0.0.6pre2 - 2004-04-08
5908 o We fixed our base32 implementation. Now it works on all architectures.
5911 Changes in version 0.0.6pre1 - 2004-04-08
5913 - Hidden services and rendezvous points are implemented. Go to
5914 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
5915 hidden services. (This only works via a socks4a proxy such as
5916 Privoxy, and currently it's quite slow.)
5919 Changes in version 0.0.5 - 2004-03-30
5923 Changes in version 0.0.5rc3 - 2004-03-29
5924 o Install torrc as torrc.sample -- we no longer clobber your
5926 o Re-enable recommendedversion checking (we broke it in rc2, oops)
5927 o Add in a 'notice' log level for things the operator should hear
5928 but that aren't warnings
5931 Changes in version 0.0.5rc2 - 2004-03-29
5932 o Hold socks connection open until reply is flushed (if possible)
5933 o Make exit nodes resolve IPs to IPs immediately, rather than asking
5934 the dns farm to do it.
5935 o Fix c99 aliasing warnings in rephist.c
5936 o Don't include server descriptors that are older than 24 hours in the
5938 o Give socks 'reject' replies their whole 15s to attempt to flush,
5939 rather than seeing the 60s timeout and assuming the flush had failed.
5940 o Clean automake droppings from the cvs repository
5943 Changes in version 0.0.5rc1 - 2004-03-28
5944 o Fix mangled-state bug in directory fetching (was causing sigpipes).
5945 o Only build circuits after we've fetched the directory: clients were
5946 using only the directory servers before they'd fetched a directory.
5947 This also means longer startup time; so it goes.
5948 o Fix an assert trigger where an OP would fail to handshake, and we'd
5949 expect it to have a nickname.
5950 o Work around a tsocks bug: do a socks reject when AP connection dies
5951 early, else tsocks goes into an infinite loop.
5954 Changes in version 0.0.4 - 2004-03-26
5955 o When connecting to a dirserver or OR and the network is down,
5959 Changes in version 0.0.3 - 2004-03-26
5960 o Warn and fail if server chose a nickname with illegal characters
5961 o Port to Solaris and Sparc:
5962 - include missing header fcntl.h
5963 - have autoconf find -lsocket -lnsl automatically
5964 - deal with hardware word alignment
5965 - make uname() work (solaris has a different return convention)
5966 - switch from using signal() to sigaction()
5967 o Preliminary work on reputation system:
5968 - Keep statistics on success/fail of connect attempts; they're published
5969 by kill -USR1 currently.
5970 - Add a RunTesting option to try to learn link state by creating test
5971 circuits, even when SocksPort is off.
5972 - Remove unused open circuits when there are too many.
5975 Changes in version 0.0.2 - 2004-03-19
5976 - Include strlcpy and strlcat for safer string ops
5977 - define INADDR_NONE so we compile (but still not run) on solaris
5980 Changes in version 0.0.2pre27 - 2004-03-14
5982 - Allow internal tor networks (we were rejecting internal IPs,
5983 now we allow them if they're set explicitly).
5984 - And fix a few endian issues.
5987 Changes in version 0.0.2pre26 - 2004-03-14
5989 - If a stream times out after 15s without a connected cell, don't
5990 try that circuit again: try a new one.
5991 - Retry streams at most 4 times. Then give up.
5992 - When a dirserver gets a descriptor from an unknown router, it
5993 logs its fingerprint (so the dirserver operator can choose to
5994 accept it even without mail from the server operator).
5995 - Inform unapproved servers when we reject their descriptors.
5996 - Make tor build on Windows again. It works as a client, who knows
5998 - Clearer instructions in the torrc for how to set up a server.
5999 - Be more efficient about reading fd's when our global token bucket
6000 (used for rate limiting) becomes empty.
6002 - Stop asserting that computers always go forward in time. It's
6004 - When we sent a cell (e.g. destroy) and then marked an OR connection
6005 expired, we might close it before finishing a flush if the other
6006 side isn't reading right then.
6007 - Don't allow dirservers to start if they haven't defined
6009 - We were caching transient dns failures. Oops.
6010 - Prevent servers from publishing an internal IP as their address.
6011 - Address a strcat vulnerability in circuit.c
6014 Changes in version 0.0.2pre25 - 2004-03-04
6016 - Put the OR's IP in its router descriptor, not its fqdn. That way
6017 we'll stop being stalled by gethostbyname for nodes with flaky dns,
6020 - If the user typed in an address that didn't resolve, the server
6024 Changes in version 0.0.2pre24 - 2004-03-03
6026 - Fix an assertion failure in dns.c, where we were trying to dequeue
6027 a pending dns resolve even if it wasn't pending
6028 - Fix a spurious socks5 warning about still trying to write after the
6029 connection is finished.
6030 - Hold certain marked_for_close connections open until they're finished
6031 flushing, rather than losing bytes by closing them too early.
6032 - Correctly report the reason for ending a stream
6033 - Remove some duplicate calls to connection_mark_for_close
6034 - Put switch_id and start_daemon earlier in the boot sequence, so it
6035 will actually try to chdir() to options.DataDirectory
6036 - Make 'make test' exit(1) if a test fails; fix some unit tests
6037 - Make tor fail when you use a config option it doesn't know about,
6038 rather than warn and continue.
6039 - Make --version work
6040 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
6043 Changes in version 0.0.2pre23 - 2004-02-29
6045 - Print a statement when the first circ is finished, so the user
6047 - If a relay cell is unrecognized at the end of the circuit,
6048 send back a destroy. (So attacks to mutate cells are more
6050 - New config option 'excludenodes' to avoid certain nodes for circuits.
6051 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
6052 so you can collect coredumps there.
6054 - Fix a bug in tls flushing where sometimes data got wedged and
6055 didn't flush until more data got sent. Hopefully this bug was
6056 a big factor in the random delays we were seeing.
6057 - Make 'connected' cells include the resolved IP, so the client
6058 dns cache actually gets populated.
6059 - Disallow changing from ORPort=0 to ORPort>0 on hup.
6060 - When we time-out on a stream and detach from the circuit, send an
6061 end cell down it first.
6062 - Only warn about an unknown router (in exitnodes, entrynodes,
6063 excludenodes) after we've fetched a directory.
6066 Changes in version 0.0.2pre22 - 2004-02-26
6068 - Servers publish less revealing uname information in descriptors.
6069 - More memory tracking and assertions, to crash more usefully when
6071 - If the default torrc isn't there, just use some default defaults.
6072 Plus provide an internal dirservers file if they don't have one.
6073 - When the user tries to use Tor as an http proxy, give them an http
6074 501 failure explaining that we're a socks proxy.
6075 - Dump a new router.desc on hup, to help confused people who change
6076 their exit policies and then wonder why router.desc doesn't reflect
6078 - Clean up the generic tor.sh init script that we ship with.
6080 - If the exit stream is pending on the resolve, and a destroy arrives,
6081 then the stream wasn't getting removed from the pending list. I
6082 think this was the one causing recent server crashes.
6083 - Use a more robust poll on OSX 10.3, since their poll is flaky.
6084 - When it couldn't resolve any dirservers, it was useless from then on.
6085 Now it reloads the RouterFile (or default dirservers) if it has no
6087 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
6088 many users don't even *have* a /usr/local/sbin/.
6091 Changes in version 0.0.2pre21 - 2004-02-18
6093 - There's a ChangeLog file that actually reflects the changelog.
6094 - There's a 'torify' wrapper script, with an accompanying
6095 tor-tsocks.conf, that simplifies the process of using tsocks for
6096 tor. It even has a man page.
6097 - The tor binary gets installed to sbin rather than bin now.
6098 - Retry streams where the connected cell hasn't arrived in 15 seconds
6099 - Clean up exit policy handling -- get the default out of the torrc,
6100 so we can update it without forcing each server operator to fix
6102 - Allow imaps and pop3s in default exit policy
6104 - Prevent picking middleman nodes as the last node in the circuit
6107 Changes in version 0.0.2pre20 - 2004-01-30
6109 - We now have a deb package, and it's in debian unstable. Go to
6111 - I've split the TotalBandwidth option into BandwidthRate (how many
6112 bytes per second you want to allow, long-term) and
6113 BandwidthBurst (how many bytes you will allow at once before the cap
6114 kicks in). This better token bucket approach lets you, say, set
6115 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
6116 performance while not exceeding your monthly bandwidth quota.
6117 - Push out a tls record's worth of data once you've got it, rather
6118 than waiting until you've read everything waiting to be read. This
6119 may improve performance by pipelining better. We'll see.
6120 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
6121 from failed circuits (if they haven't been connected yet) and attach
6123 - Expire old streams that haven't managed to connect. Some day we'll
6124 have them reattach to new circuits instead.
6127 - Fix several memory leaks that were causing servers to become bloated
6129 - Fix a few very rare assert triggers. A few more remain.
6130 - Setuid to User _before_ complaining about running as root.
6133 Changes in version 0.0.2pre19 - 2004-01-07
6135 - Fix deadlock condition in dns farm. We were telling a child to die by
6136 closing the parent's file descriptor to him. But newer children were
6137 inheriting the open file descriptor from the parent, and since they
6138 weren't closing it, the socket never closed, so the child never read
6139 eof, so he never knew to exit. Similarly, dns workers were holding
6140 open other sockets, leading to all sorts of chaos.
6141 - New cleaner daemon() code for forking and backgrounding.
6142 - If you log to a file, it now prints an entry at the top of the
6143 logfile so you know it's working.
6144 - The onionskin challenge length was 30 bytes longer than necessary.
6145 - Started to patch up the spec so it's not quite so out of date.
6148 Changes in version 0.0.2pre18 - 2004-01-02
6150 - Fix endian issues with the 'integrity' field in the relay header.
6151 - Fix a potential bug where connections in state
6152 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
6155 Changes in version 0.0.2pre17 - 2003-12-30
6157 - Made --debuglogfile (or any second log file, actually) work.
6158 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
6159 adversary could force us into an infinite loop.
6162 - Each onionskin handshake now includes a hash of the computed key,
6163 to prove the server's identity and help perfect forward secrecy.
6164 - Changed cell size from 256 to 512 bytes (working toward compatibility
6166 - Changed cell length to 2 bytes, and moved it to the relay header.
6167 - Implemented end-to-end integrity checking for the payloads of
6169 - Separated streamid from 'recognized' (otherwise circuits will get
6170 messed up when we try to have streams exit from the middle). We
6171 use the integrity-checking to confirm that a cell is addressed to
6173 - Randomize the initial circid and streamid values, so an adversary who
6174 breaks into a node can't learn how many circuits or streams have
6178 Changes in version 0.0.2pre16 - 2003-12-14
6180 - Fixed a bug that made HUP trigger an assert
6181 - Fixed a bug where a circuit that immediately failed wasn't being
6182 counted as a failed circuit in counting retries.
6185 - Now we close the circuit when we get a truncated cell: otherwise we're
6186 open to an anonymity attack where a bad node in the path truncates
6187 the circuit and then we open streams at him.
6188 - Add port ranges to exit policies
6189 - Add a conservative default exit policy
6190 - Warn if you're running tor as root
6191 - on HUP, retry OR connections and close/rebind listeners
6192 - options.EntryNodes: try these nodes first when picking the first node
6193 - options.ExitNodes: if your best choices happen to include any of
6194 your preferred exit nodes, you choose among just those preferred
6196 - options.ExcludedNodes: nodes that are never picked in path building
6199 Changes in version 0.0.2pre15 - 2003-12-03
6200 o Robustness and bugfixes:
6201 - Sometimes clients would cache incorrect DNS resolves, which would
6202 really screw things up.
6203 - An OP that goes offline would slowly leak all its sockets and stop
6205 - A wide variety of bugfixes in exit node selection, exit policy
6206 handling, and processing pending streams when a new circuit is
6208 - Pick nodes for a path only from those the directory says are up
6209 - Choose randomly from all running dirservers, not always the first one
6210 - Increase allowed http header size for directory fetch.
6211 - Stop writing to stderr (if we're daemonized it will be closed).
6212 - Enable -g always, so cores will be more useful to me.
6213 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
6216 - Wrote a man page. It lists commonly used options.
6219 - Change default loglevel to warn.
6220 - Make PidFile default to null rather than littering in your CWD.
6221 - OnionRouter config option is now obsolete. Instead it just checks
6223 - Moved to a single unified torrc file for both clients and servers.
6226 Changes in version 0.0.2pre14 - 2003-11-29
6227 o Robustness and bugfixes:
6228 - Force the admin to make the DataDirectory himself
6229 - to get ownership/permissions right
6230 - so clients no longer make a DataDirectory and then never use it
6231 - fix bug where a client who was offline for 45 minutes would never
6232 pull down a directory again
6233 - fix (or at least hide really well) the dns assert bug that was
6234 causing server crashes
6235 - warnings and improved robustness wrt clockskew for certs
6236 - use the native daemon(3) to daemonize, when available
6237 - exit if bind() fails
6238 - exit if neither socksport nor orport is defined
6239 - include our own tor_timegm (Win32 doesn't have its own)
6240 - bugfix for win32 with lots of connections
6241 - fix minor bias in PRNG
6242 - make dirserver more robust to corrupt cached directory
6245 - Wrote the design document (woo)
6247 o Circuit building and exit policies:
6248 - Circuits no longer try to use nodes that the directory has told them
6250 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
6251 bitcounts (18.0.0.0/8).
6252 - Make AP connections standby for a circuit if no suitable circuit
6253 exists, rather than failing
6254 - Circuits choose exit node based on addr/port, exit policies, and
6255 which AP connections are standing by
6256 - Bump min pathlen from 2 to 3
6257 - Relay end cells have a payload to describe why the stream ended.
6258 - If the stream failed because of exit policy, try again with a new
6260 - Clients have a dns cache to remember resolved addresses.
6261 - Notice more quickly when we have no working circuits
6264 - APPort is now called SocksPort
6265 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
6267 - RecommendedVersions is now a config variable rather than
6268 hardcoded (for dirservers)
6269 - Reloads config on HUP
6270 - Usage info on -h or --help
6271 - If you set User and Group config vars, it'll setu/gid to them.
6273 Changes in version 0.0.2pre13 - 2003-10-19
6274 o General stability:
6275 - SSL_write no longer fails when it returns WANTWRITE and the number
6276 of bytes in the buf has changed by the next SSL_write call.
6277 - Fix segfault fetching directory when network is down
6278 - Fix a variety of minor memory leaks
6279 - Dirservers reload the fingerprints file on HUP, so I don't have
6280 to take down the network when I approve a new router
6281 - Default server config file has explicit Address line to specify fqdn
6284 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
6285 - Make listener connections not ever alloc bufs
6287 o Autoconf improvements:
6288 - don't clobber an external CFLAGS in ./configure
6289 - Make install now works
6290 - create var/lib/tor on make install
6291 - autocreate a tor.sh initscript to help distribs
6292 - autocreate the torrc and sample-server-torrc with correct paths
6294 o Log files and Daemonizing now work:
6295 - If --DebugLogFile is specified, log to it at -l debug
6296 - If --LogFile is specified, use it instead of commandline
6297 - If --RunAsDaemon is set, tor forks and backgrounds on startup