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