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