2 This document summarizes new features and bugfixes in each stable release
3 of Tor. If you want to see more detailed descriptions of the changes in
4 each development snapshot, see the ChangeLog file.
6 Changes in version 0.1.2.18 - 2007-10-28
7 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
8 hidden service introduction that were causing huge delays, and a big
9 bug that was causing some servers to disappear from the network status
10 lists for a few hours each day.
12 o Major bugfixes (crashes):
13 - If a connection is shut down abruptly because of something that
14 happened inside connection_flushed_some(), do not call
15 connection_finished_flushing(). Should fix bug 451:
16 "connection_stop_writing: Assertion conn->write_event failed"
17 Bugfix on 0.1.2.7-alpha.
18 - Fix possible segfaults in functions called from
19 rend_process_relay_cell().
21 o Major bugfixes (hidden services):
22 - Hidden services were choosing introduction points uniquely by
23 hexdigest, but when constructing the hidden service descriptor
24 they merely wrote the (potentially ambiguous) nickname.
25 - Clients now use the v2 intro format for hidden service
26 connections: they specify their chosen rendezvous point by identity
27 digest rather than by (potentially ambiguous) nickname. These
28 changes could speed up hidden service connections dramatically.
30 o Major bugfixes (other):
31 - Stop publishing a new server descriptor just because we get a
32 HUP signal. This led (in a roundabout way) to some servers getting
33 dropped from the networkstatus lists for a few hours each day.
34 - When looking for a circuit to cannibalize, consider family as well
35 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
36 circuit cannibalization).
37 - When a router wasn't listed in a new networkstatus, we were leaving
38 the flags for that router alone -- meaning it remained Named,
39 Running, etc -- even though absence from the networkstatus means
40 that it shouldn't be considered to exist at all anymore. Now we
41 clear all the flags for routers that fall out of the networkstatus
42 consensus. Fixes bug 529.
45 - Don't try to access (or alter) the state file when running
46 --list-fingerprint or --verify-config or --hash-password. Resolves
48 - When generating information telling us how to extend to a given
49 router, do not try to include the nickname if it is
50 absent. Resolves bug 467.
51 - Fix a user-triggerable segfault in expand_filename(). (There isn't
52 a way to trigger this remotely.)
53 - When sending a status event to the controller telling it that an
54 OR address is readable, set the port correctly. (Previously we
55 were reporting the dir port.)
56 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
57 command. Bugfix on 0.1.2.17.
58 - When loading bandwidth history, do not believe any information in
59 the future. Fixes bug 434.
60 - When loading entry guard information, do not believe any information
62 - When we have our clock set far in the future and generate an
63 onion key, then re-set our clock to be correct, we should not stop
64 the onion key from getting rotated.
65 - On some platforms, accept() can return a broken address. Detect
66 this more quietly, and deal accordingly. Fixes bug 483.
67 - It's not actually an error to find a non-pending entry in the DNS
68 cache when canceling a pending resolve. Don't log unless stuff
69 is fishy. Resolves bug 463.
70 - Don't reset trusted dir server list when we set a configuration
71 option. Patch from Robert Hogan.
74 Changes in version 0.1.2.17 - 2007-08-30
75 o Major bugfixes (security):
76 - We removed support for the old (v0) control protocol. It has been
77 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
78 become more of a headache than it's worth.
80 o Major bugfixes (load balancing):
81 - When choosing nodes for non-guard positions, weight guards
82 proportionally less, since they already have enough load. Patch
84 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
85 will allow fast Tor servers to get more attention.
86 - When we're upgrading from an old Tor version, forget our current
87 guards and pick new ones according to the new weightings. These
88 three load balancing patches could raise effective network capacity
89 by a factor of four. Thanks to Mike Perry for measurements.
91 o Major bugfixes (stream expiration):
92 - Expire not-yet-successful application streams in all cases if
93 they've been around longer than SocksTimeout. Right now there are
94 some cases where the stream will live forever, demanding a new
95 circuit every 15 seconds. Fixes bug 454; reported by lodger.
97 o Minor features (controller):
98 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
99 is valid before any authentication has been received. It tells
100 a controller what kind of authentication is expected, and what
101 protocol is spoken. Implements proposal 119.
103 o Minor bugfixes (performance):
104 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
105 greatly speeding up loading cached-routers from disk on startup.
106 - Disable sentinel-based debugging for buffer code: we squashed all
107 the bugs that this was supposed to detect a long time ago, and now
108 its only effect is to change our buffer sizes from nice powers of
109 two (which platform mallocs tend to like) to values slightly over
110 powers of two (which make some platform mallocs sad).
112 o Minor bugfixes (misc):
113 - If exit bandwidth ever exceeds one third of total bandwidth, then
114 use the correct formula to weight exit nodes when choosing paths.
115 Based on patch from Mike Perry.
116 - Choose perfectly fairly among routers when choosing by bandwidth and
117 weighting by fraction of bandwidth provided by exits. Previously, we
118 would choose with only approximate fairness, and correct ourselves
119 if we ran off the end of the list.
120 - If we require CookieAuthentication but we fail to write the
121 cookie file, we would warn but not exit, and end up in a state
122 where no controller could authenticate. Now we exit.
123 - If we require CookieAuthentication, stop generating a new cookie
124 every time we change any piece of our config.
125 - Refuse to start with certain directory authority keys, and
126 encourage people using them to stop.
127 - Terminate multi-line control events properly. Original patch
129 - Fix a minor memory leak when we fail to find enough suitable
130 servers to choose a circuit.
131 - Stop leaking part of the descriptor when we run into a particularly
132 unparseable piece of it.
135 Changes in version 0.1.2.16 - 2007-08-01
136 o Major security fixes:
137 - Close immediately after missing authentication on control port;
138 do not allow multiple authentication attempts.
141 Changes in version 0.1.2.15 - 2007-07-17
142 o Major bugfixes (compilation):
143 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
145 o Major bugfixes (crashes):
146 - Try even harder not to dereference the first character after
147 an mmap(). Reported by lodger.
148 - Fix a crash bug in directory authorities when we re-number the
149 routerlist while inserting a new router.
150 - When the cached-routers file is an even multiple of the page size,
151 don't run off the end and crash. (Fixes bug 455; based on idea
153 - Fix eventdns.c behavior on Solaris: It is critical to include
154 orconfig.h _before_ sys/types.h, so that we can get the expected
155 definition of _FILE_OFFSET_BITS.
157 o Major bugfixes (security):
158 - Fix a possible buffer overrun when using BSD natd support. Bug
160 - When sending destroy cells from a circuit's origin, don't include
161 the reason for tearing down the circuit. The spec says we didn't,
162 and now we actually don't. Reported by lodger.
163 - Keep streamids from different exits on a circuit separate. This
164 bug may have allowed other routers on a given circuit to inject
165 cells into streams. Reported by lodger; fixes bug 446.
166 - If there's a never-before-connected-to guard node in our list,
167 never choose any guards past it. This way we don't expand our
168 guard list unless we need to.
170 o Minor bugfixes (guard nodes):
171 - Weight guard selection by bandwidth, so that low-bandwidth nodes
172 don't get overused as guards.
174 o Minor bugfixes (directory):
175 - Correctly count the number of authorities that recommend each
176 version. Previously, we were under-counting by 1.
177 - Fix a potential crash bug when we load many server descriptors at
178 once and some of them make others of them obsolete. Fixes bug 458.
180 o Minor bugfixes (hidden services):
181 - Stop tearing down the whole circuit when the user asks for a
182 connection to a port that the hidden service didn't configure.
185 o Minor bugfixes (misc):
186 - On Windows, we were preventing other processes from reading
187 cached-routers while Tor was running. Reported by janbar.
188 - Fix a possible (but very unlikely) bug in picking routers by
189 bandwidth. Add a log message to confirm that it is in fact
190 unlikely. Patch from lodger.
191 - Backport a couple of memory leak fixes.
192 - Backport miscellaneous cosmetic bugfixes.
195 Changes in version 0.1.2.14 - 2007-05-25
196 o Directory authority changes:
197 - Two directory authorities (moria1 and moria2) just moved to new
198 IP addresses. This change will particularly affect those who serve
199 or use hidden services.
201 o Major bugfixes (crashes):
202 - If a directory server runs out of space in the connection table
203 as it's processing a begin_dir request, it will free the exit stream
204 but leave it attached to the circuit, leading to unpredictable
205 behavior. (Reported by seeess, fixes bug 425.)
206 - Fix a bug in dirserv_remove_invalid() that would cause authorities
207 to corrupt memory under some really unlikely scenarios.
208 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
209 - Avoid segfaults when reading from mmaped descriptor file. (Reported
212 o Major bugfixes (security):
213 - When choosing an entry guard for a circuit, avoid using guards
214 that are in the same family as the chosen exit -- not just guards
215 that are exactly the chosen exit. (Reported by lodger.)
217 o Major bugfixes (resource management):
218 - If a directory authority is down, skip it when deciding where to get
219 networkstatus objects or descriptors. Otherwise we keep asking
220 every 10 seconds forever. Fixes bug 384.
221 - Count it as a failure if we fetch a valid network-status but we
222 don't want to keep it. Otherwise we'll keep fetching it and keep
223 not wanting to keep it. Fixes part of bug 422.
224 - If all of our dirservers have given us bad or no networkstatuses
225 lately, then stop hammering them once per minute even when we
226 think they're failed. Fixes another part of bug 422.
229 - Actually set the purpose correctly for descriptors inserted with
231 - When we have k non-v2 authorities in our DirServer config,
232 we ignored the last k authorities in the list when updating our
234 - Correctly back-off from requesting router descriptors that we are
235 having a hard time downloading.
236 - Read resolv.conf files correctly on platforms where read() returns
237 partial results on small file reads.
238 - Don't rebuild the entire router store every time we get 32K of
239 routers: rebuild it when the journal gets very large, or when
240 the gaps in the store get very large.
243 - When routers publish SVN revisions in their router descriptors,
244 authorities now include those versions correctly in networkstatus
246 - Warn when using a version of libevent before 1.3b to run a server on
247 OSX or BSD: these versions interact badly with userspace threads.
250 Changes in version 0.1.2.13 - 2007-04-24
252 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
253 of the Freenode IRC network, remembering his patience and vision for
254 free speech on the Internet.
256 o Major features, client performance:
257 - Weight directory requests by advertised bandwidth. Now we can
258 let servers enable write limiting but still allow most clients to
259 succeed at their directory requests. (We still ignore weights when
260 choosing a directory authority; I hope this is a feature.)
261 - Stop overloading exit nodes -- avoid choosing them for entry or
262 middle hops when the total bandwidth available from non-exit nodes
263 is much higher than the total bandwidth available from exit nodes.
264 - Rather than waiting a fixed amount of time between retrying
265 application connections, we wait only 10 seconds for the first,
266 10 seconds for the second, and 15 seconds for each retry after
267 that. Hopefully this will improve the expected user experience.
268 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
269 to open a stream fails; now we do in more cases. This should
270 make clients able to find a good exit faster in some cases, since
271 unhandleable requests will now get an error rather than timing out.
273 o Major features, client functionality:
274 - Implement BEGIN_DIR cells, so we can connect to a directory
275 server via TLS to do encrypted directory requests rather than
276 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
277 config options if you like. For now, this feature only works if
278 you already have a descriptor for the destination dirserver.
279 - Add support for transparent application connections: this basically
280 bundles the functionality of trans-proxy-tor into the Tor
281 mainline. Now hosts with compliant pf/netfilter implementations
282 can redirect TCP connections straight to Tor without diverting
283 through SOCKS. (Based on patch from tup.)
284 - Add support for using natd; this allows FreeBSDs earlier than
285 5.1.2 to have ipfw send connections through Tor without using
286 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
288 o Major features, servers:
289 - Setting up a dyndns name for your server is now optional: servers
290 with no hostname or IP address will learn their IP address by
291 asking the directory authorities. This code only kicks in when you
292 would normally have exited with a "no address" error. Nothing's
293 authenticated, so use with care.
294 - Directory servers now spool server descriptors, v1 directories,
295 and v2 networkstatus objects to buffers as needed rather than en
296 masse. They also mmap the cached-routers files. These steps save
298 - Stop requiring clients to have well-formed certificates, and stop
299 checking nicknames in certificates. (Clients have certificates so
300 that they can look like Tor servers, but in the future we might want
301 to allow them to look like regular TLS clients instead. Nicknames
302 in certificates serve no purpose other than making our protocol
303 easier to recognize on the wire.) Implements proposal 106.
305 o Improvements on DNS support:
306 - Add "eventdns" asynchronous dns library originally based on code
307 from Adam Langley. Now we can discard the old rickety dnsworker
308 concept, and support a wider variety of DNS functions. Allows
309 multithreaded builds on NetBSD and OpenBSD again.
310 - Add server-side support for "reverse" DNS lookups (using PTR
311 records so clients can determine the canonical hostname for a given
312 IPv4 address). Only supported by servers using eventdns; servers
313 now announce in their descriptors if they don't support eventdns.
314 - Workaround for name servers (like Earthlink's) that hijack failing
315 DNS requests and replace the no-such-server answer with a "helpful"
316 redirect to an advertising-driven search portal. Also work around
317 DNS hijackers who "helpfully" decline to hijack known-invalid
318 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
319 lets you turn it off.
320 - Servers now check for the case when common DNS requests are going to
321 wildcarded addresses (i.e. all getting the same answer), and change
322 their exit policy to reject *:* if it's happening.
323 - When asked to resolve a hostname, don't use non-exit servers unless
324 requested to do so. This allows servers with broken DNS to be
325 useful to the network.
326 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
327 useless IPv6 DNS resolves.
328 - Specify and implement client-side SOCKS5 interface for reverse DNS
329 lookups (see doc/socks-extensions.txt). Also cache them.
330 - When we change nameservers or IP addresses, reset and re-launch
331 our tests for DNS hijacking.
333 o Improvements on reachability testing:
334 - Servers send out a burst of long-range padding cells once they've
335 established that they're reachable. Spread them over 4 circuits,
336 so hopefully a few will be fast. This exercises bandwidth and
337 bootstraps them into the directory more quickly.
338 - When we find our DirPort to be reachable, publish a new descriptor
339 so we'll tell the world (reported by pnx).
340 - Directory authorities now only decide that routers are reachable
341 if their identity keys are as expected.
342 - Do DirPort reachability tests less often, since a single test
343 chews through many circuits before giving up.
344 - Avoid some false positives during reachability testing: don't try
345 to test via a server that's on the same /24 network as us.
346 - Start publishing one minute or so after we find our ORPort
347 to be reachable. This will help reduce the number of descriptors
348 we have for ourselves floating around, since it's quite likely
349 other things (e.g. DirPort) will change during that minute too.
350 - Routers no longer try to rebuild long-term connections to directory
351 authorities, and directory authorities no longer try to rebuild
352 long-term connections to all servers. We still don't hang up
353 connections in these two cases though -- we need to look at it
354 more carefully to avoid flapping, and we likely need to wait til
357 o Improvements on rate limiting:
358 - Enable write limiting as well as read limiting. Now we sacrifice
359 capacity if we're pushing out lots of directory traffic, rather
360 than overrunning the user's intended bandwidth limits.
361 - Include TLS overhead when counting bandwidth usage; previously, we
362 would count only the bytes sent over TLS, but not the bytes used
364 - Servers decline directory requests much more aggressively when
365 they're low on bandwidth. Otherwise they end up queueing more and
366 more directory responses, which can't be good for latency.
367 - But never refuse directory requests from local addresses.
368 - Be willing to read or write on local connections (e.g. controller
369 connections) even when the global rate limiting buckets are empty.
370 - Flush local controller connection buffers periodically as we're
371 writing to them, so we avoid queueing 4+ megabytes of data before
373 - Revise and clean up the torrc.sample that we ship with; add
374 a section for BandwidthRate and BandwidthBurst.
376 o Major features, NT services:
377 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
378 command-line flag so that admins can override the default by saying
379 "tor --service install --user "SomeUser"". This will not affect
380 existing installed services. Also, warn the user that the service
381 will look for its configuration file in the service user's
382 %appdata% directory. (We can't do the "hardwire the user's appdata
383 directory" trick any more, since we may not have read access to that
385 - Support running the Tor service with a torrc not in the same
386 directory as tor.exe and default to using the torrc located in
387 the %appdata%\Tor\ of the user who installed the service. Patch
389 - Add an --ignore-missing-torrc command-line option so that we can
390 get the "use sensible defaults if the configuration file doesn't
391 exist" behavior even when specifying a torrc location on the
393 - When stopping an NT service, wait up to 10 sec for it to actually
394 stop. (Patch from Matt Edman; resolves bug 295.)
396 o Directory authority improvements:
397 - Stop letting hibernating or obsolete servers affect uptime and
399 - Stop listing hibernating servers in the v1 directory.
400 - Authorities no longer recommend exits as guards if this would shift
401 too much load to the exit nodes.
402 - Authorities now specify server versions in networkstatus. This adds
403 about 2% to the size of compressed networkstatus docs, and allows
404 clients to tell which servers support BEGIN_DIR and which don't.
405 The implementation is forward-compatible with a proposed future
406 protocol version scheme not tied to Tor versions.
407 - DirServer configuration lines now have an orport= option so
408 clients can open encrypted tunnels to the authorities without
409 having downloaded their descriptors yet. Enabled for moria1,
410 moria2, tor26, and lefkada now in the default configuration.
411 - Add a BadDirectory flag to network status docs so that authorities
412 can (eventually) tell clients about caches they believe to be
413 broken. Not used yet.
414 - Allow authorities to list nodes as bad exits in their
415 approved-routers file by fingerprint or by address. If most
416 authorities set a BadExit flag for a server, clients don't think
417 of it as a general-purpose exit. Clients only consider authorities
418 that advertise themselves as listing bad exits.
419 - Patch from Steve Hildrey: Generate network status correctly on
420 non-versioning dirservers.
421 - Have directory authorities allow larger amounts of drift in uptime
422 without replacing the server descriptor: previously, a server that
423 restarted every 30 minutes could have 48 "interesting" descriptors
425 - Reserve the nickname "Unnamed" for routers that can't pick
426 a hostname: any router can call itself Unnamed; directory
427 authorities will never allocate Unnamed to any particular router;
428 clients won't believe that any router is the canonical Unnamed.
430 o Directory mirrors and clients:
431 - Discard any v1 directory info that's over 1 month old (for
432 directories) or over 1 week old (for running-routers lists).
433 - Clients track responses with status 503 from dirservers. After a
434 dirserver has given us a 503, we try not to use it until an hour has
435 gone by, or until we have no dirservers that haven't given us a 503.
436 - When we get a 503 from a directory, and we're not a server, we no
437 longer count the failure against the total number of failures
438 allowed for the object we're trying to download.
439 - Prepare for servers to publish descriptors less often: never
440 discard a descriptor simply for being too old until either it is
441 recommended by no authorities, or until we get a better one for
442 the same router. Make caches consider retaining old recommended
443 routers for even longer.
444 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
445 headers for content, so that we can work better in the presence of
446 caching HTTP proxies.
447 - Stop fetching descriptors if you're not a dir mirror and you
448 haven't tried to establish any circuits lately. (This currently
449 causes some dangerous behavior, because when you start up again
450 you'll use your ancient server descriptors.)
452 o Major fixes, crashes:
453 - Stop crashing when the controller asks us to resetconf more than
454 one config option at once. (Vidalia 0.0.11 does this.)
455 - Fix a longstanding obscure crash bug that could occur when we run
456 out of DNS worker processes, if we're not using eventdns. (Resolves
458 - Fix an assert that could trigger if a controller quickly set then
459 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
460 - Avoid crash when telling controller about stream-status and a
462 - Avoid sending junk to controllers or segfaulting when a controller
463 uses EVENT_NEW_DESC with verbose nicknames.
464 - Stop triggering asserts if the controller tries to extend hidden
465 service circuits (reported by mwenge).
466 - If we start a server with ClientOnly 1, then set ClientOnly to 0
467 and hup, stop triggering an assert based on an empty onion_key.
468 - Mask out all signals in sub-threads; only the libevent signal
469 handler should be processing them. This should prevent some crashes
470 on some machines using pthreads. (Patch from coderman.)
471 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
473 o Major fixes, anonymity/security:
474 - Automatically avoid picking more than one node from the same
475 /16 network when constructing a circuit. Add an
476 "EnforceDistinctSubnets" option to let people disable it if they
477 want to operate private test networks on a single subnet.
478 - When generating bandwidth history, round down to the nearest
479 1k. When storing accounting data, round up to the nearest 1k.
480 - When we're running as a server, remember when we last rotated onion
481 keys, so that we will rotate keys once they're a week old even if
482 we never stay up for a week ourselves.
483 - If a client asked for a server by name, and there's a named server
484 in our network-status but we don't have its descriptor yet, we
485 could return an unnamed server instead.
486 - Reject (most) attempts to use Tor circuits with length one. (If
487 many people start using Tor as a one-hop proxy, exit nodes become
488 a more attractive target for compromise.)
489 - Just because your DirPort is open doesn't mean people should be
490 able to remotely teach you about hidden service descriptors. Now
491 only accept rendezvous posts if you've got HSAuthoritativeDir set.
492 - Fix a potential race condition in the rpm installer. Found by
494 - Do not log IPs with TLS failures for incoming TLS
495 connections. (Fixes bug 382.)
497 o Major fixes, other:
498 - If our system clock jumps back in time, don't publish a negative
499 uptime in the descriptor.
500 - When we start during an accounting interval before it's time to wake
501 up, remember to wake up at the correct time. (May fix bug 342.)
502 - Previously, we would cache up to 16 old networkstatus documents
503 indefinitely, if they came from nontrusted authorities. Now we
504 discard them if they are more than 10 days old.
505 - When we have a state file we cannot parse, tell the user and
506 move it aside. Now we avoid situations where the user starts
507 Tor in 1904, Tor writes a state file with that timestamp in it,
508 the user fixes her clock, and Tor refuses to start.
509 - Publish a new descriptor after we hup/reload. This is important
510 if our config has changed such that we'll want to start advertising
511 our DirPort now, etc.
512 - If we are using an exit enclave and we can't connect, e.g. because
513 its webserver is misconfigured to not listen on localhost, then
514 back off and try connecting from somewhere else before we fail.
516 o New config options or behaviors:
517 - When EntryNodes are configured, rebuild the guard list to contain,
518 in order: the EntryNodes that were guards before; the rest of the
519 EntryNodes; the nodes that were guards before.
520 - Do not warn when individual nodes in the configuration's EntryNodes,
521 ExitNodes, etc are down: warn only when all possible nodes
522 are down. (Fixes bug 348.)
523 - Put a lower-bound on MaxAdvertisedBandwidth.
524 - Start using the state file to store bandwidth accounting data:
525 the bw_accounting file is now obsolete. We'll keep generating it
526 for a while for people who are still using 0.1.2.4-alpha.
527 - Try to batch changes to the state file so that we do as few
528 disk writes as possible while still storing important things in
530 - The state file and the bw_accounting file get saved less often when
531 the AvoidDiskWrites config option is set.
532 - Make PIDFile work on Windows.
533 - Add internal descriptions for a bunch of configuration options:
534 accessible via controller interface and in comments in saved
536 - Reject *:563 (NNTPS) in the default exit policy. We already reject
537 NNTP by default, so this seems like a sensible addition.
538 - Clients now reject hostnames with invalid characters. This should
539 avoid some inadvertent info leaks. Add an option
540 AllowNonRFC953Hostnames to disable this behavior, in case somebody
541 is running a private network with hosts called @, !, and #.
542 - Check for addresses with invalid characters at the exit as well,
543 and warn less verbosely when they fail. You can override this by
544 setting ServerDNSAllowNonRFC953Addresses to 1.
545 - Remove some options that have been deprecated since at least
546 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
547 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
548 to set log options. Mark PathlenCoinWeight as obsolete.
549 - Stop accepting certain malformed ports in configured exit policies.
550 - When the user uses bad syntax in the Log config line, stop
551 suggesting other bad syntax as a replacement.
552 - Add new config option "ResolvConf" to let the server operator
553 choose an alternate resolve.conf file when using eventdns.
554 - If one of our entry guards is on the ExcludeNodes list, or the
555 directory authorities don't think it's a good guard, treat it as
556 if it were unlisted: stop using it as a guard, and throw it off
557 the guards list if it stays that way for a long time.
558 - Allow directory authorities to be marked separately as authorities
559 for the v1 directory protocol, the v2 directory protocol, and
560 as hidden service directories, to make it easier to retire old
561 authorities. V1 authorities should set "HSAuthoritativeDir 1"
562 to continue being hidden service authorities too.
563 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
564 - Make TrackExitHosts case-insensitive, and fix the behavior of
565 ".suffix" TrackExitHosts items to avoid matching in the middle of
567 - New DirPort behavior: if you have your dirport set, you download
568 descriptors aggressively like a directory mirror, whether or not
572 - Create a new file ReleaseNotes which was the old ChangeLog. The
573 new ChangeLog file now includes the notes for all development
575 - Add a new address-spec.txt document to describe our special-case
576 addresses: .exit, .onion, and .noconnnect.
577 - Fork the v1 directory protocol into its own spec document,
578 and mark dir-spec.txt as the currently correct (v2) spec.
580 o Packaging, porting, and contrib
581 - "tor --verify-config" now exits with -1(255) or 0 depending on
582 whether the config options are bad or good.
583 - The Debian package now uses --verify-config when (re)starting,
584 to distinguish configuration errors from other errors.
585 - Adapt a patch from goodell to let the contrib/exitlist script
586 take arguments rather than require direct editing.
587 - Prevent the contrib/exitlist script from printing the same
588 result more than once.
589 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
590 - In the hidden service example in torrc.sample, stop recommending
591 esoteric and discouraged hidden service options.
592 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
593 values before failing, and always enables eventdns.
594 - Try to detect Windows correctly when cross-compiling.
595 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
596 Try to fix this in configure.in by checking for most functions
597 before we check for libevent.
598 - Update RPMs to require libevent 1.2.
599 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
600 or later. Log when we are doing this, so we can diagnose it when
601 it fails. (Also, recommend libevent 1.1b for kqueue and
602 win32 methods; deprecate libevent 1.0b harder; make libevent
603 recommendation system saner.)
604 - Build with recent (1.3+) libevents on platforms that do not
605 define the nonstandard types "u_int8_t" and friends.
606 - Remove architecture from OS X builds. The official builds are
607 now universal binaries.
608 - Run correctly on OS X platforms with case-sensitive filesystems.
609 - Correctly set maximum connection limit on Cygwin. (This time
611 - Start compiling on MinGW on Windows (patches from Mike Chiussi
613 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
614 - Finally fix the openssl warnings from newer gccs that believe that
615 ignoring a return value is okay, but casting a return value and
616 then ignoring it is a sign of madness.
617 - On architectures where sizeof(int)>4, still clamp declarable
618 bandwidth to INT32_MAX.
620 o Minor features, controller:
621 - Warn the user when an application uses the obsolete binary v0
622 control protocol. We're planning to remove support for it during
623 the next development series, so it's good to give people some
625 - Add STREAM_BW events to report per-entry-stream bandwidth
626 use. (Patch from Robert Hogan.)
627 - Rate-limit SIGNEWNYM signals in response to controllers that
628 impolitely generate them for every single stream. (Patch from
629 mwenge; closes bug 394.)
630 - Add a REMAP status to stream events to note that a stream's
631 address has changed because of a cached address or a MapAddress
633 - Make REMAP stream events have a SOURCE (cache or exit), and
634 make them generated in every case where we get a successful
635 connected or resolved cell.
636 - Track reasons for OR connection failure; make these reasons
637 available via the controller interface. (Patch from Mike Perry.)
638 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
639 can learn when clients are sending malformed hostnames to Tor.
640 - Specify and implement some of the controller status events.
641 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
642 - Reimplement GETINFO so that info/names stays in sync with the
644 - Implement "GETINFO fingerprint".
645 - Implement "SETEVENTS GUARD" so controllers can get updates on
646 entry guard status as it changes.
647 - Make all connections to addresses of the form ".noconnect"
648 immediately get closed. This lets application/controller combos
649 successfully test whether they're talking to the same Tor by
650 watching for STREAM events.
651 - Add a REASON field to CIRC events; for backward compatibility, this
652 field is sent only to controllers that have enabled the extended
653 event format. Also, add additional reason codes to explain why
654 a given circuit has been destroyed or truncated. (Patches from
656 - Add a REMOTE_REASON field to extended CIRC events to tell the
657 controller why a remote OR told us to close a circuit.
658 - Stream events also now have REASON and REMOTE_REASON fields,
659 working much like those for circuit events.
660 - There's now a GETINFO ns/... field so that controllers can ask Tor
661 about the current status of a router.
662 - A new event type "NS" to inform a controller when our opinion of
663 a router's status has changed.
664 - Add a GETINFO events/names and GETINFO features/names so controllers
665 can tell which events and features are supported.
666 - A new CLEARDNSCACHE signal to allow controllers to clear the
667 client-side DNS cache without expiring circuits.
668 - Fix CIRC controller events so that controllers can learn the
669 identity digests of non-Named servers used in circuit paths.
670 - Let controllers ask for more useful identifiers for servers. Instead
671 of learning identity digests for un-Named servers and nicknames
672 for Named servers, the new identifiers include digest, nickname,
673 and indication of Named status. Off by default; see control-spec.txt
674 for more information.
675 - Add a "getinfo address" controller command so it can display Tor's
676 best guess to the user.
677 - New controller event to alert the controller when our server
678 descriptor has changed.
679 - Give more meaningful errors on controller authentication failure.
680 - Export the default exit policy via the control port, so controllers
681 don't need to guess what it is / will be later.
683 o Minor bugfixes, controller:
684 - When creating a circuit via the controller, send a 'launched'
685 event when we're done, so we follow the spec better.
686 - Correct the control spec to match how the code actually responds
687 to 'getinfo addr-mappings/*'. Reported by daejees.
688 - The control spec described a GUARDS event, but the code
689 implemented a GUARD event. Standardize on GUARD, but let people
690 ask for GUARDS too. Reported by daejees.
691 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
692 clear the corresponding on_circuit variable, and remember later
693 that we don't need to send a redundant CLOSED event. (Resolves part
695 - Report events where a resolve succeeded or where we got a socks
696 protocol error correctly, rather than calling both of them
698 - Change reported stream target addresses to IP consistently when
699 we finally get the IP from an exit node.
700 - Send log messages to the controller even if they happen to be very
702 - Flush ERR-level controller status events just like we currently
703 flush ERR-level log events, so that a Tor shutdown doesn't prevent
704 the controller from learning about current events.
705 - Report the circuit number correctly in STREAM CLOSED events. Bug
706 reported by Mike Perry.
707 - Do not report bizarre values for results of accounting GETINFOs
708 when the last second's write or read exceeds the allotted bandwidth.
709 - Report "unrecognized key" rather than an empty string when the
710 controller tries to fetch a networkstatus that doesn't exist.
711 - When the controller does a "GETINFO network-status", tell it
712 about even those routers whose descriptors are very old, and use
713 long nicknames where appropriate.
714 - Fix handling of verbose nicknames with ORCONN controller events:
715 make them show up exactly when requested, rather than exactly when
717 - Controller signals now work on non-Unix platforms that don't define
718 SIGUSR1 and SIGUSR2 the way we expect.
719 - Respond to SIGNAL command before we execute the signal, in case
720 the signal shuts us down. Suggested by Karsten Loesing.
721 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
723 o Minor features, code performance:
724 - Major performance improvement on inserting descriptors: change
725 algorithm from O(n^2) to O(n).
726 - Do not rotate onion key immediately after setting it for the first
728 - Call router_have_min_dir_info half as often. (This is showing up in
729 some profiles, but not others.)
730 - When using GCC, make log_debug never get called at all, and its
731 arguments never get evaluated, when no debug logs are configured.
732 (This is showing up in some profiles, but not others.)
733 - Statistics dumped by -USR2 now include a breakdown of public key
734 operations, for profiling.
735 - Make the common memory allocation path faster on machines where
736 malloc(0) returns a pointer.
737 - Split circuit_t into origin_circuit_t and or_circuit_t, and
738 split connection_t into edge, or, dir, control, and base structs.
739 These will save quite a bit of memory on busy servers, and they'll
740 also help us track down bugs in the code and bugs in the spec.
741 - Use OpenSSL's AES implementation on platforms where it's faster.
742 This could save us as much as 10% CPU usage.
744 o Minor features, descriptors and descriptor handling:
745 - Avoid duplicate entries on MyFamily line in server descriptor.
746 - When Tor receives a router descriptor that it asked for, but
747 no longer wants (because it has received fresh networkstatuses
748 in the meantime), do not warn the user. Cache the descriptor if
749 we're a cache; drop it if we aren't.
750 - Servers no longer ever list themselves in their "family" line,
751 even if configured to do so. This makes it easier to configure
752 family lists conveniently.
754 o Minor fixes, confusing/misleading log messages:
755 - Display correct results when reporting which versions are
756 recommended, and how recommended they are. (Resolves bug 383.)
757 - Inform the server operator when we decide not to advertise a
758 DirPort due to AccountingMax enabled or a low BandwidthRate.
759 - Only include function names in log messages for info/debug messages.
760 For notice/warn/err, the content of the message should be clear on
761 its own, and printing the function name only confuses users.
762 - Remove even more protocol-related warnings from Tor server logs,
763 such as bad TLS handshakes and malformed begin cells.
764 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
765 when the IP address is mapped through MapAddress to a hostname.
766 - Fix misleading log messages: an entry guard that is "unlisted",
767 as well as not known to be "down" (because we've never heard
768 of it), is not therefore "up".
770 o Minor fixes, old/obsolete behavior:
771 - Start assuming we can use a create_fast cell if we don't know
772 what version a router is running.
773 - We no longer look for identity and onion keys in "identity.key" and
774 "onion.key" -- these were replaced by secret_id_key and
775 secret_onion_key in 0.0.8pre1.
776 - We no longer require unrecognized directory entries to be
778 - Drop compatibility with obsolete Tors that permit create cells
779 to have the wrong circ_id_type.
780 - Remove code to special-case "-cvs" ending, since it has not
781 actually mattered since 0.0.9.
782 - Don't re-write the fingerprint file every restart, unless it has
785 o Minor fixes, misc client-side behavior:
786 - Always remove expired routers and networkstatus docs before checking
787 whether we have enough information to build circuits. (Fixes
789 - When computing clock skew from directory HTTP headers, consider what
790 time it was when we finished asking for the directory, not what
792 - Make our socks5 handling more robust to broken socks clients:
793 throw out everything waiting on the buffer in between socks
794 handshake phases, since they can't possibly (so the theory
795 goes) have predicted what we plan to respond to them.
796 - Expire socks connections if they spend too long waiting for the
797 handshake to finish. Previously we would let them sit around for
798 days, if the connecting application didn't close them either.
799 - And if the socks handshake hasn't started, don't send a
800 "DNS resolve socks failed" handshake reply; just close it.
801 - If the user asks to use invalid exit nodes, be willing to use
803 - Track unreachable entry guards correctly: don't conflate
804 'unreachable by us right now' with 'listed as down by the directory
805 authorities'. With the old code, if a guard was unreachable by us
806 but listed as running, it would clog our guard list forever.
807 - Behave correctly in case we ever have a network with more than
808 2GB/s total advertised capacity.
809 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
810 - Fix a memory leak when we ask for "all" networkstatuses and we
811 get one we don't recognize.
814 Changes in version 0.1.1.26 - 2006-12-14
816 - Stop sending the HttpProxyAuthenticator string to directory
817 servers when directory connections are tunnelled through Tor.
818 - Clients no longer store bandwidth history in the state file.
819 - Do not log introduction points for hidden services if SafeLogging
823 - Fix an assert failure when a directory authority sets
824 AuthDirRejectUnlisted and then receives a descriptor from an
825 unlisted router (reported by seeess).
828 Changes in version 0.1.1.25 - 2006-11-04
830 - When a client asks us to resolve (rather than connect to)
831 an address, and we have a cached answer, give them the cached
832 answer. Previously, we would give them no answer at all.
833 - We were building exactly the wrong circuits when we predict
834 hidden service requirements, meaning Tor would have to build all
835 its circuits on demand.
836 - If none of our live entry guards have a high uptime, but we
837 require a guard with a high uptime, try adding a new guard before
838 we give up on the requirement. This patch should make long-lived
839 connections more stable on average.
840 - When testing reachability of our DirPort, don't launch new
841 tests when there's already one in progress -- unreachable
842 servers were stacking up dozens of testing streams.
845 - When the user sends a NEWNYM signal, clear the client-side DNS
846 cache too. Otherwise we continue to act on previous information.
849 - Avoid a memory corruption bug when creating a hash table for
851 - Avoid possibility of controller-triggered crash when misusing
852 certain commands from a v0 controller on platforms that do not
853 handle printf("%s",NULL) gracefully.
854 - Avoid infinite loop on unexpected controller input.
855 - Don't log spurious warnings when we see a circuit close reason we
856 don't recognize; it's probably just from a newer version of Tor.
857 - Add Vidalia to the OS X uninstaller script, so when we uninstall
858 Tor/Privoxy we also uninstall Vidalia.
861 Changes in version 0.1.1.24 - 2006-09-29
863 - Allow really slow clients to not hang up five minutes into their
864 directory downloads (suggested by Adam J. Richter).
865 - Fix major performance regression from 0.1.0.x: instead of checking
866 whether we have enough directory information every time we want to
867 do something, only check when the directory information has changed.
868 This should improve client CPU usage by 25-50%.
869 - Don't crash if, after a server has been running for a while,
870 it can't resolve its hostname.
871 - When a client asks us to resolve (not connect to) an address,
872 and we have a cached answer, give them the cached answer.
873 Previously, we would give them no answer at all.
876 - Allow Tor to start when RunAsDaemon is set but no logs are set.
877 - Don't crash when the controller receives a third argument to an
878 "extendcircuit" request.
879 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
880 response; fix error code when "getinfo dir/status/" fails.
881 - Fix configure.in to not produce broken configure files with
882 more recent versions of autoconf. Thanks to Clint for his auto*
884 - Fix security bug on NetBSD that could allow someone to force
885 uninitialized RAM to be sent to a server's DNS resolver. This
886 only affects NetBSD and other platforms that do not bounds-check
888 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
889 methods: these are known to be buggy.
890 - If we're a directory mirror and we ask for "all" network status
891 documents, we would discard status documents from authorities
895 Changes in version 0.1.1.23 - 2006-07-30
897 - Fast Tor servers, especially exit nodes, were triggering asserts
898 due to a bug in handling the list of pending DNS resolves. Some
899 bugs still remain here; we're hunting them.
900 - Entry guards could crash clients by sending unexpected input.
901 - More fixes on reachability testing: if you find yourself reachable,
902 then don't ever make any client requests (so you stop predicting
903 circuits), then hup or have your clock jump, then later your IP
904 changes, you won't think circuits are working, so you won't try to
905 test reachability, so you won't publish.
908 - Avoid a crash if the controller does a resetconf firewallports
909 and then a setconf fascistfirewall=1.
910 - Avoid an integer underflow when the dir authority decides whether
911 a router is stable: we might wrongly label it stable, and compute
912 a slightly wrong median stability, when a descriptor is published
914 - Fix a place where we might trigger an assert if we can't build our
915 own server descriptor yet.
918 Changes in version 0.1.1.22 - 2006-07-05
920 - Fix a big bug that was causing servers to not find themselves
921 reachable if they changed IP addresses. Since only 0.1.1.22+
922 servers can do reachability testing correctly, now we automatically
923 make sure to test via one of these.
924 - Fix to allow clients and mirrors to learn directory info from
925 descriptor downloads that get cut off partway through.
926 - Directory authorities had a bug in deciding if a newly published
927 descriptor was novel enough to make everybody want a copy -- a few
928 servers seem to be publishing new descriptors many times a minute.
930 - Fix a rare bug that was causing some servers to complain about
931 "closing wedged cpuworkers" and skip some circuit create requests.
932 - Make the Exit flag in directory status documents actually work.
935 Changes in version 0.1.1.21 - 2006-06-10
936 o Crash and assert fixes from 0.1.1.20:
937 - Fix a rare crash on Tor servers that have enabled hibernation.
938 - Fix a seg fault on startup for Tor networks that use only one
940 - Fix an assert from a race condition that occurs on Tor servers
941 while exiting, where various threads are trying to log that they're
942 exiting, and delete the logs, at the same time.
943 - Make our unit tests pass again on certain obscure platforms.
946 - Add support for building SUSE RPM packages.
947 - Speed up initial bootstrapping for clients: if we are making our
948 first ever connection to any entry guard, then don't mark it down
950 - When only one Tor server in the network is labelled as a guard,
951 and we've already picked him, we would cycle endlessly picking him
952 again, being unhappy about it, etc. Now we specifically exclude
953 current guards when picking a new guard.
954 - Servers send create cells more reliably after the TLS connection
955 is established: we were sometimes forgetting to send half of them
956 when we had more than one pending.
957 - If we get a create cell that asks us to extend somewhere, but the
958 Tor server there doesn't match the expected digest, we now send
959 a destroy cell back, rather than silently doing nothing.
960 - Make options->RedirectExit work again.
961 - Make cookie authentication for the controller work again.
962 - Stop being picky about unusual characters in the arguments to
963 mapaddress. It's none of our business.
964 - Add a new config option "TestVia" that lets you specify preferred
965 middle hops to use for test circuits. Perhaps this will let me
966 debug the reachability problems better.
968 o Log / documentation fixes:
969 - If we're a server and some peer has a broken TLS certificate, don't
970 log about it unless ProtocolWarnings is set, i.e., we want to hear
971 about protocol violations by others.
972 - Fix spelling of VirtualAddrNetwork in man page.
973 - Add a better explanation at the top of the autogenerated torrc file
974 about what happened to our old torrc.
977 Changes in version 0.1.1.20 - 2006-05-23
978 o Crash and assert fixes from 0.1.0.17:
979 - Fix assert bug in close_logs() on exit: when we close and delete
980 logs, remove them all from the global "logfiles" list.
981 - Fix an assert error when we're out of space in the connection_list
982 and we try to post a hidden service descriptor (reported by Peter
984 - Fix a rare assert error when we've tried all intro points for
985 a hidden service and we try fetching the service descriptor again:
986 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
987 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
988 out and refuse the setconf if it would fail.
989 - If you specify a relative torrc path and you set RunAsDaemon in
990 your torrc, then it chdir()'s to the new directory. If you then
991 HUP, it tries to load the new torrc location, fails, and exits.
992 The fix: no longer allow a relative path to torrc when using -f.
993 - Check for integer overflows in more places, when adding elements
994 to smartlists. This could possibly prevent a buffer overflow
995 on malicious huge inputs.
997 o Security fixes, major:
998 - When we're printing strings from the network, don't try to print
999 non-printable characters. Now we're safer against shell escape
1000 sequence exploits, and also against attacks to fool users into
1001 misreading their logs.
1002 - Implement entry guards: automatically choose a handful of entry
1003 nodes and stick with them for all circuits. Only pick new guards
1004 when the ones you have are unsuitable, and if the old guards
1005 become suitable again, switch back. This will increase security
1006 dramatically against certain end-point attacks. The EntryNodes
1007 config option now provides some hints about which entry guards you
1008 want to use most; and StrictEntryNodes means to only use those.
1009 Fixes CVE-2006-0414.
1010 - Implement exit enclaves: if we know an IP address for the
1011 destination, and there's a running Tor server at that address
1012 which allows exit to the destination, then extend the circuit to
1013 that exit first. This provides end-to-end encryption and end-to-end
1014 authentication. Also, if the user wants a .exit address or enclave,
1015 use 4 hops rather than 3, and cannibalize a general circ for it
1017 - Obey our firewall options more faithfully:
1018 . If we can't get to a dirserver directly, try going via Tor.
1019 . Don't ever try to connect (as a client) to a place our
1020 firewall options forbid.
1021 . If we specify a proxy and also firewall options, obey the
1022 firewall options even when we're using the proxy: some proxies
1023 can only proxy to certain destinations.
1024 - Make clients regenerate their keys when their IP address changes.
1025 - For the OS X package's modified privoxy config file, comment
1026 out the "logfile" line so we don't log everything passed
1028 - Our TLS handshakes were generating a single public/private
1029 keypair for the TLS context, rather than making a new one for
1030 each new connection. Oops. (But we were still rotating them
1031 periodically, so it's not so bad.)
1032 - When we were cannibalizing a circuit with a particular exit
1033 node in mind, we weren't checking to see if that exit node was
1034 already present earlier in the circuit. Now we are.
1035 - Require server descriptors to list IPv4 addresses -- hostnames
1036 are no longer allowed. This also fixes potential vulnerabilities
1037 to servers providing hostnames as their address and then
1038 preferentially resolving them so they can partition users.
1039 - Our logic to decide if the OR we connected to was the right guy
1040 was brittle and maybe open to a mitm for invalid routers.
1042 o Security fixes, minor:
1043 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
1044 Ian Goldberg can prove things about our handshake protocol more
1046 - Make directory authorities generate a separate "guard" flag to
1047 mean "would make a good entry guard". Clients now honor the
1048 is_guard flag rather than looking at is_fast or is_stable.
1049 - Try to list MyFamily elements by key, not by nickname, and warn
1050 if we've not heard of a server.
1051 - Start using RAND_bytes rather than RAND_pseudo_bytes from
1052 OpenSSL. Also, reseed our entropy every hour, not just at
1053 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
1054 - Refuse server descriptors where the fingerprint line doesn't match
1055 the included identity key. Tor doesn't care, but other apps (and
1056 humans) might actually be trusting the fingerprint line.
1057 - We used to kill the circuit when we receive a relay command we
1058 don't recognize. Now we just drop that cell.
1059 - Fix a bug found by Lasse Overlier: when we were making internal
1060 circuits (intended to be cannibalized later for rendezvous and
1061 introduction circuits), we were picking them so that they had
1062 useful exit nodes. There was no need for this, and it actually
1063 aids some statistical attacks.
1064 - Start treating internal circuits and exit circuits separately.
1065 It's important to keep them separate because internal circuits
1066 have their last hops picked like middle hops, rather than like
1067 exit hops. So exiting on them will break the user's expectations.
1068 - Fix a possible way to DoS dirservers.
1069 - When the client asked for a rendezvous port that the hidden
1070 service didn't want to provide, we were sending an IP address
1071 back along with the end cell. Fortunately, it was zero. But stop
1074 o Packaging improvements:
1075 - Implement --with-libevent-dir option to ./configure. Improve
1076 search techniques to find libevent, and use those for openssl too.
1077 - Fix a couple of bugs in OpenSSL detection. Deal better when
1078 there are multiple SSLs installed with different versions.
1079 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
1080 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
1082 - Make unit tests (and other invocations that aren't the real Tor)
1083 run without launching listeners, creating subdirectories, and so on.
1084 - The OS X installer was adding a symlink for tor_resolve but
1085 the binary was called tor-resolve (reported by Thomas Hardly).
1086 - Now we can target arch and OS in rpm builds (contributed by
1087 Phobos). Also make the resulting dist-rpm filename match the
1089 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
1090 if you log to syslog and want something other than LOG_DAEMON.
1091 - Fix the torify (tsocks) config file to not use Tor for localhost
1093 - Start shipping socks-extensions.txt, tor-doc-unix.html,
1094 tor-doc-server.html, and stylesheet.css in the tarball.
1095 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
1096 They are useless now.
1097 - Add Peter Palfrader's contributed check-tor script. It lets you
1098 easily check whether a given server (referenced by nickname)
1099 is reachable by you.
1100 - Add BSD-style contributed startup script "rc.subr" from Peter
1103 o Directory improvements -- new directory protocol:
1104 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
1105 - Authorities and caches publish individual descriptors (by
1106 digest, by fingerprint, by "all", and by "tell me yours").
1107 - Clients don't download or use the old directory anymore. Now they
1108 download network-statuses from the directory authorities, and
1109 fetch individual server descriptors as needed from mirrors.
1110 - Clients don't download descriptors of non-running servers.
1111 - Download descriptors by digest, not by fingerprint. Caches try to
1112 download all listed digests from authorities; clients try to
1113 download "best" digests from caches. This avoids partitioning
1114 and isolating attacks better.
1115 - Only upload a new server descriptor when options change, 18
1116 hours have passed, uptime is reset, or bandwidth changes a lot.
1117 - Directory authorities silently throw away new descriptors that
1118 haven't changed much if the timestamps are similar. We do this to
1119 tolerate older Tor servers that upload a new descriptor every 15
1120 minutes. (It seemed like a good idea at the time.)
1121 - Clients choose directory servers from the network status lists,
1122 not from their internal list of router descriptors. Now they can
1123 go to caches directly rather than needing to go to authorities
1124 to bootstrap the first set of descriptors.
1125 - When picking a random directory, prefer non-authorities if any
1127 - Add a new flag to network-status indicating whether the server
1128 can answer v2 directory requests too.
1129 - Directory mirrors now cache up to 16 unrecognized network-status
1130 docs, so new directory authorities will be cached too.
1131 - Stop parsing, storing, or using running-routers output (but
1132 mirrors still cache and serve it).
1133 - Clients consider a threshold of "versioning" directory authorities
1134 before deciding whether to warn the user that he's obsolete.
1135 - Authorities publish separate sorted lists of recommended versions
1136 for clients and for servers.
1137 - Change DirServers config line to note which dirs are v1 authorities.
1138 - Put nicknames on the DirServer line, so we can refer to them
1139 without requiring all our users to memorize their IP addresses.
1140 - Remove option when getting directory cache to see whether they
1141 support running-routers; they all do now. Replace it with one
1142 to see whether caches support v2 stuff.
1143 - Stop listing down or invalid nodes in the v1 directory. This
1144 reduces its bulk by about 1/3, and reduces load on mirrors.
1145 - Mirrors no longer cache the v1 directory as often.
1146 - If we as a directory mirror don't know of any v1 directory
1147 authorities, then don't try to cache any v1 directories.
1149 o Other directory improvements:
1150 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
1151 fifth authoritative directory servers.
1152 - Directory authorities no longer require an open connection from
1153 a server to consider him "reachable". We need this change because
1154 when we add new directory authorities, old servers won't know not
1156 - Dir authorities now do their own external reachability testing
1157 of each server, and only list as running the ones they found to
1158 be reachable. We also send back warnings to the server's logs if
1159 it uploads a descriptor that we already believe is unreachable.
1160 - Spread the directory authorities' reachability testing over the
1161 entire testing interval, so we don't try to do 500 TLS's at once
1163 - Make the "stable" router flag in network-status be the median of
1164 the uptimes of running valid servers, and make clients pay
1165 attention to the network-status flags. Thus the cutoff adapts
1166 to the stability of the network as a whole, making IRC, IM, etc
1167 connections more reliable.
1168 - Make the v2 dir's "Fast" flag based on relative capacity, just
1169 like "Stable" is based on median uptime. Name everything in the
1170 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
1171 - Retry directory requests if we fail to get an answer we like
1172 from a given dirserver (we were retrying before, but only if
1173 we fail to connect).
1174 - Return a robots.txt on our dirport to discourage google indexing.
1176 o Controller protocol improvements:
1177 - Revised controller protocol (version 1) that uses ascii rather
1178 than binary: tor/doc/control-spec.txt. Add supporting libraries
1179 in python and java and c# so you can use the controller from your
1180 applications without caring how our protocol works.
1181 - Allow the DEBUG controller event to work again. Mark certain log
1182 entries as "don't tell this to controllers", so we avoid cycles.
1183 - New controller function "getinfo accounting", to ask how
1184 many bytes we've used in this time period.
1185 - Add a "resetconf" command so you can set config options like
1186 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
1187 a config option in the torrc with no value, then it clears it
1188 entirely (rather than setting it to its default).
1189 - Add a "getinfo config-file" to tell us where torrc is. Also
1190 expose guard nodes, config options/names.
1191 - Add a "quit" command (when when using the controller manually).
1192 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
1193 stop using any currently-dirty circuits for new streams, so we
1194 don't link new actions to old actions. This also occurs on HUP
1196 - If we would close a stream early (e.g. it asks for a .exit that
1197 we know would refuse it) but the LeaveStreamsUnattached config
1198 option is set by the controller, then don't close it.
1199 - Add a new controller event type "authdir_newdescs" that allows
1200 controllers to get all server descriptors that were uploaded to
1201 a router in its role as directory authority.
1202 - New controller option "getinfo desc/all-recent" to fetch the
1203 latest server descriptor for every router that Tor knows about.
1204 - Fix the controller's "attachstream 0" command to treat conn like
1205 it just connected, doing address remapping, handling .exit and
1206 .onion idioms, and so on. Now we're more uniform in making sure
1207 that the controller hears about new and closing connections.
1208 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
1209 the controller. Also, rotate dns and cpu workers if the controller
1210 changes options that will affect them; and initialize the dns
1211 worker cache tree whether or not we start out as a server.
1212 - Add a new circuit purpose 'controller' to let the controller ask
1213 for a circuit that Tor won't try to use. Extend the "extendcircuit"
1214 controller command to let you specify the purpose if you're starting
1215 a new circuit. Add a new "setcircuitpurpose" controller command to
1216 let you change a circuit's purpose after it's been created.
1217 - Let the controller ask for "getinfo dir/server/foo" so it can ask
1218 directly rather than connecting to the dir port. "getinfo
1219 dir/status/foo" also works, but currently only if your DirPort
1221 - Let the controller tell us about certain router descriptors
1222 that it doesn't want Tor to use in circuits. Implement
1223 "setrouterpurpose" and modify "+postdescriptor" to do this.
1224 - If the controller's *setconf commands fail, collect an error
1225 message in a string and hand it back to the controller -- don't
1226 just tell them to go read their logs.
1228 o Scalability, resource management, and performance:
1229 - Fix a major load balance bug: we were round-robin reading in 16 KB
1230 chunks, and servers with bandwidthrate of 20 KB, while downloading
1231 a 600 KB directory, would starve their other connections. Now we
1232 try to be a bit more fair.
1233 - Be more conservative about whether to advertise our DirPort.
1234 The main change is to not advertise if we're running at capacity
1235 and either a) we could hibernate ever or b) our capacity is low
1236 and we're using a default DirPort.
1237 - We weren't cannibalizing circuits correctly for
1238 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
1239 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
1240 build those from scratch. This should make hidden services faster.
1241 - Predict required circuits better, with an eye toward making hidden
1242 services faster on the service end.
1243 - Compress exit policies even more: look for duplicate lines and
1245 - Generate 18.0.0.0/8 address policy format in descs when we can;
1246 warn when the mask is not reducible to a bit-prefix.
1247 - There used to be two ways to specify your listening ports in a
1248 server descriptor: on the "router" line and with a separate "ports"
1249 line. Remove support for the "ports" line.
1250 - Reduce memory requirements in our structs by changing the order
1251 of fields. Replace balanced trees with hash tables. Inline
1252 bottleneck smartlist functions. Add a "Map from digest to void*"
1253 abstraction so we can do less hex encoding/decoding, and use it
1254 in router_get_by_digest(). Many other CPU and memory improvements.
1255 - Allow tor_gzip_uncompress to extract as much as possible from
1256 truncated compressed data. Try to extract as many
1257 descriptors as possible from truncated http responses (when
1258 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
1259 - Make circ->onionskin a pointer, not a static array. moria2 was using
1260 125000 circuit_t's after it had been up for a few weeks, which
1261 translates to 20+ megs of wasted space.
1262 - The private half of our EDH handshake keys are now chosen out
1263 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
1264 - Stop doing the complex voodoo overkill checking for insecure
1265 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
1266 - Do round-robin writes for TLS of at most 16 kB per write. This
1267 might be more fair on loaded Tor servers.
1268 - Do not use unaligned memory access on alpha, mips, or mipsel.
1269 It *works*, but is very slow, so we treat them as if it doesn't.
1271 o Other bugfixes and improvements:
1272 - Start storing useful information to $DATADIR/state, so we can
1273 remember things across invocations of Tor. Retain unrecognized
1274 lines so we can be forward-compatible, and write a TorVersion line
1275 so we can be backward-compatible.
1276 - If ORPort is set, Address is not explicitly set, and our hostname
1277 resolves to a private IP address, try to use an interface address
1278 if it has a public address. Now Windows machines that think of
1279 themselves as localhost can guess their address.
1280 - Regenerate our local descriptor if it's dirty and we try to use
1281 it locally (e.g. if it changes during reachability detection).
1282 This was causing some Tor servers to keep publishing the same
1283 initial descriptor forever.
1284 - Tor servers with dynamic IP addresses were needing to wait 18
1285 hours before they could start doing reachability testing using
1286 the new IP address and ports. This is because they were using
1287 the internal descriptor to learn what to test, yet they were only
1288 rebuilding the descriptor once they decided they were reachable.
1289 - It turns out we couldn't bootstrap a network since we added
1290 reachability detection in 0.1.0.1-rc. Good thing the Tor network
1291 has never gone down. Add an AssumeReachable config option to let
1292 servers and authorities bootstrap. When we're trying to build a
1293 high-uptime or high-bandwidth circuit but there aren't enough
1294 suitable servers, try being less picky rather than simply failing.
1295 - Newly bootstrapped Tor networks couldn't establish hidden service
1296 circuits until they had nodes with high uptime. Be more tolerant.
1297 - Really busy servers were keeping enough circuits open on stable
1298 connections that they were wrapping around the circuit_id
1299 space. (It's only two bytes.) This exposed a bug where we would
1300 feel free to reuse a circuit_id even if it still exists but has
1301 been marked for close. Try to fix this bug. Some bug remains.
1302 - When we fail to bind or listen on an incoming or outgoing
1303 socket, we now close it before refusing, rather than just
1304 leaking it. (Thanks to Peter Palfrader for finding.)
1305 - Fix a file descriptor leak in start_daemon().
1306 - On Windows, you can't always reopen a port right after you've
1307 closed it. So change retry_listeners() to only close and re-open
1308 ports that have changed.
1309 - Workaround a problem with some http proxies that refuse GET
1310 requests that specify "Content-Length: 0". Reported by Adrian.
1311 - Recover better from TCP connections to Tor servers that are
1312 broken but don't tell you (it happens!); and rotate TLS
1313 connections once a week.
1314 - Fix a scary-looking but apparently harmless bug where circuits
1315 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
1316 servers, and never switch to state CIRCUIT_STATE_OPEN.
1317 - Check for even more Windows version flags when writing the platform
1318 string in server descriptors, and note any we don't recognize.
1319 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
1320 get a better idea of why their circuits failed. Not used yet.
1321 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
1322 We don't use them yet, but maybe one day our DNS resolver will be
1323 able to discover them.
1324 - Let people type "tor --install" as well as "tor -install" when they
1325 want to make it an NT service.
1326 - Looks like we were never delivering deflated (i.e. compressed)
1327 running-routers lists, even when asked. Oops.
1328 - We were leaking some memory every time the client changed IPs.
1329 - Clean up more of the OpenSSL memory when exiting, so we can detect
1330 memory leaks better.
1331 - Never call free() on tor_malloc()d memory. This will help us
1332 use dmalloc to detect memory leaks.
1333 - Some Tor servers process billions of cells per day. These
1334 statistics are now uint64_t's.
1335 - Check [X-]Forwarded-For headers in HTTP requests when generating
1336 log messages. This lets people run dirservers (and caches) behind
1337 Apache but still know which IP addresses are causing warnings.
1338 - Fix minor integer overflow in calculating when we expect to use up
1339 our bandwidth allocation before hibernating.
1340 - Lower the minimum required number of file descriptors to 1000,
1341 so we can have some overhead for Valgrind on Linux, where the
1342 default ulimit -n is 1024.
1343 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
1344 and its existence is confusing some users.
1346 o Config option fixes:
1347 - Add a new config option ExitPolicyRejectPrivate which defaults
1348 to on. Now all exit policies will begin with rejecting private
1349 addresses, unless the server operator explicitly turns it off.
1350 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
1351 - Add new ReachableORAddresses and ReachableDirAddresses options
1352 that understand address policies. FascistFirewall is now a synonym
1353 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
1354 - Start calling it FooListenAddress rather than FooBindAddress,
1355 since few of our users know what it means to bind an address
1357 - If the user gave Tor an odd number of command-line arguments,
1358 we were silently ignoring the last one. Now we complain and fail.
1359 This wins the oldest-bug prize -- this bug has been present since
1360 November 2002, as released in Tor 0.0.0.
1361 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
1362 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
1363 it would silently ignore the 6668.
1364 - If we get a linelist or linelist_s config option from the torrc,
1365 e.g. ExitPolicy, and it has no value, warn and skip rather than
1366 silently resetting it to its default.
1367 - Setconf was appending items to linelists, not clearing them.
1368 - Add MyFamily to torrc.sample in the server section, so operators
1369 will be more likely to learn that it exists.
1370 - Make ContactInfo mandatory for authoritative directory servers.
1371 - MaxConn has been obsolete for a while now. Document the ConnLimit
1372 config option, which is a *minimum* number of file descriptors
1373 that must be available else Tor refuses to start.
1374 - Get rid of IgnoreVersion undocumented config option, and make us
1375 only warn, never exit, when we're running an obsolete version.
1376 - Make MonthlyAccountingStart config option truly obsolete now.
1377 - Correct the man page entry on TrackHostExitsExpire.
1378 - Let directory authorities start even if they don't specify an
1379 Address config option.
1380 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
1381 reflect the updated flags in our v2 dir protocol.
1383 o Config option features:
1384 - Add a new config option FastFirstHopPK (on by default) so clients
1385 do a trivial crypto handshake for their first hop, since TLS has
1386 already taken care of confidentiality and authentication.
1387 - Let the user set ControlListenAddress in the torrc. This can be
1388 dangerous, but there are some cases (like a secured LAN) where it
1390 - New config options to help controllers: FetchServerDescriptors
1391 and FetchHidServDescriptors for whether to fetch server
1392 info and hidserv info or let the controller do it, and
1393 PublishServerDescriptor and PublishHidServDescriptors.
1394 - Also let the controller set the __AllDirActionsPrivate config
1395 option if you want all directory fetches/publishes to happen via
1396 Tor (it assumes your controller bootstraps your circuits).
1397 - Add "HardwareAccel" config option: support for crypto hardware
1398 accelerators via OpenSSL. Off by default, until we find somebody
1399 smart who can test it for us. (It appears to produce seg faults
1400 in at least some cases.)
1401 - New config option "AuthDirRejectUnlisted" for directory authorities
1402 as a panic button: if we get flooded with unusable servers we can
1403 revert to only listing servers in the approved-routers file.
1404 - Directory authorities can now reject/invalidate by key and IP,
1405 with the config options "AuthDirInvalid" and "AuthDirReject", or
1406 by marking a fingerprint as "!reject" or "!invalid" (as its
1407 nickname) in the approved-routers file. This is useful since
1408 currently we automatically list servers as running and usable
1409 even if we know they're jerks.
1410 - Add a new config option TestSocks so people can see whether their
1411 applications are using socks4, socks4a, socks5-with-ip, or
1412 socks5-with-fqdn. This way they don't have to keep mucking
1413 with tcpdump and wondering if something got cached somewhere.
1414 - Add "private:*" as an alias in configuration for policies. Now
1415 you can simplify your exit policy rather than needing to list
1416 every single internal or nonroutable network space.
1417 - Accept "private:*" in routerdesc exit policies; not generated yet
1418 because older Tors do not understand it.
1419 - Add configuration option "V1AuthoritativeDirectory 1" which
1420 moria1, moria2, and tor26 have set.
1421 - Implement an option, VirtualAddrMask, to set which addresses
1422 get handed out in response to mapaddress requests. This works
1423 around a bug in tsocks where 127.0.0.0/8 is never socksified.
1424 - Add a new config option FetchUselessDescriptors, off by default,
1425 for when you plan to run "exitlist" on your client and you want
1426 to know about even the non-running descriptors.
1427 - SocksTimeout: How long do we let a socks connection wait
1428 unattached before we fail it?
1429 - CircuitBuildTimeout: Cull non-open circuits that were born
1430 at least this many seconds ago.
1431 - CircuitIdleTimeout: Cull open clean circuits that were born
1432 at least this many seconds ago.
1433 - New config option SafeSocks to reject all application connections
1434 using unsafe socks protocols. Defaults to off.
1436 o Improved and clearer log messages:
1437 - Reduce clutter in server logs. We're going to try to make
1438 them actually usable now. New config option ProtocolWarnings that
1439 lets you hear about how _other Tors_ are breaking the protocol. Off
1441 - Divide log messages into logging domains. Once we put some sort
1442 of interface on this, it will let people looking at more verbose
1443 log levels specify the topics they want to hear more about.
1444 - Log server fingerprint on startup, so new server operators don't
1445 have to go hunting around their filesystem for it.
1446 - Provide dire warnings to any users who set DirServer manually;
1447 move it out of torrc.sample and into torrc.complete.
1448 - Make the log message less scary when all the dirservers are
1449 temporarily unreachable.
1450 - When tor_socketpair() fails in Windows, give a reasonable
1451 Windows-style errno back.
1452 - Improve tor_gettimeofday() granularity on windows.
1453 - We were printing the number of idle dns workers incorrectly when
1455 - Handle duplicate lines in approved-routers files without warning.
1456 - We were whining about using socks4 or socks5-with-local-lookup
1457 even when it's an IP address in the "virtual" range we designed
1458 exactly for this case.
1459 - Check for named servers when looking them up by nickname;
1460 warn when we're calling a non-named server by its nickname;
1461 don't warn twice about the same name.
1462 - Downgrade the dirserver log messages when whining about
1464 - Correct "your server is reachable" log entries to indicate that
1465 it was self-testing that told us so.
1466 - If we're trying to be a Tor server and running Windows 95/98/ME
1467 as a server, explain that we'll likely crash.
1468 - Provide a more useful warn message when our onion queue gets full:
1469 the CPU is too slow or the exit policy is too liberal.
1470 - Don't warn when we receive a 503 from a dirserver/cache -- this
1471 will pave the way for them being able to refuse if they're busy.
1472 - When we fail to bind a listener, try to provide a more useful
1473 log message: e.g., "Is Tor already running?"
1474 - Only start testing reachability once we've established a
1475 circuit. This will make startup on dir authorities less noisy.
1476 - Don't try to upload hidden service descriptors until we have
1477 established a circuit.
1478 - Tor didn't warn when it failed to open a log file.
1479 - Warn when listening on a public address for socks. We suspect a
1480 lot of people are setting themselves up as open socks proxies,
1481 and they have no idea that jerks on the Internet are using them,
1482 since they simply proxy the traffic into the Tor network.
1483 - Give a useful message when people run Tor as the wrong user,
1484 rather than telling them to start chowning random directories.
1485 - Fix a harmless bug that was causing Tor servers to log
1486 "Got an end because of misc error, but we're not an AP. Closing."
1487 - Fix wrong log message when you add a "HiddenServiceNodes" config
1488 line without any HiddenServiceDir line (reported by Chris Thomas).
1489 - Directory authorities now stop whining so loudly about bad
1490 descriptors that they fetch from other dirservers. So when there's
1491 a log complaint, it's for sure from a freshly uploaded descriptor.
1492 - When logging via syslog, include the pid whenever we provide
1493 a log entry. Suggested by Todd Fries.
1494 - When we're shutting down and we do something like try to post a
1495 server descriptor or rendezvous descriptor, don't complain that
1496 we seem to be unreachable. Of course we are, we're shutting down.
1497 - Change log line for unreachability to explicitly suggest /etc/hosts
1498 as the culprit. Also make it clearer what IP address and ports we're
1499 testing for reachability.
1500 - Put quotes around user-supplied strings when logging so users are
1501 more likely to realize if they add bad characters (like quotes)
1503 - NT service patch from Matt Edman to improve error messages on Win32.
1506 Changes in version 0.1.0.17 - 2006-02-17
1507 o Crash bugfixes on 0.1.0.x:
1508 - When servers with a non-zero DirPort came out of hibernation,
1509 sometimes they would trigger an assert.
1511 o Other important bugfixes:
1512 - On platforms that don't have getrlimit (like Windows), we were
1513 artificially constraining ourselves to a max of 1024
1514 connections. Now just assume that we can handle as many as 15000
1515 connections. Hopefully this won't cause other problems.
1517 o Backported features:
1518 - When we're a server, a client asks for an old-style directory,
1519 and our write bucket is empty, don't give it to him. This way
1520 small servers can continue to serve the directory *sometimes*,
1521 without getting overloaded.
1522 - Whenever you get a 503 in response to a directory fetch, try
1523 once more. This will become important once servers start sending
1524 503's whenever they feel busy.
1525 - Fetch a new directory every 120 minutes, not every 40 minutes.
1526 Now that we have hundreds of thousands of users running the old
1527 directory algorithm, it's starting to hurt a lot.
1528 - Bump up the period for forcing a hidden service descriptor upload
1529 from 20 minutes to 1 hour.
1532 Changes in version 0.1.0.16 - 2006-01-02
1533 o Crash bugfixes on 0.1.0.x:
1534 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
1535 corrupting the heap, losing FDs, or crashing when we need to resize
1536 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
1537 - It turns out sparc64 platforms crash on unaligned memory access
1538 too -- so detect and avoid this.
1539 - Handle truncated compressed data correctly (by detecting it and
1541 - Fix possible-but-unlikely free(NULL) in control.c.
1542 - When we were closing connections, there was a rare case that
1543 stomped on memory, triggering seg faults and asserts.
1544 - Avoid potential infinite recursion when building a descriptor. (We
1545 don't know that it ever happened, but better to fix it anyway.)
1546 - We were neglecting to unlink marked circuits from soon-to-close OR
1547 connections, which caused some rare scribbling on freed memory.
1548 - Fix a memory stomping race bug when closing the joining point of two
1549 rendezvous circuits.
1550 - Fix an assert in time parsing found by Steven Murdoch.
1552 o Other bugfixes on 0.1.0.x:
1553 - When we're doing reachability testing, provide more useful log
1554 messages so the operator knows what to expect.
1555 - Do not check whether DirPort is reachable when we are suppressing
1556 advertising it because of hibernation.
1557 - When building with -static or on Solaris, we sometimes needed -ldl.
1558 - One of the dirservers (tor26) changed its IP address.
1559 - When we're deciding whether a stream has enough circuits around
1560 that can handle it, count the freshly dirty ones and not the ones
1561 that are so dirty they won't be able to handle it.
1562 - When we're expiring old circuits, we had a logic error that caused
1563 us to close new rendezvous circuits rather than old ones.
1564 - Give a more helpful log message when you try to change ORPort via
1565 the controller: you should upgrade Tor if you want that to work.
1566 - We were failing to parse Tor versions that start with "Tor ".
1567 - Tolerate faulty streams better: when a stream fails for reason
1568 exitpolicy, stop assuming that the router is lying about his exit
1569 policy. When a stream fails for reason misc, allow it to retry just
1570 as if it was resolvefailed. When a stream has failed three times,
1571 reset its failure count so we can try again and get all three tries.
1574 Changes in version 0.1.0.15 - 2005-09-23
1575 o Bugfixes on 0.1.0.x:
1576 - Reject ports 465 and 587 (spam targets) in default exit policy.
1577 - Don't crash when we don't have any spare file descriptors and we
1578 try to spawn a dns or cpu worker.
1579 - Get rid of IgnoreVersion undocumented config option, and make us
1580 only warn, never exit, when we're running an obsolete version.
1581 - Don't try to print a null string when your server finds itself to
1582 be unreachable and the Address config option is empty.
1583 - Make the numbers in read-history and write-history into uint64s,
1584 so they don't overflow and publish negatives in the descriptor.
1585 - Fix a minor memory leak in smartlist_string_remove().
1586 - We were only allowing ourselves to upload a server descriptor at
1587 most every 20 minutes, even if it changed earlier than that.
1588 - Clean up log entries that pointed to old URLs.
1591 Changes in version 0.1.0.14 - 2005-08-08
1592 o Bugfixes on 0.1.0.x:
1593 - Fix the other half of the bug with crypto handshakes
1595 - Fix an assert trigger if you send a 'signal term' via the
1596 controller when it's listening for 'event info' messages.
1599 Changes in version 0.1.0.13 - 2005-08-04
1600 o Bugfixes on 0.1.0.x:
1601 - Fix a critical bug in the security of our crypto handshakes.
1602 - Fix a size_t underflow in smartlist_join_strings2() that made
1603 it do bad things when you hand it an empty smartlist.
1604 - Fix Windows installer to ship Tor license (thanks to Aphex for
1605 pointing out this oversight) and put a link to the doc directory
1607 - Explicitly set no-unaligned-access for sparc: it turns out the
1608 new gcc's let you compile broken code, but that doesn't make it
1612 Changes in version 0.1.0.12 - 2005-07-18
1613 o New directory servers:
1614 - tor26 has changed IP address.
1616 o Bugfixes on 0.1.0.x:
1617 - Fix a possible double-free in tor_gzip_uncompress().
1618 - When --disable-threads is set, do not search for or link against
1620 - Don't trigger an assert if an authoritative directory server
1621 claims its dirport is 0.
1622 - Fix bug with removing Tor as an NT service: some people were
1623 getting "The service did not return an error." Thanks to Matt
1627 Changes in version 0.1.0.11 - 2005-06-30
1628 o Bugfixes on 0.1.0.x:
1629 - Fix major security bug: servers were disregarding their
1630 exit policies if clients behaved unexpectedly.
1631 - Make OS X init script check for missing argument, so we don't
1632 confuse users who invoke it incorrectly.
1633 - Fix a seg fault in "tor --hash-password foo".
1634 - The MAPADDRESS control command was broken.
1637 Changes in version 0.1.0.10 - 2005-06-14
1639 - Make NT services work and start on startup on Win32 (based on
1640 patch by Matt Edman). See the FAQ entry for details.
1641 - Make 'platform' string in descriptor more accurate for Win32
1642 servers, so it's not just "unknown platform".
1643 - REUSEADDR on normal platforms means you can rebind to the port
1644 right after somebody else has let it go. But REUSEADDR on Win32
1645 means you can bind to the port _even when somebody else already
1646 has it bound_! So, don't do that on Win32.
1647 - Clean up the log messages when starting on Win32 with no config
1649 - Allow seeding the RNG on Win32 even when you're not running as
1650 Administrator. If seeding the RNG on Win32 fails, quit.
1652 o Assert / crash bugs:
1653 - Refuse relay cells that claim to have a length larger than the
1654 maximum allowed. This prevents a potential attack that could read
1655 arbitrary memory (e.g. keys) from an exit server's process
1657 - If unofficial Tor clients connect and send weird TLS certs, our
1658 Tor server triggers an assert. Stop asserting, and start handling
1659 TLS errors better in other situations too.
1660 - Fix a race condition that can trigger an assert when we have a
1661 pending create cell and an OR connection attempt fails.
1664 - Use pthreads for worker processes rather than forking. This was
1665 forced because when we forked, we ended up wasting a lot of
1666 duplicate ram over time.
1667 - Also switch to foo_r versions of some library calls to allow
1668 reentry and threadsafeness.
1669 - Implement --disable-threads configure option. Disable threads on
1670 netbsd and openbsd by default, because they have no reentrant
1671 resolver functions (!), and on solaris since it has other
1673 - Fix possible bug on threading platforms (e.g. win32) which was
1674 leaking a file descriptor whenever a cpuworker or dnsworker died.
1675 - Fix a minor memory leak when somebody establishes an introduction
1676 point at your Tor server.
1677 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
1679 - Add ./configure --with-dmalloc option, to track memory leaks.
1680 - And try to free all memory on closing, so we can detect what
1683 o Protocol correctness:
1684 - When we've connected to an OR and handshaked but didn't like
1685 the result, we were closing the conn without sending destroy
1686 cells back for pending circuits. Now send those destroys.
1687 - Start sending 'truncated' cells back rather than destroy cells
1688 if the circuit closes in front of you. This means we won't have
1689 to abandon partially built circuits.
1690 - Handle changed router status correctly when dirserver reloads
1691 fingerprint file. We used to be dropping all unverified descriptors
1692 right then. The bug was hidden because we would immediately
1693 fetch a directory from another dirserver, which would include the
1694 descriptors we just dropped.
1695 - Revise tor-spec to add more/better stream end reasons.
1696 - Revise all calls to connection_edge_end to avoid sending 'misc',
1697 and to take errno into account where possible.
1698 - Client now retries when streams end early for 'hibernating' or
1699 'resource limit' reasons, rather than failing them.
1700 - Try to be more zealous about calling connection_edge_end when
1701 things go bad with edge conns in connection.c.
1703 o Robustness improvements:
1704 - Better handling for heterogeneous / unreliable nodes:
1705 - Annotate circuits with whether they aim to contain high uptime
1706 nodes and/or high capacity nodes. When building circuits, choose
1708 - This means that every single node in an intro rend circuit,
1709 not just the last one, will have a minimum uptime.
1710 - New config option LongLivedPorts to indicate application streams
1711 that will want high uptime circuits.
1712 - Servers reset uptime when a dir fetch entirely fails. This
1713 hopefully reflects stability of the server's network connectivity.
1714 - If somebody starts his tor server in Jan 2004 and then fixes his
1715 clock, don't make his published uptime be a year.
1716 - Reset published uptime when we wake up from hibernation.
1717 - Introduce a notion of 'internal' circs, which are chosen without
1718 regard to the exit policy of the last hop. Intro and rendezvous
1719 circs must be internal circs, to avoid leaking information. Resolve
1720 and connect streams can use internal circs if they want.
1721 - New circuit pooling algorithm: keep track of what destination ports
1722 we've used recently (start out assuming we'll want to use 80), and
1723 make sure to have enough circs around to satisfy these ports. Also
1724 make sure to have 2 internal circs around if we've required internal
1725 circs lately (and with high uptime if we've seen that lately too).
1726 - Turn addr_policy_compare from a tristate to a quadstate; this should
1727 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
1728 for google.com" problem.
1729 - When a client asks us for a dir mirror and we don't have one,
1730 launch an attempt to get a fresh one.
1731 - First cut at support for "create-fast" cells. Clients can use
1732 these when extending to their first hop, since the TLS already
1733 provides forward secrecy and authentication. Not enabled on
1736 o Reachability testing.
1737 - Your Tor server will automatically try to see if its ORPort and
1738 DirPort are reachable from the outside, and it won't upload its
1739 descriptor until it decides at least ORPort is reachable (when
1740 DirPort is not yet found reachable, publish it as zero).
1741 - When building testing circs for ORPort testing, use only
1742 high-bandwidth nodes, so fewer circuits fail.
1743 - Notice when our IP changes, and reset stats/uptime/reachability.
1744 - Authdirservers don't do ORPort reachability detection, since
1745 they're in clique mode, so it will be rare to find a server not
1746 already connected to them.
1747 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
1751 - Now we allow two unverified servers with the same nickname
1752 but different keys. But if a nickname is verified, only that
1753 nickname+key are allowed.
1754 - If you're an authdirserver connecting to an address:port,
1755 and it's not the OR you were expecting, forget about that
1756 descriptor. If he *was* the one you were expecting, then forget
1757 about all other descriptors for that address:port.
1758 - Allow servers to publish descriptors from 12 hours in the future.
1759 Corollary: only whine about clock skew from the dirserver if
1760 he's a trusted dirserver (since now even verified servers could
1761 have quite wrong clocks).
1762 - Require servers that use the default dirservers to have public IP
1763 addresses. We have too many servers that are configured with private
1764 IPs and their admins never notice the log entries complaining that
1765 their descriptors are being rejected.
1767 o Efficiency improvements:
1768 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
1769 and /dev/poll), and hopefully work better on Windows too.
1770 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
1771 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
1772 - Find libevent even if it's hiding in /usr/local/ and your
1773 CFLAGS and LDFLAGS don't tell you to look there.
1774 - Be able to link with libevent as a shared library (the default
1775 after 1.0d), even if it's hiding in /usr/local/lib and even
1776 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
1777 assuming you're running gcc. Otherwise fail and give a useful
1779 - Switch to a new buffer management algorithm, which tries to avoid
1780 reallocing and copying quite as much. In first tests it looks like
1781 it uses *more* memory on average, but less cpu.
1782 - Switch our internal buffers implementation to use a ring buffer,
1783 to hopefully improve performance for fast servers a lot.
1784 - Reenable the part of the code that tries to flush as soon as an
1785 OR outbuf has a full TLS record available. Perhaps this will make
1786 OR outbufs not grow as huge except in rare cases, thus saving lots
1787 of CPU time plus memory.
1788 - Improve performance for dirservers: stop re-parsing the whole
1789 directory every time you regenerate it.
1790 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
1791 it much faster to look up a circuit for each relay cell.
1792 - Remove most calls to assert_all_pending_dns_resolves_ok(),
1793 since they're eating our cpu on exit nodes.
1794 - Stop wasting time doing a case insensitive comparison for every
1795 dns name every time we do any lookup. Canonicalize the names to
1796 lowercase when you first see them.
1799 - Handle unavailable hidden services better. Handle slow or busy
1800 hidden services better.
1801 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
1802 circ as necessary, if there are any completed ones lying around
1803 when we try to launch one.
1804 - Make hidden services try to establish a rendezvous for 30 seconds
1805 after fetching the descriptor, rather than for n (where n=3)
1806 attempts to build a circuit.
1807 - Adjust maximum skew and age for rendezvous descriptors: let skew
1808 be 48 hours rather than 90 minutes.
1809 - Reject malformed .onion addresses rather then passing them on as
1810 normal web requests.
1813 - More Tor controller support. See
1814 http://tor.eff.org/doc/control-spec.txt for all the new features,
1815 including signals to emulate unix signals from any platform;
1816 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
1817 closestream; closecircuit; etc.
1818 - Encode hashed controller passwords in hex instead of base64,
1819 to make it easier to write controllers.
1820 - Revise control spec and implementation to allow all log messages to
1821 be sent to controller with their severities intact (suggested by
1822 Matt Edman). Disable debug-level logs while delivering a debug-level
1823 log to the controller, to prevent loop. Update TorControl to handle
1824 new log event types.
1826 o New config options/defaults:
1827 - Begin scrubbing sensitive strings from logs by default. Turn off
1828 the config option SafeLogging if you need to do debugging.
1829 - New exit policy: accept most low-numbered ports, rather than
1830 rejecting most low-numbered ports.
1831 - Put a note in the torrc about abuse potential with the default
1833 - Add support for CONNECTing through https proxies, with "HttpsProxy"
1835 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
1836 based on patch from Adam Langley (basic auth only).
1837 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
1838 the fast servers that have been joining lately. (Clients are now
1839 willing to load balance over up to 2 MB of advertised bandwidth
1841 - New config option MaxAdvertisedBandwidth which lets you advertise
1842 a low bandwidthrate (to not attract as many circuits) while still
1843 allowing a higher bandwidthrate in reality.
1844 - Require BandwidthRate to be at least 20kB/s for servers.
1845 - Add a NoPublish config option, so you can be a server (e.g. for
1846 testing running Tor servers in other Tor networks) without
1847 publishing your descriptor to the primary dirservers.
1848 - Add a new AddressMap config directive to rewrite incoming socks
1849 addresses. This lets you, for example, declare an implicit
1850 required exit node for certain sites.
1851 - Add a new TrackHostExits config directive to trigger addressmaps
1852 for certain incoming socks addresses -- for sites that break when
1853 your exit keeps changing (based on patch from Mike Perry).
1854 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
1855 which describes how often we retry making new circuits if current
1856 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
1857 how long we're willing to make use of an already-dirty circuit.
1858 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
1859 a config option "ShutdownWaitLength" (when using kill -INT on
1861 - Fix an edge case in parsing config options: if they say "--"
1862 on the commandline, it's not a config option (thanks weasel).
1863 - New config option DirAllowPrivateAddresses for authdirservers.
1864 Now by default they refuse router descriptors that have non-IP or
1865 private-IP addresses.
1866 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
1867 smart" default value: low for servers and high for clients.
1868 - Some people were putting "Address " in their torrc, and they had
1869 a buggy resolver that resolved " " to 0.0.0.0. Oops.
1870 - If DataDir is ~/.tor, and that expands to /.tor, then default to
1871 LOCALSTATEDIR/tor instead.
1872 - Implement --verify-config command-line option to check if your torrc
1873 is valid without actually launching Tor.
1875 o Logging improvements:
1876 - When dirservers refuse a server descriptor, we now log its
1877 contactinfo, platform, and the poster's IP address.
1878 - Only warn once per nickname from add_nickname_list_to_smartlist()
1879 per failure, so an entrynode or exitnode choice that's down won't
1881 - When we're connecting to an OR and he's got a different nickname/key
1882 than we were expecting, only complain loudly if we're an OP or a
1883 dirserver. Complaining loudly to the OR admins just confuses them.
1884 - Whine at you if you're a server and you don't set your contactinfo.
1885 - Warn when exit policy implicitly allows local addresses.
1886 - Give a better warning when some other server advertises an
1887 ORPort that is actually an apache running ssl.
1888 - If we get an incredibly skewed timestamp from a dirserver mirror
1889 that isn't a verified OR, don't warn -- it's probably him that's
1891 - When a dirserver causes you to give a warn, mention which dirserver
1893 - Initialize libevent later in the startup process, so the logs are
1894 already established by the time we start logging libevent warns.
1895 - Use correct errno on win32 if libevent fails.
1896 - Check and warn about known-bad/slow libevent versions.
1897 - Stop warning about sigpipes in the logs. We're going to
1898 pretend that getting these occassionally is normal and fine.
1900 o New contrib scripts:
1901 - New experimental script tor/contrib/exitlist: a simple python
1902 script to parse directories and find Tor nodes that exit to listed
1904 - New experimental script tor/contrib/ExerciseServer.py (needs more
1905 work) that uses the controller interface to build circuits and
1906 fetch pages over them. This will help us bootstrap servers that
1907 have lots of capacity but haven't noticed it yet.
1908 - New experimental script tor/contrib/PathDemo.py (needs more work)
1909 that uses the controller interface to let you choose whole paths
1911 "<hostname>.<path,separated by dots>.<length of path>.path"
1912 - New contributed script "privoxy-tor-toggle" to toggle whether
1913 Privoxy uses Tor. Seems to be configured for Debian by default.
1914 - Have torctl.in/tor.sh.in check for location of su binary (needed
1918 - chdir() to your datadirectory at the *end* of the daemonize process,
1919 not the beginning. This was a problem because the first time you
1920 run tor, if your datadir isn't there, and you have runasdaemon set
1921 to 1, it will try to chdir to it before it tries to create it. Oops.
1922 - Fix several double-mark-for-close bugs, e.g. where we were finding
1923 a conn for a cell even if that conn is already marked for close.
1924 - Stop most cases of hanging up on a socks connection without sending
1926 - Fix a bug in the RPM package: set home directory for _tor to
1927 something more reasonable when first installing.
1928 - Stop putting nodename in the Platform string in server descriptors.
1929 It doesn't actually help, and it is confusing/upsetting some people.
1930 - When using preferred entry or exit nodes, ignore whether the
1931 circuit wants uptime or capacity. They asked for the nodes, they
1933 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
1934 artificially capped at 500kB.
1935 - Cache local dns resolves correctly even when they're .exit
1937 - If we're hibernating and we get a SIGINT, exit immediately.
1938 - tor-resolve requests were ignoring .exit if there was a working circuit
1939 they could use instead.
1940 - Pay more attention to the ClientOnly config option.
1941 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
1942 installer screens; and don't put stuff into StartupItems unless
1943 the user asks you to.
1946 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
1947 rather than just rejecting it.
1948 - If our clock jumps forward by 100 seconds or more, assume something
1949 has gone wrong with our network and abandon all not-yet-used circs.
1950 - When an application is using socks5, give him the whole variety of
1951 potential socks5 responses (connect refused, host unreachable, etc),
1952 rather than just "success" or "failure".
1953 - A more sane version numbering system. See
1954 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
1955 - Change version parsing logic: a version is "obsolete" if it is not
1956 recommended and (1) there is a newer recommended version in the
1957 same series, or (2) there are no recommended versions in the same
1958 series, but there are some recommended versions in a newer series.
1959 A version is "new" if it is newer than any recommended version in
1961 - Report HTTP reasons to client when getting a response from directory
1962 servers -- so you can actually know what went wrong.
1963 - Reject odd-looking addresses at the client (e.g. addresses that
1964 contain a colon), rather than having the server drop them because
1966 - Stop publishing socksport in the directory, since it's not
1967 actually meant to be public. For compatibility, publish a 0 there
1969 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
1970 cookies to disk and doesn't log each web request to disk. (Thanks
1971 to Brett Carrington for pointing this out.)
1972 - Add OSX uninstall instructions. An actual uninstall script will
1974 - Add "opt hibernating 1" to server descriptor to make it clearer
1975 whether the server is hibernating.
1978 Changes in version 0.0.9.10 - 2005-06-16
1979 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
1980 - Refuse relay cells that claim to have a length larger than the
1981 maximum allowed. This prevents a potential attack that could read
1982 arbitrary memory (e.g. keys) from an exit server's process
1986 Changes in version 0.0.9.9 - 2005-04-23
1987 o Bugfixes on 0.0.9.x:
1988 - If unofficial Tor clients connect and send weird TLS certs, our
1989 Tor server triggers an assert. This release contains a minimal
1990 backport from the broader fix that we put into 0.1.0.4-rc.
1993 Changes in version 0.0.9.8 - 2005-04-07
1994 o Bugfixes on 0.0.9.x:
1995 - We have a bug that I haven't found yet. Sometimes, very rarely,
1996 cpuworkers get stuck in the 'busy' state, even though the cpuworker
1997 thinks of itself as idle. This meant that no new circuits ever got
1998 established. Here's a workaround to kill any cpuworker that's been
1999 busy for more than 100 seconds.
2002 Changes in version 0.0.9.7 - 2005-04-01
2003 o Bugfixes on 0.0.9.x:
2004 - Fix another race crash bug (thanks to Glenn Fink for reporting).
2005 - Compare identity to identity, not to nickname, when extending to
2006 a router not already in the directory. This was preventing us from
2007 extending to unknown routers. Oops.
2008 - Make sure to create OS X Tor user in <500 range, so we aren't
2009 creating actual system users.
2010 - Note where connection-that-hasn't-sent-end was marked, and fix
2011 a few really loud instances of this harmless bug (it's fixed more
2015 Changes in version 0.0.9.6 - 2005-03-24
2016 o Bugfixes on 0.0.9.x (crashes and asserts):
2017 - Add new end stream reasons to maintainance branch. Fix bug where
2018 reason (8) could trigger an assert. Prevent bug from recurring.
2019 - Apparently win32 stat wants paths to not end with a slash.
2020 - Fix assert triggers in assert_cpath_layer_ok(), where we were
2021 blowing away the circuit that conn->cpath_layer points to, then
2022 checking to see if the circ is well-formed. Backport check to make
2023 sure we dont use the cpath on a closed connection.
2024 - Prevent circuit_resume_edge_reading_helper() from trying to package
2025 inbufs for marked-for-close streams.
2026 - Don't crash on hup if your options->address has become unresolvable.
2027 - Some systems (like OS X) sometimes accept() a connection and tell
2028 you the remote host is 0.0.0.0:0. If this happens, due to some
2029 other mis-features, we get confused; so refuse the conn for now.
2031 o Bugfixes on 0.0.9.x (other):
2032 - Fix harmless but scary "Unrecognized content encoding" warn message.
2033 - Add new stream error reason: TORPROTOCOL reason means "you are not
2034 speaking a version of Tor I understand; say bye-bye to your stream."
2035 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
2036 into the future, now that we are more tolerant of skew. This
2037 resolves a bug where a Tor server would refuse to cache a directory
2038 because all the directories it gets are too far in the future;
2039 yet the Tor server never logs any complaints about clock skew.
2040 - Mac packaging magic: make man pages useable, and do not overwrite
2041 existing torrc files.
2042 - Make OS X log happily to /var/log/tor/tor.log
2045 Changes in version 0.0.9.5 - 2005-02-22
2046 o Bugfixes on 0.0.9.x:
2047 - Fix an assert race at exit nodes when resolve requests fail.
2048 - Stop picking unverified dir mirrors--it only leads to misery.
2049 - Patch from Matt Edman to make NT services work better. Service
2050 support is still not compiled into the executable by default.
2051 - Patch from Dmitri Bely so the Tor service runs better under
2052 the win32 SYSTEM account.
2053 - Make tor-resolve actually work (?) on Win32.
2054 - Fix a sign bug when getrlimit claims to have 4+ billion
2055 file descriptors available.
2056 - Stop refusing to start when bandwidthburst == bandwidthrate.
2057 - When create cells have been on the onion queue more than five
2058 seconds, just send back a destroy and take them off the list.
2061 Changes in version 0.0.9.4 - 2005-02-03
2062 o Bugfixes on 0.0.9:
2063 - Fix an assert bug that took down most of our servers: when
2064 a server claims to have 1 GB of bandwidthburst, don't
2066 - Don't crash as badly if we have spawned the max allowed number
2067 of dnsworkers, or we're out of file descriptors.
2068 - Block more file-sharing ports in the default exit policy.
2069 - MaxConn is now automatically set to the hard limit of max
2070 file descriptors we're allowed (ulimit -n), minus a few for
2072 - Give a clearer message when servers need to raise their
2073 ulimit -n when they start running out of file descriptors.
2074 - SGI Compatibility patches from Jan Schaumann.
2075 - Tolerate a corrupt cached directory better.
2076 - When a dirserver hasn't approved your server, list which one.
2077 - Go into soft hibernation after 95% of the bandwidth is used,
2078 not 99%. This is especially important for daily hibernators who
2079 have a small accounting max. Hopefully it will result in fewer
2080 cut connections when the hard hibernation starts.
2081 - Load-balance better when using servers that claim more than
2082 800kB/s of capacity.
2083 - Make NT services work (experimental, only used if compiled in).
2086 Changes in version 0.0.9.3 - 2005-01-21
2087 o Bugfixes on 0.0.9:
2088 - Backport the cpu use fixes from main branch, so busy servers won't
2089 need as much processor time.
2090 - Work better when we go offline and then come back, or when we
2091 run Tor at boot before the network is up. We do this by
2092 optimistically trying to fetch a new directory whenever an
2093 application request comes in and we think we're offline -- the
2094 human is hopefully a good measure of when the network is back.
2095 - Backport some minimal hidserv bugfixes: keep rend circuits open as
2096 long as you keep using them; actually publish hidserv descriptors
2097 shortly after they change, rather than waiting 20-40 minutes.
2098 - Enable Mac startup script by default.
2099 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
2100 - When you update AllowUnverifiedNodes or FirewallPorts via the
2101 controller's setconf feature, we were always appending, never
2103 - When you update HiddenServiceDir via setconf, it was screwing up
2104 the order of reading the lines, making it fail.
2105 - Do not rewrite a cached directory back to the cache; otherwise we
2106 will think it is recent and not fetch a newer one on startup.
2107 - Workaround for webservers that lie about Content-Encoding: Tor
2108 now tries to autodetect compressed directories and compression
2109 itself. This lets us Proxypass dir fetches through apache.
2112 Changes in version 0.0.9.2 - 2005-01-04
2113 o Bugfixes on 0.0.9 (crashes and asserts):
2114 - Fix an assert on startup when the disk is full and you're logging
2116 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
2117 style address, then we'd crash.
2118 - Fix an assert trigger when the running-routers string we get from
2119 a dirserver is broken.
2120 - Make worker threads start and run on win32. Now win32 servers
2122 - Bandaid (not actually fix, but now it doesn't crash) an assert
2123 where the dns worker dies mysteriously and the main Tor process
2124 doesn't remember anything about the address it was resolving.
2126 o Bugfixes on 0.0.9 (Win32):
2127 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
2128 name out of the warning/assert messages.
2129 - Fix a superficial "unhandled error on read" bug on win32.
2130 - The win32 installer no longer requires a click-through for our
2131 license, since our Free Software license grants rights but does not
2133 - Win32: When connecting to a dirserver fails, try another one
2134 immediately. (This was already working for non-win32 Tors.)
2135 - Stop trying to parse $HOME on win32 when hunting for default
2137 - Make tor-resolve.c work on win32 by calling network_init().
2139 o Bugfixes on 0.0.9 (other):
2140 - Make 0.0.9.x build on Solaris again.
2141 - Due to a fencepost error, we were blowing away the \n when reporting
2142 confvalue items in the controller. So asking for multiple config
2143 values at once couldn't work.
2144 - When listing circuits that are pending on an opening OR connection,
2145 if we're an OR we were listing circuits that *end* at us as
2146 being pending on every listener, dns/cpu worker, etc. Stop that.
2147 - Dirservers were failing to create 'running-routers' or 'directory'
2148 strings if we had more than some threshold of routers. Fix them so
2149 they can handle any number of routers.
2150 - Fix a superficial "Duplicate mark for close" bug.
2151 - Stop checking for clock skew for OR connections, even for servers.
2152 - Fix a fencepost error that was chopping off the last letter of any
2153 nickname that is the maximum allowed nickname length.
2154 - Update URLs in log messages so they point to the new website.
2155 - Fix a potential problem in mangling server private keys while
2156 writing to disk (not triggered yet, as far as we know).
2157 - Include the licenses for other free software we include in Tor,
2158 now that we're shipping binary distributions more regularly.
2161 Changes in version 0.0.9.1 - 2004-12-15
2162 o Bugfixes on 0.0.9:
2163 - Make hibernation actually work.
2164 - Make HashedControlPassword config option work.
2165 - When we're reporting event circuit status to a controller,
2166 don't use the stream status code.
2169 Changes in version 0.0.9 - 2004-12-12
2170 o Bugfixes on 0.0.8.1 (Crashes and asserts):
2171 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
2172 write() call will fail and we handle it there.
2173 - When we run out of disk space, or other log writing error, don't
2174 crash. Just stop logging to that log and continue.
2175 - Fix isspace() and friends so they still make Solaris happy
2176 but also so they don't trigger asserts on win32.
2177 - Fix assert failure on malformed socks4a requests.
2178 - Fix an assert bug where a hidden service provider would fail if
2179 the first hop of his rendezvous circuit was down.
2180 - Better handling of size_t vs int, so we're more robust on 64
2183 o Bugfixes on 0.0.8.1 (Win32):
2184 - Make windows sockets actually non-blocking (oops), and handle
2185 win32 socket errors better.
2186 - Fix parse_iso_time on platforms without strptime (eg win32).
2187 - win32: when being multithreaded, leave parent fdarray open.
2188 - Better handling of winsock includes on non-MSV win32 compilers.
2189 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
2191 - Make unit tests work on win32.
2193 o Bugfixes on 0.0.8.1 (Path selection and streams):
2194 - Calculate timeout for waiting for a connected cell from the time
2195 we sent the begin cell, not from the time the stream started. If
2196 it took a long time to establish the circuit, we would time out
2197 right after sending the begin cell.
2198 - Fix router_compare_addr_to_addr_policy: it was not treating a port
2199 of * as always matching, so we were picking reject *:* nodes as
2200 exit nodes too. Oops.
2201 - When read() failed on a stream, we would close it without sending
2202 back an end. So 'connection refused' would simply be ignored and
2203 the user would get no response.
2204 - Stop a sigpipe: when an 'end' cell races with eof from the app,
2205 we shouldn't hold-open-until-flush if the eof arrived first.
2206 - Let resolve conns retry/expire also, rather than sticking around
2208 - Fix more dns related bugs: send back resolve_failed and end cells
2209 more reliably when the resolve fails, rather than closing the
2210 circuit and then trying to send the cell. Also attach dummy resolve
2211 connections to a circuit *before* calling dns_resolve(), to fix
2212 a bug where cached answers would never be sent in RESOLVED cells.
2214 o Bugfixes on 0.0.8.1 (Circuits):
2215 - Finally fix a bug that's been plaguing us for a year:
2216 With high load, circuit package window was reaching 0. Whenever
2217 we got a circuit-level sendme, we were reading a lot on each
2218 socket, but only writing out a bit. So we would eventually reach
2219 eof. This would be noticed and acted on even when there were still
2220 bytes sitting in the inbuf.
2221 - Use identity comparison, not nickname comparison, to choose which
2222 half of circuit-ID-space each side gets to use. This is needed
2223 because sometimes we think of a router as a nickname, and sometimes
2224 as a hex ID, and we can't predict what the other side will do.
2226 o Bugfixes on 0.0.8.1 (Other):
2227 - Fix a whole slew of memory leaks.
2228 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
2229 - If we are using select, make sure we stay within FD_SETSIZE.
2230 - When poll() is interrupted, we shouldn't believe the revents values.
2231 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
2232 and smartlist_len, which are two major profiling offenders.
2233 - If do_hup fails, actually notice.
2234 - Flush the log file descriptor after we print "Tor opening log file",
2235 so we don't see those messages days later.
2236 - Hidden service operators now correctly handle version 1 style
2237 INTRODUCE1 cells (nobody generates them still, so not a critical
2239 - Handle more errnos from accept() without closing the listener.
2240 Some OpenBSD machines were closing their listeners because
2241 they ran out of file descriptors.
2242 - Some people had wrapped their tor client/server in a script
2243 that would restart it whenever it died. This did not play well
2244 with our "shut down if your version is obsolete" code. Now people
2245 don't fetch a new directory if their local cached version is
2247 - Make our autogen.sh work on ksh as well as bash.
2248 - Better torrc example lines for dirbindaddress and orbindaddress.
2249 - Improved bounds checking on parsed ints (e.g. config options and
2250 the ones we find in directories.)
2251 - Stop using separate defaults for no-config-file and
2252 empty-config-file. Now you have to explicitly turn off SocksPort,
2253 if you don't want it open.
2254 - We were starting to daemonize before we opened our logs, so if
2255 there were any problems opening logs, we would complain to stderr,
2256 which wouldn't work, and then mysteriously exit.
2257 - If a verified OR connects to us before he's uploaded his descriptor,
2258 or we verify him and hup but he still has the original TLS
2259 connection, then conn->nickname is still set like he's unverified.
2261 o Code security improvements, inspired by Ilja:
2262 - tor_snprintf wrapper over snprintf with consistent (though not C99)
2264 - Replace sprintf with tor_snprintf. (I think they were all safe, but
2266 - Replace strcpy/strncpy with strlcpy in more places.
2267 - Avoid strcat; use tor_snprintf or strlcat instead.
2269 o Features (circuits and streams):
2270 - New circuit building strategy: keep a list of ports that we've
2271 used in the past 6 hours, and always try to have 2 circuits open
2272 or on the way that will handle each such port. Seed us with port
2273 80 so web users won't complain that Tor is "slow to start up".
2274 - Make kill -USR1 dump more useful stats about circuits.
2275 - When warning about retrying or giving up, print the address, so
2276 the user knows which one it's talking about.
2277 - If you haven't used a clean circuit in an hour, throw it away,
2278 just to be on the safe side. (This means after 6 hours a totally
2279 unused Tor client will have no circuits open.)
2280 - Support "foo.nickname.exit" addresses, to let Alice request the
2281 address "foo" as viewed by exit node "nickname". Based on a patch
2283 - If your requested entry or exit node has advertised bandwidth 0,
2285 - Be more greedy about filling up relay cells -- we try reading again
2286 once we've processed the stuff we read, in case enough has arrived
2287 to fill the last cell completely.
2288 - Refuse application socks connections to port 0.
2289 - Use only 0.0.9pre1 and later servers for resolve cells.
2291 o Features (bandwidth):
2292 - Hibernation: New config option "AccountingMax" lets you
2293 set how many bytes per month (in each direction) you want to
2294 allow your server to consume. Rather than spreading those
2295 bytes out evenly over the month, we instead hibernate for some
2296 of the month and pop up at a deterministic time, work until
2297 the bytes are consumed, then hibernate again. Config option
2298 "MonthlyAccountingStart" lets you specify which day of the month
2299 your billing cycle starts on.
2300 - Implement weekly/monthly/daily accounting: now you specify your
2301 hibernation properties by
2302 AccountingMax N bytes|KB|MB|GB|TB
2303 AccountingStart day|week|month [day] HH:MM
2304 Defaults to "month 1 0:00".
2305 - Let bandwidth and interval config options be specified as 5 bytes,
2306 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
2308 o Features (directories):
2309 - New "router-status" line in directory, to better bind each verified
2310 nickname to its identity key.
2311 - Clients can ask dirservers for /dir.z to get a compressed version
2312 of the directory. Only works for servers running 0.0.9, of course.
2313 - Make clients cache directories and use them to seed their router
2314 lists at startup. This means clients have a datadir again.
2315 - Respond to content-encoding headers by trying to uncompress as
2317 - Clients and servers now fetch running-routers; cache
2318 running-routers; compress running-routers; serve compressed
2320 - Make moria2 advertise a dirport of 80, so people behind firewalls
2321 will be able to get a directory.
2322 - Http proxy support
2323 - Dirservers translate requests for http://%s:%d/x to /x
2324 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
2325 be routed through this host.
2326 - Clients ask for /tor/x rather than /x for new enough dirservers.
2327 This way we can one day coexist peacefully with apache.
2328 - Clients specify a "Host: %s%d" http header, to be compatible
2329 with more proxies, and so running squid on an exit node can work.
2330 - Protect dirservers from overzealous descriptor uploading -- wait
2331 10 seconds after directory gets dirty, before regenerating.
2333 o Features (packages and install):
2334 - Add NSI installer contributed by J Doe.
2335 - Apply NT service patch from Osamu Fujino. Still needs more work.
2336 - Commit VC6 and VC7 workspace/project files.
2337 - Commit a tor.spec for making RPM files, with help from jbash.
2338 - Add contrib/torctl.in contributed by Glenn Fink.
2339 - Make expand_filename handle ~ and ~username.
2340 - Use autoconf to enable largefile support where necessary. Use
2341 ftello where available, since ftell can fail at 2GB.
2342 - Ship src/win32/ in the tarball, so people can use it to build.
2343 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
2346 o Features (ui controller):
2347 - Control interface: a separate program can now talk to your
2348 client/server over a socket, and get/set config options, receive
2349 notifications of circuits and streams starting/finishing/dying,
2350 bandwidth used, etc. The next step is to get some GUIs working.
2351 Let us know if you want to help out. See doc/control-spec.txt .
2352 - Ship a contrib/tor-control.py as an example script to interact
2353 with the control port.
2354 - "tor --hash-password zzyxz" will output a salted password for
2355 use in authenticating to the control interface.
2356 - Implement the control-spec's SAVECONF command, to write your
2357 configuration to torrc.
2358 - Get cookie authentication for the controller closer to working.
2359 - When set_conf changes our server descriptor, upload a new copy.
2360 But don't upload it too often if there are frequent changes.
2362 o Features (config and command-line):
2363 - Deprecate unofficial config option abbreviations, and abbreviations
2364 not on the command line.
2365 - Configuration infrastructure support for warning on obsolete
2367 - Give a slightly more useful output for "tor -h".
2368 - Break DirFetchPostPeriod into:
2369 - DirFetchPeriod for fetching full directory,
2370 - StatusFetchPeriod for fetching running-routers,
2371 - DirPostPeriod for posting server descriptor,
2372 - RendPostPeriod for posting hidden service descriptors.
2373 - New log format in config:
2374 "Log minsev[-maxsev] stdout|stderr|syslog" or
2375 "Log minsev[-maxsev] file /var/foo"
2376 - DirPolicy config option, to let people reject incoming addresses
2377 from their dirserver.
2378 - "tor --list-fingerprint" will list your identity key fingerprint
2380 - Make tor --version --version dump the cvs Id of every file.
2381 - New 'MyFamily nick1,...' config option for a server to
2382 specify other servers that shouldn't be used in the same circuit
2383 with it. Only believed if nick1 also specifies us.
2384 - New 'NodeFamily nick1,nick2,...' config option for a client to
2385 specify nodes that it doesn't want to use in the same circuit.
2386 - New 'Redirectexit pattern address:port' config option for a
2387 server to redirect exit connections, e.g. to a local squid.
2388 - Add "pass" target for RedirectExit, to make it easier to break
2389 out of a sequence of RedirectExit rules.
2390 - Make the dirservers file obsolete.
2391 - Include a dir-signing-key token in directories to tell the
2392 parsing entity which key is being used to sign.
2393 - Remove the built-in bulky default dirservers string.
2394 - New config option "Dirserver %s:%d [fingerprint]", which can be
2395 repeated as many times as needed. If no dirservers specified,
2396 default to moria1,moria2,tor26.
2397 - Make 'Routerfile' config option obsolete.
2398 - Discourage people from setting their dirfetchpostperiod more often
2399 than once per minute.
2402 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
2403 get back to normal.)
2404 - Accept *:706 (silc) in default exit policy.
2405 - Implement new versioning format for post 0.1.
2406 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
2407 log more informatively.
2408 - Check clock skew for verified servers, but allow unverified
2409 servers and clients to have any clock skew.
2410 - Make sure the hidden service descriptors are at a random offset
2411 from each other, to hinder linkability.
2412 - Clients now generate a TLS cert too, in preparation for having
2413 them act more like real nodes.
2414 - Add a pure-C tor-resolve implementation.
2415 - Use getrlimit and friends to ensure we can reach MaxConn (currently
2416 1024) file descriptors.
2417 - Raise the max dns workers from 50 to 100.
2420 Changes in version 0.0.8.1 - 2004-10-13
2422 - Fix a seg fault that can be triggered remotely for Tor
2423 clients/servers with an open dirport.
2424 - Fix a rare assert trigger, where routerinfos for entries in
2425 our cpath would expire while we're building the path.
2426 - Fix a bug in OutboundBindAddress so it (hopefully) works.
2427 - Fix a rare seg fault for people running hidden services on
2428 intermittent connections.
2429 - Fix a bug in parsing opt keywords with objects.
2430 - Fix a stale pointer assert bug when a stream detaches and
2432 - Fix a string format vulnerability (probably not exploitable)
2433 in reporting stats locally.
2434 - Fix an assert trigger: sometimes launching circuits can fail
2435 immediately, e.g. because too many circuits have failed recently.
2436 - Fix a compile warning on 64 bit platforms.
2439 Changes in version 0.0.8 - 2004-08-25
2441 - Made our unit tests compile again on OpenBSD 3.5, and tor
2442 itself compile again on OpenBSD on a sparc64.
2443 - We were neglecting milliseconds when logging on win32, so
2444 everything appeared to happen at the beginning of each second.
2445 - Check directory signature _before_ you decide whether you're
2446 you're running an obsolete version and should exit.
2447 - Check directory signature _before_ you parse the running-routers
2448 list to decide who's running.
2449 - Check return value of fclose while writing to disk, so we don't
2450 end up with broken files when servers run out of disk space.
2451 - Port it to SunOS 5.9 / Athena
2452 - Fix two bugs in saving onion keys to disk when rotating, so
2453 hopefully we'll get fewer people using old onion keys.
2454 - Remove our mostly unused -- and broken -- hex_encode()
2455 function. Use base16_encode() instead. (Thanks to Timo Lindfors
2456 for pointing out this bug.)
2457 - Only pick and establish intro points after we've gotten a
2459 - Fix assert triggers: if the other side returns an address 0.0.0.0,
2460 don't put it into the client dns cache.
2461 - If a begin failed due to exit policy, but we believe the IP
2462 address should have been allowed, switch that router to exitpolicy
2463 reject *:* until we get our next directory.
2466 - 'Extend' relay cell payloads now include the digest of the
2467 intended next hop's identity key. Now we can verify that we're
2468 extending to the right router, and also extend to routers we
2469 hadn't heard of before.
2472 - Tor nodes can now act as relays (with an advertised ORPort)
2473 without being manually verified by the dirserver operators.
2474 - Uploaded descriptors of unverified routers are now accepted
2475 by the dirservers, and included in the directory.
2476 - Verified routers are listed by nickname in the running-routers
2477 list; unverified routers are listed as "$<fingerprint>".
2478 - We now use hash-of-identity-key in most places rather than
2479 nickname or addr:port, for improved security/flexibility.
2480 - AllowUnverifiedNodes config option to let circuits choose no-name
2481 routers in entry,middle,exit,introduction,rendezvous positions.
2482 Allow middle and rendezvous positions by default.
2483 - When picking unverified routers, skip those with low uptime and/or
2484 low bandwidth, depending on what properties you care about.
2485 - ClientOnly option for nodes that never want to become servers.
2486 - Directory caching.
2487 - "AuthoritativeDir 1" option for the official dirservers.
2488 - Now other nodes (clients and servers) will cache the latest
2489 directory they've pulled down.
2490 - They can enable their DirPort to serve it to others.
2491 - Clients will pull down a directory from any node with an open
2492 DirPort, and check the signature/timestamp correctly.
2493 - Authoritative dirservers now fetch directories from other
2494 authdirservers, to stay better synced.
2495 - Running-routers list tells who's down also, along with noting
2496 if they're verified (listed by nickname) or unverified (listed
2498 - Allow dirservers to serve running-router list separately.
2499 This isn't used yet.
2500 - You can now fetch $DIRURL/running-routers to get just the
2501 running-routers line, not the whole descriptor list. (But
2502 clients don't use this yet.)
2503 - Clients choose nodes proportional to advertised bandwidth.
2504 - Clients avoid using nodes with low uptime as introduction points.
2505 - Handle servers with dynamic IP addresses: don't just replace
2506 options->Address with the resolved one at startup, and
2507 detect our address right before we make a routerinfo each time.
2508 - 'FascistFirewall' option to pick dirservers and ORs on specific
2509 ports; plus 'FirewallPorts' config option to tell FascistFirewall
2510 which ports are open. (Defaults to 80,443)
2511 - Try other dirservers immediately if the one you try is down. This
2512 should tolerate down dirservers better now.
2513 - ORs connect-on-demand to other ORs
2514 - If you get an extend cell to an OR you're not connected to,
2515 connect, handshake, and forward the create cell.
2516 - The authoritative dirservers stay connected to everybody,
2517 and everybody stays connected to 0.0.7 servers, but otherwise
2518 clients/servers expire unused connections after 5 minutes.
2519 - When servers get a sigint, they delay 30 seconds (refusing new
2520 connections) then exit. A second sigint causes immediate exit.
2521 - File and name management:
2522 - Look for .torrc if no CONFDIR "torrc" is found.
2523 - If no datadir is defined, then choose, make, and secure ~/.tor
2525 - If torrc not found, exitpolicy reject *:*.
2526 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
2527 - If no nickname is defined, derive default from hostname.
2528 - Rename secret key files, e.g. identity.key -> secret_id_key,
2529 to discourage people from mailing their identity key to tor-ops.
2530 - Refuse to build a circuit before the directory has arrived --
2531 it won't work anyway, since you won't know the right onion keys
2533 - Parse tor version numbers so we can do an is-newer-than check
2534 rather than an is-in-the-list check.
2535 - New socks command 'resolve', to let us shim gethostbyname()
2537 - A 'tor_resolve' script to access the socks resolve functionality.
2538 - A new socks-extensions.txt doc file to describe our
2539 interpretation and extensions to the socks protocols.
2540 - Add a ContactInfo option, which gets published in descriptor.
2541 - Write tor version at the top of each log file
2542 - New docs in the tarball:
2544 - Document that you should proxy your SSL traffic too.
2545 - Log a warning if the user uses an unsafe socks variant, so people
2546 are more likely to learn about privoxy or socat.
2547 - Log a warning if you're running an unverified server, to let you
2548 know you might want to get it verified.
2549 - Change the default exit policy to reject the default edonkey,
2550 kazaa, gnutella ports.
2551 - Add replace_file() to util.[ch] to handle win32's rename().
2552 - Publish OR uptime in descriptor (and thus in directory) too.
2553 - Remember used bandwidth (both in and out), and publish 15-minute
2554 snapshots for the past day into our descriptor.
2555 - Be more aggressive about trying to make circuits when the network
2556 has changed (e.g. when you unsuspend your laptop).
2557 - Check for time skew on http headers; report date in response to
2559 - If the entrynode config line has only one node, don't pick it as
2561 - Add strict{entry|exit}nodes config options. If set to 1, then
2562 we refuse to build circuits that don't include the specified entry
2564 - OutboundBindAddress config option, to bind to a specific
2565 IP address for outgoing connect()s.
2566 - End truncated log entries (e.g. directories) with "[truncated]".
2569 Changes in version 0.0.7.3 - 2004-08-12
2570 o Stop dnsworkers from triggering an assert failure when you
2571 ask them to resolve the host "".
2574 Changes in version 0.0.7.2 - 2004-07-07
2575 o A better fix for the 0.0.0.0 problem, that will hopefully
2576 eliminate the remaining related assertion failures.
2579 Changes in version 0.0.7.1 - 2004-07-04
2580 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
2581 since internally we use 0.0.0.0 to signify "not yet resolved".
2584 Changes in version 0.0.7 - 2004-06-07
2585 o Fixes for crashes and other obnoxious bugs:
2586 - Fix an epipe bug: sometimes when directory connections failed
2587 to connect, we would give them a chance to flush before closing
2589 - When we detached from a circuit because of resolvefailed, we
2590 would immediately try the same circuit twice more, and then
2591 give up on the resolve thinking we'd tried three different
2593 - Limit the number of intro circuits we'll attempt to build for a
2594 hidden service per 15-minute period.
2595 - Check recommended-software string *early*, before actually parsing
2596 the directory. Thus we can detect an obsolete version and exit,
2597 even if the new directory format doesn't parse.
2598 o Fixes for security bugs:
2599 - Remember which nodes are dirservers when you startup, and if a
2600 random OR enables his dirport, don't automatically assume he's
2601 a trusted dirserver.
2603 - Directory connections were asking the wrong poll socket to
2604 start writing, and not asking themselves to start writing.
2605 - When we detached from a circuit because we sent a begin but
2606 didn't get a connected, we would use it again the first time;
2607 but after that we would correctly switch to a different one.
2608 - Stop warning when the first onion decrypt attempt fails; they
2609 will sometimes legitimately fail now that we rotate keys.
2610 - Override unaligned-access-ok check when $host_cpu is ia64 or
2611 arm. Apparently they allow it but the kernel whines.
2612 - Dirservers try to reconnect periodically too, in case connections
2614 - Fix some memory leaks in directory servers.
2615 - Allow backslash in Win32 filenames.
2616 - Made Tor build complain-free on FreeBSD, hopefully without
2617 breaking other BSD builds. We'll see.
2618 - Check directory signatures based on name of signer, not on whom
2619 we got the directory from. This will let us cache directories more
2621 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
2624 - Doxygen markup on all functions and global variables.
2625 - Make directory functions update routerlist, not replace it. So
2626 now directory disagreements are not so critical a problem.
2627 - Remove the upper limit on number of descriptors in a dirserver's
2628 directory (not that we were anywhere close).
2629 - Allow multiple logfiles at different severity ranges.
2630 - Allow *BindAddress to specify ":port" rather than setting *Port
2631 separately. Allow multiple instances of each BindAddress config
2632 option, so you can bind to multiple interfaces if you want.
2633 - Allow multiple exit policy lines, which are processed in order.
2634 Now we don't need that huge line with all the commas in it.
2635 - Enable accept/reject policies on SOCKS connections, so you can bind
2636 to 0.0.0.0 but still control who can use your OP.
2637 - Updated the man page to reflect these features.
2640 Changes in version 0.0.6.2 - 2004-05-16
2641 o Our integrity-checking digest was checking only the most recent cell,
2642 not the previous cells like we'd thought.
2643 Thanks to Stefan Mark for finding the flaw!
2646 Changes in version 0.0.6.1 - 2004-05-06
2647 o Fix two bugs in our AES counter-mode implementation (this affected
2648 onion-level stream encryption, but not TLS-level). It turns
2649 out we were doing something much more akin to a 16-character
2650 polyalphabetic cipher. Oops.
2651 Thanks to Stefan Mark for finding the flaw!
2652 o Retire moria3 as a directory server, and add tor26 as a directory
2656 Changes in version 0.0.6 - 2004-05-02
2658 - Hidden services and rendezvous points are implemented. Go to
2659 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
2660 hidden services. (This only works via a socks4a proxy such as
2661 Privoxy, and currently it's quite slow.)
2662 - We now rotate link (tls context) keys and onion keys.
2663 - CREATE cells now include oaep padding, so you can tell
2664 if you decrypted them correctly.
2665 - Retry stream correctly when we fail to connect because of
2666 exit-policy-reject (should try another) or can't-resolve-address.
2667 - When we hup a dirserver and we've *removed* a server from the
2668 approved-routers list, now we remove that server from the
2669 in-memory directories too.
2670 - Add bandwidthburst to server descriptor.
2671 - Directories now say which dirserver signed them.
2672 - Use a tor_assert macro that logs failed assertions too.
2673 - Since we don't support truncateds much, don't bother sending them;
2674 just close the circ.
2675 - Fetch randomness from /dev/urandom better (not via fopen/fread)
2676 - Better debugging for tls errors
2677 - Set Content-Type on the directory and hidserv descriptor.
2678 - Remove IVs from cipher code, since AES-ctr has none.
2680 - Fix an assert trigger for exit nodes that's been plaguing us since
2681 the days of 0.0.2prexx (thanks weasel!)
2682 - Fix a bug where we were closing tls connections intermittently.
2683 It turns out openssl keeps its errors around -- so if an error
2684 happens, and you don't ask about it, and then another openssl
2685 operation happens and succeeds, and you ask if there was an error,
2686 it tells you about the first error.
2687 - Fix a bug that's been lurking since 27 may 03 (!)
2688 When passing back a destroy cell, we would use the wrong circ id.
2689 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
2690 - Some versions of openssl have an SSL_pending function that erroneously
2691 returns bytes when there is a non-application record pending.
2692 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
2693 o We were using an array of length zero in a few places.
2694 o Win32's gethostbyname can't resolve an IP to an IP.
2695 o Win32's close can't close a socket.
2696 o Handle windows socket errors correctly.
2698 - check for <sys/limits.h> so we build on FreeBSD again, and
2699 <machine/limits.h> for NetBSD.
2702 Changes in version 0.0.5 - 2004-03-30
2703 o Install torrc as torrc.sample -- we no longer clobber your
2705 o Fix mangled-state bug in directory fetching (was causing sigpipes).
2706 o Only build circuits after we've fetched the directory: clients were
2707 using only the directory servers before they'd fetched a directory.
2708 This also means longer startup time; so it goes.
2709 o Fix an assert trigger where an OP would fail to handshake, and we'd
2710 expect it to have a nickname.
2711 o Work around a tsocks bug: do a socks reject when AP connection dies
2712 early, else tsocks goes into an infinite loop.
2713 o Hold socks connection open until reply is flushed (if possible)
2714 o Make exit nodes resolve IPs to IPs immediately, rather than asking
2715 the dns farm to do it.
2716 o Fix c99 aliasing warnings in rephist.c
2717 o Don't include server descriptors that are older than 24 hours in the
2719 o Give socks 'reject' replies their whole 15s to attempt to flush,
2720 rather than seeing the 60s timeout and assuming the flush had failed.
2721 o Clean automake droppings from the cvs repository
2722 o Add in a 'notice' log level for things the operator should hear
2723 but that aren't warnings
2726 Changes in version 0.0.4 - 2004-03-26
2727 o When connecting to a dirserver or OR and the network is down,
2731 Changes in version 0.0.3 - 2004-03-26
2732 o Warn and fail if server chose a nickname with illegal characters
2733 o Port to Solaris and Sparc:
2734 - include missing header fcntl.h
2735 - have autoconf find -lsocket -lnsl automatically
2736 - deal with hardware word alignment
2737 - make uname() work (solaris has a different return convention)
2738 - switch from using signal() to sigaction()
2739 o Preliminary work on reputation system:
2740 - Keep statistics on success/fail of connect attempts; they're published
2741 by kill -USR1 currently.
2742 - Add a RunTesting option to try to learn link state by creating test
2743 circuits, even when SocksPort is off.
2744 - Remove unused open circuits when there are too many.
2747 Changes in version 0.0.2 - 2004-03-19
2748 - Include strlcpy and strlcat for safer string ops
2749 - define INADDR_NONE so we compile (but still not run) on solaris
2752 Changes in version 0.0.2pre27 - 2004-03-14
2754 - Allow internal tor networks (we were rejecting internal IPs,
2755 now we allow them if they're set explicitly).
2756 - And fix a few endian issues.
2759 Changes in version 0.0.2pre26 - 2004-03-14
2761 - If a stream times out after 15s without a connected cell, don't
2762 try that circuit again: try a new one.
2763 - Retry streams at most 4 times. Then give up.
2764 - When a dirserver gets a descriptor from an unknown router, it
2765 logs its fingerprint (so the dirserver operator can choose to
2766 accept it even without mail from the server operator).
2767 - Inform unapproved servers when we reject their descriptors.
2768 - Make tor build on Windows again. It works as a client, who knows
2770 - Clearer instructions in the torrc for how to set up a server.
2771 - Be more efficient about reading fd's when our global token bucket
2772 (used for rate limiting) becomes empty.
2774 - Stop asserting that computers always go forward in time. It's
2776 - When we sent a cell (e.g. destroy) and then marked an OR connection
2777 expired, we might close it before finishing a flush if the other
2778 side isn't reading right then.
2779 - Don't allow dirservers to start if they haven't defined
2781 - We were caching transient dns failures. Oops.
2782 - Prevent servers from publishing an internal IP as their address.
2783 - Address a strcat vulnerability in circuit.c
2786 Changes in version 0.0.2pre25 - 2004-03-04
2788 - Put the OR's IP in its router descriptor, not its fqdn. That way
2789 we'll stop being stalled by gethostbyname for nodes with flaky dns,
2792 - If the user typed in an address that didn't resolve, the server
2796 Changes in version 0.0.2pre24 - 2004-03-03
2798 - Fix an assertion failure in dns.c, where we were trying to dequeue
2799 a pending dns resolve even if it wasn't pending
2800 - Fix a spurious socks5 warning about still trying to write after the
2801 connection is finished.
2802 - Hold certain marked_for_close connections open until they're finished
2803 flushing, rather than losing bytes by closing them too early.
2804 - Correctly report the reason for ending a stream
2805 - Remove some duplicate calls to connection_mark_for_close
2806 - Put switch_id and start_daemon earlier in the boot sequence, so it
2807 will actually try to chdir() to options.DataDirectory
2808 - Make 'make test' exit(1) if a test fails; fix some unit tests
2809 - Make tor fail when you use a config option it doesn't know about,
2810 rather than warn and continue.
2811 - Make --version work
2812 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
2815 Changes in version 0.0.2pre23 - 2004-02-29
2817 - Print a statement when the first circ is finished, so the user
2819 - If a relay cell is unrecognized at the end of the circuit,
2820 send back a destroy. (So attacks to mutate cells are more
2822 - New config option 'excludenodes' to avoid certain nodes for circuits.
2823 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
2824 so you can collect coredumps there.
2826 - Fix a bug in tls flushing where sometimes data got wedged and
2827 didn't flush until more data got sent. Hopefully this bug was
2828 a big factor in the random delays we were seeing.
2829 - Make 'connected' cells include the resolved IP, so the client
2830 dns cache actually gets populated.
2831 - Disallow changing from ORPort=0 to ORPort>0 on hup.
2832 - When we time-out on a stream and detach from the circuit, send an
2833 end cell down it first.
2834 - Only warn about an unknown router (in exitnodes, entrynodes,
2835 excludenodes) after we've fetched a directory.
2838 Changes in version 0.0.2pre22 - 2004-02-26
2840 - Servers publish less revealing uname information in descriptors.
2841 - More memory tracking and assertions, to crash more usefully when
2843 - If the default torrc isn't there, just use some default defaults.
2844 Plus provide an internal dirservers file if they don't have one.
2845 - When the user tries to use Tor as an http proxy, give them an http
2846 501 failure explaining that we're a socks proxy.
2847 - Dump a new router.desc on hup, to help confused people who change
2848 their exit policies and then wonder why router.desc doesn't reflect
2850 - Clean up the generic tor.sh init script that we ship with.
2852 - If the exit stream is pending on the resolve, and a destroy arrives,
2853 then the stream wasn't getting removed from the pending list. I
2854 think this was the one causing recent server crashes.
2855 - Use a more robust poll on OSX 10.3, since their poll is flaky.
2856 - When it couldn't resolve any dirservers, it was useless from then on.
2857 Now it reloads the RouterFile (or default dirservers) if it has no
2859 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
2860 many users don't even *have* a /usr/local/sbin/.
2863 Changes in version 0.0.2pre21 - 2004-02-18
2865 - There's a ChangeLog file that actually reflects the changelog.
2866 - There's a 'torify' wrapper script, with an accompanying
2867 tor-tsocks.conf, that simplifies the process of using tsocks for
2868 tor. It even has a man page.
2869 - The tor binary gets installed to sbin rather than bin now.
2870 - Retry streams where the connected cell hasn't arrived in 15 seconds
2871 - Clean up exit policy handling -- get the default out of the torrc,
2872 so we can update it without forcing each server operator to fix
2874 - Allow imaps and pop3s in default exit policy
2876 - Prevent picking middleman nodes as the last node in the circuit
2879 Changes in version 0.0.2pre20 - 2004-01-30
2881 - We now have a deb package, and it's in debian unstable. Go to
2883 - I've split the TotalBandwidth option into BandwidthRate (how many
2884 bytes per second you want to allow, long-term) and
2885 BandwidthBurst (how many bytes you will allow at once before the cap
2886 kicks in). This better token bucket approach lets you, say, set
2887 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
2888 performance while not exceeding your monthly bandwidth quota.
2889 - Push out a tls record's worth of data once you've got it, rather
2890 than waiting until you've read everything waiting to be read. This
2891 may improve performance by pipelining better. We'll see.
2892 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
2893 from failed circuits (if they haven't been connected yet) and attach
2895 - Expire old streams that haven't managed to connect. Some day we'll
2896 have them reattach to new circuits instead.
2899 - Fix several memory leaks that were causing servers to become bloated
2901 - Fix a few very rare assert triggers. A few more remain.
2902 - Setuid to User _before_ complaining about running as root.
2905 Changes in version 0.0.2pre19 - 2004-01-07
2907 - Fix deadlock condition in dns farm. We were telling a child to die by
2908 closing the parent's file descriptor to him. But newer children were
2909 inheriting the open file descriptor from the parent, and since they
2910 weren't closing it, the socket never closed, so the child never read
2911 eof, so he never knew to exit. Similarly, dns workers were holding
2912 open other sockets, leading to all sorts of chaos.
2913 - New cleaner daemon() code for forking and backgrounding.
2914 - If you log to a file, it now prints an entry at the top of the
2915 logfile so you know it's working.
2916 - The onionskin challenge length was 30 bytes longer than necessary.
2917 - Started to patch up the spec so it's not quite so out of date.
2920 Changes in version 0.0.2pre18 - 2004-01-02
2922 - Fix endian issues with the 'integrity' field in the relay header.
2923 - Fix a potential bug where connections in state
2924 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
2927 Changes in version 0.0.2pre17 - 2003-12-30
2929 - Made --debuglogfile (or any second log file, actually) work.
2930 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
2931 adversary could force us into an infinite loop.
2934 - Each onionskin handshake now includes a hash of the computed key,
2935 to prove the server's identity and help perfect forward secrecy.
2936 - Changed cell size from 256 to 512 bytes (working toward compatibility
2938 - Changed cell length to 2 bytes, and moved it to the relay header.
2939 - Implemented end-to-end integrity checking for the payloads of
2941 - Separated streamid from 'recognized' (otherwise circuits will get
2942 messed up when we try to have streams exit from the middle). We
2943 use the integrity-checking to confirm that a cell is addressed to
2945 - Randomize the initial circid and streamid values, so an adversary who
2946 breaks into a node can't learn how many circuits or streams have
2950 Changes in version 0.0.2pre16 - 2003-12-14
2952 - Fixed a bug that made HUP trigger an assert
2953 - Fixed a bug where a circuit that immediately failed wasn't being
2954 counted as a failed circuit in counting retries.
2957 - Now we close the circuit when we get a truncated cell: otherwise we're
2958 open to an anonymity attack where a bad node in the path truncates
2959 the circuit and then we open streams at him.
2960 - Add port ranges to exit policies
2961 - Add a conservative default exit policy
2962 - Warn if you're running tor as root
2963 - on HUP, retry OR connections and close/rebind listeners
2964 - options.EntryNodes: try these nodes first when picking the first node
2965 - options.ExitNodes: if your best choices happen to include any of
2966 your preferred exit nodes, you choose among just those preferred
2968 - options.ExcludedNodes: nodes that are never picked in path building
2971 Changes in version 0.0.2pre15 - 2003-12-03
2972 o Robustness and bugfixes:
2973 - Sometimes clients would cache incorrect DNS resolves, which would
2974 really screw things up.
2975 - An OP that goes offline would slowly leak all its sockets and stop
2977 - A wide variety of bugfixes in exit node selection, exit policy
2978 handling, and processing pending streams when a new circuit is
2980 - Pick nodes for a path only from those the directory says are up
2981 - Choose randomly from all running dirservers, not always the first one
2982 - Increase allowed http header size for directory fetch.
2983 - Stop writing to stderr (if we're daemonized it will be closed).
2984 - Enable -g always, so cores will be more useful to me.
2985 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
2988 - Wrote a man page. It lists commonly used options.
2991 - Change default loglevel to warn.
2992 - Make PidFile default to null rather than littering in your CWD.
2993 - OnionRouter config option is now obsolete. Instead it just checks
2995 - Moved to a single unified torrc file for both clients and servers.
2998 Changes in version 0.0.2pre14 - 2003-11-29
2999 o Robustness and bugfixes:
3000 - Force the admin to make the DataDirectory himself
3001 - to get ownership/permissions right
3002 - so clients no longer make a DataDirectory and then never use it
3003 - fix bug where a client who was offline for 45 minutes would never
3004 pull down a directory again
3005 - fix (or at least hide really well) the dns assert bug that was
3006 causing server crashes
3007 - warnings and improved robustness wrt clockskew for certs
3008 - use the native daemon(3) to daemonize, when available
3009 - exit if bind() fails
3010 - exit if neither socksport nor orport is defined
3011 - include our own tor_timegm (Win32 doesn't have its own)
3012 - bugfix for win32 with lots of connections
3013 - fix minor bias in PRNG
3014 - make dirserver more robust to corrupt cached directory
3017 - Wrote the design document (woo)
3019 o Circuit building and exit policies:
3020 - Circuits no longer try to use nodes that the directory has told them
3022 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
3023 bitcounts (18.0.0.0/8).
3024 - Make AP connections standby for a circuit if no suitable circuit
3025 exists, rather than failing
3026 - Circuits choose exit node based on addr/port, exit policies, and
3027 which AP connections are standing by
3028 - Bump min pathlen from 2 to 3
3029 - Relay end cells have a payload to describe why the stream ended.
3030 - If the stream failed because of exit policy, try again with a new
3032 - Clients have a dns cache to remember resolved addresses.
3033 - Notice more quickly when we have no working circuits
3036 - APPort is now called SocksPort
3037 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
3039 - RecommendedVersions is now a config variable rather than
3040 hardcoded (for dirservers)
3041 - Reloads config on HUP
3042 - Usage info on -h or --help
3043 - If you set User and Group config vars, it'll setu/gid to them.
3045 Changes in version 0.0.2pre13 - 2003-10-19
3046 o General stability:
3047 - SSL_write no longer fails when it returns WANTWRITE and the number
3048 of bytes in the buf has changed by the next SSL_write call.
3049 - Fix segfault fetching directory when network is down
3050 - Fix a variety of minor memory leaks
3051 - Dirservers reload the fingerprints file on HUP, so I don't have
3052 to take down the network when I approve a new router
3053 - Default server config file has explicit Address line to specify fqdn
3056 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
3057 - Make listener connections not ever alloc bufs
3059 o Autoconf improvements:
3060 - don't clobber an external CFLAGS in ./configure
3061 - Make install now works
3062 - create var/lib/tor on make install
3063 - autocreate a tor.sh initscript to help distribs
3064 - autocreate the torrc and sample-server-torrc with correct paths
3066 o Log files and Daemonizing now work:
3067 - If --DebugLogFile is specified, log to it at -l debug
3068 - If --LogFile is specified, use it instead of commandline
3069 - If --RunAsDaemon is set, tor forks and backgrounds on startup