1 Changes in version 0.2.3.2-alpha - 2011-07-18
2 Tor 0.2.3.2-alpha introduces two new experimental features:
3 microdescriptors and pluggable transports. It also continues cleaning
4 up a variety of recently introduced features.
7 - Clients can now use microdescriptors instead of regular descriptors
8 to build circuits. Microdescriptors are authority-generated
9 summaries of regular descriptors' contents, designed to change
10 very rarely (see proposal 158 for details). This feature is
11 designed to save bandwidth, especially for clients on slow internet
12 connections. It's off by default for now, since nearly no caches
13 support it, but it will be on-by-default for clients in a future
14 version. You can use the UseMicrodescriptors option to turn it on.
15 - Tor clients using bridges can now be configured to use a separate
16 'transport' proxy for each bridge. This approach helps to resist
17 censorship by allowing bridges to use protocol obfuscation
18 plugins. It implements part of proposal 180. Implements ticket 2841.
19 - While we're trying to bootstrap, record how many TLS connections
20 fail in each state, and report which states saw the most failures
21 in response to any bootstrap failures. This feature may speed up
22 diagnosis of censorship events. Implements ticket 3116.
24 o Major bugfixes (on 0.2.3.1-alpha):
25 - When configuring a large set of nodes in EntryNodes (as with
26 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
27 random subset to be guards, and choose them in random
28 order. Fixes bug 2798.
29 - Tor could crash when remembering a consensus in a non-used consensus
30 flavor without having a current consensus set. Fixes bug 3361.
31 - Comparing an unknown address to a microdescriptor's shortened exit
32 policy would always give a "rejected" result. Fixes bug 3599.
33 - Using microdescriptors as a client no longer prevents Tor from
34 uploading and downloading hidden service descriptors. Fixes
38 - Allow nameservers with IPv6 address. Resolves bug 2574.
39 - Accept attempts to include a password authenticator in the
40 handshake, as supported by SOCKS5. This handles SOCKS clients that
41 don't know how to omit a password when authenticating. Resolves
43 - When configuring a large set of nodes in EntryNodes, and there are
44 enough of them listed as Guard so that we don't need to consider
45 the non-guard entries, prefer the ones listed with the Guard flag.
46 - Check for and recover from inconsistency in the microdescriptor
47 cache. This will make it harder for us to accidentally free a
48 microdescriptor without removing it from the appropriate data
49 structures. Fixes issue 3135; issue noted by "wanoskarnet".
50 - Log SSL state transitions at log level DEBUG, log domain
51 HANDSHAKE. This can be useful for debugging censorship events.
52 Implements ticket 3264.
53 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
54 implements ticket 3439.
56 o Minor bugfixes (on 0.2.3.1-alpha):
57 - Do not free all general-purpose regular descriptors just
58 because microdescriptor use is enabled. Fixes bug 3113.
59 - Correctly link libevent_openssl when --enable-static-libevent
60 is passed to configure. Fixes bug 3118.
61 - Bridges should not complain during their heartbeat log messages that
62 they are unlisted in the consensus: that's more or less the point
63 of being a bridge. Fixes bug 3183.
64 - Report a SIGNAL event to controllers when acting on a delayed
65 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
66 event to the controller if we acted on a SIGNAL NEWNYM command
67 immediately, and otherwise not report a SIGNAL event for the
68 command at all. Fixes bug 3349.
69 - Fix a crash when handling the SIGNAL controller command or
70 reporting ERR-level status events with bufferevents enabled. Found
71 by Robert Ransom. Fixes bug 3367.
72 - Always ship the tor-fw-helper manpage in our release tarballs.
73 Fixes bug 3389. Reported by Stephen Walker.
74 - Fix a class of double-mark-for-close bugs when bufferevents
75 are enabled. Fixes bug 3403.
76 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
77 - Add SIGNAL to the list returned by the 'GETINFO events/names'
78 control-port command. Fixes part of bug 3465.
79 - Prevent using negative indices during unit test runs when read_all()
80 fails. Spotted by coverity.
81 - Fix a rare memory leak when checking the nodelist without it being
82 present. Found by coverity.
83 - Only try to download a microdescriptor-flavored consensus from
84 a directory cache that provides them.
86 o Minor bugfixes (on 0.2.2.x and earlier):
87 - Assert that hidden-service-related operations are not performed
88 using single-hop circuits. Previously, Tor would assert that
89 client-side streams are not attached to single-hop circuits,
90 but not that other sensitive operations on the client and service
91 side are not performed using single-hop circuits. Fixes bug 3332;
93 - Don't publish a new relay descriptor when we reload our onion key,
94 unless the onion key has actually changed. Fixes bug 3263 and
95 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
96 - Allow GETINFO fingerprint to return a fingerprint even when
97 we have not yet built a router descriptor. Fixes bug 3577;
98 bugfix on 0.2.0.1-alpha.
99 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
100 on 0.2.2.4-alpha; fixes bug 3427.
102 o Code simplification and refactoring:
103 - Use tor_sscanf() in place of scanf() in more places through the
104 code. This makes us a little more locale-independent, and
105 should help shut up code-analysis tools that can't tell
106 a safe sscanf string from a dangerous one.
107 - Use tt_assert(), not tor_assert(), for checking for test failures.
108 This makes the unit tests more able to go on in the event that
110 - Split connection_about_to_close() into separate functions for each
114 - On Windows, we now define the _WIN32_WINNT macros only if they
115 are not already defined. This lets the person building Tor decide,
116 if they want, to require a later version of Windows.
119 Changes in version 0.2.2.30-rc - 2011-07-07
120 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
121 series. It fixes a few smaller bugs, but generally appears stable.
122 Please test it and let us know whether it is!
125 - Send a SUCCEEDED stream event to the controller when a reverse
126 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
127 discovered by katmagic.
128 - Always NUL-terminate the sun_path field of a sockaddr_un before
129 passing it to the kernel. (Not a security issue: kernels are
130 smart enough to reject bad sockaddr_uns.) Found by Coverity;
131 CID #428. Bugfix on Tor 0.2.0.3-alpha.
132 - Don't stack-allocate the list of supplementary GIDs when we're
133 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
134 could take up to 256K, which is way too much stack. Found by
135 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
136 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
137 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
138 fixes part of bug 3465.
139 - Fix a memory leak when receiving a descriptor for a hidden
140 service we didn't ask for. Found by Coverity; CID #30. Bugfix
144 - Update to the July 1 2011 Maxmind GeoLite Country database.
147 Changes in version 0.2.2.29-beta - 2011-06-20
148 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
149 have bridge lines in their torrc but don't want to use them; gets
150 us closer to having the control socket feature working on Debian;
151 and fixes a variety of smaller bugs.
154 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
155 When we changed the default behavior to "use bridges if any
156 are listed in the torrc", we surprised users who had bridges
157 in their torrc files but who didn't actually want to use them.
158 Partial resolution for bug 3354.
161 - Don't attach new streams to old rendezvous circuits after SIGNAL
162 NEWNYM. Previously, we would keep using an existing rendezvous
163 circuit if it remained open (i.e. if it were kept open by a
164 long-lived stream, or if a new stream were attached to it before
165 Tor could notice that it was old and no longer in use). Bugfix on
166 0.1.1.15-rc; fixes bug 3375.
169 - Fix a bug when using ControlSocketsGroupWritable with User. The
170 directory's group would be checked against the current group, not
171 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
172 bugfix on 0.2.2.26-beta.
173 - Make connection_printf_to_buf()'s behaviour sane. Its callers
174 expect it to emit a CRLF iff the format string ends with CRLF;
175 it actually emitted a CRLF iff (a) the format string ended with
176 CRLF or (b) the resulting string was over 1023 characters long or
177 (c) the format string did not end with CRLF *and* the resulting
178 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
179 fixes part of bug 3407.
180 - Make send_control_event_impl()'s behaviour sane. Its callers
181 expect it to always emit a CRLF at the end of the string; it
182 might have emitted extra control characters as well. Bugfix on
183 0.1.1.9-alpha; fixes another part of bug 3407.
184 - Make crypto_rand_int() check the value of its input correctly.
185 Previously, it accepted values up to UINT_MAX, but could return a
186 negative number if given a value above INT_MAX+1. Found by George
187 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
188 - Avoid a segfault when reading a malformed circuit build state
189 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
191 - When asked about a DNS record type we don't support via a
192 client DNSPort, reply with NOTIMPL rather than an empty
193 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
194 - Fix a rare memory leak during stats writing. Found by coverity.
197 - Update to the June 1 2011 Maxmind GeoLite Country database.
199 o Code simplifications and refactoring:
200 - Remove some dead code as indicated by coverity.
201 - Remove a few dead assignments during router parsing. Found by
203 - Add some forgotten return value checks during unit tests. Found
205 - Don't use 1-bit wide signed bit fields. Found by coverity.
208 Changes in version 0.2.2.28-beta - 2011-06-04
209 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
210 fixed a big bug in whether relays stay in the consensus consistently,
211 we moved closer to handling bridges and hidden services correctly,
212 and we started the process of better handling the dreaded "my Vidalia
213 died, and now my Tor demands a password when I try to reconnect to it"
217 - Don't decide to make a new descriptor when receiving a HUP signal.
218 This bug has caused a lot of 0.2.2.x relays to disappear from the
219 consensus periodically. Fixes the most common case of triggering
220 bug 1810; bugfix on 0.2.2.7-alpha.
221 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
222 - Don't try to build descriptors if "ORPort auto" is set and we
223 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
225 - Resolve a crash that occurred when setting BridgeRelay to 1 with
226 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
227 - Apply circuit timeouts to opened hidden-service-related circuits
228 based on the correct start time. Previously, we would apply the
229 circuit build timeout based on time since the circuit's creation;
230 it was supposed to be applied based on time since the circuit
231 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
232 - Use the same circuit timeout for client-side introduction
233 circuits as for other four-hop circuits, rather than the timeout
234 for single-hop directory-fetch circuits; the shorter timeout may
235 have been appropriate with the static circuit build timeout in
236 0.2.1.x and earlier, but caused many hidden service access attempts
237 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
238 on 0.2.2.2-alpha; fixes another part of bug 1297.
239 - In ticket 2511 we fixed a case where you could use an unconfigured
240 bridge if you had configured it as a bridge the last time you ran
241 Tor. Now fix another edge case: if you had configured it as a bridge
242 but then switched to a different bridge via the controller, you
243 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
247 - Add an __OwningControllerProcess configuration option and a
248 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
249 that when it exits, Tor will shut down. Implements feature 3049.
250 - If "UseBridges 1" is set and no bridges are configured, Tor will
251 now refuse to build any circuits until some bridges are set.
252 If "UseBridges auto" is set, Tor will use bridges if they are
253 configured and we are not running as a server, but otherwise will
254 make circuits as usual. The new default is "auto". Patch by anonym,
255 so the Tails LiveCD can stop automatically revealing you as a Tor
259 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
260 - Remove a trailing asterisk from "exit-policy/default" in the
261 output of the control port command "GETINFO info/names". Bugfix
263 - Use a wide type to hold sockets when built for 64-bit Windows builds.
265 - Warn when the user configures two HiddenServiceDir lines that point
266 to the same directory. Bugfix on 0.0.6 (the version introducing
267 HiddenServiceDir); fixes bug 3289.
268 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
269 part of bug 2748; bugfix on 0.2.0.10-alpha.
270 - Log malformed requests for rendezvous descriptors as protocol
271 warnings, not warnings. Also, use a more informative log message
272 in case someone sees it at log level warning without prior
273 info-level messages. Fixes the other part of bug 2748; bugfix
275 - Clear the table recording the time of the last request for each
276 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
277 Previously, we would clear our HS descriptor cache on SIGNAL
278 NEWNYM, but if we had previously retrieved a descriptor (or tried
279 to) from every directory responsible for it, we would refuse to
280 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
282 - Fix a log message that said "bits" while displaying a value in
283 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
285 - When checking for 1024-bit keys, check for 1024 bits, not 128
286 bytes. This allows Tor to correctly discard keys of length 1017
287 through 1023. Bugfix on 0.0.9pre5.
290 - Relays now log the reason for publishing a new relay descriptor,
291 so we have a better chance of hunting down instances of bug 1810.
292 Resolves ticket 3252.
293 - Revise most log messages that refer to nodes by nickname to
294 instead use the "$key=nickname at address" format. This should be
295 more useful, especially since nicknames are less and less likely
296 to be unique. Resolves ticket 3045.
297 - Log (at info level) when purging pieces of hidden-service-client
298 state because of SIGNAL NEWNYM.
301 - Remove undocumented option "-F" from tor-resolve: it hasn't done
302 anything since 0.2.1.16-rc.
305 Changes in version 0.2.2.27-beta - 2011-05-18
306 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
307 release, and also adds a few more general bugfixes.
310 - Fix a crash bug when changing bridges in a running Tor process.
311 Fixes bug 3213; bugfix on 0.2.2.26-beta.
312 - When the controller configures a new bridge, don't wait 10 to 60
313 seconds before trying to fetch its descriptor. Bugfix on
314 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
317 - Require that onion keys have exponent 65537 in microdescriptors too.
318 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
319 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
320 Changed the limit to 512 characters by removing base64 newlines.
321 Fixes bug 2752. Fix by Michael Yakubovich.
322 - When a client starts or stops using bridges, never use a circuit
323 that was built before the configuration change. This behavior could
324 put at risk a user who uses bridges to ensure that her traffic
325 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
329 Changes in version 0.2.2.26-beta - 2011-05-17
330 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
331 also introduces a new "socksport auto" approach that should make it
332 easier to run multiple Tors on the same system, and does a lot of
333 cleanup to get us closer to a release candidate.
335 o Security/privacy fixes:
336 - Replace all potentially sensitive memory comparison operations
337 with versions whose runtime does not depend on the data being
338 compared. This will help resist a class of attacks where an
339 adversary can use variations in timing information to learn
340 sensitive data. Fix for one case of bug 3122. (Safe memcmp
341 implementation by Robert Ransom based partially on code by DJB.)
342 - When receiving a hidden service descriptor, check that it is for
343 the hidden service we wanted. Previously, Tor would store any
344 hidden service descriptors that a directory gave it, whether it
345 wanted them or not. This wouldn't have let an attacker impersonate
346 a hidden service, but it did let directories pre-seed a client
347 with descriptors that it didn't want. Bugfix on 0.0.6.
348 - On SIGHUP, do not clear out all TrackHostExits mappings, client
349 DNS cache entries, and virtual address mappings: that's what
350 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
353 - The options SocksPort, ControlPort, and so on now all accept a
354 value "auto" that opens a socket on an OS-selected port. A
355 new ControlPortWriteToFile option tells Tor to write its
356 actual control port or ports to a chosen file. If the option
357 ControlPortFileGroupReadable is set, the file is created as
358 group-readable. Now users can run two Tor clients on the same
359 system without needing to manually mess with parameters. Resolves
361 - Set SO_REUSEADDR on all sockets, not just listeners. This should
362 help busy exit nodes avoid running out of useable ports just
363 because all the ports have been used in the near past. Resolves
367 - New "GETINFO net/listeners/(type)" controller command to return
368 a list of addresses and ports that are bound for listeners for a
369 given connection type. This is useful when the user has configured
370 "SocksPort auto" and the controller needs to know which port got
371 chosen. Resolves another part of ticket 3076.
372 - Add a new ControlSocketsGroupWritable configuration option: when
373 it is turned on, ControlSockets are group-writeable by the default
374 group of the current user. Patch by Jérémy Bobbio; implements
376 - Tor now refuses to create a ControlSocket in a directory that is
377 world-readable (or group-readable if ControlSocketsGroupWritable
378 is 0). This is necessary because some operating systems do not
379 enforce permissions on an AF_UNIX sockets. Permissions on the
380 directory holding the socket, however, seems to work everywhere.
381 - Rate-limit a warning about failures to download v2 networkstatus
382 documents. Resolves part of bug 1352.
383 - Backport code from 0.2.3.x that allows directory authorities to
384 clean their microdescriptor caches. Needed to resolve bug 2230.
385 - When an HTTPS proxy reports "403 Forbidden", we now explain
386 what it means rather than calling it an unexpected status code.
387 Closes bug 2503. Patch from Michael Yakubovich.
388 - Update to the May 1 2011 Maxmind GeoLite Country database.
391 - Authorities now clean their microdesc cache periodically and when
392 reading from disk initially, not only when adding new descriptors.
393 This prevents a bug where we could lose microdescriptors. Bugfix
394 on 0.2.2.6-alpha. 2230
395 - Do not crash when our configuration file becomes unreadable, for
396 example due to a permissions change, between when we start up
397 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
399 - Avoid a bug that would keep us from replacing a microdescriptor
400 cache on Windows. (We would try to replace the file while still
401 holding it open. That's fine on Unix, but Windows doesn't let us
402 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
403 - Add missing explanations for the authority-related torrc options
404 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
405 man page. Resolves issue 2379.
406 - As an authority, do not upload our own vote or signature set to
407 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
408 it would get flagged as a duplicate. Resolves bug 3026.
409 - Accept hidden service descriptors if we think we might be a hidden
410 service directory, regardless of what our consensus says. This
411 helps robustness, since clients and hidden services can sometimes
412 have a more up-to-date view of the network consensus than we do,
413 and if they think that the directory authorities list us a HSDir,
414 we might actually be one. Related to bug 2732; bugfix on
416 - When a controller changes TrackHostExits, remove mappings for
417 hosts that should no longer have their exits tracked. Bugfix on
419 - When a controller changes VirtualAddrNetwork, remove any mappings
420 for hosts that were automapped to the old network. Bugfix on
422 - When a controller changes one of the AutomapHosts* options, remove
423 any mappings for hosts that should no longer be automapped. Bugfix
425 - Do not reset the bridge descriptor download status every time we
426 re-parse our configuration or get a configuration change. Fixes
427 bug 3019; bugfix on 0.2.0.3-alpha.
429 o Minor bugfixes (code cleanup):
430 - When loading the microdesc journal, remember its current size.
431 In 0.2.2, this helps prevent the microdesc journal from growing
432 without limit on authorities (who are the only ones to use it in
433 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
434 Fix posted by "cypherpunks."
435 - The microdesc journal is supposed to get rebuilt only if it is
436 at least _half_ the length of the store, not _twice_ the length
437 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
438 - Fix a potential null-pointer dereference while computing a
439 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
441 - Avoid a possible null-pointer dereference when rebuilding the mdesc
442 cache without actually having any descriptors to cache. Bugfix on
443 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
444 - If we fail to compute the identity digest of a v3 legacy keypair,
445 warn, and don't use a buffer-full of junk instead. Bugfix on
446 0.2.1.1-alpha; fixes bug 3106.
447 - Resolve an untriggerable issue in smartlist_string_num_isin(),
448 where if the function had ever in the future been used to check
449 for the presence of a too-large number, it would have given an
450 incorrect result. (Fortunately, we only used it for 16-bit
451 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
452 - Require that introduction point keys and onion handshake keys
453 have a public exponent of 65537. Starts to fix bug 3207; bugfix
457 - Caches no longer download and serve v2 networkstatus documents
458 unless FetchV2Networkstatus flag is set: these documents haven't
459 haven't been used by clients or relays since 0.2.0.x. Resolves
463 Changes in version 0.2.3.1-alpha - 2011-05-05
464 Tor 0.2.3.1-alpha adds some new experimental features, including support
465 for an improved network IO backend, IOCP networking on Windows,
466 microdescriptor caching, "fast-start" support for streams, and automatic
467 home router configuration. There are also numerous internal improvements
468 to try to make the code easier for developers to work with.
470 This is the first alpha release in a new series, so expect there to be
471 bugs. Users who would rather test out a more stable branch should
472 stay with 0.2.2.x for now.
475 - Tor can now optionally build with the "bufferevents" buffered IO
476 backend provided by Libevent 2. To use this feature, make sure you
477 have the latest possible version of Libevent, and pass the
478 --enable-bufferevents flag to configure when building Tor from
479 source. This feature will make our networking code more flexible,
480 let us stack layers on each other, and let us use more efficient
481 zero-copy transports where available.
482 - As an experimental feature, Tor can use IOCP for networking on Windows.
483 Once this code is tuned and optimized, it promises much better
484 performance than the select-based backend we've used in the past. To
485 try this feature, you must build Tor with Libevent 2, configure Tor
486 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
487 your torrc. There are known bugs here: only try this if you can help
488 debug it as it breaks.
489 - The EntryNodes option can now include country codes like {de} or IP
490 addresses or network masks. Previously we had disallowed these options
491 because we didn't have an efficient way to keep the list up to
492 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
493 - Exit nodes now accept and queue data on not-yet-connected streams.
494 Previously, the client wasn't allowed to send data until the stream was
495 connected, which slowed down all connections. This change will enable
496 clients to perform a "fast-start" on streams and send data without
497 having to wait for a confirmation that the stream has opened. (Patch
498 from Ian Goldberg; implements the server side of Proposal 174.)
499 - Tor now has initial support for automatic port mapping on the many
500 home routers that support NAT-PMP or UPnP. (Not yet supported on
501 Windows). To build the support code, you'll need to have libnatpnp
502 library and/or the libminiupnpc library, and you'll need to enable the
503 feature specifically by passing "--enable-upnp" and/or
504 "--enable-natpnp" to configure. To turn it on, use the new
505 PortForwarding option.
506 - Caches now download, cache, and serve multiple "flavors" of the
507 consensus, including a flavor that describes microdescriptors.
508 - Caches now download, cache, and serve microdescriptors -- small
509 summaries of router descriptors that are authenticated by all of the
510 directory authorities. Once enough caches are running this code,
511 clients will be able to save significant amounts of directory bandwidth
512 by downloading microdescriptors instead of router descriptors.
515 - Make logging resolution configurable with a new LogTimeGranularity
516 option, and change the default from 1 millisecond to 1 second.
517 Implements enhancement 1668.
518 - We log which torrc file we're using on startup. Implements ticket
520 - Ordinarily, Tor does not count traffic from private addresses (like
521 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
522 There is now a new option, CountPrivateBandwidth, to disable this
523 behavior. Patch from Daniel Cagara.
524 - New --enable-static-tor configure option for building Tor as
525 statically as possible. Idea, general hackery and thoughts from
526 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
528 - If you set the NumCPUs option to 0, Tor will now try to detect how
529 many CPUs you have. This is the new default behavior.
530 - Turn on directory request statistics by default and include them in
531 extra-info descriptors. Don't break if we have no GeoIP database.
532 - Relays that set "ConnDirectionStatistics 1" write statistics on the
533 bidirectional use of connections to disk every 24 hours.
534 - Add a GeoIP file digest to the extra-info descriptor. Implements
536 - The NodeFamily option -- which let you declare that you want to
537 consider nodes to be part of a family whether they list themselves
538 that way or not -- now allows IP address ranges and country codes.
539 - Add a new 'Heartbeat' log message type to periodically log a message
540 describing Tor's status at level Notice. This feature is meant for
541 operators who log at notice, and want to make sure that their Tor
542 server is still working. Implementation by George Kadianakis.
544 o Minor bugfixes (on 0.2.2.25-alpha):
545 - When loading the microdesc journal, remember its current size.
546 In 0.2.2, this helps prevent the microdesc journal from growing
547 without limit on authorities (who are the only ones to use it in
548 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
549 Fix posted by "cypherpunks."
550 - The microdesc journal is supposed to get rebuilt only if it is
551 at least _half_ the length of the store, not _twice_ the length
552 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
553 - If as an authority we fail to compute the identity digest of a v3
554 legacy keypair, warn, and don't use a buffer-full of junk instead.
555 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
556 - Authorities now clean their microdesc cache periodically and when
557 reading from disk initially, not only when adding new descriptors.
558 This prevents a bug where we could lose microdescriptors. Bugfix
561 o Minor features (controller):
562 - Add a new SIGNAL event to the controller interface so that
563 controllers can be notified when Tor handles a signal. Resolves
564 issue 1955. Patch by John Brooks.
565 - Add a new GETINFO option to get total bytes read and written. Patch
566 from pipe, revised by atagar. Resolves ticket 2345.
567 - Implement some GETINFO controller fields to provide information about
568 the Tor process's pid, euid, username, and resource limits.
571 - Our build system requires automake 1.6 or later to create the
572 Makefile.in files. Previously, you could have used 1.4.
573 This only affects developers and people building Tor from git;
574 people who build Tor from the source distribution without changing
575 the Makefile.am files should be fine.
576 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
577 so on. This is more robust against some of the failure modes
578 associated with running the autotools pieces on their own.
580 o Minor packaging issues:
581 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
582 already created. Patch from Andreas Stieger. Fixes bug 2573.
584 o Code simplifications and refactoring:
585 - A major revision to our internal node-selecting and listing logic.
586 Tor already had at least two major ways to look at the question of
587 "which Tor servers do we know about": a list of router descriptors,
588 and a list of entries in the current consensus. With
589 microdescriptors, we're adding a third. Having so many systems
590 without an abstraction layer over them was hurting the codebase.
591 Now, we have a new "node_t" abstraction that presents a consistent
592 interface to a client's view of a Tor node, and holds (nearly) all
593 of the mutable state formerly in routerinfo_t and routerstatus_t.
594 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
595 no longer link against Libevent: they never used it, but
596 our library structure used to force them to link it.
599 - Remove some old code to work around even older versions of Tor that
600 used forked processes to handle DNS requests. Such versions of Tor
601 are no longer in use as servers.
603 o Documentation fixes:
604 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
605 - Add missing documentation for the authority-related torrc options
606 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
610 Changes in version 0.2.2.25-alpha - 2011-04-29
611 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
612 robust, routers no longer overreport their bandwidth, Win7 should crash
613 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
614 now prevents hidden service-related activity from being linkable. It
615 provides more information to Vidalia so you can see if your bridge is
616 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
617 StrictNodes configuration options to make them more reliable, more
618 understandable, and more regularly applied. If you use those options,
619 please see the revised documentation for them in the manual page.
622 - Relays were publishing grossly inflated bandwidth values because
623 they were writing their state files wrong--now they write the
624 correct value. Also, resume reading bandwidth history from the
625 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
626 - Improve hidden service robustness: When we find that we have
627 extended a hidden service's introduction circuit to a relay not
628 listed as an introduction point in the HS descriptor we currently
629 have, retry with an introduction point from the current
630 descriptor. Previously we would just give up. Fixes bugs 1024 and
631 1930; bugfix on 0.2.0.10-alpha.
632 - Clients now stop trying to use an exit node associated with a given
633 destination by TrackHostExits if they fail to reach that exit node.
634 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
635 - Fix crash bug on platforms where gmtime and localtime can return
636 NULL. Windows 7 users were running into this one. Fixes part of bug
637 2077. Bugfix on all versions of Tor. Found by boboper.
639 o Security and stability fixes:
640 - Don't double-free a parsable, but invalid, microdescriptor, even if
641 it is followed in the blob we're parsing by an unparsable
642 microdescriptor. Fixes an issue reported in a comment on bug 2954.
643 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
644 - If the Nickname configuration option isn't given, Tor would pick a
645 nickname based on the local hostname as the nickname for a relay.
646 Because nicknames are not very important in today's Tor and the
647 "Unnamed" nickname has been implemented, this is now problematic
648 behavior: It leaks information about the hostname without being
649 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
650 introduced the Unnamed nickname. Reported by tagnaq.
651 - Fix an uncommon assertion failure when running with DNSPort under
652 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
653 - Avoid linkability based on cached hidden service descriptors: forget
654 all hidden service descriptors cached as a client when processing a
655 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
658 - Export GeoIP information on bridge usage to controllers even if we
659 have not yet been running for 24 hours. Now Vidalia bridge operators
660 can get more accurate and immediate feedback about their
661 contributions to the network.
663 o Major features and bugfixes (node selection):
664 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
665 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
666 options. Previously, we had been ambiguous in describing what
667 counted as an "exit" node, and what operations exactly "StrictNodes
668 0" would permit. This created confusion when people saw nodes built
669 through unexpected circuits, and made it hard to tell real bugs from
670 surprises. Now the intended behavior is:
671 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
672 a node that delivers user traffic outside the Tor network.
673 . "Entry", in the context of EntryNodes, means a node used as the
674 first hop of a multihop circuit. It doesn't include direct
675 connections to directory servers.
676 . "ExcludeNodes" applies to all nodes.
677 . "StrictNodes" changes the behavior of ExcludeNodes only. When
678 StrictNodes is set, Tor should avoid all nodes listed in
679 ExcludeNodes, even when it will make user requests fail. When
680 StrictNodes is *not* set, then Tor should follow ExcludeNodes
681 whenever it can, except when it must use an excluded node to
682 perform self-tests, connect to a hidden service, provide a
683 hidden service, fulfill a .exit request, upload directory
684 information, or fetch directory information.
685 Collectively, the changes to implement the behavior fix bug 1090.
686 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
687 a node is listed in both, it's treated as excluded.
688 - ExcludeNodes now applies to directory nodes -- as a preference if
689 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
690 Don't exclude all the directory authorities and set StrictNodes to 1
691 unless you really want your Tor to break.
692 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
693 - ExcludeExitNodes now overrides .exit requests.
694 - We don't use bridges listed in ExcludeNodes.
695 - When StrictNodes is 1:
696 . We now apply ExcludeNodes to hidden service introduction points
697 and to rendezvous points selected by hidden service users. This
698 can make your hidden service less reliable: use it with caution!
699 . If we have used ExcludeNodes on ourself, do not try relay
700 reachability self-tests.
701 . If we have excluded all the directory authorities, we will not
702 even try to upload our descriptor if we're a relay.
703 . Do not honor .exit requests to an excluded node.
704 - Remove a misfeature that caused us to ignore the Fast/Stable flags
705 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
706 - When the set of permitted nodes changes, we now remove any mappings
707 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
709 - We never cannibalize a circuit that had excluded nodes on it, even
710 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
711 - Revert a change where we would be laxer about attaching streams to
712 circuits than when building the circuits. This was meant to prevent
713 a set of bugs where streams were never attachable, but our improved
714 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
715 - Keep track of how many times we launch a new circuit to handle a
716 given stream. Too many launches could indicate an inconsistency
717 between our "launch a circuit to handle this stream" logic and our
718 "attach this stream to one of the available circuits" logic.
719 - Improve log messages related to excluded nodes.
722 - Fix a spurious warning when moving from a short month to a long
723 month on relays with month-based BandwidthAccounting. Bugfix on
724 0.2.2.17-alpha; fixes bug 3020.
725 - When a client finds that an origin circuit has run out of 16-bit
726 stream IDs, we now mark it as unusable for new streams. Previously,
727 we would try to close the entire circuit. Bugfix on 0.0.6.
728 - Add a forgotten cast that caused a compile warning on OS X 10.6.
729 Bugfix on 0.2.2.24-alpha.
730 - Be more careful about reporting the correct error from a failed
731 connect() system call. Under some circumstances, it was possible to
732 look at an incorrect value for errno when sending the end reason.
733 Bugfix on 0.1.0.1-rc.
734 - Correctly handle an "impossible" overflow cases in connection byte
735 counting, where we write or read more than 4GB on an edge connection
736 in a single second. Bugfix on 0.1.2.8-beta.
737 - Correct the warning displayed when a rendezvous descriptor exceeds
738 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
740 - Clients and hidden services now use HSDir-flagged relays for hidden
741 service descriptor downloads and uploads even if the relays have no
742 DirPort set and the client has disabled TunnelDirConns. This will
743 eventually allow us to give the HSDir flag to relays with no
744 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
745 - Downgrade "no current certificates known for authority" message from
746 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
747 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
748 2917. Bugfix on 0.1.1.1-alpha.
749 - Only limit the lengths of single HS descriptors, even when multiple
750 HS descriptors are published to an HSDir relay in a single POST
751 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
752 - Write the current time into the LastWritten line in our state file,
753 rather than the time from the previous write attempt. Also, stop
754 trying to use a time of -1 in our log statements. Fixes bug 3039;
755 bugfix on 0.2.2.14-alpha.
756 - Be more consistent in our treatment of file system paths. "~" should
757 get expanded to the user's home directory in the Log config option.
758 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
759 feature for the -f and --DataDirectory options.
762 - Make sure every relay writes a state file at least every 12 hours.
763 Previously, a relay could go for weeks without writing its state
764 file, and on a crash could lose its bandwidth history, capacity
765 estimates, client country statistics, and so on. Addresses bug 3012.
766 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
767 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
768 clients are already deprecated because of security bugs.
769 - Don't allow v0 hidden service authorities to act as clients.
770 Required by fix for bug 3000.
771 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
773 - Ensure that no empty [dirreq-](read|write)-history lines are added
774 to an extrainfo document. Implements ticket 2497.
776 o Code simplification and refactoring:
777 - Remove workaround code to handle directory responses from servers
778 that had bug 539 (they would send HTTP status 503 responses _and_
779 send a body too). Since only server versions before
780 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
781 keep the workaround in place.
782 - Remove the old 'fuzzy time' logic. It was supposed to be used for
783 handling calculations where we have a known amount of clock skew and
784 an allowed amount of unknown skew. But we only used it in three
785 places, and we never adjusted the known/unknown skew values. This is
786 still something we might want to do someday, but if we do, we'll
787 want to do it differently.
788 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
789 None of the cases where we did this before were wrong, but by making
790 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
791 - Use GetTempDir to find the proper temporary directory location on
792 Windows when generating temporary files for the unit tests. Patch by
796 Changes in version 0.2.2.24-alpha - 2011-04-08
797 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
798 prevented Tor clients from effectively using "multihomed" bridges,
799 that is, bridges that listen on multiple ports or IP addresses so users
800 can continue to use some of their addresses even if others get blocked.
803 - Fix a bug where bridge users who configure the non-canonical
804 address of a bridge automatically switch to its canonical
805 address. If a bridge listens at more than one address, it should be
806 able to advertise those addresses independently and any non-blocked
807 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
809 - If you configured Tor to use bridge A, and then quit and
810 configured Tor to use bridge B instead, it would happily continue
811 to use bridge A if it's still reachable. While this behavior is
812 a feature if your goal is connectivity, in some scenarios it's a
813 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
814 - Directory authorities now use data collected from their own
815 uptime observations when choosing whether to assign the HSDir flag
816 to relays, instead of trusting the uptime value the relay reports in
817 its descriptor. This change helps prevent an attack where a small
818 set of nodes with frequently-changing identity keys can blackhole
819 a hidden service. (Only authorities need upgrade; others will be
820 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
823 - When we restart our relay, we might get a successful connection
824 from the outside before we've started our reachability tests,
825 triggering a warning: "ORPort found reachable, but I have no
826 routerinfo yet. Failing to inform controller of success." This
827 bug was harmless unless Tor is running under a controller
828 like Vidalia, in which case the controller would never get a
829 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
831 - Make directory authorities more accurate at recording when
832 relays that have failed several reachability tests became
833 unreachable, so we can provide more accuracy at assigning Stable,
834 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
835 - Fix an issue that prevented static linking of libevent on
836 some platforms (notably Linux). Fixes bug 2698; bugfix on
837 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
838 the --with-static-libevent configure option).
839 - We now ask the other side of a stream (the client or the exit)
840 for more data on that stream when the amount of queued data on
841 that stream dips low enough. Previously, we wouldn't ask the
842 other side for more data until either it sent us more data (which
843 it wasn't supposed to do if it had exhausted its window!) or we
844 had completely flushed all our queued data. This flow control fix
845 should improve throughput. Fixes bug 2756; bugfix on the earliest
846 released versions of Tor (svn commit r152).
847 - Avoid a double-mark-for-free warning when failing to attach a
848 transparent proxy connection. (We thought we had fixed this in
849 0.2.2.23-alpha, but it turns out our fix was checking the wrong
850 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
851 bug) and 0.2.2.23-alpha (the incorrect fix).
852 - When warning about missing zlib development packages during compile,
853 give the correct package names. Bugfix on 0.2.0.1-alpha.
856 - Directory authorities now log the source of a rejected POSTed v3
858 - Make compilation with clang possible when using
859 --enable-gcc-warnings by removing two warning optionss that clang
860 hasn't implemented yet and by fixing a few warnings. Implements
862 - When expiring circuits, use microsecond timers rather than
863 one-second timers. This can avoid an unpleasant situation where a
864 circuit is launched near the end of one second and expired right
865 near the beginning of the next, and prevent fluctuations in circuit
867 - Use computed circuit-build timeouts to decide when to launch
868 parallel introduction circuits for hidden services. (Previously,
869 we would retry after 15 seconds.)
870 - Update to the April 1 2011 Maxmind GeoLite Country database.
873 - Create the /var/run/tor directory on startup on OpenSUSE if it is
874 not already created. Patch from Andreas Stieger. Fixes bug 2573.
876 o Documentation changes:
877 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
878 - Resolve all doxygen warnings except those for missing documentation.
880 - Add doxygen documentation for more functions, fields, and types.
883 Changes in version 0.2.2.23-alpha - 2011-03-08
884 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
885 they restart they don't lose their bandwidth capacity estimate. This
886 release also fixes a diverse set of user-facing bugs, ranging from
887 relays overrunning their rate limiting to clients falsely warning about
888 clock skew to bridge descriptor leaks by our bridge directory authority.
891 - Stop sending a CLOCK_SKEW controller status event whenever
892 we fetch directory information from a relay that has a wrong clock.
893 Instead, only inform the controller when it's a trusted authority
894 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
895 the rest of bug 1074.
896 - Fix an assert in parsing router descriptors containing IPv6
897 addresses. This one took down the directory authorities when
898 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
899 - Make the bridge directory authority refuse to answer directory
900 requests for "all" descriptors. It used to include bridge
901 descriptors in its answer, which was a major information leak.
902 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
903 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
904 Tor would ignore their RelayBandwidthBurst setting,
905 potentially using more bandwidth than expected. Bugfix on
906 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
907 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
908 hidserv" in her torrc. The 'hidserv' argument never controlled
909 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
912 - Relays now save observed peak bandwidth throughput rates to their
913 state file (along with total usage, which was already saved)
914 so that they can determine their correct estimated bandwidth on
915 restart. Resolves bug 1863, where Tor relays would reset their
916 estimated bandwidth to 0 after restarting.
917 - Directory authorities now take changes in router IP address and
918 ORPort into account when determining router stability. Previously,
919 if a router changed its IP or ORPort, the authorities would not
920 treat it as having any downtime for the purposes of stability
921 calculation, whereas clients would experience downtime since the
922 change could take a while to propagate to them. Resolves issue 1035.
923 - Enable Address Space Layout Randomization (ASLR) and Data Execution
924 Prevention (DEP) by default on Windows to make it harder for
925 attackers to exploit vulnerabilities. Patch from John Brooks.
927 o Minor bugfixes (on 0.2.1.x and earlier):
928 - Fix a rare crash bug that could occur when a client was configured
929 with a large number of bridges. Fixes bug 2629; bugfix on
930 0.2.1.2-alpha. Bugfix by trac user "shitlei".
931 - Avoid a double mark-for-free warning when failing to attach a
932 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
934 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
935 found by "cypherpunks". This bug was introduced before the first
936 Tor release, in svn commit r110.
937 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
938 don't mention them in the manpage. Fixes bug 2450; issue
939 spotted by keb and G-Lo.
940 - Fix a bug in bandwidth history state parsing that could have been
941 triggered if a future version of Tor ever changed the timing
942 granularity at which bandwidth history is measured. Bugfix on
944 - When a relay decides that its DNS is too broken for it to serve
945 as an exit server, it advertised itself as a non-exit, but
946 continued to act as an exit. This could create accidental
947 partitioning opportunities for users. Instead, if a relay is
948 going to advertise reject *:* as its exit policy, it should
949 really act with exit policy "reject *:*". Fixes bug 2366.
950 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
951 - In the special case where you configure a public exit relay as your
952 bridge, Tor would be willing to use that exit relay as the last
953 hop in your circuit as well. Now we fail that circuit instead.
954 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
955 - Fix a bug with our locking implementation on Windows that couldn't
956 correctly detect when a file was already locked. Fixes bug 2504,
957 bugfix on 0.2.1.6-alpha.
958 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
959 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
961 - Set target port in get_interface_address6() correctly. Bugfix
962 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
963 - Directory authorities are now more robust to hops back in time
964 when calculating router stability. Previously, if a run of uptime
965 or downtime appeared to be negative, the calculation could give
966 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
968 - Fix an assert that got triggered when using the TestingTorNetwork
969 configuration option and then issuing a GETINFO config-text control
970 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
972 o Minor bugfixes (on 0.2.2.x):
973 - Clients should not weight BadExit nodes as Exits in their node
974 selection. Similarly, directory authorities should not count BadExit
975 bandwidth as Exit bandwidth when computing bandwidth-weights.
976 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
977 - Correctly clear our dir_read/dir_write history when there is an
978 error parsing any bw history value from the state file. Bugfix on
980 - Resolve a bug in verifying signatures of directory objects
981 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
982 Fixes bug 2409. Found by "piebeer".
983 - Bridge authorities no longer crash on SIGHUP when they try to
984 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
988 - Log less aggressively about circuit timeout changes, and improve
989 some other circuit timeout messages. Resolves bug 2004.
990 - Log a little more clearly about the times at which we're no longer
991 accepting new connections. Resolves bug 2181.
992 - Reject attempts at the client side to open connections to private
993 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
994 a randomly chosen exit node. Attempts to do so are always
995 ill-defined, generally prevented by exit policies, and usually
996 in error. This will also help to detect loops in transparent
997 proxy configurations. You can disable this feature by setting
998 "ClientRejectInternalAddresses 0" in your torrc.
999 - Always treat failure to allocate an RSA key as an unrecoverable
1001 - Update to the March 1 2011 Maxmind GeoLite Country database.
1003 o Minor features (log subsystem):
1004 - Add documentation for configuring logging at different severities in
1005 different log domains. We've had this feature since 0.2.1.1-alpha,
1006 but for some reason it never made it into the manpage. Fixes
1008 - Make it simpler to specify "All log domains except for A and B".
1009 Previously you needed to say "[*,~A,~B]". Now you can just say
1011 - Add a "LogMessageDomains 1" option to include the domains of log
1012 messages along with the messages. Without this, there's no way
1013 to use log domains without reading the source or doing a lot
1016 o Packaging changes:
1017 - Stop shipping the Tor specs files and development proposal documents
1018 in the tarball. They are now in a separate git repository at
1019 git://git.torproject.org/torspec.git
1022 Changes in version 0.2.2.22-alpha - 2011-01-25
1023 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
1024 main other change is a slight tweak to Tor's TLS handshake that makes
1025 relays and bridges that run this new version reachable from Iran again.
1026 We don't expect this tweak will win the arms race long-term, but it
1027 will buy us a bit more time until we roll out a better solution.
1030 - Fix a bounds-checking error that could allow an attacker to
1031 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
1033 - Don't assert when changing from bridge to relay or vice versa
1034 via the controller. The assert happened because we didn't properly
1035 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
1036 bug 2433. Reported by bastik.
1039 - Adjust our TLS Diffie-Hellman parameters to match those used by
1041 - Provide a log message stating which geoip file we're parsing
1042 instead of just stating that we're parsing the geoip file.
1043 Implements ticket 2432.
1046 - Check for and reject overly long directory certificates and
1047 directory tokens before they have a chance to hit any assertions.
1048 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
1051 Changes in version 0.2.2.21-alpha - 2011-01-15
1052 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
1053 continues our recent code security audit work. The main fix resolves
1054 a remote heap overflow vulnerability that can allow remote code
1055 execution (CVE-2011-0427). Other fixes address a variety of assert
1056 and crash bugs, most of which we think are hard to exploit remotely.
1058 o Major bugfixes (security), also included in 0.2.1.29:
1059 - Fix a heap overflow bug where an adversary could cause heap
1060 corruption. This bug probably allows remote code execution
1061 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
1063 - Prevent a denial-of-service attack by disallowing any
1064 zlib-compressed data whose compression factor is implausibly
1065 high. Fixes part of bug 2324; reported by "doorss".
1066 - Zero out a few more keys in memory before freeing them. Fixes
1067 bug 2384 and part of bug 2385. These key instances found by
1068 "cypherpunks", based on Andrew Case's report about being able
1069 to find sensitive data in Tor's memory space if you have enough
1070 permissions. Bugfix on 0.0.2pre9.
1072 o Major bugfixes (crashes), also included in 0.2.1.29:
1073 - Prevent calls to Libevent from inside Libevent log handlers.
1074 This had potential to cause a nasty set of crashes, especially
1075 if running Libevent with debug logging enabled, and running
1076 Tor with a controller watching for low-severity log messages.
1077 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
1078 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
1079 underflow errors there too. Fixes the other part of bug 2324.
1080 - Fix a bug where we would assert if we ever had a
1081 cached-descriptors.new file (or another file read directly into
1082 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
1083 on 0.2.1.25. Found by doorss.
1084 - Fix some potential asserts and parsing issues with grossly
1085 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
1088 o Minor bugfixes (other), also included in 0.2.1.29:
1089 - Fix a bug with handling misformed replies to reverse DNS lookup
1090 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
1091 bug reported by doorss.
1092 - Fix compilation on mingw when a pthreads compatibility library
1093 has been installed. (We don't want to use it, so we shouldn't
1094 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
1095 - Fix a bug where we would declare that we had run out of virtual
1096 addresses when the address space was only half-exhausted. Bugfix
1098 - Correctly handle the case where AutomapHostsOnResolve is set but
1099 no virtual addresses are available. Fixes bug 2328; bugfix on
1100 0.1.2.1-alpha. Bug found by doorss.
1101 - Correctly handle wrapping around when we run out of virtual
1102 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
1104 o Minor features, also included in 0.2.1.29:
1105 - Update to the January 1 2011 Maxmind GeoLite Country database.
1106 - Introduce output size checks on all of our decryption functions.
1108 o Build changes, also included in 0.2.1.29:
1109 - Tor does not build packages correctly with Automake 1.6 and earlier;
1110 added a check to Makefile.am to make sure that we're building with
1111 Automake 1.7 or later.
1112 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
1113 because we built it with a too-old version of automake. Thus that
1114 release broke ./configure --enable-openbsd-malloc, which is popular
1115 among really fast exit relays on Linux.
1117 o Major bugfixes, new in 0.2.2.21-alpha:
1118 - Prevent crash/heap corruption when the cbtnummodes consensus
1119 parameter is set to 0 or large values. Fixes bug 2317; bugfix
1122 o Major features, new in 0.2.2.21-alpha:
1123 - Introduce minimum/maximum values that clients will believe
1124 from the consensus. Now we'll have a better chance to avoid crashes
1125 or worse when a consensus param has a weird value.
1127 o Minor features, new in 0.2.2.21-alpha:
1128 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
1129 used on bridges, and it makes bridge scanning somewhat easier.
1130 - If writing the state file to disk fails, wait up to an hour before
1131 retrying again, rather than trying again each second. Fixes bug
1132 2346; bugfix on Tor 0.1.1.3-alpha.
1133 - Make Libevent log messages get delivered to controllers later,
1134 and not from inside the Libevent log handler. This prevents unsafe
1135 reentrant Libevent calls while still letting the log messages
1137 - Detect platforms that brokenly use a signed size_t, and refuse to
1138 build there. Found and analyzed by doorss and rransom.
1139 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
1142 o Minor bugfixes, new in 0.2.2.21-alpha:
1143 - Handle SOCKS messages longer than 128 bytes long correctly, rather
1144 than waiting forever for them to finish. Fixes bug 2330; bugfix
1145 on 0.2.0.16-alpha. Found by doorss.
1146 - Add assertions to check for overflow in arguments to
1147 base32_encode() and base32_decode(); fix a signed-unsigned
1148 comparison there too. These bugs are not actually reachable in Tor,
1149 but it's good to prevent future errors too. Found by doorss.
1150 - Correctly detect failures to create DNS requests when using Libevent
1151 versions before v2. (Before Libevent 2, we used our own evdns
1152 implementation. Its return values for Libevent's evdns_resolve_*()
1153 functions are not consistent with those from Libevent.) Fixes bug
1154 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
1156 o Documentation, new in 0.2.2.21-alpha:
1157 - Document the default socks host and port (127.0.0.1:9050) for
1161 Changes in version 0.2.1.29 - 2011-01-15
1162 Tor 0.2.1.29 continues our recent code security audit work. The main
1163 fix resolves a remote heap overflow vulnerability that can allow remote
1164 code execution. Other fixes address a variety of assert and crash bugs,
1165 most of which we think are hard to exploit remotely.
1167 o Major bugfixes (security):
1168 - Fix a heap overflow bug where an adversary could cause heap
1169 corruption. This bug probably allows remote code execution
1170 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
1172 - Prevent a denial-of-service attack by disallowing any
1173 zlib-compressed data whose compression factor is implausibly
1174 high. Fixes part of bug 2324; reported by "doorss".
1175 - Zero out a few more keys in memory before freeing them. Fixes
1176 bug 2384 and part of bug 2385. These key instances found by
1177 "cypherpunks", based on Andrew Case's report about being able
1178 to find sensitive data in Tor's memory space if you have enough
1179 permissions. Bugfix on 0.0.2pre9.
1181 o Major bugfixes (crashes):
1182 - Prevent calls to Libevent from inside Libevent log handlers.
1183 This had potential to cause a nasty set of crashes, especially
1184 if running Libevent with debug logging enabled, and running
1185 Tor with a controller watching for low-severity log messages.
1186 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
1187 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
1188 underflow errors there too. Fixes the other part of bug 2324.
1189 - Fix a bug where we would assert if we ever had a
1190 cached-descriptors.new file (or another file read directly into
1191 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
1192 on 0.2.1.25. Found by doorss.
1193 - Fix some potential asserts and parsing issues with grossly
1194 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
1197 o Minor bugfixes (other):
1198 - Fix a bug with handling misformed replies to reverse DNS lookup
1199 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
1200 bug reported by doorss.
1201 - Fix compilation on mingw when a pthreads compatibility library
1202 has been installed. (We don't want to use it, so we shouldn't
1203 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
1204 - Fix a bug where we would declare that we had run out of virtual
1205 addresses when the address space was only half-exhausted. Bugfix
1207 - Correctly handle the case where AutomapHostsOnResolve is set but
1208 no virtual addresses are available. Fixes bug 2328; bugfix on
1209 0.1.2.1-alpha. Bug found by doorss.
1210 - Correctly handle wrapping around to when we run out of virtual
1211 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
1212 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
1213 because we built it with a too-old version of automake. Thus that
1214 release broke ./configure --enable-openbsd-malloc, which is popular
1215 among really fast exit relays on Linux.
1218 - Update to the January 1 2011 Maxmind GeoLite Country database.
1219 - Introduce output size checks on all of our decryption functions.
1222 - Tor does not build packages correctly with Automake 1.6 and earlier;
1223 added a check to Makefile.am to make sure that we're building with
1224 Automake 1.7 or later.
1227 Changes in version 0.2.2.20-alpha - 2010-12-17
1228 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
1229 exploitable bugs. We also fix a variety of other significant bugs,
1230 change the IP address for one of our directory authorities, and update
1231 the minimum version that Tor relays must run to join the network.
1234 - Fix a remotely exploitable bug that could be used to crash instances
1235 of Tor remotely by overflowing on the heap. Remote-code execution
1236 hasn't been confirmed, but can't be ruled out. Everyone should
1237 upgrade. Bugfix on the 0.1.1 series and later.
1238 - Fix a bug that could break accounting on 64-bit systems with large
1239 time_t values, making them hibernate for impossibly long intervals.
1240 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
1241 - Fix a logic error in directory_fetches_from_authorities() that
1242 would cause all _non_-exits refusing single-hop-like circuits
1243 to fetch from authorities, when we wanted to have _exits_ fetch
1244 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
1246 - Fix a stream fairness bug that would cause newer streams on a given
1247 circuit to get preference when reading bytes from the origin or
1248 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
1249 introduced before the first Tor release, in svn revision r152.
1251 o Directory authority changes:
1252 - Change IP address and ports for gabelmoo (v3 directory authority).
1255 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
1256 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
1257 - Fix an off-by-one error in calculating some controller command
1258 argument lengths. Fortunately, this mistake is harmless since
1259 the controller code does redundant NUL termination too. Found by
1260 boboper. Bugfix on 0.1.1.1-alpha.
1261 - Do not dereference NULL if a bridge fails to build its
1262 extra-info descriptor. Found by an anonymous commenter on
1263 Trac. Bugfix on 0.2.2.19-alpha.
1266 - Update to the December 1 2010 Maxmind GeoLite Country database.
1267 - Directory authorities now reject relays running any versions of
1268 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
1269 known bugs that keep RELAY_EARLY cells from working on rendezvous
1270 circuits. Followup to fix for bug 2081.
1271 - Directory authorities now reject relays running any version of Tor
1272 older than 0.2.0.26-rc. That version is the earliest that fetches
1273 current directory information correctly. Fixes bug 2156.
1274 - Report only the top 10 ports in exit-port stats in order not to
1275 exceed the maximum extra-info descriptor length of 50 KB. Implements
1279 Changes in version 0.2.1.28 - 2010-12-17
1280 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
1281 exploitable bugs. We also took this opportunity to change the IP address
1282 for one of our directory authorities, and to update the geoip database
1286 - Fix a remotely exploitable bug that could be used to crash instances
1287 of Tor remotely by overflowing on the heap. Remote-code execution
1288 hasn't been confirmed, but can't be ruled out. Everyone should
1289 upgrade. Bugfix on the 0.1.1 series and later.
1291 o Directory authority changes:
1292 - Change IP address and ports for gabelmoo (v3 directory authority).
1295 - Update to the December 1 2010 Maxmind GeoLite Country database.
1298 Changes in version 0.2.1.27 - 2010-11-23
1299 Yet another OpenSSL security patch broke its compatibility with Tor:
1300 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
1301 also took this opportunity to fix several crash bugs, integrate a new
1302 directory authority, and update the bundled GeoIP database.
1305 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
1306 No longer set the tlsext_host_name extension on server SSL objects;
1307 but continue to set it on client SSL objects. Our goal in setting
1308 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
1309 bugfix on 0.2.1.1-alpha.
1310 - Do not log messages to the controller while shrinking buffer
1311 freelists. Doing so would sometimes make the controller connection
1312 try to allocate a buffer chunk, which would mess up the internals
1313 of the freelist and cause an assertion failure. Fixes bug 1125;
1314 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
1315 - Learn our external IP address when we're a relay or bridge, even if
1316 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
1317 where we introduced bridge relays that don't need to publish to
1318 be useful. Fixes bug 2050.
1319 - Do even more to reject (and not just ignore) annotations on
1320 router descriptors received anywhere but from the cache. Previously
1321 we would ignore such annotations at first, but cache them to disk
1322 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
1323 - When you're using bridges and your network goes away and your
1324 bridges get marked as down, recover when you attempt a new socks
1325 connection (if the network is back), rather than waiting up to an
1326 hour to try fetching new descriptors for your bridges. Bugfix on
1327 0.2.0.3-alpha; fixes bug 1981.
1330 - Move to the November 2010 Maxmind GeoLite country db (rather
1331 than the June 2009 ip-to-country GeoIP db) for our statistics that
1332 count how many users relays are seeing from each country. Now we'll
1333 have more accurate data, especially for many African countries.
1335 o New directory authorities:
1336 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
1340 - Fix an assertion failure that could occur in directory caches or
1341 bridge users when using a very short voting interval on a testing
1342 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
1344 - Enforce multiplicity rules when parsing annotations. Bugfix on
1345 0.2.0.8-alpha. Found by piebeer.
1346 - Allow handshaking OR connections to take a full KeepalivePeriod
1347 seconds to handshake. Previously, we would close them after
1348 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
1349 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
1351 - When building with --enable-gcc-warnings on OpenBSD, disable
1352 warnings in system headers. This makes --enable-gcc-warnings
1353 pass on OpenBSD 4.8.
1356 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
1357 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
1358 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
1359 Servers can start sending this code when enough clients recognize
1360 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
1361 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
1362 Patch from mingw-san.
1365 - Remove the old debian/ directory from the main Tor distribution.
1366 The official Tor-for-debian git repository lives at the URL
1367 https://git.torproject.org/debian/tor.git
1368 - Stop shipping the old doc/website/ directory in the tarball. We
1369 changed the website format in late 2010, and what we shipped in
1370 0.2.1.26 really wasn't that useful anyway.
1373 Changes in version 0.2.2.19-alpha - 2010-11-22
1374 Yet another OpenSSL security patch broke its compatibility with Tor:
1375 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
1378 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
1379 No longer set the tlsext_host_name extension on server SSL objects;
1380 but continue to set it on client SSL objects. Our goal in setting
1381 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
1382 bugfix on 0.2.1.1-alpha.
1385 - Try harder not to exceed the maximum length of 50 KB when writing
1386 statistics to extra-info descriptors. This bug was triggered by very
1387 fast relays reporting exit-port, entry, and dirreq statistics.
1388 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
1389 - Publish a router descriptor even if generating an extra-info
1390 descriptor fails. Previously we would not publish a router
1391 descriptor without an extra-info descriptor; this can cause fast
1392 exit relays collecting exit-port statistics to drop from the
1393 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
1396 Changes in version 0.2.2.18-alpha - 2010-11-16
1397 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
1398 us lately, makes unpublished bridge relays able to detect their IP
1399 address, and fixes a wide variety of other bugs to get us much closer
1400 to a stable release.
1403 - Do even more to reject (and not just ignore) annotations on
1404 router descriptors received anywhere but from the cache. Previously
1405 we would ignore such annotations at first, but cache them to disk
1406 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
1407 - Do not log messages to the controller while shrinking buffer
1408 freelists. Doing so would sometimes make the controller connection
1409 try to allocate a buffer chunk, which would mess up the internals
1410 of the freelist and cause an assertion failure. Fixes bug 1125;
1411 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
1412 - Learn our external IP address when we're a relay or bridge, even if
1413 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
1414 where we introduced bridge relays that don't need to publish to
1415 be useful. Fixes bug 2050.
1416 - Maintain separate TLS contexts and certificates for incoming and
1417 outgoing connections in bridge relays. Previously we would use the
1418 same TLS contexts and certs for incoming and outgoing connections.
1419 Bugfix on 0.2.0.3-alpha; addresses bug 988.
1420 - Maintain separate identity keys for incoming and outgoing TLS
1421 contexts in bridge relays. Previously we would use the same
1422 identity keys for incoming and outgoing TLS contexts. Bugfix on
1423 0.2.0.3-alpha; addresses the other half of bug 988.
1424 - Avoid an assertion failure when we as an authority receive a
1425 duplicate upload of a router descriptor that we already have,
1426 but which we previously considered an obsolete descriptor.
1427 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
1428 - Avoid a crash bug triggered by looking at a dangling pointer while
1429 setting the network status consensus. Found by Robert Ransom.
1430 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
1431 - Fix a logic error where servers that _didn't_ act as exits would
1432 try to keep their server lists more aggressively up to date than
1433 exits, when it was supposed to be the other way around. Bugfix
1436 o Minor bugfixes (on Tor 0.2.1.x and earlier):
1437 - When we're trying to guess whether we know our IP address as
1438 a relay, we would log various ways that we failed to guess
1439 our address, but never log that we ended up guessing it
1440 successfully. Now add a log line to help confused and anxious
1441 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
1442 - Bring the logic that gathers routerinfos and assesses the
1443 acceptability of circuits into line. This prevents a Tor OP from
1444 getting locked in a cycle of choosing its local OR as an exit for a
1445 path (due to a .exit request) and then rejecting the circuit because
1446 its OR is not listed yet. It also prevents Tor clients from using an
1447 OR running in the same instance as an exit (due to a .exit request)
1448 if the OR does not meet the same requirements expected of an OR
1449 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
1450 - Correctly describe errors that occur when generating a TLS object.
1451 Previously we would attribute them to a failure while generating a
1452 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
1454 - Enforce multiplicity rules when parsing annotations. Bugfix on
1455 0.2.0.8-alpha. Found by piebeer.
1456 - Fix warnings that newer versions of autoconf produced during
1457 ./autogen.sh. These warnings appear to be harmless in our case,
1458 but they were extremely verbose. Fixes bug 2020.
1460 o Minor bugfixes (on Tor 0.2.2.x):
1461 - Enable protection of small arrays whenever we build with gcc
1462 hardening features, not only when also building with warnings
1463 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
1466 - Make hidden services work better in private Tor networks by not
1467 requiring any uptime to join the hidden service descriptor
1468 DHT. Implements ticket 2088.
1469 - Rate-limit the "your application is giving Tor only an IP address"
1470 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
1471 - When AllowSingleHopExits is set, print a warning to explain to the
1472 relay operator why most clients are avoiding her relay.
1473 - Update to the November 1 2010 Maxmind GeoLite Country database.
1475 o Code simplifications and refactoring:
1476 - When we fixed bug 1038 we had to put in a restriction not to send
1477 RELAY_EARLY cells on rend circuits. This was necessary as long
1478 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
1479 active. Now remove this obsolete check. Resolves bug 2081.
1480 - Some options used different conventions for uppercasing of acronyms
1481 when comparing manpage and source. Fix those in favor of the
1482 manpage, as it makes sense to capitalize acronyms.
1483 - Remove the torrc.complete file. It hasn't been kept up to date
1484 and users will have better luck checking out the manpage.
1485 - Remove the obsolete "NoPublish" option; it has been flagged
1486 as obsolete and has produced a warning since 0.1.1.18-rc.
1487 - Remove everything related to building the expert bundle for OS X.
1488 It has confused many users, doesn't work right on OS X 10.6,
1489 and is hard to get rid of once installed. Resolves bug 1274.
1492 Changes in version 0.2.2.17-alpha - 2010-09-30
1493 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
1494 to use one-hop circuits (which can put the exit relays at higher risk,
1495 plus unbalance the network); fixes a big bug in bandwidth accounting
1496 for relays that want to limit their monthly bandwidth use; fixes a
1497 big pile of bugs in how clients tolerate temporary network failure;
1498 and makes our adaptive circuit build timeout feature (which improves
1499 client performance if your network is fast while not breaking things
1500 if your network is slow) better handle bad networks.
1503 - Exit relays now try harder to block exit attempts from unknown
1504 relays, to make it harder for people to use them as one-hop proxies
1505 a la tortunnel. Controlled by the refuseunknownexits consensus
1506 parameter (currently enabled), or you can override it on your
1507 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
1509 o Major bugfixes (0.2.1.x and earlier):
1510 - Fix a bug in bandwidth accounting that could make us use twice
1511 the intended bandwidth when our interval start changes due to
1512 daylight saving time. Now we tolerate skew in stored vs computed
1513 interval starts: if the start of the period changes by no more than
1514 50% of the period's duration, we remember bytes that we transferred
1515 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
1516 - Always search the Windows system directory for system DLLs, and
1517 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
1518 - When you're using bridges and your network goes away and your
1519 bridges get marked as down, recover when you attempt a new socks
1520 connection (if the network is back), rather than waiting up to an
1521 hour to try fetching new descriptors for your bridges. Bugfix on
1522 0.2.0.3-alpha; fixes bug 1981.
1524 o Major bugfixes (on 0.2.2.x):
1525 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
1527 - Fix a segfault that could happen when operating a bridge relay with
1528 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
1529 - The consensus bandwidth-weights (used by clients to choose fast
1530 relays) entered an unexpected edge case in September where
1531 Exits were much scarcer than Guards, resulting in bad weight
1532 recommendations. Now we compute them using new constraints that
1533 should succeed in all cases. Also alter directory authorities to
1534 not include the bandwidth-weights line if they fail to produce
1535 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
1536 - When weighting bridges during path selection, we used to trust
1537 the bandwidths they provided in their descriptor, only capping them
1538 at 10MB/s. This turned out to be problematic for two reasons:
1539 Bridges could claim to handle a lot more traffic then they
1540 actually would, thus making more clients pick them and have a
1541 pretty effective DoS attack. The other issue is that new bridges
1542 that might not have a good estimate for their bw capacity yet
1543 would not get used at all unless no other bridges are available
1544 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
1546 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
1547 - Ignore cannibalized circuits when recording circuit build times.
1548 This should provide for a minor performance improvement for hidden
1549 service users using 0.2.2.14-alpha, and should remove two spurious
1550 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
1551 - Simplify the logic that causes us to decide if the network is
1552 unavailable for purposes of recording circuit build times. If we
1553 receive no cells whatsoever for the entire duration of a circuit's
1554 full measured lifetime, the network is probably down. Also ignore
1555 one-hop directory fetching circuit timeouts when calculating our
1556 circuit build times. These changes should hopefully reduce the
1557 cases where we see ridiculous circuit build timeouts for people
1558 with spotty wireless connections. Fixes part of bug 1772; bugfix
1560 - Prevent the circuit build timeout from becoming larger than
1561 the maximum build time we have ever seen. Also, prevent the time
1562 period for measurement circuits from becoming larger than twice that
1563 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
1566 - When we run out of directory information such that we can't build
1567 circuits, but then get enough that we can build circuits, log when
1568 we actually construct a circuit, so the user has a better chance of
1569 knowing what's going on. Fixes bug 1362.
1570 - Be more generous with how much bandwidth we'd use up (with
1571 accounting enabled) before entering "soft hibernation". Previously,
1572 we'd refuse new connections and circuits once we'd used up 95% of
1573 our allotment. Now, we use up 95% of our allotment, AND make sure
1574 that we have no more than 500MB (or 3 hours of expected traffic,
1575 whichever is lower) remaining before we enter soft hibernation.
1576 - If we've configured EntryNodes and our network goes away and/or all
1577 our entrynodes get marked down, optimistically retry them all when
1578 a new socks application request appears. Fixes bug 1882.
1579 - Add some more defensive programming for architectures that can't
1580 handle unaligned integer accesses. We don't know of any actual bugs
1581 right now, but that's the best time to fix them. Fixes bug 1943.
1582 - Support line continuations in the torrc config file. If a line
1583 ends with a single backslash character, the newline is ignored, and
1584 the configuration value is treated as continuing on the next line.
1587 o Minor bugfixes (on 0.2.1.x and earlier):
1588 - For bandwidth accounting, calculate our expected bandwidth rate
1589 based on the time during which we were active and not in
1590 soft-hibernation during the last interval. Previously, we were
1591 also considering the time spent in soft-hibernation. If this
1592 was a long time, we would wind up underestimating our bandwidth
1593 by a lot, and skewing our wakeup time towards the start of the
1594 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
1596 o Minor bugfixes (on 0.2.2.x):
1597 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
1598 which were disabled by the circuit build timeout changes in
1599 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
1600 - Make sure we don't warn about missing bandwidth weights when
1601 choosing bridges or other relays not in the consensus. Bugfix on
1602 0.2.2.10-alpha; fixes bug 1805.
1603 - In our logs, do not double-report signatures from unrecognized
1604 authorities both as "from unknown authority" and "not
1605 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
1608 Changes in version 0.2.2.16-alpha - 2010-09-17
1609 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
1610 evident at exit relays), and also continues to resolve all the little
1611 bugs that have been filling up trac lately.
1613 o Major bugfixes (stream-level fairness):
1614 - When receiving a circuit-level SENDME for a blocked circuit, try
1615 to package cells fairly from all the streams that had previously
1616 been blocked on that circuit. Previously, we had started with the
1617 oldest stream, and allowed each stream to potentially exhaust
1618 the circuit's package window. This gave older streams on any
1619 given circuit priority over newer ones. Fixes bug 1937. Detected
1620 originally by Camilo Viecco. This bug was introduced before the
1621 first Tor release, in svn commit r152: it is the new winner of
1622 the longest-lived bug prize.
1623 - When the exit relay got a circuit-level sendme cell, it started
1624 reading on the exit streams, even if had 500 cells queued in the
1625 circuit queue already, so the circuit queue just grew and grew in
1626 some cases. We fix this by not re-enabling reading on receipt of a
1627 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
1628 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
1630 - Newly created streams were allowed to read cells onto circuits,
1631 even if the circuit's cell queue was blocked and waiting to drain.
1632 This created potential unfairness, as older streams would be
1633 blocked, but newer streams would gladly fill the queue completely.
1634 We add code to detect this situation and prevent any stream from
1635 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
1639 - Update to the September 1 2010 Maxmind GeoLite Country database.
1640 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
1641 not. This would lead to a cookie that is still not group readable.
1642 Closes bug 1843. Suggested by katmagic.
1643 - When logging a rate-limited warning, we now mention how many messages
1644 got suppressed since the last warning.
1645 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
1646 do individual connection-level rate limiting of clients. The torrc
1647 config options with the same names trump the consensus params, if
1648 both are present. Replaces the old "bwconnrate" and "bwconnburst"
1649 consensus params which were broken from 0.2.2.7-alpha through
1650 0.2.2.14-alpha. Closes bug 1947.
1651 - When a router changes IP address or port, authorities now launch
1652 a new reachability test for it. Implements ticket 1899.
1653 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
1654 2 no signature, 4 required" messages about consensus signatures
1655 easier to read, and make sure they get logged at the same severity
1656 as the messages explaining which keys are which. Fixes bug 1290.
1657 - Don't warn when we have a consensus that we can't verify because
1658 of missing certificates, unless those certificates are ones
1659 that we have been trying and failing to download. Fixes bug 1145.
1660 - If you configure your bridge with a known identity fingerprint,
1661 and the bridge authority is unreachable (as it is in at least
1662 one country now), fall back to directly requesting the descriptor
1663 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
1665 - When building with --enable-gcc-warnings on OpenBSD, disable
1666 warnings in system headers. This makes --enable-gcc-warnings
1667 pass on OpenBSD 4.8.
1669 o Minor bugfixes (on 0.2.1.x and earlier):
1670 - Authorities will now attempt to download consensuses if their
1671 own efforts to make a live consensus have failed. This change
1672 means authorities that restart will fetch a valid consensus, and
1673 it means authorities that didn't agree with the current consensus
1674 will still fetch and serve it if it has enough signatures. Bugfix
1675 on 0.2.0.9-alpha; fixes bug 1300.
1676 - Ensure DNS requests launched by "RESOLVE" commands from the
1677 controller respect the __LeaveStreamsUnattached setconf options. The
1678 same goes for requests launched via DNSPort or transparent
1679 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
1680 - Allow handshaking OR connections to take a full KeepalivePeriod
1681 seconds to handshake. Previously, we would close them after
1682 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
1683 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
1685 - Rate-limit "Failed to hand off onionskin" warnings.
1686 - Never relay a cell for a circuit we have already destroyed.
1687 Between marking a circuit as closeable and finally closing it,
1688 it may have been possible for a few queued cells to get relayed,
1689 even though they would have been immediately dropped by the next
1690 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
1691 - Never queue a cell for a circuit that's already been marked
1693 - Never vote for a server as "Running" if we have a descriptor for
1694 it claiming to be hibernating, and that descriptor was published
1695 more recently than our last contact with the server. Bugfix on
1696 0.2.0.3-alpha; fixes bug 911.
1697 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
1700 o Minor bugfixes (on 0.2.2.x):
1701 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
1702 down if a directory fetch fails and you've configured either
1703 bridges or EntryNodes. The intent was to mark the relay as down
1704 _unless_ you're using bridges or EntryNodes, since if you are
1705 then you could quickly run out of entry points.
1706 - Fix the Windows directory-listing code. A bug introduced in
1707 0.2.2.14-alpha could make Windows directory servers forget to load
1708 some of their cached v2 networkstatus files.
1709 - Really allow clients to use relays as bridges. Fixes bug 1776;
1710 bugfix on 0.2.2.15-alpha.
1711 - Demote a warn to info that happens when the CellStatistics option
1712 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
1713 Reported by Moritz Bartl.
1714 - On Windows, build correctly either with or without Unicode support.
1715 This is necessary so that Tor can support fringe platforms like
1716 Windows 98 (which has no Unicode), or Windows CE (which has no
1717 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
1720 - Add a unit test for cross-platform directory-listing code.
1723 Changes in version 0.2.2.15-alpha - 2010-08-18
1724 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
1725 fixes a variety of other bugs that were preventing performance
1726 experiments from moving forward, fixes several bothersome memory leaks,
1727 and generally closes a lot of smaller bugs that have been filling up
1731 - Stop assigning the HSDir flag to relays that disable their
1732 DirPort (and thus will refuse to answer directory requests). This
1733 fix should dramatically improve the reachability of hidden services:
1734 hidden services and hidden service clients pick six HSDir relays
1735 to store and retrieve the hidden service descriptor, and currently
1736 about half of the HSDir relays will refuse to work. Bugfix on
1737 0.2.0.10-alpha; fixes part of bug 1693.
1738 - The PerConnBWRate and Burst config options, along with the
1739 bwconnrate and bwconnburst consensus params, initialized each conn's
1740 token bucket values only when the connection is established. Now we
1741 update them if the config options change, and update them every time
1742 we get a new consensus. Otherwise we can encounter an ugly edge
1743 case where we initialize an OR conn to client-level bandwidth,
1744 but then later the relay joins the consensus and we leave it
1745 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
1746 - Fix a regression that caused Tor to rebind its ports if it receives
1747 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
1750 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
1751 should give us approximately 40-50% more Guard-flagged nodes,
1752 improving the anonymity the Tor network can provide and also
1753 decreasing the dropoff in throughput that relays experience when
1754 they first get the Guard flag.
1755 - Allow enabling or disabling the *Statistics config options while
1759 - Update to the August 1 2010 Maxmind GeoLite Country database.
1760 - Have the controller interface give a more useful message than
1761 "Internal Error" in response to failed GETINFO requests.
1762 - Warn when the same option is provided more than once in a torrc
1763 file, on the command line, or in a single SETCONF statement, and
1764 the option is one that only accepts a single line. Closes bug 1384.
1765 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
1766 Patch from mingw-san.
1767 - Add support for the country code "{??}" in torrc options like
1768 ExcludeNodes, to indicate all routers of unknown country. Closes
1770 - Relays report the number of bytes spent on answering directory
1771 requests in extra-info descriptors similar to {read,write}-history.
1772 Implements enhancement 1790.
1774 o Minor bugfixes (on 0.2.1.x and earlier):
1775 - Complain if PublishServerDescriptor is given multiple arguments that
1776 include 0 or 1. This configuration will be rejected in the future.
1777 Bugfix on 0.2.0.1-alpha; closes bug 1107.
1778 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
1779 Bugfix on 0.2.0.13-alpha; closes bug 928.
1780 - Change "Application request when we're believed to be offline."
1781 notice to "Application request when we haven't used client
1782 functionality lately.", to clarify that it's not an error. Bugfix
1783 on 0.0.9.3; fixes bug 1222.
1784 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
1785 would return "551 Internal error" rather than "552 Unrecognized key
1786 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
1787 - Users can't configure a regular relay to be their bridge. It didn't
1788 work because when Tor fetched the bridge descriptor, it found
1789 that it already had it, and didn't realize that the purpose of the
1790 descriptor had changed. Now we replace routers with a purpose other
1791 than bridge with bridge descriptors when fetching them. Bugfix on
1792 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
1793 refetch the descriptor with router purpose 'general', disabling
1795 - Fix a rare bug in rend_fn unit tests: we would fail a test when
1796 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
1797 on 0.2.0.10-alpha; fixes bug 1808.
1798 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
1799 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
1800 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
1801 Servers can start sending this code when enough clients recognize
1802 it. Also update the spec to reflect this new reason. Bugfix on
1803 0.1.0.1-rc; fixes part of bug 1793.
1804 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
1805 when we switch from being a public relay to a bridge. Otherwise
1806 there will still be clients that see the relay in their consensus,
1807 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
1809 - Instead of giving an assertion failure on an internal mismatch
1810 on estimated freelist size, just log a BUG warning and try later.
1811 Mitigates but does not fix bug 1125.
1812 - Fix an assertion failure that could occur in caches or bridge users
1813 when using a very short voting interval on a testing network.
1814 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
1816 o Minor bugfixes (on 0.2.2.x):
1817 - Alter directory authorities to always consider Exit-flagged nodes
1818 as potential Guard nodes in their votes. The actual decision to
1819 use Exits as Guards is done in the consensus bandwidth weights.
1820 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
1821 - When the controller is reporting the purpose of circuits that
1822 didn't finish building before the circuit build timeout, it was
1823 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
1824 - Our libevent version parsing code couldn't handle versions like
1825 1.4.14b-stable and incorrectly warned the user about using an
1826 old and broken version of libevent. Treat 1.4.14b-stable like
1827 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
1829 - Don't use substitution references like $(VAR:MOD) when
1830 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
1831 '$(:x)' to 'x' rather than the empty string. This bites us in
1832 doc/ when configured with --disable-asciidoc. Bugfix on
1833 0.2.2.9-alpha; fixes bug 1773.
1834 - Remove a spurious hidden service server-side log notice about
1835 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
1837 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
1839 - Correctly report written bytes on linked connections. Found while
1840 implementing 1790. Bugfix on 0.2.2.4-alpha.
1841 - Fix three memory leaks: one in circuit_build_times_parse_state(),
1842 one in dirvote_add_signatures_to_pending_consensus(), and one every
1843 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
1844 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
1846 o Code simplifications and refactoring:
1847 - Take a first step towards making or.h smaller by splitting out
1848 function definitions for all source files in src/or/. Leave
1849 structures and defines in or.h for now.
1850 - Remove a bunch of unused function declarations as well as a block of
1851 #if 0'd code from the unit tests. Closes bug 1824.
1852 - New unit tests for exit-port history statistics; refactored exit
1853 statistics code to be more easily tested.
1854 - Remove the old debian/ directory from the main Tor distribution.
1855 The official Tor-for-debian git repository lives at the URL
1856 https://git.torproject.org/debian/tor.git
1859 Changes in version 0.2.2.14-alpha - 2010-07-12
1860 Tor 0.2.2.14-alpha greatly improves client-side handling of
1861 circuit build timeouts, which are used to estimate speed and improve
1862 performance. We also move to a much better GeoIP database, port Tor to
1863 Windows CE, introduce new compile flags that improve code security,
1864 add an eighth v3 directory authority, and address a lot of more
1868 - Tor directory authorities no longer crash when started with a
1869 cached-microdesc-consensus file in their data directory. Bugfix
1870 on 0.2.2.6-alpha; fixes bug 1532.
1871 - Treat an unset $HOME like an empty $HOME rather than triggering an
1872 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
1873 - Ignore negative and large circuit build timeout values that can
1874 happen during a suspend or hibernate. These values caused various
1875 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
1876 - Alter calculation of Pareto distribution parameter 'Xm' for
1877 Circuit Build Timeout learning to use the weighted average of the
1878 top N=3 modes (because we have three entry guards). Considering
1879 multiple modes should improve the timeout calculation in some cases,
1880 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
1882 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
1883 right censored distribution model. This approach improves over the
1884 synthetic timeout generation approach that was producing insanely
1885 high timeout values. Now we calculate build timeouts using truncated
1886 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
1887 - Do not close circuits that are under construction when they reach
1888 the circuit build timeout. Instead, leave them building (but do not
1889 use them) for up until the time corresponding to the 95th percentile
1890 on the Pareto CDF or 60 seconds, whichever is greater. This is done
1891 to provide better data for the new Pareto model. This percentile
1892 can be controlled by the consensus.
1895 - Move to the June 2010 Maxmind GeoLite country db (rather than the
1896 June 2009 ip-to-country GeoIP db) for our statistics that count
1897 how many users relays are seeing from each country. Now we have
1898 more accurate data for many African countries.
1899 - Port Tor to build and run correctly on Windows CE systems, using
1900 the wcecompat library. Contributed by Valerio Lupi.
1901 - New "--enable-gcc-hardening" ./configure flag (off by default)
1902 to turn on gcc compile time hardening options. It ensures
1903 that signed ints have defined behavior (-fwrapv), enables
1904 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
1905 with canaries (-fstack-protector-all), turns on ASLR protection if
1906 supported by the kernel (-fPIE, -pie), and adds additional security
1907 related warnings. Verified to work on Mac OS X and Debian Lenny.
1908 - New "--enable-linker-hardening" ./configure flag (off by default)
1909 to turn on ELF specific hardening features (relro, now). This does
1910 not work with Mac OS X or any other non-ELF binary format.
1912 o New directory authorities:
1913 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
1917 - New config option "WarnUnsafeSocks 0" disables the warning that
1918 occurs whenever Tor receives only an IP address instead of a
1919 hostname. Setups that do DNS locally over Tor are fine, and we
1920 shouldn't spam the logs in that case.
1921 - Convert the HACKING file to asciidoc, and add a few new sections
1922 to it, explaining how we use Git, how we make changelogs, and
1923 what should go in a patch.
1924 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
1925 event, to give information on the current rate of circuit timeouts
1926 over our stored history.
1927 - Add ability to disable circuit build time learning via consensus
1928 parameter and via a LearnCircuitBuildTimeout config option. Also
1929 automatically disable circuit build time calculation if we are
1930 either a AuthoritativeDirectory, or if we fail to write our state
1931 file. Fixes bug 1296.
1932 - More gracefully handle corrupt state files, removing asserts
1933 in favor of saving a backup and resetting state.
1934 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
1938 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
1940 - When a2x fails, mention that the user could disable manpages instead
1941 of trying to fix their asciidoc installation.
1942 - Where available, use Libevent 2.0's periodic timers so that our
1943 once-per-second cleanup code gets called even more closely to
1944 once per second than it would otherwise. Fixes bug 943.
1945 - If you run a bridge that listens on multiple IP addresses, and
1946 some user configures a bridge address that uses a different IP
1947 address than your bridge writes in its router descriptor, and the
1948 user doesn't specify an identity key, their Tor would discard the
1949 descriptor because "it isn't one of our configured bridges", and
1950 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
1951 Bugfix on 0.2.0.3-alpha.
1952 - If OpenSSL fails to make a duplicate of a private or public key, log
1953 an error message and try to exit cleanly. May help with debugging
1954 if bug 1209 ever remanifests.
1955 - Save a couple bytes in memory allocation every time we escape
1956 certain characters in a string. Patch from Florian Zumbiehl.
1957 - Make it explicit that we don't cannibalize one-hop circuits. This
1958 happens in the wild, but doesn't turn out to be a problem because
1959 we fortunately don't use those circuits. Many thanks to outofwords
1960 for the initial analysis and to swissknife who confirmed that
1961 two-hop circuits are actually created.
1962 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
1963 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
1964 - Eliminate a case where a circuit build time warning was displayed
1965 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
1968 Changes in version 0.2.1.26 - 2010-05-02
1969 Tor 0.2.1.26 addresses the recent connection and memory overload
1970 problems we've been seeing on relays, especially relays with their
1971 DirPort open. If your relay has been crashing, or you turned it off
1972 because it used too many resources, give this release a try.
1974 This release also fixes yet another instance of broken OpenSSL libraries
1975 that was causing some relays to drop out of the consensus.
1978 - Teach relays to defend themselves from connection overload. Relays
1979 now close idle circuits early if it looks like they were intended
1980 for directory fetches. Relays are also more aggressive about closing
1981 TLS connections that have no circuits on them. Such circuits are
1982 unlikely to be re-used, and tens of thousands of them were piling
1983 up at the fast relays, causing the relays to run out of sockets
1984 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
1985 their directory fetches over TLS).
1986 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
1987 that claim to be earlier than 0.9.8m, but which have in reality
1988 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
1989 behavior. Possible fix for some cases of bug 1346.
1990 - Directory mirrors were fetching relay descriptors only from v2
1991 directory authorities, rather than v3 authorities like they should.
1992 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
1993 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
1996 - Finally get rid of the deprecated and now harmful notion of "clique
1997 mode", where directory authorities maintain TLS connections to
2001 - In the util/threads test, no longer free the test_mutex before all
2002 worker threads have finished. Bugfix on 0.2.1.6-alpha.
2003 - The master thread could starve the worker threads quite badly on
2004 certain systems, causing them to run only partially in the allowed
2005 window. This resulted in test failures. Now the master thread sleeps
2006 occasionally for a few microseconds while the two worker-threads
2007 compete for the mutex. Bugfix on 0.2.0.1-alpha.
2010 Changes in version 0.2.2.13-alpha - 2010-04-24
2011 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
2012 problems we've been seeing on relays, especially relays with their
2013 DirPort open. If your relay has been crashing, or you turned it off
2014 because it used too many resources, give this release a try.
2017 - Teach relays to defend themselves from connection overload. Relays
2018 now close idle circuits early if it looks like they were intended
2019 for directory fetches. Relays are also more aggressive about closing
2020 TLS connections that have no circuits on them. Such circuits are
2021 unlikely to be re-used, and tens of thousands of them were piling
2022 up at the fast relays, causing the relays to run out of sockets
2023 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
2024 their directory fetches over TLS).
2027 - Finally get rid of the deprecated and now harmful notion of "clique
2028 mode", where directory authorities maintain TLS connections to
2030 - Directory authorities now do an immediate reachability check as soon
2031 as they hear about a new relay. This change should slightly reduce
2032 the time between setting up a relay and getting listed as running
2033 in the consensus. It should also improve the time between setting
2034 up a bridge and seeing use by bridge users.
2035 - Directory authorities no longer launch a TLS connection to every
2036 relay as they startup. Now that we have 2k+ descriptors cached,
2037 the resulting network hiccup is becoming a burden. Besides,
2038 authorities already avoid voting about Running for the first half
2039 hour of their uptime.
2042 Changes in version 0.2.2.12-alpha - 2010-04-20
2043 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
2044 handle and vote on descriptors. It was causing relays to drop out of
2048 - Many relays have been falling out of the consensus lately because
2049 not enough authorities know about their descriptor for them to get
2050 a majority of votes. When we deprecated the v2 directory protocol,
2051 we got rid of the only way that v3 authorities can hear from each
2052 other about other descriptors. Now authorities examine every v3
2053 vote for new descriptors, and fetch them from that authority. Bugfix
2055 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
2056 and a warning in or.h related to bandwidth_weight_rule_t that
2057 prevented clean compile on OS X. Fixes bug 1363; bugfix on
2059 - Fix a segfault on relays when DirReqStatistics is enabled
2060 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
2064 - Demote a confusing TLS warning that relay operators might get when
2065 someone tries to talk to their OrPort. It is neither the operator's
2066 fault nor can they do anything about it. Fixes bug 1364; bugfix
2070 Changes in version 0.2.2.11-alpha - 2010-04-15
2071 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
2072 libraries that was causing some relays to drop out of the consensus.
2075 - Directory mirrors were fetching relay descriptors only from v2
2076 directory authorities, rather than v3 authorities like they should.
2077 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
2078 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
2079 - Fix a parsing error that made every possible value of
2080 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
2081 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
2082 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
2083 about the option without breaking older ones.
2084 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
2085 that claim to be earlier than 0.9.8m, but which have in reality
2086 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
2087 behavior. Possible fix for some cases of bug 1346.
2090 - Experiment with a more aggressive approach to preventing clients
2091 from making one-hop exit streams. Exit relays who want to try it
2092 out can set "RefuseUnknownExits 1" in their torrc, and then look
2093 for "Attempt by %s to open a stream" log messages. Let us know
2095 - Add support for statically linking zlib by specifying
2096 --enable-static-zlib, to go with our support for statically linking
2097 openssl and libevent. Resolves bug 1358.
2100 - Fix a segfault that happens whenever a Tor client that is using
2101 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
2103 - When we cleaned up the contrib/tor-exit-notice.html file, we left
2104 out the first line. Fixes bug 1295.
2105 - When building the manpage from a tarball, we required asciidoc, but
2106 the asciidoc -> roff/html conversion was already done for the
2107 tarball. Make 'make' complain only when we need asciidoc (either
2108 because we're compiling directly from git, or because we altered
2109 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
2110 - When none of the directory authorities vote on any params, Tor
2111 segfaulted when trying to make the consensus from the votes. We
2112 didn't trigger the bug in practice, because authorities do include
2113 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
2116 - In the util/threads test, no longer free the test_mutex before all
2117 worker threads have finished. Bugfix on 0.2.1.6-alpha.
2118 - The master thread could starve the worker threads quite badly on
2119 certain systems, causing them to run only partially in the allowed
2120 window. This resulted in test failures. Now the master thread sleeps
2121 occasionally for a few microseconds while the two worker-threads
2122 compete for the mutex. Bugfix on 0.2.0.1-alpha.
2125 Changes in version 0.2.2.10-alpha - 2010-03-07
2126 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
2127 could prevent relays from guessing their IP address correctly. It also
2128 starts the groundwork for another client-side performance boost, since
2129 currently we're not making efficient use of relays that have both the
2130 Guard flag and the Exit flag.
2133 - Fix a regression from our patch for bug 1244 that caused relays
2134 to guess their IP address incorrectly if they didn't set Address
2135 in their torrc and/or their address fails to resolve. Bugfix on
2136 0.2.2.9-alpha; fixes bug 1269.
2138 o Major features (performance):
2139 - Directory authorities now compute consensus weightings that instruct
2140 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
2141 and no flag. Clients that use these weightings will distribute
2142 network load more evenly across these different relay types. The
2143 weightings are in the consensus so we can change them globally in
2144 the future. Extra thanks to "outofwords" for finding some nasty
2145 security bugs in the first implementation of this feature.
2147 o Minor features (performance):
2148 - Always perform router selections using weighted relay bandwidth,
2149 even if we don't need a high capacity circuit at the time. Non-fast
2150 circuits now only differ from fast ones in that they can use relays
2151 not marked with the Fast flag. This "feature" could turn out to
2152 be a horrible bug; we should investigate more before it goes into
2156 - Allow disabling building of the manpages. Skipping the manpage
2157 speeds up the build considerably.
2159 o Minor bugfixes (on 0.2.2.x):
2160 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
2161 Bugfix on 0.2.2.9-alpha.
2162 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
2163 config option. Bugfix on 0.2.2.7-alpha.
2164 - Ship the asciidoc-helper file in the tarball, so that people can
2165 build from source if they want to, and touching the .1.txt files
2166 doesn't break the build. Bugfix on 0.2.2.9-alpha.
2168 o Minor bugfixes (on 0.2.1.x or earlier):
2169 - Fix a dereference-then-NULL-check sequence when publishing
2170 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
2172 - Fix another dereference-then-NULL-check sequence. Bugfix on
2173 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
2174 - Make sure we treat potentially not NUL-terminated strings correctly.
2175 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
2177 o Code simplifications and refactoring:
2178 - Fix some urls in the exit notice file and make it XHTML1.1 strict
2179 compliant. Based on a patch from Christian Kujau.
2180 - Don't use sed in asciidoc-helper anymore.
2181 - Make the build process fail if asciidoc cannot be found and
2182 building with asciidoc isn't disabled.
2185 Changes in version 0.2.2.9-alpha - 2010-02-22
2186 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
2187 location of a directory authority, and cleans up a bunch of small bugs.
2189 o Directory authority changes:
2190 - Change IP address for dannenberg (v3 directory authority), and
2191 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
2192 service directory authority) from the list.
2195 - Make Tor work again on the latest OS X: when deciding whether to
2196 use strange flags to turn TLS renegotiation on, detect the OpenSSL
2197 version at run-time, not compile time. We need to do this because
2198 Apple doesn't update its dev-tools headers when it updates its
2199 libraries in a security patch.
2200 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
2201 that could happen on 32-bit platforms with 64-bit time_t. Also fix
2202 a memory leak when requesting a hidden service descriptor we've
2203 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
2205 - Authorities could be tricked into giving out the Exit flag to relays
2206 that didn't allow exiting to any ports. This bug could screw
2207 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
2208 1238. Bug discovered by Martin Kowalczyk.
2209 - When freeing a session key, zero it out completely. We only zeroed
2210 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
2211 patched by ekir. Fixes bug 1254.
2214 - Fix static compilation by listing the openssl libraries in the right
2215 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
2216 - Resume handling .exit hostnames in a special way: originally we
2217 stripped the .exit part and used the requested exit relay. In
2218 0.2.2.1-alpha we stopped treating them in any special way, meaning
2219 if you use a .exit address then Tor will pass it on to the exit
2220 relay. Now we reject the .exit stream outright, since that behavior
2221 might be more expected by the user. Found and diagnosed by Scott
2222 Bennett and Downie on or-talk.
2223 - Don't spam the controller with events when we have no file
2224 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
2225 for log messages was already solved from bug 748.)
2226 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
2228 - Make the DNSPort option work with libevent 2.x. Don't alter the
2229 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
2230 - Emit a GUARD DROPPED controller event for a case we missed.
2231 - Make more fields in the controller protocol case-insensitive, since
2232 control-spec.txt said they were.
2233 - Refactor resolve_my_address() to not use gethostbyname() anymore.
2234 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
2235 - Fix a spec conformance issue: the network-status-version token
2236 must be the first token in a v3 consensus or vote. Discovered by
2237 parakeep. Bugfix on 0.2.0.3-alpha.
2239 o Code simplifications and refactoring:
2240 - Generate our manpage and HTML documentation using Asciidoc. This
2241 change should make it easier to maintain the documentation, and
2243 - Remove the --enable-iphone option. According to reports from Marco
2244 Bonetti, Tor builds fine without any special tweaking on recent
2245 iPhone SDK versions.
2246 - Removed some unnecessary files from the source distribution. The
2247 AUTHORS file has now been merged into the people page on the
2248 website. The roadmaps and design doc can now be found in the
2249 projects directory in svn.
2250 - Enabled various circuit build timeout constants to be controlled
2251 by consensus parameters. Also set better defaults for these
2252 parameters based on experimentation on broadband and simulated
2256 - The 'EXTENDCIRCUIT' control port command can now be used with
2257 a circ id of 0 and no path. This feature will cause Tor to build
2258 a new 'fast' general purpose circuit using its own path selection
2260 - Added a BUILDTIMEOUT_SET controller event to describe changes
2261 to the circuit build timeout.
2262 - Future-proof the controller protocol a bit by ignoring keyword
2263 arguments we do not recognize.
2264 - Expand homedirs passed to tor-checkkey. This should silence a
2265 coverity complaint about passing a user-supplied string into
2266 open() without checking it.
2269 Changes in version 0.2.1.25 - 2010-03-16
2270 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
2271 prevent relays from guessing their IP address correctly. It also fixes
2272 several minor potential security bugs.
2275 - Fix a regression from our patch for bug 1244 that caused relays
2276 to guess their IP address incorrectly if they didn't set Address
2277 in their torrc and/or their address fails to resolve. Bugfix on
2278 0.2.1.23; fixes bug 1269.
2279 - When freeing a session key, zero it out completely. We only zeroed
2280 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
2281 patched by ekir. Fixes bug 1254.
2284 - Fix a dereference-then-NULL-check sequence when publishing
2285 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
2287 - Fix another dereference-then-NULL-check sequence. Bugfix on
2288 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
2289 - Make sure we treat potentially not NUL-terminated strings correctly.
2290 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
2294 Changes in version 0.2.1.24 - 2010-02-21
2295 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
2299 - Work correctly out-of-the-box with even more vendor-patched versions
2300 of OpenSSL. In particular, make it so Debian and OS X don't need
2301 customized patches to run/build.
2304 Changes in version 0.2.1.23 - 2010-02-13
2305 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
2306 again on the latest OS X, and updates the location of a directory
2309 o Major bugfixes (performance):
2310 - We were selecting our guards uniformly at random, and then weighting
2311 which of our guards we'd use uniformly at random. This imbalance
2312 meant that Tor clients were severely limited on throughput (and
2313 probably latency too) by the first hop in their circuit. Now we
2314 select guards weighted by currently advertised bandwidth. We also
2315 automatically discard guards picked using the old algorithm. Fixes
2316 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
2319 - Make Tor work again on the latest OS X: when deciding whether to
2320 use strange flags to turn TLS renegotiation on, detect the OpenSSL
2321 version at run-time, not compile time. We need to do this because
2322 Apple doesn't update its dev-tools headers when it updates its
2323 libraries in a security patch.
2324 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
2325 that could happen on 32-bit platforms with 64-bit time_t. Also fix
2326 a memory leak when requesting a hidden service descriptor we've
2327 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
2330 o Directory authority changes:
2331 - Change IP address for dannenberg (v3 directory authority), and
2332 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
2333 service directory authority) from the list.
2336 - Refactor resolve_my_address() to not use gethostbyname() anymore.
2337 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
2340 - Avoid a mad rush at the beginning of each month when each client
2341 rotates half of its guards. Instead we spread the rotation out
2342 throughout the month, but we still avoid leaving a precise timestamp
2343 in the state file about when we first picked the guard. Improves
2344 over the behavior introduced in 0.1.2.17.
2347 Changes in version 0.2.2.8-alpha - 2010-01-26
2348 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
2349 causing bridge relays to disappear. If you're running a bridge,
2353 - Fix a memory corruption bug on bridges that occured during the
2354 inclusion of stats data in extra-info descriptors. Also fix the
2355 interface for geoip_get_bridge_stats* to prevent similar bugs in
2356 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
2357 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
2360 - Ignore OutboundBindAddress when connecting to localhost.
2361 Connections to localhost need to come _from_ localhost, or else
2362 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
2366 Changes in version 0.2.2.7-alpha - 2010-01-19
2367 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
2368 as laying the groundwork for further relay-side performance fixes. It
2369 also starts cleaning up client behavior with respect to the EntryNodes,
2370 ExitNodes, and StrictNodes config options.
2372 This release also rotates two directory authority keys, due to a
2373 security breach of some of the Torproject servers.
2375 o Directory authority changes:
2376 - Rotate keys (both v3 identity and relay identity) for moria1
2379 o Major features (performance):
2380 - We were selecting our guards uniformly at random, and then weighting
2381 which of our guards we'd use uniformly at random. This imbalance
2382 meant that Tor clients were severely limited on throughput (and
2383 probably latency too) by the first hop in their circuit. Now we
2384 select guards weighted by currently advertised bandwidth. We also
2385 automatically discard guards picked using the old algorithm. Fixes
2386 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
2387 - When choosing which cells to relay first, relays can now favor
2388 circuits that have been quiet recently, to provide lower latency
2389 for low-volume circuits. By default, relays enable or disable this
2390 feature based on a setting in the consensus. You can override
2391 this default by using the new "CircuitPriorityHalflife" config
2392 option. Design and code by Ian Goldberg, Can Tang, and Chris
2394 - Add separate per-conn write limiting to go with the per-conn read
2395 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
2396 but never per-conn write limits.
2397 - New consensus params "bwconnrate" and "bwconnburst" to let us
2398 rate-limit client connections as they enter the network. It's
2399 controlled in the consensus so we can turn it on and off for
2400 experiments. It's starting out off. Based on proposal 163.
2402 o Major features (relay selection options):
2403 - Switch to a StrictNodes config option, rather than the previous
2404 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
2405 "StrictExcludeNodes" option.
2406 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
2407 change during a config reload, mark and discard all our origin
2408 circuits. This fix should address edge cases where we change the
2409 config options and but then choose a circuit that we created before
2411 - If EntryNodes or ExitNodes are set, be more willing to use an
2412 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
2414 - Make EntryNodes config option much more aggressive even when
2415 StrictNodes is not set. Before it would prepend your requested
2416 entrynodes to your list of guard nodes, but feel free to use others
2417 after that. Now it chooses only from your EntryNodes if any of
2418 those are available, and only falls back to others if a) they're
2419 all down and b) StrictNodes is not set.
2420 - Now we refresh your entry guards from EntryNodes at each consensus
2421 fetch -- rather than just at startup and then they slowly rot as
2422 the network changes.
2425 - Stop bridge directory authorities from answering dbg-stability.txt
2426 directory queries, which would let people fetch a list of all
2427 bridge identities they track. Bugfix on 0.2.1.6-alpha.
2430 - Log a notice when we get a new control connection. Now it's easier
2431 for security-conscious users to recognize when a local application
2432 is knocking on their controller door. Suggested by bug 1196.
2433 - New config option "CircuitStreamTimeout" to override our internal
2434 timeout schedule for how many seconds until we detach a stream from
2435 a circuit and try a new circuit. If your network is particularly
2436 slow, you might want to set this to a number like 60.
2437 - New controller command "getinfo config-text". It returns the
2438 contents that Tor would write if you send it a SAVECONF command,
2439 so the controller can write the file to disk itself.
2440 - New options for SafeLogging to allow scrubbing only log messages
2441 generated while acting as a relay.
2442 - Ship the bridges spec file in the tarball too.
2443 - Avoid a mad rush at the beginning of each month when each client
2444 rotates half of its guards. Instead we spread the rotation out
2445 throughout the month, but we still avoid leaving a precise timestamp
2446 in the state file about when we first picked the guard. Improves
2447 over the behavior introduced in 0.1.2.17.
2449 o Minor bugfixes (compiling):
2450 - Fix compilation on OS X 10.3, which has a stub mlockall() but
2451 hides it. Bugfix on 0.2.2.6-alpha.
2452 - Fix compilation on Solaris by removing support for the
2453 DisableAllSwap config option. Solaris doesn't have an rlimit for
2454 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
2457 o Minor bugfixes (crashes):
2458 - Do not segfault when writing buffer stats when we haven't observed
2459 a single circuit to report about. Found by Fabian Lanze. Bugfix on
2461 - If we're in the pathological case where there's no exit bandwidth
2462 but there is non-exit bandwidth, or no guard bandwidth but there
2463 is non-guard bandwidth, don't crash during path selection. Bugfix
2465 - Fix an impossible-to-actually-trigger buffer overflow in relay
2466 descriptor generation. Bugfix on 0.1.0.15.
2468 o Minor bugfixes (privacy):
2469 - Fix an instance where a Tor directory mirror might accidentally
2470 log the IP address of a misbehaving Tor client. Bugfix on
2472 - Don't list Windows capabilities in relay descriptors. We never made
2473 use of them, and maybe it's a bad idea to publish them. Bugfix
2476 o Minor bugfixes (other):
2477 - Resolve an edge case in path weighting that could make us misweight
2478 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
2479 - Fix statistics on client numbers by country as seen by bridges that
2480 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
2481 intervals instead of variable 12-to-48-hour intervals.
2482 - After we free an internal connection structure, overwrite it
2483 with a different memory value than we use for overwriting a freed
2484 internal circuit structure. Should help with debugging. Suggested
2486 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
2490 - Remove the HSAuthorityRecordStats option that version 0 hidden
2491 service authorities could have used to track statistics of overall
2492 hidden service usage.
2495 Changes in version 0.2.1.22 - 2010-01-19
2496 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
2497 authorities -- it would tell you its whole history of bridge descriptors
2498 if you make the right directory request. This stable update also
2499 rotates two of the seven v3 directory authority keys and locations.
2501 o Directory authority changes:
2502 - Rotate keys (both v3 identity and relay identity) for moria1
2506 - Stop bridge directory authorities from answering dbg-stability.txt
2507 directory queries, which would let people fetch a list of all
2508 bridge identities they track. Bugfix on 0.2.1.6-alpha.
2511 Changes in version 0.2.1.21 - 2009-12-21
2512 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
2513 library. If you use Tor on Linux / Unix and you're getting SSL
2514 renegotiation errors, upgrading should help. We also recommend an
2515 upgrade if you're an exit relay.
2518 - Work around a security feature in OpenSSL 0.9.8l that prevents our
2519 handshake from working unless we explicitly tell OpenSSL that we
2520 are using SSL renegotiation safely. We are, of course, but OpenSSL
2521 0.9.8l won't work unless we say we are.
2522 - Avoid crashing if the client is trying to upload many bytes and the
2523 circuit gets torn down at the same time, or if the flip side
2524 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
2527 - Do not refuse to learn about authority certs and v2 networkstatus
2528 documents that are older than the latest consensus. This bug might
2529 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
2530 Spotted and fixed by xmux.
2531 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
2532 trigger platform-specific option misparsing case found by Coverity
2534 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
2535 trigger assert. Fixes bug 1173.
2538 Changes in version 0.2.2.6-alpha - 2009-11-19
2539 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
2540 support for the new lower-footprint "microdescriptor" directory design,
2541 future-proofing our consensus format against new hash functions or
2542 other changes, and an Android port. It also makes Tor compatible with
2543 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
2546 - Directory authorities can now create, vote on, and serve multiple
2547 parallel formats of directory data as part of their voting process.
2548 Partially implements Proposal 162: "Publish the consensus in
2550 - Directory authorities can now agree on and publish small summaries
2551 of router information that clients can use in place of regular
2552 server descriptors. This transition will eventually allow clients
2553 to use far less bandwidth for downloading information about the
2554 network. Begins the implementation of Proposal 158: "Clients
2555 download consensus + microdescriptors".
2556 - The directory voting system is now extensible to use multiple hash
2557 algorithms for signatures and resource selection. Newer formats
2558 are signed with SHA256, with a possibility for moving to a better
2559 hash algorithm in the future.
2560 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
2561 current and future memory pages via mlockall(). On supported
2562 platforms (modern Linux and probably BSD but not Windows or OS X),
2563 this should effectively disable any and all attempts to page out
2564 memory. This option requires that you start your Tor as root --
2565 if you use DisableAllSwap, please consider using the User option
2566 to properly reduce the privileges of your Tor.
2567 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
2568 to help Tor build correctly for Android phones.
2571 - Work around a security feature in OpenSSL 0.9.8l that prevents our
2572 handshake from working unless we explicitly tell OpenSSL that we
2573 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
2574 won't work unless we say we are.
2577 - Fix a crash bug when trying to initialize the evdns module in
2578 Libevent 2. Bugfix on 0.2.1.16-rc.
2579 - Stop logging at severity 'warn' when some other Tor client tries
2580 to establish a circuit with us using weak DH keys. It's a protocol
2581 violation, but that doesn't mean ordinary users need to hear about
2582 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
2583 - Do not refuse to learn about authority certs and v2 networkstatus
2584 documents that are older than the latest consensus. This bug might
2585 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
2586 Spotted and fixed by xmux.
2587 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
2588 - If all authorities restart at once right before a consensus vote,
2589 nobody will vote about "Running", and clients will get a consensus
2590 with no usable relays. Instead, authorities refuse to build a
2591 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
2592 - If your relay can't keep up with the number of incoming create
2593 cells, it would log one warning per failure into your logs. Limit
2594 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
2595 - Bridges now use "reject *:*" as their default exit policy. Bugfix
2596 on 0.2.0.3-alpha; fixes bug 1113.
2597 - Fix a memory leak on directory authorities during voting that was
2598 introduced in 0.2.2.1-alpha. Found via valgrind.
2601 Changes in version 0.2.1.20 - 2009-10-15
2602 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
2603 services at once, prepares for more performance improvements, and
2604 fixes a bunch of smaller bugs.
2606 The Windows and OS X bundles also include a more recent Vidalia,
2607 and switch from Privoxy to Polipo.
2609 The OS X installers are now drag and drop. It's best to un-install
2610 Tor/Vidalia and then install this new bundle, rather than upgrade. If
2611 you want to upgrade, you'll need to update the paths for Tor and Polipo
2612 in the Vidalia Settings window.
2615 - Send circuit or stream sendme cells when our window has decreased
2616 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
2617 by Karsten when testing the "reduce circuit window" performance
2618 patch. Bugfix on the 54th commit on Tor -- from July 2002,
2619 before the release of Tor 0.0.0. This is the new winner of the
2621 - Fix a remotely triggerable memory leak when a consensus document
2622 contains more than one signature from the same voter. Bugfix on
2624 - Avoid segfault in rare cases when finishing an introduction circuit
2625 as a client and finding out that we don't have an introduction key
2626 for it. Fixes bug 1073. Reported by Aaron Swartz.
2629 - Tor now reads the "circwindow" parameter out of the consensus,
2630 and uses that value for its circuit package window rather than the
2631 default of 1000 cells. Begins the implementation of proposal 168.
2633 o New directory authorities:
2634 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
2636 - Move moria1 and tonga to alternate IP addresses.
2639 - Fix a signed/unsigned compile warning in 0.2.1.19.
2640 - Fix possible segmentation fault on directory authorities. Bugfix on
2642 - Fix an extremely rare infinite recursion bug that could occur if
2643 we tried to log a message after shutting down the log subsystem.
2644 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
2645 - Fix an obscure bug where hidden services on 64-bit big-endian
2646 systems might mis-read the timestamp in v3 introduce cells, and
2647 refuse to connect back to the client. Discovered by "rotor".
2648 Bugfix on 0.2.1.6-alpha.
2649 - We were triggering a CLOCK_SKEW controller status event whenever
2650 we connect via the v2 connection protocol to any relay that has
2651 a wrong clock. Instead, we should only inform the controller when
2652 it's a trusted authority that claims our clock is wrong. Bugfix
2653 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
2654 - We were telling the controller about CHECKING_REACHABILITY and
2655 REACHABILITY_FAILED status events whenever we launch a testing
2656 circuit or notice that one has failed. Instead, only tell the
2657 controller when we want to inform the user of overall success or
2658 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
2660 - Don't warn when we're using a circuit that ends with a node
2661 excluded in ExcludeExitNodes, but the circuit is not used to access
2662 the outside world. This should help fix bug 1090. Bugfix on
2664 - Work around a small memory leak in some versions of OpenSSL that
2665 stopped the memory used by the hostname TLS extension from being
2669 - Add a "getinfo status/accepted-server-descriptor" controller
2670 command, which is the recommended way for controllers to learn
2671 whether our server descriptor has been successfully received by at
2672 least on directory authority. Un-recommend good-server-descriptor
2673 getinfo and status events until we have a better design for them.
2676 Changes in version 0.2.2.5-alpha - 2009-10-11
2677 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
2680 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
2682 o New directory authorities:
2683 - Move dizum to an alternate IP address.
2686 Changes in version 0.2.2.4-alpha - 2009-10-10
2687 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
2688 introduces a new unit test framework, shifts directry authority
2689 addresses around to reduce the impact from recent blocking events,
2690 and fixes a few smaller bugs.
2693 - Fix several more asserts in the circuit_build_times code, for
2694 example one that causes Tor to fail to start once we have
2695 accumulated 5000 build times in the state file. Bugfixes on
2696 0.2.2.2-alpha; fixes bug 1108.
2698 o New directory authorities:
2699 - Move moria1 and Tonga to alternate IP addresses.
2702 - Log SSL state transitions at debug level during handshake, and
2703 include SSL states in error messages. This may help debug future
2704 SSL handshake issues.
2705 - Add a new "Handshake" log domain for activities that happen
2706 during the TLS handshake.
2707 - Revert to the "June 3 2009" ip-to-country file. The September one
2708 seems to have removed most US IP addresses.
2709 - Directory authorities now reject Tor relays with versions less than
2710 0.1.2.14. This step cuts out four relays from the current network,
2711 none of which are very big.
2714 - Fix a couple of smaller issues with gathering statistics. Bugfixes
2716 - Fix two memory leaks in the error case of
2717 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
2718 - Don't count one-hop circuits when we're estimating how long it
2719 takes circuits to build on average. Otherwise we'll set our circuit
2720 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
2721 - Directory authorities no longer change their opinion of, or vote on,
2722 whether a router is Running, unless they have themselves been
2723 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
2726 o Code simplifications and refactoring:
2727 - Revise our unit tests to use the "tinytest" framework, so we
2728 can run tests in their own processes, have smarter setup/teardown
2729 code, and so on. The unit test code has moved to its own
2730 subdirectory, and has been split into multiple modules.
2733 Changes in version 0.2.2.3-alpha - 2009-09-23
2734 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
2737 - Fix an overzealous assert in our new circuit build timeout code.
2738 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
2741 - If the networkstatus consensus tells us that we should use a
2742 negative circuit package window, ignore it. Otherwise we'll
2743 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
2746 Changes in version 0.2.2.2-alpha - 2009-09-21
2747 Tor 0.2.2.2-alpha introduces our latest performance improvement for
2748 clients: Tor tracks the average time it takes to build a circuit, and
2749 avoids using circuits that take too long to build. For fast connections,
2750 this feature can cut your expected latency in half. For slow or flaky
2751 connections, it could ruin your Tor experience. Let us know if it does!
2754 - Tor now tracks how long it takes to build client-side circuits
2755 over time, and adapts its timeout to local network performance.
2756 Since a circuit that takes a long time to build will also provide
2757 bad performance, we get significant latency improvements by
2758 discarding the slowest 20% of circuits. Specifically, Tor creates
2759 circuits more aggressively than usual until it has enough data
2760 points for a good timeout estimate. Implements proposal 151.
2761 We are especially looking for reports (good and bad) from users with
2762 both EDGE and broadband connections that can move from broadband
2763 to EDGE and find out if the build-time data in the .tor/state gets
2764 reset without loss of Tor usability. You should also see a notice
2765 log message telling you that Tor has reset its timeout.
2766 - Directory authorities can now vote on arbitary integer values as
2767 part of the consensus process. This is designed to help set
2768 network-wide parameters. Implements proposal 167.
2769 - Tor now reads the "circwindow" parameter out of the consensus,
2770 and uses that value for its circuit package window rather than the
2771 default of 1000 cells. Begins the implementation of proposal 168.
2774 - Fix a remotely triggerable memory leak when a consensus document
2775 contains more than one signature from the same voter. Bugfix on
2779 - Fix an extremely rare infinite recursion bug that could occur if
2780 we tried to log a message after shutting down the log subsystem.
2781 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
2782 - Fix parsing for memory or time units given without a space between
2783 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
2784 - A networkstatus vote must contain exactly one signature. Spec
2785 conformance issue. Bugfix on 0.2.0.3-alpha.
2786 - Fix an obscure bug where hidden services on 64-bit big-endian
2787 systems might mis-read the timestamp in v3 introduce cells, and
2788 refuse to connect back to the client. Discovered by "rotor".
2789 Bugfix on 0.2.1.6-alpha.
2790 - We were triggering a CLOCK_SKEW controller status event whenever
2791 we connect via the v2 connection protocol to any relay that has
2792 a wrong clock. Instead, we should only inform the controller when
2793 it's a trusted authority that claims our clock is wrong. Bugfix
2794 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
2795 - We were telling the controller about CHECKING_REACHABILITY and
2796 REACHABILITY_FAILED status events whenever we launch a testing
2797 circuit or notice that one has failed. Instead, only tell the
2798 controller when we want to inform the user of overall success or
2799 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
2801 - Don't warn when we're using a circuit that ends with a node
2802 excluded in ExcludeExitNodes, but the circuit is not used to access
2803 the outside world. This should help fix bug 1090, but more problems
2804 remain. Bugfix on 0.2.1.6-alpha.
2805 - Work around a small memory leak in some versions of OpenSSL that
2806 stopped the memory used by the hostname TLS extension from being
2808 - Make our 'torify' script more portable; if we have only one of
2809 'torsocks' or 'tsocks' installed, don't complain to the user;
2810 and explain our warning about tsocks better.
2813 - Add a "getinfo status/accepted-server-descriptor" controller
2814 command, which is the recommended way for controllers to learn
2815 whether our server descriptor has been successfully received by at
2816 least on directory authority. Un-recommend good-server-descriptor
2817 getinfo and status events until we have a better design for them.
2818 - Update to the "September 4 2009" ip-to-country file.
2821 Changes in version 0.2.2.1-alpha - 2009-08-26
2822 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
2823 Tor clients to bootstrap on networks where only port 80 is reachable,
2824 makes it more straightforward to support hardware crypto accelerators,
2825 and starts the groundwork for gathering stats safely at relays.
2828 - Start the process of disabling ".exit" address notation, since it
2829 can be used for a variety of esoteric application-level attacks
2830 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
2833 o New directory authorities:
2834 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
2838 - New AccelName and AccelDir options add support for dynamic OpenSSL
2839 hardware crypto acceleration engines.
2840 - Tor now supports tunneling all of its outgoing connections over
2841 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
2842 configuration options. Code by Christopher Davis.
2845 - Send circuit or stream sendme cells when our window has decreased
2846 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
2847 by Karsten when testing the "reduce circuit window" performance
2848 patch. Bugfix on the 54th commit on Tor -- from July 2002,
2849 before the release of Tor 0.0.0. This is the new winner of the
2852 o New options for gathering stats safely:
2853 - Directories that set "DirReqStatistics 1" write statistics on
2854 directory request to disk every 24 hours. As compared to the
2855 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
2856 1) stats are written to disk exactly every 24 hours; 2) estimated
2857 shares of v2 and v3 requests are determined as mean values, not at
2858 the end of a measurement period; 3) unresolved requests are listed
2859 with country code '??'; 4) directories also measure download times.
2860 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
2861 number of exit streams and transferred bytes per port to disk every
2863 - Relays that set "CellStatistics 1" write statistics on how long
2864 cells spend in their circuit queues to disk every 24 hours.
2865 - Entry nodes that set "EntryStatistics 1" write statistics on the
2866 rough number and origins of connecting clients to disk every 24
2868 - Relays that write any of the above statistics to disk and set
2869 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
2870 their extra-info documents.
2873 - New --digests command-line switch to output the digests of the
2874 source files Tor was built with.
2875 - The "torify" script now uses torsocks where available.
2876 - The memarea code now uses a sentinel value at the end of each area
2877 to make sure nothing writes beyond the end of an area. This might
2878 help debug some conceivable causes of bug 930.
2879 - Time and memory units in the configuration file can now be set to
2880 fractional units. For example, "2.5 GB" is now a valid value for
2882 - Certain Tor clients (such as those behind check.torproject.org) may
2883 want to fetch the consensus in an extra early manner. To enable this
2884 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
2885 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
2886 as only certain clients who must have this information sooner should
2888 - Instead of adding the svn revision to the Tor version string, report
2889 the git commit (when we're building from a git checkout).
2892 - If any the v3 certs we download are unparseable, we should actually
2893 notice the failure so we don't retry indefinitely. Bugfix on
2894 0.2.0.x; reported by "rotator".
2895 - If the cached cert file is unparseable, warn but don't exit.
2896 - Fix possible segmentation fault on directory authorities. Bugfix on
2898 - When Tor fails to parse a descriptor of any kind, dump it to disk.
2899 Might help diagnosing bug 1051.
2901 o Deprecated and removed features:
2902 - The controller no longer accepts the old obsolete "addr-mappings/"
2903 or "unregistered-servers-" GETINFO values.
2904 - Hidden services no longer publish version 0 descriptors, and clients
2905 do not request or use version 0 descriptors. However, the old hidden
2906 service authorities still accept and serve version 0 descriptors
2907 when contacted by older hidden services/clients.
2908 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
2909 always on; using them is necessary for correct forward-compatible
2911 - Remove support for .noconnect style addresses. Nobody was using
2912 them, and they provided another avenue for detecting Tor users
2913 via application-level web tricks.
2915 o Packaging changes:
2916 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
2917 installer bundles. See
2918 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
2919 for details of what's new in Vidalia 0.2.3.
2920 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
2921 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
2922 configuration file, rather than the old Privoxy.
2923 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
2924 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
2925 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
2926 better compatibility with OS X 10.6, aka Snow Leopard.
2927 - OS X Vidalia Bundle: The multi-package installer is now replaced
2928 by a simple drag and drop to the /Applications folder. This change
2929 occurred with the upgrade to Vidalia 0.2.3.
2932 Changes in version 0.2.1.19 - 2009-07-28
2933 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
2934 services on Tor 0.2.1.3-alpha through 0.2.1.18.
2937 - Make accessing hidden services on 0.2.1.x work right again.
2938 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
2939 part of patch provided by "optimist".
2942 - When a relay/bridge is writing out its identity key fingerprint to
2943 the "fingerprint" file and to its logs, write it without spaces. Now
2944 it will look like the fingerprints in our bridges documentation,
2945 and confuse fewer users.
2948 - Relays no longer publish a new server descriptor if they change
2949 their MaxAdvertisedBandwidth config option but it doesn't end up
2950 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
2951 fixes bug 1026. Patch from Sebastian.
2952 - Avoid leaking memory every time we get a create cell but we have
2953 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
2954 fixes bug 1034. Reported by BarkerJr.
2957 Changes in version 0.2.1.18 - 2009-07-24
2958 Tor 0.2.1.18 lays the foundations for performance improvements,
2959 adds status events to help users diagnose bootstrap problems, adds
2960 optional authentication/authorization for hidden services, fixes a
2961 variety of potential anonymity problems, and includes a huge pile of
2962 other features and bug fixes.
2965 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
2968 Changes in version 0.2.1.17-rc - 2009-07-07
2969 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
2970 candidate for the 0.2.1.x series. It lays the groundwork for further
2971 client performance improvements, and also fixes a big bug with directory
2972 authorities that were causing them to assign Guard and Stable flags
2975 The Windows bundles also finally include the geoip database that we
2976 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
2977 should actually install Torbutton rather than giving you a cryptic
2978 failure message (oops).
2981 - Clients now use the bandwidth values in the consensus, rather than
2982 the bandwidth values in each relay descriptor. This approach opens
2983 the door to more accurate bandwidth estimates once the directory
2984 authorities start doing active measurements. Implements more of
2988 - When Tor clients restart after 1-5 days, they discard all their
2989 cached descriptors as too old, but they still use the cached
2990 consensus document. This approach is good for robustness, but
2991 bad for performance: since they don't know any bandwidths, they
2992 end up choosing at random rather than weighting their choice by
2993 speed. Fixed by the above feature of putting bandwidths in the
2994 consensus. Bugfix on 0.2.0.x.
2995 - Directory authorities were neglecting to mark relays down in their
2996 internal histories if the relays fall off the routerlist without
2997 ever being found unreachable. So there were relays in the histories
2998 that haven't been seen for eight months, and are listed as being
2999 up for eight months. This wreaked havoc on the "median wfu"
3000 and "median mtbf" calculations, in turn making Guard and Stable
3001 flags very wrong, hurting network performance. Fixes bugs 696 and
3002 969. Bugfix on 0.2.0.6-alpha.
3005 - Serve the DirPortFrontPage page even when we have been approaching
3006 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
3007 - The control port would close the connection before flushing long
3008 replies, such as the network consensus, if a QUIT command was issued
3009 before the reply had completed. Now, the control port flushes all
3010 pending replies before closing the connection. Also fixed a spurious
3011 warning when a QUIT command is issued after a malformed or rejected
3012 AUTHENTICATE command, but before the connection was closed. Patch
3013 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
3014 - When we can't find an intro key for a v2 hidden service descriptor,
3015 fall back to the v0 hidden service descriptor and log a bug message.
3016 Workaround for bug 1024.
3017 - Fix a log message that did not respect the SafeLogging option.
3021 - If we're a relay and we change our IP address, be more verbose
3022 about the reason that made us change. Should help track down
3023 further bugs for relays on dynamic IP addresses.
3026 Changes in version 0.2.0.35 - 2009-06-24
3028 - Avoid crashing in the presence of certain malformed descriptors.
3029 Found by lark, and by automated fuzzing.
3030 - Fix an edge case where a malicious exit relay could convince a
3031 controller that the client's DNS question resolves to an internal IP
3032 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
3035 - Finally fix the bug where dynamic-IP relays disappear when their
3036 IP address changes: directory mirrors were mistakenly telling
3037 them their old address if they asked via begin_dir, so they
3038 never got an accurate answer about their new address, so they
3039 just vanished after a day. For belt-and-suspenders, relays that
3040 don't set Address in their config now avoid using begin_dir for
3041 all direct connections. Should fix bugs 827, 883, and 900.
3042 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
3043 that would occur on some exit nodes when DNS failures and timeouts
3044 occurred in certain patterns. Fix for bug 957.
3047 - When starting with a cache over a few days old, do not leak
3048 memory for the obsolete router descriptors in it. Bugfix on
3049 0.2.0.33; fixes bug 672.
3050 - Hidden service clients didn't use a cached service descriptor that
3051 was older than 15 minutes, but wouldn't fetch a new one either,
3052 because there was already one in the cache. Now, fetch a v2
3053 descriptor unless the same descriptor was added to the cache within
3054 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
3057 Changes in version 0.2.1.16-rc - 2009-06-20
3058 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
3059 a bunch of minor bugs.
3062 - Fix an edge case where a malicious exit relay could convince a
3063 controller that the client's DNS question resolves to an internal IP
3064 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
3066 o Major performance improvements (on 0.2.0.x):
3067 - Disable and refactor some debugging checks that forced a linear scan
3068 over the whole server-side DNS cache. These accounted for over 50%
3069 of CPU time on a relatively busy exit node's gprof profile. Found
3071 - Disable some debugging checks that appeared in exit node profile
3075 - Update to the "June 3 2009" ip-to-country file.
3076 - Do not have tor-resolve automatically refuse all .onion addresses;
3077 if AutomapHostsOnResolve is set in your torrc, this will work fine.
3079 o Minor bugfixes (on 0.2.0.x):
3080 - Log correct error messages for DNS-related network errors on
3082 - Fix a race condition that could cause crashes or memory corruption
3083 when running as a server with a controller listening for log
3085 - Avoid crashing when we have a policy specified in a DirPolicy or
3086 SocksPolicy or ReachableAddresses option with ports set on it,
3087 and we re-load the policy. May fix bug 996.
3088 - Hidden service clients didn't use a cached service descriptor that
3089 was older than 15 minutes, but wouldn't fetch a new one either,
3090 because there was already one in the cache. Now, fetch a v2
3091 descriptor unless the same descriptor was added to the cache within
3092 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
3094 o Minor bugfixes (on 0.2.1.x):
3095 - Don't warn users about low port and hibernation mix when they
3096 provide a *ListenAddress directive to fix that. Bugfix on
3098 - When switching back and forth between bridge mode, do not start
3099 gathering GeoIP data until two hours have passed.
3100 - Do not complain that the user has requested an excluded node as
3101 an exit when the node is not really an exit. This could happen
3102 because the circuit was for testing, or an introduction point.
3106 Changes in version 0.2.1.15-rc - 2009-05-25
3107 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
3108 series. It fixes a major bug on fast exit relays, as well as a variety
3111 o Major bugfixes (on 0.2.0.x):
3112 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
3113 that would occur on some exit nodes when DNS failures and timeouts
3114 occurred in certain patterns. Fix for bug 957.
3116 o Minor bugfixes (on 0.2.0.x):
3117 - Actually return -1 in the error case for read_bandwidth_usage().
3118 Harmless bug, since we currently don't care about the return value
3119 anywhere. Bugfix on 0.2.0.9-alpha.
3120 - Provide a more useful log message if bug 977 (related to buffer
3121 freelists) ever reappears, and do not crash right away.
3122 - Fix an assertion failure on 64-bit platforms when we allocated
3123 memory right up to the end of a memarea, then realigned the memory
3124 one step beyond the end. Fixes a possible cause of bug 930.
3125 - Protect the count of open sockets with a mutex, so we can't
3126 corrupt it when two threads are closing or opening sockets at once.
3127 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
3128 - Don't allow a bridge to publish its router descriptor to a
3129 non-bridge directory authority. Fixes part of bug 932.
3130 - When we change to or from being a bridge, reset our counts of
3131 client usage by country. Fixes bug 932.
3132 - Fix a bug that made stream bandwidth get misreported to the
3134 - Stop using malloc_usable_size() to use more area than we had
3135 actually allocated: it was safe, but made valgrind really unhappy.
3136 - Fix a memory leak when v3 directory authorities load their keys
3137 and cert from disk. Bugfix on 0.2.0.1-alpha.
3139 o Minor bugfixes (on 0.2.1.x):
3140 - Fix use of freed memory when deciding to mark a non-addable
3141 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
3144 Changes in version 0.2.1.14-rc - 2009-04-12
3145 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
3146 series. It begins fixing some major performance problems, and also
3147 finally addresses the bug that was causing relays on dynamic IP
3148 addresses to fall out of the directory.
3151 - Clients replace entry guards that were chosen more than a few months
3152 ago. This change should significantly improve client performance,
3153 especially once more people upgrade, since relays that have been
3154 a guard for a long time are currently overloaded.
3156 o Major bugfixes (on 0.2.0):
3157 - Finally fix the bug where dynamic-IP relays disappear when their
3158 IP address changes: directory mirrors were mistakenly telling
3159 them their old address if they asked via begin_dir, so they
3160 never got an accurate answer about their new address, so they
3161 just vanished after a day. For belt-and-suspenders, relays that
3162 don't set Address in their config now avoid using begin_dir for
3163 all direct connections. Should fix bugs 827, 883, and 900.
3164 - Relays were falling out of the networkstatus consensus for
3165 part of a day if they changed their local config but the
3166 authorities discarded their new descriptor as "not sufficiently
3167 different". Now directory authorities accept a descriptor as changed
3168 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
3170 - Avoid crashing in the presence of certain malformed descriptors.
3171 Found by lark, and by automated fuzzing.
3174 - When generating circuit events with verbose nicknames for
3175 controllers, try harder to look up nicknames for routers on a
3176 circuit. (Previously, we would look in the router descriptors we had
3177 for nicknames, but not in the consensus.) Partial fix for bug 941.
3178 - If the bridge config line doesn't specify a port, assume 443.
3179 This makes bridge lines a bit smaller and easier for users to
3181 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
3182 bytes (aka 20KB/s), to match our documentation. Also update
3183 directory authorities so they always assign the Fast flag to relays
3184 with 20KB/s of capacity. Now people running relays won't suddenly
3185 find themselves not seeing any use, if the network gets faster
3187 - Update to the "April 3 2009" ip-to-country file.
3190 - Avoid trying to print raw memory to the logs when we decide to
3191 give up on downloading a given relay descriptor. Bugfix on
3193 - In tor-resolve, when the Tor client to use is specified by
3194 <hostname>:<port>, actually use the specified port rather than
3195 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
3196 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
3197 - When starting with a cache over a few days old, do not leak
3198 memory for the obsolete router descriptors in it. Bugfix on
3200 - Avoid double-free on list of successfully uploaded hidden
3201 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
3202 - Change memarea_strndup() implementation to work even when
3203 duplicating a string at the end of a page. This bug was
3204 harmless for now, but could have meant crashes later. Fix by
3205 lark. Bugfix on 0.2.1.1-alpha.
3206 - Limit uploaded directory documents to be 16M rather than 500K.
3207 The directory authorities were refusing v3 consensus votes from
3208 other authorities, since the votes are now 504K. Fixes bug 959;
3209 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
3210 - Directory authorities should never send a 503 "busy" response to
3211 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
3215 Changes in version 0.2.1.13-alpha - 2009-03-09
3216 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
3217 cleanups. We're finally getting close to a release candidate.
3220 - Correctly update the list of which countries we exclude as
3221 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
3222 lark. Bugfix on 0.2.1.6-alpha.
3224 o Minor bugfixes (on 0.2.0.x and earlier):
3225 - Automatically detect MacOSX versions earlier than 10.4.0, and
3226 disable kqueue from inside Tor when running with these versions.
3227 We previously did this from the startup script, but that was no
3228 help to people who didn't use the startup script. Resolves bug 863.
3229 - When we had picked an exit node for a connection, but marked it as
3230 "optional", and it turned out we had no onion key for the exit,
3231 stop wanting that exit and try again. This situation may not
3232 be possible now, but will probably become feasible with proposal
3233 158. Spotted by rovv. Fixes another case of bug 752.
3234 - Clients no longer cache certificates for authorities they do not
3235 recognize. Bugfix on 0.2.0.9-alpha.
3236 - When we can't transmit a DNS request due to a network error, retry
3237 it after a while, and eventually transmit a failing response to
3238 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
3239 - If the controller claimed responsibility for a stream, but that
3240 stream never finished making its connection, it would live
3241 forever in circuit_wait state. Now we close it after SocksTimeout
3242 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
3243 - Drop begin cells to a hidden service if they come from the middle
3244 of a circuit. Patch from lark.
3245 - When we erroneously receive two EXTEND cells for the same circuit
3246 ID on the same connection, drop the second. Patch from lark.
3247 - Fix a crash that occurs on exit nodes when a nameserver request
3248 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
3249 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
3251 - Do not assume that a stack-allocated character array will be
3252 64-bit aligned on platforms that demand that uint64_t access is
3253 aligned. Possible fix for bug 604.
3254 - Parse dates and IPv4 addresses in a locale- and libc-independent
3255 manner, to avoid platform-dependent behavior on malformed input.
3256 - Build correctly when configured to build outside the main source
3257 path. Patch from Michael Gold.
3258 - We were already rejecting relay begin cells with destination port
3259 of 0. Now also reject extend cells with destination port or address
3260 of 0. Suggested by lark.
3262 o Minor bugfixes (on 0.2.1.x):
3263 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
3264 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
3265 - If we're an exit node, scrub the IP address to which we are exiting
3266 in the logs. Bugfix on 0.2.1.8-alpha.
3269 - On Linux, use the prctl call to re-enable core dumps when the user
3271 - New controller event NEWCONSENSUS that lists the networkstatus
3272 lines for every recommended relay. Now controllers like Torflow
3273 can keep up-to-date on which relays they should be using.
3274 - Update to the "February 26 2009" ip-to-country file.
3277 Changes in version 0.2.0.34 - 2009-02-08
3278 Tor 0.2.0.34 features several more security-related fixes. You should
3279 upgrade, especially if you run an exit relay (remote crash) or a
3280 directory authority (remote infinite loop), or you're on an older
3281 (pre-XP) or not-recently-patched Windows (remote exploit).
3283 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
3284 have many known flaws, and nobody should be using them. You should
3285 upgrade. If you're using a Linux or BSD and its packages are obsolete,
3286 stop using those packages and upgrade anyway.
3289 - Fix an infinite-loop bug on handling corrupt votes under certain
3290 circumstances. Bugfix on 0.2.0.8-alpha.
3291 - Fix a temporary DoS vulnerability that could be performed by
3292 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
3293 - Avoid a potential crash on exit nodes when processing malformed
3294 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
3295 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
3296 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
3299 - Fix compilation on systems where time_t is a 64-bit integer.
3300 Patch from Matthias Drochner.
3301 - Don't consider expiring already-closed client connections. Fixes
3302 bug 893. Bugfix on 0.0.2pre20.
3305 Changes in version 0.2.1.12-alpha - 2009-02-08
3306 Tor 0.2.1.12-alpha features several more security-related fixes. You
3307 should upgrade, especially if you run an exit relay (remote crash) or
3308 a directory authority (remote infinite loop), or you're on an older
3309 (pre-XP) or not-recently-patched Windows (remote exploit). It also
3310 includes a big pile of minor bugfixes and cleanups.
3313 - Fix an infinite-loop bug on handling corrupt votes under certain
3314 circumstances. Bugfix on 0.2.0.8-alpha.
3315 - Fix a temporary DoS vulnerability that could be performed by
3316 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
3317 - Avoid a potential crash on exit nodes when processing malformed
3318 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
3321 - Let controllers actually ask for the "clients_seen" event for
3322 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
3323 reported by Matt Edman.
3324 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
3326 - Fix a bug in address parsing that was preventing bridges or hidden
3327 service targets from being at IPv6 addresses.
3328 - Solve a bug that kept hardware crypto acceleration from getting
3329 enabled when accounting was turned on. Fixes bug 907. Bugfix on
3331 - Remove a bash-ism from configure.in to build properly on non-Linux
3332 platforms. Bugfix on 0.2.1.1-alpha.
3333 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
3334 headers. Bugfix on 0.2.0.10-alpha.
3335 - Don't consider expiring already-closed client connections. Fixes
3336 bug 893. Bugfix on 0.0.2pre20.
3337 - Fix another interesting corner-case of bug 891 spotted by rovv:
3338 Previously, if two hosts had different amounts of clock drift, and
3339 one of them created a new connection with just the wrong timing,
3340 the other might decide to deprecate the new connection erroneously.
3341 Bugfix on 0.1.1.13-alpha.
3342 - Resolve a very rare crash bug that could occur when the user forced
3343 a nameserver reconfiguration during the middle of a nameserver
3344 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
3345 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
3346 Bugfix on 0.2.1.7-alpha.
3347 - If we're using bridges and our network goes away, be more willing
3348 to forgive our bridges and try again when we get an application
3349 request. Bugfix on 0.2.0.x.
3352 - Support platforms where time_t is 64 bits long. (Congratulations,
3353 NetBSD!) Patch from Matthias Drochner.
3354 - Add a 'getinfo status/clients-seen' controller command, in case
3355 controllers want to hear clients_seen events but connect late.
3358 - Disable GCC's strict alias optimization by default, to avoid the
3359 likelihood of its introducing subtle bugs whenever our code violates
3360 the letter of C99's alias rules.
3363 Changes in version 0.2.0.33 - 2009-01-21
3364 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
3365 useful to users. It also finally fixes a bug where a relay or client
3366 that's been off for many days would take a long time to bootstrap.
3368 This update also fixes an important security-related bug reported by
3369 Ilja van Sprundel. You should upgrade. (We'll send out more details
3370 about the bug once people have had some time to upgrade.)
3373 - Fix a heap-corruption bug that may be remotely triggerable on
3374 some platforms. Reported by Ilja van Sprundel.
3377 - When a stream at an exit relay is in state "resolving" or
3378 "connecting" and it receives an "end" relay cell, the exit relay
3379 would silently ignore the end cell and not close the stream. If
3380 the client never closes the circuit, then the exit relay never
3381 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
3383 - When sending CREATED cells back for a given circuit, use a 64-bit
3384 connection ID to find the right connection, rather than an addr:port
3385 combination. Now that we can have multiple OR connections between
3386 the same ORs, it is no longer possible to use addr:port to uniquely
3387 identify a connection.
3388 - Bridge relays that had DirPort set to 0 would stop fetching
3389 descriptors shortly after startup, and then briefly resume
3390 after a new bandwidth test and/or after publishing a new bridge
3391 descriptor. Bridge users that try to bootstrap from them would
3392 get a recent networkstatus but would get descriptors from up to
3393 18 hours earlier, meaning most of the descriptors were obsolete
3394 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
3395 - Prevent bridge relays from serving their 'extrainfo' document
3396 to anybody who asks, now that extrainfo docs include potentially
3397 sensitive aggregated client geoip summaries. Bugfix on
3399 - If the cached networkstatus consensus is more than five days old,
3400 discard it rather than trying to use it. In theory it could be
3401 useful because it lists alternate directory mirrors, but in practice
3402 it just means we spend many minutes trying directory mirrors that
3403 are long gone from the network. Also discard router descriptors as
3404 we load them if they are more than five days old, since the onion
3405 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
3408 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
3409 could make gcc generate non-functional binary search code. Bugfix
3411 - Build correctly on platforms without socklen_t.
3412 - Compile without warnings on solaris.
3413 - Avoid potential crash on internal error during signature collection.
3414 Fixes bug 864. Patch from rovv.
3415 - Correct handling of possible malformed authority signing key
3416 certificates with internal signature types. Fixes bug 880.
3417 Bugfix on 0.2.0.3-alpha.
3418 - Fix a hard-to-trigger resource leak when logging credential status.
3420 - When we can't initialize DNS because the network is down, do not
3421 automatically stop Tor from starting. Instead, we retry failed
3422 dns_init() every 10 minutes, and change the exit policy to reject
3423 *:* until one succeeds. Fixes bug 691.
3424 - Use 64 bits instead of 32 bits for connection identifiers used with
3425 the controller protocol, to greatly reduce risk of identifier reuse.
3426 - When we're choosing an exit node for a circuit, and we have
3427 no pending streams, choose a good general exit rather than one that
3428 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
3429 - Fix another case of assuming, when a specific exit is requested,
3430 that we know more than the user about what hosts it allows.
3431 Fixes one case of bug 752. Patch from rovv.
3432 - Clip the MaxCircuitDirtiness config option to a minimum of 10
3433 seconds. Warn the user if lower values are given in the
3434 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
3435 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
3436 user if lower values are given in the configuration. Bugfix on
3437 0.1.1.17-rc. Patch by Sebastian.
3438 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
3439 the cache because we already had a v0 descriptor with the same ID.
3440 Bugfix on 0.2.0.18-alpha.
3441 - Fix a race condition when freeing keys shared between main thread
3442 and CPU workers that could result in a memory leak. Bugfix on
3443 0.1.0.1-rc. Fixes bug 889.
3444 - Send a valid END cell back when a client tries to connect to a
3445 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
3446 840. Patch from rovv.
3447 - Check which hops rendezvous stream cells are associated with to
3448 prevent possible guess-the-streamid injection attacks from
3449 intermediate hops. Fixes another case of bug 446. Based on patch
3451 - If a broken client asks a non-exit router to connect somewhere,
3452 do not even do the DNS lookup before rejecting the connection.
3453 Fixes another case of bug 619. Patch from rovv.
3454 - When a relay gets a create cell it can't decrypt (e.g. because it's
3455 using the wrong onion key), we were dropping it and letting the
3456 client time out. Now actually answer with a destroy cell. Fixes
3457 bug 904. Bugfix on 0.0.2pre8.
3459 o Minor bugfixes (hidden services):
3460 - Do not throw away existing introduction points on SIGHUP. Bugfix on
3461 0.0.6pre1. Patch by Karsten. Fixes bug 874.
3464 - Report the case where all signatures in a detached set are rejected
3465 differently than the case where there is an error handling the
3467 - When we realize that another process has modified our cached
3468 descriptors, print out a more useful error message rather than
3469 triggering an assertion. Fixes bug 885. Patch from Karsten.
3470 - Implement the 0x20 hack to better resist DNS poisoning: set the
3471 case on outgoing DNS requests randomly, and reject responses that do
3472 not match the case correctly. This logic can be disabled with the
3473 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
3474 of servers that do not reliably preserve case in replies. See
3475 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
3477 - Check DNS replies for more matching fields to better resist DNS
3479 - Never use OpenSSL compression: it wastes RAM and CPU trying to
3480 compress cells, which are basically all encrypted, compressed, or
3484 Changes in version 0.2.1.11-alpha - 2009-01-20
3485 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
3486 week it will take a long time to bootstrap again" bug. It also fixes
3487 an important security-related bug reported by Ilja van Sprundel. You
3488 should upgrade. (We'll send out more details about the bug once people
3489 have had some time to upgrade.)
3492 - Fix a heap-corruption bug that may be remotely triggerable on
3493 some platforms. Reported by Ilja van Sprundel.
3496 - Discard router descriptors as we load them if they are more than
3497 five days old. Otherwise if Tor is off for a long time and then
3498 starts with cached descriptors, it will try to use the onion
3499 keys in those obsolete descriptors when building circuits. Bugfix
3500 on 0.2.0.x. Fixes bug 887.
3503 - Try to make sure that the version of Libevent we're running with
3504 is binary-compatible with the one we built with. May address bug
3506 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
3507 for bug 905. Bugfix on 0.2.1.7-alpha.
3508 - Add a new --enable-local-appdata configuration switch to change
3509 the default location of the datadir on win32 from APPDATA to
3510 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
3511 entirely. Patch from coderman.
3514 - Make outbound DNS packets respect the OutboundBindAddress setting.
3515 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
3516 - When our circuit fails at the first hop (e.g. we get a destroy
3517 cell back), avoid using that OR connection anymore, and also
3518 tell all the one-hop directory requests waiting for it that they
3519 should fail. Bugfix on 0.2.1.3-alpha.
3520 - In the torify(1) manpage, mention that tsocks will leak your
3524 Changes in version 0.2.1.10-alpha - 2009-01-06
3525 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
3526 would make the bridge relay not so useful if it had DirPort set to 0,
3527 and one that could let an attacker learn a little bit of information
3528 about the bridge's users), and a bug that would cause your Tor relay
3529 to ignore a circuit create request it can't decrypt (rather than reply
3530 with an error). It also fixes a wide variety of other bugs.
3533 - If the cached networkstatus consensus is more than five days old,
3534 discard it rather than trying to use it. In theory it could
3535 be useful because it lists alternate directory mirrors, but in
3536 practice it just means we spend many minutes trying directory
3537 mirrors that are long gone from the network. Helps bug 887 a bit;
3539 - Bridge relays that had DirPort set to 0 would stop fetching
3540 descriptors shortly after startup, and then briefly resume
3541 after a new bandwidth test and/or after publishing a new bridge
3542 descriptor. Bridge users that try to bootstrap from them would
3543 get a recent networkstatus but would get descriptors from up to
3544 18 hours earlier, meaning most of the descriptors were obsolete
3545 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
3546 - Prevent bridge relays from serving their 'extrainfo' document
3547 to anybody who asks, now that extrainfo docs include potentially
3548 sensitive aggregated client geoip summaries. Bugfix on
3552 - New controller event "clients_seen" to report a geoip-based summary
3553 of which countries we've seen clients from recently. Now controllers
3554 like Vidalia can show bridge operators that they're actually making
3556 - Build correctly against versions of OpenSSL 0.9.8 or later built
3557 without support for deprecated functions.
3558 - Update to the "December 19 2008" ip-to-country file.
3560 o Minor bugfixes (on 0.2.0.x):
3561 - Authorities now vote for the Stable flag for any router whose
3562 weighted MTBF is at least 5 days, regardless of the mean MTBF.
3563 - Do not remove routers as too old if we do not have any consensus
3564 document. Bugfix on 0.2.0.7-alpha.
3565 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
3566 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
3567 - When an exit relay resolves a stream address to a local IP address,
3568 do not just keep retrying that same exit relay over and
3569 over. Instead, just close the stream. Addresses bug 872. Bugfix
3570 on 0.2.0.32. Patch from rovv.
3571 - If a hidden service sends us an END cell, do not consider
3572 retrying the connection; just close it. Patch from rovv.
3573 - When we made bridge authorities stop serving bridge descriptors over
3574 unencrypted links, we also broke DirPort reachability testing for
3575 bridges. So bridges with a non-zero DirPort were printing spurious
3576 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
3577 - When a relay gets a create cell it can't decrypt (e.g. because it's
3578 using the wrong onion key), we were dropping it and letting the
3579 client time out. Now actually answer with a destroy cell. Fixes
3580 bug 904. Bugfix on 0.0.2pre8.
3581 - Squeeze 2-5% out of client performance (according to oprofile) by
3582 improving the implementation of some policy-manipulation functions.
3584 o Minor bugfixes (on 0.2.1.x):
3585 - Make get_interface_address() function work properly again; stop
3586 guessing the wrong parts of our address as our address.
3587 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
3588 send on that circuit. Otherwise we might violate the proposal-110
3589 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
3591 - When we're sending non-EXTEND cells to the first hop in a circuit,
3592 for example to use an encrypted directory connection, we don't need
3593 to use RELAY_EARLY cells: the first hop knows what kind of cell
3594 it is, and nobody else can even see the cell type. Conserving
3595 RELAY_EARLY cells makes it easier to cannibalize circuits like
3597 - Stop logging nameserver addresses in reverse order.
3598 - If we are retrying a directory download slowly over and over, do
3599 not automatically give up after the 254th failure. Bugfix on
3601 - Resume reporting accurate "stream end" reasons to the local control
3602 port. They were lost in the changes for Proposal 148. Bugfix on
3605 o Deprecated and removed features:
3606 - The old "tor --version --version" command, which would print out
3607 the subversion "Id" of most of the source files, is now removed. It
3608 turned out to be less useful than we'd expected, and harder to
3611 o Code simplifications and refactoring:
3612 - Change our header file guard macros to be less likely to conflict
3613 with system headers. Adam Langley noticed that we were conflicting
3614 with log.h on Android.
3615 - Tool-assisted documentation cleanup. Nearly every function or
3616 static variable in Tor should have its own documentation now.
3619 Changes in version 0.2.1.9-alpha - 2008-12-25
3620 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
3622 o New directory authorities:
3623 - gabelmoo (the authority run by Karsten Loesing) now has a new
3627 - Never use a connection with a mismatched address to extend a
3628 circuit, unless that connection is canonical. A canonical
3629 connection is one whose address is authenticated by the router's
3630 identity key, either in a NETINFO cell or in a router descriptor.
3631 - Avoid a possible memory corruption bug when receiving hidden service
3632 descriptors. Bugfix on 0.2.1.6-alpha.
3635 - Fix a logic error that would automatically reject all but the first
3636 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
3637 part of bug 813/868. Bug spotted by coderman.
3638 - When a stream at an exit relay is in state "resolving" or
3639 "connecting" and it receives an "end" relay cell, the exit relay
3640 would silently ignore the end cell and not close the stream. If
3641 the client never closes the circuit, then the exit relay never
3642 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
3644 - When we can't initialize DNS because the network is down, do not
3645 automatically stop Tor from starting. Instead, retry failed
3646 dns_init() every 10 minutes, and change the exit policy to reject
3647 *:* until one succeeds. Fixes bug 691.
3650 - Give a better error message when an overzealous init script says
3651 "sudo -u username tor --user username". Makes Bug 882 easier for
3653 - When a directory authority gives us a new guess for our IP address,
3654 log which authority we used. Hopefully this will help us debug
3655 the recent complaints about bad IP address guesses.
3656 - Detect svn revision properly when we're using git-svn.
3657 - Try not to open more than one descriptor-downloading connection
3658 to an authority at once. This should reduce load on directory
3659 authorities. Fixes bug 366.
3660 - Add cross-certification to newly generated certificates, so that
3661 a signing key is enough information to look up a certificate.
3662 Partial implementation of proposal 157.
3663 - Start serving certificates by <identity digest, signing key digest>
3664 pairs. Partial implementation of proposal 157.
3665 - Clients now never report any stream end reason except 'MISC'.
3666 Implements proposal 148.
3667 - On platforms with a maximum syslog string length, truncate syslog
3668 messages to that length ourselves, rather than relying on the
3669 system to do it for us.
3670 - Optimize out calls to time(NULL) that occur for every IO operation,
3671 or for every cell. On systems where time() is a slow syscall,
3672 this fix will be slightly helpful.
3673 - Exit servers can now answer resolve requests for ip6.arpa addresses.
3674 - When we download a descriptor that we then immediately (as
3675 a directory authority) reject, do not retry downloading it right
3676 away. Should save some bandwidth on authorities. Fix for bug
3677 888. Patch by Sebastian Hahn.
3678 - When a download gets us zero good descriptors, do not notify
3679 Tor that new directory information has arrived.
3680 - Avoid some nasty corner cases in the logic for marking connections
3681 as too old or obsolete or noncanonical for circuits. Partial
3684 o Minor features (controller):
3685 - New CONSENSUS_ARRIVED event to note when a new consensus has
3686 been fetched and validated.
3687 - When we realize that another process has modified our cached
3688 descriptors file, print out a more useful error message rather
3689 than triggering an assertion. Fixes bug 885. Patch from Karsten.
3690 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
3691 controllers to prevent SIGHUP from reloading the
3692 configuration. Fixes bug 856.
3695 - Resume using the correct "REASON=" stream when telling the
3696 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
3697 - When a canonical connection appears later in our internal list
3698 than a noncanonical one for a given OR ID, always use the
3699 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
3701 - Clip the MaxCircuitDirtiness config option to a minimum of 10
3702 seconds. Warn the user if lower values are given in the
3703 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
3704 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
3705 user if lower values are given in the configuration. Bugfix on
3706 0.1.1.17-rc. Patch by Sebastian.
3707 - Fix a race condition when freeing keys shared between main thread
3708 and CPU workers that could result in a memory leak. Bugfix on
3709 0.1.0.1-rc. Fixes bug 889.
3711 o Minor bugfixes (hidden services):
3712 - Do not throw away existing introduction points on SIGHUP (bugfix on
3713 0.0.6pre1); also, do not stall hidden services because we're
3714 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
3715 by John Brooks. Patch by Karsten. Fixes bug 874.
3716 - Fix a memory leak when we decline to add a v2 rendezvous
3717 descriptor to the cache because we already had a v0 descriptor
3718 with the same ID. Bugfix on 0.2.0.18-alpha.
3720 o Deprecated and removed features:
3721 - RedirectExits has been removed. It was deprecated since
3723 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
3724 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
3725 - Cell pools are now always enabled; --disable-cell-pools is ignored.
3727 o Code simplifications and refactoring:
3728 - Rename the confusing or_is_obsolete field to the more appropriate
3729 is_bad_for_new_circs, and move it to or_connection_t where it
3731 - Move edge-only flags from connection_t to edge_connection_t: not
3732 only is this better coding, but on machines of plausible alignment,
3733 it should save 4-8 bytes per connection_t. "Every little bit helps."
3734 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
3735 for consistency; keep old option working for backward compatibility.
3736 - Simplify the code for finding connections to use for a circuit.
3739 Changes in version 0.2.1.8-alpha - 2008-12-08
3740 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
3741 builds better on unusual platforms like Solaris and old OS X, and
3742 fixes a variety of other issues.
3745 - New DirPortFrontPage option that takes an html file and publishes
3746 it as "/" on the DirPort. Now relay operators can provide a
3747 disclaimer without needing to set up a separate webserver. There's
3748 a sample disclaimer in contrib/tor-exit-notice.html.
3751 - When the client is choosing entry guards, now it selects at most
3752 one guard from a given relay family. Otherwise we could end up with
3753 all of our entry points into the network run by the same operator.
3754 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
3757 - Fix a DOS opportunity during the voting signature collection process
3758 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
3759 - Fix a possible segfault when establishing an exit connection. Bugfix
3763 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
3765 - Made Tor a little less aggressive about deleting expired
3766 certificates. Partial fix for bug 854.
3767 - Stop doing unaligned memory access that generated bus errors on
3768 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
3769 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
3770 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
3771 - Make USR2 log-level switch take effect immediately. Bugfix on
3773 - If one win32 nameserver fails to get added, continue adding the
3774 rest, and don't automatically fail.
3775 - Use fcntl() for locking when flock() is not available. Should fix
3776 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
3777 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
3778 could make gcc generate non-functional binary search code. Bugfix
3780 - Build correctly on platforms without socklen_t.
3781 - Avoid potential crash on internal error during signature collection.
3782 Fixes bug 864. Patch from rovv.
3783 - Do not use C's stdio library for writing to log files. This will
3784 improve logging performance by a minute amount, and will stop
3785 leaking fds when our disk is full. Fixes bug 861.
3786 - Stop erroneous use of O_APPEND in cases where we did not in fact
3787 want to re-seek to the end of a file before every last write().
3788 - Correct handling of possible malformed authority signing key
3789 certificates with internal signature types. Fixes bug 880. Bugfix
3791 - Fix a hard-to-trigger resource leak when logging credential status.
3795 - Directory mirrors no longer fetch the v1 directory or
3796 running-routers files. They are obsolete, and nobody asks for them
3797 anymore. This is the first step to making v1 authorities obsolete.
3799 o Minor features (controller):
3800 - Return circuit purposes in response to GETINFO circuit-status. Fixes
3804 Changes in version 0.2.0.32 - 2008-11-20
3805 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
3806 packages (and maybe other packages) noticed by Theo de Raadt, fixes
3807 a smaller security flaw that might allow an attacker to access local
3808 services, further improves hidden service performance, and fixes a
3809 variety of other issues.
3812 - The "User" and "Group" config options did not clear the
3813 supplementary group entries for the Tor process. The "User" option
3814 is now more robust, and we now set the groups to the specified
3815 user's primary group. The "Group" option is now ignored. For more
3816 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
3817 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
3818 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
3819 - The "ClientDNSRejectInternalAddresses" config option wasn't being
3820 consistently obeyed: if an exit relay refuses a stream because its
3821 exit policy doesn't allow it, we would remember what IP address
3822 the relay said the destination address resolves to, even if it's
3823 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
3826 - Fix a DOS opportunity during the voting signature collection process
3827 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
3829 o Major bugfixes (hidden services):
3830 - When fetching v0 and v2 rendezvous service descriptors in parallel,
3831 we were failing the whole hidden service request when the v0
3832 descriptor fetch fails, even if the v2 fetch is still pending and
3833 might succeed. Similarly, if the last v2 fetch fails, we were
3834 failing the whole hidden service request even if a v0 fetch is
3835 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
3836 - When extending a circuit to a hidden service directory to upload a
3837 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
3838 requests failed, because the router descriptor has not been
3839 downloaded yet. In these cases, do not attempt to upload the
3840 rendezvous descriptor, but wait until the router descriptor is
3841 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
3842 descriptor from a hidden service directory for which the router
3843 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
3847 - Fix several infrequent memory leaks spotted by Coverity.
3848 - When testing for libevent functions, set the LDFLAGS variable
3849 correctly. Found by Riastradh.
3850 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
3851 bootstrapping with tunneled directory connections. Bugfix on
3852 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
3853 - When asked to connect to A.B.exit:80, if we don't know the IP for A
3854 and we know that server B rejects most-but-not all connections to
3855 port 80, we would previously reject the connection. Now, we assume
3856 the user knows what they were asking for. Fixes bug 752. Bugfix
3857 on 0.0.9rc5. Diagnosed by BarkerJr.
3858 - If we overrun our per-second write limits a little, count this as
3859 having used up our write allocation for the second, and choke
3860 outgoing directory writes. Previously, we had only counted this when
3861 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
3862 Bugfix on 0.2.0.x (??).
3863 - Remove the old v2 directory authority 'lefkada' from the default
3864 list. It has been gone for many months.
3865 - Stop doing unaligned memory access that generated bus errors on
3866 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
3867 - Make USR2 log-level switch take effect immediately. Bugfix on
3870 o Minor bugfixes (controller):
3871 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
3872 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
3875 Changes in version 0.2.1.7-alpha - 2008-11-08
3876 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
3877 packages (and maybe other packages) noticed by Theo de Raadt, fixes
3878 a smaller security flaw that might allow an attacker to access local
3879 services, adds better defense against DNS poisoning attacks on exit
3880 relays, further improves hidden service performance, and fixes a
3881 variety of other issues.
3884 - The "ClientDNSRejectInternalAddresses" config option wasn't being
3885 consistently obeyed: if an exit relay refuses a stream because its
3886 exit policy doesn't allow it, we would remember what IP address
3887 the relay said the destination address resolves to, even if it's
3888 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
3889 - The "User" and "Group" config options did not clear the
3890 supplementary group entries for the Tor process. The "User" option
3891 is now more robust, and we now set the groups to the specified
3892 user's primary group. The "Group" option is now ignored. For more
3893 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
3894 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
3895 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
3896 - Do not use or believe expired v3 authority certificates. Patch
3897 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
3900 - Now NodeFamily and MyFamily config options allow spaces in
3901 identity fingerprints, so it's easier to paste them in.
3902 Suggested by Lucky Green.
3903 - Implement the 0x20 hack to better resist DNS poisoning: set the
3904 case on outgoing DNS requests randomly, and reject responses that do
3905 not match the case correctly. This logic can be disabled with the
3906 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
3907 of servers that do not reliably preserve case in replies. See
3908 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
3910 - Preserve case in replies to DNSPort requests in order to support
3911 the 0x20 hack for resisting DNS poisoning attacks.
3913 o Hidden service performance improvements:
3914 - When the client launches an introduction circuit, retry with a
3915 new circuit after 30 seconds rather than 60 seconds.
3916 - Launch a second client-side introduction circuit in parallel
3917 after a delay of 15 seconds (based on work by Christian Wilms).
3918 - Hidden services start out building five intro circuits rather
3919 than three, and when the first three finish they publish a service
3920 descriptor using those. Now we publish our service descriptor much
3921 faster after restart.
3924 - Minor fix in the warning messages when you're having problems
3925 bootstrapping; also, be more forgiving of bootstrap problems when
3926 we're still making incremental progress on a given bootstrap phase.
3927 - When we're choosing an exit node for a circuit, and we have
3928 no pending streams, choose a good general exit rather than one that
3929 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
3930 - Send a valid END cell back when a client tries to connect to a
3931 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
3932 840. Patch from rovv.
3933 - If a broken client asks a non-exit router to connect somewhere,
3934 do not even do the DNS lookup before rejecting the connection.
3935 Fixes another case of bug 619. Patch from rovv.
3936 - Fix another case of assuming, when a specific exit is requested,
3937 that we know more than the user about what hosts it allows.
3938 Fixes another case of bug 752. Patch from rovv.
3939 - Check which hops rendezvous stream cells are associated with to
3940 prevent possible guess-the-streamid injection attacks from
3941 intermediate hops. Fixes another case of bug 446. Based on patch
3943 - Avoid using a negative right-shift when comparing 32-bit
3944 addresses. Possible fix for bug 845 and bug 811.
3945 - Make the assert_circuit_ok() function work correctly on circuits that
3946 have already been marked for close.
3947 - Fix read-off-the-end-of-string error in unit tests when decoding
3948 introduction points.
3949 - Fix uninitialized size field for memory area allocation: may improve
3950 memory performance during directory parsing.
3951 - Treat duplicate certificate fetches as failures, so that we do
3952 not try to re-fetch an expired certificate over and over and over.
3953 - Do not say we're fetching a certificate when we'll in fact skip it
3954 because of a pending download.
3957 Changes in version 0.2.1.6-alpha - 2008-09-30
3958 Tor 0.2.1.6-alpha further improves performance and robustness of
3959 hidden services, starts work on supporting per-country relay selection,
3960 and fixes a variety of smaller issues.
3963 - Implement proposal 121: make it possible to build hidden services
3964 that only certain clients are allowed to connect to. This is
3965 enforced at several points, so that unauthorized clients are unable
3966 to send INTRODUCE cells to the service, or even (depending on the
3967 type of authentication) to learn introduction points. This feature
3968 raises the bar for certain kinds of active attacks against hidden
3969 services. Code by Karsten Loesing.
3970 - Relays now store and serve v2 hidden service descriptors by default,
3971 i.e., the new default value for HidServDirectoryV2 is 1. This is
3972 the last step in proposal 114, which aims to make hidden service
3973 lookups more reliable.
3974 - Start work to allow node restrictions to include country codes. The
3975 syntax to exclude nodes in a country with country code XX is
3976 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
3977 refinement to decide what config options should take priority if
3978 you ask to both use a particular node and exclude it.
3979 - Allow ExitNodes list to include IP ranges and country codes, just
3980 like the Exclude*Nodes lists. Patch from Robert Hogan.
3983 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
3984 Tor to fail to start if you had it configured to use a bridge
3985 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
3986 - When extending a circuit to a hidden service directory to upload a
3987 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
3988 requests failed, because the router descriptor had not been
3989 downloaded yet. In these cases, we now wait until the router
3990 descriptor is downloaded, and then retry. Likewise, clients
3991 now skip over a hidden service directory if they don't yet have
3992 its router descriptor, rather than futilely requesting it and
3993 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
3995 - When fetching v0 and v2 rendezvous service descriptors in parallel,
3996 we were failing the whole hidden service request when the v0
3997 descriptor fetch fails, even if the v2 fetch is still pending and
3998 might succeed. Similarly, if the last v2 fetch fails, we were
3999 failing the whole hidden service request even if a v0 fetch is
4000 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
4001 - DNS replies need to have names matching their requests, but
4002 these names should be in the questions section, not necessarily
4003 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
4006 - Update to the "September 1 2008" ip-to-country file.
4007 - Allow ports 465 and 587 in the default exit policy again. We had
4008 rejected them in 0.1.0.15, because back in 2005 they were commonly
4009 misconfigured and ended up as spam targets. We hear they are better
4010 locked down these days.
4011 - Use a lockfile to make sure that two Tor processes are not
4012 simultaneously running with the same datadir.
4013 - Serve the latest v3 networkstatus consensus via the control
4014 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
4015 - Better logging about stability/reliability calculations on directory
4017 - Drop the requirement to have an open dir port for storing and
4018 serving v2 hidden service descriptors.
4019 - Directory authorities now serve a /tor/dbg-stability.txt URL to
4020 help debug WFU and MTBF calculations.
4021 - Implement most of Proposal 152: allow specialized servers to permit
4022 single-hop circuits, and clients to use those servers to build
4023 single-hop circuits when using a specialized controller. Patch
4024 from Josh Albrecht. Resolves feature request 768.
4025 - Add a -p option to tor-resolve for specifying the SOCKS port: some
4026 people find host:port too confusing.
4027 - Make TrackHostExit mappings expire a while after their last use, not
4028 after their creation. Patch from Robert Hogan.
4029 - Provide circuit purposes along with circuit events to the controller.
4032 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
4034 - Fixed some memory leaks -- some quite frequent, some almost
4035 impossible to trigger -- based on results from Coverity.
4036 - When testing for libevent functions, set the LDFLAGS variable
4037 correctly. Found by Riastradh.
4038 - Fix an assertion bug in parsing policy-related options; possible fix
4040 - Catch and report a few more bootstrapping failure cases when Tor
4041 fails to establish a TCP connection. Cleanup on 0.2.1.x.
4042 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
4043 bootstrapping with tunneled directory connections. Bugfix on
4044 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
4045 - When asked to connect to A.B.exit:80, if we don't know the IP for A
4046 and we know that server B rejects most-but-not all connections to
4047 port 80, we would previously reject the connection. Now, we assume
4048 the user knows what they were asking for. Fixes bug 752. Bugfix
4049 on 0.0.9rc5. Diagnosed by BarkerJr.
4050 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
4051 service directories if they have no advertised dir port. Bugfix
4053 - If we overrun our per-second write limits a little, count this as
4054 having used up our write allocation for the second, and choke
4055 outgoing directory writes. Previously, we had only counted this when
4056 we had met our limits precisely. Fixes bug 824. Patch by rovv.
4057 Bugfix on 0.2.0.x (??).
4058 - Avoid a "0 divided by 0" calculation when calculating router uptime
4059 at directory authorities. Bugfix on 0.2.0.8-alpha.
4060 - Make DNS resolved controller events into "CLOSED", not
4061 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
4063 - Fix a bug where an unreachable relay would establish enough
4064 reachability testing circuits to do a bandwidth test -- if
4065 we already have a connection to the middle hop of the testing
4066 circuit, then it could establish the last hop by using the existing
4067 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
4068 circuits no longer use entry guards in 0.2.1.3-alpha.
4069 - If we have correct permissions on $datadir, we complain to stdout
4070 and fail to start. But dangerous permissions on
4071 $datadir/cached-status/ would cause us to open a log and complain
4072 there. Now complain to stdout and fail to start in both cases. Fixes
4073 bug 820, reported by seeess.
4074 - Remove the old v2 directory authority 'lefkada' from the default
4075 list. It has been gone for many months.
4077 o Code simplifications and refactoring:
4078 - Revise the connection_new functions so that a more typesafe variant
4079 exists. This will work better with Coverity, and let us find any
4080 actual mistakes we're making here.
4081 - Refactor unit testing logic so that dmalloc can be used sensibly
4082 with unit tests to check for memory leaks.
4083 - Move all hidden-service related fields from connection and circuit
4084 structure to substructures: this way they won't eat so much memory.
4087 Changes in version 0.2.0.31 - 2008-09-03
4088 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
4089 a big bug we're seeing where in rare cases traffic from one Tor stream
4090 gets mixed into another stream, and fixes a variety of smaller issues.
4093 - Make sure that two circuits can never exist on the same connection
4094 with the same circuit ID, even if one is marked for close. This
4095 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
4096 - Relays now reject risky extend cells: if the extend cell includes
4097 a digest of all zeroes, or asks to extend back to the relay that
4098 sent the extend cell, tear down the circuit. Ideas suggested
4100 - If not enough of our entry guards are available so we add a new
4101 one, we might use the new one even if it overlapped with the
4102 current circuit's exit relay (or its family). Anonymity bugfix
4103 pointed out by rovv.
4106 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
4107 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
4108 - Correctly detect the presence of the linux/netfilter_ipv4.h header
4109 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
4110 - Pick size of default geoip filename string correctly on windows.
4111 Fixes bug 806. Bugfix on 0.2.0.30.
4112 - Make the autoconf script accept the obsolete --with-ssl-dir
4113 option as an alias for the actually-working --with-openssl-dir
4114 option. Fix the help documentation to recommend --with-openssl-dir.
4115 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
4116 - When using the TransPort option on OpenBSD, and using the User
4117 option to change UID and drop privileges, make sure to open
4118 /dev/pf before dropping privileges. Fixes bug 782. Patch from
4119 Christopher Davis. Bugfix on 0.1.2.1-alpha.
4120 - Try to attach connections immediately upon receiving a RENDEZVOUS2
4121 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
4122 on the client side when connecting to a hidden service. Bugfix
4123 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
4124 - When closing an application-side connection because its circuit is
4125 getting torn down, generate the stream event correctly. Bugfix on
4126 0.1.2.x. Anonymous patch.
4129 Changes in version 0.2.1.5-alpha - 2008-08-31
4130 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
4131 in a lot of the infrastructure for adding authorization to hidden
4132 services, lays the groundwork for having clients read their load
4133 balancing information out of the networkstatus consensus rather than
4134 the individual router descriptors, addresses two potential anonymity
4135 issues, and fixes a variety of smaller issues.
4138 - Convert many internal address representations to optionally hold
4140 - Generate and accept IPv6 addresses in many protocol elements.
4141 - Make resolver code handle nameservers located at ipv6 addresses.
4142 - Begin implementation of proposal 121 ("Client authorization for
4143 hidden services"): configure hidden services with client
4144 authorization, publish descriptors for them, and configure
4145 authorization data for hidden services at clients. The next
4146 step is to actually access hidden services that perform client
4148 - More progress toward proposal 141: Network status consensus
4149 documents and votes now contain bandwidth information for each
4150 router and a summary of that router's exit policy. Eventually this
4151 will be used by clients so that they do not have to download every
4152 known descriptor before building circuits.
4154 o Major bugfixes (on 0.2.0.x and before):
4155 - When sending CREATED cells back for a given circuit, use a 64-bit
4156 connection ID to find the right connection, rather than an addr:port
4157 combination. Now that we can have multiple OR connections between
4158 the same ORs, it is no longer possible to use addr:port to uniquely
4159 identify a connection.
4160 - Relays now reject risky extend cells: if the extend cell includes
4161 a digest of all zeroes, or asks to extend back to the relay that
4162 sent the extend cell, tear down the circuit. Ideas suggested
4164 - If not enough of our entry guards are available so we add a new
4165 one, we might use the new one even if it overlapped with the
4166 current circuit's exit relay (or its family). Anonymity bugfix
4167 pointed out by rovv.
4170 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
4171 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
4172 - When using the TransPort option on OpenBSD, and using the User
4173 option to change UID and drop privileges, make sure to open /dev/pf
4174 before dropping privileges. Fixes bug 782. Patch from Christopher
4175 Davis. Bugfix on 0.1.2.1-alpha.
4176 - Correctly detect the presence of the linux/netfilter_ipv4.h header
4177 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
4178 - Add a missing safe_str() call for a debug log message.
4179 - Use 64 bits instead of 32 bits for connection identifiers used with
4180 the controller protocol, to greatly reduce risk of identifier reuse.
4181 - Make the autoconf script accept the obsolete --with-ssl-dir
4182 option as an alias for the actually-working --with-openssl-dir
4183 option. Fix the help documentation to recommend --with-openssl-dir.
4184 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
4187 - Rate-limit too-many-sockets messages: when they happen, they happen
4188 a lot. Resolves bug 748.
4189 - Resist DNS poisoning a little better by making sure that names in
4190 answer sections match.
4191 - Print the SOCKS5 error message string as well as the error code
4192 when a tor-resolve request fails. Patch from Jacob.
4195 Changes in version 0.2.1.4-alpha - 2008-08-04
4196 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
4199 - The address part of exit policies was not correctly written
4200 to router descriptors. This generated router descriptors that failed
4201 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
4203 - Tor triggered a false assert when extending a circuit to a relay
4204 but we already have a connection open to that relay. Noticed by
4205 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
4208 - Fix a hidden service logging bug: in some edge cases, the router
4209 descriptor of a previously picked introduction point becomes
4210 obsolete and we need to give up on it rather than continually
4211 complaining that it has become obsolete. Observed by xiando. Bugfix
4215 - Take out the TestVia config option, since it was a workaround for
4216 a bug that was fixed in Tor 0.1.1.21.
4219 Changes in version 0.2.1.3-alpha - 2008-08-03
4220 Tor 0.2.1.3-alpha implements most of the pieces to prevent
4221 infinite-length circuit attacks (see proposal 110); fixes a bug that
4222 might cause exit relays to corrupt streams they send back; allows
4223 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
4224 ExcludeExitNodes config options; and fixes a big pile of bugs.
4226 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
4227 - Send a bootstrap problem "warn" event on the first problem if the
4228 reason is NO_ROUTE (that is, our network is down).
4231 - Implement most of proposal 110: The first K cells to be sent
4232 along a circuit are marked as special "early" cells; only K "early"
4233 cells will be allowed. Once this code is universal, we can block
4234 certain kinds of DOS attack by requiring that EXTEND commands must
4235 be sent using an "early" cell.
4238 - Try to attach connections immediately upon receiving a RENDEZVOUS2
4239 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
4240 on the client side when connecting to a hidden service. Bugfix
4241 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
4242 - Ensure that two circuits can never exist on the same connection
4243 with the same circuit ID, even if one is marked for close. This
4244 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
4247 - When relays do their initial bandwidth measurement, don't limit
4248 to just our entry guards for the test circuits. Otherwise we tend
4249 to have multiple test circuits going through a single entry guard,
4250 which makes our bandwidth test less accurate. Fixes part of bug 654;
4251 patch contributed by Josh Albrecht.
4252 - Add an ExcludeExitNodes option so users can list a set of nodes
4253 that should be be excluded from the exit node position, but
4254 allowed elsewhere. Implements proposal 151.
4255 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
4256 ExcludeNodes and ExcludeExitNodes lists.
4257 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
4258 be more efficient. Formerly it was quadratic in the number of
4259 servers; now it should be linear. Fixes bug 509.
4260 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
4261 and n_conn_id_digest fields into a separate structure that's
4262 only needed when the circuit has not yet attached to an n_conn.
4265 - Change the contrib/tor.logrotate script so it makes the new
4266 logs as "_tor:_tor" rather than the default, which is generally
4267 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
4268 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
4269 warnings (occasionally), but it can also cause the compiler to
4270 eliminate error-checking code. Suggested by Peter Gutmann.
4271 - When a hidden service is giving up on an introduction point candidate
4272 that was not included in the last published rendezvous descriptor,
4273 don't reschedule publication of the next descriptor. Fixes bug 763.
4275 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
4276 HiddenServiceExcludeNodes as obsolete: they never worked properly,
4277 and nobody claims to be using them. Fixes bug 754. Bugfix on
4278 0.1.0.1-rc. Patch from Christian Wilms.
4279 - Fix a small alignment and memory-wasting bug on buffer chunks.
4282 o Minor bugfixes (controller):
4283 - When closing an application-side connection because its circuit
4284 is getting torn down, generate the stream event correctly.
4285 Bugfix on 0.1.2.x. Anonymous patch.
4288 - Remove all backward-compatibility code to support relays running
4289 versions of Tor so old that they no longer work at all on the
4293 Changes in version 0.2.0.30 - 2008-07-15
4295 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
4296 warnings (occasionally), but it can also cause the compiler to
4297 eliminate error-checking code. Suggested by Peter Gutmann.
4300 Changes in version 0.2.0.29-rc - 2008-07-08
4301 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
4302 hidden-service performance bugs, and fixes a bunch of smaller bugs.
4305 - If you have more than one bridge but don't know their keys,
4306 you would only launch a request for the descriptor of the first one
4307 on your list. (Tor considered launching requests for the others, but
4308 found that it already had a connection on the way for $0000...0000
4309 so it didn't open another.) Bugfix on 0.2.0.x.
4310 - If you have more than one bridge but don't know their keys, and the
4311 connection to one of the bridges failed, you would cancel all
4312 pending bridge connections. (After all, they all have the same
4313 digest.) Bugfix on 0.2.0.x.
4314 - When a hidden service was trying to establish an introduction point,
4315 and Tor had built circuits preemptively for such purposes, we
4316 were ignoring all the preemptive circuits and launching a new one
4317 instead. Bugfix on 0.2.0.14-alpha.
4318 - When a hidden service was trying to establish an introduction point,
4319 and Tor *did* manage to reuse one of the preemptively built
4320 circuits, it didn't correctly remember which one it used,
4321 so it asked for another one soon after, until there were no
4322 more preemptive circuits, at which point it launched one from
4323 scratch. Bugfix on 0.0.9.x.
4324 - Make directory servers include the X-Your-Address-Is: http header in
4325 their responses even for begin_dir conns. Now clients who only
4326 ever use begin_dir connections still have a way to learn their IP
4327 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
4330 - Fix a macro/CPP interaction that was confusing some compilers:
4331 some GCCs don't like #if/#endif pairs inside macro arguments.
4333 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
4334 Fixes bug 704; fix from Steven Murdoch.
4335 - When opening /dev/null in finish_daemonize(), do not pass the
4336 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
4337 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
4338 - Correctly detect transparent proxy support on Linux hosts that
4339 require in.h to be included before netfilter_ipv4.h. Patch
4341 - Disallow session resumption attempts during the renegotiation
4342 stage of the v2 handshake protocol. Clients should never be trying
4343 session resumption at this point, but apparently some did, in
4344 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
4345 found by Geoff Goodell.
4348 Changes in version 0.2.1.2-alpha - 2008-06-20
4349 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
4350 make it easier to set up your own private Tor network; fixes several
4351 big bugs with using more than one bridge relay; fixes a big bug with
4352 offering hidden services quickly after Tor starts; and uses a better
4353 API for reporting potential bootstrapping problems to the controller.
4356 - New TestingTorNetwork config option to allow adjustment of
4357 previously constant values that, while reasonable, could slow
4358 bootstrapping. Implements proposal 135. Patch from Karsten.
4361 - If you have more than one bridge but don't know their digests,
4362 you would only learn a request for the descriptor of the first one
4363 on your list. (Tor considered launching requests for the others, but
4364 found that it already had a connection on the way for $0000...0000
4365 so it didn't open another.) Bugfix on 0.2.0.x.
4366 - If you have more than one bridge but don't know their digests,
4367 and the connection to one of the bridges failed, you would cancel
4368 all pending bridge connections. (After all, they all have the
4369 same digest.) Bugfix on 0.2.0.x.
4370 - When establishing a hidden service, introduction points that
4371 originate from cannibalized circuits are completely ignored and not
4372 included in rendezvous service descriptors. This might be another
4373 reason for delay in making a hidden service available. Bugfix
4374 from long ago (0.0.9.x?)
4377 - Allow OpenSSL to use dynamic locks if it wants.
4378 - When building a consensus, do not include routers that are down.
4379 This will cut down 30% to 40% on consensus size. Implements
4381 - In directory authorities' approved-routers files, allow
4382 fingerprints with or without space.
4383 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
4384 controller can query our current bootstrap state in case it attaches
4385 partway through and wants to catch up.
4386 - Send an initial "Starting" bootstrap status event, so we have a
4387 state to start out in.
4390 - Asking for a conditional consensus at .../consensus/<fingerprints>
4391 would crash a dirserver if it did not already have a
4392 consensus. Bugfix on 0.2.1.1-alpha.
4393 - Clean up some macro/CPP interactions: some GCC versions don't like
4394 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
4397 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
4398 - Directory authorities shouldn't complain about bootstrapping
4399 problems just because they do a lot of reachability testing and
4400 some of the connection attempts fail.
4401 - Start sending "count" and "recommendation" key/value pairs in
4402 bootstrap problem status events, so the controller can hear about
4403 problems even before Tor decides they're worth reporting for sure.
4404 - If you're using bridges, generate "bootstrap problem" warnings
4405 as soon as you run out of working bridges, rather than waiting
4406 for ten failures -- which will never happen if you have less than
4408 - If we close our OR connection because there's been a circuit
4409 pending on it for too long, we were telling our bootstrap status
4410 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
4413 Changes in version 0.2.1.1-alpha - 2008-06-13
4414 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
4415 were making the Tor process bloat especially on Linux; makes our TLS
4416 handshake blend in better; sends "bootstrap phase" status events to
4417 the controller, so it can keep the user informed of progress (and
4418 problems) fetching directory information and establishing circuits;
4419 and adds a variety of smaller features.
4422 - More work on making our TLS handshake blend in: modify the list
4423 of ciphers advertised by OpenSSL in client mode to even more
4424 closely resemble a common web browser. We cheat a little so that
4425 we can advertise ciphers that the locally installed OpenSSL doesn't
4427 - Start sending "bootstrap phase" status events to the controller,
4428 so it can keep the user informed of progress fetching directory
4429 information and establishing circuits. Also inform the controller
4430 if we think we're stuck at a particular bootstrap phase. Implements
4432 - Resume using OpenSSL's RAND_poll() for better (and more portable)
4433 cross-platform entropy collection again. We used to use it, then
4434 stopped using it because of a bug that could crash systems that
4435 called RAND_poll when they had a lot of fds open. It looks like the
4436 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
4437 at startup, and to call RAND_poll() when we reseed later only if
4438 we have a non-buggy OpenSSL version.
4441 - When we choose to abandon a new entry guard because we think our
4442 older ones might be better, close any circuits pending on that
4443 new entry guard connection. This fix should make us recover much
4444 faster when our network is down and then comes back. Bugfix on
4445 0.1.2.8-beta; found by lodger.
4447 o Memory fixes and improvements:
4448 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
4449 to avoid unused RAM in buffer chunks and memory pools.
4450 - Speed up parsing and cut down on memory fragmentation by using
4451 stack-style allocations for parsing directory objects. Previously,
4452 this accounted for over 40% of allocations from within Tor's code
4453 on a typical directory cache.
4454 - Use a Bloom filter rather than a digest-based set to track which
4455 descriptors we need to keep around when we're cleaning out old
4456 router descriptors. This speeds up the computation significantly,
4457 and may reduce fragmentation.
4458 - Reduce the default smartlist size from 32 to 16; it turns out that
4459 most smartlists hold around 8-12 elements tops.
4460 - Make dumpstats() log the fullness and size of openssl-internal
4462 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
4463 patch to their OpenSSL, turn it on to save memory on servers. This
4464 patch will (with any luck) get included in a mainline distribution
4466 - Never use OpenSSL compression: it wastes RAM and CPU trying to
4467 compress cells, which are basically all encrypted, compressed,
4471 - Stop reloading the router list from disk for no reason when we
4472 run out of reachable directory mirrors. Once upon a time reloading
4473 it would set the 'is_running' flag back to 1 for them. It hasn't
4474 done that for a long time.
4475 - In very rare situations new hidden service descriptors were
4476 published earlier than 30 seconds after the last change to the
4477 service. (We currently think that a hidden service descriptor
4478 that's been stable for 30 seconds is worth publishing.)
4481 - Allow separate log levels to be configured for different logging
4482 domains. For example, this allows one to log all notices, warnings,
4483 or errors, plus all memory management messages of level debug or
4484 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
4485 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
4486 and stop using a warning that had become unfixably verbose under
4488 - New --hush command-line option similar to --quiet. While --quiet
4489 disables all logging to the console on startup, --hush limits the
4490 output to messages of warning and error severity.
4491 - Servers support a new URL scheme for consensus downloads that
4492 allows the client to specify which authorities are trusted.
4493 The server then only sends the consensus if the client will trust
4494 it. Otherwise a 404 error is sent back. Clients use this
4495 new scheme when the server supports it (meaning it's running
4496 0.2.1.1-alpha or later). Implements proposal 134.
4497 - New configure/torrc options (--enable-geoip-stats,
4498 DirRecordUsageByCountry) to record how many IPs we've served
4499 directory info to in each country code, how many status documents
4500 total we've sent to each country code, and what share of the total
4501 directory requests we should expect to see.
4502 - Use the TLS1 hostname extension to more closely resemble browser
4504 - Lots of new unit tests.
4505 - Add a macro to implement the common pattern of iterating through
4506 two parallel lists in lockstep.
4509 Changes in version 0.2.0.28-rc - 2008-06-13
4510 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
4511 performance bug, and fixes a bunch of smaller bugs.
4514 - Fix a bug where, when we were choosing the 'end stream reason' to
4515 put in our relay end cell that we send to the exit relay, Tor
4516 clients on Windows were sometimes sending the wrong 'reason'. The
4517 anonymity problem is that exit relays may be able to guess whether
4518 the client is running Windows, thus helping partition the anonymity
4519 set. Down the road we should stop sending reasons to exit relays,
4520 or otherwise prevent future versions of this bug.
4523 - While setting up a hidden service, some valid introduction circuits
4524 were overlooked and abandoned. This might be the reason for
4525 the long delay in making a hidden service available. Bugfix on
4529 - Update to the "June 9 2008" ip-to-country file.
4530 - Run 'make test' as part of 'make dist', so we stop releasing so
4531 many development snapshots that fail their unit tests.
4534 - When we're checking if we have enough dir info for each relay
4535 to begin establishing circuits, make sure that we actually have
4536 the descriptor listed in the consensus, not just any descriptor.
4538 - Bridge relays no longer print "xx=0" in their extrainfo document
4539 for every single country code in the geoip db. Bugfix on
4541 - Only warn when we fail to load the geoip file if we were planning to
4542 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
4543 - If we change our MaxAdvertisedBandwidth and then reload torrc,
4544 Tor won't realize it should publish a new relay descriptor. Fixes
4545 bug 688, reported by mfr. Bugfix on 0.1.2.x.
4546 - When we haven't had any application requests lately, don't bother
4547 logging that we have expired a bunch of descriptors. Bugfix
4549 - Make relay cells written on a connection count as non-padding when
4550 tracking how long a connection has been in use. Bugfix on
4551 0.2.0.1-alpha. Spotted by lodger.
4552 - Fix unit tests in 0.2.0.27-rc.
4553 - Fix compile on Windows.
4556 Changes in version 0.2.0.27-rc - 2008-06-03
4557 Tor 0.2.0.27-rc adds a few features we left out of the earlier
4558 release candidates. In particular, we now include an IP-to-country
4559 GeoIP database, so controllers can easily look up what country a
4560 given relay is in, and so bridge relays can give us some sanitized
4561 summaries about which countries are making use of bridges. (See proposal
4562 126-geoip-fetching.txt for details.)
4565 - Include an IP-to-country GeoIP file in the tarball, so bridge
4566 relays can report sanitized summaries of the usage they're seeing.
4569 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
4570 Robert Hogan. Fixes the first part of bug 681.
4571 - Make bridge authorities never serve extrainfo docs.
4572 - Add support to detect Libevent versions in the 1.4.x series
4574 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
4575 - Include a new contrib/tor-exit-notice.html file that exit relay
4576 operators can put on their website to help reduce abuse queries.
4579 - When tunneling an encrypted directory connection, and its first
4580 circuit fails, do not leave it unattached and ask the controller
4581 to deal. Fixes the second part of bug 681.
4582 - Make bridge authorities correctly expire old extrainfo documents
4586 Changes in version 0.2.0.26-rc - 2008-05-13
4587 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
4588 in Debian's OpenSSL packages. All users running any 0.2.0.x version
4589 should upgrade, whether they're running Debian or not.
4591 o Major security fixes:
4592 - Use new V3 directory authority keys on the tor26, gabelmoo, and
4593 moria1 V3 directory authorities. The old keys were generated with
4594 a vulnerable version of Debian's OpenSSL package, and must be
4595 considered compromised. Other authorities' keys were not generated
4596 with an affected version of OpenSSL.
4599 - List authority signatures as "unrecognized" based on DirServer
4600 lines, not on cert cache. Bugfix on 0.2.0.x.
4603 - Add a new V3AuthUseLegacyKey option to make it easier for
4604 authorities to change their identity keys if they have to.
4607 Changes in version 0.2.0.25-rc - 2008-04-23
4608 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
4611 - Remember to initialize threading before initializing logging.
4612 Otherwise, many BSD-family implementations will crash hard on
4613 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
4616 - Authorities correctly free policies on bad servers on
4617 exit. Fixes bug 672. Bugfix on 0.2.0.x.
4620 Changes in version 0.2.0.24-rc - 2008-04-22
4621 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
4622 v3 directory authority, makes relays with dynamic IP addresses and no
4623 DirPort notice more quickly when their IP address changes, fixes a few
4624 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
4626 o New directory authorities:
4627 - Take lefkada out of the list of v3 directory authorities, since
4628 it has been down for months.
4629 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
4633 - Detect address changes more quickly on non-directory mirror
4634 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
4636 o Minor features (security):
4637 - Reject requests for reverse-dns lookup of names that are in
4638 a private address space. Patch from lodger.
4639 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
4642 o Minor bugfixes (crashes):
4643 - Avoid a rare assert that can trigger when Tor doesn't have much
4644 directory information yet and it tries to fetch a v2 hidden
4645 service descriptor. Fixes bug 651, reported by nwf.
4646 - Initialize log mutex before initializing dmalloc. Otherwise,
4647 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
4648 - Use recursive pthread mutexes in order to avoid deadlock when
4649 logging debug-level messages to a controller. Bug spotted by nwf,
4650 bugfix on 0.2.0.16-alpha.
4652 o Minor bugfixes (resource management):
4653 - Keep address policies from leaking memory: start their refcount
4654 at 1, not 2. Bugfix on 0.2.0.16-alpha.
4655 - Free authority certificates on exit, so they don't look like memory
4656 leaks. Bugfix on 0.2.0.19-alpha.
4657 - Free static hashtables for policy maps and for TLS connections on
4658 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
4659 - Avoid allocating extra space when computing consensuses on 64-bit
4660 platforms. Bug spotted by aakova.
4662 o Minor bugfixes (misc):
4663 - Do not read the configuration file when we've only been told to
4664 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
4665 based on patch from Sebastian Hahn.
4666 - Exit relays that are used as a client can now reach themselves
4667 using the .exit notation, rather than just launching an infinite
4668 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
4669 - When attempting to open a logfile fails, tell us why.
4670 - Fix a dumb bug that was preventing us from knowing that we should
4671 preemptively build circuits to handle expected directory requests.
4672 Fixes bug 660. Bugfix on 0.1.2.x.
4673 - Warn less verbosely about clock skew from netinfo cells from
4674 untrusted sources. Fixes bug 663.
4675 - Make controller stream events for DNS requests more consistent,
4676 by adding "new stream" events for DNS requests, and removing
4677 spurious "stream closed" events" for cached reverse resolves.
4678 Patch from mwenge. Fixes bug 646.
4679 - Correctly notify one-hop connections when a circuit build has
4680 failed. Possible fix for bug 669. Found by lodger.
4683 Changes in version 0.2.0.23-rc - 2008-03-24
4684 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
4685 makes bootstrapping faster if the first directory mirror you contact
4686 is down. The bundles also include the new Vidalia 0.1.2 release.
4689 - When a tunneled directory request is made to a directory server
4690 that's down, notice after 30 seconds rather than 120 seconds. Also,
4691 fail any begindir streams that are pending on it, so they can
4692 retry elsewhere. This was causing multi-minute delays on bootstrap.
4695 Changes in version 0.2.0.22-rc - 2008-03-18
4696 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
4697 enables encrypted directory connections by default for non-relays, fixes
4698 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
4699 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
4702 - Enable encrypted directory connections by default for non-relays,
4703 so censor tools that block Tor directory connections based on their
4704 plaintext patterns will no longer work. This means Tor works in
4705 certain censored countries by default again.
4708 - Make sure servers always request certificates from clients during
4709 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
4710 - Do not enter a CPU-eating loop when a connection is closed in
4711 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
4712 diagnosed by lodger; bugfix on 0.2.0.20-rc.
4713 - Fix assertion failure that could occur when a blocked circuit
4714 became unblocked, and it had pending client DNS requests. Bugfix
4715 on 0.2.0.1-alpha. Fixes bug 632.
4717 o Minor bugfixes (on 0.1.2.x):
4718 - Generate "STATUS_SERVER" events rather than misspelled
4719 "STATUS_SEVER" events. Caught by mwenge.
4720 - When counting the number of bytes written on a TLS connection,
4721 look at the BIO actually used for writing to the network, not
4722 at the BIO used (sometimes) to buffer data for the network.
4723 Looking at different BIOs could result in write counts on the
4724 order of ULONG_MAX. Fixes bug 614.
4725 - On Windows, correctly detect errors when listing the contents of
4726 a directory. Fix from lodger.
4728 o Minor bugfixes (on 0.2.0.x):
4729 - Downgrade "sslv3 alert handshake failure" message to INFO.
4730 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
4731 left BandwidthRate and BandwidthBurst at the default, we would be
4732 silently limited by those defaults. Now raise them to match the
4733 RelayBandwidth* values.
4734 - Fix the SVK version detection logic to work correctly on a branch.
4735 - Make --enable-openbsd-malloc work correctly on Linux with alpha
4736 CPUs. Fixes bug 625.
4737 - Logging functions now check that the passed severity is sane.
4738 - Use proper log levels in the testsuite call of
4739 get_interface_address6().
4740 - When using a nonstandard malloc, do not use the platform values for
4741 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
4742 - Make the openbsd malloc code use 8k pages on alpha CPUs and
4744 - Detect mismatched page sizes when using --enable-openbsd-malloc.
4745 - Avoid double-marked-for-close warning when certain kinds of invalid
4746 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
4747 for bug 617. Bugfix on 0.2.0.1-alpha.
4748 - Make sure that the "NULL-means-reject *:*" convention is followed by
4749 all the policy manipulation functions, avoiding some possible crash
4750 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
4751 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
4752 actually works, and doesn't warn about every single reverse lookup.
4753 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
4756 - Only log guard node status when guard node status has changed.
4757 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
4758 make "INFO" 75% less verbose.
4761 Changes in version 0.2.0.21-rc - 2008-03-02
4762 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
4763 makes Tor work well with Vidalia again, fixes a rare assert bug,
4764 and fixes a pair of more minor bugs. The bundles also include Vidalia
4765 0.1.0 and Torbutton 1.1.16.
4768 - The control port should declare that it requires password auth
4769 when HashedControlSessionPassword is set too. Patch from Matt Edman;
4770 bugfix on 0.2.0.20-rc. Fixes bug 615.
4771 - Downgrade assert in connection_buckets_decrement() to a log message.
4772 This may help us solve bug 614, and in any case will make its
4773 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
4774 - We were sometimes miscounting the number of bytes read from the
4775 network, causing our rate limiting to not be followed exactly.
4776 Bugfix on 0.2.0.16-alpha. Reported by lodger.
4779 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
4780 OpenSSL versions should have been working fine. Diagnosis and patch
4781 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
4782 Bugfix on 0.2.0.20-rc.
4785 Changes in version 0.2.0.20-rc - 2008-02-24
4786 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
4787 makes more progress towards normalizing Tor's TLS handshake, makes
4788 hidden services work better again, helps relays bootstrap if they don't
4789 know their IP address, adds optional support for linking in openbsd's
4790 allocator or tcmalloc, allows really fast relays to scale past 15000
4791 sockets, and fixes a bunch of minor bugs reported by Veracode.
4794 - Enable the revised TLS handshake based on the one designed by
4795 Steven Murdoch in proposal 124, as revised in proposal 130. It
4796 includes version negotiation for OR connections as described in
4797 proposal 105. The new handshake is meant to be harder for censors
4798 to fingerprint, and it adds the ability to detect certain kinds of
4799 man-in-the-middle traffic analysis attacks. The version negotiation
4800 feature will allow us to improve Tor's link protocol more safely
4802 - Choose which bridge to use proportional to its advertised bandwidth,
4803 rather than uniformly at random. This should speed up Tor for
4804 bridge users. Also do this for people who set StrictEntryNodes.
4805 - When a TrackHostExits-chosen exit fails too many times in a row,
4806 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
4809 - Resolved problems with (re-)fetching hidden service descriptors.
4810 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
4812 - If we only ever used Tor for hidden service lookups or posts, we
4813 would stop building circuits and start refusing connections after
4814 24 hours, since we falsely believed that Tor was dormant. Reported
4815 by nwf; bugfix on 0.1.2.x.
4816 - Servers that don't know their own IP address should go to the
4817 authorities for their first directory fetch, even if their DirPort
4818 is off or if they don't know they're reachable yet. This will help
4819 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
4820 - When counting the number of open sockets, count not only the number
4821 of sockets we have received from the socket() call, but also
4822 the number we've gotten from accept() and socketpair(). This bug
4823 made us fail to count all sockets that we were using for incoming
4824 connections. Bugfix on 0.2.0.x.
4825 - Fix code used to find strings within buffers, when those strings
4826 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
4827 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
4828 - Add a new __HashedControlSessionPassword option for controllers
4829 to use for one-off session password hashes that shouldn't get
4830 saved to disk by SAVECONF --- Vidalia users were accumulating a
4831 pile of HashedControlPassword lines in their torrc files, one for
4832 each time they had restarted Tor and then clicked Save. Make Tor
4833 automatically convert "HashedControlPassword" to this new option but
4834 only when it's given on the command line. Partial fix for bug 586.
4836 o Minor features (performance):
4837 - Tune parameters for cell pool allocation to minimize amount of
4839 - Add OpenBSD malloc code from phk as an optional malloc
4840 replacement on Linux: some glibc libraries do very poorly
4841 with Tor's memory allocation patterns. Pass
4842 --enable-openbsd-malloc to get the replacement malloc code.
4843 - Add a --with-tcmalloc option to the configure script to link
4844 against tcmalloc (if present). Does not yet search for
4845 non-system include paths.
4846 - Stop imposing an arbitrary maximum on the number of file descriptors
4847 used for busy servers. Bug reported by Olaf Selke; patch from
4850 o Minor features (other):
4851 - When SafeLogging is disabled, log addresses along with all TLS
4853 - When building with --enable-gcc-warnings, check for whether Apple's
4854 warning "-Wshorten-64-to-32" is available.
4855 - Add a --passphrase-fd argument to the tor-gencert command for
4858 o Minor bugfixes (memory leaks and code problems):
4859 - We were leaking a file descriptor if Tor started with a zero-length
4860 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
4861 - Detect size overflow in zlib code. Reported by Justin Ferguson and
4863 - We were comparing the raw BridgePassword entry with a base64'ed
4864 version of it, when handling a "/tor/networkstatus-bridges"
4865 directory request. Now compare correctly. Noticed by Veracode.
4866 - Recover from bad tracked-since value in MTBF-history file.
4868 - Alter the code that tries to recover from unhandled write
4869 errors, to not try to flush onto a socket that's given us
4870 unhandled errors. Bugfix on 0.1.2.x.
4871 - Make Unix controlsockets work correctly on OpenBSD. Patch from
4872 tup. Bugfix on 0.2.0.3-alpha.
4874 o Minor bugfixes (other):
4875 - If we have an extra-info document for our server, always make
4876 it available on the control port, even if we haven't gotten
4877 a copy of it from an authority yet. Patch from mwenge.
4878 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
4879 - Directory mirrors no longer include a guess at the client's IP
4880 address if the connection appears to be coming from the same /24
4881 network; it was producing too many wrong guesses.
4882 - Make the new hidden service code respect the SafeLogging setting.
4883 Bugfix on 0.2.0.x. Patch from Karsten.
4884 - When starting as an authority, do not overwrite all certificates
4885 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
4886 - If we're trying to flush the last bytes on a connection (for
4887 example, when answering a directory request), reset the
4888 time-to-give-up timeout every time we manage to write something
4889 on the socket. Bugfix on 0.1.2.x.
4890 - Change the behavior of "getinfo status/good-server-descriptor"
4891 so it doesn't return failure when any authority disappears.
4892 - Even though the man page said that "TrackHostExits ." should
4893 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
4894 - Report TLS "zero return" case as a "clean close" and "IO error"
4895 as a "close". Stop calling closes "unexpected closes": existing
4896 Tors don't use SSL_close(), so having a connection close without
4897 the TLS shutdown handshake is hardly unexpected.
4898 - Send NAMESERVER_STATUS messages for a single failed nameserver
4901 o Code simplifications and refactoring:
4902 - Remove the tor_strpartition function: its logic was confused,
4903 and it was only used for one thing that could be implemented far
4907 Changes in version 0.2.0.19-alpha - 2008-02-09
4908 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
4909 handshake, makes path selection for relays more secure and IP address
4910 guessing more robust, and generally fixes a lot of bugs in preparation
4911 for calling the 0.2.0 branch stable.
4914 - Do not include recognizeable strings in the commonname part of
4915 Tor's x509 certificates.
4918 - If we're a relay, avoid picking ourselves as an introduction point,
4919 a rendezvous point, or as the final hop for internal circuits. Bug
4920 reported by taranis and lodger. Bugfix on 0.1.2.x.
4921 - Patch from "Andrew S. Lists" to catch when we contact a directory
4922 mirror at IP address X and he says we look like we're coming from
4923 IP address X. Bugfix on 0.1.2.x.
4925 o Minor features (security):
4926 - Be more paranoid about overwriting sensitive memory on free(),
4927 as a defensive programming tactic to ensure forward secrecy.
4929 o Minor features (directory authority):
4930 - Actually validate the options passed to AuthDirReject,
4931 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
4932 - Reject router descriptors with out-of-range bandwidthcapacity or
4933 bandwidthburst values.
4935 o Minor features (controller):
4936 - Reject controller commands over 1MB in length. This keeps rogue
4937 processes from running us out of memory.
4939 o Minor features (misc):
4940 - Give more descriptive well-formedness errors for out-of-range
4941 hidden service descriptor/protocol versions.
4942 - Make memory debugging information describe more about history
4943 of cell allocation, so we can help reduce our memory use.
4945 o Deprecated features (controller):
4946 - The status/version/num-versioning and status/version/num-concurring
4947 GETINFO options are no longer useful in the v3 directory protocol:
4948 treat them as deprecated, and warn when they're used.
4951 - When our consensus networkstatus has been expired for a while, stop
4952 being willing to build circuits using it. Fixes bug 401. Bugfix
4954 - Directory caches now fetch certificates from all authorities
4955 listed in a networkstatus consensus, even when they do not
4956 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
4957 - When connecting to a bridge without specifying its key, insert
4958 the connection into the identity-to-connection map as soon as
4959 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
4960 - Detect versions of OS X where malloc_good_size() is present in the
4961 library but never actually declared. Resolves bug 587. Bugfix
4963 - Stop incorrectly truncating zlib responses to directory authority
4964 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
4965 - Stop recommending that every server operator send mail to tor-ops.
4966 Resolves bug 597. Bugfix on 0.1.2.x.
4967 - Don't trigger an assert if we start a directory authority with a
4968 private IP address (like 127.0.0.1).
4969 - Avoid possible failures when generating a directory with routers
4970 with over-long versions strings, or too many flags set. Bugfix
4972 - If an attempt to launch a DNS resolve request over the control
4973 port fails because we have overrun the limit on the number of
4974 connections, tell the controller that the request has failed.
4975 - Avoid using too little bandwidth when our clock skips a few
4976 seconds. Bugfix on 0.1.2.x.
4977 - Fix shell error when warning about missing packages in configure
4978 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
4979 - Do not become confused when receiving a spurious VERSIONS-like
4980 cell from a confused v1 client. Bugfix on 0.2.0.x.
4981 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
4982 introduction points for a hidden service have failed. Patch from
4983 Karsten Loesing. Bugfix on 0.2.0.x.
4985 o Code simplifications and refactoring:
4986 - Remove some needless generality from cpuworker code, for improved
4988 - Stop overloading the circuit_t.onionskin field for both "onionskin
4989 from a CREATE cell that we are waiting for a cpuworker to be
4990 assigned" and "onionskin from an EXTEND cell that we are going to
4991 send to an OR as soon as we are connected". Might help with bug 600.
4992 - Add an in-place version of aes_crypt() so that we can avoid doing a
4993 needless memcpy() call on each cell payload.
4996 Changes in version 0.2.0.18-alpha - 2008-01-25
4997 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
4998 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
4999 that can warn or reject connections to ports generally associated with
5000 vulnerable-plaintext protocols.
5002 o New directory authorities:
5003 - Set up dannenberg (run by CCC) as the sixth v3 directory
5007 - Fix a major memory leak when attempting to use the v2 TLS
5008 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
5009 - We accidentally enabled the under-development v2 TLS handshake
5010 code, which was causing log entries like "TLS error while
5011 renegotiating handshake". Disable it again. Resolves bug 590.
5012 - We were computing the wrong Content-Length: header for directory
5013 responses that need to be compressed on the fly, causing clients
5014 asking for those items to always fail. Bugfix on 0.2.0.x; partially
5018 - Avoid going directly to the directory authorities even if you're a
5019 relay, if you haven't found yourself reachable yet or if you've
5020 decided not to advertise your dirport yet. Addresses bug 556.
5021 - If we've gone 12 hours since our last bandwidth check, and we
5022 estimate we have less than 50KB bandwidth capacity but we could
5023 handle more, do another bandwidth test.
5024 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
5025 Tor can warn and/or refuse connections to ports commonly used with
5026 vulnerable-plaintext protocols. Currently we warn on ports 23,
5027 109, 110, and 143, but we don't reject any.
5030 - When we setconf ClientOnly to 1, close any current OR and Dir
5031 listeners. Reported by mwenge.
5032 - When we get a consensus that's been signed by more people than
5033 we expect, don't log about it; it's not a big deal. Reported
5037 - Don't answer "/tor/networkstatus-bridges" directory requests if
5038 the request isn't encrypted.
5039 - Make "ClientOnly 1" config option disable directory ports too.
5040 - Patches from Karsten Loesing to make v2 hidden services more
5041 robust: work even when there aren't enough HSDir relays available;
5042 retry when a v2 rend desc fetch fails; but don't retry if we
5043 already have a usable v0 rend desc.
5046 Changes in version 0.2.0.17-alpha - 2008-01-17
5047 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
5050 - Make the tor-gencert man page get included correctly in the tarball.
5053 Changes in version 0.2.0.16-alpha - 2008-01-17
5054 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
5055 Loesing, and generally cleans up a lot of features and minor bugs.
5057 o New directory authorities:
5058 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
5061 o Major performance improvements:
5062 - Switch our old ring buffer implementation for one more like that
5063 used by free Unix kernels. The wasted space in a buffer with 1mb
5064 of data will now be more like 8k than 1mb. The new implementation
5065 also avoids realloc();realloc(); patterns that can contribute to
5066 memory fragmentation.
5069 - Configuration files now accept C-style strings as values. This
5070 helps encode characters not allowed in the current configuration
5071 file format, such as newline or #. Addresses bug 557.
5072 - Although we fixed bug 539 (where servers would send HTTP status 503
5073 responses _and_ send a body too), there are still servers out
5074 there that haven't upgraded. Therefore, make clients parse such
5075 bodies when they receive them.
5076 - When we're not serving v2 directory information, there is no reason
5077 to actually keep any around. Remove the obsolete files and directory
5078 on startup if they are very old and we aren't going to serve them.
5080 o Minor performance improvements:
5081 - Reference-count and share copies of address policy entries; only 5%
5082 of them were actually distinct.
5083 - Never walk through the list of logs if we know that no log is
5084 interested in a given message.
5087 - When an authority has not signed a consensus, do not try to
5088 download a nonexistent "certificate with key 00000000". Bugfix
5089 on 0.2.0.x. Fixes bug 569.
5090 - Fix a rare assert error when we're closing one of our threads:
5091 use a mutex to protect the list of logs, so we never write to the
5092 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
5093 bug 575, which is kind of the revenge of bug 222.
5094 - Patch from Karsten Loesing to complain less at both the client
5095 and the relay when a relay used to have the HSDir flag but doesn't
5096 anymore, and we try to upload a hidden service descriptor.
5097 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
5099 - Do not try to download missing certificates until we have tried
5100 to check our fallback consensus. Fixes bug 583.
5101 - Make bridges round reported GeoIP stats info up to the nearest
5102 estimate, not down. Now we can distinguish between "0 people from
5103 this country" and "1 person from this country".
5104 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
5105 - Avoid possible segfault if key generation fails in
5106 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
5107 - Avoid segfault in the case where a badly behaved v2 versioning
5108 directory sends a signed networkstatus with missing client-versions.
5110 - Avoid segfaults on certain complex invocations of
5111 router_get_by_hexdigest(). Bugfix on 0.1.2.
5112 - Correct bad index on array access in parse_http_time(). Bugfix
5114 - Fix possible bug in vote generation when server versions are present
5115 but client versions are not.
5116 - Fix rare bug on REDIRECTSTREAM control command when called with no
5117 port set: it could erroneously report an error when none had
5119 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
5120 compressing large objects and find ourselves with more than 4k
5121 left over. Bugfix on 0.2.0.
5122 - Fix a small memory leak when setting up a hidden service.
5123 - Fix a few memory leaks that could in theory happen under bizarre
5125 - Fix an assert if we post a general-purpose descriptor via the
5126 control port but that descriptor isn't mentioned in our current
5127 network consensus. Bug reported by Jon McLachlan; bugfix on
5130 o Minor features (controller):
5131 - Get NS events working again. Patch from tup.
5132 - The GETCONF command now escapes and quotes configuration values
5133 that don't otherwise fit into the torrc file.
5134 - The SETCONF command now handles quoted values correctly.
5136 o Minor features (directory authorities):
5137 - New configuration options to override default maximum number of
5138 servers allowed on a single IP address. This is important for
5139 running a test network on a single host.
5140 - Actually implement the -s option to tor-gencert.
5141 - Add a manual page for tor-gencert.
5143 o Minor features (bridges):
5144 - Bridge authorities no longer serve bridge descriptors over
5145 unencrypted connections.
5147 o Minor features (other):
5148 - Add hidden services and DNSPorts to the list of things that make
5149 Tor accept that it has running ports. Change starting Tor with no
5150 ports from a fatal error to a warning; we might change it back if
5151 this turns out to confuse anybody. Fixes bug 579.
5154 Changes in version 0.1.2.19 - 2008-01-17
5155 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
5156 exit policy a little bit more conservative so it's safer to run an
5157 exit relay on a home system, and fixes a variety of smaller issues.
5160 - Exit policies now reject connections that are addressed to a
5161 relay's public (external) IP address too, unless
5162 ExitPolicyRejectPrivate is turned off. We do this because too
5163 many relays are running nearby to services that trust them based
5167 - When the clock jumps forward a lot, do not allow the bandwidth
5168 buckets to become negative. Fixes bug 544.
5169 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
5170 on every successful resolve. Reported by Mike Perry.
5171 - Purge old entries from the "rephist" database and the hidden
5172 service descriptor database even when DirPort is zero.
5173 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
5174 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
5175 crashing or mis-answering these requests.
5176 - When we decide to send a 503 response to a request for servers, do
5177 not then also send the server descriptors: this defeats the whole
5178 purpose. Fixes bug 539.
5181 - Changing the ExitPolicyRejectPrivate setting should cause us to
5182 rebuild our server descriptor.
5183 - Fix handling of hex nicknames when answering controller requests for
5184 networkstatus by name, or when deciding whether to warn about
5185 unknown routers in a config option. (Patch from mwenge.)
5186 - Fix a couple of hard-to-trigger autoconf problems that could result
5187 in really weird results on platforms whose sys/types.h files define
5188 nonstandard integer types.
5189 - Don't try to create the datadir when running --verify-config or
5190 --hash-password. Resolves bug 540.
5191 - If we were having problems getting a particular descriptor from the
5192 directory caches, and then we learned about a new descriptor for
5193 that router, we weren't resetting our failure count. Reported
5195 - Although we fixed bug 539 (where servers would send HTTP status 503
5196 responses _and_ send a body too), there are still servers out there
5197 that haven't upgraded. Therefore, make clients parse such bodies
5198 when they receive them.
5199 - Run correctly on systems where rlim_t is larger than unsigned long.
5200 This includes some 64-bit systems.
5201 - Run correctly on platforms (like some versions of OS X 10.5) where
5202 the real limit for number of open files is OPEN_FILES, not rlim_max
5203 from getrlimit(RLIMIT_NOFILES).
5204 - Avoid a spurious free on base64 failure.
5205 - Avoid segfaults on certain complex invocations of
5206 router_get_by_hexdigest().
5207 - Fix rare bug on REDIRECTSTREAM control command when called with no
5208 port set: it could erroneously report an error when none had
5212 Changes in version 0.2.0.15-alpha - 2007-12-25
5213 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
5214 features added in 0.2.0.13-alpha.
5217 - Fix several remotely triggerable asserts based on DirPort requests
5218 for a v2 or v3 networkstatus object before we were prepared. This
5219 was particularly bad for 0.2.0.13 and later bridge relays, who
5220 would never have a v2 networkstatus and would thus always crash
5221 when used. Bugfixes on 0.2.0.x.
5222 - Estimate the v3 networkstatus size more accurately, rather than
5223 estimating it at zero bytes and giving it artificially high priority
5224 compared to other directory requests. Bugfix on 0.2.0.x.
5227 - Fix configure.in logic for cross-compilation.
5228 - When we load a bridge descriptor from the cache, and it was
5229 previously unreachable, mark it as retriable so we won't just
5230 ignore it. Also, try fetching a new copy immediately. Bugfixes
5232 - The bridge GeoIP stats were counting other relays, for example
5233 self-reachability and authority-reachability tests.
5236 - Support compilation to target iPhone; patch from cjacker huang.
5237 To build for iPhone, pass the --enable-iphone option to configure.
5240 Changes in version 0.2.0.14-alpha - 2007-12-23
5242 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
5243 without a datadirectory from a previous Tor install. Reported
5245 - Fix a crash when we fetch a descriptor that turns out to be
5246 unexpected (it used to be in our networkstatus when we started
5247 fetching it, but it isn't in our current networkstatus), and we
5248 aren't using bridges. Bugfix on 0.2.0.x.
5249 - Fix a crash when accessing hidden services: it would work the first
5250 time you use a given introduction point for your service, but
5251 on subsequent requests we'd be using garbage memory. Fixed by
5252 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
5253 - Fix a crash when we load a bridge descriptor from disk but we don't
5254 currently have a Bridge line for it in our torrc. Bugfix on
5258 - If bridge authorities set BridgePassword, they will serve a
5259 snapshot of known bridge routerstatuses from their DirPort to
5260 anybody who knows that password. Unset by default.
5263 - Make the unit tests build again.
5264 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
5265 - Make PublishServerDescriptor default to 1, so the default doesn't
5266 have to change as we invent new directory protocol versions.
5267 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
5268 be included unless sys/time.h is already included. Fixes
5269 bug 553. Bugfix on 0.2.0.x.
5270 - If we receive a general-purpose descriptor and then receive an
5271 identical bridge-purpose descriptor soon after, don't discard
5272 the next one as a duplicate.
5275 - If BridgeRelay is set to 1, then the default for
5276 PublishServerDescriptor is now "bridge" rather than "v2,v3".
5277 - If the user sets RelayBandwidthRate but doesn't set
5278 RelayBandwidthBurst, then make them equal rather than erroring out.
5281 Changes in version 0.2.0.13-alpha - 2007-12-21
5282 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
5283 Goodell, fixes many more bugs, and adds a lot of infrastructure for
5286 o New directory authorities:
5287 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
5291 - Only update guard status (usable / not usable) once we have
5292 enough directory information. This was causing us to always pick
5293 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
5294 causing us to discard all our guards on startup if we hadn't been
5295 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
5296 - Purge old entries from the "rephist" database and the hidden
5297 service descriptor databases even when DirPort is zero. Bugfix
5299 - We were ignoring our RelayBandwidthRate for the first 30 seconds
5300 after opening a circuit -- even a relayed circuit. Bugfix on
5302 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
5303 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
5304 crashing or mis-answering these types of requests.
5305 - Relays were publishing their server descriptor to v1 and v2
5306 directory authorities, but they didn't try publishing to v3-only
5307 authorities. Fix this; and also stop publishing to v1 authorities.
5309 - When we were reading router descriptors from cache, we were ignoring
5310 the annotations -- so for example we were reading in bridge-purpose
5311 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
5312 - When we decided to send a 503 response to a request for servers, we
5313 were then also sending the server descriptors: this defeats the
5314 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
5317 - Bridge relays now behave like clients with respect to time
5318 intervals for downloading new consensus documents -- otherwise they
5319 stand out. Bridge users now wait until the end of the interval,
5320 so their bridge relay will be sure to have a new consensus document.
5321 - Three new config options (AlternateDirAuthority,
5322 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
5323 user selectively replace the default directory authorities by type,
5324 rather than the all-or-nothing replacement that DirServer offers.
5325 - Tor can now be configured to read a GeoIP file from disk in one
5326 of two formats. This can be used by controllers to map IP addresses
5327 to countries. Eventually, it may support exit-by-country.
5328 - When possible, bridge relays remember which countries users
5329 are coming from, and report aggregate information in their
5330 extra-info documents, so that the bridge authorities can learn
5331 where Tor is blocked.
5332 - Bridge directory authorities now do reachability testing on the
5333 bridges they know. They provide router status summaries to the
5334 controller via "getinfo ns/purpose/bridge", and also dump summaries
5335 to a file periodically.
5336 - Stop fetching directory info so aggressively if your DirPort is
5337 on but your ORPort is off; stop fetching v2 dir info entirely.
5338 You can override these choices with the new FetchDirInfoEarly
5342 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
5343 consensus documents when there are too many relays at a single
5344 IP address. Now clear it in v2 network status documents too, and
5345 also clear it in routerinfo_t when the relay is no longer listed
5346 in the relevant networkstatus document.
5347 - Don't crash if we get an unexpected value for the
5348 PublishServerDescriptor config option. Reported by Matt Edman;
5349 bugfix on 0.2.0.9-alpha.
5350 - Our new v2 hidden service descriptor format allows descriptors
5351 that have no introduction points. But Tor crashed when we tried
5352 to build a descriptor with no intro points (and it would have
5353 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
5355 - Fix building with dmalloc 5.5.2 with glibc.
5356 - Reject uploaded descriptors and extrainfo documents if they're
5357 huge. Otherwise we'll cache them all over the network and it'll
5358 clog everything up. Reported by Aljosha Judmayer.
5359 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
5360 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
5361 - When the DANGEROUS_VERSION controller status event told us we're
5362 running an obsolete version, it used the string "OLD" to describe
5363 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
5364 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
5365 - If we can't expand our list of entry guards (e.g. because we're
5366 using bridges or we have StrictEntryNodes set), don't mark relays
5367 down when they fail a directory request. Otherwise we're too quick
5368 to mark all our entry points down. Bugfix on 0.1.2.x.
5369 - Fix handling of hex nicknames when answering controller requests for
5370 networkstatus by name, or when deciding whether to warn about unknown
5371 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
5372 - Fix a couple of hard-to-trigger autoconf problems that could result
5373 in really weird results on platforms whose sys/types.h files define
5374 nonstandard integer types. Bugfix on 0.1.2.x.
5375 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
5376 - Don't crash on name lookup when we have no current consensus. Fixes
5377 bug 538; bugfix on 0.2.0.x.
5378 - Only Tors that want to mirror the v2 directory info should
5379 create the "cached-status" directory in their datadir. (All Tors
5380 used to create it.) Bugfix on 0.2.0.9-alpha.
5381 - Directory authorities should only automatically download Extra Info
5382 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
5385 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
5386 consumers. (We already do this on HUP.)
5387 - Authorities and caches fetch the v2 networkstatus documents
5388 less often, now that v3 is encouraged.
5389 - Add a new config option BridgeRelay that specifies you want to
5390 be a bridge relay. Right now the only difference is that it makes
5391 you answer begin_dir requests, and it makes you cache dir info,
5392 even if your DirPort isn't on.
5393 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
5394 ask about source, timestamp of arrival, purpose, etc. We need
5395 something like this to help Vidalia not do GeoIP lookups on bridge
5397 - Allow multiple HashedControlPassword config lines, to support
5398 multiple controller passwords.
5399 - Authorities now decide whether they're authoritative for a given
5400 router based on the router's purpose.
5401 - New config options AuthDirBadDir and AuthDirListBadDirs for
5402 authorities to mark certain relays as "bad directories" in the
5403 networkstatus documents. Also supports the "!baddir" directive in
5404 the approved-routers file.
5407 Changes in version 0.2.0.12-alpha - 2007-11-16
5408 This twelfth development snapshot fixes some more build problems as
5409 well as a few minor bugs.
5412 - Make it build on OpenBSD again. Patch from tup.
5413 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
5414 package-building for Red Hat, OS X, etc.
5416 o Minor bugfixes (on 0.1.2.x):
5417 - Changing the ExitPolicyRejectPrivate setting should cause us to
5418 rebuild our server descriptor.
5420 o Minor bugfixes (on 0.2.0.x):
5421 - When we're lacking a consensus, don't try to perform rendezvous
5422 operations. Reported by Karsten Loesing.
5423 - Fix a small memory leak whenever we decide against using a
5424 newly picked entry guard. Reported by Mike Perry.
5425 - When authorities detected more than two relays running on the same
5426 IP address, they were clearing all the status flags but forgetting
5427 to clear the "hsdir" flag. So clients were being told that a
5428 given relay was the right choice for a v2 hsdir lookup, yet they
5429 never had its descriptor because it was marked as 'not running'
5431 - If we're trying to fetch a bridge descriptor and there's no way
5432 the bridge authority could help us (for example, we don't know
5433 a digest, or there is no bridge authority), don't be so eager to
5434 fall back to asking the bridge authority.
5435 - If we're using bridges or have strictentrynodes set, and our
5436 chosen exit is in the same family as all our bridges/entry guards,
5437 then be flexible about families.
5440 - When we negotiate a v2 link-layer connection (not yet implemented),
5441 accept RELAY_EARLY cells and turn them into RELAY cells if we've
5442 negotiated a v1 connection for their next step. Initial code for
5446 Changes in version 0.2.0.11-alpha - 2007-11-12
5447 This eleventh development snapshot fixes some build problems with
5448 the previous snapshot. It also includes a more secure-by-default exit
5449 policy for relays, fixes an enormous memory leak for exit relays, and
5450 fixes another bug where servers were falling out of the directory list.
5453 - Exit policies now reject connections that are addressed to a
5454 relay's public (external) IP address too, unless
5455 ExitPolicyRejectPrivate is turned off. We do this because too
5456 many relays are running nearby to services that trust them based
5457 on network address. Bugfix on 0.1.2.x.
5460 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
5461 on every successful resolve. Reported by Mike Perry; bugfix
5463 - On authorities, never downgrade to old router descriptors simply
5464 because they're listed in the consensus. This created a catch-22
5465 where we wouldn't list a new descriptor because there was an
5466 old one in the consensus, and we couldn't get the new one in the
5467 consensus because we wouldn't list it. Possible fix for bug 548.
5468 Also, this might cause bug 543 to appear on authorities; if so,
5469 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
5471 o Packaging fixes on 0.2.0.10-alpha:
5472 - We were including instructions about what to do with the
5473 src/config/fallback-consensus file, but we weren't actually
5474 including it in the tarball. Disable all of that for now.
5477 - Allow people to say PreferTunnelledDirConns rather than
5478 PreferTunneledDirConns, for those alternate-spellers out there.
5481 - Don't reevaluate all the information from our consensus document
5482 just because we've downloaded a v2 networkstatus that we intend
5483 to cache. Fixes bug 545; bugfix on 0.2.0.x.
5486 Changes in version 0.2.0.10-alpha - 2007-11-10
5487 This tenth development snapshot adds a third v3 directory authority
5488 run by Mike Perry, adds most of Karsten Loesing's new hidden service
5489 descriptor format, fixes a bad crash bug and new bridge bugs introduced
5490 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
5491 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
5492 addresses many more minor issues.
5494 o New directory authorities:
5495 - Set up ides (run by Mike Perry) as the third v3 directory authority.
5498 - Allow tunnelled directory connections to ask for an encrypted
5499 "begin_dir" connection or an anonymized "uses a full Tor circuit"
5500 connection independently. Now we can make anonymized begin_dir
5501 connections for (e.g.) more secure hidden service posting and
5503 - More progress on proposal 114: code from Karsten Loesing to
5504 implement new hidden service descriptor format.
5505 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
5506 accommodate the growing number of servers that use the default
5507 and are reaching it.
5508 - Directory authorities use a new formula for selecting which nodes
5509 to advertise as Guards: they must be in the top 7/8 in terms of
5510 how long we have known about them, and above the median of those
5511 nodes in terms of weighted fractional uptime.
5512 - Make "not enough dir info yet" warnings describe *why* Tor feels
5513 it doesn't have enough directory info yet.
5516 - Stop servers from crashing if they set a Family option (or
5517 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
5519 - Make bridge users work again -- the move to v3 directories in
5520 0.2.0.9-alpha had introduced a number of bugs that made bridges
5521 no longer work for clients.
5522 - When the clock jumps forward a lot, do not allow the bandwidth
5523 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
5525 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
5526 - When the consensus lists a router descriptor that we previously were
5527 mirroring, but that we considered non-canonical, reload the
5528 descriptor as canonical. This fixes bug 543 where Tor servers
5529 would start complaining after a few days that they don't have
5530 enough directory information to build a circuit.
5531 - Consider replacing the current consensus when certificates arrive
5532 that make the pending consensus valid. Previously, we were only
5533 considering replacement when the new certs _didn't_ help.
5534 - Fix an assert error on startup if we didn't already have the
5535 consensus and certs cached in our datadirectory: we were caching
5536 the consensus in consensus_waiting_for_certs but then free'ing it
5538 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
5539 Request) if we need more v3 certs but we've already got pending
5540 requests for all of them.
5541 - Correctly back off from failing certificate downloads. Fixes
5543 - Authorities don't vote on the Running flag if they have been running
5544 for less than 30 minutes themselves. Fixes bug 547, where a newly
5545 started authority would vote that everyone was down.
5548 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
5549 it, it had no AES, and it hasn't seen any security patches since
5553 - Clients now hold circuitless TLS connections open for 1.5 times
5554 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
5555 rebuild a new circuit over them within that timeframe. Previously,
5556 they held them open only for KeepalivePeriod (5 minutes).
5557 - Use "If-Modified-Since" to avoid retrieving consensus
5558 networkstatuses that we already have.
5559 - When we have no consensus, check FallbackNetworkstatusFile (defaults
5560 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
5561 we start knowing some directory caches.
5562 - When we receive a consensus from the future, warn about skew.
5563 - Improve skew reporting: try to give the user a better log message
5564 about how skewed they are, and how much this matters.
5565 - When we have a certificate for an authority, believe that
5566 certificate's claims about the authority's IP address.
5567 - New --quiet command-line option to suppress the default console log.
5568 Good in combination with --hash-password.
5569 - Authorities send back an X-Descriptor-Not-New header in response to
5570 an accepted-but-discarded descriptor upload. Partially implements
5572 - Make the log message for "tls error. breaking." more useful.
5573 - Better log messages about certificate downloads, to attempt to
5574 track down the second incarnation of bug 546.
5576 o Minor features (bridges):
5577 - If bridge users set UpdateBridgesFromAuthority, but the digest
5578 they ask for is a 404 from the bridge authority, they now fall
5579 back to trying the bridge directly.
5580 - Bridges now use begin_dir to publish their server descriptor to
5581 the bridge authority, even when they haven't set TunnelDirConns.
5583 o Minor features (controller):
5584 - When reporting clock skew, and we know that the clock is _at least
5585 as skewed_ as some value, but we don't know the actual value,
5586 report the value as a "minimum skew."
5589 - Update linux-tor-prio.sh script to allow QoS based on the uid of
5590 the Tor process. Patch from Marco Bonetti with tweaks from Mike
5594 - Refuse to start if both ORPort and UseBridges are set. Bugfix
5595 on 0.2.0.x, suggested by Matt Edman.
5596 - Don't stop fetching descriptors when FetchUselessDescriptors is
5597 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
5598 reported by tup and ioerror.
5599 - Better log message on vote from unknown authority.
5600 - Don't log "Launching 0 request for 0 router" message.
5602 o Minor bugfixes (memory leaks):
5603 - Stop leaking memory every time we parse a v3 certificate. Bugfix
5605 - Stop leaking memory every time we load a v3 certificate. Bugfix
5606 on 0.2.0.1-alpha. Fixes bug 536.
5607 - Stop leaking a cached networkstatus on exit. Bugfix on
5609 - Stop leaking voter information every time we free a consensus.
5610 Bugfix on 0.2.0.3-alpha.
5611 - Stop leaking signed data every time we check a voter signature.
5612 Bugfix on 0.2.0.3-alpha.
5613 - Stop leaking a signature every time we fail to parse a consensus or
5614 a vote. Bugfix on 0.2.0.3-alpha.
5615 - Stop leaking v2_download_status_map on shutdown. Bugfix on
5617 - Stop leaking conn->nickname every time we make a connection to a
5618 Tor relay without knowing its expected identity digest (e.g. when
5619 using bridges). Bugfix on 0.2.0.3-alpha.
5621 - Minor bugfixes (portability):
5622 - Run correctly on platforms where rlim_t is larger than unsigned
5623 long, and/or where the real limit for number of open files is
5624 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
5625 particular, these may be needed for OS X 10.5.
5628 Changes in version 0.1.2.18 - 2007-10-28
5629 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
5630 hidden service introduction that were causing huge delays, and a big
5631 bug that was causing some servers to disappear from the network status
5632 lists for a few hours each day.
5634 o Major bugfixes (crashes):
5635 - If a connection is shut down abruptly because of something that
5636 happened inside connection_flushed_some(), do not call
5637 connection_finished_flushing(). Should fix bug 451:
5638 "connection_stop_writing: Assertion conn->write_event failed"
5639 Bugfix on 0.1.2.7-alpha.
5640 - Fix possible segfaults in functions called from
5641 rend_process_relay_cell().
5643 o Major bugfixes (hidden services):
5644 - Hidden services were choosing introduction points uniquely by
5645 hexdigest, but when constructing the hidden service descriptor
5646 they merely wrote the (potentially ambiguous) nickname.
5647 - Clients now use the v2 intro format for hidden service
5648 connections: they specify their chosen rendezvous point by identity
5649 digest rather than by (potentially ambiguous) nickname. These
5650 changes could speed up hidden service connections dramatically.
5652 o Major bugfixes (other):
5653 - Stop publishing a new server descriptor just because we get a
5654 HUP signal. This led (in a roundabout way) to some servers getting
5655 dropped from the networkstatus lists for a few hours each day.
5656 - When looking for a circuit to cannibalize, consider family as well
5657 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
5658 circuit cannibalization).
5659 - When a router wasn't listed in a new networkstatus, we were leaving
5660 the flags for that router alone -- meaning it remained Named,
5661 Running, etc -- even though absence from the networkstatus means
5662 that it shouldn't be considered to exist at all anymore. Now we
5663 clear all the flags for routers that fall out of the networkstatus
5664 consensus. Fixes bug 529.
5667 - Don't try to access (or alter) the state file when running
5668 --list-fingerprint or --verify-config or --hash-password. Resolves
5670 - When generating information telling us how to extend to a given
5671 router, do not try to include the nickname if it is
5672 absent. Resolves bug 467.
5673 - Fix a user-triggerable segfault in expand_filename(). (There isn't
5674 a way to trigger this remotely.)
5675 - When sending a status event to the controller telling it that an
5676 OR address is reachable, set the port correctly. (Previously we
5677 were reporting the dir port.)
5678 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
5679 command. Bugfix on 0.1.2.17.
5680 - When loading bandwidth history, do not believe any information in
5681 the future. Fixes bug 434.
5682 - When loading entry guard information, do not believe any information
5684 - When we have our clock set far in the future and generate an
5685 onion key, then re-set our clock to be correct, we should not stop
5686 the onion key from getting rotated.
5687 - On some platforms, accept() can return a broken address. Detect
5688 this more quietly, and deal accordingly. Fixes bug 483.
5689 - It's not actually an error to find a non-pending entry in the DNS
5690 cache when canceling a pending resolve. Don't log unless stuff
5691 is fishy. Resolves bug 463.
5692 - Don't reset trusted dir server list when we set a configuration
5693 option. Patch from Robert Hogan.
5694 - Don't try to create the datadir when running --verify-config or
5695 --hash-password. Resolves bug 540.
5698 Changes in version 0.2.0.9-alpha - 2007-10-24
5699 This ninth development snapshot switches clients to the new v3 directory
5700 system; allows servers to be listed in the network status even when they
5701 have the same nickname as a registered server; and fixes many other
5702 bugs including a big one that was causing some servers to disappear
5703 from the network status lists for a few hours each day.
5705 o Major features (directory system):
5706 - Clients now download v3 consensus networkstatus documents instead
5707 of v2 networkstatus documents. Clients and caches now base their
5708 opinions about routers on these consensus documents. Clients only
5709 download router descriptors listed in the consensus.
5710 - Authorities now list servers who have the same nickname as
5711 a different named server, but list them with a new flag,
5712 "Unnamed". Now we can list servers that happen to pick the same
5713 nickname as a server that registered two years ago and then
5714 disappeared. Partially implements proposal 122.
5715 - If the consensus lists a router as "Unnamed", the name is assigned
5716 to a different router: do not identify the router by that name.
5717 Partially implements proposal 122.
5718 - Authorities can now come to a consensus on which method to use to
5719 compute the consensus. This gives us forward compatibility.
5722 - Stop publishing a new server descriptor just because we HUP or
5723 when we find our DirPort to be reachable but won't actually publish
5724 it. New descriptors without any real changes are dropped by the
5725 authorities, and can screw up our "publish every 18 hours" schedule.
5727 - When a router wasn't listed in a new networkstatus, we were leaving
5728 the flags for that router alone -- meaning it remained Named,
5729 Running, etc -- even though absence from the networkstatus means
5730 that it shouldn't be considered to exist at all anymore. Now we
5731 clear all the flags for routers that fall out of the networkstatus
5732 consensus. Fixes bug 529; bugfix on 0.1.2.x.
5733 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
5734 extrainfo documents and then discard them immediately for not
5735 matching the latest router. Bugfix on 0.2.0.1-alpha.
5737 o Minor features (v3 directory protocol):
5738 - Allow tor-gencert to generate a new certificate without replacing
5740 - Allow certificates to include an address.
5741 - When we change our directory-cache settings, reschedule all voting
5742 and download operations.
5743 - Reattempt certificate downloads immediately on failure, as long as
5744 we haven't failed a threshold number of times yet.
5745 - Delay retrying consensus downloads while we're downloading
5746 certificates to verify the one we just got. Also, count getting a
5747 consensus that we already have (or one that isn't valid) as a failure,
5748 and count failing to get the certificates after 20 minutes as a
5750 - Build circuits and download descriptors even if our consensus is a
5751 little expired. (This feature will go away once authorities are
5754 o Minor features (router descriptor cache):
5755 - If we find a cached-routers file that's been sitting around for more
5756 than 28 days unmodified, then most likely it's a leftover from
5757 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
5759 - When we (as a cache) download a descriptor because it was listed
5760 in a consensus, remember when the consensus was supposed to expire,
5761 and don't expire the descriptor until then.
5763 o Minor features (performance):
5764 - Call routerlist_remove_old_routers() much less often. This should
5765 speed startup, especially on directory caches.
5766 - Don't try to launch new descriptor downloads quite so often when we
5767 already have enough directory information to build circuits.
5768 - Base64 decoding was actually showing up on our profile when parsing
5769 the initial descriptor file; switch to an in-process all-at-once
5770 implementation that's about 3.5x times faster than calling out to
5773 o Minor features (compilation):
5774 - Detect non-ASCII platforms (if any still exist) and refuse to
5775 build there: some of our code assumes that 'A' is 65 and so on.
5777 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
5778 - Make the "next period" votes into "current period" votes immediately
5779 after publishing the consensus; avoid a heisenbug that made them
5780 stick around indefinitely.
5781 - When we discard a vote as a duplicate, do not report this as
5783 - Treat missing v3 keys or certificates as an error when running as a
5784 v3 directory authority.
5785 - When we're configured to be a v3 authority, but we're only listed
5786 as a non-v3 authority in our DirServer line for ourself, correct
5788 - If an authority doesn't have a qualified hostname, just put
5789 its address in the vote. This fixes the problem where we referred to
5790 "moria on moria:9031."
5791 - Distinguish between detached signatures for the wrong period, and
5792 detached signatures for a divergent vote.
5793 - Fix a small memory leak when computing a consensus.
5794 - When there's no concensus, we were forming a vote every 30
5795 minutes, but writing the "valid-after" line in our vote based
5796 on our configured V3AuthVotingInterval: so unless the intervals
5797 matched up, we immediately rejected our own vote because it didn't
5798 start at the voting interval that caused us to construct a vote.
5800 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
5801 - Delete unverified-consensus when the real consensus is set.
5802 - Consider retrying a consensus networkstatus fetch immediately
5803 after one fails: don't wait 60 seconds to notice.
5804 - When fetching a consensus as a cache, wait until a newer consensus
5805 should exist before trying to replace the current one.
5806 - Use a more forgiving schedule for retrying failed consensus
5807 downloads than for other types.
5809 o Minor bugfixes (other directory issues):
5810 - Correct the implementation of "download votes by digest." Bugfix on
5812 - Authorities no longer send back "400 you're unreachable please fix
5813 it" errors to Tor servers that aren't online all the time. We're
5814 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
5816 o Minor bugfixes (controller):
5817 - Don't reset trusted dir server list when we set a configuration
5818 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
5819 - Respond to INT and TERM SIGNAL commands before we execute the
5820 signal, in case the signal shuts us down. We had a patch in
5821 0.1.2.1-alpha that tried to do this by queueing the response on
5822 the connection's buffer before shutting down, but that really
5823 isn't the same thing at all. Bug located by Matt Edman.
5825 o Minor bugfixes (misc):
5826 - Correctly check for bad options to the "PublishServerDescriptor"
5827 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
5828 - Stop leaking memory on failing case of base32_decode, and make
5829 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
5830 - Don't try to download extrainfo documents when we're trying to
5831 fetch enough directory info to build a circuit: having enough
5832 info should get priority. Bugfix on 0.2.0.x.
5833 - Don't complain that "your server has not managed to confirm that its
5834 ports are reachable" if we haven't been able to build any circuits
5835 yet. Bug found by spending four hours without a v3 consensus. Bugfix
5837 - Detect the reason for failing to mmap a descriptor file we just
5838 wrote, and give a more useful log message. Fixes bug 533. Bugfix
5841 o Code simplifications and refactoring:
5842 - Remove support for the old bw_accounting file: we've been storing
5843 bandwidth accounting information in the state file since
5844 0.1.2.5-alpha. This may result in bandwidth accounting errors
5845 if you try to upgrade from 0.1.1.x or earlier, or if you try to
5846 downgrade to 0.1.1.x or earlier.
5847 - New convenience code to locate a file within the DataDirectory.
5848 - Move non-authority functionality out of dirvote.c.
5849 - Refactor the arguments for router_pick_{directory_|trusteddir}server
5850 so that they all take the same named flags.
5853 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
5854 Unix users an easy way to script their Tor process (e.g. by
5855 adjusting bandwidth based on the time of the day).
5858 Changes in version 0.2.0.8-alpha - 2007-10-12
5859 This eighth development snapshot fixes a crash bug that's been bothering
5860 us since February 2007, lets bridge authorities store a list of bridge
5861 descriptors they've seen, gets v3 directory voting closer to working,
5862 starts caching v3 directory consensus documents on directory mirrors,
5863 and fixes a variety of smaller issues including some minor memory leaks.
5865 o Major features (router descriptor cache):
5866 - Store routers in a file called cached-descriptors instead of in
5867 cached-routers. Initialize cached-descriptors from cached-routers
5868 if the old format is around. The new format allows us to store
5869 annotations along with descriptors.
5870 - Use annotations to record the time we received each descriptor, its
5871 source, and its purpose.
5872 - Disable the SETROUTERPURPOSE controller command: it is now
5874 - Controllers should now specify cache=no or cache=yes when using
5875 the +POSTDESCRIPTOR command.
5876 - Bridge authorities now write bridge descriptors to disk, meaning
5877 we can export them to other programs and begin distributing them
5880 o Major features (directory authorities):
5881 - When a v3 authority is missing votes or signatures, it now tries
5883 - Directory authorities track weighted fractional uptime as well as
5884 weighted mean-time-between failures. WFU is suitable for deciding
5885 whether a node is "usually up", while MTBF is suitable for deciding
5886 whether a node is "likely to stay up." We need both, because
5887 "usually up" is a good requirement for guards, while "likely to
5888 stay up" is a good requirement for long-lived connections.
5890 o Major features (v3 directory system):
5891 - Caches now download v3 network status documents as needed,
5892 and download the descriptors listed in them.
5893 - All hosts now attempt to download and keep fresh v3 authority
5894 certificates, and re-attempt after failures.
5895 - More internal-consistency checks for vote parsing.
5897 o Major bugfixes (crashes):
5898 - If a connection is shut down abruptly because of something that
5899 happened inside connection_flushed_some(), do not call
5900 connection_finished_flushing(). Should fix bug 451. Bugfix on
5903 o Major bugfixes (performance):
5904 - Fix really bad O(n^2) performance when parsing a long list of
5905 routers: Instead of searching the entire list for an "extra-info "
5906 string which usually wasn't there, once for every routerinfo
5907 we read, just scan lines forward until we find one we like.
5909 - When we add data to a write buffer in response to the data on that
5910 write buffer getting low because of a flush, do not consider the
5911 newly added data as a candidate for immediate flushing, but rather
5912 make it wait until the next round of writing. Otherwise, we flush
5913 and refill recursively, and a single greedy TLS connection can
5914 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
5916 o Minor features (v3 authority system):
5917 - Add more ways for tools to download the votes that lead to the
5919 - Send a 503 when low on bandwidth and a vote, consensus, or
5920 certificate is requested.
5921 - If-modified-since is now implemented properly for all kinds of
5922 certificate requests.
5924 o Minor bugfixes (network statuses):
5925 - Tweak the implementation of proposal 109 slightly: allow at most
5926 two Tor servers on the same IP address, except if it's the location
5927 of a directory authority, in which case allow five. Bugfix on
5930 o Minor bugfixes (controller):
5931 - When sending a status event to the controller telling it that an
5932 OR address is reachable, set the port correctly. (Previously we
5933 were reporting the dir port.) Bugfix on 0.1.2.x.
5935 o Minor bugfixes (v3 directory system):
5936 - Fix logic to look up a cert by its signing key digest. Bugfix on
5938 - Only change the reply to a vote to "OK" if it's not already
5939 set. This gets rid of annoying "400 OK" log messages, which may
5940 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
5941 - When we get a valid consensus, recompute the voting schedule.
5942 - Base the valid-after time of a vote on the consensus voting
5943 schedule, not on our preferred schedule.
5944 - Make the return values and messages from signature uploads and
5945 downloads more sensible.
5946 - Fix a memory leak when serving votes and consensus documents, and
5947 another when serving certificates.
5949 o Minor bugfixes (performance):
5950 - Use a slightly simpler string hashing algorithm (copying Python's
5951 instead of Java's) and optimize our digest hashing algorithm to take
5952 advantage of 64-bit platforms and to remove some possibly-costly
5954 - Fix a minor memory leak whenever we parse guards from our state
5955 file. Bugfix on 0.2.0.7-alpha.
5956 - Fix a minor memory leak whenever we write out a file. Bugfix on
5958 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
5959 command. Bugfix on 0.2.0.5-alpha.
5961 o Minor bugfixes (portability):
5962 - On some platforms, accept() can return a broken address. Detect
5963 this more quietly, and deal accordingly. Fixes bug 483.
5964 - Stop calling tor_strlower() on uninitialized memory in some cases.
5965 Bugfix in 0.2.0.7-alpha.
5967 o Minor bugfixes (usability):
5968 - Treat some 403 responses from directory servers as INFO rather than
5969 WARN-severity events.
5970 - It's not actually an error to find a non-pending entry in the DNS
5971 cache when canceling a pending resolve. Don't log unless stuff is
5972 fishy. Resolves bug 463.
5974 o Minor bugfixes (anonymity):
5975 - Never report that we've used more bandwidth than we're willing to
5976 relay: it leaks how much non-relay traffic we're using. Resolves
5978 - When looking for a circuit to cannibalize, consider family as well
5979 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
5980 circuit cannibalization).
5982 o Code simplifications and refactoring:
5983 - Make a bunch of functions static. Remove some dead code.
5984 - Pull out about a third of the really big routerlist.c; put it in a
5985 new module, networkstatus.c.
5986 - Merge the extra fields in local_routerstatus_t back into
5987 routerstatus_t: we used to need one routerstatus_t for each
5988 authority's opinion, plus a local_routerstatus_t for the locally
5989 computed consensus opinion. To save space, we put the locally
5990 modified fields into local_routerstatus_t, and only the common
5991 stuff into routerstatus_t. But once v3 directories are in use,
5992 clients and caches will no longer need to hold authority opinions;
5993 thus, the rationale for keeping the types separate is now gone.
5994 - Make the code used to reschedule and reattempt downloads more
5996 - Turn all 'Are we a directory server/mirror?' logic into a call to
5998 - Remove the code to generate the oldest (v1) directory format.
5999 The code has been disabled since 0.2.0.5-alpha.
6002 Changes in version 0.2.0.7-alpha - 2007-09-21
6003 This seventh development snapshot makes bridges work again, makes bridge
6004 authorities work for the first time, fixes two huge performance flaws
6005 in hidden services, and fixes a variety of minor issues.
6007 o New directory authorities:
6008 - Set up moria1 and tor26 as the first v3 directory authorities. See
6009 doc/spec/dir-spec.txt for details on the new directory design.
6011 o Major bugfixes (crashes):
6012 - Fix possible segfaults in functions called from
6013 rend_process_relay_cell(). Bugfix on 0.1.2.x.
6015 o Major bugfixes (bridges):
6016 - Fix a bug that made servers send a "404 Not found" in response to
6017 attempts to fetch their server descriptor. This caused Tor servers
6018 to take many minutes to establish reachability for their DirPort,
6019 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
6020 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
6021 users configure that and specify a bridge with an identity
6022 fingerprint, now they will lookup the bridge descriptor at the
6023 default bridge authority via a one-hop tunnel, but once circuits
6024 are established they will switch to a three-hop tunnel for later
6025 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
6027 o Major bugfixes (hidden services):
6028 - Hidden services were choosing introduction points uniquely by
6029 hexdigest, but when constructing the hidden service descriptor
6030 they merely wrote the (potentially ambiguous) nickname.
6031 - Clients now use the v2 intro format for hidden service
6032 connections: they specify their chosen rendezvous point by identity
6033 digest rather than by (potentially ambiguous) nickname. Both
6034 are bugfixes on 0.1.2.x, and they could speed up hidden service
6035 connections dramatically. Thanks to Karsten Loesing.
6037 o Minor features (security):
6038 - As a client, do not believe any server that tells us that an
6039 address maps to an internal address space.
6040 - Make it possible to enable HashedControlPassword and
6041 CookieAuthentication at the same time.
6043 o Minor features (guard nodes):
6044 - Tag every guard node in our state file with the version that
6045 we believe added it, or with our own version if we add it. This way,
6046 if a user temporarily runs an old version of Tor and then switches
6047 back to a new one, she doesn't automatically lose her guards.
6049 o Minor features (speed):
6050 - When implementing AES counter mode, update only the portions of the
6051 counter buffer that need to change, and don't keep separate
6052 network-order and host-order counters when they are the same (i.e.,
6053 on big-endian hosts.)
6055 o Minor features (controller):
6056 - Accept LF instead of CRLF on controller, since some software has a
6057 hard time generating real Internet newlines.
6058 - Add GETINFO values for the server status events
6059 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
6063 - Routers no longer include bandwidth-history lines in their
6064 descriptors; this information is already available in extra-info
6065 documents, and including it in router descriptors took up 60%
6066 (!) of compressed router descriptor downloads. Completes
6067 implementation of proposal 104.
6068 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
6069 and TorControl.py, as they use the old v0 controller protocol,
6070 and are obsoleted by TorFlow anyway.
6071 - Drop support for v1 rendezvous descriptors, since we never used
6072 them anyway, and the code has probably rotted by now. Based on
6073 patch from Karsten Loesing.
6074 - On OSX, stop warning the user that kqueue support in libevent is
6075 "experimental", since it seems to have worked fine for ages.
6078 - When generating information telling us how to extend to a given
6079 router, do not try to include the nickname if it is absent. Fixes
6080 bug 467. Bugfix on 0.2.0.3-alpha.
6081 - Fix a user-triggerable (but not remotely-triggerable) segfault
6082 in expand_filename(). Bugfix on 0.1.2.x.
6083 - Fix a memory leak when freeing incomplete requests from DNSPort.
6084 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
6085 - Don't try to access (or alter) the state file when running
6086 --list-fingerprint or --verify-config or --hash-password. (Resolves
6087 bug 499.) Bugfix on 0.1.2.x.
6088 - Servers used to decline to publish their DirPort if their
6089 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
6090 were below a threshold. Now they only look at BandwidthRate and
6091 RelayBandwidthRate. Bugfix on 0.1.2.x.
6092 - Remove an optimization in the AES counter-mode code that assumed
6093 that the counter never exceeded 2^68. When the counter can be set
6094 arbitrarily as an IV (as it is by Karsten's new hidden services
6095 code), this assumption no longer holds. Bugfix on 0.1.2.x.
6096 - Resume listing "AUTHORITY" flag for authorities in network status.
6097 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
6099 o Code simplifications and refactoring:
6100 - Revamp file-writing logic so we don't need to have the entire
6101 contents of a file in memory at once before we write to disk. Tor,
6103 - Turn "descriptor store" into a full-fledged type.
6104 - Move all NT services code into a separate source file.
6105 - Unify all code that computes medians, percentile elements, etc.
6106 - Get rid of a needless malloc when parsing address policies.
6109 Changes in version 0.1.2.17 - 2007-08-30
6110 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
6111 X bundles. Vidalia 0.0.14 makes authentication required for the
6112 ControlPort in the default configuration, which addresses important
6113 security risks. Everybody who uses Vidalia (or another controller)
6116 In addition, this Tor update fixes major load balancing problems with
6117 path selection, which should speed things up a lot once many people
6120 o Major bugfixes (security):
6121 - We removed support for the old (v0) control protocol. It has been
6122 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
6123 become more of a headache than it's worth.
6125 o Major bugfixes (load balancing):
6126 - When choosing nodes for non-guard positions, weight guards
6127 proportionally less, since they already have enough load. Patch
6129 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
6130 will allow fast Tor servers to get more attention.
6131 - When we're upgrading from an old Tor version, forget our current
6132 guards and pick new ones according to the new weightings. These
6133 three load balancing patches could raise effective network capacity
6134 by a factor of four. Thanks to Mike Perry for measurements.
6136 o Major bugfixes (stream expiration):
6137 - Expire not-yet-successful application streams in all cases if
6138 they've been around longer than SocksTimeout. Right now there are
6139 some cases where the stream will live forever, demanding a new
6140 circuit every 15 seconds. Fixes bug 454; reported by lodger.
6142 o Minor features (controller):
6143 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
6144 is valid before any authentication has been received. It tells
6145 a controller what kind of authentication is expected, and what
6146 protocol is spoken. Implements proposal 119.
6148 o Minor bugfixes (performance):
6149 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
6150 greatly speeding up loading cached-routers from disk on startup.
6151 - Disable sentinel-based debugging for buffer code: we squashed all
6152 the bugs that this was supposed to detect a long time ago, and now
6153 its only effect is to change our buffer sizes from nice powers of
6154 two (which platform mallocs tend to like) to values slightly over
6155 powers of two (which make some platform mallocs sad).
6157 o Minor bugfixes (misc):
6158 - If exit bandwidth ever exceeds one third of total bandwidth, then
6159 use the correct formula to weight exit nodes when choosing paths.
6160 Based on patch from Mike Perry.
6161 - Choose perfectly fairly among routers when choosing by bandwidth and
6162 weighting by fraction of bandwidth provided by exits. Previously, we
6163 would choose with only approximate fairness, and correct ourselves
6164 if we ran off the end of the list.
6165 - If we require CookieAuthentication but we fail to write the
6166 cookie file, we would warn but not exit, and end up in a state
6167 where no controller could authenticate. Now we exit.
6168 - If we require CookieAuthentication, stop generating a new cookie
6169 every time we change any piece of our config.
6170 - Refuse to start with certain directory authority keys, and
6171 encourage people using them to stop.
6172 - Terminate multi-line control events properly. Original patch
6174 - Fix a minor memory leak when we fail to find enough suitable
6175 servers to choose a circuit.
6176 - Stop leaking part of the descriptor when we run into a particularly
6177 unparseable piece of it.
6180 Changes in version 0.2.0.6-alpha - 2007-08-26
6181 This sixth development snapshot features a new Vidalia version in the
6182 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
6183 the ControlPort in the default configuration, which addresses important
6186 In addition, this snapshot fixes major load balancing problems
6187 with path selection, which should speed things up a lot once many
6188 people have upgraded. The directory authorities also use a new
6189 mean-time-between-failure approach to tracking which servers are stable,
6190 rather than just looking at the most recent uptime.
6192 o New directory authorities:
6193 - Set up Tonga as the default bridge directory authority.
6196 - Directory authorities now track servers by weighted
6197 mean-times-between-failures. When we have 4 or more days of data,
6198 use measured MTBF rather than declared uptime to decide whether
6199 to call a router Stable. Implements proposal 108.
6201 o Major bugfixes (load balancing):
6202 - When choosing nodes for non-guard positions, weight guards
6203 proportionally less, since they already have enough load. Patch
6205 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
6206 will allow fast Tor servers to get more attention.
6207 - When we're upgrading from an old Tor version, forget our current
6208 guards and pick new ones according to the new weightings. These
6209 three load balancing patches could raise effective network capacity
6210 by a factor of four. Thanks to Mike Perry for measurements.
6212 o Major bugfixes (descriptor parsing):
6213 - Handle unexpected whitespace better in malformed descriptors. Bug
6214 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
6217 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
6218 GETINFO for Torstat to use until it can switch to using extrainfos.
6219 - Optionally (if built with -DEXPORTMALLINFO) export the output
6220 of mallinfo via http, as tor/mallinfo.txt. Only accessible
6224 - Do not intermix bridge routers with controller-added
6225 routers. (Bugfix on 0.2.0.x)
6226 - Do not fail with an assert when accept() returns an unexpected
6227 address family. Addresses but does not wholly fix bug 483. (Bugfix
6229 - Let directory authorities startup even when they can't generate
6230 a descriptor immediately, e.g. because they don't know their
6232 - Stop putting the authentication cookie in a file called "0"
6233 in your working directory if you don't specify anything for the
6234 new CookieAuthFile option. Reported by Matt Edman.
6235 - Make it possible to read the PROTOCOLINFO response in a way that
6236 conforms to our control-spec. Reported by Matt Edman.
6237 - Fix a minor memory leak when we fail to find enough suitable
6238 servers to choose a circuit. Bugfix on 0.1.2.x.
6239 - Stop leaking part of the descriptor when we run into a particularly
6240 unparseable piece of it. Bugfix on 0.1.2.x.
6241 - Unmap the extrainfo cache file on exit.
6244 Changes in version 0.2.0.5-alpha - 2007-08-19
6245 This fifth development snapshot fixes compilation on Windows again;
6246 fixes an obnoxious client-side bug that slowed things down and put
6247 extra load on the network; gets us closer to using the v3 directory
6248 voting scheme; makes it easier for Tor controllers to use cookie-based
6249 authentication; and fixes a variety of other bugs.
6252 - Version 1 directories are no longer generated in full. Instead,
6253 authorities generate and serve "stub" v1 directories that list
6254 no servers. This will stop Tor versions 0.1.0.x and earlier from
6255 working, but (for security reasons) nobody should be running those
6258 o Major bugfixes (compilation, 0.2.0.x):
6259 - Try to fix Win32 compilation again: improve checking for IPv6 types.
6260 - Try to fix MSVC compilation: build correctly on platforms that do
6261 not define s6_addr16 or s6_addr32.
6262 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
6265 o Major bugfixes (stream expiration):
6266 - Expire not-yet-successful application streams in all cases if
6267 they've been around longer than SocksTimeout. Right now there are
6268 some cases where the stream will live forever, demanding a new
6269 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
6272 o Minor features (directory servers):
6273 - When somebody requests a list of statuses or servers, and we have
6274 none of those, return a 404 rather than an empty 200.
6276 o Minor features (directory voting):
6277 - Store v3 consensus status consensuses on disk, and reload them
6280 o Minor features (security):
6281 - Warn about unsafe ControlPort configurations.
6282 - Refuse to start with certain directory authority keys, and
6283 encourage people using them to stop.
6285 o Minor features (controller):
6286 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
6287 is valid before any authentication has been received. It tells
6288 a controller what kind of authentication is expected, and what
6289 protocol is spoken. Implements proposal 119.
6290 - New config option CookieAuthFile to choose a new location for the
6291 cookie authentication file, and config option
6292 CookieAuthFileGroupReadable to make it group-readable.
6294 o Minor features (unit testing):
6295 - Add command-line arguments to unit-test executable so that we can
6296 invoke any chosen test from the command line rather than having
6297 to run the whole test suite at once; and so that we can turn on
6298 logging for the unit tests.
6300 o Minor bugfixes (on 0.1.2.x):
6301 - If we require CookieAuthentication but we fail to write the
6302 cookie file, we would warn but not exit, and end up in a state
6303 where no controller could authenticate. Now we exit.
6304 - If we require CookieAuthentication, stop generating a new cookie
6305 every time we change any piece of our config.
6306 - When loading bandwidth history, do not believe any information in
6307 the future. Fixes bug 434.
6308 - When loading entry guard information, do not believe any information
6310 - When we have our clock set far in the future and generate an
6311 onion key, then re-set our clock to be correct, we should not stop
6312 the onion key from getting rotated.
6313 - Clean up torrc sample config file.
6314 - Do not automatically run configure from autogen.sh. This
6315 non-standard behavior tended to annoy people who have built other
6318 o Minor bugfixes (on 0.2.0.x):
6319 - Fix a bug with AutomapHostsOnResolve that would always cause
6320 the second request to fail. Bug reported by Kate. Bugfix on
6322 - Fix a bug in ADDRMAP controller replies that would sometimes
6323 try to print a NULL. Patch from tup.
6324 - Read v3 directory authority keys from the right location.
6325 - Numerous bugfixes to directory voting code.
6328 Changes in version 0.1.2.16 - 2007-08-01
6329 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
6330 remote attacker in certain situations to rewrite the user's torrc
6331 configuration file. This can completely compromise anonymity of users
6332 in most configurations, including those running the Vidalia bundles,
6333 TorK, etc. Or worse.
6335 o Major security fixes:
6336 - Close immediately after missing authentication on control port;
6337 do not allow multiple authentication attempts.
6340 Changes in version 0.2.0.4-alpha - 2007-08-01
6341 This fourth development snapshot fixes a critical security vulnerability
6342 for most users, specifically those running Vidalia, TorK, etc. Everybody
6343 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
6345 o Major security fixes:
6346 - Close immediately after missing authentication on control port;
6347 do not allow multiple authentication attempts.
6349 o Major bugfixes (compilation):
6350 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
6353 o Minor features (performance):
6354 - Be even more aggressive about releasing RAM from small
6355 empty buffers. Thanks to our free-list code, this shouldn't be too
6356 performance-intensive.
6357 - Disable sentinel-based debugging for buffer code: we squashed all
6358 the bugs that this was supposed to detect a long time ago, and
6359 now its only effect is to change our buffer sizes from nice
6360 powers of two (which platform mallocs tend to like) to values
6361 slightly over powers of two (which make some platform mallocs sad).
6362 - Log malloc statistics from mallinfo() on platforms where it
6366 Changes in version 0.2.0.3-alpha - 2007-07-29
6367 This third development snapshot introduces new experimental
6368 blocking-resistance features and a preliminary version of the v3
6369 directory voting design, and includes many other smaller features
6373 - The first pieces of our "bridge" design for blocking-resistance
6374 are implemented. People can run bridge directory authorities;
6375 people can run bridges; and people can configure their Tor clients
6376 with a set of bridges to use as the first hop into the Tor network.
6377 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
6379 - Create listener connections before we setuid to the configured
6380 User and Group. Now non-Windows users can choose port values
6381 under 1024, start Tor as root, and have Tor bind those ports
6382 before it changes to another UID. (Windows users could already
6384 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
6385 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
6386 on "vserver" accounts. (Patch from coderman.)
6387 - Be even more aggressive about separating local traffic from relayed
6388 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
6390 o Major features (experimental):
6391 - First cut of code for "v3 dir voting": directory authorities will
6392 vote on a common network status document rather than each publishing
6393 their own opinion. This code needs more testing and more corner-case
6394 handling before it's ready for use.
6397 - Directory authorities now call routers Fast if their bandwidth is
6398 at least 100KB/s, and consider their bandwidth adequate to be a
6399 Guard if it is at least 250KB/s, no matter the medians. This fix
6400 complements proposal 107. [Bugfix on 0.1.2.x]
6401 - Directory authorities now never mark more than 3 servers per IP as
6402 Valid and Running. (Implements proposal 109, by Kevin Bauer and
6404 - Minor change to organizationName and commonName generation
6405 procedures in TLS certificates during Tor handshakes, to invalidate
6406 some earlier censorware approaches. This is not a long-term
6407 solution, but applying it will give us a bit of time to look into
6408 the epidemiology of countermeasures as they spread.
6410 o Major bugfixes (directory):
6411 - Rewrite directory tokenization code to never run off the end of
6412 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
6414 o Minor features (controller):
6415 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
6416 match requests to applications. (Patch from Robert Hogan.)
6417 - Report address and port correctly on connections to DNSPort. (Patch
6419 - Add a RESOLVE command to launch hostname lookups. (Original patch
6421 - Add GETINFO status/enough-dir-info to let controllers tell whether
6422 Tor has downloaded sufficient directory information. (Patch
6424 - You can now use the ControlSocket option to tell Tor to listen for
6425 controller connections on Unix domain sockets on systems that
6426 support them. (Patch from Peter Palfrader.)
6427 - STREAM NEW events are generated for DNSPort requests and for
6428 tunneled directory connections. (Patch from Robert Hogan.)
6429 - New "GETINFO address-mappings/*" command to get address mappings
6430 with expiry information. "addr-mappings/*" is now deprecated.
6433 o Minor features (misc):
6434 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
6436 - The tor-gencert tool for v3 directory authorities now creates all
6437 files as readable to the file creator only, and write-protects
6438 the authority identity key.
6439 - When dumping memory usage, list bytes used in buffer memory
6441 - When running with dmalloc, dump more stats on hup and on exit.
6442 - Directory authorities now fail quickly and (relatively) harmlessly
6443 if they generate a network status document that is somehow
6446 o Traffic load balancing improvements:
6447 - If exit bandwidth ever exceeds one third of total bandwidth, then
6448 use the correct formula to weight exit nodes when choosing paths.
6449 (Based on patch from Mike Perry.)
6450 - Choose perfectly fairly among routers when choosing by bandwidth and
6451 weighting by fraction of bandwidth provided by exits. Previously, we
6452 would choose with only approximate fairness, and correct ourselves
6453 if we ran off the end of the list. [Bugfix on 0.1.2.x]
6455 o Performance improvements:
6456 - Be more aggressive with freeing buffer RAM or putting it on the
6458 - Use Critical Sections rather than Mutexes for synchronizing threads
6459 on win32; Mutexes are heavier-weight, and designed for synchronizing
6462 o Deprecated and removed features:
6463 - RedirectExits is now deprecated.
6464 - Stop allowing address masks that do not correspond to bit prefixes.
6465 We have warned about these for a really long time; now it's time
6466 to reject them. (Patch from croup.)
6468 o Minor bugfixes (directory):
6469 - Fix another crash bug related to extra-info caching. (Bug found by
6470 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
6471 - Directories no longer return a "304 not modified" when they don't
6472 have the networkstatus the client asked for. Also fix a memory
6473 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
6474 - We had accidentally labelled 0.1.2.x directory servers as not
6475 suitable for begin_dir requests, and had labelled no directory
6476 servers as suitable for uploading extra-info documents. [Bugfix
6479 o Minor bugfixes (dns):
6480 - Fix a crash when DNSPort is set more than once. (Patch from Robert
6481 Hogan.) [Bugfix on 0.2.0.2-alpha]
6482 - Add DNSPort connections to the global connection list, so that we
6483 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
6485 - Fix a dangling reference that could lead to a crash when DNSPort is
6486 changed or closed (Patch from Robert Hogan.) [Bugfix on
6489 o Minor bugfixes (controller):
6490 - Provide DNS expiry times in GMT, not in local time. For backward
6491 compatibility, ADDRMAP events only provide GMT expiry in an extended
6492 field. "GETINFO address-mappings" always does the right thing.
6493 - Use CRLF line endings properly in NS events.
6494 - Terminate multi-line control events properly. (Original patch
6495 from tup.) [Bugfix on 0.1.2.x-alpha]
6496 - Do not include spaces in SOURCE_ADDR fields in STREAM
6497 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
6500 Changes in version 0.1.2.15 - 2007-07-17
6501 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
6502 problems, fixes compilation on BSD, and fixes a variety of other
6503 bugs. Everybody should upgrade.
6505 o Major bugfixes (compilation):
6506 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
6508 o Major bugfixes (crashes):
6509 - Try even harder not to dereference the first character after
6510 an mmap(). Reported by lodger.
6511 - Fix a crash bug in directory authorities when we re-number the
6512 routerlist while inserting a new router.
6513 - When the cached-routers file is an even multiple of the page size,
6514 don't run off the end and crash. (Fixes bug 455; based on idea
6516 - Fix eventdns.c behavior on Solaris: It is critical to include
6517 orconfig.h _before_ sys/types.h, so that we can get the expected
6518 definition of _FILE_OFFSET_BITS.
6520 o Major bugfixes (security):
6521 - Fix a possible buffer overrun when using BSD natd support. Bug
6523 - When sending destroy cells from a circuit's origin, don't include
6524 the reason for tearing down the circuit. The spec says we didn't,
6525 and now we actually don't. Reported by lodger.
6526 - Keep streamids from different exits on a circuit separate. This
6527 bug may have allowed other routers on a given circuit to inject
6528 cells into streams. Reported by lodger; fixes bug 446.
6529 - If there's a never-before-connected-to guard node in our list,
6530 never choose any guards past it. This way we don't expand our
6531 guard list unless we need to.
6533 o Minor bugfixes (guard nodes):
6534 - Weight guard selection by bandwidth, so that low-bandwidth nodes
6535 don't get overused as guards.
6537 o Minor bugfixes (directory):
6538 - Correctly count the number of authorities that recommend each
6539 version. Previously, we were under-counting by 1.
6540 - Fix a potential crash bug when we load many server descriptors at
6541 once and some of them make others of them obsolete. Fixes bug 458.
6543 o Minor bugfixes (hidden services):
6544 - Stop tearing down the whole circuit when the user asks for a
6545 connection to a port that the hidden service didn't configure.
6548 o Minor bugfixes (misc):
6549 - On Windows, we were preventing other processes from reading
6550 cached-routers while Tor was running. Reported by janbar.
6551 - Fix a possible (but very unlikely) bug in picking routers by
6552 bandwidth. Add a log message to confirm that it is in fact
6553 unlikely. Patch from lodger.
6554 - Backport a couple of memory leak fixes.
6555 - Backport miscellaneous cosmetic bugfixes.
6558 Changes in version 0.2.0.2-alpha - 2007-06-02
6559 o Major bugfixes on 0.2.0.1-alpha:
6560 - Fix an assertion failure related to servers without extra-info digests.
6561 Resolves bugs 441 and 442.
6563 o Minor features (directory):
6564 - Support "If-Modified-Since" when answering HTTP requests for
6565 directories, running-routers documents, and network-status documents.
6566 (There's no need to support it for router descriptors, since those
6567 are downloaded by descriptor digest.)
6569 o Minor build issues:
6570 - Clear up some MIPSPro compiler warnings.
6571 - When building from a tarball on a machine that happens to have SVK
6572 installed, report the micro-revision as whatever version existed
6573 in the tarball, not as "x".
6576 Changes in version 0.2.0.1-alpha - 2007-06-01
6577 This early development snapshot provides new features for people running
6578 Tor as both a client and a server (check out the new RelayBandwidth
6579 config options); lets Tor run as a DNS proxy; and generally moves us
6580 forward on a lot of fronts.
6582 o Major features, server usability:
6583 - New config options RelayBandwidthRate and RelayBandwidthBurst:
6584 a separate set of token buckets for relayed traffic. Right now
6585 relayed traffic is defined as answers to directory requests, and
6586 OR connections that don't have any local circuits on them.
6588 o Major features, client usability:
6589 - A client-side DNS proxy feature to replace the need for
6590 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
6591 for DNS requests on port 9999, use the Tor network to resolve them
6592 anonymously, and send the reply back like a regular DNS server.
6593 The code still only implements a subset of DNS.
6594 - Make PreferTunneledDirConns and TunnelDirConns work even when
6595 we have no cached directory info. This means Tor clients can now
6596 do all of their connections protected by TLS.
6598 o Major features, performance and efficiency:
6599 - Directory authorities accept and serve "extra info" documents for
6600 routers. These documents contain fields from router descriptors
6601 that aren't usually needed, and that use a lot of excess
6602 bandwidth. Once these fields are removed from router descriptors,
6603 the bandwidth savings should be about 60%. [Partially implements
6605 - Servers upload extra-info documents to any authority that accepts
6606 them. Authorities (and caches that have been configured to download
6607 extra-info documents) download them as needed. [Partially implements
6609 - Change the way that Tor buffers data that it is waiting to write.
6610 Instead of queueing data cells in an enormous ring buffer for each
6611 client->OR or OR->OR connection, we now queue cells on a separate
6612 queue for each circuit. This lets us use less slack memory, and
6613 will eventually let us be smarter about prioritizing different kinds
6615 - Use memory pools to allocate cells with better speed and memory
6616 efficiency, especially on platforms where malloc() is inefficient.
6617 - Stop reading on edge connections when their corresponding circuit
6618 buffers are full; start again as the circuits empty out.
6620 o Major features, other:
6621 - Add an HSAuthorityRecordStats option that hidden service authorities
6622 can use to track statistics of overall hidden service usage without
6623 logging information that would be very useful to an attacker.
6624 - Start work implementing multi-level keys for directory authorities:
6625 Add a standalone tool to generate key certificates. (Proposal 103.)
6628 - Directory authorities now call routers Stable if they have an
6629 uptime of at least 30 days, even if that's not the median uptime
6630 in the network. Implements proposal 107, suggested by Kevin Bauer
6633 o Minor fixes (resource management):
6634 - Count the number of open sockets separately from the number
6635 of active connection_t objects. This will let us avoid underusing
6636 our allocated connection limit.
6637 - We no longer use socket pairs to link an edge connection to an
6638 anonymous directory connection or a DirPort test connection.
6639 Instead, we track the link internally and transfer the data
6640 in-process. This saves two sockets per "linked" connection (at the
6641 client and at the server), and avoids the nasty Windows socketpair()
6643 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
6644 for every single inactive connection_t. Free items from the
6645 4k/16k-buffer free lists when they haven't been used for a while.
6647 o Minor features (build):
6648 - Make autoconf search for libevent, openssl, and zlib consistently.
6649 - Update deprecated macros in configure.in.
6650 - When warning about missing headers, tell the user to let us
6651 know if the compile succeeds anyway, so we can downgrade the
6653 - Include the current subversion revision as part of the version
6654 string: either fetch it directly if we're in an SVN checkout, do
6655 some magic to guess it if we're in an SVK checkout, or use
6656 the last-detected version if we're building from a .tar.gz.
6657 Use this version consistently in log messages.
6659 o Minor features (logging):
6660 - Always prepend "Bug: " to any log message about a bug.
6661 - Put a platform string (e.g. "Linux i686") in the startup log
6662 message, so when people paste just their logs, we know if it's
6663 OpenBSD or Windows or what.
6664 - When logging memory usage, break down memory used in buffers by
6667 o Minor features (directory system):
6668 - New config option V2AuthoritativeDirectory that all directory
6669 authorities should set. This will let future authorities choose
6670 not to serve V2 directory information.
6671 - Directory authorities allow multiple router descriptors and/or extra
6672 info documents to be uploaded in a single go. This will make
6673 implementing proposal 104 simpler.
6675 o Minor features (controller):
6676 - Add a new config option __DisablePredictedCircuits designed for
6677 use by the controller, when we don't want Tor to build any circuits
6679 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
6680 so we can exit from the middle of the circuit.
6681 - Implement "getinfo status/circuit-established".
6682 - Implement "getinfo status/version/..." so a controller can tell
6683 whether the current version is recommended, and whether any versions
6684 are good, and how many authorities agree. (Patch from shibz.)
6686 o Minor features (hidden services):
6687 - Allow multiple HiddenServicePort directives with the same virtual
6688 port; when they occur, the user is sent round-robin to one
6689 of the target ports chosen at random. Partially fixes bug 393 by
6690 adding limited ad-hoc round-robining.
6692 o Minor features (other):
6694 - Add a new AutomapHostsOnResolve option: when it is enabled, any
6695 resolve request for hosts matching a given pattern causes Tor to
6696 generate an internal virtual address mapping for that host. This
6697 allows DNSPort to work sensibly with hidden service users. By
6698 default, .exit and .onion addresses are remapped; the list of
6699 patterns can be reconfigured with AutomapHostsSuffixes.
6700 - Add an "-F" option to tor-resolve to force a resolve for a .onion
6701 address. Thanks to the AutomapHostsOnResolve option, this is no
6702 longer a completely silly thing to do.
6703 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
6704 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
6705 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
6706 minus 1 byte: the actual maximum declared bandwidth.
6709 - Removed support for the old binary "version 0" controller protocol.
6710 This has been deprecated since 0.1.1, and warnings have been issued
6711 since 0.1.2. When we encounter a v0 control message, we now send
6712 back an error and close the connection.
6713 - Remove the old "dns worker" server DNS code: it hasn't been default
6714 since 0.1.2.2-alpha, and all the servers seem to be using the new
6717 o Minor bugfixes (portability):
6718 - Even though Windows is equally happy with / and \ as path separators,
6719 try to use \ consistently on Windows and / consistently on Unix: it
6720 makes the log messages nicer.
6721 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
6722 - Read resolv.conf files correctly on platforms where read() returns
6723 partial results on small file reads.
6725 o Minor bugfixes (directory):
6726 - Correctly enforce that elements of directory objects do not appear
6727 more often than they are allowed to appear.
6728 - When we are reporting the DirServer line we just parsed, we were
6729 logging the second stanza of the key fingerprint, not the first.
6731 o Minor bugfixes (logging):
6732 - When we hit an EOF on a log (probably because we're shutting down),
6733 don't try to remove the log from the list: just mark it as
6734 unusable. (Bulletproofs against bug 222.)
6736 o Minor bugfixes (other):
6737 - In the exitlist script, only consider the most recently published
6738 server descriptor for each server. Also, when the user requests
6739 a list of servers that _reject_ connections to a given address,
6740 explicitly exclude the IPs that also have servers that accept
6741 connections to that address. (Resolves bug 405.)
6742 - Stop allowing hibernating servers to be "stable" or "fast".
6743 - On Windows, we were preventing other processes from reading
6744 cached-routers while Tor was running. (Reported by janbar)
6745 - Make the NodeFamilies config option work. (Reported by
6746 lodger -- it has never actually worked, even though we added it
6748 - Check return values from pthread_mutex functions.
6749 - Don't save non-general-purpose router descriptors to the disk cache,
6750 because we have no way of remembering what their purpose was when
6752 - Add even more asserts to hunt down bug 417.
6753 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
6754 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
6755 Add a log message to confirm that it is in fact unlikely.
6757 o Minor bugfixes (controller):
6758 - Make 'getinfo fingerprint' return a 551 error if we're not a
6759 server, so we match what the control spec claims we do. Reported
6761 - Fix a typo in an error message when extendcircuit fails that
6762 caused us to not follow the \r\n-based delimiter protocol. Reported
6765 o Code simplifications and refactoring:
6766 - Stop passing around circuit_t and crypt_path_t pointers that are
6767 implicit in other procedure arguments.
6768 - Drop the old code to choke directory connections when the
6769 corresponding OR connections got full: thanks to the cell queue
6770 feature, OR conns don't get full any more.
6771 - Make dns_resolve() handle attaching connections to circuits
6772 properly, so the caller doesn't have to.
6773 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
6774 - Keep the connection array as a dynamic smartlist_t, rather than as
6775 a fixed-sized array. This is important, as the number of connections
6776 is becoming increasingly decoupled from the number of sockets.
6779 Changes in version 0.1.2.14 - 2007-05-25
6780 Tor 0.1.2.14 changes the addresses of two directory authorities (this
6781 change especially affects those who serve or use hidden services),
6782 and fixes several other crash- and security-related bugs.
6784 o Directory authority changes:
6785 - Two directory authorities (moria1 and moria2) just moved to new
6786 IP addresses. This change will particularly affect those who serve
6787 or use hidden services.
6789 o Major bugfixes (crashes):
6790 - If a directory server runs out of space in the connection table
6791 as it's processing a begin_dir request, it will free the exit stream
6792 but leave it attached to the circuit, leading to unpredictable
6793 behavior. (Reported by seeess, fixes bug 425.)
6794 - Fix a bug in dirserv_remove_invalid() that would cause authorities
6795 to corrupt memory under some really unlikely scenarios.
6796 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
6797 - Avoid segfaults when reading from mmaped descriptor file. (Reported
6800 o Major bugfixes (security):
6801 - When choosing an entry guard for a circuit, avoid using guards
6802 that are in the same family as the chosen exit -- not just guards
6803 that are exactly the chosen exit. (Reported by lodger.)
6805 o Major bugfixes (resource management):
6806 - If a directory authority is down, skip it when deciding where to get
6807 networkstatus objects or descriptors. Otherwise we keep asking
6808 every 10 seconds forever. Fixes bug 384.
6809 - Count it as a failure if we fetch a valid network-status but we
6810 don't want to keep it. Otherwise we'll keep fetching it and keep
6811 not wanting to keep it. Fixes part of bug 422.
6812 - If all of our dirservers have given us bad or no networkstatuses
6813 lately, then stop hammering them once per minute even when we
6814 think they're failed. Fixes another part of bug 422.
6817 - Actually set the purpose correctly for descriptors inserted with
6819 - When we have k non-v2 authorities in our DirServer config,
6820 we ignored the last k authorities in the list when updating our
6822 - Correctly back-off from requesting router descriptors that we are
6823 having a hard time downloading.
6824 - Read resolv.conf files correctly on platforms where read() returns
6825 partial results on small file reads.
6826 - Don't rebuild the entire router store every time we get 32K of
6827 routers: rebuild it when the journal gets very large, or when
6828 the gaps in the store get very large.
6831 - When routers publish SVN revisions in their router descriptors,
6832 authorities now include those versions correctly in networkstatus
6834 - Warn when using a version of libevent before 1.3b to run a server on
6835 OSX or BSD: these versions interact badly with userspace threads.
6838 Changes in version 0.1.2.13 - 2007-04-24
6839 This release features some major anonymity fixes, such as safer path
6840 selection; better client performance; faster bootstrapping, better
6841 address detection, and better DNS support for servers; write limiting as
6842 well as read limiting to make servers easier to run; and a huge pile of
6843 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
6845 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
6846 of the Freenode IRC network, remembering his patience and vision for
6847 free speech on the Internet.
6850 - Fix a memory leak when we ask for "all" networkstatuses and we
6851 get one we don't recognize.
6852 - Add more asserts to hunt down bug 417.
6853 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
6856 Changes in version 0.1.2.12-rc - 2007-03-16
6858 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
6859 directory information requested inside Tor connections (i.e. via
6860 begin_dir cells). It only triggered when the same connection was
6861 serving other data at the same time. Reported by seeess.
6864 - When creating a circuit via the controller, send a 'launched'
6865 event when we're done, so we follow the spec better.
6868 Changes in version 0.1.2.11-rc - 2007-03-15
6869 o Minor bugfixes (controller), reported by daejees:
6870 - Correct the control spec to match how the code actually responds
6871 to 'getinfo addr-mappings/*'.
6872 - The control spec described a GUARDS event, but the code
6873 implemented a GUARD event. Standardize on GUARD, but let people
6877 Changes in version 0.1.2.10-rc - 2007-03-07
6878 o Major bugfixes (Windows):
6879 - Do not load the NT services library functions (which may not exist)
6880 just to detect if we're a service trying to shut down. Now we run
6881 on Win98 and friends again.
6883 o Minor bugfixes (other):
6884 - Clarify a couple of log messages.
6885 - Fix a misleading socks5 error number.
6888 Changes in version 0.1.2.9-rc - 2007-03-02
6889 o Major bugfixes (Windows):
6890 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
6891 of the usual GCC "%llu". This prevents a bug when saving 64-bit
6892 int configuration values: the high-order 32 bits would get
6893 truncated. In particular, we were being bitten by the default
6894 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
6895 and maybe also bug 397.)
6897 o Minor bugfixes (performance):
6898 - Use OpenSSL's AES implementation on platforms where it's faster.
6899 This could save us as much as 10% CPU usage.
6901 o Minor bugfixes (server):
6902 - Do not rotate onion key immediately after setting it for the first
6905 o Minor bugfixes (directory authorities):
6906 - Stop calling servers that have been hibernating for a long time
6907 "stable". Also, stop letting hibernating or obsolete servers affect
6908 uptime and bandwidth cutoffs.
6909 - Stop listing hibernating servers in the v1 directory.
6911 o Minor bugfixes (hidden services):
6912 - Upload hidden service descriptors slightly less often, to reduce
6913 load on authorities.
6915 o Minor bugfixes (other):
6916 - Fix an assert that could trigger if a controller quickly set then
6917 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
6918 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
6920 - Fix a potential race condition in the rpm installer. Found by
6922 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
6923 of 2 as indicating that the server is completely bad; it sometimes
6924 means that the server is just bad for the request in question. (may fix
6925 the last of bug 326.)
6926 - Disable encrypted directory connections when we don't have a server
6927 descriptor for the destination. We'll get this working again in
6931 Changes in version 0.1.2.8-beta - 2007-02-26
6932 o Major bugfixes (crashes):
6933 - Stop crashing when the controller asks us to resetconf more than
6934 one config option at once. (Vidalia 0.0.11 does this.)
6935 - Fix a crash that happened on Win98 when we're given command-line
6936 arguments: don't try to load NT service functions from advapi32.dll
6937 except when we need them. (Bug introduced in 0.1.2.7-alpha;
6939 - Fix a longstanding obscure crash bug that could occur when
6940 we run out of DNS worker processes. (Resolves bug 390.)
6942 o Major bugfixes (hidden services):
6943 - Correctly detect whether hidden service descriptor downloads are
6944 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
6946 o Major bugfixes (accounting):
6947 - When we start during an accounting interval before it's time to wake
6948 up, remember to wake up at the correct time. (May fix bug 342.)
6950 o Minor bugfixes (controller):
6951 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
6952 clear the corresponding on_circuit variable, and remember later
6953 that we don't need to send a redundant CLOSED event. (Resolves part
6955 - Report events where a resolve succeeded or where we got a socks
6956 protocol error correctly, rather than calling both of them
6958 - Change reported stream target addresses to IP consistently when
6959 we finally get the IP from an exit node.
6960 - Send log messages to the controller even if they happen to be very
6963 o Minor bugfixes (other):
6964 - Display correct results when reporting which versions are
6965 recommended, and how recommended they are. (Resolves bug 383.)
6966 - Improve our estimates for directory bandwidth to be less random:
6967 guess that an unrecognized directory will have the average bandwidth
6968 from all known directories, not that it will have the average
6969 bandwidth from those directories earlier than it on the list.
6970 - If we start a server with ClientOnly 1, then set ClientOnly to 0
6971 and hup, stop triggering an assert based on an empty onion_key.
6972 - On platforms with no working mmap() equivalent, don't warn the
6973 user when cached-routers doesn't exist.
6974 - Warn the user when mmap() [or its equivalent] fails for some reason
6975 other than file-not-found.
6976 - Don't warn the user when cached-routers.new doesn't exist: that's
6977 perfectly fine when starting up for the first time.
6978 - When EntryNodes are configured, rebuild the guard list to contain,
6979 in order: the EntryNodes that were guards before; the rest of the
6980 EntryNodes; the nodes that were guards before.
6981 - Mask out all signals in sub-threads; only the libevent signal
6982 handler should be processing them. This should prevent some crashes
6983 on some machines using pthreads. (Patch from coderman.)
6984 - Fix switched arguments on memset in the implementation of
6985 tor_munmap() for systems with no mmap() call.
6986 - When Tor receives a router descriptor that it asked for, but
6987 no longer wants (because it has received fresh networkstatuses
6988 in the meantime), do not warn the user. Cache the descriptor if
6989 we're a cache; drop it if we aren't.
6990 - Make earlier entry guards _really_ get retried when the network
6992 - On a malformed DNS reply, always give an error to the corresponding
6994 - Build with recent libevents on platforms that do not define the
6995 nonstandard types "u_int8_t" and friends.
6997 o Minor features (controller):
6998 - Warn the user when an application uses the obsolete binary v0
6999 control protocol. We're planning to remove support for it during
7000 the next development series, so it's good to give people some
7002 - Add STREAM_BW events to report per-entry-stream bandwidth
7003 use. (Patch from Robert Hogan.)
7004 - Rate-limit SIGNEWNYM signals in response to controllers that
7005 impolitely generate them for every single stream. (Patch from
7006 mwenge; closes bug 394.)
7007 - Make REMAP stream events have a SOURCE (cache or exit), and
7008 make them generated in every case where we get a successful
7009 connected or resolved cell.
7011 o Minor bugfixes (performance):
7012 - Call router_have_min_dir_info half as often. (This is showing up in
7013 some profiles, but not others.)
7014 - When using GCC, make log_debug never get called at all, and its
7015 arguments never get evaluated, when no debug logs are configured.
7016 (This is showing up in some profiles, but not others.)
7019 - Remove some never-implemented options. Mark PathlenCoinWeight as
7021 - Implement proposal 106: Stop requiring clients to have well-formed
7022 certificates; stop checking nicknames in certificates. (Clients
7023 have certificates so that they can look like Tor servers, but in
7024 the future we might want to allow them to look like regular TLS
7025 clients instead. Nicknames in certificates serve no purpose other
7026 than making our protocol easier to recognize on the wire.)
7027 - Revise messages on handshake failure again to be even more clear about
7028 which are incoming connections and which are outgoing.
7029 - Discard any v1 directory info that's over 1 month old (for
7030 directories) or over 1 week old (for running-routers lists).
7031 - Do not warn when individual nodes in the configuration's EntryNodes,
7032 ExitNodes, etc are down: warn only when all possible nodes
7033 are down. (Fixes bug 348.)
7034 - Always remove expired routers and networkstatus docs before checking
7035 whether we have enough information to build circuits. (Fixes
7037 - Put a lower-bound on MaxAdvertisedBandwidth.
7040 Changes in version 0.1.2.7-alpha - 2007-02-06
7041 o Major bugfixes (rate limiting):
7042 - Servers decline directory requests much more aggressively when
7043 they're low on bandwidth. Otherwise they end up queueing more and
7044 more directory responses, which can't be good for latency.
7045 - But never refuse directory requests from local addresses.
7046 - Fix a memory leak when sending a 503 response for a networkstatus
7048 - Be willing to read or write on local connections (e.g. controller
7049 connections) even when the global rate limiting buckets are empty.
7050 - If our system clock jumps back in time, don't publish a negative
7051 uptime in the descriptor. Also, don't let the global rate limiting
7052 buckets go absurdly negative.
7053 - Flush local controller connection buffers periodically as we're
7054 writing to them, so we avoid queueing 4+ megabytes of data before
7057 o Major bugfixes (NT services):
7058 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
7059 command-line flag so that admins can override the default by saying
7060 "tor --service install --user "SomeUser"". This will not affect
7061 existing installed services. Also, warn the user that the service
7062 will look for its configuration file in the service user's
7063 %appdata% directory. (We can't do the 'hardwire the user's appdata
7064 directory' trick any more, since we may not have read access to that
7067 o Major bugfixes (other):
7068 - Previously, we would cache up to 16 old networkstatus documents
7069 indefinitely, if they came from nontrusted authorities. Now we
7070 discard them if they are more than 10 days old.
7071 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
7073 - Detect and reject malformed DNS responses containing circular
7075 - If exits are rare enough that we're not marking exits as guards,
7076 ignore exit bandwidth when we're deciding the required bandwidth
7078 - When we're handling a directory connection tunneled over Tor,
7079 don't fill up internal memory buffers with all the data we want
7080 to tunnel; instead, only add it if the OR connection that will
7081 eventually receive it has some room for it. (This can lead to
7082 slowdowns in tunneled dir connections; a better solution will have
7085 o Minor bugfixes (dns):
7086 - Add some defensive programming to eventdns.c in an attempt to catch
7087 possible memory-stomping bugs.
7088 - Detect and reject DNS replies containing IPv4 or IPv6 records with
7089 an incorrect number of bytes. (Previously, we would ignore the
7091 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
7092 in the correct order, and doesn't crash.
7093 - Free memory held in recently-completed DNS lookup attempts on exit.
7094 This was not a memory leak, but may have been hiding memory leaks.
7095 - Handle TTL values correctly on reverse DNS lookups.
7096 - Treat failure to parse resolv.conf as an error.
7098 o Minor bugfixes (other):
7099 - Fix crash with "tor --list-fingerprint" (reported by seeess).
7100 - When computing clock skew from directory HTTP headers, consider what
7101 time it was when we finished asking for the directory, not what
7103 - Expire socks connections if they spend too long waiting for the
7104 handshake to finish. Previously we would let them sit around for
7105 days, if the connecting application didn't close them either.
7106 - And if the socks handshake hasn't started, don't send a
7107 "DNS resolve socks failed" handshake reply; just close it.
7108 - Stop using C functions that OpenBSD's linker doesn't like.
7109 - Don't launch requests for descriptors unless we have networkstatuses
7110 from at least half of the authorities. This delays the first
7111 download slightly under pathological circumstances, but can prevent
7112 us from downloading a bunch of descriptors we don't need.
7113 - Do not log IPs with TLS failures for incoming TLS
7114 connections. (Fixes bug 382.)
7115 - If the user asks to use invalid exit nodes, be willing to use
7117 - Stop using the reserved ac_cv namespace in our configure script.
7118 - Call stat() slightly less often; use fstat() when possible.
7119 - Refactor the way we handle pending circuits when an OR connection
7120 completes or fails, in an attempt to fix a rare crash bug.
7121 - Only rewrite a conn's address based on X-Forwarded-For: headers
7122 if it's a parseable public IP address; and stop adding extra quotes
7123 to the resulting address.
7126 - Weight directory requests by advertised bandwidth. Now we can
7127 let servers enable write limiting but still allow most clients to
7128 succeed at their directory requests. (We still ignore weights when
7129 choosing a directory authority; I hope this is a feature.)
7132 - Create a new file ReleaseNotes which was the old ChangeLog. The
7133 new ChangeLog file now includes the summaries for all development
7135 - Check for addresses with invalid characters at the exit as well
7136 as at the client, and warn less verbosely when they fail. You can
7137 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
7138 - Adapt a patch from goodell to let the contrib/exitlist script
7139 take arguments rather than require direct editing.
7140 - Inform the server operator when we decide not to advertise a
7141 DirPort due to AccountingMax enabled or a low BandwidthRate. It
7142 was confusing Zax, so now we're hopefully more helpful.
7143 - Bring us one step closer to being able to establish an encrypted
7144 directory tunnel without knowing a descriptor first. Still not
7145 ready yet. As part of the change, now assume we can use a
7146 create_fast cell if we don't know anything about a router.
7147 - Allow exit nodes to use nameservers running on ports other than 53.
7148 - Servers now cache reverse DNS replies.
7149 - Add an --ignore-missing-torrc command-line option so that we can
7150 get the "use sensible defaults if the configuration file doesn't
7151 exist" behavior even when specifying a torrc location on the command
7154 o Minor features (controller):
7155 - Track reasons for OR connection failure; make these reasons
7156 available via the controller interface. (Patch from Mike Perry.)
7157 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
7158 can learn when clients are sending malformed hostnames to Tor.
7159 - Clean up documentation for controller status events.
7160 - Add a REMAP status to stream events to note that a stream's
7161 address has changed because of a cached address or a MapAddress
7165 Changes in version 0.1.2.6-alpha - 2007-01-09
7167 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
7168 connection handles more than 4 gigs in either direction, we crash.
7169 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
7170 advertised exit node, somebody might try to exit from us when
7171 we're bootstrapping and before we've built our descriptor yet.
7172 Refuse the connection rather than crashing.
7175 - Warn if we (as a server) find that we've resolved an address that we
7176 weren't planning to resolve.
7177 - Warn that using select() on any libevent version before 1.1 will be
7178 unnecessarily slow (even for select()).
7179 - Flush ERR-level controller status events just like we currently
7180 flush ERR-level log events, so that a Tor shutdown doesn't prevent
7181 the controller from learning about current events.
7183 o Minor features (more controller status events):
7184 - Implement EXTERNAL_ADDRESS server status event so controllers can
7185 learn when our address changes.
7186 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
7187 can learn when directories reject our descriptor.
7188 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
7189 can learn when a client application is speaking a non-socks protocol
7191 - Implement DANGEROUS_SOCKS client status event so controllers
7192 can learn when a client application is leaking DNS addresses.
7193 - Implement BUG general status event so controllers can learn when
7194 Tor is unhappy about its internal invariants.
7195 - Implement CLOCK_SKEW general status event so controllers can learn
7196 when Tor thinks the system clock is set incorrectly.
7197 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
7198 server status events so controllers can learn when their descriptors
7199 are accepted by a directory.
7200 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
7201 server status events so controllers can learn about Tor's progress in
7202 deciding whether it's reachable from the outside.
7203 - Implement BAD_LIBEVENT general status event so controllers can learn
7204 when we have a version/method combination in libevent that needs to
7206 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
7207 and DNS_USELESS server status events so controllers can learn
7208 about changes to DNS server status.
7210 o Minor features (directory):
7211 - Authorities no longer recommend exits as guards if this would shift
7212 too much load to the exit nodes.
7215 Changes in version 0.1.2.5-alpha - 2007-01-06
7217 - Enable write limiting as well as read limiting. Now we sacrifice
7218 capacity if we're pushing out lots of directory traffic, rather
7219 than overrunning the user's intended bandwidth limits.
7220 - Include TLS overhead when counting bandwidth usage; previously, we
7221 would count only the bytes sent over TLS, but not the bytes used
7223 - Support running the Tor service with a torrc not in the same
7224 directory as tor.exe and default to using the torrc located in
7225 the %appdata%\Tor\ of the user who installed the service. Patch
7227 - Servers now check for the case when common DNS requests are going to
7228 wildcarded addresses (i.e. all getting the same answer), and change
7229 their exit policy to reject *:* if it's happening.
7230 - Implement BEGIN_DIR cells, so we can connect to the directory
7231 server via TLS to do encrypted directory requests rather than
7232 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
7233 config options if you like.
7235 o Minor features (config and docs):
7236 - Start using the state file to store bandwidth accounting data:
7237 the bw_accounting file is now obsolete. We'll keep generating it
7238 for a while for people who are still using 0.1.2.4-alpha.
7239 - Try to batch changes to the state file so that we do as few
7240 disk writes as possible while still storing important things in
7242 - The state file and the bw_accounting file get saved less often when
7243 the AvoidDiskWrites config option is set.
7244 - Make PIDFile work on Windows (untested).
7245 - Add internal descriptions for a bunch of configuration options:
7246 accessible via controller interface and in comments in saved
7248 - Reject *:563 (NNTPS) in the default exit policy. We already reject
7249 NNTP by default, so this seems like a sensible addition.
7250 - Clients now reject hostnames with invalid characters. This should
7251 avoid some inadvertent info leaks. Add an option
7252 AllowNonRFC953Hostnames to disable this behavior, in case somebody
7253 is running a private network with hosts called @, !, and #.
7254 - Add a maintainer script to tell us which options are missing
7255 documentation: "make check-docs".
7256 - Add a new address-spec.txt document to describe our special-case
7257 addresses: .exit, .onion, and .noconnnect.
7259 o Minor features (DNS):
7260 - Ongoing work on eventdns infrastructure: now it has dns server
7261 and ipv6 support. One day Tor will make use of it.
7262 - Add client-side caching for reverse DNS lookups.
7263 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
7264 - When we change nameservers or IP addresses, reset and re-launch
7265 our tests for DNS hijacking.
7267 o Minor features (directory):
7268 - Authorities now specify server versions in networkstatus. This adds
7269 about 2% to the size of compressed networkstatus docs, and allows
7270 clients to tell which servers support BEGIN_DIR and which don't.
7271 The implementation is forward-compatible with a proposed future
7272 protocol version scheme not tied to Tor versions.
7273 - DirServer configuration lines now have an orport= option so
7274 clients can open encrypted tunnels to the authorities without
7275 having downloaded their descriptors yet. Enabled for moria1,
7276 moria2, tor26, and lefkada now in the default configuration.
7277 - Directory servers are more willing to send a 503 "busy" if they
7278 are near their write limit, especially for v1 directory requests.
7279 Now they can use their limited bandwidth for actual Tor traffic.
7280 - Clients track responses with status 503 from dirservers. After a
7281 dirserver has given us a 503, we try not to use it until an hour has
7282 gone by, or until we have no dirservers that haven't given us a 503.
7283 - When we get a 503 from a directory, and we're not a server, we don't
7284 count the failure against the total number of failures allowed
7285 for the thing we're trying to download.
7286 - Report X-Your-Address-Is correctly from tunneled directory
7287 connections; don't report X-Your-Address-Is when it's an internal
7288 address; and never believe reported remote addresses when they're
7290 - Protect against an unlikely DoS attack on directory servers.
7291 - Add a BadDirectory flag to network status docs so that authorities
7292 can (eventually) tell clients about caches they believe to be
7295 o Minor features (controller):
7296 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
7297 - Reimplement GETINFO so that info/names stays in sync with the
7299 - Implement "GETINFO fingerprint".
7300 - Implement "SETEVENTS GUARD" so controllers can get updates on
7301 entry guard status as it changes.
7303 o Minor features (clean up obsolete pieces):
7304 - Remove some options that have been deprecated since at least
7305 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
7306 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
7308 - We no longer look for identity and onion keys in "identity.key" and
7309 "onion.key" -- these were replaced by secret_id_key and
7310 secret_onion_key in 0.0.8pre1.
7311 - We no longer require unrecognized directory entries to be
7314 o Major bugfixes (security):
7315 - Stop sending the HttpProxyAuthenticator string to directory
7316 servers when directory connections are tunnelled through Tor.
7317 - Clients no longer store bandwidth history in the state file.
7318 - Do not log introduction points for hidden services if SafeLogging
7320 - When generating bandwidth history, round down to the nearest
7321 1k. When storing accounting data, round up to the nearest 1k.
7322 - When we're running as a server, remember when we last rotated onion
7323 keys, so that we will rotate keys once they're a week old even if
7324 we never stay up for a week ourselves.
7326 o Major bugfixes (other):
7327 - Fix a longstanding bug in eventdns that prevented the count of
7328 timed-out resolves from ever being reset. This bug caused us to
7329 give up on a nameserver the third time it timed out, and try it
7330 10 seconds later... and to give up on it every time it timed out
7332 - Take out the '5 second' timeout from the connection retry
7333 schedule. Now the first connect attempt will wait a full 10
7334 seconds before switching to a new circuit. Perhaps this will help
7335 a lot. Based on observations from Mike Perry.
7336 - Fix a bug on the Windows implementation of tor_mmap_file() that
7337 would prevent the cached-routers file from ever loading. Reported
7341 - Fix an assert failure when a directory authority sets
7342 AuthDirRejectUnlisted and then receives a descriptor from an
7343 unlisted router. Reported by seeess.
7344 - Avoid a double-free when parsing malformed DirServer lines.
7345 - Fix a bug when a BSD-style PF socket is first used. Patch from
7347 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
7348 to resolve an address at a given exit node even when they ask for
7350 - Servers no longer ever list themselves in their "family" line,
7351 even if configured to do so. This makes it easier to configure
7352 family lists conveniently.
7353 - When running as a server, don't fall back to 127.0.0.1 when no
7354 nameservers are configured in /etc/resolv.conf; instead, make the
7355 user fix resolv.conf or specify nameservers explicitly. (Resolves
7357 - Stop accepting certain malformed ports in configured exit policies.
7358 - Don't re-write the fingerprint file every restart, unless it has
7360 - Stop warning when a single nameserver fails: only warn when _all_ of
7361 our nameservers have failed. Also, when we only have one nameserver,
7362 raise the threshold for deciding that the nameserver is dead.
7363 - Directory authorities now only decide that routers are reachable
7364 if their identity keys are as expected.
7365 - When the user uses bad syntax in the Log config line, stop
7366 suggesting other bad syntax as a replacement.
7367 - Correctly detect ipv6 DNS capability on OpenBSD.
7369 o Minor bugfixes (controller):
7370 - Report the circuit number correctly in STREAM CLOSED events. Bug
7371 reported by Mike Perry.
7372 - Do not report bizarre values for results of accounting GETINFOs
7373 when the last second's write or read exceeds the allotted bandwidth.
7374 - Report "unrecognized key" rather than an empty string when the
7375 controller tries to fetch a networkstatus that doesn't exist.
7378 Changes in version 0.1.1.26 - 2006-12-14
7379 o Security bugfixes:
7380 - Stop sending the HttpProxyAuthenticator string to directory
7381 servers when directory connections are tunnelled through Tor.
7382 - Clients no longer store bandwidth history in the state file.
7383 - Do not log introduction points for hidden services if SafeLogging
7387 - Fix an assert failure when a directory authority sets
7388 AuthDirRejectUnlisted and then receives a descriptor from an
7389 unlisted router (reported by seeess).
7392 Changes in version 0.1.2.4-alpha - 2006-12-03
7394 - Add support for using natd; this allows FreeBSDs earlier than
7395 5.1.2 to have ipfw send connections through Tor without using
7396 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
7399 - Make all connections to addresses of the form ".noconnect"
7400 immediately get closed. This lets application/controller combos
7401 successfully test whether they're talking to the same Tor by
7402 watching for STREAM events.
7403 - Make cross.sh cross-compilation script work even when autogen.sh
7404 hasn't been run. (Patch from Michael Mohr.)
7405 - Statistics dumped by -USR2 now include a breakdown of public key
7406 operations, for profiling.
7409 - Fix a major leak when directory authorities parse their
7410 approved-routers list, a minor memory leak when we fail to pick
7411 an exit node, and a few rare leaks on errors.
7412 - Handle TransPort connections even when the server sends data before
7413 the client sends data. Previously, the connection would just hang
7414 until the client sent data. (Patch from tup based on patch from
7416 - Avoid assert failure when our cached-routers file is empty on
7420 - Don't log spurious warnings when we see a circuit close reason we
7421 don't recognize; it's probably just from a newer version of Tor.
7422 - Have directory authorities allow larger amounts of drift in uptime
7423 without replacing the server descriptor: previously, a server that
7424 restarted every 30 minutes could have 48 "interesting" descriptors
7426 - Start linking to the Tor specification and Tor reference manual
7427 correctly in the Windows installer.
7428 - Add Vidalia to the OS X uninstaller script, so when we uninstall
7429 Tor/Privoxy we also uninstall Vidalia.
7430 - Resume building on Irix64, and fix a lot of warnings from its
7432 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
7433 when we're running as a client.
7436 Changes in version 0.1.1.25 - 2006-11-04
7438 - When a client asks us to resolve (rather than connect to)
7439 an address, and we have a cached answer, give them the cached
7440 answer. Previously, we would give them no answer at all.
7441 - We were building exactly the wrong circuits when we predict
7442 hidden service requirements, meaning Tor would have to build all
7443 its circuits on demand.
7444 - If none of our live entry guards have a high uptime, but we
7445 require a guard with a high uptime, try adding a new guard before
7446 we give up on the requirement. This patch should make long-lived
7447 connections more stable on average.
7448 - When testing reachability of our DirPort, don't launch new
7449 tests when there's already one in progress -- unreachable
7450 servers were stacking up dozens of testing streams.
7452 o Security bugfixes:
7453 - When the user sends a NEWNYM signal, clear the client-side DNS
7454 cache too. Otherwise we continue to act on previous information.
7457 - Avoid a memory corruption bug when creating a hash table for
7459 - Avoid possibility of controller-triggered crash when misusing
7460 certain commands from a v0 controller on platforms that do not
7461 handle printf("%s",NULL) gracefully.
7462 - Avoid infinite loop on unexpected controller input.
7463 - Don't log spurious warnings when we see a circuit close reason we
7464 don't recognize; it's probably just from a newer version of Tor.
7465 - Add Vidalia to the OS X uninstaller script, so when we uninstall
7466 Tor/Privoxy we also uninstall Vidalia.
7469 Changes in version 0.1.2.3-alpha - 2006-10-29
7471 - Prepare for servers to publish descriptors less often: never
7472 discard a descriptor simply for being too old until either it is
7473 recommended by no authorities, or until we get a better one for
7474 the same router. Make caches consider retaining old recommended
7475 routers for even longer.
7476 - If most authorities set a BadExit flag for a server, clients
7477 don't think of it as a general-purpose exit. Clients only consider
7478 authorities that advertise themselves as listing bad exits.
7479 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
7480 headers for content, so that we can work better in the presence of
7481 caching HTTP proxies.
7482 - Allow authorities to list nodes as bad exits by fingerprint or by
7485 o Minor features, controller:
7486 - Add a REASON field to CIRC events; for backward compatibility, this
7487 field is sent only to controllers that have enabled the extended
7488 event format. Also, add additional reason codes to explain why
7489 a given circuit has been destroyed or truncated. (Patches from
7491 - Add a REMOTE_REASON field to extended CIRC events to tell the
7492 controller about why a remote OR told us to close a circuit.
7493 - Stream events also now have REASON and REMOTE_REASON fields,
7494 working much like those for circuit events.
7495 - There's now a GETINFO ns/... field so that controllers can ask Tor
7496 about the current status of a router.
7497 - A new event type "NS" to inform a controller when our opinion of
7498 a router's status has changed.
7499 - Add a GETINFO events/names and GETINFO features/names so controllers
7500 can tell which events and features are supported.
7501 - A new CLEARDNSCACHE signal to allow controllers to clear the
7502 client-side DNS cache without expiring circuits.
7504 o Security bugfixes:
7505 - When the user sends a NEWNYM signal, clear the client-side DNS
7506 cache too. Otherwise we continue to act on previous information.
7509 - Avoid sending junk to controllers or segfaulting when a controller
7510 uses EVENT_NEW_DESC with verbose nicknames.
7511 - Stop triggering asserts if the controller tries to extend hidden
7512 service circuits (reported by mwenge).
7513 - Avoid infinite loop on unexpected controller input.
7514 - When the controller does a "GETINFO network-status", tell it
7515 about even those routers whose descriptors are very old, and use
7516 long nicknames where appropriate.
7517 - Change NT service functions to be loaded on demand. This lets us
7518 build with MinGW without breaking Tor for Windows 98 users.
7519 - Do DirPort reachability tests less often, since a single test
7520 chews through many circuits before giving up.
7521 - In the hidden service example in torrc.sample, stop recommending
7522 esoteric and discouraged hidden service options.
7523 - When stopping an NT service, wait up to 10 sec for it to actually
7524 stop. (Patch from Matt Edman; resolves bug 295.)
7525 - Fix handling of verbose nicknames with ORCONN controller events:
7526 make them show up exactly when requested, rather than exactly when
7528 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
7529 printing a duplicate "$" in the keys we send (reported by mwenge).
7530 - Correctly set maximum connection limit on Cygwin. (This time
7532 - Try to detect Windows correctly when cross-compiling.
7533 - Detect the size of the routers file correctly even if it is
7534 corrupted (on systems without mmap) or not page-aligned (on systems
7535 with mmap). This bug was harmless.
7536 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
7537 to open a stream fails; now we do in more cases. This should
7538 make clients able to find a good exit faster in some cases, since
7539 unhandleable requests will now get an error rather than timing out.
7540 - Resolve two memory leaks when rebuilding the on-disk router cache
7541 (reported by fookoowa).
7542 - Clean up minor code warnings suggested by the MIPSpro C compiler,
7543 and reported by some Centos users.
7544 - Controller signals now work on non-Unix platforms that don't define
7545 SIGUSR1 and SIGUSR2 the way we expect.
7546 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
7547 values before failing, and always enables eventdns.
7548 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
7549 Try to fix this in configure.in by checking for most functions
7550 before we check for libevent.
7553 Changes in version 0.1.2.2-alpha - 2006-10-07
7555 - Make our async eventdns library on-by-default for Tor servers,
7556 and plan to deprecate the separate dnsworker threads.
7557 - Add server-side support for "reverse" DNS lookups (using PTR
7558 records so clients can determine the canonical hostname for a given
7559 IPv4 address). Only supported by servers using eventdns; servers
7560 now announce in their descriptors whether they support eventdns.
7561 - Specify and implement client-side SOCKS5 interface for reverse DNS
7562 lookups (see doc/socks-extensions.txt).
7563 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
7564 connect to directory servers through Tor. Previously, clients needed
7565 to find Tor exits to make private connections to directory servers.
7566 - Avoid choosing Exit nodes for entry or middle hops when the
7567 total bandwidth available from non-Exit nodes is much higher than
7568 the total bandwidth available from Exit nodes.
7569 - Workaround for name servers (like Earthlink's) that hijack failing
7570 DNS requests and replace the no-such-server answer with a "helpful"
7571 redirect to an advertising-driven search portal. Also work around
7572 DNS hijackers who "helpfully" decline to hijack known-invalid
7573 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
7574 lets you turn it off.
7575 - Send out a burst of long-range padding cells once we've established
7576 that we're reachable. Spread them over 4 circuits, so hopefully
7577 a few will be fast. This exercises our bandwidth and bootstraps
7578 us into the directory more quickly.
7580 o New/improved config options:
7581 - Add new config option "ResolvConf" to let the server operator
7582 choose an alternate resolve.conf file when using eventdns.
7583 - Add an "EnforceDistinctSubnets" option to control our "exclude
7584 servers on the same /16" behavior. It's still on by default; this
7585 is mostly for people who want to operate private test networks with
7586 all the machines on the same subnet.
7587 - If one of our entry guards is on the ExcludeNodes list, or the
7588 directory authorities don't think it's a good guard, treat it as
7589 if it were unlisted: stop using it as a guard, and throw it off
7590 the guards list if it stays that way for a long time.
7591 - Allow directory authorities to be marked separately as authorities
7592 for the v1 directory protocol, the v2 directory protocol, and
7593 as hidden service directories, to make it easier to retire old
7594 authorities. V1 authorities should set "HSAuthoritativeDir 1"
7595 to continue being hidden service authorities too.
7596 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
7598 o Minor features, controller:
7599 - Fix CIRC controller events so that controllers can learn the
7600 identity digests of non-Named servers used in circuit paths.
7601 - Let controllers ask for more useful identifiers for servers. Instead
7602 of learning identity digests for un-Named servers and nicknames
7603 for Named servers, the new identifiers include digest, nickname,
7604 and indication of Named status. Off by default; see control-spec.txt
7605 for more information.
7606 - Add a "getinfo address" controller command so it can display Tor's
7607 best guess to the user.
7608 - New controller event to alert the controller when our server
7609 descriptor has changed.
7610 - Give more meaningful errors on controller authentication failure.
7612 o Minor features, other:
7613 - When asked to resolve a hostname, don't use non-exit servers unless
7614 requested to do so. This allows servers with broken DNS to be
7615 useful to the network.
7616 - Divide eventdns log messages into warn and info messages.
7617 - Reserve the nickname "Unnamed" for routers that can't pick
7618 a hostname: any router can call itself Unnamed; directory
7619 authorities will never allocate Unnamed to any particular router;
7620 clients won't believe that any router is the canonical Unnamed.
7621 - Only include function names in log messages for info/debug messages.
7622 For notice/warn/err, the content of the message should be clear on
7623 its own, and printing the function name only confuses users.
7624 - Avoid some false positives during reachability testing: don't try
7625 to test via a server that's on the same /24 as us.
7626 - If we fail to build a circuit to an intended enclave, and it's
7627 not mandatory that we use that enclave, stop wanting it.
7628 - When eventdns is enabled, allow multithreaded builds on NetBSD and
7629 OpenBSD. (We had previously disabled threads on these platforms
7630 because they didn't have working thread-safe resolver functions.)
7632 o Major bugfixes, anonymity/security:
7633 - If a client asked for a server by name, and there's a named server
7634 in our network-status but we don't have its descriptor yet, we
7635 could return an unnamed server instead.
7636 - Fix NetBSD bug that could allow someone to force uninitialized RAM
7637 to be sent to a server's DNS resolver. This only affects NetBSD
7638 and other platforms that do not bounds-check tolower().
7639 - Reject (most) attempts to use Tor circuits with length one. (If
7640 many people start using Tor as a one-hop proxy, exit nodes become
7641 a more attractive target for compromise.)
7642 - Just because your DirPort is open doesn't mean people should be
7643 able to remotely teach you about hidden service descriptors. Now
7644 only accept rendezvous posts if you've got HSAuthoritativeDir set.
7646 o Major bugfixes, other:
7647 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
7648 - When a client asks the server to resolve (not connect to)
7649 an address, and it has a cached answer, give them the cached answer.
7650 Previously, the server would give them no answer at all.
7651 - Allow really slow clients to not hang up five minutes into their
7652 directory downloads (suggested by Adam J. Richter).
7653 - We were building exactly the wrong circuits when we anticipated
7654 hidden service requirements, meaning Tor would have to build all
7655 its circuits on demand.
7656 - Avoid crashing when we mmap a router cache file of size 0.
7657 - When testing reachability of our DirPort, don't launch new
7658 tests when there's already one in progress -- unreachable
7659 servers were stacking up dozens of testing streams.
7661 o Minor bugfixes, correctness:
7662 - If we're a directory mirror and we ask for "all" network status
7663 documents, we would discard status documents from authorities
7665 - Avoid a memory corruption bug when creating a hash table for
7667 - Avoid controller-triggered crash when misusing certain commands
7668 from a v0 controller on platforms that do not handle
7669 printf("%s",NULL) gracefully.
7670 - Don't crash when a controller sends a third argument to an
7671 "extendcircuit" request.
7672 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
7673 response; fix error code when "getinfo dir/status/" fails.
7674 - Avoid crash when telling controller stream-status and a stream
7676 - Patch from Adam Langley to fix assert() in eventdns.c.
7677 - Fix a debug log message in eventdns to say "X resolved to Y"
7678 instead of "X resolved to X".
7679 - Make eventdns give strings for DNS errors, not just error numbers.
7680 - Track unreachable entry guards correctly: don't conflate
7681 'unreachable by us right now' with 'listed as down by the directory
7682 authorities'. With the old code, if a guard was unreachable by
7683 us but listed as running, it would clog our guard list forever.
7684 - Behave correctly in case we ever have a network with more than
7685 2GB/s total advertised capacity.
7686 - Make TrackExitHosts case-insensitive, and fix the behavior of
7687 ".suffix" TrackExitHosts items to avoid matching in the middle of
7689 - Finally fix the openssl warnings from newer gccs that believe that
7690 ignoring a return value is okay, but casting a return value and
7691 then ignoring it is a sign of madness.
7692 - Prevent the contrib/exitlist script from printing the same
7693 result more than once.
7694 - Patch from Steve Hildrey: Generate network status correctly on
7695 non-versioning dirservers.
7696 - Don't listen to the X-Your-Address-Is hint if you did the lookup
7697 via Tor; otherwise you'll think you're the exit node's IP address.
7699 o Minor bugfixes, performance:
7700 - Two small performance improvements on parsing descriptors.
7701 - Major performance improvement on inserting descriptors: change
7702 algorithm from O(n^2) to O(n).
7703 - Make the common memory allocation path faster on machines where
7704 malloc(0) returns a pointer.
7705 - Start remembering X-Your-Address-Is directory hints even if you're
7706 a client, so you can become a server more smoothly.
7707 - Avoid duplicate entries on MyFamily line in server descriptor.
7709 o Packaging, features:
7710 - Remove architecture from OS X builds. The official builds are
7711 now universal binaries.
7712 - The Debian package now uses --verify-config when (re)starting,
7713 to distinguish configuration errors from other errors.
7714 - Update RPMs to require libevent 1.1b.
7716 o Packaging, bugfixes:
7717 - Patches so Tor builds with MinGW on Windows.
7718 - Patches so Tor might run on Cygwin again.
7719 - Resume building on non-gcc compilers and ancient gcc. Resume
7720 building with the -O0 compile flag. Resume building cleanly on
7722 - Run correctly on OS X platforms with case-sensitive filesystems.
7723 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
7724 - Add autoconf checks so Tor can build on Solaris x86 again.
7727 - Documented (and renamed) ServerDNSSearchDomains and
7728 ServerDNSResolvConfFile options.
7729 - Be clearer that the *ListenAddress directives can be repeated
7733 Changes in version 0.1.1.24 - 2006-09-29
7735 - Allow really slow clients to not hang up five minutes into their
7736 directory downloads (suggested by Adam J. Richter).
7737 - Fix major performance regression from 0.1.0.x: instead of checking
7738 whether we have enough directory information every time we want to
7739 do something, only check when the directory information has changed.
7740 This should improve client CPU usage by 25-50%.
7741 - Don't crash if, after a server has been running for a while,
7742 it can't resolve its hostname.
7745 - Allow Tor to start when RunAsDaemon is set but no logs are set.
7746 - Don't crash when the controller receives a third argument to an
7747 "extendcircuit" request.
7748 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
7749 response; fix error code when "getinfo dir/status/" fails.
7750 - Fix configure.in to not produce broken configure files with
7751 more recent versions of autoconf. Thanks to Clint for his auto*
7753 - Fix security bug on NetBSD that could allow someone to force
7754 uninitialized RAM to be sent to a server's DNS resolver. This
7755 only affects NetBSD and other platforms that do not bounds-check
7757 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
7758 methods: these are known to be buggy.
7759 - If we're a directory mirror and we ask for "all" network status
7760 documents, we would discard status documents from authorities
7764 Changes in version 0.1.2.1-alpha - 2006-08-27
7766 - Add "eventdns" async dns library from Adam Langley, tweaked to
7767 build on OSX and Windows. Only enabled if you pass the
7768 --enable-eventdns argument to configure.
7769 - Allow servers with no hostname or IP address to learn their
7770 IP address by asking the directory authorities. This code only
7771 kicks in when you would normally have exited with a "no address"
7772 error. Nothing's authenticated, so use with care.
7773 - Rather than waiting a fixed amount of time between retrying
7774 application connections, we wait only 5 seconds for the first,
7775 10 seconds for the second, and 15 seconds for each retry after
7776 that. Hopefully this will improve the expected user experience.
7777 - Patch from Tup to add support for transparent AP connections:
7778 this basically bundles the functionality of trans-proxy-tor
7779 into the Tor mainline. Now hosts with compliant pf/netfilter
7780 implementations can redirect TCP connections straight to Tor
7781 without diverting through SOCKS. Needs docs.
7782 - Busy directory servers save lots of memory by spooling server
7783 descriptors, v1 directories, and v2 networkstatus docs to buffers
7784 as needed rather than en masse. Also mmap the cached-routers
7785 files, so we don't need to keep the whole thing in memory too.
7786 - Automatically avoid picking more than one node from the same
7787 /16 network when constructing a circuit.
7788 - Revise and clean up the torrc.sample that we ship with; add
7789 a section for BandwidthRate and BandwidthBurst.
7792 - Split circuit_t into origin_circuit_t and or_circuit_t, and
7793 split connection_t into edge, or, dir, control, and base structs.
7794 These will save quite a bit of memory on busy servers, and they'll
7795 also help us track down bugs in the code and bugs in the spec.
7796 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
7797 or later. Log when we are doing this, so we can diagnose it when
7798 it fails. (Also, recommend libevent 1.1b for kqueue and
7799 win32 methods; deprecate libevent 1.0b harder; make libevent
7800 recommendation system saner.)
7801 - Start being able to build universal binaries on OS X (thanks
7803 - Export the default exit policy via the control port, so controllers
7804 don't need to guess what it is / will be later.
7805 - Add a man page entry for ProtocolWarnings.
7806 - Add TestVia config option to the man page.
7807 - Remove even more protocol-related warnings from Tor server logs,
7808 such as bad TLS handshakes and malformed begin cells.
7809 - Stop fetching descriptors if you're not a dir mirror and you
7810 haven't tried to establish any circuits lately. [This currently
7811 causes some dangerous behavior, because when you start up again
7812 you'll use your ancient server descriptors.]
7813 - New DirPort behavior: if you have your dirport set, you download
7814 descriptors aggressively like a directory mirror, whether or not
7816 - Get rid of the router_retry_connections notion. Now routers
7817 no longer try to rebuild long-term connections to directory
7818 authorities, and directory authorities no longer try to rebuild
7819 long-term connections to all servers. We still don't hang up
7820 connections in these two cases though -- we need to look at it
7821 more carefully to avoid flapping, and we likely need to wait til
7822 0.1.1.x is obsolete.
7823 - Drop compatibility with obsolete Tors that permit create cells
7824 to have the wrong circ_id_type.
7825 - Re-enable per-connection rate limiting. Get rid of the "OP
7826 bandwidth" concept. Lay groundwork for "bandwidth classes" --
7827 separate global buckets that apply depending on what sort of conn
7829 - Start publishing one minute or so after we find our ORPort
7830 to be reachable. This will help reduce the number of descriptors
7831 we have for ourselves floating around, since it's quite likely
7832 other things (e.g. DirPort) will change during that minute too.
7833 - Fork the v1 directory protocol into its own spec document,
7834 and mark dir-spec.txt as the currently correct (v2) spec.
7837 - When we find our DirPort to be reachable, publish a new descriptor
7838 so we'll tell the world (reported by pnx).
7839 - Publish a new descriptor after we hup/reload. This is important
7840 if our config has changed such that we'll want to start advertising
7841 our DirPort now, etc.
7842 - Allow Tor to start when RunAsDaemon is set but no logs are set.
7843 - When we have a state file we cannot parse, tell the user and
7844 move it aside. Now we avoid situations where the user starts
7845 Tor in 1904, Tor writes a state file with that timestamp in it,
7846 the user fixes her clock, and Tor refuses to start.
7847 - Fix configure.in to not produce broken configure files with
7848 more recent versions of autoconf. Thanks to Clint for his auto*
7850 - "tor --verify-config" now exits with -1(255) or 0 depending on
7851 whether the config options are bad or good.
7852 - Resolve bug 321 when using dnsworkers: append a period to every
7853 address we resolve at the exit node, so that we do not accidentally
7854 pick up local addresses, and so that failing searches are retried
7855 in the resolver search domains. (This is already solved for
7856 eventdns.) (This breaks Blossom servers for now.)
7857 - If we are using an exit enclave and we can't connect, e.g. because
7858 its webserver is misconfigured to not listen on localhost, then
7859 back off and try connecting from somewhere else before we fail.
7862 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
7863 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
7864 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
7865 when the IP address is mapped through MapAddress to a hostname.
7866 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
7867 useless IPv6 DNS resolves.
7868 - Patch suggested by Karsten Loesing: respond to SIGNAL command
7869 before we execute the signal, in case the signal shuts us down.
7870 - Clean up AllowInvalidNodes man page entry.
7871 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
7872 - Add more asserts to track down an assert error on a windows Tor
7873 server with connection_add being called with socket == -1.
7874 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
7875 - Fix misleading log messages: an entry guard that is "unlisted",
7876 as well as not known to be "down" (because we've never heard
7877 of it), is not therefore "up".
7878 - Remove code to special-case "-cvs" ending, since it has not
7879 actually mattered since 0.0.9.
7880 - Make our socks5 handling more robust to broken socks clients:
7881 throw out everything waiting on the buffer in between socks
7882 handshake phases, since they can't possibly (so the theory
7883 goes) have predicted what we plan to respond to them.
7886 Changes in version 0.1.1.23 - 2006-07-30
7888 - Fast Tor servers, especially exit nodes, were triggering asserts
7889 due to a bug in handling the list of pending DNS resolves. Some
7890 bugs still remain here; we're hunting them.
7891 - Entry guards could crash clients by sending unexpected input.
7892 - More fixes on reachability testing: if you find yourself reachable,
7893 then don't ever make any client requests (so you stop predicting
7894 circuits), then hup or have your clock jump, then later your IP
7895 changes, you won't think circuits are working, so you won't try to
7896 test reachability, so you won't publish.
7899 - Avoid a crash if the controller does a resetconf firewallports
7900 and then a setconf fascistfirewall=1.
7901 - Avoid an integer underflow when the dir authority decides whether
7902 a router is stable: we might wrongly label it stable, and compute
7903 a slightly wrong median stability, when a descriptor is published
7905 - Fix a place where we might trigger an assert if we can't build our
7906 own server descriptor yet.
7909 Changes in version 0.1.1.22 - 2006-07-05
7911 - Fix a big bug that was causing servers to not find themselves
7912 reachable if they changed IP addresses. Since only 0.1.1.22+
7913 servers can do reachability testing correctly, now we automatically
7914 make sure to test via one of these.
7915 - Fix to allow clients and mirrors to learn directory info from
7916 descriptor downloads that get cut off partway through.
7917 - Directory authorities had a bug in deciding if a newly published
7918 descriptor was novel enough to make everybody want a copy -- a few
7919 servers seem to be publishing new descriptors many times a minute.
7921 - Fix a rare bug that was causing some servers to complain about
7922 "closing wedged cpuworkers" and skip some circuit create requests.
7923 - Make the Exit flag in directory status documents actually work.
7926 Changes in version 0.1.1.21 - 2006-06-10
7927 o Crash and assert fixes from 0.1.1.20:
7928 - Fix a rare crash on Tor servers that have enabled hibernation.
7929 - Fix a seg fault on startup for Tor networks that use only one
7930 directory authority.
7931 - Fix an assert from a race condition that occurs on Tor servers
7932 while exiting, where various threads are trying to log that they're
7933 exiting, and delete the logs, at the same time.
7934 - Make our unit tests pass again on certain obscure platforms.
7937 - Add support for building SUSE RPM packages.
7938 - Speed up initial bootstrapping for clients: if we are making our
7939 first ever connection to any entry guard, then don't mark it down
7941 - When only one Tor server in the network is labelled as a guard,
7942 and we've already picked him, we would cycle endlessly picking him
7943 again, being unhappy about it, etc. Now we specifically exclude
7944 current guards when picking a new guard.
7945 - Servers send create cells more reliably after the TLS connection
7946 is established: we were sometimes forgetting to send half of them
7947 when we had more than one pending.
7948 - If we get a create cell that asks us to extend somewhere, but the
7949 Tor server there doesn't match the expected digest, we now send
7950 a destroy cell back, rather than silently doing nothing.
7951 - Make options->RedirectExit work again.
7952 - Make cookie authentication for the controller work again.
7953 - Stop being picky about unusual characters in the arguments to
7954 mapaddress. It's none of our business.
7955 - Add a new config option "TestVia" that lets you specify preferred
7956 middle hops to use for test circuits. Perhaps this will let me
7957 debug the reachability problems better.
7959 o Log / documentation fixes:
7960 - If we're a server and some peer has a broken TLS certificate, don't
7961 log about it unless ProtocolWarnings is set, i.e., we want to hear
7962 about protocol violations by others.
7963 - Fix spelling of VirtualAddrNetwork in man page.
7964 - Add a better explanation at the top of the autogenerated torrc file
7965 about what happened to our old torrc.
7968 Changes in version 0.1.1.20 - 2006-05-23
7970 - Downgrade a log severity where servers complain that they're
7972 - Avoid a compile warning on FreeBSD.
7973 - Remove string size limit on NEWDESC messages; solve bug 291.
7974 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
7975 more thoroughly when we're running on windows.
7978 Changes in version 0.1.1.19-rc - 2006-05-03
7980 - Regenerate our local descriptor if it's dirty and we try to use
7981 it locally (e.g. if it changes during reachability detection).
7982 - If we setconf our ORPort to 0, we continued to listen on the
7983 old ORPort and receive connections.
7984 - Avoid a second warning about machine/limits.h on Debian
7986 - Be willing to add our own routerinfo into the routerlist.
7987 Now authorities will include themselves in their directories
7988 and network-statuses.
7989 - Stop trying to upload rendezvous descriptors to every
7990 directory authority: only try the v1 authorities.
7991 - Servers no longer complain when they think they're not
7992 registered with the directory authorities. There were too many
7994 - Backport dist-rpm changes so rpms can be built without errors.
7997 - Implement an option, VirtualAddrMask, to set which addresses
7998 get handed out in response to mapaddress requests. This works
7999 around a bug in tsocks where 127.0.0.0/8 is never socksified.
8002 Changes in version 0.1.1.18-rc - 2006-04-10
8004 - Work harder to download live network-statuses from all the
8005 directory authorities we know about. Improve the threshold
8006 decision logic so we're more robust to edge cases.
8007 - When fetching rendezvous descriptors, we were willing to ask
8008 v2 authorities too, which would always return 404.
8011 - Stop listing down or invalid nodes in the v1 directory. This will
8012 reduce its bulk by about 1/3, and reduce load on directory
8014 - When deciding whether a router is Fast or Guard-worthy, consider
8015 his advertised BandwidthRate and not just the BandwidthCapacity.
8016 - No longer ship INSTALL and README files -- they are useless now.
8017 - Force rpmbuild to behave and honor target_cpu.
8018 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
8019 - Start to include translated versions of the tor-doc-*.html
8020 files, along with the screenshots. Still needs more work.
8021 - Start sending back 512 and 451 errors if mapaddress fails,
8022 rather than not sending anything back at all.
8023 - When we fail to bind or listen on an incoming or outgoing
8024 socket, we should close it before failing. otherwise we just
8025 leak it. (thanks to weasel for finding.)
8026 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
8027 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
8028 - Make NoPublish (even though deprecated) work again.
8029 - Fix a minor security flaw where a versioning auth dirserver
8030 could list a recommended version many times in a row to make
8031 clients more convinced that it's recommended.
8032 - Fix crash bug if there are two unregistered servers running
8033 with the same nickname, one of them is down, and you ask for
8034 them by nickname in your EntryNodes or ExitNodes. Also, try
8035 to pick the one that's running rather than an arbitrary one.
8036 - Fix an infinite loop we could hit if we go offline for too long.
8037 - Complain when we hit WSAENOBUFS on recv() or write() too.
8038 Perhaps this will help us hunt the bug.
8039 - If you're not a versioning dirserver, don't put the string
8040 "client-versions \nserver-versions \n" in your network-status.
8041 - Lower the minimum required number of file descriptors to 1000,
8042 so we can have some overhead for Valgrind on Linux, where the
8043 default ulimit -n is 1024.
8046 - Add tor.dizum.com as the fifth authoritative directory server.
8047 - Add a new config option FetchUselessDescriptors, off by default,
8048 for when you plan to run "exitlist" on your client and you want
8049 to know about even the non-running descriptors.
8052 Changes in version 0.1.1.17-rc - 2006-03-28
8054 - Clients and servers since 0.1.1.10-alpha have been expiring
8055 connections whenever they are idle for 5 minutes and they *do*
8056 have circuits on them. Oops. With this new version, clients will
8057 discard their previous entry guard choices and avoid choosing
8058 entry guards running these flawed versions.
8059 - Fix memory leak when uncompressing concatenated zlib streams. This
8060 was causing substantial leaks over time on Tor servers.
8061 - The v1 directory was including servers as much as 48 hours old,
8062 because that's how the new routerlist->routers works. Now only
8063 include them if they're 20 hours old or less.
8066 - Resume building on irix64, netbsd 2.0, etc.
8067 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
8069 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
8070 and it is confusing some users.
8071 - Mirrors stop caching the v1 directory so often.
8072 - Make the max number of old descriptors that a cache will hold
8073 rise with the number of directory authorities, so we can scale.
8074 - Change our win32 uname() hack to be more forgiving about what
8075 win32 versions it thinks it's found.
8078 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
8080 - When the controller's *setconf commands fail, collect an error
8081 message in a string and hand it back to the controller.
8082 - Make the v2 dir's "Fast" flag based on relative capacity, just
8083 like "Stable" is based on median uptime. Name everything in the
8084 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
8085 - Log server fingerprint on startup, so new server operators don't
8086 have to go hunting around their filesystem for it.
8087 - Return a robots.txt on our dirport to discourage google indexing.
8088 - Let the controller ask for GETINFO dir/status/foo so it can ask
8089 directly rather than connecting to the dir port. Only works when
8090 dirport is set for now.
8092 o New config options rather than constants in the code:
8093 - SocksTimeout: How long do we let a socks connection wait
8094 unattached before we fail it?
8095 - CircuitBuildTimeout: Cull non-open circuits that were born
8096 at least this many seconds ago.
8097 - CircuitIdleTimeout: Cull open clean circuits that were born
8098 at least this many seconds ago.
8101 Changes in version 0.1.1.16-rc - 2006-03-18
8102 o Bugfixes on 0.1.1.15-rc:
8103 - Fix assert when the controller asks to attachstream a connect-wait
8104 or resolve-wait stream.
8105 - Now do address rewriting when the controller asks us to attach
8106 to a particular circuit too. This will let Blossom specify
8107 "moria2.exit" without having to learn what moria2's IP address is.
8108 - Make the "tor --verify-config" command-line work again, so people
8109 can automatically check if their torrc will parse.
8110 - Authoritative dirservers no longer require an open connection from
8111 a server to consider him "reachable". We need this change because
8112 when we add new auth dirservers, old servers won't know not to
8114 - Let Tor build on Sun CC again.
8115 - Fix an off-by-one buffer size in dirserv.c that magically never
8116 hit our three authorities but broke sjmurdoch's own tor network.
8117 - If we as a directory mirror don't know of any v1 directory
8118 authorities, then don't try to cache any v1 directories.
8119 - Stop warning about unknown servers in our family when they are
8120 given as hex digests.
8121 - Stop complaining as quickly to the server operator that he
8122 hasn't registered his nickname/key binding.
8123 - Various cleanups so we can add new V2 Auth Dirservers.
8124 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
8125 reflect the updated flags in our v2 dir protocol.
8126 - Resume allowing non-printable characters for exit streams (both
8127 for connecting and for resolving). Now we tolerate applications
8128 that don't follow the RFCs. But continue to block malformed names
8131 o Bugfixes on 0.1.0.x:
8132 - Fix assert bug in close_logs(): when we close and delete logs,
8133 remove them all from the global "logfiles" list.
8134 - Fix minor integer overflow in calculating when we expect to use up
8135 our bandwidth allocation before hibernating.
8136 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
8137 there are multiple SSLs installed with different versions.
8138 - When we try to be a server and Address is not explicitly set and
8139 our hostname resolves to a private IP address, try to use an
8140 interface address if it has a public address. Now Windows machines
8141 that think of themselves as localhost can work by default.
8144 - Let the controller ask for GETINFO dir/server/foo so it can ask
8145 directly rather than connecting to the dir port.
8146 - Let the controller tell us about certain router descriptors
8147 that it doesn't want Tor to use in circuits. Implement
8148 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
8149 - New config option SafeSocks to reject all application connections
8150 using unsafe socks protocols. Defaults to off.
8153 Changes in version 0.1.1.15-rc - 2006-03-11
8154 o Bugfixes and cleanups:
8155 - When we're printing strings from the network, don't try to print
8156 non-printable characters. This protects us against shell escape
8157 sequence exploits, and also against attacks to fool humans into
8158 misreading their logs.
8159 - Fix a bug where Tor would fail to establish any connections if you
8160 left it off for 24 hours and then started it: we were happy with
8161 the obsolete network statuses, but they all referred to router
8162 descriptors that were too old to fetch, so we ended up with no
8163 valid router descriptors.
8164 - Fix a seg fault in the controller's "getinfo orconn-status"
8165 command while listing status on incoming handshaking connections.
8166 Introduce a status name "NEW" for these connections.
8167 - If we get a linelist or linelist_s config option from the torrc
8168 (e.g. ExitPolicy) and it has no value, warn and skip rather than
8169 silently resetting it to its default.
8170 - Don't abandon entry guards until they've been down or gone for
8172 - Cleaner and quieter log messages.
8175 - New controller signal NEWNYM that makes new application requests
8177 - Add a new circuit purpose 'controller' to let the controller ask
8178 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
8179 controller command to let you specify the purpose if you're
8180 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
8181 command to let you change a circuit's purpose after it's been
8183 - Accept "private:*" in routerdesc exit policies; not generated yet
8184 because older Tors do not understand it.
8185 - Add BSD-style contributed startup script "rc.subr" from Peter
8189 Changes in version 0.1.1.14-alpha - 2006-02-20
8190 o Bugfixes on 0.1.1.x:
8191 - Don't die if we ask for a stdout or stderr log (even implicitly)
8192 and we're set to RunAsDaemon -- just warn.
8193 - We still had a few bugs in the OR connection rotation code that
8194 caused directory servers to slowly aggregate connections to other
8195 fast Tor servers. This time for sure!
8196 - Make log entries on Win32 include the name of the function again.
8197 - We were treating a pair of exit policies if they were equal even
8198 if one said accept and the other said reject -- causing us to
8199 not always publish a new descriptor since we thought nothing
8201 - Retry pending server downloads as well as pending networkstatus
8202 downloads when we unexpectedly get a socks request.
8203 - We were ignoring the IS_FAST flag in the directory status,
8204 meaning we were willing to pick trivial-bandwidth nodes for "fast"
8206 - If the controller's SAVECONF command fails (e.g. due to file
8207 permissions), let the controller know that it failed.
8210 - If we're trying to be a Tor server and running Windows 95/98/ME
8211 as a server, explain that we'll likely crash.
8212 - When we're a server, a client asks for an old-style directory,
8213 and our write bucket is empty, don't give it to him. This way
8214 small servers can continue to serve the directory *sometimes*,
8215 without getting overloaded.
8216 - Compress exit policies even more -- look for duplicate lines
8218 - Clients now honor the "guard" flag in the router status when
8219 picking entry guards, rather than looking at is_fast or is_stable.
8220 - Retain unrecognized lines in $DATADIR/state file, so that we can
8221 be forward-compatible.
8222 - Generate 18.0.0.0/8 address policy format in descs when we can;
8223 warn when the mask is not reducible to a bit-prefix.
8224 - Let the user set ControlListenAddress in the torrc. This can be
8225 dangerous, but there are some cases (like a secured LAN) where it
8227 - Split ReachableAddresses into ReachableDirAddresses and
8228 ReachableORAddresses, so we can restrict Dir conns to port 80
8229 and OR conns to port 443.
8230 - Now we can target arch and OS in rpm builds (contributed by
8231 Phobos). Also make the resulting dist-rpm filename match the
8233 - New config options to help controllers: FetchServerDescriptors
8234 and FetchHidServDescriptors for whether to fetch server
8235 info and hidserv info or let the controller do it, and
8236 PublishServerDescriptor and PublishHidServDescriptors.
8237 - Also let the controller set the __AllDirActionsPrivate config
8238 option if you want all directory fetches/publishes to happen via
8239 Tor (it assumes your controller bootstraps your circuits).
8242 Changes in version 0.1.0.17 - 2006-02-17
8243 o Crash bugfixes on 0.1.0.x:
8244 - When servers with a non-zero DirPort came out of hibernation,
8245 sometimes they would trigger an assert.
8247 o Other important bugfixes:
8248 - On platforms that don't have getrlimit (like Windows), we were
8249 artificially constraining ourselves to a max of 1024
8250 connections. Now just assume that we can handle as many as 15000
8251 connections. Hopefully this won't cause other problems.
8253 o Backported features:
8254 - When we're a server, a client asks for an old-style directory,
8255 and our write bucket is empty, don't give it to him. This way
8256 small servers can continue to serve the directory *sometimes*,
8257 without getting overloaded.
8258 - Whenever you get a 503 in response to a directory fetch, try
8259 once more. This will become important once servers start sending
8260 503's whenever they feel busy.
8261 - Fetch a new directory every 120 minutes, not every 40 minutes.
8262 Now that we have hundreds of thousands of users running the old
8263 directory algorithm, it's starting to hurt a lot.
8264 - Bump up the period for forcing a hidden service descriptor upload
8265 from 20 minutes to 1 hour.
8268 Changes in version 0.1.1.13-alpha - 2006-02-09
8269 o Crashes in 0.1.1.x:
8270 - When you tried to setconf ORPort via the controller, Tor would
8271 crash. So people using TorCP to become a server were sad.
8272 - Solve (I hope) the stack-smashing bug that we were seeing on fast
8273 servers. The problem appears to be something do with OpenSSL's
8274 random number generation, or how we call it, or something. Let me
8275 know if the crashes continue.
8276 - Turn crypto hardware acceleration off by default, until we find
8277 somebody smart who can test it for us. (It appears to produce
8278 seg faults in at least some cases.)
8279 - Fix a rare assert error when we've tried all intro points for
8280 a hidden service and we try fetching the service descriptor again:
8281 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
8284 - Fix a major load balance bug: we were round-robining in 16 KB
8285 chunks, and servers with bandwidthrate of 20 KB, while downloading
8286 a 600 KB directory, would starve their other connections. Now we
8287 try to be a bit more fair.
8288 - Dir authorities and mirrors were never expiring the newest
8289 descriptor for each server, causing memory and directory bloat.
8290 - Fix memory-bloating and connection-bloating bug on servers: We
8291 were never closing any connection that had ever had a circuit on
8292 it, because we were checking conn->n_circuits == 0, yet we had a
8293 bug that let it go negative.
8294 - Make Tor work using squid as your http proxy again -- squid
8295 returns an error if you ask for a URL that's too long, and it uses
8296 a really generic error message. Plus, many people are behind a
8297 transparent squid so they don't even realize it.
8298 - On platforms that don't have getrlimit (like Windows), we were
8299 artificially constraining ourselves to a max of 1024
8300 connections. Now just assume that we can handle as many as 15000
8301 connections. Hopefully this won't cause other problems.
8302 - Add a new config option ExitPolicyRejectPrivate which defaults to
8303 1. This means all exit policies will begin with rejecting private
8304 addresses, unless the server operator explicitly turns it off.
8307 - Clients no longer download descriptors for non-running
8309 - Before we add new directory authorities, we should make it
8310 clear that only v1 authorities should receive/publish hidden
8311 service descriptors.
8314 - As soon as we've fetched some more directory info, immediately
8315 try to download more server descriptors. This way we don't have
8316 a 10 second pause during initial bootstrapping.
8317 - Remove even more loud log messages that the server operator can't
8319 - When we're running an obsolete or un-recommended version, make
8320 the log message more clear about what the problem is and what
8321 versions *are* still recommended.
8322 - Provide a more useful warn message when our onion queue gets full:
8323 the CPU is too slow or the exit policy is too liberal.
8324 - Don't warn when we receive a 503 from a dirserver/cache -- this
8325 will pave the way for them being able to refuse if they're busy.
8326 - When we fail to bind a listener, try to provide a more useful
8327 log message: e.g., "Is Tor already running?"
8328 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
8329 Goldberg can prove things about our handshake protocol more
8331 - MaxConn has been obsolete for a while now. Document the ConnLimit
8332 config option, which is a *minimum* number of file descriptors
8333 that must be available else Tor refuses to start.
8334 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
8335 if you log to syslog and want something other than LOG_DAEMON.
8336 - Make dirservers generate a separate "guard" flag to mean,
8337 "would make a good entry guard". Make clients parse it and vote
8338 on it. Not used by clients yet.
8339 - Implement --with-libevent-dir option to ./configure. Also, improve
8340 search techniques to find libevent, and use those for openssl too.
8341 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
8342 - Only start testing reachability once we've established a
8343 circuit. This will make startup on dirservers less noisy.
8344 - Don't try to upload hidden service descriptors until we have
8345 established a circuit.
8346 - Fix the controller's "attachstream 0" command to treat conn like
8347 it just connected, doing address remapping, handling .exit and
8348 .onion idioms, and so on. Now we're more uniform in making sure
8349 that the controller hears about new and closing connections.
8352 Changes in version 0.1.1.12-alpha - 2006-01-11
8353 o Bugfixes on 0.1.1.x:
8354 - The fix to close duplicate server connections was closing all
8355 Tor client connections if they didn't establish a circuit
8356 quickly enough. Oops.
8357 - Fix minor memory issue (double-free) that happened on exit.
8359 o Bugfixes on 0.1.0.x:
8360 - Tor didn't warn when it failed to open a log file.
8363 Changes in version 0.1.1.11-alpha - 2006-01-10
8364 o Crashes in 0.1.1.x:
8365 - Include all the assert/crash fixes from 0.1.0.16.
8366 - If you start Tor and then quit very quickly, there were some
8367 races that tried to free things that weren't allocated yet.
8368 - Fix a rare memory stomp if you're running hidden services.
8369 - Fix segfault when specifying DirServer in config without nickname.
8370 - Fix a seg fault when you finish connecting to a server but at
8371 that moment you dump his server descriptor.
8372 - Extendcircuit and Attachstream controller commands would
8373 assert/crash if you don't give them enough arguments.
8374 - Fix an assert error when we're out of space in the connection_list
8375 and we try to post a hidden service descriptor (reported by weasel).
8376 - If you specify a relative torrc path and you set RunAsDaemon in
8377 your torrc, then it chdir()'s to the new directory. If you HUP,
8378 it tries to load the new torrc location, fails, and exits.
8379 The fix: no longer allow a relative path to torrc using -f.
8382 - Implement "entry guards": automatically choose a handful of entry
8383 nodes and stick with them for all circuits. Only pick new guards
8384 when the ones you have are unsuitable, and if the old guards
8385 become suitable again, switch back. This will increase security
8386 dramatically against certain end-point attacks. The EntryNodes
8387 config option now provides some hints about which entry guards you
8388 want to use most; and StrictEntryNodes means to only use those.
8389 - New directory logic: download by descriptor digest, not by
8390 fingerprint. Caches try to download all listed digests from
8391 authorities; clients try to download "best" digests from caches.
8392 This avoids partitioning and isolating attacks better.
8393 - Make the "stable" router flag in network-status be the median of
8394 the uptimes of running valid servers, and make clients pay
8395 attention to the network-status flags. Thus the cutoff adapts
8396 to the stability of the network as a whole, making IRC, IM, etc
8397 connections more reliable.
8400 - Tor servers with dynamic IP addresses were needing to wait 18
8401 hours before they could start doing reachability testing using
8402 the new IP address and ports. This is because they were using
8403 the internal descriptor to learn what to test, yet they were only
8404 rebuilding the descriptor once they decided they were reachable.
8405 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
8406 to download certain server descriptors, throw them away, and then
8407 fetch them again after 30 minutes. Now mirrors throw away these
8408 server descriptors so clients can't get them.
8409 - We were leaving duplicate connections to other ORs open for a week,
8410 rather than closing them once we detect a duplicate. This only
8411 really affected authdirservers, but it affected them a lot.
8412 - Spread the authdirservers' reachability testing over the entire
8413 testing interval, so we don't try to do 500 TLS's at once every
8417 - If the network is down, and we try to connect to a conn because
8418 we have a circuit in mind, and we timeout (30 seconds) because the
8419 network never answers, we were expiring the circuit, but we weren't
8420 obsoleting the connection or telling the entry_guards functions.
8421 - Some Tor servers process billions of cells per day. These statistics
8422 need to be uint64_t's.
8423 - Check for integer overflows in more places, when adding elements
8424 to smartlists. This could possibly prevent a buffer overflow
8425 on malicious huge inputs. I don't see any, but I haven't looked
8427 - ReachableAddresses kept growing new "reject *:*" lines on every
8429 - When you "setconf log" via the controller, it should remove all
8430 logs. We were automatically adding back in a "log notice stdout".
8431 - Newly bootstrapped Tor networks couldn't establish hidden service
8432 circuits until they had nodes with high uptime. Be more tolerant.
8433 - We were marking servers down when they could not answer every piece
8434 of the directory request we sent them. This was far too harsh.
8435 - Fix the torify (tsocks) config file to not use Tor for localhost
8437 - Directory authorities now go to the proper authority when asking for
8438 a networkstatus, even when they want a compressed one.
8439 - Fix a harmless bug that was causing Tor servers to log
8440 "Got an end because of misc error, but we're not an AP. Closing."
8441 - Authorities were treating their own descriptor changes as cosmetic,
8442 meaning the descriptor available in the network-status and the
8443 descriptor that clients downloaded were different.
8444 - The OS X installer was adding a symlink for tor_resolve but
8445 the binary was called tor-resolve (reported by Thomas Hardly).
8446 - Workaround a problem with some http proxies where they refuse GET
8447 requests that specify "Content-Length: 0" (reported by Adrian).
8448 - Fix wrong log message when you add a "HiddenServiceNodes" config
8449 line without any HiddenServiceDir line (reported by Chris Thomas).
8452 - Write the TorVersion into the state file so we have a prayer of
8453 keeping forward and backward compatibility.
8454 - Revive the FascistFirewall config option rather than eliminating it:
8455 now it's a synonym for ReachableAddresses *:80,*:443.
8456 - Clients choose directory servers from the network status lists,
8457 not from their internal list of router descriptors. Now they can
8458 go to caches directly rather than needing to go to authorities
8460 - Directory authorities ignore router descriptors that have only
8461 cosmetic differences: do this for 0.1.0.x servers now too.
8462 - Add a new flag to network-status indicating whether the server
8463 can answer v2 directory requests too.
8464 - Authdirs now stop whining so loudly about bad descriptors that
8465 they fetch from other dirservers. So when there's a log complaint,
8466 it's for sure from a freshly uploaded descriptor.
8467 - Reduce memory requirements in our structs by changing the order
8469 - There used to be two ways to specify your listening ports in a
8470 server descriptor: on the "router" line and with a separate "ports"
8471 line. Remove support for the "ports" line.
8472 - New config option "AuthDirRejectUnlisted" for auth dirservers as
8473 a panic button: if we get flooded with unusable servers we can
8474 revert to only listing servers in the approved-routers file.
8475 - Auth dir servers can now mark a fingerprint as "!reject" or
8476 "!invalid" in the approved-routers file (as its nickname), to
8477 refuse descriptors outright or include them but marked as invalid.
8478 - Servers store bandwidth history across restarts/crashes.
8479 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
8480 get a better idea of why their circuits failed. Not used yet.
8481 - Directory mirrors now cache up to 16 unrecognized network-status
8482 docs. Now we can add new authdirservers and they'll be cached too.
8483 - When picking a random directory, prefer non-authorities if any
8485 - New controller option "getinfo desc/all-recent" to fetch the
8486 latest server descriptor for every router that Tor knows about.
8489 Changes in version 0.1.0.16 - 2006-01-02
8490 o Crash bugfixes on 0.1.0.x:
8491 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8492 corrupting the heap, losing FDs, or crashing when we need to resize
8493 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8494 - It turns out sparc64 platforms crash on unaligned memory access
8495 too -- so detect and avoid this.
8496 - Handle truncated compressed data correctly (by detecting it and
8498 - Fix possible-but-unlikely free(NULL) in control.c.
8499 - When we were closing connections, there was a rare case that
8500 stomped on memory, triggering seg faults and asserts.
8501 - Avoid potential infinite recursion when building a descriptor. (We
8502 don't know that it ever happened, but better to fix it anyway.)
8503 - We were neglecting to unlink marked circuits from soon-to-close OR
8504 connections, which caused some rare scribbling on freed memory.
8505 - Fix a memory stomping race bug when closing the joining point of two
8506 rendezvous circuits.
8507 - Fix an assert in time parsing found by Steven Murdoch.
8509 o Other bugfixes on 0.1.0.x:
8510 - When we're doing reachability testing, provide more useful log
8511 messages so the operator knows what to expect.
8512 - Do not check whether DirPort is reachable when we are suppressing
8513 advertising it because of hibernation.
8514 - When building with -static or on Solaris, we sometimes needed -ldl.
8515 - When we're deciding whether a stream has enough circuits around
8516 that can handle it, count the freshly dirty ones and not the ones
8517 that are so dirty they won't be able to handle it.
8518 - When we're expiring old circuits, we had a logic error that caused
8519 us to close new rendezvous circuits rather than old ones.
8520 - Give a more helpful log message when you try to change ORPort via
8521 the controller: you should upgrade Tor if you want that to work.
8522 - We were failing to parse Tor versions that start with "Tor ".
8523 - Tolerate faulty streams better: when a stream fails for reason
8524 exitpolicy, stop assuming that the router is lying about his exit
8525 policy. When a stream fails for reason misc, allow it to retry just
8526 as if it was resolvefailed. When a stream has failed three times,
8527 reset its failure count so we can try again and get all three tries.
8530 Changes in version 0.1.1.10-alpha - 2005-12-11
8531 o Correctness bugfixes on 0.1.0.x:
8532 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8533 corrupting the heap, losing FDs, or crashing when we need to resize
8534 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8535 - Stop doing the complex voodoo overkill checking for insecure
8536 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
8537 - When we were closing connections, there was a rare case that
8538 stomped on memory, triggering seg faults and asserts.
8539 - We were neglecting to unlink marked circuits from soon-to-close OR
8540 connections, which caused some rare scribbling on freed memory.
8541 - When we're deciding whether a stream has enough circuits around
8542 that can handle it, count the freshly dirty ones and not the ones
8543 that are so dirty they won't be able to handle it.
8544 - Recover better from TCP connections to Tor servers that are
8545 broken but don't tell you (it happens!); and rotate TLS
8546 connections once a week.
8547 - When we're expiring old circuits, we had a logic error that caused
8548 us to close new rendezvous circuits rather than old ones.
8549 - Fix a scary-looking but apparently harmless bug where circuits
8550 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
8551 servers, and never switch to state CIRCUIT_STATE_OPEN.
8552 - When building with -static or on Solaris, we sometimes needed to
8554 - Give a useful message when people run Tor as the wrong user,
8555 rather than telling them to start chowning random directories.
8556 - We were failing to inform the controller about new .onion streams.
8558 o Security bugfixes on 0.1.0.x:
8559 - Refuse server descriptors if the fingerprint line doesn't match
8560 the included identity key. Tor doesn't care, but other apps (and
8561 humans) might actually be trusting the fingerprint line.
8562 - We used to kill the circuit when we receive a relay command we
8563 don't recognize. Now we just drop it.
8564 - Start obeying our firewall options more rigorously:
8565 . If we can't get to a dirserver directly, try going via Tor.
8566 . Don't ever try to connect (as a client) to a place our
8567 firewall options forbid.
8568 . If we specify a proxy and also firewall options, obey the
8569 firewall options even when we're using the proxy: some proxies
8570 can only proxy to certain destinations.
8571 - Fix a bug found by Lasse Overlier: when we were making internal
8572 circuits (intended to be cannibalized later for rendezvous and
8573 introduction circuits), we were picking them so that they had
8574 useful exit nodes. There was no need for this, and it actually
8575 aids some statistical attacks.
8576 - Start treating internal circuits and exit circuits separately.
8577 It's important to keep them separate because internal circuits
8578 have their last hops picked like middle hops, rather than like
8579 exit hops. So exiting on them will break the user's expectations.
8581 o Bugfixes on 0.1.1.x:
8582 - Take out the mis-feature where we tried to detect IP address
8583 flapping for people with DynDNS, and chose not to upload a new
8584 server descriptor sometimes.
8585 - Try to be compatible with OpenSSL 0.9.6 again.
8586 - Log fix: when the controller is logging about .onion addresses,
8587 sometimes it didn't include the ".onion" part of the address.
8588 - Don't try to modify options->DirServers internally -- if the
8589 user didn't specify any, just add the default ones directly to
8590 the trusted dirserver list. This fixes a bug where people running
8591 controllers would use SETCONF on some totally unrelated config
8592 option, and Tor would start yelling at them about changing their
8594 - Let the controller's redirectstream command specify a port, in
8595 case the controller wants to change that too.
8596 - When we requested a pile of server descriptors, we sometimes
8597 accidentally launched a duplicate request for the first one.
8598 - Bugfix for trackhostexits: write down the fingerprint of the
8599 chosen exit, not its nickname, because the chosen exit might not
8601 - When parsing foo.exit, if foo is unknown, and we are leaving
8602 circuits unattached, set the chosen_exit field and leave the
8603 address empty. This matters because controllers got confused
8605 - Directory authorities no longer try to download server
8606 descriptors that they know they will reject.
8608 o Features and updates:
8609 - Replace balanced trees with hash tables: this should make stuff
8610 significantly faster.
8611 - Resume using the AES counter-mode implementation that we ship,
8612 rather than OpenSSL's. Ours is significantly faster.
8613 - Many other CPU and memory improvements.
8614 - Add a new config option FastFirstHopPK (on by default) so clients
8615 do a trivial crypto handshake for their first hop, since TLS has
8616 already taken care of confidentiality and authentication.
8617 - Add a new config option TestSocks so people can see if their
8618 applications are using socks4, socks4a, socks5-with-ip, or
8619 socks5-with-hostname. This way they don't have to keep mucking
8620 with tcpdump and wondering if something got cached somewhere.
8621 - Warn when listening on a public address for socks. I suspect a
8622 lot of people are setting themselves up as open socks proxies,
8623 and they have no idea that jerks on the Internet are using them,
8624 since they simply proxy the traffic into the Tor network.
8625 - Add "private:*" as an alias in configuration for policies. Now
8626 you can simplify your exit policy rather than needing to list
8627 every single internal or nonroutable network space.
8628 - Add a new controller event type that allows controllers to get
8629 all server descriptors that were uploaded to a router in its role
8630 as authoritative dirserver.
8631 - Start shipping socks-extensions.txt, tor-doc-unix.html,
8632 tor-doc-server.html, and stylesheet.css in the tarball.
8633 - Stop shipping tor-doc.html in the tarball.
8636 Changes in version 0.1.1.9-alpha - 2005-11-15
8637 o Usability improvements:
8638 - Start calling it FooListenAddress rather than FooBindAddress,
8639 since few of our users know what it means to bind an address
8641 - Reduce clutter in server logs. We're going to try to make
8642 them actually usable now. New config option ProtocolWarnings that
8643 lets you hear about how _other Tors_ are breaking the protocol. Off
8645 - Divide log messages into logging domains. Once we put some sort
8646 of interface on this, it will let people looking at more verbose
8647 log levels specify the topics they want to hear more about.
8648 - Make directory servers return better http 404 error messages
8649 instead of a generic "Servers unavailable".
8650 - Check for even more Windows version flags when writing the platform
8651 string in server descriptors, and note any we don't recognize.
8652 - Clean up more of the OpenSSL memory when exiting, so we can detect
8653 memory leaks better.
8654 - Make directory authorities be non-versioning, non-naming by
8655 default. Now we can add new directory servers without requiring
8656 their operators to pay close attention.
8657 - When logging via syslog, include the pid whenever we provide
8658 a log entry. Suggested by Todd Fries.
8660 o Performance improvements:
8661 - Directory servers now silently throw away new descriptors that
8662 haven't changed much if the timestamps are similar. We do this to
8663 tolerate older Tor servers that upload a new descriptor every 15
8664 minutes. (It seemed like a good idea at the time.)
8665 - Inline bottleneck smartlist functions; use fast versions by default.
8666 - Add a "Map from digest to void*" abstraction digestmap_t so we
8667 can do less hex encoding/decoding. Use it in router_get_by_digest()
8668 to resolve a performance bottleneck.
8669 - Allow tor_gzip_uncompress to extract as much as possible from
8670 truncated compressed data. Try to extract as many
8671 descriptors as possible from truncated http responses (when
8672 DIR_PURPOSE_FETCH_ROUTERDESC).
8673 - Make circ->onionskin a pointer, not a static array. moria2 was using
8674 125000 circuit_t's after it had been up for a few weeks, which
8675 translates to 20+ megs of wasted space.
8676 - The private half of our EDH handshake keys are now chosen out
8677 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
8679 o Security improvements:
8680 - Start making directory caches retain old routerinfos, so soon
8681 clients can start asking by digest of descriptor rather than by
8682 fingerprint of server.
8683 - Add half our entropy from RAND_poll in OpenSSL. This knows how
8684 to use egd (if present), openbsd weirdness (if present), vms/os2
8685 weirdness (if we ever port there), and more in the future.
8687 o Bugfixes on 0.1.0.x:
8688 - Do round-robin writes of at most 16 kB per write. This might be
8689 more fair on loaded Tor servers, and it might resolve our Windows
8690 crash bug. It might also slow things down.
8691 - Our TLS handshakes were generating a single public/private
8692 keypair for the TLS context, rather than making a new one for
8693 each new connections. Oops. (But we were still rotating them
8694 periodically, so it's not so bad.)
8695 - When we were cannibalizing a circuit with a particular exit
8696 node in mind, we weren't checking to see if that exit node was
8697 already present earlier in the circuit. Oops.
8698 - When a Tor server's IP changes (e.g. from a dyndns address),
8699 upload a new descriptor so clients will learn too.
8700 - Really busy servers were keeping enough circuits open on stable
8701 connections that they were wrapping around the circuit_id
8702 space. (It's only two bytes.) This exposed a bug where we would
8703 feel free to reuse a circuit_id even if it still exists but has
8704 been marked for close. Try to fix this bug. Some bug remains.
8705 - If we would close a stream early (e.g. it asks for a .exit that
8706 we know would refuse it) but the LeaveStreamsUnattached config
8707 option is set by the controller, then don't close it.
8709 o Bugfixes on 0.1.1.8-alpha:
8710 - Fix a big pile of memory leaks, some of them serious.
8711 - Do not try to download a routerdesc if we would immediately reject
8713 - Resume inserting a newline between all router descriptors when
8714 generating (old style) signed directories, since our spec says
8716 - When providing content-type application/octet-stream for
8717 server descriptors using .z, we were leaving out the
8718 content-encoding header. Oops. (Everything tolerated this just
8719 fine, but that doesn't mean we need to be part of the problem.)
8720 - Fix a potential seg fault in getconf and getinfo using version 1
8721 of the controller protocol.
8722 - Avoid crash: do not check whether DirPort is reachable when we
8723 are suppressing it because of hibernation.
8724 - Make --hash-password not crash on exit.
8727 Changes in version 0.1.1.8-alpha - 2005-10-07
8728 o New features (major):
8729 - Clients don't download or use the directory anymore. Now they
8730 download and use network-statuses from the trusted dirservers,
8731 and fetch individual server descriptors as needed from mirrors.
8732 See dir-spec.txt for all the gory details.
8733 - Be more conservative about whether to advertise our DirPort.
8734 The main change is to not advertise if we're running at capacity
8735 and either a) we could hibernate or b) our capacity is low and
8736 we're using a default DirPort.
8737 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
8739 o New features (minor):
8740 - Try to be smart about when to retry network-status and
8741 server-descriptor fetches. Still needs some tuning.
8742 - Stop parsing, storing, or using running-routers output (but
8743 mirrors still cache and serve it).
8744 - Consider a threshold of versioning dirservers (dirservers who have
8745 an opinion about which Tor versions are still recommended) before
8746 deciding whether to warn the user that he's obsolete.
8747 - Dirservers can now reject/invalidate by key and IP, with the
8748 config options "AuthDirInvalid" and "AuthDirReject". This is
8749 useful since currently we automatically list servers as running
8750 and usable even if we know they're jerks.
8751 - Provide dire warnings to any users who set DirServer; move it out
8752 of torrc.sample and into torrc.complete.
8753 - Add MyFamily to torrc.sample in the server section.
8754 - Add nicknames to the DirServer line, so we can refer to them
8755 without requiring all our users to memorize their IP addresses.
8756 - When we get an EOF or a timeout on a directory connection, note
8757 how many bytes of serverdesc we are dropping. This will help
8758 us determine whether it is smart to parse incomplete serverdesc
8760 - Add a new function to "change pseudonyms" -- that is, to stop
8761 using any currently-dirty circuits for new streams, so we don't
8762 link new actions to old actions. Currently it's only called on
8763 HUP (or SIGNAL RELOAD).
8764 - On sighup, if UseHelperNodes changed to 1, use new circuits.
8765 - Start using RAND_bytes rather than RAND_pseudo_bytes from
8766 OpenSSL. Also, reseed our entropy every hour, not just at
8767 startup. And entropy in 512-bit chunks, not 160-bit chunks.
8769 o Fixes on 0.1.1.7-alpha:
8770 - Nobody ever implemented EVENT_ADDRMAP for control protocol
8771 version 0, so don't let version 0 controllers ask for it.
8772 - If you requested something with too many newlines via the
8773 v1 controller protocol, you could crash tor.
8774 - Fix a number of memory leaks, including some pretty serious ones.
8775 - Re-enable DirPort testing again, so Tor servers will be willing
8776 to advertise their DirPort if it's reachable.
8777 - On TLS handshake, only check the other router's nickname against
8778 its expected nickname if is_named is set.
8780 o Fixes forward-ported from 0.1.0.15:
8781 - Don't crash when we don't have any spare file descriptors and we
8782 try to spawn a dns or cpu worker.
8783 - Make the numbers in read-history and write-history into uint64s,
8784 so they don't overflow and publish negatives in the descriptor.
8787 - For the OS X package's modified privoxy config file, comment
8788 out the "logfile" line so we don't log everything passed
8790 - We were whining about using socks4 or socks5-with-local-lookup
8791 even when it's an IP in the "virtual" range we designed exactly
8793 - We were leaking some memory every time the client changes IPs.
8794 - Never call free() on tor_malloc()d memory. This will help us
8795 use dmalloc to detect memory leaks.
8796 - Check for named servers when looking them up by nickname;
8797 warn when we'recalling a non-named server by its nickname;
8798 don't warn twice about the same name.
8799 - Try to list MyFamily elements by key, not by nickname, and warn
8800 if we've not heard of the server.
8801 - Make windows platform detection (uname equivalent) smarter.
8802 - It turns out sparc64 doesn't like unaligned access either.
8805 Changes in version 0.1.0.15 - 2005-09-23
8806 o Bugfixes on 0.1.0.x:
8807 - Reject ports 465 and 587 (spam targets) in default exit policy.
8808 - Don't crash when we don't have any spare file descriptors and we
8809 try to spawn a dns or cpu worker.
8810 - Get rid of IgnoreVersion undocumented config option, and make us
8811 only warn, never exit, when we're running an obsolete version.
8812 - Don't try to print a null string when your server finds itself to
8813 be unreachable and the Address config option is empty.
8814 - Make the numbers in read-history and write-history into uint64s,
8815 so they don't overflow and publish negatives in the descriptor.
8816 - Fix a minor memory leak in smartlist_string_remove().
8817 - We were only allowing ourselves to upload a server descriptor at
8818 most every 20 minutes, even if it changed earlier than that.
8819 - Clean up log entries that pointed to old URLs.
8822 Changes in version 0.1.1.7-alpha - 2005-09-14
8823 o Fixes on 0.1.1.6-alpha:
8824 - Exit servers were crashing when people asked them to make a
8825 connection to an address not in their exit policy.
8826 - Looking up a non-existent stream for a v1 control connection would
8828 - Fix a seg fault if we ask a dirserver for a descriptor by
8829 fingerprint but he doesn't know about him.
8830 - SETCONF was appending items to linelists, not clearing them.
8831 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
8832 out and refuse the setconf if it would fail.
8833 - Downgrade the dirserver log messages when whining about
8837 - Add Peter Palfrader's check-tor script to tor/contrib/
8838 It lets you easily check whether a given server (referenced by
8839 nickname) is reachable by you.
8840 - Numerous changes to move towards client-side v2 directories. Not
8844 - If the user gave tor an odd number of command-line arguments,
8845 we were silently ignoring the last one. Now we complain and fail.
8846 [This wins the oldest-bug prize -- this bug has been present since
8847 November 2002, as released in Tor 0.0.0.]
8848 - Do not use unaligned memory access on alpha, mips, or mipsel.
8849 It *works*, but is very slow, so we treat them as if it doesn't.
8850 - Retry directory requests if we fail to get an answer we like
8851 from a given dirserver (we were retrying before, but only if
8852 we fail to connect).
8853 - When writing the RecommendedVersions line, sort them first.
8854 - When the client asked for a rendezvous port that the hidden
8855 service didn't want to provide, we were sending an IP address
8856 back along with the end cell. Fortunately, it was zero. But stop
8858 - Correct "your server is reachable" log entries to indicate that
8859 it was self-testing that told us so.
8862 Changes in version 0.1.1.6-alpha - 2005-09-09
8863 o Fixes on 0.1.1.5-alpha:
8864 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
8865 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
8866 - Fix bug with tor_memmem finding a match at the end of the string.
8867 - Make unit tests run without segfaulting.
8868 - Resolve some solaris x86 compile warnings.
8869 - Handle duplicate lines in approved-routers files without warning.
8870 - Fix bug where as soon as a server refused any requests due to his
8871 exit policy (e.g. when we ask for localhost and he tells us that's
8872 127.0.0.1 and he won't do it), we decided he wasn't obeying his
8873 exit policy using him for any exits.
8874 - Only do openssl hardware accelerator stuff if openssl version is
8877 o New controller features/fixes:
8878 - Add a "RESETCONF" command so you can set config options like
8879 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
8880 a config option in the torrc with no value, then it clears it
8881 entirely (rather than setting it to its default).
8882 - Add a "GETINFO config-file" to tell us where torrc is.
8883 - Avoid sending blank lines when GETINFO replies should be empty.
8884 - Add a QUIT command for the controller (for using it manually).
8885 - Fix a bug in SAVECONF that was adding default dirservers and
8886 other redundant entries to the torrc file.
8888 o Start on the new directory design:
8889 - Generate, publish, cache, serve new network-status format.
8890 - Publish individual descriptors (by fingerprint, by "all", and by
8892 - Publish client and server recommended versions separately.
8893 - Allow tor_gzip_uncompress() to handle multiple concatenated
8894 compressed strings. Serve compressed groups of router
8895 descriptors. The compression logic here could be more
8897 - Distinguish v1 authorities (all currently trusted directories)
8898 from v2 authorities (all trusted directories).
8899 - Change DirServers config line to note which dirs are v1 authorities.
8900 - Add configuration option "V1AuthoritativeDirectory 1" which
8901 moria1, moria2, and tor26 should set.
8902 - Remove option when getting directory cache to see whether they
8903 support running-routers; they all do now. Replace it with one
8904 to see whether caches support v2 stuff.
8907 - Dirservers now do their own external reachability testing of each
8908 Tor server, and only list them as running if they've been found to
8909 be reachable. We also send back warnings to the server's logs if
8910 it uploads a descriptor that we already believe is unreachable.
8911 - Implement exit enclaves: if we know an IP address for the
8912 destination, and there's a running Tor server at that address
8913 which allows exit to the destination, then extend the circuit to
8914 that exit first. This provides end-to-end encryption and end-to-end
8915 authentication. Also, if the user wants a .exit address or enclave,
8916 use 4 hops rather than 3, and cannibalize a general circ for it
8918 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
8919 controller. Also, rotate dns and cpu workers if the controller
8920 changes options that will affect them; and initialize the dns
8921 worker cache tree whether or not we start out as a server.
8922 - Only upload a new server descriptor when options change, 18
8923 hours have passed, uptime is reset, or bandwidth changes a lot.
8924 - Check [X-]Forwarded-For headers in HTTP requests when generating
8925 log messages. This lets people run dirservers (and caches) behind
8926 Apache but still know which IP addresses are causing warnings.
8928 o Config option changes:
8929 - Replace (Fascist)Firewall* config options with a new
8930 ReachableAddresses option that understands address policies.
8931 For example, "ReachableAddresses *:80,*:443"
8932 - Get rid of IgnoreVersion undocumented config option, and make us
8933 only warn, never exit, when we're running an obsolete version.
8934 - Make MonthlyAccountingStart config option truly obsolete now.
8937 - Reject ports 465 and 587 in the default exit policy, since
8938 people have started using them for spam too.
8939 - It turns out we couldn't bootstrap a network since we added
8940 reachability detection in 0.1.0.1-rc. Good thing the Tor network
8941 has never gone down. Add an AssumeReachable config option to let
8942 servers and dirservers bootstrap. When we're trying to build a
8943 high-uptime or high-bandwidth circuit but there aren't enough
8944 suitable servers, try being less picky rather than simply failing.
8945 - Our logic to decide if the OR we connected to was the right guy
8946 was brittle and maybe open to a mitm for unverified routers.
8947 - We weren't cannibalizing circuits correctly for
8948 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
8949 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
8950 build those from scratch. This should make hidden services faster.
8951 - Predict required circuits better, with an eye toward making hidden
8952 services faster on the service end.
8953 - Retry streams if the exit node sends back a 'misc' failure. This
8954 should result in fewer random failures. Also, after failing
8955 from resolve failed or misc, reset the num failures, so we give
8956 it a fair shake next time we try.
8957 - Clean up the rendezvous warn log msgs, and downgrade some to info.
8958 - Reduce severity on logs about dns worker spawning and culling.
8959 - When we're shutting down and we do something like try to post a
8960 server descriptor or rendezvous descriptor, don't complain that
8961 we seem to be unreachable. Of course we are, we're shutting down.
8962 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
8963 We don't use them yet, but maybe one day our DNS resolver will be
8964 able to discover them.
8965 - Make ContactInfo mandatory for authoritative directory servers.
8966 - Require server descriptors to list IPv4 addresses -- hostnames
8967 are no longer allowed. This also fixes some potential security
8968 problems with people providing hostnames as their address and then
8969 preferentially resolving them to partition users.
8970 - Change log line for unreachability to explicitly suggest /etc/hosts
8971 as the culprit. Also make it clearer what IP address and ports we're
8972 testing for reachability.
8973 - Put quotes around user-supplied strings when logging so users are
8974 more likely to realize if they add bad characters (like quotes)
8976 - Let auth dir servers start without specifying an Address config
8978 - Make unit tests (and other invocations that aren't the real Tor)
8979 run without launching listeners, creating subdirectories, and so on.
8982 Changes in version 0.1.1.5-alpha - 2005-08-08
8983 o Bugfixes included in 0.1.0.14.
8985 o Bugfixes on 0.1.0.x:
8986 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
8987 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
8988 it would silently using ignore the 6668.
8991 Changes in version 0.1.0.14 - 2005-08-08
8992 o Bugfixes on 0.1.0.x:
8993 - Fix the other half of the bug with crypto handshakes
8995 - Fix an assert trigger if you send a 'signal term' via the
8996 controller when it's listening for 'event info' messages.
8999 Changes in version 0.1.1.4-alpha - 2005-08-04
9000 o Bugfixes included in 0.1.0.13.
9003 - Improve tor_gettimeofday() granularity on windows.
9004 - Make clients regenerate their keys when their IP address changes.
9005 - Implement some more GETINFO goodness: expose helper nodes, config
9006 options, getinfo keys.
9009 Changes in version 0.1.0.13 - 2005-08-04
9010 o Bugfixes on 0.1.0.x:
9011 - Fix a critical bug in the security of our crypto handshakes.
9012 - Fix a size_t underflow in smartlist_join_strings2() that made
9013 it do bad things when you hand it an empty smartlist.
9014 - Fix Windows installer to ship Tor license (thanks to Aphex for
9015 pointing out this oversight) and put a link to the doc directory
9017 - Explicitly set no-unaligned-access for sparc: it turns out the
9018 new gcc's let you compile broken code, but that doesn't make it
9022 Changes in version 0.1.1.3-alpha - 2005-07-23
9023 o Bugfixes on 0.1.1.2-alpha:
9024 - Fix a bug in handling the controller's "post descriptor"
9026 - Fix several bugs in handling the controller's "extend circuit"
9028 - Fix a bug in handling the controller's "stream status" event.
9029 - Fix an assert failure if we have a controller listening for
9030 circuit events and we go offline.
9031 - Re-allow hidden service descriptors to publish 0 intro points.
9032 - Fix a crash when generating your hidden service descriptor if
9033 you don't have enough intro points already.
9035 o New features on 0.1.1.2-alpha:
9036 - New controller function "getinfo accounting", to ask how
9037 many bytes we've used in this time period.
9038 - Experimental support for helper nodes: a lot of the risk from
9039 a small static adversary comes because users pick new random
9040 nodes every time they rebuild a circuit. Now users will try to
9041 stick to the same small set of entry nodes if they can. Not
9042 enabled by default yet.
9044 o Bugfixes on 0.1.0.12:
9045 - If you're an auth dir server, always publish your dirport,
9046 even if you haven't yet found yourself to be reachable.
9047 - Fix a size_t underflow in smartlist_join_strings2() that made
9048 it do bad things when you hand it an empty smartlist.
9051 Changes in version 0.1.0.12 - 2005-07-18
9052 o New directory servers:
9053 - tor26 has changed IP address.
9055 o Bugfixes on 0.1.0.x:
9056 - Fix a possible double-free in tor_gzip_uncompress().
9057 - When --disable-threads is set, do not search for or link against
9059 - Don't trigger an assert if an authoritative directory server
9060 claims its dirport is 0.
9061 - Fix bug with removing Tor as an NT service: some people were
9062 getting "The service did not return an error." Thanks to Matt
9066 Changes in version 0.1.1.2-alpha - 2005-07-15
9067 o New directory servers:
9068 - tor26 has changed IP address.
9070 o Bugfixes on 0.1.0.x, crashes/leaks:
9071 - Port the servers-not-obeying-their-exit-policies fix from
9073 - Fix an fd leak in start_daemon().
9074 - On Windows, you can't always reopen a port right after you've
9075 closed it. So change retry_listeners() to only close and re-open
9076 ports that have changed.
9077 - Fix a possible double-free in tor_gzip_uncompress().
9079 o Bugfixes on 0.1.0.x, usability:
9080 - When tor_socketpair() fails in Windows, give a reasonable
9081 Windows-style errno back.
9082 - Let people type "tor --install" as well as "tor -install" when
9084 want to make it an NT service.
9085 - NT service patch from Matt Edman to improve error messages.
9086 - When the controller asks for a config option with an abbreviated
9087 name, give the full name in our response.
9088 - Correct the man page entry on TrackHostExitsExpire.
9089 - Looks like we were never delivering deflated (i.e. compressed)
9090 running-routers lists, even when asked. Oops.
9091 - When --disable-threads is set, do not search for or link against
9094 o Bugfixes on 0.1.1.x:
9095 - Fix a seg fault with autodetecting which controller version is
9099 - New hidden service descriptor format: put a version in it, and
9100 let people specify introduction/rendezvous points that aren't
9101 in "the directory" (which is subjective anyway).
9102 - Allow the DEBUG controller event to work again. Mark certain log
9103 entries as "don't tell this to controllers", so we avoid cycles.
9106 Changes in version 0.1.0.11 - 2005-06-30
9107 o Bugfixes on 0.1.0.x:
9108 - Fix major security bug: servers were disregarding their
9109 exit policies if clients behaved unexpectedly.
9110 - Make OS X init script check for missing argument, so we don't
9111 confuse users who invoke it incorrectly.
9112 - Fix a seg fault in "tor --hash-password foo".
9113 - The MAPADDRESS control command was broken.
9116 Changes in version 0.1.1.1-alpha - 2005-06-29
9118 - Make OS X init script check for missing argument, so we don't
9119 confuse users who invoke it incorrectly.
9120 - Fix a seg fault in "tor --hash-password foo".
9121 - Fix a possible way to DoS dirservers.
9122 - When we complain that your exit policy implicitly allows local or
9123 private address spaces, name them explicitly so operators can
9125 - Make the log message less scary when all the dirservers are
9126 temporarily unreachable.
9127 - We were printing the number of idle dns workers incorrectly when
9131 - Revised controller protocol (version 1) that uses ascii rather
9132 than binary. Add supporting libraries in python and java so you
9133 can use the controller from your applications without caring how
9135 - Spiffy new support for crypto hardware accelerators. Can somebody
9139 Changes in version 0.0.9.10 - 2005-06-16
9140 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
9141 - Refuse relay cells that claim to have a length larger than the
9142 maximum allowed. This prevents a potential attack that could read
9143 arbitrary memory (e.g. keys) from an exit server's process
9147 Changes in version 0.1.0.10 - 2005-06-14
9148 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
9149 libevent before 1.1a.
9152 Changes in version 0.1.0.9-rc - 2005-06-09
9154 - Reset buf->highwater every time buf_shrink() is called, not just on
9155 a successful shrink. This was causing significant memory bloat.
9156 - Fix buffer overflow when checking hashed passwords.
9157 - Security fix: if seeding the RNG on Win32 fails, quit.
9158 - Allow seeding the RNG on Win32 even when you're not running as
9160 - Disable threading on Solaris too. Something is wonky with it,
9161 cpuworkers, and reentrant libs.
9162 - Reenable the part of the code that tries to flush as soon as an
9163 OR outbuf has a full TLS record available. Perhaps this will make
9164 OR outbufs not grow as huge except in rare cases, thus saving lots
9165 of CPU time plus memory.
9166 - Reject malformed .onion addresses rather then passing them on as
9167 normal web requests.
9168 - Adapt patch from Adam Langley: fix possible memory leak in
9169 tor_lookup_hostname().
9170 - Initialize libevent later in the startup process, so the logs are
9171 already established by the time we start logging libevent warns.
9172 - Use correct errno on win32 if libevent fails.
9173 - Check and warn about known-bad/slow libevent versions.
9174 - Pay more attention to the ClientOnly config option.
9175 - Have torctl.in/tor.sh.in check for location of su binary (needed
9177 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
9178 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
9179 HttpProxyAuthenticator
9180 - Stop warning about sigpipes in the logs. We're going to
9181 pretend that getting these occassionally is normal and fine.
9182 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
9184 installer screens; and don't put stuff into StartupItems unless
9185 the user asks you to.
9186 - Require servers that use the default dirservers to have public IP
9187 addresses. We have too many servers that are configured with private
9188 IPs and their admins never notice the log entries complaining that
9189 their descriptors are being rejected.
9190 - Add OSX uninstall instructions. An actual uninstall script will
9194 Changes in version 0.1.0.8-rc - 2005-05-23
9196 - It turns out that kqueue on OS X 10.3.9 was causing kernel
9197 panics. Disable kqueue on all OS X Tors.
9198 - Fix RPM: remove duplicate line accidentally added to the rpm
9200 - Disable threads on openbsd too, since its gethostaddr is not
9202 - Tolerate libevent 0.8 since it still works, even though it's
9204 - Enable building on Red Hat 9.0 again.
9205 - Allow the middle hop of the testing circuit to be running any
9206 version, now that most of them have the bugfix to let them connect
9207 to unknown servers. This will allow reachability testing to work
9208 even when 0.0.9.7-0.0.9.9 become obsolete.
9209 - Handle relay cells with rh.length too large. This prevents
9210 a potential attack that could read arbitrary memory (maybe even
9211 keys) from the exit server's process.
9212 - We screwed up the dirport reachability testing when we don't yet
9213 have a cached version of the directory. Hopefully now fixed.
9214 - Clean up router_load_single_router() (used by the controller),
9215 so it doesn't seg fault on error.
9216 - Fix a minor memory leak when somebody establishes an introduction
9217 point at your Tor server.
9218 - If a socks connection ends because read fails, don't warn that
9219 you're not sending a socks reply back.
9222 - Add HttpProxyAuthenticator config option too, that works like
9223 the HttpsProxyAuthenticator config option.
9224 - Encode hashed controller passwords in hex instead of base64,
9225 to make it easier to write controllers.
9228 Changes in version 0.1.0.7-rc - 2005-05-17
9230 - Fix a bug in the OS X package installer that prevented it from
9231 installing on Tiger.
9232 - Fix a script bug in the OS X package installer that made it
9233 complain during installation.
9234 - Find libevent even if it's hiding in /usr/local/ and your
9235 CFLAGS and LDFLAGS don't tell you to look there.
9236 - Be able to link with libevent as a shared library (the default
9237 after 1.0d), even if it's hiding in /usr/local/lib and even
9238 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
9239 assuming you're running gcc. Otherwise fail and give a useful
9241 - Fix a bug in the RPM packager: set home directory for _tor to
9242 something more reasonable when first installing.
9243 - Free a minor amount of memory that is still reachable on exit.
9246 Changes in version 0.1.0.6-rc - 2005-05-14
9248 - Implement --disable-threads configure option. Disable threads on
9249 netbsd by default, because it appears to have no reentrant resolver
9251 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
9252 release (1.1) detects and disables kqueue if it's broken.
9253 - Append default exit policy before checking for implicit internal
9254 addresses. Now we don't log a bunch of complaints on startup
9255 when using the default exit policy.
9256 - Some people were putting "Address " in their torrc, and they had
9257 a buggy resolver that resolved " " to 0.0.0.0. Oops.
9258 - If DataDir is ~/.tor, and that expands to /.tor, then default to
9259 LOCALSTATEDIR/tor instead.
9260 - Fix fragmented-message bug in TorControl.py.
9261 - Resolve a minor bug which would prevent unreachable dirports
9262 from getting suppressed in the published descriptor.
9263 - When the controller gave us a new descriptor, we weren't resolving
9264 it immediately, so Tor would think its address was 0.0.0.0 until
9265 we fetched a new directory.
9266 - Fix an uppercase/lowercase case error in suppressing a bogus
9267 libevent warning on some Linuxes.
9270 - Begin scrubbing sensitive strings from logs by default. Turn off
9271 the config option SafeLogging if you need to do debugging.
9272 - Switch to a new buffer management algorithm, which tries to avoid
9273 reallocing and copying quite as much. In first tests it looks like
9274 it uses *more* memory on average, but less cpu.
9275 - First cut at support for "create-fast" cells. Clients can use
9276 these when extending to their first hop, since the TLS already
9277 provides forward secrecy and authentication. Not enabled on
9279 - When dirservers refuse a router descriptor, we now log its
9280 contactinfo, platform, and the poster's IP address.
9281 - Call tor_free_all instead of connections_free_all after forking, to
9282 save memory on systems that need to fork.
9283 - Whine at you if you're a server and you don't set your contactinfo.
9284 - Implement --verify-config command-line option to check if your torrc
9285 is valid without actually launching Tor.
9286 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
9287 rather than just rejecting it.
9290 Changes in version 0.1.0.5-rc - 2005-04-27
9292 - Stop trying to print a null pointer if an OR conn fails because
9293 we didn't like its cert.
9295 - Switch our internal buffers implementation to use a ring buffer,
9296 to hopefully improve performance for fast servers a lot.
9297 - Add HttpsProxyAuthenticator support (basic auth only), based
9298 on patch from Adam Langley.
9299 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
9300 the fast servers that have been joining lately.
9301 - Give hidden service accesses extra time on the first attempt,
9302 since 60 seconds is often only barely enough. This might improve
9304 - Improve performance for dirservers: stop re-parsing the whole
9305 directory every time you regenerate it.
9306 - Add more debugging info to help us find the weird dns freebsd
9307 pthreads bug; cleaner debug messages to help track future issues.
9310 Changes in version 0.0.9.9 - 2005-04-23
9311 o Bugfixes on 0.0.9.x:
9312 - If unofficial Tor clients connect and send weird TLS certs, our
9313 Tor server triggers an assert. This release contains a minimal
9314 backport from the broader fix that we put into 0.1.0.4-rc.
9317 Changes in version 0.1.0.4-rc - 2005-04-23
9319 - If unofficial Tor clients connect and send weird TLS certs, our
9320 Tor server triggers an assert. Stop asserting, and start handling
9321 TLS errors better in other situations too.
9322 - When the controller asks us to tell it about all the debug-level
9323 logs, it turns out we were generating debug-level logs while
9324 telling it about them, which turns into a bad loop. Now keep
9325 track of whether you're sending a debug log to the controller,
9326 and don't log when you are.
9327 - Fix the "postdescriptor" feature of the controller interface: on
9328 non-complete success, only say "done" once.
9330 - Clients are now willing to load balance over up to 2mB, not 1mB,
9331 of advertised bandwidth capacity.
9332 - Add a NoPublish config option, so you can be a server (e.g. for
9333 testing running Tor servers in other Tor networks) without
9334 publishing your descriptor to the primary dirservers.
9337 Changes in version 0.1.0.3-rc - 2005-04-08
9338 o Improvements on 0.1.0.2-rc:
9339 - Client now retries when streams end early for 'hibernating' or
9340 'resource limit' reasons, rather than failing them.
9341 - More automated handling for dirserver operators:
9342 - Automatically approve nodes running 0.1.0.2-rc or later,
9343 now that the the reachability detection stuff is working.
9344 - Now we allow two unverified servers with the same nickname
9345 but different keys. But if a nickname is verified, only that
9346 nickname+key are allowed.
9347 - If you're an authdirserver connecting to an address:port,
9348 and it's not the OR you were expecting, forget about that
9349 descriptor. If he *was* the one you were expecting, then forget
9350 about all other descriptors for that address:port.
9351 - Allow servers to publish descriptors from 12 hours in the future.
9352 Corollary: only whine about clock skew from the dirserver if
9353 he's a trusted dirserver (since now even verified servers could
9354 have quite wrong clocks).
9355 - Adjust maximum skew and age for rendezvous descriptors: let skew
9356 be 48 hours rather than 90 minutes.
9357 - Efficiency improvements:
9358 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
9359 it much faster to look up a circuit for each relay cell.
9360 - Remove most calls to assert_all_pending_dns_resolves_ok(),
9361 since they're eating our cpu on exit nodes.
9362 - Stop wasting time doing a case insensitive comparison for every
9363 dns name every time we do any lookup. Canonicalize the names to
9364 lowercase and be done with it.
9365 - Start sending 'truncated' cells back rather than destroy cells,
9366 if the circuit closes in front of you. This means we won't have
9367 to abandon partially built circuits.
9368 - Only warn once per nickname from add_nickname_list_to_smartlist
9369 per failure, so an entrynode or exitnode choice that's down won't
9371 - Put a note in the torrc about abuse potential with the default
9373 - Revise control spec and implementation to allow all log messages to
9374 be sent to controller with their severities intact (suggested by
9375 Matt Edman). Update TorControl to handle new log event types.
9376 - Provide better explanation messages when controller's POSTDESCRIPTOR
9378 - Stop putting nodename in the Platform string in server descriptors.
9379 It doesn't actually help, and it is confusing/upsetting some people.
9381 o Bugfixes on 0.1.0.2-rc:
9382 - We were printing the host mask wrong in exit policies in server
9383 descriptors. This isn't a critical bug though, since we were still
9384 obeying the exit policy internally.
9385 - Fix Tor when compiled with libevent but without pthreads: move
9386 connection_unregister() from _connection_free() to
9388 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
9389 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
9390 when we look through the connection array, we'll find any of the
9391 cpu/dnsworkers. This is no good.
9393 o Bugfixes on 0.0.9.8:
9394 - Fix possible bug on threading platforms (e.g. win32) which was
9395 leaking a file descriptor whenever a cpuworker or dnsworker died.
9396 - When using preferred entry or exit nodes, ignore whether the
9397 circuit wants uptime or capacity. They asked for the nodes, they
9399 - chdir() to your datadirectory at the *end* of the daemonize process,
9400 not the beginning. This was a problem because the first time you
9401 run tor, if your datadir isn't there, and you have runasdaemon set
9402 to 1, it will try to chdir to it before it tries to create it. Oops.
9403 - Handle changed router status correctly when dirserver reloads
9404 fingerprint file. We used to be dropping all unverified descriptors
9405 right then. The bug was hidden because we would immediately
9406 fetch a directory from another dirserver, which would include the
9407 descriptors we just dropped.
9408 - When we're connecting to an OR and he's got a different nickname/key
9409 than we were expecting, only complain loudly if we're an OP or a
9410 dirserver. Complaining loudly to the OR admins just confuses them.
9411 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
9412 artificially capped at 500kB.
9415 Changes in version 0.0.9.8 - 2005-04-07
9416 o Bugfixes on 0.0.9.x:
9417 - We have a bug that I haven't found yet. Sometimes, very rarely,
9418 cpuworkers get stuck in the 'busy' state, even though the cpuworker
9419 thinks of itself as idle. This meant that no new circuits ever got
9420 established. Here's a workaround to kill any cpuworker that's been
9421 busy for more than 100 seconds.
9424 Changes in version 0.1.0.2-rc - 2005-04-01
9425 o Bugfixes on 0.1.0.1-rc:
9426 - Fixes on reachability detection:
9427 - Don't check for reachability while hibernating.
9428 - If ORPort is reachable but DirPort isn't, still publish the
9429 descriptor, but zero out DirPort until it's found reachable.
9430 - When building testing circs for ORPort testing, use only
9431 high-bandwidth nodes, so fewer circuits fail.
9432 - Complain about unreachable ORPort separately from unreachable
9433 DirPort, so the user knows what's going on.
9434 - Make sure we only conclude ORPort reachability if we didn't
9435 initiate the conn. Otherwise we could falsely conclude that
9436 we're reachable just because we connected to the guy earlier
9437 and he used that same pipe to extend to us.
9438 - Authdirservers shouldn't do ORPort reachability detection,
9439 since they're in clique mode, so it will be rare to find a
9440 server not already connected to them.
9441 - When building testing circuits, always pick middle hops running
9442 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
9443 bug. (This is a kludge; it will go away when 0.0.9.x becomes
9445 - When we decide we're reachable, actually publish our descriptor
9447 - Fix bug in redirectstream in the controller.
9448 - Fix the state descriptor strings so logs don't claim edge streams
9449 are in a different state than they actually are.
9450 - Use recent libevent features when possible (this only really affects
9451 win32 and osx right now, because the new libevent with these
9452 features hasn't been released yet). Add code to suppress spurious
9454 - Prevent possible segfault in connection_close_unattached_ap().
9455 - Fix newlines on torrc in win32.
9456 - Improve error msgs when tor-resolve fails.
9458 o Improvements on 0.0.9.x:
9459 - New experimental script tor/contrib/ExerciseServer.py (needs more
9460 work) that uses the controller interface to build circuits and
9461 fetch pages over them. This will help us bootstrap servers that
9462 have lots of capacity but haven't noticed it yet.
9463 - New experimental script tor/contrib/PathDemo.py (needs more work)
9464 that uses the controller interface to let you choose whole paths
9466 "<hostname>.<path,separated by dots>.<length of path>.path"
9467 - When we've connected to an OR and handshaked but didn't like
9468 the result, we were closing the conn without sending destroy
9469 cells back for pending circuits. Now send those destroys.
9472 Changes in version 0.0.9.7 - 2005-04-01
9473 o Bugfixes on 0.0.9.x:
9474 - Fix another race crash bug (thanks to Glenn Fink for reporting).
9475 - Compare identity to identity, not to nickname, when extending to
9476 a router not already in the directory. This was preventing us from
9477 extending to unknown routers. Oops.
9478 - Make sure to create OS X Tor user in <500 range, so we aren't
9479 creating actual system users.
9480 - Note where connection-that-hasn't-sent-end was marked, and fix
9481 a few really loud instances of this harmless bug (it's fixed more
9485 Changes in version 0.1.0.1-rc - 2005-03-28
9487 - Add reachability testing. Your Tor server will automatically try
9488 to see if its ORPort and DirPort are reachable from the outside,
9489 and it won't upload its descriptor until it decides they are.
9490 - Handle unavailable hidden services better. Handle slow or busy
9491 hidden services better.
9492 - Add support for CONNECTing through https proxies, with "HttpsProxy"
9494 - New exit policy: accept most low-numbered ports, rather than
9495 rejecting most low-numbered ports.
9496 - More Tor controller support (still experimental). See
9497 http://tor.eff.org/doc/control-spec.txt for all the new features,
9498 including signals to emulate unix signals from any platform;
9499 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
9500 closestream; closecircuit; etc.
9501 - Make nt services work and start on startup on win32 (based on
9502 patch by Matt Edman).
9503 - Add a new AddressMap config directive to rewrite incoming socks
9504 addresses. This lets you, for example, declare an implicit
9505 required exit node for certain sites.
9506 - Add a new TrackHostExits config directive to trigger addressmaps
9507 for certain incoming socks addresses -- for sites that break when
9508 your exit keeps changing (based on patch by Mike Perry).
9509 - Redo the client-side dns cache so it's just an addressmap too.
9510 - Notice when our IP changes, and reset stats/uptime/reachability.
9511 - When an application is using socks5, give him the whole variety of
9512 potential socks5 responses (connect refused, host unreachable, etc),
9513 rather than just "success" or "failure".
9514 - A more sane version numbering system. See
9515 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
9516 - New contributed script "exitlist": a simple python script to
9517 parse directories and find Tor nodes that exit to listed
9519 - New contributed script "privoxy-tor-toggle" to toggle whether
9520 Privoxy uses Tor. Seems to be configured for Debian by default.
9521 - Report HTTP reasons to client when getting a response from directory
9522 servers -- so you can actually know what went wrong.
9523 - New config option MaxAdvertisedBandwidth which lets you advertise
9524 a low bandwidthrate (to not attract as many circuits) while still
9525 allowing a higher bandwidthrate in reality.
9527 o Robustness/stability fixes:
9528 - Make Tor use Niels Provos's libevent instead of its current
9529 poll-but-sometimes-select mess. This will let us use faster async
9530 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
9532 - pthread support now too. This was forced because when we forked,
9533 we ended up wasting a lot of duplicate ram over time. Also switch
9534 to foo_r versions of some library calls to allow reentry and
9536 - Better handling for heterogeneous / unreliable nodes:
9537 - Annotate circuits w/ whether they aim to contain high uptime nodes
9538 and/or high capacity nodes. When building circuits, choose
9540 - This means that every single node in an intro rend circuit,
9541 not just the last one, will have a minimum uptime.
9542 - New config option LongLivedPorts to indicate application streams
9543 that will want high uptime circuits.
9544 - Servers reset uptime when a dir fetch entirely fails. This
9545 hopefully reflects stability of the server's network connectivity.
9546 - If somebody starts his tor server in Jan 2004 and then fixes his
9547 clock, don't make his published uptime be a year.
9548 - Reset published uptime when you wake up from hibernation.
9549 - Introduce a notion of 'internal' circs, which are chosen without
9550 regard to the exit policy of the last hop. Intro and rendezvous
9551 circs must be internal circs, to avoid leaking information. Resolve
9552 and connect streams can use internal circs if they want.
9553 - New circuit pooling algorithm: make sure to have enough circs around
9554 to satisfy any predicted ports, and also make sure to have 2 internal
9555 circs around if we've required internal circs lately (and with high
9556 uptime if we've seen that lately too).
9557 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
9558 which describes how often we retry making new circuits if current
9559 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
9560 how long we're willing to make use of an already-dirty circuit.
9561 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
9562 circ as necessary, if there are any completed ones lying around
9563 when we try to launch one.
9564 - Make hidden services try to establish a rendezvous for 30 seconds,
9565 rather than for n (where n=3) attempts to build a circuit.
9566 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
9567 "ShutdownWaitLength".
9568 - Try to be more zealous about calling connection_edge_end when
9569 things go bad with edge conns in connection.c.
9570 - Revise tor-spec to add more/better stream end reasons.
9571 - Revise all calls to connection_edge_end to avoid sending "misc",
9572 and to take errno into account where possible.
9575 - Fix a race condition that can trigger an assert, when we have a
9576 pending create cell and an OR connection fails right then.
9577 - Fix several double-mark-for-close bugs, e.g. where we were finding
9578 a conn for a cell even if that conn is already marked for close.
9579 - Make sequence of log messages when starting on win32 with no config
9580 file more reasonable.
9581 - When choosing an exit node for a new non-internal circ, don't take
9582 into account whether it'll be useful for any pending x.onion
9583 addresses -- it won't.
9584 - Turn addr_policy_compare from a tristate to a quadstate; this should
9585 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
9586 for google.com" problem.
9587 - Make "platform" string in descriptor more accurate for Win32 servers,
9588 so it's not just "unknown platform".
9589 - Fix an edge case in parsing config options (thanks weasel).
9590 If they say "--" on the commandline, it's not an option.
9591 - Reject odd-looking addresses at the client (e.g. addresses that
9592 contain a colon), rather than having the server drop them because
9594 - tor-resolve requests were ignoring .exit if there was a working circuit
9595 they could use instead.
9596 - REUSEADDR on normal platforms means you can rebind to the port
9597 right after somebody else has let it go. But REUSEADDR on win32
9598 means to let you bind to the port _even when somebody else
9599 already has it bound_! So, don't do that on Win32.
9600 - Change version parsing logic: a version is "obsolete" if it is not
9601 recommended and (1) there is a newer recommended version in the
9602 same series, or (2) there are no recommended versions in the same
9603 series, but there are some recommended versions in a newer series.
9604 A version is "new" if it is newer than any recommended version in
9606 - Stop most cases of hanging up on a socks connection without sending
9610 - Require BandwidthRate to be at least 20kB/s for servers.
9611 - When a dirserver causes you to give a warn, mention which dirserver
9613 - New config option DirAllowPrivateAddresses for authdirservers.
9614 Now by default they refuse router descriptors that have non-IP or
9615 private-IP addresses.
9616 - Stop publishing socksport in the directory, since it's not
9617 actually meant to be public. For compatibility, publish a 0 there
9619 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
9620 smart" value, that is low for servers and high for clients.
9621 - If our clock jumps forward by 100 seconds or more, assume something
9622 has gone wrong with our network and abandon all not-yet-used circs.
9623 - Warn when exit policy implicitly allows local addresses.
9624 - If we get an incredibly skewed timestamp from a dirserver mirror
9625 that isn't a verified OR, don't warn -- it's probably him that's
9627 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
9628 cookies to disk and doesn't log each web request to disk. (Thanks
9629 to Brett Carrington for pointing this out.)
9630 - When a client asks us for a dir mirror and we don't have one,
9631 launch an attempt to get a fresh one.
9632 - If we're hibernating and we get a SIGINT, exit immediately.
9633 - Add --with-dmalloc ./configure option, to track memory leaks.
9634 - And try to free all memory on closing, so we can detect what
9636 - Cache local dns resolves correctly even when they're .exit
9638 - Give a better warning when some other server advertises an
9639 ORPort that is actually an apache running ssl.
9640 - Add "opt hibernating 1" to server descriptor to make it clearer
9641 whether the server is hibernating.
9644 Changes in version 0.0.9.6 - 2005-03-24
9645 o Bugfixes on 0.0.9.x (crashes and asserts):
9646 - Add new end stream reasons to maintainance branch. Fix bug where
9647 reason (8) could trigger an assert. Prevent bug from recurring.
9648 - Apparently win32 stat wants paths to not end with a slash.
9649 - Fix assert triggers in assert_cpath_layer_ok(), where we were
9650 blowing away the circuit that conn->cpath_layer points to, then
9651 checking to see if the circ is well-formed. Backport check to make
9652 sure we dont use the cpath on a closed connection.
9653 - Prevent circuit_resume_edge_reading_helper() from trying to package
9654 inbufs for marked-for-close streams.
9655 - Don't crash on hup if your options->address has become unresolvable.
9656 - Some systems (like OS X) sometimes accept() a connection and tell
9657 you the remote host is 0.0.0.0:0. If this happens, due to some
9658 other mis-features, we get confused; so refuse the conn for now.
9660 o Bugfixes on 0.0.9.x (other):
9661 - Fix harmless but scary "Unrecognized content encoding" warn message.
9662 - Add new stream error reason: TORPROTOCOL reason means "you are not
9663 speaking a version of Tor I understand; say bye-bye to your stream."
9664 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
9665 into the future, now that we are more tolerant of skew. This
9666 resolves a bug where a Tor server would refuse to cache a directory
9667 because all the directories it gets are too far in the future;
9668 yet the Tor server never logs any complaints about clock skew.
9669 - Mac packaging magic: make man pages useable, and do not overwrite
9670 existing torrc files.
9671 - Make OS X log happily to /var/log/tor/tor.log
9674 Changes in version 0.0.9.5 - 2005-02-22
9675 o Bugfixes on 0.0.9.x:
9676 - Fix an assert race at exit nodes when resolve requests fail.
9677 - Stop picking unverified dir mirrors--it only leads to misery.
9678 - Patch from Matt Edman to make NT services work better. Service
9679 support is still not compiled into the executable by default.
9680 - Patch from Dmitri Bely so the Tor service runs better under
9681 the win32 SYSTEM account.
9682 - Make tor-resolve actually work (?) on Win32.
9683 - Fix a sign bug when getrlimit claims to have 4+ billion
9684 file descriptors available.
9685 - Stop refusing to start when bandwidthburst == bandwidthrate.
9686 - When create cells have been on the onion queue more than five
9687 seconds, just send back a destroy and take them off the list.
9690 Changes in version 0.0.9.4 - 2005-02-03
9691 o Bugfixes on 0.0.9:
9692 - Fix an assert bug that took down most of our servers: when
9693 a server claims to have 1 GB of bandwidthburst, don't
9695 - Don't crash as badly if we have spawned the max allowed number
9696 of dnsworkers, or we're out of file descriptors.
9697 - Block more file-sharing ports in the default exit policy.
9698 - MaxConn is now automatically set to the hard limit of max
9699 file descriptors we're allowed (ulimit -n), minus a few for
9701 - Give a clearer message when servers need to raise their
9702 ulimit -n when they start running out of file descriptors.
9703 - SGI Compatibility patches from Jan Schaumann.
9704 - Tolerate a corrupt cached directory better.
9705 - When a dirserver hasn't approved your server, list which one.
9706 - Go into soft hibernation after 95% of the bandwidth is used,
9707 not 99%. This is especially important for daily hibernators who
9708 have a small accounting max. Hopefully it will result in fewer
9709 cut connections when the hard hibernation starts.
9710 - Load-balance better when using servers that claim more than
9711 800kB/s of capacity.
9712 - Make NT services work (experimental, only used if compiled in).
9715 Changes in version 0.0.9.3 - 2005-01-21
9716 o Bugfixes on 0.0.9:
9717 - Backport the cpu use fixes from main branch, so busy servers won't
9718 need as much processor time.
9719 - Work better when we go offline and then come back, or when we
9720 run Tor at boot before the network is up. We do this by
9721 optimistically trying to fetch a new directory whenever an
9722 application request comes in and we think we're offline -- the
9723 human is hopefully a good measure of when the network is back.
9724 - Backport some minimal hidserv bugfixes: keep rend circuits open as
9725 long as you keep using them; actually publish hidserv descriptors
9726 shortly after they change, rather than waiting 20-40 minutes.
9727 - Enable Mac startup script by default.
9728 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
9729 - When you update AllowUnverifiedNodes or FirewallPorts via the
9730 controller's setconf feature, we were always appending, never
9732 - When you update HiddenServiceDir via setconf, it was screwing up
9733 the order of reading the lines, making it fail.
9734 - Do not rewrite a cached directory back to the cache; otherwise we
9735 will think it is recent and not fetch a newer one on startup.
9736 - Workaround for webservers that lie about Content-Encoding: Tor
9737 now tries to autodetect compressed directories and compression
9738 itself. This lets us Proxypass dir fetches through apache.
9741 Changes in version 0.0.9.2 - 2005-01-04
9742 o Bugfixes on 0.0.9 (crashes and asserts):
9743 - Fix an assert on startup when the disk is full and you're logging
9745 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
9746 style address, then we'd crash.
9747 - Fix an assert trigger when the running-routers string we get from
9748 a dirserver is broken.
9749 - Make worker threads start and run on win32. Now win32 servers
9751 - Bandaid (not actually fix, but now it doesn't crash) an assert
9752 where the dns worker dies mysteriously and the main Tor process
9753 doesn't remember anything about the address it was resolving.
9755 o Bugfixes on 0.0.9 (Win32):
9756 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
9757 name out of the warning/assert messages.
9758 - Fix a superficial "unhandled error on read" bug on win32.
9759 - The win32 installer no longer requires a click-through for our
9760 license, since our Free Software license grants rights but does not
9762 - Win32: When connecting to a dirserver fails, try another one
9763 immediately. (This was already working for non-win32 Tors.)
9764 - Stop trying to parse $HOME on win32 when hunting for default
9766 - Make tor-resolve.c work on win32 by calling network_init().
9768 o Bugfixes on 0.0.9 (other):
9769 - Make 0.0.9.x build on Solaris again.
9770 - Due to a fencepost error, we were blowing away the \n when reporting
9771 confvalue items in the controller. So asking for multiple config
9772 values at once couldn't work.
9773 - When listing circuits that are pending on an opening OR connection,
9774 if we're an OR we were listing circuits that *end* at us as
9775 being pending on every listener, dns/cpu worker, etc. Stop that.
9776 - Dirservers were failing to create 'running-routers' or 'directory'
9777 strings if we had more than some threshold of routers. Fix them so
9778 they can handle any number of routers.
9779 - Fix a superficial "Duplicate mark for close" bug.
9780 - Stop checking for clock skew for OR connections, even for servers.
9781 - Fix a fencepost error that was chopping off the last letter of any
9782 nickname that is the maximum allowed nickname length.
9783 - Update URLs in log messages so they point to the new website.
9784 - Fix a potential problem in mangling server private keys while
9785 writing to disk (not triggered yet, as far as we know).
9786 - Include the licenses for other free software we include in Tor,
9787 now that we're shipping binary distributions more regularly.
9790 Changes in version 0.0.9.1 - 2004-12-15
9791 o Bugfixes on 0.0.9:
9792 - Make hibernation actually work.
9793 - Make HashedControlPassword config option work.
9794 - When we're reporting event circuit status to a controller,
9795 don't use the stream status code.
9798 Changes in version 0.0.9 - 2004-12-12
9800 - Clean up manpage and torrc.sample file.
9801 - Clean up severities and text of log warnings.
9803 - Make servers trigger an assert when they enter hibernation.
9806 Changes in version 0.0.9rc7 - 2004-12-08
9807 o Bugfixes on 0.0.9rc:
9808 - Fix a stack-trashing crash when an exit node begins hibernating.
9809 - Avoid looking at unallocated memory while considering which
9810 ports we need to build circuits to cover.
9811 - Stop a sigpipe: when an 'end' cell races with eof from the app,
9812 we shouldn't hold-open-until-flush if the eof arrived first.
9813 - Fix a bug with init_cookie_authentication() in the controller.
9814 - When recommending new-format log lines, if the upper bound is
9815 LOG_ERR, leave it implicit.
9817 o Bugfixes on 0.0.8.1:
9818 - Fix a whole slew of memory leaks.
9819 - Fix isspace() and friends so they still make Solaris happy
9820 but also so they don't trigger asserts on win32.
9821 - Fix parse_iso_time on platforms without strptime (eg win32).
9822 - win32: tolerate extra "readable" events better.
9823 - win32: when being multithreaded, leave parent fdarray open.
9824 - Make unit tests work on win32.
9827 Changes in version 0.0.9rc6 - 2004-12-06
9828 o Bugfixes on 0.0.9pre:
9829 - Clean up some more integer underflow opportunities (not exploitable
9831 - While hibernating, hup should not regrow our listeners.
9832 - Send an end to the streams we close when we hibernate, rather
9833 than just chopping them off.
9834 - React to eof immediately on non-open edge connections.
9836 o Bugfixes on 0.0.8.1:
9837 - Calculate timeout for waiting for a connected cell from the time
9838 we sent the begin cell, not from the time the stream started. If
9839 it took a long time to establish the circuit, we would time out
9840 right after sending the begin cell.
9841 - Fix router_compare_addr_to_addr_policy: it was not treating a port
9842 of * as always matching, so we were picking reject *:* nodes as
9843 exit nodes too. Oops.
9846 - New circuit building strategy: keep a list of ports that we've
9847 used in the past 6 hours, and always try to have 2 circuits open
9848 or on the way that will handle each such port. Seed us with port
9849 80 so web users won't complain that Tor is "slow to start up".
9850 - Make kill -USR1 dump more useful stats about circuits.
9851 - When warning about retrying or giving up, print the address, so
9852 the user knows which one it's talking about.
9853 - If you haven't used a clean circuit in an hour, throw it away,
9854 just to be on the safe side. (This means after 6 hours a totally
9855 unused Tor client will have no circuits open.)
9858 Changes in version 0.0.9rc5 - 2004-12-01
9859 o Bugfixes on 0.0.8.1:
9860 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
9861 - Let resolve conns retry/expire also, rather than sticking around
9863 - If we are using select, make sure we stay within FD_SETSIZE.
9865 o Bugfixes on 0.0.9pre:
9866 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
9867 but doesn't seem to be currently; thanks to Ilja van Sprundel for
9869 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
9870 instead. Impose minima and maxima for all *Period options; impose
9871 even tighter maxima for fetching if we are a caching dirserver.
9872 Clip rather than rejecting.
9873 - Fetch cached running-routers from servers that serve it (that is,
9874 authdirservers and servers running 0.0.9rc5-cvs or later.)
9877 - Accept *:706 (silc) in default exit policy.
9878 - Implement new versioning format for post 0.1.
9879 - Support "foo.nickname.exit" addresses, to let Alice request the
9880 address "foo" as viewed by exit node "nickname". Based on a patch
9882 - Make tor --version --version dump the cvs Id of every file.
9885 Changes in version 0.0.9rc4 - 2004-11-28
9886 o Bugfixes on 0.0.8.1:
9887 - Make windows sockets actually non-blocking (oops), and handle
9888 win32 socket errors better.
9890 o Bugfixes on 0.0.9rc1:
9891 - Actually catch the -USR2 signal.
9894 Changes in version 0.0.9rc3 - 2004-11-25
9895 o Bugfixes on 0.0.8.1:
9896 - Flush the log file descriptor after we print "Tor opening log file",
9897 so we don't see those messages days later.
9899 o Bugfixes on 0.0.9rc1:
9900 - Make tor-resolve work again.
9901 - Avoid infinite loop in tor-resolve if tor hangs up on it.
9902 - Fix an assert trigger for clients/servers handling resolves.
9905 Changes in version 0.0.9rc2 - 2004-11-24
9906 o Bugfixes on 0.0.9rc1:
9907 - I broke socks5 support while fixing the eof bug.
9908 - Allow unitless bandwidths and intervals; they default to bytes
9910 - New servers don't start out hibernating; they are active until
9911 they run out of bytes, so they have a better estimate of how
9912 long it takes, and so their operators can know they're working.
9915 Changes in version 0.0.9rc1 - 2004-11-23
9916 o Bugfixes on 0.0.8.1:
9917 - Finally fix a bug that's been plaguing us for a year:
9918 With high load, circuit package window was reaching 0. Whenever
9919 we got a circuit-level sendme, we were reading a lot on each
9920 socket, but only writing out a bit. So we would eventually reach
9921 eof. This would be noticed and acted on even when there were still
9922 bytes sitting in the inbuf.
9923 - When poll() is interrupted, we shouldn't believe the revents values.
9925 o Bugfixes on 0.0.9pre6:
9926 - Fix hibernate bug that caused pre6 to be broken.
9927 - Don't keep rephist info for routers that haven't had activity for
9928 24 hours. (This matters now that clients have keys, since we track
9930 - Never call close_temp_logs while validating log options.
9931 - Fix backslash-escaping on tor.sh.in and torctl.in.
9934 - Implement weekly/monthly/daily accounting: now you specify your
9935 hibernation properties by
9936 AccountingMax N bytes|KB|MB|GB|TB
9937 AccountingStart day|week|month [day] HH:MM
9938 Defaults to "month 1 0:00".
9939 - Let bandwidth and interval config options be specified as 5 bytes,
9940 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
9941 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
9942 get back to normal.)
9943 - If your requested entry or exit node has advertised bandwidth 0,
9945 - Be more greedy about filling up relay cells -- we try reading again
9946 once we've processed the stuff we read, in case enough has arrived
9947 to fill the last cell completely.
9948 - Apply NT service patch from Osamu Fujino. Still needs more work.
9951 Changes in version 0.0.9pre6 - 2004-11-15
9952 o Bugfixes on 0.0.8.1:
9953 - Fix assert failure on malformed socks4a requests.
9954 - Use identity comparison, not nickname comparison, to choose which
9955 half of circuit-ID-space each side gets to use. This is needed
9956 because sometimes we think of a router as a nickname, and sometimes
9957 as a hex ID, and we can't predict what the other side will do.
9958 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
9959 write() call will fail and we handle it there.
9960 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
9961 and smartlist_len, which are two major profiling offenders.
9963 o Bugfixes on 0.0.9pre5:
9964 - Fix a bug in read_all that was corrupting config files on windows.
9965 - When we're raising the max number of open file descriptors to
9966 'unlimited', don't log that we just raised it to '-1'.
9967 - Include event code with events, as required by control-spec.txt.
9968 - Don't give a fingerprint when clients do --list-fingerprint:
9969 it's misleading, because it will never be the same again.
9970 - Stop using strlcpy in tor_strndup, since it was slowing us
9972 - Remove warn on startup about missing cached-directory file.
9973 - Make kill -USR1 work again.
9974 - Hibernate if we start tor during the "wait for wakeup-time" phase
9975 of an accounting interval. Log our hibernation plans better.
9976 - Authoritative dirservers now also cache their directory, so they
9977 have it on start-up.
9980 - Fetch running-routers; cache running-routers; compress
9981 running-routers; serve compressed running-routers.z
9982 - Add NSI installer script contributed by J Doe.
9983 - Commit VC6 and VC7 workspace/project files.
9984 - Commit a tor.spec for making RPM files, with help from jbash.
9985 - Add contrib/torctl.in contributed by Glenn Fink.
9986 - Implement the control-spec's SAVECONF command, to write your
9987 configuration to torrc.
9988 - Get cookie authentication for the controller closer to working.
9989 - Include control-spec.txt in the tarball.
9990 - When set_conf changes our server descriptor, upload a new copy.
9991 But don't upload it too often if there are frequent changes.
9992 - Document authentication config in man page, and document signals
9994 - Clean up confusing parts of man page and torrc.sample.
9995 - Make expand_filename handle ~ and ~username.
9996 - Use autoconf to enable largefile support where necessary. Use
9997 ftello where available, since ftell can fail at 2GB.
9998 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
9999 log more informatively.
10000 - Give a slightly more useful output for "tor -h".
10001 - Refuse application socks connections to port 0.
10002 - Check clock skew for verified servers, but allow unverified
10003 servers and clients to have any clock skew.
10004 - Break DirFetchPostPeriod into:
10005 - DirFetchPeriod for fetching full directory,
10006 - StatusFetchPeriod for fetching running-routers,
10007 - DirPostPeriod for posting server descriptor,
10008 - RendPostPeriod for posting hidden service descriptors.
10009 - Make sure the hidden service descriptors are at a random offset
10010 from each other, to hinder linkability.
10013 Changes in version 0.0.9pre5 - 2004-11-09
10014 o Bugfixes on 0.0.9pre4:
10015 - Fix a seg fault in unit tests (doesn't affect main program).
10016 - Fix an assert bug where a hidden service provider would fail if
10017 the first hop of his rendezvous circuit was down.
10018 - Hidden service operators now correctly handle version 1 style
10019 INTRODUCE1 cells (nobody generates them still, so not a critical
10021 - If do_hup fails, actually notice.
10022 - Handle more errnos from accept() without closing the listener.
10023 Some OpenBSD machines were closing their listeners because
10024 they ran out of file descriptors.
10025 - Send resolve cells to exit routers that are running a new
10026 enough version of the resolve code to work right.
10027 - Better handling of winsock includes on non-MSV win32 compilers.
10028 - Some people had wrapped their tor client/server in a script
10029 that would restart it whenever it died. This did not play well
10030 with our "shut down if your version is obsolete" code. Now people
10031 don't fetch a new directory if their local cached version is
10033 - Make our autogen.sh work on ksh as well as bash.
10036 - Hibernation: New config option "AccountingMaxKB" lets you
10037 set how many KBytes per month you want to allow your server to
10038 consume. Rather than spreading those bytes out evenly over the
10039 month, we instead hibernate for some of the month and pop up
10040 at a deterministic time, work until the bytes are consumed, then
10041 hibernate again. Config option "MonthlyAccountingStart" lets you
10042 specify which day of the month your billing cycle starts on.
10043 - Control interface: a separate program can now talk to your
10044 client/server over a socket, and get/set config options, receive
10045 notifications of circuits and streams starting/finishing/dying,
10046 bandwidth used, etc. The next step is to get some GUIs working.
10047 Let us know if you want to help out. See doc/control-spec.txt .
10048 - Ship a contrib/tor-control.py as an example script to interact
10049 with the control port.
10050 - "tor --hash-password zzyxz" will output a salted password for
10051 use in authenticating to the control interface.
10052 - New log format in config:
10053 "Log minsev[-maxsev] stdout|stderr|syslog" or
10054 "Log minsev[-maxsev] file /var/foo"
10057 - DirPolicy config option, to let people reject incoming addresses
10058 from their dirserver.
10059 - "tor --list-fingerprint" will list your identity key fingerprint
10061 - Add "pass" target for RedirectExit, to make it easier to break
10062 out of a sequence of RedirectExit rules.
10063 - Clients now generate a TLS cert too, in preparation for having
10064 them act more like real nodes.
10065 - Ship src/win32/ in the tarball, so people can use it to build.
10066 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
10068 - New "router-status" line in directory, to better bind each verified
10069 nickname to its identity key.
10070 - Deprecate unofficial config option abbreviations, and abbreviations
10071 not on the command line.
10072 - Add a pure-C tor-resolve implementation.
10073 - Use getrlimit and friends to ensure we can reach MaxConn (currently
10074 1024) file descriptors.
10076 o Code security improvements, inspired by Ilja:
10077 - Replace sprintf with snprintf. (I think they were all safe, but
10079 - Replace strcpy/strncpy with strlcpy in more places.
10080 - Avoid strcat; use snprintf or strlcat instead.
10081 - snprintf wrapper with consistent (though not C99) overflow behavior.
10084 Changes in version 0.0.9pre4 - 2004-10-17
10085 o Bugfixes on 0.0.9pre3:
10086 - If the server doesn't specify an exit policy, use the real default
10087 exit policy, not reject *:*.
10088 - Ignore fascistfirewall when uploading/downloading hidden service
10089 descriptors, since we go through Tor for those; and when using
10090 an HttpProxy, since we assume it can reach them all.
10091 - When looking for an authoritative dirserver, use only the ones
10092 configured at boot. Don't bother looking in the directory.
10093 - The rest of the fix for get_default_conf_file() on older win32.
10094 - Make 'Routerfile' config option obsolete.
10097 - New 'MyFamily nick1,...' config option for a server to
10098 specify other servers that shouldn't be used in the same circuit
10099 with it. Only believed if nick1 also specifies us.
10100 - New 'NodeFamily nick1,nick2,...' config option for a client to
10101 specify nodes that it doesn't want to use in the same circuit.
10102 - New 'Redirectexit pattern address:port' config option for a
10103 server to redirect exit connections, e.g. to a local squid.
10106 Changes in version 0.0.9pre3 - 2004-10-13
10107 o Bugfixes on 0.0.8.1:
10108 - Better torrc example lines for dirbindaddress and orbindaddress.
10109 - Improved bounds checking on parsed ints (e.g. config options and
10110 the ones we find in directories.)
10111 - Better handling of size_t vs int, so we're more robust on 64
10113 - Fix the rest of the bug where a newly started OR would appear
10114 as unverified even after we've added his fingerprint and hupped
10116 - Fix a bug from 0.0.7: when read() failed on a stream, we would
10117 close it without sending back an end. So 'connection refused'
10118 would simply be ignored and the user would get no response.
10120 o Bugfixes on 0.0.9pre2:
10121 - Serving the cached-on-disk directory to people is bad. We now
10122 provide no directory until we've fetched a fresh one.
10123 - Workaround for bug on windows where cached-directories get crlf
10125 - Make get_default_conf_file() work on older windows too.
10126 - If we write a *:* exit policy line in the descriptor, don't write
10127 any more exit policy lines.
10130 - Use only 0.0.9pre1 and later servers for resolve cells.
10131 - Make the dirservers file obsolete.
10132 - Include a dir-signing-key token in directories to tell the
10133 parsing entity which key is being used to sign.
10134 - Remove the built-in bulky default dirservers string.
10135 - New config option "Dirserver %s:%d [fingerprint]", which can be
10136 repeated as many times as needed. If no dirservers specified,
10137 default to moria1,moria2,tor26.
10138 - Make moria2 advertise a dirport of 80, so people behind firewalls
10139 will be able to get a directory.
10140 - Http proxy support
10141 - Dirservers translate requests for http://%s:%d/x to /x
10142 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
10143 be routed through this host.
10144 - Clients ask for /tor/x rather than /x for new enough dirservers.
10145 This way we can one day coexist peacefully with apache.
10146 - Clients specify a "Host: %s%d" http header, to be compatible
10147 with more proxies, and so running squid on an exit node can work.
10150 Changes in version 0.0.8.1 - 2004-10-13
10152 - Fix a seg fault that can be triggered remotely for Tor
10153 clients/servers with an open dirport.
10154 - Fix a rare assert trigger, where routerinfos for entries in
10155 our cpath would expire while we're building the path.
10156 - Fix a bug in OutboundBindAddress so it (hopefully) works.
10157 - Fix a rare seg fault for people running hidden services on
10158 intermittent connections.
10159 - Fix a bug in parsing opt keywords with objects.
10160 - Fix a stale pointer assert bug when a stream detaches and
10162 - Fix a string format vulnerability (probably not exploitable)
10163 in reporting stats locally.
10164 - Fix an assert trigger: sometimes launching circuits can fail
10165 immediately, e.g. because too many circuits have failed recently.
10166 - Fix a compile warning on 64 bit platforms.
10169 Changes in version 0.0.9pre2 - 2004-10-03
10171 - Make fetching a cached directory work for 64-bit platforms too.
10172 - Make zlib.h a required header, not an optional header.
10175 Changes in version 0.0.9pre1 - 2004-10-01
10177 - Stop using separate defaults for no-config-file and
10178 empty-config-file. Now you have to explicitly turn off SocksPort,
10179 if you don't want it open.
10180 - Fix a bug in OutboundBindAddress so it (hopefully) works.
10181 - Improve man page to mention more of the 0.0.8 features.
10182 - Fix a rare seg fault for people running hidden services on
10183 intermittent connections.
10184 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
10186 - Fix more dns related bugs: send back resolve_failed and end cells
10187 more reliably when the resolve fails, rather than closing the
10188 circuit and then trying to send the cell. Also attach dummy resolve
10189 connections to a circuit *before* calling dns_resolve(), to fix
10190 a bug where cached answers would never be sent in RESOLVED cells.
10191 - When we run out of disk space, or other log writing error, don't
10192 crash. Just stop logging to that log and continue.
10193 - We were starting to daemonize before we opened our logs, so if
10194 there were any problems opening logs, we would complain to stderr,
10195 which wouldn't work, and then mysteriously exit.
10196 - Fix a rare bug where sometimes a verified OR would connect to us
10197 before he'd uploaded his descriptor, which would cause us to
10198 assign conn->nickname as though he's unverified. Now we look through
10199 the fingerprint list to see if he's there.
10200 - Fix a rare assert trigger, where routerinfos for entries in
10201 our cpath would expire while we're building the path.
10204 - Clients can ask dirservers for /dir.z to get a compressed version
10205 of the directory. Only works for servers running 0.0.9, of course.
10206 - Make clients cache directories and use them to seed their router
10207 lists at startup. This means clients have a datadir again.
10208 - Configuration infrastructure support for warning on obsolete
10210 - Respond to content-encoding headers by trying to uncompress as
10212 - Reply with a deflated directory when a client asks for "dir.z".
10213 We could use allow-encodings instead, but allow-encodings isn't
10214 specified in HTTP 1.0.
10215 - Raise the max dns workers from 50 to 100.
10216 - Discourage people from setting their dirfetchpostperiod more often
10217 than once per minute.
10218 - Protect dirservers from overzealous descriptor uploading -- wait
10219 10 seconds after directory gets dirty, before regenerating.
10222 Changes in version 0.0.8 - 2004-08-25
10223 o Port it to SunOS 5.9 / Athena
10226 Changes in version 0.0.8rc2 - 2004-08-20
10227 o Make it compile on cygwin again.
10228 o When picking unverified routers, skip those with low uptime and/or
10229 low bandwidth, depending on what properties you care about.
10232 Changes in version 0.0.8rc1 - 2004-08-18
10233 o Changes from 0.0.7.3:
10235 - Fix assert triggers: if the other side returns an address 0.0.0.0,
10236 don't put it into the client dns cache.
10237 - If a begin failed due to exit policy, but we believe the IP address
10238 should have been allowed, switch that router to exitpolicy reject *:*
10239 until we get our next directory.
10241 - Clients choose nodes proportional to advertised bandwidth.
10242 - Avoid using nodes with low uptime as introduction points.
10243 - Handle servers with dynamic IP addresses: don't replace
10244 options->Address with the resolved one at startup, and
10245 detect our address right before we make a routerinfo each time.
10246 - 'FascistFirewall' option to pick dirservers and ORs on specific
10247 ports; plus 'FirewallPorts' config option to tell FascistFirewall
10248 which ports are open. (Defaults to 80,443)
10249 - Be more aggressive about trying to make circuits when the network
10250 has changed (e.g. when you unsuspend your laptop).
10251 - Check for time skew on http headers; report date in response to
10253 - If the entrynode config line has only one node, don't pick it as
10255 - Add strict{entry|exit}nodes config options. If set to 1, then
10256 we refuse to build circuits that don't include the specified entry
10258 - OutboundBindAddress config option, to bind to a specific
10259 IP address for outgoing connect()s.
10260 - End truncated log entries (e.g. directories) with "[truncated]".
10262 o Patches to 0.0.8preX:
10264 - Patches to compile and run on win32 again (maybe)?
10265 - Fix crash when looking for ~/.torrc with no $HOME set.
10266 - Fix a race bug in the unit tests.
10267 - Handle verified/unverified name collisions better when new
10268 routerinfo's arrive in a directory.
10269 - Sometimes routers were getting entered into the stats before
10270 we'd assigned their identity_digest. Oops.
10271 - Only pick and establish intro points after we've gotten a
10274 - AllowUnverifiedNodes config option to let circuits choose no-name
10275 routers in entry,middle,exit,introduction,rendezvous positions.
10276 Allow middle and rendezvous positions by default.
10277 - Add a man page for tor-resolve.
10280 Changes in version 0.0.7.3 - 2004-08-12
10281 o Stop dnsworkers from triggering an assert failure when you
10282 ask them to resolve the host "".
10285 Changes in version 0.0.8pre3 - 2004-08-09
10286 o Changes from 0.0.7.2:
10287 - Allow multiple ORs with same nickname in routerlist -- now when
10288 people give us one identity key for a nickname, then later
10289 another, we don't constantly complain until the first expires.
10290 - Remember used bandwidth (both in and out), and publish 15-minute
10291 snapshots for the past day into our descriptor.
10292 - You can now fetch $DIRURL/running-routers to get just the
10293 running-routers line, not the whole descriptor list. (But
10294 clients don't use this yet.)
10295 - When people mistakenly use Tor as an http proxy, point them
10296 at the tor-doc.html rather than the INSTALL.
10297 - Remove our mostly unused -- and broken -- hex_encode()
10298 function. Use base16_encode() instead. (Thanks to Timo Lindfors
10299 for pointing out this bug.)
10300 - Rotate onion keys every 12 hours, not every 2 hours, so we have
10301 fewer problems with people using the wrong key.
10302 - Change the default exit policy to reject the default edonkey,
10303 kazaa, gnutella ports.
10304 - Add replace_file() to util.[ch] to handle win32's rename().
10306 o Changes from 0.0.8preX:
10307 - Fix two bugs in saving onion keys to disk when rotating, so
10308 hopefully we'll get fewer people using old onion keys.
10309 - Fix an assert error that was making SocksPolicy not work.
10310 - Be willing to expire routers that have an open dirport -- it's
10311 just the authoritative dirservers we want to not forget.
10312 - Reject tor-resolve requests for .onion addresses early, so we
10313 don't build a whole rendezvous circuit and then fail.
10314 - When you're warning a server that he's unverified, don't cry
10315 wolf unpredictably.
10316 - Fix a race condition: don't try to extend onto a connection
10317 that's still handshaking.
10318 - For servers in clique mode, require the conn to be open before
10319 you'll choose it for your path.
10320 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
10321 end relay cell, etc.
10322 - Measure bandwidth capacity over the last 24 hours, not just 12
10323 - Bugfix: authoritative dirservers were making and signing a new
10324 directory for each client, rather than reusing the cached one.
10327 Changes in version 0.0.8pre2 - 2004-08-04
10328 o Changes from 0.0.7.2:
10330 - Check directory signature _before_ you decide whether you're
10331 you're running an obsolete version and should exit.
10332 - Check directory signature _before_ you parse the running-routers
10333 list to decide who's running or verified.
10334 - Bugfixes and features:
10335 - Check return value of fclose while writing to disk, so we don't
10336 end up with broken files when servers run out of disk space.
10337 - Log a warning if the user uses an unsafe socks variant, so people
10338 are more likely to learn about privoxy or socat.
10339 - Dirservers now include RFC1123-style dates in the HTTP headers,
10340 which one day we will use to better detect clock skew.
10342 o Changes from 0.0.8pre1:
10343 - Make it compile without warnings again on win32.
10344 - Log a warning if you're running an unverified server, to let you
10345 know you might want to get it verified.
10346 - Only pick a default nickname if you plan to be a server.
10349 Changes in version 0.0.8pre1 - 2004-07-23
10351 - Made our unit tests compile again on OpenBSD 3.5, and tor
10352 itself compile again on OpenBSD on a sparc64.
10353 - We were neglecting milliseconds when logging on win32, so
10354 everything appeared to happen at the beginning of each second.
10356 o Protocol changes:
10357 - 'Extend' relay cell payloads now include the digest of the
10358 intended next hop's identity key. Now we can verify that we're
10359 extending to the right router, and also extend to routers we
10360 hadn't heard of before.
10363 - Tor nodes can now act as relays (with an advertised ORPort)
10364 without being manually verified by the dirserver operators.
10365 - Uploaded descriptors of unverified routers are now accepted
10366 by the dirservers, and included in the directory.
10367 - Verified routers are listed by nickname in the running-routers
10368 list; unverified routers are listed as "$<fingerprint>".
10369 - We now use hash-of-identity-key in most places rather than
10370 nickname or addr:port, for improved security/flexibility.
10371 - To avoid Sybil attacks, paths still use only verified servers.
10372 But now we have a chance to play around with hybrid approaches.
10373 - Nodes track bandwidth usage to estimate capacity (not used yet).
10374 - ClientOnly option for nodes that never want to become servers.
10375 - Directory caching.
10376 - "AuthoritativeDir 1" option for the official dirservers.
10377 - Now other nodes (clients and servers) will cache the latest
10378 directory they've pulled down.
10379 - They can enable their DirPort to serve it to others.
10380 - Clients will pull down a directory from any node with an open
10381 DirPort, and check the signature/timestamp correctly.
10382 - Authoritative dirservers now fetch directories from other
10383 authdirservers, to stay better synced.
10384 - Running-routers list tells who's down also, along with noting
10385 if they're verified (listed by nickname) or unverified (listed
10387 - Allow dirservers to serve running-router list separately.
10388 This isn't used yet.
10389 - ORs connect-on-demand to other ORs
10390 - If you get an extend cell to an OR you're not connected to,
10391 connect, handshake, and forward the create cell.
10392 - The authoritative dirservers stay connected to everybody,
10393 and everybody stays connected to 0.0.7 servers, but otherwise
10394 clients/servers expire unused connections after 5 minutes.
10395 - When servers get a sigint, they delay 30 seconds (refusing new
10396 connections) then exit. A second sigint causes immediate exit.
10397 - File and name management:
10398 - Look for .torrc if no CONFDIR "torrc" is found.
10399 - If no datadir is defined, then choose, make, and secure ~/.tor
10401 - If torrc not found, exitpolicy reject *:*.
10402 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
10403 - If no nickname is defined, derive default from hostname.
10404 - Rename secret key files, e.g. identity.key -> secret_id_key,
10405 to discourage people from mailing their identity key to tor-ops.
10406 - Refuse to build a circuit before the directory has arrived --
10407 it won't work anyway, since you won't know the right onion keys
10409 - Try other dirservers immediately if the one you try is down. This
10410 should tolerate down dirservers better now.
10411 - Parse tor version numbers so we can do an is-newer-than check
10412 rather than an is-in-the-list check.
10413 - New socks command 'resolve', to let us shim gethostbyname()
10415 - A 'tor_resolve' script to access the socks resolve functionality.
10416 - A new socks-extensions.txt doc file to describe our
10417 interpretation and extensions to the socks protocols.
10418 - Add a ContactInfo option, which gets published in descriptor.
10419 - Publish OR uptime in descriptor (and thus in directory) too.
10420 - Write tor version at the top of each log file
10421 - New docs in the tarball:
10423 - Document that you should proxy your SSL traffic too.
10426 Changes in version 0.0.7.2 - 2004-07-07
10427 o A better fix for the 0.0.0.0 problem, that will hopefully
10428 eliminate the remaining related assertion failures.
10431 Changes in version 0.0.7.1 - 2004-07-04
10432 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
10433 since internally we use 0.0.0.0 to signify "not yet resolved".
10436 Changes in version 0.0.7 - 2004-06-07
10437 o Updated the man page to reflect the new features.
10440 Changes in version 0.0.7rc2 - 2004-06-06
10441 o Changes from 0.0.7rc1:
10442 - Make it build on Win32 again.
10443 o Changes from 0.0.6.2:
10444 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
10448 Changes in version 0.0.7rc1 - 2004-06-02
10450 - On sighup, we were adding another log without removing the first
10451 one. So log messages would get duplicated n times for n sighups.
10452 - Several cases of using a connection after we'd freed it. The
10453 problem was that connections that are pending resolve are in both
10454 the pending_resolve tree, and also the circuit's resolving_streams
10455 list. When you want to remove one, you must remove it from both.
10456 - Fix a double-mark-for-close where an end cell arrived for a
10457 resolving stream, and then the resolve failed.
10458 - Check directory signatures based on name of signer, not on whom
10459 we got the directory from. This will let us cache directories more
10462 - Crank up some of our constants to handle more users.
10465 Changes in version 0.0.7pre1 - 2004-06-02
10466 o Fixes for crashes and other obnoxious bugs:
10467 - Fix an epipe bug: sometimes when directory connections failed
10468 to connect, we would give them a chance to flush before closing
10470 - When we detached from a circuit because of resolvefailed, we
10471 would immediately try the same circuit twice more, and then
10472 give up on the resolve thinking we'd tried three different
10474 - Limit the number of intro circuits we'll attempt to build for a
10475 hidden service per 15-minute period.
10476 - Check recommended-software string *early*, before actually parsing
10477 the directory. Thus we can detect an obsolete version and exit,
10478 even if the new directory format doesn't parse.
10479 o Fixes for security bugs:
10480 - Remember which nodes are dirservers when you startup, and if a
10481 random OR enables his dirport, don't automatically assume he's
10482 a trusted dirserver.
10484 - Directory connections were asking the wrong poll socket to
10485 start writing, and not asking themselves to start writing.
10486 - When we detached from a circuit because we sent a begin but
10487 didn't get a connected, we would use it again the first time;
10488 but after that we would correctly switch to a different one.
10489 - Stop warning when the first onion decrypt attempt fails; they
10490 will sometimes legitimately fail now that we rotate keys.
10491 - Override unaligned-access-ok check when $host_cpu is ia64 or
10492 arm. Apparently they allow it but the kernel whines.
10493 - Dirservers try to reconnect periodically too, in case connections
10495 - Fix some memory leaks in directory servers.
10496 - Allow backslash in Win32 filenames.
10497 - Made Tor build complain-free on FreeBSD, hopefully without
10498 breaking other BSD builds. We'll see.
10500 - Doxygen markup on all functions and global variables.
10501 - Make directory functions update routerlist, not replace it. So
10502 now directory disagreements are not so critical a problem.
10503 - Remove the upper limit on number of descriptors in a dirserver's
10504 directory (not that we were anywhere close).
10505 - Allow multiple logfiles at different severity ranges.
10506 - Allow *BindAddress to specify ":port" rather than setting *Port
10507 separately. Allow multiple instances of each BindAddress config
10508 option, so you can bind to multiple interfaces if you want.
10509 - Allow multiple exit policy lines, which are processed in order.
10510 Now we don't need that huge line with all the commas in it.
10511 - Enable accept/reject policies on SOCKS connections, so you can bind
10512 to 0.0.0.0 but still control who can use your OP.
10515 Changes in version 0.0.6.2 - 2004-05-16
10516 o Our integrity-checking digest was checking only the most recent cell,
10517 not the previous cells like we'd thought.
10518 Thanks to Stefan Mark for finding the flaw!
10521 Changes in version 0.0.6.1 - 2004-05-06
10522 o Fix two bugs in our AES counter-mode implementation (this affected
10523 onion-level stream encryption, but not TLS-level). It turns
10524 out we were doing something much more akin to a 16-character
10525 polyalphabetic cipher. Oops.
10526 Thanks to Stefan Mark for finding the flaw!
10527 o Retire moria3 as a directory server, and add tor26 as a directory
10531 Changes in version 0.0.6 - 2004-05-02
10532 [version bump only]
10535 Changes in version 0.0.6rc4 - 2004-05-01
10536 o Update the built-in dirservers list to use the new directory format
10537 o Fix a rare seg fault: if a node offering a hidden service attempts
10538 to build a circuit to Alice's rendezvous point and fails before it
10539 reaches the last hop, it retries with a different circuit, but
10541 o Handle windows socket errors correctly.
10544 Changes in version 0.0.6rc3 - 2004-04-28
10545 o Don't expire non-general excess circuits (if we had enough
10546 circuits open, we were expiring rendezvous circuits -- even
10547 when they had a stream attached. oops.)
10548 o Fetch randomness from /dev/urandom better (not via fopen/fread)
10549 o Better debugging for tls errors
10550 o Some versions of openssl have an SSL_pending function that erroneously
10551 returns bytes when there is a non-application record pending.
10552 o Set Content-Type on the directory and hidserv descriptor.
10553 o Remove IVs from cipher code, since AES-ctr has none.
10554 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
10555 o We were using an array of length zero in a few places.
10556 o win32's gethostbyname can't resolve an IP to an IP.
10557 o win32's close can't close a socket.
10560 Changes in version 0.0.6rc2 - 2004-04-26
10561 o Fix a bug where we were closing tls connections intermittently.
10562 It turns out openssl keeps its errors around -- so if an error
10563 happens, and you don't ask about it, and then another openssl
10564 operation happens and succeeds, and you ask if there was an error,
10565 it tells you about the first error. Fun fun.
10566 o Fix a bug that's been lurking since 27 may 03 (!)
10567 When passing back a destroy cell, we would use the wrong circ id.
10568 'Mostly harmless', but still worth fixing.
10569 o Since we don't support truncateds much, don't bother sending them;
10570 just close the circ.
10571 o check for <machine/limits.h> so we build on NetBSD again (I hope).
10572 o don't crash if a conn that sent a begin has suddenly lost its circuit
10573 (this was quite rare).
10576 Changes in version 0.0.6rc1 - 2004-04-25
10577 o We now rotate link (tls context) keys and onion keys.
10578 o CREATE cells now include oaep padding, so you can tell
10579 if you decrypted them correctly.
10580 o Add bandwidthburst to server descriptor.
10581 o Directories now say which dirserver signed them.
10582 o Use a tor_assert macro that logs failed assertions too.
10585 Changes in version 0.0.6pre5 - 2004-04-18
10586 o changes from 0.0.6pre4:
10587 - make tor build on broken freebsd 5.2 installs
10588 - fix a failed assert when you try an intro point, get a nack, and try
10589 a second one and it works.
10590 - when alice uses a port that the hidden service doesn't accept,
10591 it now sends back an end cell (denied by exit policy). otherwise
10592 alice would just have to wait to time out.
10593 - fix another rare bug: when we had tried all the intro
10594 points for a hidden service, we fetched the descriptor
10595 again, but we left our introcirc thinking it had already
10596 sent an intro, so it kept waiting for a response...
10597 - bugfix: when you sleep your hidden-service laptop, as soon
10598 as it wakes up it tries to upload a service descriptor, but
10599 socketpair fails for some reason (localhost not up yet?).
10600 now we simply give up on that upload, and we'll try again later.
10601 i'd still like to find the bug though.
10602 - if an intro circ waiting for an ack dies before getting one, then
10604 - we were reusing stale service descriptors and refetching usable
10608 Changes in version 0.0.6pre4 - 2004-04-14
10609 o changes from 0.0.6pre3:
10610 - when bob fails to connect to the rendezvous point, and his
10611 circ didn't fail because of the rendezvous point itself, then
10612 he retries a couple of times
10613 - we expire introduction and rendezvous circs more thoroughly
10614 (sometimes they were hanging around forever)
10615 - we expire unattached rendezvous streams that have been around
10616 too long (they were sticking around forever).
10617 - fix a measly fencepost error that was crashing everybody with
10621 Changes in version 0.0.6pre3 - 2004-04-14
10622 o changes from 0.0.6pre2:
10623 - make hup work again
10624 - fix some memory leaks for dirservers
10625 - allow more skew in rendezvous descriptor timestamps, to help
10626 handle people like blanu who don't know what time it is
10627 - normal circs are 3 hops, but some rend/intro circs are 4, if
10628 the initiator doesn't get to choose the last hop
10629 - send acks for introductions, so alice can know whether to try
10631 - bob publishes intro points more correctly
10632 o changes from 0.0.5:
10633 - fix an assert trigger that's been plaguing us since the days
10634 of 0.0.2prexx (thanks weasel!)
10635 - retry stream correctly when we fail to connect because of
10636 exit-policy-reject (should try another) or can't-resolve-address
10637 (also should try another, because dns on random internet servers
10639 - when we hup a dirserver and we've *removed* a server from the
10640 approved-routers list, now we remove that server from the
10641 in-memory directories too
10644 Changes in version 0.0.6pre2 - 2004-04-08
10645 o We fixed our base32 implementation. Now it works on all architectures.
10648 Changes in version 0.0.6pre1 - 2004-04-08
10650 - Hidden services and rendezvous points are implemented. Go to
10651 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
10652 hidden services. (This only works via a socks4a proxy such as
10653 Privoxy, and currently it's quite slow.)
10656 Changes in version 0.0.5 - 2004-03-30
10657 [version bump only]
10660 Changes in version 0.0.5rc3 - 2004-03-29
10661 o Install torrc as torrc.sample -- we no longer clobber your
10663 o Re-enable recommendedversion checking (we broke it in rc2, oops)
10664 o Add in a 'notice' log level for things the operator should hear
10665 but that aren't warnings
10668 Changes in version 0.0.5rc2 - 2004-03-29
10669 o Hold socks connection open until reply is flushed (if possible)
10670 o Make exit nodes resolve IPs to IPs immediately, rather than asking
10671 the dns farm to do it.
10672 o Fix c99 aliasing warnings in rephist.c
10673 o Don't include server descriptors that are older than 24 hours in the
10675 o Give socks 'reject' replies their whole 15s to attempt to flush,
10676 rather than seeing the 60s timeout and assuming the flush had failed.
10677 o Clean automake droppings from the cvs repository
10680 Changes in version 0.0.5rc1 - 2004-03-28
10681 o Fix mangled-state bug in directory fetching (was causing sigpipes).
10682 o Only build circuits after we've fetched the directory: clients were
10683 using only the directory servers before they'd fetched a directory.
10684 This also means longer startup time; so it goes.
10685 o Fix an assert trigger where an OP would fail to handshake, and we'd
10686 expect it to have a nickname.
10687 o Work around a tsocks bug: do a socks reject when AP connection dies
10688 early, else tsocks goes into an infinite loop.
10691 Changes in version 0.0.4 - 2004-03-26
10692 o When connecting to a dirserver or OR and the network is down,
10696 Changes in version 0.0.3 - 2004-03-26
10697 o Warn and fail if server chose a nickname with illegal characters
10698 o Port to Solaris and Sparc:
10699 - include missing header fcntl.h
10700 - have autoconf find -lsocket -lnsl automatically
10701 - deal with hardware word alignment
10702 - make uname() work (solaris has a different return convention)
10703 - switch from using signal() to sigaction()
10704 o Preliminary work on reputation system:
10705 - Keep statistics on success/fail of connect attempts; they're published
10706 by kill -USR1 currently.
10707 - Add a RunTesting option to try to learn link state by creating test
10708 circuits, even when SocksPort is off.
10709 - Remove unused open circuits when there are too many.
10712 Changes in version 0.0.2 - 2004-03-19
10713 - Include strlcpy and strlcat for safer string ops
10714 - define INADDR_NONE so we compile (but still not run) on solaris
10717 Changes in version 0.0.2pre27 - 2004-03-14
10719 - Allow internal tor networks (we were rejecting internal IPs,
10720 now we allow them if they're set explicitly).
10721 - And fix a few endian issues.
10724 Changes in version 0.0.2pre26 - 2004-03-14
10726 - If a stream times out after 15s without a connected cell, don't
10727 try that circuit again: try a new one.
10728 - Retry streams at most 4 times. Then give up.
10729 - When a dirserver gets a descriptor from an unknown router, it
10730 logs its fingerprint (so the dirserver operator can choose to
10731 accept it even without mail from the server operator).
10732 - Inform unapproved servers when we reject their descriptors.
10733 - Make tor build on Windows again. It works as a client, who knows
10735 - Clearer instructions in the torrc for how to set up a server.
10736 - Be more efficient about reading fd's when our global token bucket
10737 (used for rate limiting) becomes empty.
10739 - Stop asserting that computers always go forward in time. It's
10741 - When we sent a cell (e.g. destroy) and then marked an OR connection
10742 expired, we might close it before finishing a flush if the other
10743 side isn't reading right then.
10744 - Don't allow dirservers to start if they haven't defined
10745 RecommendedVersions
10746 - We were caching transient dns failures. Oops.
10747 - Prevent servers from publishing an internal IP as their address.
10748 - Address a strcat vulnerability in circuit.c
10751 Changes in version 0.0.2pre25 - 2004-03-04
10753 - Put the OR's IP in its router descriptor, not its fqdn. That way
10754 we'll stop being stalled by gethostbyname for nodes with flaky dns,
10757 - If the user typed in an address that didn't resolve, the server
10761 Changes in version 0.0.2pre24 - 2004-03-03
10763 - Fix an assertion failure in dns.c, where we were trying to dequeue
10764 a pending dns resolve even if it wasn't pending
10765 - Fix a spurious socks5 warning about still trying to write after the
10766 connection is finished.
10767 - Hold certain marked_for_close connections open until they're finished
10768 flushing, rather than losing bytes by closing them too early.
10769 - Correctly report the reason for ending a stream
10770 - Remove some duplicate calls to connection_mark_for_close
10771 - Put switch_id and start_daemon earlier in the boot sequence, so it
10772 will actually try to chdir() to options.DataDirectory
10773 - Make 'make test' exit(1) if a test fails; fix some unit tests
10774 - Make tor fail when you use a config option it doesn't know about,
10775 rather than warn and continue.
10776 - Make --version work
10777 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
10780 Changes in version 0.0.2pre23 - 2004-02-29
10782 - Print a statement when the first circ is finished, so the user
10783 knows it's working.
10784 - If a relay cell is unrecognized at the end of the circuit,
10785 send back a destroy. (So attacks to mutate cells are more
10787 - New config option 'excludenodes' to avoid certain nodes for circuits.
10788 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
10789 so you can collect coredumps there.
10791 - Fix a bug in tls flushing where sometimes data got wedged and
10792 didn't flush until more data got sent. Hopefully this bug was
10793 a big factor in the random delays we were seeing.
10794 - Make 'connected' cells include the resolved IP, so the client
10795 dns cache actually gets populated.
10796 - Disallow changing from ORPort=0 to ORPort>0 on hup.
10797 - When we time-out on a stream and detach from the circuit, send an
10798 end cell down it first.
10799 - Only warn about an unknown router (in exitnodes, entrynodes,
10800 excludenodes) after we've fetched a directory.
10803 Changes in version 0.0.2pre22 - 2004-02-26
10805 - Servers publish less revealing uname information in descriptors.
10806 - More memory tracking and assertions, to crash more usefully when
10808 - If the default torrc isn't there, just use some default defaults.
10809 Plus provide an internal dirservers file if they don't have one.
10810 - When the user tries to use Tor as an http proxy, give them an http
10811 501 failure explaining that we're a socks proxy.
10812 - Dump a new router.desc on hup, to help confused people who change
10813 their exit policies and then wonder why router.desc doesn't reflect
10815 - Clean up the generic tor.sh init script that we ship with.
10817 - If the exit stream is pending on the resolve, and a destroy arrives,
10818 then the stream wasn't getting removed from the pending list. I
10819 think this was the one causing recent server crashes.
10820 - Use a more robust poll on OSX 10.3, since their poll is flaky.
10821 - When it couldn't resolve any dirservers, it was useless from then on.
10822 Now it reloads the RouterFile (or default dirservers) if it has no
10824 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
10825 many users don't even *have* a /usr/local/sbin/.
10828 Changes in version 0.0.2pre21 - 2004-02-18
10830 - There's a ChangeLog file that actually reflects the changelog.
10831 - There's a 'torify' wrapper script, with an accompanying
10832 tor-tsocks.conf, that simplifies the process of using tsocks for
10833 tor. It even has a man page.
10834 - The tor binary gets installed to sbin rather than bin now.
10835 - Retry streams where the connected cell hasn't arrived in 15 seconds
10836 - Clean up exit policy handling -- get the default out of the torrc,
10837 so we can update it without forcing each server operator to fix
10839 - Allow imaps and pop3s in default exit policy
10841 - Prevent picking middleman nodes as the last node in the circuit
10844 Changes in version 0.0.2pre20 - 2004-01-30
10846 - We now have a deb package, and it's in debian unstable. Go to
10847 it, apt-getters. :)
10848 - I've split the TotalBandwidth option into BandwidthRate (how many
10849 bytes per second you want to allow, long-term) and
10850 BandwidthBurst (how many bytes you will allow at once before the cap
10851 kicks in). This better token bucket approach lets you, say, set
10852 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
10853 performance while not exceeding your monthly bandwidth quota.
10854 - Push out a tls record's worth of data once you've got it, rather
10855 than waiting until you've read everything waiting to be read. This
10856 may improve performance by pipelining better. We'll see.
10857 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
10858 from failed circuits (if they haven't been connected yet) and attach
10860 - Expire old streams that haven't managed to connect. Some day we'll
10861 have them reattach to new circuits instead.
10864 - Fix several memory leaks that were causing servers to become bloated
10866 - Fix a few very rare assert triggers. A few more remain.
10867 - Setuid to User _before_ complaining about running as root.
10870 Changes in version 0.0.2pre19 - 2004-01-07
10872 - Fix deadlock condition in dns farm. We were telling a child to die by
10873 closing the parent's file descriptor to him. But newer children were
10874 inheriting the open file descriptor from the parent, and since they
10875 weren't closing it, the socket never closed, so the child never read
10876 eof, so he never knew to exit. Similarly, dns workers were holding
10877 open other sockets, leading to all sorts of chaos.
10878 - New cleaner daemon() code for forking and backgrounding.
10879 - If you log to a file, it now prints an entry at the top of the
10880 logfile so you know it's working.
10881 - The onionskin challenge length was 30 bytes longer than necessary.
10882 - Started to patch up the spec so it's not quite so out of date.
10885 Changes in version 0.0.2pre18 - 2004-01-02
10887 - Fix endian issues with the 'integrity' field in the relay header.
10888 - Fix a potential bug where connections in state
10889 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
10892 Changes in version 0.0.2pre17 - 2003-12-30
10894 - Made --debuglogfile (or any second log file, actually) work.
10895 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
10896 adversary could force us into an infinite loop.
10899 - Each onionskin handshake now includes a hash of the computed key,
10900 to prove the server's identity and help perfect forward secrecy.
10901 - Changed cell size from 256 to 512 bytes (working toward compatibility
10903 - Changed cell length to 2 bytes, and moved it to the relay header.
10904 - Implemented end-to-end integrity checking for the payloads of
10906 - Separated streamid from 'recognized' (otherwise circuits will get
10907 messed up when we try to have streams exit from the middle). We
10908 use the integrity-checking to confirm that a cell is addressed to
10910 - Randomize the initial circid and streamid values, so an adversary who
10911 breaks into a node can't learn how many circuits or streams have
10915 Changes in version 0.0.2pre16 - 2003-12-14
10917 - Fixed a bug that made HUP trigger an assert
10918 - Fixed a bug where a circuit that immediately failed wasn't being
10919 counted as a failed circuit in counting retries.
10922 - Now we close the circuit when we get a truncated cell: otherwise we're
10923 open to an anonymity attack where a bad node in the path truncates
10924 the circuit and then we open streams at him.
10925 - Add port ranges to exit policies
10926 - Add a conservative default exit policy
10927 - Warn if you're running tor as root
10928 - on HUP, retry OR connections and close/rebind listeners
10929 - options.EntryNodes: try these nodes first when picking the first node
10930 - options.ExitNodes: if your best choices happen to include any of
10931 your preferred exit nodes, you choose among just those preferred
10933 - options.ExcludedNodes: nodes that are never picked in path building
10936 Changes in version 0.0.2pre15 - 2003-12-03
10937 o Robustness and bugfixes:
10938 - Sometimes clients would cache incorrect DNS resolves, which would
10939 really screw things up.
10940 - An OP that goes offline would slowly leak all its sockets and stop
10942 - A wide variety of bugfixes in exit node selection, exit policy
10943 handling, and processing pending streams when a new circuit is
10945 - Pick nodes for a path only from those the directory says are up
10946 - Choose randomly from all running dirservers, not always the first one
10947 - Increase allowed http header size for directory fetch.
10948 - Stop writing to stderr (if we're daemonized it will be closed).
10949 - Enable -g always, so cores will be more useful to me.
10950 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
10953 - Wrote a man page. It lists commonly used options.
10956 - Change default loglevel to warn.
10957 - Make PidFile default to null rather than littering in your CWD.
10958 - OnionRouter config option is now obsolete. Instead it just checks
10960 - Moved to a single unified torrc file for both clients and servers.
10963 Changes in version 0.0.2pre14 - 2003-11-29
10964 o Robustness and bugfixes:
10965 - Force the admin to make the DataDirectory himself
10966 - to get ownership/permissions right
10967 - so clients no longer make a DataDirectory and then never use it
10968 - fix bug where a client who was offline for 45 minutes would never
10969 pull down a directory again
10970 - fix (or at least hide really well) the dns assert bug that was
10971 causing server crashes
10972 - warnings and improved robustness wrt clockskew for certs
10973 - use the native daemon(3) to daemonize, when available
10974 - exit if bind() fails
10975 - exit if neither socksport nor orport is defined
10976 - include our own tor_timegm (Win32 doesn't have its own)
10977 - bugfix for win32 with lots of connections
10978 - fix minor bias in PRNG
10979 - make dirserver more robust to corrupt cached directory
10982 - Wrote the design document (woo)
10984 o Circuit building and exit policies:
10985 - Circuits no longer try to use nodes that the directory has told them
10987 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
10988 bitcounts (18.0.0.0/8).
10989 - Make AP connections standby for a circuit if no suitable circuit
10990 exists, rather than failing
10991 - Circuits choose exit node based on addr/port, exit policies, and
10992 which AP connections are standing by
10993 - Bump min pathlen from 2 to 3
10994 - Relay end cells have a payload to describe why the stream ended.
10995 - If the stream failed because of exit policy, try again with a new
10997 - Clients have a dns cache to remember resolved addresses.
10998 - Notice more quickly when we have no working circuits
11001 - APPort is now called SocksPort
11002 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
11004 - RecommendedVersions is now a config variable rather than
11005 hardcoded (for dirservers)
11006 - Reloads config on HUP
11007 - Usage info on -h or --help
11008 - If you set User and Group config vars, it'll setu/gid to them.
11011 Changes in version 0.0.2pre13 - 2003-10-19
11012 o General stability:
11013 - SSL_write no longer fails when it returns WANTWRITE and the number
11014 of bytes in the buf has changed by the next SSL_write call.
11015 - Fix segfault fetching directory when network is down
11016 - Fix a variety of minor memory leaks
11017 - Dirservers reload the fingerprints file on HUP, so I don't have
11018 to take down the network when I approve a new router
11019 - Default server config file has explicit Address line to specify fqdn
11022 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
11023 - Make listener connections not ever alloc bufs
11025 o Autoconf improvements:
11026 - don't clobber an external CFLAGS in ./configure
11027 - Make install now works
11028 - create var/lib/tor on make install
11029 - autocreate a tor.sh initscript to help distribs
11030 - autocreate the torrc and sample-server-torrc with correct paths
11032 o Log files and Daemonizing now work:
11033 - If --DebugLogFile is specified, log to it at -l debug
11034 - If --LogFile is specified, use it instead of commandline
11035 - If --RunAsDaemon is set, tor forks and backgrounds on startup