1 Changes in version 0.2.3.1-alpha - 2011-05-05
2 Tor 0.2.3.1-alpha adds some new experimental features, including support
3 for an improved network IO backend, IOCP networking on Windows,
4 microdescriptor caching, "fast-start" support for streams, and automatic
5 home router configuration. There are also numerous internal improvements
6 to try to make the code easier for developers to work with.
8 This is the first alpha release in a new series, so expect there to be
9 bugs. Users who would rather test out a more stable branch should
10 stay with 0.2.2.x for now.
13 - Tor can now optionally build with the "bufferevents" buffered IO
14 backend provided by Libevent 2. To use this feature, make sure you
15 have the latest possible version of Libevent, and pass the
16 --enable-bufferevents flag to configure when building Tor from
17 source. This feature will make our networking code more flexible,
18 let us stack layers on each other, and let us use more efficient
19 zero-copy transports where available.
20 - As an experimental feature, Tor can use IOCP for networking on Windows.
21 Once this code is tuned and optimized, it promises much better
22 performance than the select-based backend we've used in the past. To
23 try this feature, you must build Tor with Libevent 2, configure Tor
24 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
25 your torrc. There are known bugs here: only try this if you can help
26 debug it as it breaks.
27 - The EntryNodes option can now include country codes like {de} or IP
28 addresses or network masks. Previously we had disallowed these options
29 because we didn't have an efficient way to keep the list up to
30 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
31 - Exit nodes now accept and queue data on not-yet-connected streams.
32 Previously, the client wasn't allowed to send data until the stream was
33 connected, which slowed down all connections. This change will enable
34 clients to perform a "fast-start" on streams and send data without
35 having to wait for a confirmation that the stream has opened. (Patch
36 from Ian Goldberg; implements the server side of Proposal 174.)
37 - Tor now has initial support for automatic port mapping on the many
38 home routers that support NAT-PMP or UPnP. (Not yet supported on
39 Windows). To build the support code, you'll need to have libnatpnp
40 library and/or the libminiupnpc library, and you'll need to enable the
41 feature specifically by passing "--enable-upnp" and/or
42 "--enable-natpnp" to configure. To turn it on, use the new
43 PortForwarding option.
44 - Caches now download, cache, and serve multiple "flavors" of the
45 consensus, including a flavor that describes microdescriptors.
46 - Caches now download, cache, and serve microdescriptors -- small
47 summaries of router descriptors that are authenticated by all of the
48 directory authorities. Once enough caches are running this code,
49 clients will be able to save significant amounts of directory bandwidth
50 by downloading microdescriptors instead of router descriptors.
53 - Make logging resolution configurable with a new LogGranularity
54 option, and change the default from 1 millisecond to 1
55 second. Implements enhancement 1668.
56 - We log which torrc file we're using on startup. Implements ticket
58 - Ordinarily, Tor does not count traffic from private addresses (like
59 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
60 There is now a new option, CountPrivateBandwidth, to disable this
61 behavior. Patch from Daniel Cagara.
62 - New --enable-static-tor configure option for building Tor as
63 statically as possible. Idea, general hackery and thoughts from
64 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
66 - If you set the NumCPUs option to 0, Tor will now try to detect how
67 many CPUs you have. This is the new default behavior.
68 - Turn on directory request statistics by default and include them in
69 extra-info descriptors. Don't break if we have no GeoIP database.
70 - Relays that set "ConnDirectionStatistics 1" write statistics on the
71 bidirectional use of connections to disk every 24 hours.
72 - Add a GeoIP file digest to the extra-info descriptor. Implements
74 - Add a new 'Heartbeat' log message type to periodically log a message
75 describing Tor's status at level Notice. This feature is meant for
76 operators who log at notice, and want to make sure that their Tor
77 server is still working. Implementation by George Kadianakis.
79 o Minor bugfixes (on 0.2.2.25-alpha):
80 - When loading the microdesc journal, remember its current size.
81 In 0.2.2, this helps prevent the microdesc journal from growing
82 without limit on authorities (who are the only ones to use it in
83 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
84 Fix posted by "cypherpunks."
85 - The microdesc journal is supposed to get rebuilt only if it is
86 at least _half_ the length of the store, not _twice_ the length
87 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
88 - If as an authority we fail to compute the identity digest of a v3
89 legacy keypair, warn, and don't use a buffer-full of junk instead.
90 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
91 - Authorities now clean their microdesc cache periodically and when
92 reading from disk initially, not only when adding new descriptors.
93 This prevents a bug where we could lose microdescriptors. Bugfix
96 o Minor features (controller):
97 - Add a new SIGNAL event to the controller interface so that
98 controllers can be notified when Tor handles a signal. Resolves
99 issue 1955. Patch by John Brooks.
100 - Add a new GETINFO option to get total bytes read and written. Patch
101 from pipe, revised by atagar. Resolves ticket 2345.
102 - Implement some GETINFO controller fields to provide information about
103 the Tor process's pid, euid, username, and resource limits.
106 - Our build system requires automake 1.6 or later to create the
107 Makefile.in files. Previously, you could have used 1.4.
108 This only affects developers and people building Tor from git;
109 people who build Tor from the source distribution without changing
110 the Makefile.am files should be fine.
111 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
112 so on. This is more robust against some of the failure modes
113 associated with running the autotools pieces on their own.
115 o Minor packaging issues:
116 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
117 already created. Patch from Andreas Stieger. Fixes bug 2573.
119 o Code simplifications and refactoring:
120 - A major revision to our internal node-selecting and listing logic.
121 Tor already had at least two major ways to look at the question of
122 "which Tor servers do we know about": a list of router descriptors,
123 and a list of entries in the current consensus. With
124 microdescriptors, we're adding a third. Having so many systems
125 without an abstraction layer over them was hurting the codebase.
126 Now, we have a new "node_t" abstraction that presents a consistent
127 interface to a client's view of a Tor node, and holds (nearly) all
128 of the mutable state formerly in routerinfo_t and routerstatus_t.
129 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
130 no longer link against Libevent: they never used it, but
131 our library structure used to force them to link it.
134 - Remove some old code to work around even older versions of Tor that
135 used forked processes to handle DNS requests. Such versions of Tor
136 are no longer in use as servers.
138 o Documentation fixes:
139 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
140 - Add missing documentation for the authority-related torrc options
141 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
145 Changes in version 0.2.2.27-beta - 2011-05-18
146 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
147 release, and also adds a few more general bugfixes.
150 - Fix a crash bug when changing bridges in a running Tor process.
151 Fixes bug 3213; bugfix on 0.2.2.26-beta.
152 - When the controller configures a new bridge, don't wait 10 to 60
153 seconds before trying to fetch its descriptor. Bugfix on
154 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
157 - Require that onion keys have exponent 65537 in microdescriptors too.
158 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
159 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
160 Changed the limit to 512 characters by removing base64 newlines.
161 Fixes bug 2752. Fix by Michael Yakubovich.
162 - When a client starts or stops using bridges, never use a circuit
163 that was built before the configuration change. This behavior could
164 put at risk a user who uses bridges to ensure that her traffic
165 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
169 Changes in version 0.2.2.26-beta - 2011-05-17
170 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
171 also introduces a new "socksport auto" approach that should make it
172 easier to run multiple Tors on the same system, and does a lot of
173 cleanup to get us closer to a release candidate.
175 o Security/privacy fixes:
176 - Replace all potentially sensitive memory comparison operations
177 with versions whose runtime does not depend on the data being
178 compared. This will help resist a class of attacks where an
179 adversary can use variations in timing information to learn
180 sensitive data. Fix for one case of bug 3122. (Safe memcmp
181 implementation by Robert Ransom based partially on code by DJB.)
182 - When receiving a hidden service descriptor, check that it is for
183 the hidden service we wanted. Previously, Tor would store any
184 hidden service descriptors that a directory gave it, whether it
185 wanted them or not. This wouldn't have let an attacker impersonate
186 a hidden service, but it did let directories pre-seed a client
187 with descriptors that it didn't want. Bugfix on 0.0.6.
188 - On SIGHUP, do not clear out all TrackHostExits mappings, client
189 DNS cache entries, and virtual address mappings: that's what
190 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
193 - The options SocksPort, ControlPort, and so on now all accept a
194 value "auto" that opens a socket on an OS-selected port. A
195 new ControlPortWriteToFile option tells Tor to write its
196 actual control port or ports to a chosen file. If the option
197 ControlPortFileGroupReadable is set, the file is created as
198 group-readable. Now users can run two Tor clients on the same
199 system without needing to manually mess with parameters. Resolves
201 - Set SO_REUSEADDR on all sockets, not just listeners. This should
202 help busy exit nodes avoid running out of useable ports just
203 because all the ports have been used in the near past. Resolves
207 - New "GETINFO net/listeners/(type)" controller command to return
208 a list of addresses and ports that are bound for listeners for a
209 given connection type. This is useful when the user has configured
210 "SocksPort auto" and the controller needs to know which port got
211 chosen. Resolves another part of ticket 3076.
212 - Add a new ControlSocketsGroupWritable configuration option: when
213 it is turned on, ControlSockets are group-writeable by the default
214 group of the current user. Patch by Jérémy Bobbio; implements
216 - Tor now refuses to create a ControlSocket in a directory that is
217 world-readable (or group-readable if ControlSocketsGroupWritable
218 is 0). This is necessary because some operating systems do not
219 enforce permissions on an AF_UNIX sockets. Permissions on the
220 directory holding the socket, however, seems to work everywhere.
221 - Rate-limit a warning about failures to download v2 networkstatus
222 documents. Resolves part of bug 1352.
223 - Backport code from 0.2.3.x that allows directory authorities to
224 clean their microdescriptor caches. Needed to resolve bug 2230.
225 - When an HTTPS proxy reports "403 Forbidden", we now explain
226 what it means rather than calling it an unexpected status code.
227 Closes bug 2503. Patch from Michael Yakubovich.
228 - Update to the May 1 2011 Maxmind GeoLite Country database.
231 - Authorities now clean their microdesc cache periodically and when
232 reading from disk initially, not only when adding new descriptors.
233 This prevents a bug where we could lose microdescriptors. Bugfix
234 on 0.2.2.6-alpha. 2230
235 - Do not crash when our configuration file becomes unreadable, for
236 example due to a permissions change, between when we start up
237 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
239 - Avoid a bug that would keep us from replacing a microdescriptor
240 cache on Windows. (We would try to replace the file while still
241 holding it open. That's fine on Unix, but Windows doesn't let us
242 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
243 - Add missing explanations for the authority-related torrc options
244 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
245 man page. Resolves issue 2379.
246 - As an authority, do not upload our own vote or signature set to
247 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
248 it would get flagged as a duplicate. Resolves bug 3026.
249 - Accept hidden service descriptors if we think we might be a hidden
250 service directory, regardless of what our consensus says. This
251 helps robustness, since clients and hidden services can sometimes
252 have a more up-to-date view of the network consensus than we do,
253 and if they think that the directory authorities list us a HSDir,
254 we might actually be one. Related to bug 2732; bugfix on
256 - When a controller changes TrackHostExits, remove mappings for
257 hosts that should no longer have their exits tracked. Bugfix on
259 - When a controller changes VirtualAddrNetwork, remove any mappings
260 for hosts that were automapped to the old network. Bugfix on
262 - When a controller changes one of the AutomapHosts* options, remove
263 any mappings for hosts that should no longer be automapped. Bugfix
265 - Do not reset the bridge descriptor download status every time we
266 re-parse our configuration or get a configuration change. Fixes
267 bug 3019; bugfix on 0.2.0.3-alpha.
269 o Minor bugfixes (code cleanup):
270 - When loading the microdesc journal, remember its current size.
271 In 0.2.2, this helps prevent the microdesc journal from growing
272 without limit on authorities (who are the only ones to use it in
273 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
274 Fix posted by "cypherpunks."
275 - The microdesc journal is supposed to get rebuilt only if it is
276 at least _half_ the length of the store, not _twice_ the length
277 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
278 - Fix a potential null-pointer dereference while computing a
279 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
281 - Avoid a possible null-pointer dereference when rebuilding the mdesc
282 cache without actually having any descriptors to cache. Bugfix on
283 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
284 - If we fail to compute the identity digest of a v3 legacy keypair,
285 warn, and don't use a buffer-full of junk instead. Bugfix on
286 0.2.1.1-alpha; fixes bug 3106.
287 - Resolve an untriggerable issue in smartlist_string_num_isin(),
288 where if the function had ever in the future been used to check
289 for the presence of a too-large number, it would have given an
290 incorrect result. (Fortunately, we only used it for 16-bit
291 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
292 - Require that introduction point keys and onion handshake keys
293 have a public exponent of 65537. Starts to fix bug 3207; bugfix
297 - Caches no longer download and serve v2 networkstatus documents
298 unless FetchV2Networkstatus flag is set: these documents haven't
299 haven't been used by clients or relays since 0.2.0.x. Resolves
303 Changes in version 0.2.2.25-alpha - 2011-04-29
304 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
305 robust, routers no longer overreport their bandwidth, Win7 should crash
306 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
307 now prevents hidden service-related activity from being linkable. It
308 provides more information to Vidalia so you can see if your bridge is
309 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
310 StrictNodes configuration options to make them more reliable, more
311 understandable, and more regularly applied. If you use those options,
312 please see the revised documentation for them in the manual page.
315 - Relays were publishing grossly inflated bandwidth values because
316 they were writing their state files wrong--now they write the
317 correct value. Also, resume reading bandwidth history from the
318 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
319 - Improve hidden service robustness: When we find that we have
320 extended a hidden service's introduction circuit to a relay not
321 listed as an introduction point in the HS descriptor we currently
322 have, retry with an introduction point from the current
323 descriptor. Previously we would just give up. Fixes bugs 1024 and
324 1930; bugfix on 0.2.0.10-alpha.
325 - Clients now stop trying to use an exit node associated with a given
326 destination by TrackHostExits if they fail to reach that exit node.
327 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
328 - Fix crash bug on platforms where gmtime and localtime can return
329 NULL. Windows 7 users were running into this one. Fixes part of bug
330 2077. Bugfix on all versions of Tor. Found by boboper.
332 o Security and stability fixes:
333 - Don't double-free a parsable, but invalid, microdescriptor, even if
334 it is followed in the blob we're parsing by an unparsable
335 microdescriptor. Fixes an issue reported in a comment on bug 2954.
336 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
337 - If the Nickname configuration option isn't given, Tor would pick a
338 nickname based on the local hostname as the nickname for a relay.
339 Because nicknames are not very important in today's Tor and the
340 "Unnamed" nickname has been implemented, this is now problematic
341 behavior: It leaks information about the hostname without being
342 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
343 introduced the Unnamed nickname. Reported by tagnaq.
344 - Fix an uncommon assertion failure when running with DNSPort under
345 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
346 - Avoid linkability based on cached hidden service descriptors: forget
347 all hidden service descriptors cached as a client when processing a
348 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
351 - Export GeoIP information on bridge usage to controllers even if we
352 have not yet been running for 24 hours. Now Vidalia bridge operators
353 can get more accurate and immediate feedback about their
354 contributions to the network.
356 o Major features and bugfixes (node selection):
357 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
358 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
359 options. Previously, we had been ambiguous in describing what
360 counted as an "exit" node, and what operations exactly "StrictNodes
361 0" would permit. This created confusion when people saw nodes built
362 through unexpected circuits, and made it hard to tell real bugs from
363 surprises. Now the intended behavior is:
364 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
365 a node that delivers user traffic outside the Tor network.
366 . "Entry", in the context of EntryNodes, means a node used as the
367 first hop of a multihop circuit. It doesn't include direct
368 connections to directory servers.
369 . "ExcludeNodes" applies to all nodes.
370 . "StrictNodes" changes the behavior of ExcludeNodes only. When
371 StrictNodes is set, Tor should avoid all nodes listed in
372 ExcludeNodes, even when it will make user requests fail. When
373 StrictNodes is *not* set, then Tor should follow ExcludeNodes
374 whenever it can, except when it must use an excluded node to
375 perform self-tests, connect to a hidden service, provide a
376 hidden service, fulfill a .exit request, upload directory
377 information, or fetch directory information.
378 Collectively, the changes to implement the behavior fix bug 1090.
379 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
380 a node is listed in both, it's treated as excluded.
381 - ExcludeNodes now applies to directory nodes -- as a preference if
382 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
383 Don't exclude all the directory authorities and set StrictNodes to 1
384 unless you really want your Tor to break.
385 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
386 - ExcludeExitNodes now overrides .exit requests.
387 - We don't use bridges listed in ExcludeNodes.
388 - When StrictNodes is 1:
389 . We now apply ExcludeNodes to hidden service introduction points
390 and to rendezvous points selected by hidden service users. This
391 can make your hidden service less reliable: use it with caution!
392 . If we have used ExcludeNodes on ourself, do not try relay
393 reachability self-tests.
394 . If we have excluded all the directory authorities, we will not
395 even try to upload our descriptor if we're a relay.
396 . Do not honor .exit requests to an excluded node.
397 - Remove a misfeature that caused us to ignore the Fast/Stable flags
398 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
399 - When the set of permitted nodes changes, we now remove any mappings
400 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
402 - We never cannibalize a circuit that had excluded nodes on it, even
403 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
404 - Revert a change where we would be laxer about attaching streams to
405 circuits than when building the circuits. This was meant to prevent
406 a set of bugs where streams were never attachable, but our improved
407 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
408 - Keep track of how many times we launch a new circuit to handle a
409 given stream. Too many launches could indicate an inconsistency
410 between our "launch a circuit to handle this stream" logic and our
411 "attach this stream to one of the available circuits" logic.
412 - Improve log messages related to excluded nodes.
415 - Fix a spurious warning when moving from a short month to a long
416 month on relays with month-based BandwidthAccounting. Bugfix on
417 0.2.2.17-alpha; fixes bug 3020.
418 - When a client finds that an origin circuit has run out of 16-bit
419 stream IDs, we now mark it as unusable for new streams. Previously,
420 we would try to close the entire circuit. Bugfix on 0.0.6.
421 - Add a forgotten cast that caused a compile warning on OS X 10.6.
422 Bugfix on 0.2.2.24-alpha.
423 - Be more careful about reporting the correct error from a failed
424 connect() system call. Under some circumstances, it was possible to
425 look at an incorrect value for errno when sending the end reason.
426 Bugfix on 0.1.0.1-rc.
427 - Correctly handle an "impossible" overflow cases in connection byte
428 counting, where we write or read more than 4GB on an edge connection
429 in a single second. Bugfix on 0.1.2.8-beta.
430 - Correct the warning displayed when a rendezvous descriptor exceeds
431 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
433 - Clients and hidden services now use HSDir-flagged relays for hidden
434 service descriptor downloads and uploads even if the relays have no
435 DirPort set and the client has disabled TunnelDirConns. This will
436 eventually allow us to give the HSDir flag to relays with no
437 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
438 - Downgrade "no current certificates known for authority" message from
439 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
440 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
441 2917. Bugfix on 0.1.1.1-alpha.
442 - Only limit the lengths of single HS descriptors, even when multiple
443 HS descriptors are published to an HSDir relay in a single POST
444 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
445 - Write the current time into the LastWritten line in our state file,
446 rather than the time from the previous write attempt. Also, stop
447 trying to use a time of -1 in our log statements. Fixes bug 3039;
448 bugfix on 0.2.2.14-alpha.
449 - Be more consistent in our treatment of file system paths. "~" should
450 get expanded to the user's home directory in the Log config option.
451 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
452 feature for the -f and --DataDirectory options.
455 - Make sure every relay writes a state file at least every 12 hours.
456 Previously, a relay could go for weeks without writing its state
457 file, and on a crash could lose its bandwidth history, capacity
458 estimates, client country statistics, and so on. Addresses bug 3012.
459 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
460 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
461 clients are already deprecated because of security bugs.
462 - Don't allow v0 hidden service authorities to act as clients.
463 Required by fix for bug 3000.
464 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
466 - Ensure that no empty [dirreq-](read|write)-history lines are added
467 to an extrainfo document. Implements ticket 2497.
469 o Code simplification and refactoring:
470 - Remove workaround code to handle directory responses from servers
471 that had bug 539 (they would send HTTP status 503 responses _and_
472 send a body too). Since only server versions before
473 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
474 keep the workaround in place.
475 - Remove the old 'fuzzy time' logic. It was supposed to be used for
476 handling calculations where we have a known amount of clock skew and
477 an allowed amount of unknown skew. But we only used it in three
478 places, and we never adjusted the known/unknown skew values. This is
479 still something we might want to do someday, but if we do, we'll
480 want to do it differently.
481 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
482 None of the cases where we did this before were wrong, but by making
483 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
484 - Use GetTempDir to find the proper temporary directory location on
485 Windows when generating temporary files for the unit tests. Patch by
489 Changes in version 0.2.2.24-alpha - 2011-04-08
490 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
491 prevented Tor clients from effectively using "multihomed" bridges,
492 that is, bridges that listen on multiple ports or IP addresses so users
493 can continue to use some of their addresses even if others get blocked.
496 - Fix a bug where bridge users who configure the non-canonical
497 address of a bridge automatically switch to its canonical
498 address. If a bridge listens at more than one address, it should be
499 able to advertise those addresses independently and any non-blocked
500 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
502 - If you configured Tor to use bridge A, and then quit and
503 configured Tor to use bridge B instead, it would happily continue
504 to use bridge A if it's still reachable. While this behavior is
505 a feature if your goal is connectivity, in some scenarios it's a
506 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
507 - Directory authorities now use data collected from their own
508 uptime observations when choosing whether to assign the HSDir flag
509 to relays, instead of trusting the uptime value the relay reports in
510 its descriptor. This change helps prevent an attack where a small
511 set of nodes with frequently-changing identity keys can blackhole
512 a hidden service. (Only authorities need upgrade; others will be
513 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
516 - When we restart our relay, we might get a successful connection
517 from the outside before we've started our reachability tests,
518 triggering a warning: "ORPort found reachable, but I have no
519 routerinfo yet. Failing to inform controller of success." This
520 bug was harmless unless Tor is running under a controller
521 like Vidalia, in which case the controller would never get a
522 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
524 - Make directory authorities more accurate at recording when
525 relays that have failed several reachability tests became
526 unreachable, so we can provide more accuracy at assigning Stable,
527 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
528 - Fix an issue that prevented static linking of libevent on
529 some platforms (notably Linux). Fixes bug 2698; bugfix on
530 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
531 the --with-static-libevent configure option).
532 - We now ask the other side of a stream (the client or the exit)
533 for more data on that stream when the amount of queued data on
534 that stream dips low enough. Previously, we wouldn't ask the
535 other side for more data until either it sent us more data (which
536 it wasn't supposed to do if it had exhausted its window!) or we
537 had completely flushed all our queued data. This flow control fix
538 should improve throughput. Fixes bug 2756; bugfix on the earliest
539 released versions of Tor (svn commit r152).
540 - Avoid a double-mark-for-free warning when failing to attach a
541 transparent proxy connection. (We thought we had fixed this in
542 0.2.2.23-alpha, but it turns out our fix was checking the wrong
543 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
544 bug) and 0.2.2.23-alpha (the incorrect fix).
545 - When warning about missing zlib development packages during compile,
546 give the correct package names. Bugfix on 0.2.0.1-alpha.
549 - Directory authorities now log the source of a rejected POSTed v3
551 - Make compilation with clang possible when using
552 --enable-gcc-warnings by removing two warning optionss that clang
553 hasn't implemented yet and by fixing a few warnings. Implements
555 - When expiring circuits, use microsecond timers rather than
556 one-second timers. This can avoid an unpleasant situation where a
557 circuit is launched near the end of one second and expired right
558 near the beginning of the next, and prevent fluctuations in circuit
560 - Use computed circuit-build timeouts to decide when to launch
561 parallel introduction circuits for hidden services. (Previously,
562 we would retry after 15 seconds.)
563 - Update to the April 1 2011 Maxmind GeoLite Country database.
566 - Create the /var/run/tor directory on startup on OpenSUSE if it is
567 not already created. Patch from Andreas Stieger. Fixes bug 2573.
569 o Documentation changes:
570 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
571 - Resolve all doxygen warnings except those for missing documentation.
573 - Add doxygen documentation for more functions, fields, and types.
576 Changes in version 0.2.2.23-alpha - 2011-03-08
577 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
578 they restart they don't lose their bandwidth capacity estimate. This
579 release also fixes a diverse set of user-facing bugs, ranging from
580 relays overrunning their rate limiting to clients falsely warning about
581 clock skew to bridge descriptor leaks by our bridge directory authority.
584 - Stop sending a CLOCK_SKEW controller status event whenever
585 we fetch directory information from a relay that has a wrong clock.
586 Instead, only inform the controller when it's a trusted authority
587 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
588 the rest of bug 1074.
589 - Fix an assert in parsing router descriptors containing IPv6
590 addresses. This one took down the directory authorities when
591 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
592 - Make the bridge directory authority refuse to answer directory
593 requests for "all" descriptors. It used to include bridge
594 descriptors in its answer, which was a major information leak.
595 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
596 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
597 Tor would ignore their RelayBandwidthBurst setting,
598 potentially using more bandwidth than expected. Bugfix on
599 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
600 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
601 hidserv" in her torrc. The 'hidserv' argument never controlled
602 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
605 - Relays now save observed peak bandwidth throughput rates to their
606 state file (along with total usage, which was already saved)
607 so that they can determine their correct estimated bandwidth on
608 restart. Resolves bug 1863, where Tor relays would reset their
609 estimated bandwidth to 0 after restarting.
610 - Directory authorities now take changes in router IP address and
611 ORPort into account when determining router stability. Previously,
612 if a router changed its IP or ORPort, the authorities would not
613 treat it as having any downtime for the purposes of stability
614 calculation, whereas clients would experience downtime since the
615 change could take a while to propagate to them. Resolves issue 1035.
616 - Enable Address Space Layout Randomization (ASLR) and Data Execution
617 Prevention (DEP) by default on Windows to make it harder for
618 attackers to exploit vulnerabilities. Patch from John Brooks.
620 o Minor bugfixes (on 0.2.1.x and earlier):
621 - Fix a rare crash bug that could occur when a client was configured
622 with a large number of bridges. Fixes bug 2629; bugfix on
623 0.2.1.2-alpha. Bugfix by trac user "shitlei".
624 - Avoid a double mark-for-free warning when failing to attach a
625 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
627 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
628 found by "cypherpunks". This bug was introduced before the first
629 Tor release, in svn commit r110.
630 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
631 don't mention them in the manpage. Fixes bug 2450; issue
632 spotted by keb and G-Lo.
633 - Fix a bug in bandwidth history state parsing that could have been
634 triggered if a future version of Tor ever changed the timing
635 granularity at which bandwidth history is measured. Bugfix on
637 - When a relay decides that its DNS is too broken for it to serve
638 as an exit server, it advertised itself as a non-exit, but
639 continued to act as an exit. This could create accidental
640 partitioning opportunities for users. Instead, if a relay is
641 going to advertise reject *:* as its exit policy, it should
642 really act with exit policy "reject *:*". Fixes bug 2366.
643 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
644 - In the special case where you configure a public exit relay as your
645 bridge, Tor would be willing to use that exit relay as the last
646 hop in your circuit as well. Now we fail that circuit instead.
647 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
648 - Fix a bug with our locking implementation on Windows that couldn't
649 correctly detect when a file was already locked. Fixes bug 2504,
650 bugfix on 0.2.1.6-alpha.
651 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
652 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
654 - Set target port in get_interface_address6() correctly. Bugfix
655 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
656 - Directory authorities are now more robust to hops back in time
657 when calculating router stability. Previously, if a run of uptime
658 or downtime appeared to be negative, the calculation could give
659 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
661 - Fix an assert that got triggered when using the TestingTorNetwork
662 configuration option and then issuing a GETINFO config-text control
663 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
665 o Minor bugfixes (on 0.2.2.x):
666 - Clients should not weight BadExit nodes as Exits in their node
667 selection. Similarly, directory authorities should not count BadExit
668 bandwidth as Exit bandwidth when computing bandwidth-weights.
669 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
670 - Correctly clear our dir_read/dir_write history when there is an
671 error parsing any bw history value from the state file. Bugfix on
673 - Resolve a bug in verifying signatures of directory objects
674 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
675 Fixes bug 2409. Found by "piebeer".
676 - Bridge authorities no longer crash on SIGHUP when they try to
677 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
681 - Log less aggressively about circuit timeout changes, and improve
682 some other circuit timeout messages. Resolves bug 2004.
683 - Log a little more clearly about the times at which we're no longer
684 accepting new connections. Resolves bug 2181.
685 - Reject attempts at the client side to open connections to private
686 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
687 a randomly chosen exit node. Attempts to do so are always
688 ill-defined, generally prevented by exit policies, and usually
689 in error. This will also help to detect loops in transparent
690 proxy configurations. You can disable this feature by setting
691 "ClientRejectInternalAddresses 0" in your torrc.
692 - Always treat failure to allocate an RSA key as an unrecoverable
694 - Update to the March 1 2011 Maxmind GeoLite Country database.
696 o Minor features (log subsystem):
697 - Add documentation for configuring logging at different severities in
698 different log domains. We've had this feature since 0.2.1.1-alpha,
699 but for some reason it never made it into the manpage. Fixes
701 - Make it simpler to specify "All log domains except for A and B".
702 Previously you needed to say "[*,~A,~B]". Now you can just say
704 - Add a "LogMessageDomains 1" option to include the domains of log
705 messages along with the messages. Without this, there's no way
706 to use log domains without reading the source or doing a lot
710 - Stop shipping the Tor specs files and development proposal documents
711 in the tarball. They are now in a separate git repository at
712 git://git.torproject.org/torspec.git
715 Changes in version 0.2.2.22-alpha - 2011-01-25
716 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
717 main other change is a slight tweak to Tor's TLS handshake that makes
718 relays and bridges that run this new version reachable from Iran again.
719 We don't expect this tweak will win the arms race long-term, but it
720 will buy us a bit more time until we roll out a better solution.
723 - Fix a bounds-checking error that could allow an attacker to
724 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
726 - Don't assert when changing from bridge to relay or vice versa
727 via the controller. The assert happened because we didn't properly
728 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
729 bug 2433. Reported by bastik.
732 - Adjust our TLS Diffie-Hellman parameters to match those used by
734 - Provide a log message stating which geoip file we're parsing
735 instead of just stating that we're parsing the geoip file.
736 Implements ticket 2432.
739 - Check for and reject overly long directory certificates and
740 directory tokens before they have a chance to hit any assertions.
741 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
744 Changes in version 0.2.2.21-alpha - 2011-01-15
745 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
746 continues our recent code security audit work. The main fix resolves
747 a remote heap overflow vulnerability that can allow remote code
748 execution (CVE-2011-0427). Other fixes address a variety of assert
749 and crash bugs, most of which we think are hard to exploit remotely.
751 o Major bugfixes (security), also included in 0.2.1.29:
752 - Fix a heap overflow bug where an adversary could cause heap
753 corruption. This bug probably allows remote code execution
754 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
756 - Prevent a denial-of-service attack by disallowing any
757 zlib-compressed data whose compression factor is implausibly
758 high. Fixes part of bug 2324; reported by "doorss".
759 - Zero out a few more keys in memory before freeing them. Fixes
760 bug 2384 and part of bug 2385. These key instances found by
761 "cypherpunks", based on Andrew Case's report about being able
762 to find sensitive data in Tor's memory space if you have enough
763 permissions. Bugfix on 0.0.2pre9.
765 o Major bugfixes (crashes), also included in 0.2.1.29:
766 - Prevent calls to Libevent from inside Libevent log handlers.
767 This had potential to cause a nasty set of crashes, especially
768 if running Libevent with debug logging enabled, and running
769 Tor with a controller watching for low-severity log messages.
770 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
771 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
772 underflow errors there too. Fixes the other part of bug 2324.
773 - Fix a bug where we would assert if we ever had a
774 cached-descriptors.new file (or another file read directly into
775 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
776 on 0.2.1.25. Found by doorss.
777 - Fix some potential asserts and parsing issues with grossly
778 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
781 o Minor bugfixes (other), also included in 0.2.1.29:
782 - Fix a bug with handling misformed replies to reverse DNS lookup
783 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
784 bug reported by doorss.
785 - Fix compilation on mingw when a pthreads compatibility library
786 has been installed. (We don't want to use it, so we shouldn't
787 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
788 - Fix a bug where we would declare that we had run out of virtual
789 addresses when the address space was only half-exhausted. Bugfix
791 - Correctly handle the case where AutomapHostsOnResolve is set but
792 no virtual addresses are available. Fixes bug 2328; bugfix on
793 0.1.2.1-alpha. Bug found by doorss.
794 - Correctly handle wrapping around when we run out of virtual
795 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
797 o Minor features, also included in 0.2.1.29:
798 - Update to the January 1 2011 Maxmind GeoLite Country database.
799 - Introduce output size checks on all of our decryption functions.
801 o Build changes, also included in 0.2.1.29:
802 - Tor does not build packages correctly with Automake 1.6 and earlier;
803 added a check to Makefile.am to make sure that we're building with
804 Automake 1.7 or later.
805 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
806 because we built it with a too-old version of automake. Thus that
807 release broke ./configure --enable-openbsd-malloc, which is popular
808 among really fast exit relays on Linux.
810 o Major bugfixes, new in 0.2.2.21-alpha:
811 - Prevent crash/heap corruption when the cbtnummodes consensus
812 parameter is set to 0 or large values. Fixes bug 2317; bugfix
815 o Major features, new in 0.2.2.21-alpha:
816 - Introduce minimum/maximum values that clients will believe
817 from the consensus. Now we'll have a better chance to avoid crashes
818 or worse when a consensus param has a weird value.
820 o Minor features, new in 0.2.2.21-alpha:
821 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
822 used on bridges, and it makes bridge scanning somewhat easier.
823 - If writing the state file to disk fails, wait up to an hour before
824 retrying again, rather than trying again each second. Fixes bug
825 2346; bugfix on Tor 0.1.1.3-alpha.
826 - Make Libevent log messages get delivered to controllers later,
827 and not from inside the Libevent log handler. This prevents unsafe
828 reentrant Libevent calls while still letting the log messages
830 - Detect platforms that brokenly use a signed size_t, and refuse to
831 build there. Found and analyzed by doorss and rransom.
832 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
835 o Minor bugfixes, new in 0.2.2.21-alpha:
836 - Handle SOCKS messages longer than 128 bytes long correctly, rather
837 than waiting forever for them to finish. Fixes bug 2330; bugfix
838 on 0.2.0.16-alpha. Found by doorss.
839 - Add assertions to check for overflow in arguments to
840 base32_encode() and base32_decode(); fix a signed-unsigned
841 comparison there too. These bugs are not actually reachable in Tor,
842 but it's good to prevent future errors too. Found by doorss.
843 - Correctly detect failures to create DNS requests when using Libevent
844 versions before v2. (Before Libevent 2, we used our own evdns
845 implementation. Its return values for Libevent's evdns_resolve_*()
846 functions are not consistent with those from Libevent.) Fixes bug
847 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
849 o Documentation, new in 0.2.2.21-alpha:
850 - Document the default socks host and port (127.0.0.1:9050) for
854 Changes in version 0.2.1.29 - 2011-01-15
855 Tor 0.2.1.29 continues our recent code security audit work. The main
856 fix resolves a remote heap overflow vulnerability that can allow remote
857 code execution. Other fixes address a variety of assert and crash bugs,
858 most of which we think are hard to exploit remotely.
860 o Major bugfixes (security):
861 - Fix a heap overflow bug where an adversary could cause heap
862 corruption. This bug probably allows remote code execution
863 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
865 - Prevent a denial-of-service attack by disallowing any
866 zlib-compressed data whose compression factor is implausibly
867 high. Fixes part of bug 2324; reported by "doorss".
868 - Zero out a few more keys in memory before freeing them. Fixes
869 bug 2384 and part of bug 2385. These key instances found by
870 "cypherpunks", based on Andrew Case's report about being able
871 to find sensitive data in Tor's memory space if you have enough
872 permissions. Bugfix on 0.0.2pre9.
874 o Major bugfixes (crashes):
875 - Prevent calls to Libevent from inside Libevent log handlers.
876 This had potential to cause a nasty set of crashes, especially
877 if running Libevent with debug logging enabled, and running
878 Tor with a controller watching for low-severity log messages.
879 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
880 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
881 underflow errors there too. Fixes the other part of bug 2324.
882 - Fix a bug where we would assert if we ever had a
883 cached-descriptors.new file (or another file read directly into
884 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
885 on 0.2.1.25. Found by doorss.
886 - Fix some potential asserts and parsing issues with grossly
887 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
890 o Minor bugfixes (other):
891 - Fix a bug with handling misformed replies to reverse DNS lookup
892 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
893 bug reported by doorss.
894 - Fix compilation on mingw when a pthreads compatibility library
895 has been installed. (We don't want to use it, so we shouldn't
896 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
897 - Fix a bug where we would declare that we had run out of virtual
898 addresses when the address space was only half-exhausted. Bugfix
900 - Correctly handle the case where AutomapHostsOnResolve is set but
901 no virtual addresses are available. Fixes bug 2328; bugfix on
902 0.1.2.1-alpha. Bug found by doorss.
903 - Correctly handle wrapping around to when we run out of virtual
904 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
905 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
906 because we built it with a too-old version of automake. Thus that
907 release broke ./configure --enable-openbsd-malloc, which is popular
908 among really fast exit relays on Linux.
911 - Update to the January 1 2011 Maxmind GeoLite Country database.
912 - Introduce output size checks on all of our decryption functions.
915 - Tor does not build packages correctly with Automake 1.6 and earlier;
916 added a check to Makefile.am to make sure that we're building with
917 Automake 1.7 or later.
920 Changes in version 0.2.2.20-alpha - 2010-12-17
921 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
922 exploitable bugs. We also fix a variety of other significant bugs,
923 change the IP address for one of our directory authorities, and update
924 the minimum version that Tor relays must run to join the network.
927 - Fix a remotely exploitable bug that could be used to crash instances
928 of Tor remotely by overflowing on the heap. Remote-code execution
929 hasn't been confirmed, but can't be ruled out. Everyone should
930 upgrade. Bugfix on the 0.1.1 series and later.
931 - Fix a bug that could break accounting on 64-bit systems with large
932 time_t values, making them hibernate for impossibly long intervals.
933 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
934 - Fix a logic error in directory_fetches_from_authorities() that
935 would cause all _non_-exits refusing single-hop-like circuits
936 to fetch from authorities, when we wanted to have _exits_ fetch
937 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
939 - Fix a stream fairness bug that would cause newer streams on a given
940 circuit to get preference when reading bytes from the origin or
941 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
942 introduced before the first Tor release, in svn revision r152.
944 o Directory authority changes:
945 - Change IP address and ports for gabelmoo (v3 directory authority).
948 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
949 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
950 - Fix an off-by-one error in calculating some controller command
951 argument lengths. Fortunately, this mistake is harmless since
952 the controller code does redundant NUL termination too. Found by
953 boboper. Bugfix on 0.1.1.1-alpha.
954 - Do not dereference NULL if a bridge fails to build its
955 extra-info descriptor. Found by an anonymous commenter on
956 Trac. Bugfix on 0.2.2.19-alpha.
959 - Update to the December 1 2010 Maxmind GeoLite Country database.
960 - Directory authorities now reject relays running any versions of
961 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
962 known bugs that keep RELAY_EARLY cells from working on rendezvous
963 circuits. Followup to fix for bug 2081.
964 - Directory authorities now reject relays running any version of Tor
965 older than 0.2.0.26-rc. That version is the earliest that fetches
966 current directory information correctly. Fixes bug 2156.
967 - Report only the top 10 ports in exit-port stats in order not to
968 exceed the maximum extra-info descriptor length of 50 KB. Implements
972 Changes in version 0.2.1.28 - 2010-12-17
973 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
974 exploitable bugs. We also took this opportunity to change the IP address
975 for one of our directory authorities, and to update the geoip database
979 - Fix a remotely exploitable bug that could be used to crash instances
980 of Tor remotely by overflowing on the heap. Remote-code execution
981 hasn't been confirmed, but can't be ruled out. Everyone should
982 upgrade. Bugfix on the 0.1.1 series and later.
984 o Directory authority changes:
985 - Change IP address and ports for gabelmoo (v3 directory authority).
988 - Update to the December 1 2010 Maxmind GeoLite Country database.
991 Changes in version 0.2.1.27 - 2010-11-23
992 Yet another OpenSSL security patch broke its compatibility with Tor:
993 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
994 also took this opportunity to fix several crash bugs, integrate a new
995 directory authority, and update the bundled GeoIP database.
998 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
999 No longer set the tlsext_host_name extension on server SSL objects;
1000 but continue to set it on client SSL objects. Our goal in setting
1001 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
1002 bugfix on 0.2.1.1-alpha.
1003 - Do not log messages to the controller while shrinking buffer
1004 freelists. Doing so would sometimes make the controller connection
1005 try to allocate a buffer chunk, which would mess up the internals
1006 of the freelist and cause an assertion failure. Fixes bug 1125;
1007 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
1008 - Learn our external IP address when we're a relay or bridge, even if
1009 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
1010 where we introduced bridge relays that don't need to publish to
1011 be useful. Fixes bug 2050.
1012 - Do even more to reject (and not just ignore) annotations on
1013 router descriptors received anywhere but from the cache. Previously
1014 we would ignore such annotations at first, but cache them to disk
1015 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
1016 - When you're using bridges and your network goes away and your
1017 bridges get marked as down, recover when you attempt a new socks
1018 connection (if the network is back), rather than waiting up to an
1019 hour to try fetching new descriptors for your bridges. Bugfix on
1020 0.2.0.3-alpha; fixes bug 1981.
1023 - Move to the November 2010 Maxmind GeoLite country db (rather
1024 than the June 2009 ip-to-country GeoIP db) for our statistics that
1025 count how many users relays are seeing from each country. Now we'll
1026 have more accurate data, especially for many African countries.
1028 o New directory authorities:
1029 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
1033 - Fix an assertion failure that could occur in directory caches or
1034 bridge users when using a very short voting interval on a testing
1035 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
1037 - Enforce multiplicity rules when parsing annotations. Bugfix on
1038 0.2.0.8-alpha. Found by piebeer.
1039 - Allow handshaking OR connections to take a full KeepalivePeriod
1040 seconds to handshake. Previously, we would close them after
1041 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
1042 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
1044 - When building with --enable-gcc-warnings on OpenBSD, disable
1045 warnings in system headers. This makes --enable-gcc-warnings
1046 pass on OpenBSD 4.8.
1049 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
1050 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
1051 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
1052 Servers can start sending this code when enough clients recognize
1053 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
1054 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
1055 Patch from mingw-san.
1058 - Remove the old debian/ directory from the main Tor distribution.
1059 The official Tor-for-debian git repository lives at the URL
1060 https://git.torproject.org/debian/tor.git
1061 - Stop shipping the old doc/website/ directory in the tarball. We
1062 changed the website format in late 2010, and what we shipped in
1063 0.2.1.26 really wasn't that useful anyway.
1066 Changes in version 0.2.2.19-alpha - 2010-11-22
1067 Yet another OpenSSL security patch broke its compatibility with Tor:
1068 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
1071 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
1072 No longer set the tlsext_host_name extension on server SSL objects;
1073 but continue to set it on client SSL objects. Our goal in setting
1074 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
1075 bugfix on 0.2.1.1-alpha.
1078 - Try harder not to exceed the maximum length of 50 KB when writing
1079 statistics to extra-info descriptors. This bug was triggered by very
1080 fast relays reporting exit-port, entry, and dirreq statistics.
1081 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
1082 - Publish a router descriptor even if generating an extra-info
1083 descriptor fails. Previously we would not publish a router
1084 descriptor without an extra-info descriptor; this can cause fast
1085 exit relays collecting exit-port statistics to drop from the
1086 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
1089 Changes in version 0.2.2.18-alpha - 2010-11-16
1090 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
1091 us lately, makes unpublished bridge relays able to detect their IP
1092 address, and fixes a wide variety of other bugs to get us much closer
1093 to a stable release.
1096 - Do even more to reject (and not just ignore) annotations on
1097 router descriptors received anywhere but from the cache. Previously
1098 we would ignore such annotations at first, but cache them to disk
1099 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
1100 - Do not log messages to the controller while shrinking buffer
1101 freelists. Doing so would sometimes make the controller connection
1102 try to allocate a buffer chunk, which would mess up the internals
1103 of the freelist and cause an assertion failure. Fixes bug 1125;
1104 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
1105 - Learn our external IP address when we're a relay or bridge, even if
1106 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
1107 where we introduced bridge relays that don't need to publish to
1108 be useful. Fixes bug 2050.
1109 - Maintain separate TLS contexts and certificates for incoming and
1110 outgoing connections in bridge relays. Previously we would use the
1111 same TLS contexts and certs for incoming and outgoing connections.
1112 Bugfix on 0.2.0.3-alpha; addresses bug 988.
1113 - Maintain separate identity keys for incoming and outgoing TLS
1114 contexts in bridge relays. Previously we would use the same
1115 identity keys for incoming and outgoing TLS contexts. Bugfix on
1116 0.2.0.3-alpha; addresses the other half of bug 988.
1117 - Avoid an assertion failure when we as an authority receive a
1118 duplicate upload of a router descriptor that we already have,
1119 but which we previously considered an obsolete descriptor.
1120 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
1121 - Avoid a crash bug triggered by looking at a dangling pointer while
1122 setting the network status consensus. Found by Robert Ransom.
1123 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
1124 - Fix a logic error where servers that _didn't_ act as exits would
1125 try to keep their server lists more aggressively up to date than
1126 exits, when it was supposed to be the other way around. Bugfix
1129 o Minor bugfixes (on Tor 0.2.1.x and earlier):
1130 - When we're trying to guess whether we know our IP address as
1131 a relay, we would log various ways that we failed to guess
1132 our address, but never log that we ended up guessing it
1133 successfully. Now add a log line to help confused and anxious
1134 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
1135 - Bring the logic that gathers routerinfos and assesses the
1136 acceptability of circuits into line. This prevents a Tor OP from
1137 getting locked in a cycle of choosing its local OR as an exit for a
1138 path (due to a .exit request) and then rejecting the circuit because
1139 its OR is not listed yet. It also prevents Tor clients from using an
1140 OR running in the same instance as an exit (due to a .exit request)
1141 if the OR does not meet the same requirements expected of an OR
1142 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
1143 - Correctly describe errors that occur when generating a TLS object.
1144 Previously we would attribute them to a failure while generating a
1145 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
1147 - Enforce multiplicity rules when parsing annotations. Bugfix on
1148 0.2.0.8-alpha. Found by piebeer.
1149 - Fix warnings that newer versions of autoconf produced during
1150 ./autogen.sh. These warnings appear to be harmless in our case,
1151 but they were extremely verbose. Fixes bug 2020.
1153 o Minor bugfixes (on Tor 0.2.2.x):
1154 - Enable protection of small arrays whenever we build with gcc
1155 hardening features, not only when also building with warnings
1156 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
1159 - Make hidden services work better in private Tor networks by not
1160 requiring any uptime to join the hidden service descriptor
1161 DHT. Implements ticket 2088.
1162 - Rate-limit the "your application is giving Tor only an IP address"
1163 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
1164 - When AllowSingleHopExits is set, print a warning to explain to the
1165 relay operator why most clients are avoiding her relay.
1166 - Update to the November 1 2010 Maxmind GeoLite Country database.
1168 o Code simplifications and refactoring:
1169 - When we fixed bug 1038 we had to put in a restriction not to send
1170 RELAY_EARLY cells on rend circuits. This was necessary as long
1171 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
1172 active. Now remove this obsolete check. Resolves bug 2081.
1173 - Some options used different conventions for uppercasing of acronyms
1174 when comparing manpage and source. Fix those in favor of the
1175 manpage, as it makes sense to capitalize acronyms.
1176 - Remove the torrc.complete file. It hasn't been kept up to date
1177 and users will have better luck checking out the manpage.
1178 - Remove the obsolete "NoPublish" option; it has been flagged
1179 as obsolete and has produced a warning since 0.1.1.18-rc.
1180 - Remove everything related to building the expert bundle for OS X.
1181 It has confused many users, doesn't work right on OS X 10.6,
1182 and is hard to get rid of once installed. Resolves bug 1274.
1185 Changes in version 0.2.2.17-alpha - 2010-09-30
1186 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
1187 to use one-hop circuits (which can put the exit relays at higher risk,
1188 plus unbalance the network); fixes a big bug in bandwidth accounting
1189 for relays that want to limit their monthly bandwidth use; fixes a
1190 big pile of bugs in how clients tolerate temporary network failure;
1191 and makes our adaptive circuit build timeout feature (which improves
1192 client performance if your network is fast while not breaking things
1193 if your network is slow) better handle bad networks.
1196 - Exit relays now try harder to block exit attempts from unknown
1197 relays, to make it harder for people to use them as one-hop proxies
1198 a la tortunnel. Controlled by the refuseunknownexits consensus
1199 parameter (currently enabled), or you can override it on your
1200 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
1202 o Major bugfixes (0.2.1.x and earlier):
1203 - Fix a bug in bandwidth accounting that could make us use twice
1204 the intended bandwidth when our interval start changes due to
1205 daylight saving time. Now we tolerate skew in stored vs computed
1206 interval starts: if the start of the period changes by no more than
1207 50% of the period's duration, we remember bytes that we transferred
1208 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
1209 - Always search the Windows system directory for system DLLs, and
1210 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
1211 - When you're using bridges and your network goes away and your
1212 bridges get marked as down, recover when you attempt a new socks
1213 connection (if the network is back), rather than waiting up to an
1214 hour to try fetching new descriptors for your bridges. Bugfix on
1215 0.2.0.3-alpha; fixes bug 1981.
1217 o Major bugfixes (on 0.2.2.x):
1218 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
1220 - Fix a segfault that could happen when operating a bridge relay with
1221 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
1222 - The consensus bandwidth-weights (used by clients to choose fast
1223 relays) entered an unexpected edge case in September where
1224 Exits were much scarcer than Guards, resulting in bad weight
1225 recommendations. Now we compute them using new constraints that
1226 should succeed in all cases. Also alter directory authorities to
1227 not include the bandwidth-weights line if they fail to produce
1228 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
1229 - When weighting bridges during path selection, we used to trust
1230 the bandwidths they provided in their descriptor, only capping them
1231 at 10MB/s. This turned out to be problematic for two reasons:
1232 Bridges could claim to handle a lot more traffic then they
1233 actually would, thus making more clients pick them and have a
1234 pretty effective DoS attack. The other issue is that new bridges
1235 that might not have a good estimate for their bw capacity yet
1236 would not get used at all unless no other bridges are available
1237 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
1239 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
1240 - Ignore cannibalized circuits when recording circuit build times.
1241 This should provide for a minor performance improvement for hidden
1242 service users using 0.2.2.14-alpha, and should remove two spurious
1243 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
1244 - Simplify the logic that causes us to decide if the network is
1245 unavailable for purposes of recording circuit build times. If we
1246 receive no cells whatsoever for the entire duration of a circuit's
1247 full measured lifetime, the network is probably down. Also ignore
1248 one-hop directory fetching circuit timeouts when calculating our
1249 circuit build times. These changes should hopefully reduce the
1250 cases where we see ridiculous circuit build timeouts for people
1251 with spotty wireless connections. Fixes part of bug 1772; bugfix
1253 - Prevent the circuit build timeout from becoming larger than
1254 the maximum build time we have ever seen. Also, prevent the time
1255 period for measurement circuits from becoming larger than twice that
1256 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
1259 - When we run out of directory information such that we can't build
1260 circuits, but then get enough that we can build circuits, log when
1261 we actually construct a circuit, so the user has a better chance of
1262 knowing what's going on. Fixes bug 1362.
1263 - Be more generous with how much bandwidth we'd use up (with
1264 accounting enabled) before entering "soft hibernation". Previously,
1265 we'd refuse new connections and circuits once we'd used up 95% of
1266 our allotment. Now, we use up 95% of our allotment, AND make sure
1267 that we have no more than 500MB (or 3 hours of expected traffic,
1268 whichever is lower) remaining before we enter soft hibernation.
1269 - If we've configured EntryNodes and our network goes away and/or all
1270 our entrynodes get marked down, optimistically retry them all when
1271 a new socks application request appears. Fixes bug 1882.
1272 - Add some more defensive programming for architectures that can't
1273 handle unaligned integer accesses. We don't know of any actual bugs
1274 right now, but that's the best time to fix them. Fixes bug 1943.
1275 - Support line continuations in the torrc config file. If a line
1276 ends with a single backslash character, the newline is ignored, and
1277 the configuration value is treated as continuing on the next line.
1280 o Minor bugfixes (on 0.2.1.x and earlier):
1281 - For bandwidth accounting, calculate our expected bandwidth rate
1282 based on the time during which we were active and not in
1283 soft-hibernation during the last interval. Previously, we were
1284 also considering the time spent in soft-hibernation. If this
1285 was a long time, we would wind up underestimating our bandwidth
1286 by a lot, and skewing our wakeup time towards the start of the
1287 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
1289 o Minor bugfixes (on 0.2.2.x):
1290 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
1291 which were disabled by the circuit build timeout changes in
1292 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
1293 - Make sure we don't warn about missing bandwidth weights when
1294 choosing bridges or other relays not in the consensus. Bugfix on
1295 0.2.2.10-alpha; fixes bug 1805.
1296 - In our logs, do not double-report signatures from unrecognized
1297 authorities both as "from unknown authority" and "not
1298 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
1301 Changes in version 0.2.2.16-alpha - 2010-09-17
1302 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
1303 evident at exit relays), and also continues to resolve all the little
1304 bugs that have been filling up trac lately.
1306 o Major bugfixes (stream-level fairness):
1307 - When receiving a circuit-level SENDME for a blocked circuit, try
1308 to package cells fairly from all the streams that had previously
1309 been blocked on that circuit. Previously, we had started with the
1310 oldest stream, and allowed each stream to potentially exhaust
1311 the circuit's package window. This gave older streams on any
1312 given circuit priority over newer ones. Fixes bug 1937. Detected
1313 originally by Camilo Viecco. This bug was introduced before the
1314 first Tor release, in svn commit r152: it is the new winner of
1315 the longest-lived bug prize.
1316 - When the exit relay got a circuit-level sendme cell, it started
1317 reading on the exit streams, even if had 500 cells queued in the
1318 circuit queue already, so the circuit queue just grew and grew in
1319 some cases. We fix this by not re-enabling reading on receipt of a
1320 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
1321 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
1323 - Newly created streams were allowed to read cells onto circuits,
1324 even if the circuit's cell queue was blocked and waiting to drain.
1325 This created potential unfairness, as older streams would be
1326 blocked, but newer streams would gladly fill the queue completely.
1327 We add code to detect this situation and prevent any stream from
1328 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
1332 - Update to the September 1 2010 Maxmind GeoLite Country database.
1333 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
1334 not. This would lead to a cookie that is still not group readable.
1335 Closes bug 1843. Suggested by katmagic.
1336 - When logging a rate-limited warning, we now mention how many messages
1337 got suppressed since the last warning.
1338 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
1339 do individual connection-level rate limiting of clients. The torrc
1340 config options with the same names trump the consensus params, if
1341 both are present. Replaces the old "bwconnrate" and "bwconnburst"
1342 consensus params which were broken from 0.2.2.7-alpha through
1343 0.2.2.14-alpha. Closes bug 1947.
1344 - When a router changes IP address or port, authorities now launch
1345 a new reachability test for it. Implements ticket 1899.
1346 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
1347 2 no signature, 4 required" messages about consensus signatures
1348 easier to read, and make sure they get logged at the same severity
1349 as the messages explaining which keys are which. Fixes bug 1290.
1350 - Don't warn when we have a consensus that we can't verify because
1351 of missing certificates, unless those certificates are ones
1352 that we have been trying and failing to download. Fixes bug 1145.
1353 - If you configure your bridge with a known identity fingerprint,
1354 and the bridge authority is unreachable (as it is in at least
1355 one country now), fall back to directly requesting the descriptor
1356 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
1358 - When building with --enable-gcc-warnings on OpenBSD, disable
1359 warnings in system headers. This makes --enable-gcc-warnings
1360 pass on OpenBSD 4.8.
1362 o Minor bugfixes (on 0.2.1.x and earlier):
1363 - Authorities will now attempt to download consensuses if their
1364 own efforts to make a live consensus have failed. This change
1365 means authorities that restart will fetch a valid consensus, and
1366 it means authorities that didn't agree with the current consensus
1367 will still fetch and serve it if it has enough signatures. Bugfix
1368 on 0.2.0.9-alpha; fixes bug 1300.
1369 - Ensure DNS requests launched by "RESOLVE" commands from the
1370 controller respect the __LeaveStreamsUnattached setconf options. The
1371 same goes for requests launched via DNSPort or transparent
1372 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
1373 - Allow handshaking OR connections to take a full KeepalivePeriod
1374 seconds to handshake. Previously, we would close them after
1375 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
1376 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
1378 - Rate-limit "Failed to hand off onionskin" warnings.
1379 - Never relay a cell for a circuit we have already destroyed.
1380 Between marking a circuit as closeable and finally closing it,
1381 it may have been possible for a few queued cells to get relayed,
1382 even though they would have been immediately dropped by the next
1383 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
1384 - Never queue a cell for a circuit that's already been marked
1386 - Never vote for a server as "Running" if we have a descriptor for
1387 it claiming to be hibernating, and that descriptor was published
1388 more recently than our last contact with the server. Bugfix on
1389 0.2.0.3-alpha; fixes bug 911.
1390 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
1393 o Minor bugfixes (on 0.2.2.x):
1394 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
1395 down if a directory fetch fails and you've configured either
1396 bridges or EntryNodes. The intent was to mark the relay as down
1397 _unless_ you're using bridges or EntryNodes, since if you are
1398 then you could quickly run out of entry points.
1399 - Fix the Windows directory-listing code. A bug introduced in
1400 0.2.2.14-alpha could make Windows directory servers forget to load
1401 some of their cached v2 networkstatus files.
1402 - Really allow clients to use relays as bridges. Fixes bug 1776;
1403 bugfix on 0.2.2.15-alpha.
1404 - Demote a warn to info that happens when the CellStatistics option
1405 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
1406 Reported by Moritz Bartl.
1407 - On Windows, build correctly either with or without Unicode support.
1408 This is necessary so that Tor can support fringe platforms like
1409 Windows 98 (which has no Unicode), or Windows CE (which has no
1410 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
1413 - Add a unit test for cross-platform directory-listing code.
1416 Changes in version 0.2.2.15-alpha - 2010-08-18
1417 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
1418 fixes a variety of other bugs that were preventing performance
1419 experiments from moving forward, fixes several bothersome memory leaks,
1420 and generally closes a lot of smaller bugs that have been filling up
1424 - Stop assigning the HSDir flag to relays that disable their
1425 DirPort (and thus will refuse to answer directory requests). This
1426 fix should dramatically improve the reachability of hidden services:
1427 hidden services and hidden service clients pick six HSDir relays
1428 to store and retrieve the hidden service descriptor, and currently
1429 about half of the HSDir relays will refuse to work. Bugfix on
1430 0.2.0.10-alpha; fixes part of bug 1693.
1431 - The PerConnBWRate and Burst config options, along with the
1432 bwconnrate and bwconnburst consensus params, initialized each conn's
1433 token bucket values only when the connection is established. Now we
1434 update them if the config options change, and update them every time
1435 we get a new consensus. Otherwise we can encounter an ugly edge
1436 case where we initialize an OR conn to client-level bandwidth,
1437 but then later the relay joins the consensus and we leave it
1438 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
1439 - Fix a regression that caused Tor to rebind its ports if it receives
1440 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
1443 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
1444 should give us approximately 40-50% more Guard-flagged nodes,
1445 improving the anonymity the Tor network can provide and also
1446 decreasing the dropoff in throughput that relays experience when
1447 they first get the Guard flag.
1448 - Allow enabling or disabling the *Statistics config options while
1452 - Update to the August 1 2010 Maxmind GeoLite Country database.
1453 - Have the controller interface give a more useful message than
1454 "Internal Error" in response to failed GETINFO requests.
1455 - Warn when the same option is provided more than once in a torrc
1456 file, on the command line, or in a single SETCONF statement, and
1457 the option is one that only accepts a single line. Closes bug 1384.
1458 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
1459 Patch from mingw-san.
1460 - Add support for the country code "{??}" in torrc options like
1461 ExcludeNodes, to indicate all routers of unknown country. Closes
1463 - Relays report the number of bytes spent on answering directory
1464 requests in extra-info descriptors similar to {read,write}-history.
1465 Implements enhancement 1790.
1467 o Minor bugfixes (on 0.2.1.x and earlier):
1468 - Complain if PublishServerDescriptor is given multiple arguments that
1469 include 0 or 1. This configuration will be rejected in the future.
1470 Bugfix on 0.2.0.1-alpha; closes bug 1107.
1471 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
1472 Bugfix on 0.2.0.13-alpha; closes bug 928.
1473 - Change "Application request when we're believed to be offline."
1474 notice to "Application request when we haven't used client
1475 functionality lately.", to clarify that it's not an error. Bugfix
1476 on 0.0.9.3; fixes bug 1222.
1477 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
1478 would return "551 Internal error" rather than "552 Unrecognized key
1479 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
1480 - Users can't configure a regular relay to be their bridge. It didn't
1481 work because when Tor fetched the bridge descriptor, it found
1482 that it already had it, and didn't realize that the purpose of the
1483 descriptor had changed. Now we replace routers with a purpose other
1484 than bridge with bridge descriptors when fetching them. Bugfix on
1485 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
1486 refetch the descriptor with router purpose 'general', disabling
1488 - Fix a rare bug in rend_fn unit tests: we would fail a test when
1489 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
1490 on 0.2.0.10-alpha; fixes bug 1808.
1491 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
1492 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
1493 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
1494 Servers can start sending this code when enough clients recognize
1495 it. Also update the spec to reflect this new reason. Bugfix on
1496 0.1.0.1-rc; fixes part of bug 1793.
1497 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
1498 when we switch from being a public relay to a bridge. Otherwise
1499 there will still be clients that see the relay in their consensus,
1500 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
1502 - Instead of giving an assertion failure on an internal mismatch
1503 on estimated freelist size, just log a BUG warning and try later.
1504 Mitigates but does not fix bug 1125.
1505 - Fix an assertion failure that could occur in caches or bridge users
1506 when using a very short voting interval on a testing network.
1507 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
1509 o Minor bugfixes (on 0.2.2.x):
1510 - Alter directory authorities to always consider Exit-flagged nodes
1511 as potential Guard nodes in their votes. The actual decision to
1512 use Exits as Guards is done in the consensus bandwidth weights.
1513 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
1514 - When the controller is reporting the purpose of circuits that
1515 didn't finish building before the circuit build timeout, it was
1516 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
1517 - Our libevent version parsing code couldn't handle versions like
1518 1.4.14b-stable and incorrectly warned the user about using an
1519 old and broken version of libevent. Treat 1.4.14b-stable like
1520 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
1522 - Don't use substitution references like $(VAR:MOD) when
1523 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
1524 '$(:x)' to 'x' rather than the empty string. This bites us in
1525 doc/ when configured with --disable-asciidoc. Bugfix on
1526 0.2.2.9-alpha; fixes bug 1773.
1527 - Remove a spurious hidden service server-side log notice about
1528 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
1530 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
1532 - Correctly report written bytes on linked connections. Found while
1533 implementing 1790. Bugfix on 0.2.2.4-alpha.
1534 - Fix three memory leaks: one in circuit_build_times_parse_state(),
1535 one in dirvote_add_signatures_to_pending_consensus(), and one every
1536 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
1537 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
1539 o Code simplifications and refactoring:
1540 - Take a first step towards making or.h smaller by splitting out
1541 function definitions for all source files in src/or/. Leave
1542 structures and defines in or.h for now.
1543 - Remove a bunch of unused function declarations as well as a block of
1544 #if 0'd code from the unit tests. Closes bug 1824.
1545 - New unit tests for exit-port history statistics; refactored exit
1546 statistics code to be more easily tested.
1547 - Remove the old debian/ directory from the main Tor distribution.
1548 The official Tor-for-debian git repository lives at the URL
1549 https://git.torproject.org/debian/tor.git
1552 Changes in version 0.2.2.14-alpha - 2010-07-12
1553 Tor 0.2.2.14-alpha greatly improves client-side handling of
1554 circuit build timeouts, which are used to estimate speed and improve
1555 performance. We also move to a much better GeoIP database, port Tor to
1556 Windows CE, introduce new compile flags that improve code security,
1557 add an eighth v3 directory authority, and address a lot of more
1561 - Tor directory authorities no longer crash when started with a
1562 cached-microdesc-consensus file in their data directory. Bugfix
1563 on 0.2.2.6-alpha; fixes bug 1532.
1564 - Treat an unset $HOME like an empty $HOME rather than triggering an
1565 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
1566 - Ignore negative and large circuit build timeout values that can
1567 happen during a suspend or hibernate. These values caused various
1568 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
1569 - Alter calculation of Pareto distribution parameter 'Xm' for
1570 Circuit Build Timeout learning to use the weighted average of the
1571 top N=3 modes (because we have three entry guards). Considering
1572 multiple modes should improve the timeout calculation in some cases,
1573 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
1575 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
1576 right censored distribution model. This approach improves over the
1577 synthetic timeout generation approach that was producing insanely
1578 high timeout values. Now we calculate build timeouts using truncated
1579 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
1580 - Do not close circuits that are under construction when they reach
1581 the circuit build timeout. Instead, leave them building (but do not
1582 use them) for up until the time corresponding to the 95th percentile
1583 on the Pareto CDF or 60 seconds, whichever is greater. This is done
1584 to provide better data for the new Pareto model. This percentile
1585 can be controlled by the consensus.
1588 - Move to the June 2010 Maxmind GeoLite country db (rather than the
1589 June 2009 ip-to-country GeoIP db) for our statistics that count
1590 how many users relays are seeing from each country. Now we have
1591 more accurate data for many African countries.
1592 - Port Tor to build and run correctly on Windows CE systems, using
1593 the wcecompat library. Contributed by Valerio Lupi.
1594 - New "--enable-gcc-hardening" ./configure flag (off by default)
1595 to turn on gcc compile time hardening options. It ensures
1596 that signed ints have defined behavior (-fwrapv), enables
1597 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
1598 with canaries (-fstack-protector-all), turns on ASLR protection if
1599 supported by the kernel (-fPIE, -pie), and adds additional security
1600 related warnings. Verified to work on Mac OS X and Debian Lenny.
1601 - New "--enable-linker-hardening" ./configure flag (off by default)
1602 to turn on ELF specific hardening features (relro, now). This does
1603 not work with Mac OS X or any other non-ELF binary format.
1605 o New directory authorities:
1606 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
1610 - New config option "WarnUnsafeSocks 0" disables the warning that
1611 occurs whenever Tor receives only an IP address instead of a
1612 hostname. Setups that do DNS locally over Tor are fine, and we
1613 shouldn't spam the logs in that case.
1614 - Convert the HACKING file to asciidoc, and add a few new sections
1615 to it, explaining how we use Git, how we make changelogs, and
1616 what should go in a patch.
1617 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
1618 event, to give information on the current rate of circuit timeouts
1619 over our stored history.
1620 - Add ability to disable circuit build time learning via consensus
1621 parameter and via a LearnCircuitBuildTimeout config option. Also
1622 automatically disable circuit build time calculation if we are
1623 either a AuthoritativeDirectory, or if we fail to write our state
1624 file. Fixes bug 1296.
1625 - More gracefully handle corrupt state files, removing asserts
1626 in favor of saving a backup and resetting state.
1627 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
1631 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
1633 - When a2x fails, mention that the user could disable manpages instead
1634 of trying to fix their asciidoc installation.
1635 - Where available, use Libevent 2.0's periodic timers so that our
1636 once-per-second cleanup code gets called even more closely to
1637 once per second than it would otherwise. Fixes bug 943.
1638 - If you run a bridge that listens on multiple IP addresses, and
1639 some user configures a bridge address that uses a different IP
1640 address than your bridge writes in its router descriptor, and the
1641 user doesn't specify an identity key, their Tor would discard the
1642 descriptor because "it isn't one of our configured bridges", and
1643 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
1644 Bugfix on 0.2.0.3-alpha.
1645 - If OpenSSL fails to make a duplicate of a private or public key, log
1646 an error message and try to exit cleanly. May help with debugging
1647 if bug 1209 ever remanifests.
1648 - Save a couple bytes in memory allocation every time we escape
1649 certain characters in a string. Patch from Florian Zumbiehl.
1650 - Make it explicit that we don't cannibalize one-hop circuits. This
1651 happens in the wild, but doesn't turn out to be a problem because
1652 we fortunately don't use those circuits. Many thanks to outofwords
1653 for the initial analysis and to swissknife who confirmed that
1654 two-hop circuits are actually created.
1655 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
1656 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
1657 - Eliminate a case where a circuit build time warning was displayed
1658 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
1661 Changes in version 0.2.1.26 - 2010-05-02
1662 Tor 0.2.1.26 addresses the recent connection and memory overload
1663 problems we've been seeing on relays, especially relays with their
1664 DirPort open. If your relay has been crashing, or you turned it off
1665 because it used too many resources, give this release a try.
1667 This release also fixes yet another instance of broken OpenSSL libraries
1668 that was causing some relays to drop out of the consensus.
1671 - Teach relays to defend themselves from connection overload. Relays
1672 now close idle circuits early if it looks like they were intended
1673 for directory fetches. Relays are also more aggressive about closing
1674 TLS connections that have no circuits on them. Such circuits are
1675 unlikely to be re-used, and tens of thousands of them were piling
1676 up at the fast relays, causing the relays to run out of sockets
1677 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
1678 their directory fetches over TLS).
1679 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
1680 that claim to be earlier than 0.9.8m, but which have in reality
1681 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
1682 behavior. Possible fix for some cases of bug 1346.
1683 - Directory mirrors were fetching relay descriptors only from v2
1684 directory authorities, rather than v3 authorities like they should.
1685 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
1686 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
1689 - Finally get rid of the deprecated and now harmful notion of "clique
1690 mode", where directory authorities maintain TLS connections to
1694 - In the util/threads test, no longer free the test_mutex before all
1695 worker threads have finished. Bugfix on 0.2.1.6-alpha.
1696 - The master thread could starve the worker threads quite badly on
1697 certain systems, causing them to run only partially in the allowed
1698 window. This resulted in test failures. Now the master thread sleeps
1699 occasionally for a few microseconds while the two worker-threads
1700 compete for the mutex. Bugfix on 0.2.0.1-alpha.
1703 Changes in version 0.2.2.13-alpha - 2010-04-24
1704 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
1705 problems we've been seeing on relays, especially relays with their
1706 DirPort open. If your relay has been crashing, or you turned it off
1707 because it used too many resources, give this release a try.
1710 - Teach relays to defend themselves from connection overload. Relays
1711 now close idle circuits early if it looks like they were intended
1712 for directory fetches. Relays are also more aggressive about closing
1713 TLS connections that have no circuits on them. Such circuits are
1714 unlikely to be re-used, and tens of thousands of them were piling
1715 up at the fast relays, causing the relays to run out of sockets
1716 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
1717 their directory fetches over TLS).
1720 - Finally get rid of the deprecated and now harmful notion of "clique
1721 mode", where directory authorities maintain TLS connections to
1723 - Directory authorities now do an immediate reachability check as soon
1724 as they hear about a new relay. This change should slightly reduce
1725 the time between setting up a relay and getting listed as running
1726 in the consensus. It should also improve the time between setting
1727 up a bridge and seeing use by bridge users.
1728 - Directory authorities no longer launch a TLS connection to every
1729 relay as they startup. Now that we have 2k+ descriptors cached,
1730 the resulting network hiccup is becoming a burden. Besides,
1731 authorities already avoid voting about Running for the first half
1732 hour of their uptime.
1735 Changes in version 0.2.2.12-alpha - 2010-04-20
1736 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
1737 handle and vote on descriptors. It was causing relays to drop out of
1741 - Many relays have been falling out of the consensus lately because
1742 not enough authorities know about their descriptor for them to get
1743 a majority of votes. When we deprecated the v2 directory protocol,
1744 we got rid of the only way that v3 authorities can hear from each
1745 other about other descriptors. Now authorities examine every v3
1746 vote for new descriptors, and fetch them from that authority. Bugfix
1748 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
1749 and a warning in or.h related to bandwidth_weight_rule_t that
1750 prevented clean compile on OS X. Fixes bug 1363; bugfix on
1752 - Fix a segfault on relays when DirReqStatistics is enabled
1753 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
1757 - Demote a confusing TLS warning that relay operators might get when
1758 someone tries to talk to their OrPort. It is neither the operator's
1759 fault nor can they do anything about it. Fixes bug 1364; bugfix
1763 Changes in version 0.2.2.11-alpha - 2010-04-15
1764 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
1765 libraries that was causing some relays to drop out of the consensus.
1768 - Directory mirrors were fetching relay descriptors only from v2
1769 directory authorities, rather than v3 authorities like they should.
1770 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
1771 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
1772 - Fix a parsing error that made every possible value of
1773 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
1774 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
1775 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
1776 about the option without breaking older ones.
1777 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
1778 that claim to be earlier than 0.9.8m, but which have in reality
1779 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
1780 behavior. Possible fix for some cases of bug 1346.
1783 - Experiment with a more aggressive approach to preventing clients
1784 from making one-hop exit streams. Exit relays who want to try it
1785 out can set "RefuseUnknownExits 1" in their torrc, and then look
1786 for "Attempt by %s to open a stream" log messages. Let us know
1788 - Add support for statically linking zlib by specifying
1789 --enable-static-zlib, to go with our support for statically linking
1790 openssl and libevent. Resolves bug 1358.
1793 - Fix a segfault that happens whenever a Tor client that is using
1794 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
1796 - When we cleaned up the contrib/tor-exit-notice.html file, we left
1797 out the first line. Fixes bug 1295.
1798 - When building the manpage from a tarball, we required asciidoc, but
1799 the asciidoc -> roff/html conversion was already done for the
1800 tarball. Make 'make' complain only when we need asciidoc (either
1801 because we're compiling directly from git, or because we altered
1802 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
1803 - When none of the directory authorities vote on any params, Tor
1804 segfaulted when trying to make the consensus from the votes. We
1805 didn't trigger the bug in practice, because authorities do include
1806 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
1809 - In the util/threads test, no longer free the test_mutex before all
1810 worker threads have finished. Bugfix on 0.2.1.6-alpha.
1811 - The master thread could starve the worker threads quite badly on
1812 certain systems, causing them to run only partially in the allowed
1813 window. This resulted in test failures. Now the master thread sleeps
1814 occasionally for a few microseconds while the two worker-threads
1815 compete for the mutex. Bugfix on 0.2.0.1-alpha.
1818 Changes in version 0.2.2.10-alpha - 2010-03-07
1819 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
1820 could prevent relays from guessing their IP address correctly. It also
1821 starts the groundwork for another client-side performance boost, since
1822 currently we're not making efficient use of relays that have both the
1823 Guard flag and the Exit flag.
1826 - Fix a regression from our patch for bug 1244 that caused relays
1827 to guess their IP address incorrectly if they didn't set Address
1828 in their torrc and/or their address fails to resolve. Bugfix on
1829 0.2.2.9-alpha; fixes bug 1269.
1831 o Major features (performance):
1832 - Directory authorities now compute consensus weightings that instruct
1833 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
1834 and no flag. Clients that use these weightings will distribute
1835 network load more evenly across these different relay types. The
1836 weightings are in the consensus so we can change them globally in
1837 the future. Extra thanks to "outofwords" for finding some nasty
1838 security bugs in the first implementation of this feature.
1840 o Minor features (performance):
1841 - Always perform router selections using weighted relay bandwidth,
1842 even if we don't need a high capacity circuit at the time. Non-fast
1843 circuits now only differ from fast ones in that they can use relays
1844 not marked with the Fast flag. This "feature" could turn out to
1845 be a horrible bug; we should investigate more before it goes into
1849 - Allow disabling building of the manpages. Skipping the manpage
1850 speeds up the build considerably.
1852 o Minor bugfixes (on 0.2.2.x):
1853 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
1854 Bugfix on 0.2.2.9-alpha.
1855 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
1856 config option. Bugfix on 0.2.2.7-alpha.
1857 - Ship the asciidoc-helper file in the tarball, so that people can
1858 build from source if they want to, and touching the .1.txt files
1859 doesn't break the build. Bugfix on 0.2.2.9-alpha.
1861 o Minor bugfixes (on 0.2.1.x or earlier):
1862 - Fix a dereference-then-NULL-check sequence when publishing
1863 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
1865 - Fix another dereference-then-NULL-check sequence. Bugfix on
1866 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
1867 - Make sure we treat potentially not NUL-terminated strings correctly.
1868 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
1870 o Code simplifications and refactoring:
1871 - Fix some urls in the exit notice file and make it XHTML1.1 strict
1872 compliant. Based on a patch from Christian Kujau.
1873 - Don't use sed in asciidoc-helper anymore.
1874 - Make the build process fail if asciidoc cannot be found and
1875 building with asciidoc isn't disabled.
1878 Changes in version 0.2.2.9-alpha - 2010-02-22
1879 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
1880 location of a directory authority, and cleans up a bunch of small bugs.
1882 o Directory authority changes:
1883 - Change IP address for dannenberg (v3 directory authority), and
1884 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
1885 service directory authority) from the list.
1888 - Make Tor work again on the latest OS X: when deciding whether to
1889 use strange flags to turn TLS renegotiation on, detect the OpenSSL
1890 version at run-time, not compile time. We need to do this because
1891 Apple doesn't update its dev-tools headers when it updates its
1892 libraries in a security patch.
1893 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
1894 that could happen on 32-bit platforms with 64-bit time_t. Also fix
1895 a memory leak when requesting a hidden service descriptor we've
1896 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
1898 - Authorities could be tricked into giving out the Exit flag to relays
1899 that didn't allow exiting to any ports. This bug could screw
1900 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
1901 1238. Bug discovered by Martin Kowalczyk.
1902 - When freeing a session key, zero it out completely. We only zeroed
1903 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
1904 patched by ekir. Fixes bug 1254.
1907 - Fix static compilation by listing the openssl libraries in the right
1908 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
1909 - Resume handling .exit hostnames in a special way: originally we
1910 stripped the .exit part and used the requested exit relay. In
1911 0.2.2.1-alpha we stopped treating them in any special way, meaning
1912 if you use a .exit address then Tor will pass it on to the exit
1913 relay. Now we reject the .exit stream outright, since that behavior
1914 might be more expected by the user. Found and diagnosed by Scott
1915 Bennett and Downie on or-talk.
1916 - Don't spam the controller with events when we have no file
1917 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
1918 for log messages was already solved from bug 748.)
1919 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
1921 - Make the DNSPort option work with libevent 2.x. Don't alter the
1922 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
1923 - Emit a GUARD DROPPED controller event for a case we missed.
1924 - Make more fields in the controller protocol case-insensitive, since
1925 control-spec.txt said they were.
1926 - Refactor resolve_my_address() to not use gethostbyname() anymore.
1927 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
1928 - Fix a spec conformance issue: the network-status-version token
1929 must be the first token in a v3 consensus or vote. Discovered by
1930 parakeep. Bugfix on 0.2.0.3-alpha.
1932 o Code simplifications and refactoring:
1933 - Generate our manpage and HTML documentation using Asciidoc. This
1934 change should make it easier to maintain the documentation, and
1936 - Remove the --enable-iphone option. According to reports from Marco
1937 Bonetti, Tor builds fine without any special tweaking on recent
1938 iPhone SDK versions.
1939 - Removed some unnecessary files from the source distribution. The
1940 AUTHORS file has now been merged into the people page on the
1941 website. The roadmaps and design doc can now be found in the
1942 projects directory in svn.
1943 - Enabled various circuit build timeout constants to be controlled
1944 by consensus parameters. Also set better defaults for these
1945 parameters based on experimentation on broadband and simulated
1949 - The 'EXTENDCIRCUIT' control port command can now be used with
1950 a circ id of 0 and no path. This feature will cause Tor to build
1951 a new 'fast' general purpose circuit using its own path selection
1953 - Added a BUILDTIMEOUT_SET controller event to describe changes
1954 to the circuit build timeout.
1955 - Future-proof the controller protocol a bit by ignoring keyword
1956 arguments we do not recognize.
1957 - Expand homedirs passed to tor-checkkey. This should silence a
1958 coverity complaint about passing a user-supplied string into
1959 open() without checking it.
1962 Changes in version 0.2.1.25 - 2010-03-16
1963 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
1964 prevent relays from guessing their IP address correctly. It also fixes
1965 several minor potential security bugs.
1968 - Fix a regression from our patch for bug 1244 that caused relays
1969 to guess their IP address incorrectly if they didn't set Address
1970 in their torrc and/or their address fails to resolve. Bugfix on
1971 0.2.1.23; fixes bug 1269.
1972 - When freeing a session key, zero it out completely. We only zeroed
1973 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
1974 patched by ekir. Fixes bug 1254.
1977 - Fix a dereference-then-NULL-check sequence when publishing
1978 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
1980 - Fix another dereference-then-NULL-check sequence. Bugfix on
1981 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
1982 - Make sure we treat potentially not NUL-terminated strings correctly.
1983 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
1987 Changes in version 0.2.1.24 - 2010-02-21
1988 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
1992 - Work correctly out-of-the-box with even more vendor-patched versions
1993 of OpenSSL. In particular, make it so Debian and OS X don't need
1994 customized patches to run/build.
1997 Changes in version 0.2.1.23 - 2010-02-13
1998 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
1999 again on the latest OS X, and updates the location of a directory
2002 o Major bugfixes (performance):
2003 - We were selecting our guards uniformly at random, and then weighting
2004 which of our guards we'd use uniformly at random. This imbalance
2005 meant that Tor clients were severely limited on throughput (and
2006 probably latency too) by the first hop in their circuit. Now we
2007 select guards weighted by currently advertised bandwidth. We also
2008 automatically discard guards picked using the old algorithm. Fixes
2009 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
2012 - Make Tor work again on the latest OS X: when deciding whether to
2013 use strange flags to turn TLS renegotiation on, detect the OpenSSL
2014 version at run-time, not compile time. We need to do this because
2015 Apple doesn't update its dev-tools headers when it updates its
2016 libraries in a security patch.
2017 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
2018 that could happen on 32-bit platforms with 64-bit time_t. Also fix
2019 a memory leak when requesting a hidden service descriptor we've
2020 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
2023 o Directory authority changes:
2024 - Change IP address for dannenberg (v3 directory authority), and
2025 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
2026 service directory authority) from the list.
2029 - Refactor resolve_my_address() to not use gethostbyname() anymore.
2030 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
2033 - Avoid a mad rush at the beginning of each month when each client
2034 rotates half of its guards. Instead we spread the rotation out
2035 throughout the month, but we still avoid leaving a precise timestamp
2036 in the state file about when we first picked the guard. Improves
2037 over the behavior introduced in 0.1.2.17.
2040 Changes in version 0.2.2.8-alpha - 2010-01-26
2041 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
2042 causing bridge relays to disappear. If you're running a bridge,
2046 - Fix a memory corruption bug on bridges that occured during the
2047 inclusion of stats data in extra-info descriptors. Also fix the
2048 interface for geoip_get_bridge_stats* to prevent similar bugs in
2049 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
2050 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
2053 - Ignore OutboundBindAddress when connecting to localhost.
2054 Connections to localhost need to come _from_ localhost, or else
2055 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
2059 Changes in version 0.2.2.7-alpha - 2010-01-19
2060 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
2061 as laying the groundwork for further relay-side performance fixes. It
2062 also starts cleaning up client behavior with respect to the EntryNodes,
2063 ExitNodes, and StrictNodes config options.
2065 This release also rotates two directory authority keys, due to a
2066 security breach of some of the Torproject servers.
2068 o Directory authority changes:
2069 - Rotate keys (both v3 identity and relay identity) for moria1
2072 o Major features (performance):
2073 - We were selecting our guards uniformly at random, and then weighting
2074 which of our guards we'd use uniformly at random. This imbalance
2075 meant that Tor clients were severely limited on throughput (and
2076 probably latency too) by the first hop in their circuit. Now we
2077 select guards weighted by currently advertised bandwidth. We also
2078 automatically discard guards picked using the old algorithm. Fixes
2079 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
2080 - When choosing which cells to relay first, relays can now favor
2081 circuits that have been quiet recently, to provide lower latency
2082 for low-volume circuits. By default, relays enable or disable this
2083 feature based on a setting in the consensus. You can override
2084 this default by using the new "CircuitPriorityHalflife" config
2085 option. Design and code by Ian Goldberg, Can Tang, and Chris
2087 - Add separate per-conn write limiting to go with the per-conn read
2088 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
2089 but never per-conn write limits.
2090 - New consensus params "bwconnrate" and "bwconnburst" to let us
2091 rate-limit client connections as they enter the network. It's
2092 controlled in the consensus so we can turn it on and off for
2093 experiments. It's starting out off. Based on proposal 163.
2095 o Major features (relay selection options):
2096 - Switch to a StrictNodes config option, rather than the previous
2097 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
2098 "StrictExcludeNodes" option.
2099 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
2100 change during a config reload, mark and discard all our origin
2101 circuits. This fix should address edge cases where we change the
2102 config options and but then choose a circuit that we created before
2104 - If EntryNodes or ExitNodes are set, be more willing to use an
2105 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
2107 - Make EntryNodes config option much more aggressive even when
2108 StrictNodes is not set. Before it would prepend your requested
2109 entrynodes to your list of guard nodes, but feel free to use others
2110 after that. Now it chooses only from your EntryNodes if any of
2111 those are available, and only falls back to others if a) they're
2112 all down and b) StrictNodes is not set.
2113 - Now we refresh your entry guards from EntryNodes at each consensus
2114 fetch -- rather than just at startup and then they slowly rot as
2115 the network changes.
2118 - Stop bridge directory authorities from answering dbg-stability.txt
2119 directory queries, which would let people fetch a list of all
2120 bridge identities they track. Bugfix on 0.2.1.6-alpha.
2123 - Log a notice when we get a new control connection. Now it's easier
2124 for security-conscious users to recognize when a local application
2125 is knocking on their controller door. Suggested by bug 1196.
2126 - New config option "CircuitStreamTimeout" to override our internal
2127 timeout schedule for how many seconds until we detach a stream from
2128 a circuit and try a new circuit. If your network is particularly
2129 slow, you might want to set this to a number like 60.
2130 - New controller command "getinfo config-text". It returns the
2131 contents that Tor would write if you send it a SAVECONF command,
2132 so the controller can write the file to disk itself.
2133 - New options for SafeLogging to allow scrubbing only log messages
2134 generated while acting as a relay.
2135 - Ship the bridges spec file in the tarball too.
2136 - Avoid a mad rush at the beginning of each month when each client
2137 rotates half of its guards. Instead we spread the rotation out
2138 throughout the month, but we still avoid leaving a precise timestamp
2139 in the state file about when we first picked the guard. Improves
2140 over the behavior introduced in 0.1.2.17.
2142 o Minor bugfixes (compiling):
2143 - Fix compilation on OS X 10.3, which has a stub mlockall() but
2144 hides it. Bugfix on 0.2.2.6-alpha.
2145 - Fix compilation on Solaris by removing support for the
2146 DisableAllSwap config option. Solaris doesn't have an rlimit for
2147 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
2150 o Minor bugfixes (crashes):
2151 - Do not segfault when writing buffer stats when we haven't observed
2152 a single circuit to report about. Found by Fabian Lanze. Bugfix on
2154 - If we're in the pathological case where there's no exit bandwidth
2155 but there is non-exit bandwidth, or no guard bandwidth but there
2156 is non-guard bandwidth, don't crash during path selection. Bugfix
2158 - Fix an impossible-to-actually-trigger buffer overflow in relay
2159 descriptor generation. Bugfix on 0.1.0.15.
2161 o Minor bugfixes (privacy):
2162 - Fix an instance where a Tor directory mirror might accidentally
2163 log the IP address of a misbehaving Tor client. Bugfix on
2165 - Don't list Windows capabilities in relay descriptors. We never made
2166 use of them, and maybe it's a bad idea to publish them. Bugfix
2169 o Minor bugfixes (other):
2170 - Resolve an edge case in path weighting that could make us misweight
2171 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
2172 - Fix statistics on client numbers by country as seen by bridges that
2173 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
2174 intervals instead of variable 12-to-48-hour intervals.
2175 - After we free an internal connection structure, overwrite it
2176 with a different memory value than we use for overwriting a freed
2177 internal circuit structure. Should help with debugging. Suggested
2179 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
2183 - Remove the HSAuthorityRecordStats option that version 0 hidden
2184 service authorities could have used to track statistics of overall
2185 hidden service usage.
2188 Changes in version 0.2.1.22 - 2010-01-19
2189 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
2190 authorities -- it would tell you its whole history of bridge descriptors
2191 if you make the right directory request. This stable update also
2192 rotates two of the seven v3 directory authority keys and locations.
2194 o Directory authority changes:
2195 - Rotate keys (both v3 identity and relay identity) for moria1
2199 - Stop bridge directory authorities from answering dbg-stability.txt
2200 directory queries, which would let people fetch a list of all
2201 bridge identities they track. Bugfix on 0.2.1.6-alpha.
2204 Changes in version 0.2.1.21 - 2009-12-21
2205 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
2206 library. If you use Tor on Linux / Unix and you're getting SSL
2207 renegotiation errors, upgrading should help. We also recommend an
2208 upgrade if you're an exit relay.
2211 - Work around a security feature in OpenSSL 0.9.8l that prevents our
2212 handshake from working unless we explicitly tell OpenSSL that we
2213 are using SSL renegotiation safely. We are, of course, but OpenSSL
2214 0.9.8l won't work unless we say we are.
2215 - Avoid crashing if the client is trying to upload many bytes and the
2216 circuit gets torn down at the same time, or if the flip side
2217 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
2220 - Do not refuse to learn about authority certs and v2 networkstatus
2221 documents that are older than the latest consensus. This bug might
2222 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
2223 Spotted and fixed by xmux.
2224 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
2225 trigger platform-specific option misparsing case found by Coverity
2227 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
2228 trigger assert. Fixes bug 1173.
2231 Changes in version 0.2.2.6-alpha - 2009-11-19
2232 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
2233 support for the new lower-footprint "microdescriptor" directory design,
2234 future-proofing our consensus format against new hash functions or
2235 other changes, and an Android port. It also makes Tor compatible with
2236 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
2239 - Directory authorities can now create, vote on, and serve multiple
2240 parallel formats of directory data as part of their voting process.
2241 Partially implements Proposal 162: "Publish the consensus in
2243 - Directory authorities can now agree on and publish small summaries
2244 of router information that clients can use in place of regular
2245 server descriptors. This transition will eventually allow clients
2246 to use far less bandwidth for downloading information about the
2247 network. Begins the implementation of Proposal 158: "Clients
2248 download consensus + microdescriptors".
2249 - The directory voting system is now extensible to use multiple hash
2250 algorithms for signatures and resource selection. Newer formats
2251 are signed with SHA256, with a possibility for moving to a better
2252 hash algorithm in the future.
2253 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
2254 current and future memory pages via mlockall(). On supported
2255 platforms (modern Linux and probably BSD but not Windows or OS X),
2256 this should effectively disable any and all attempts to page out
2257 memory. This option requires that you start your Tor as root --
2258 if you use DisableAllSwap, please consider using the User option
2259 to properly reduce the privileges of your Tor.
2260 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
2261 to help Tor build correctly for Android phones.
2264 - Work around a security feature in OpenSSL 0.9.8l that prevents our
2265 handshake from working unless we explicitly tell OpenSSL that we
2266 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
2267 won't work unless we say we are.
2270 - Fix a crash bug when trying to initialize the evdns module in
2271 Libevent 2. Bugfix on 0.2.1.16-rc.
2272 - Stop logging at severity 'warn' when some other Tor client tries
2273 to establish a circuit with us using weak DH keys. It's a protocol
2274 violation, but that doesn't mean ordinary users need to hear about
2275 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
2276 - Do not refuse to learn about authority certs and v2 networkstatus
2277 documents that are older than the latest consensus. This bug might
2278 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
2279 Spotted and fixed by xmux.
2280 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
2281 - If all authorities restart at once right before a consensus vote,
2282 nobody will vote about "Running", and clients will get a consensus
2283 with no usable relays. Instead, authorities refuse to build a
2284 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
2285 - If your relay can't keep up with the number of incoming create
2286 cells, it would log one warning per failure into your logs. Limit
2287 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
2288 - Bridges now use "reject *:*" as their default exit policy. Bugfix
2289 on 0.2.0.3-alpha; fixes bug 1113.
2290 - Fix a memory leak on directory authorities during voting that was
2291 introduced in 0.2.2.1-alpha. Found via valgrind.
2294 Changes in version 0.2.1.20 - 2009-10-15
2295 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
2296 services at once, prepares for more performance improvements, and
2297 fixes a bunch of smaller bugs.
2299 The Windows and OS X bundles also include a more recent Vidalia,
2300 and switch from Privoxy to Polipo.
2302 The OS X installers are now drag and drop. It's best to un-install
2303 Tor/Vidalia and then install this new bundle, rather than upgrade. If
2304 you want to upgrade, you'll need to update the paths for Tor and Polipo
2305 in the Vidalia Settings window.
2308 - Send circuit or stream sendme cells when our window has decreased
2309 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
2310 by Karsten when testing the "reduce circuit window" performance
2311 patch. Bugfix on the 54th commit on Tor -- from July 2002,
2312 before the release of Tor 0.0.0. This is the new winner of the
2314 - Fix a remotely triggerable memory leak when a consensus document
2315 contains more than one signature from the same voter. Bugfix on
2317 - Avoid segfault in rare cases when finishing an introduction circuit
2318 as a client and finding out that we don't have an introduction key
2319 for it. Fixes bug 1073. Reported by Aaron Swartz.
2322 - Tor now reads the "circwindow" parameter out of the consensus,
2323 and uses that value for its circuit package window rather than the
2324 default of 1000 cells. Begins the implementation of proposal 168.
2326 o New directory authorities:
2327 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
2329 - Move moria1 and tonga to alternate IP addresses.
2332 - Fix a signed/unsigned compile warning in 0.2.1.19.
2333 - Fix possible segmentation fault on directory authorities. Bugfix on
2335 - Fix an extremely rare infinite recursion bug that could occur if
2336 we tried to log a message after shutting down the log subsystem.
2337 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
2338 - Fix an obscure bug where hidden services on 64-bit big-endian
2339 systems might mis-read the timestamp in v3 introduce cells, and
2340 refuse to connect back to the client. Discovered by "rotor".
2341 Bugfix on 0.2.1.6-alpha.
2342 - We were triggering a CLOCK_SKEW controller status event whenever
2343 we connect via the v2 connection protocol to any relay that has
2344 a wrong clock. Instead, we should only inform the controller when
2345 it's a trusted authority that claims our clock is wrong. Bugfix
2346 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
2347 - We were telling the controller about CHECKING_REACHABILITY and
2348 REACHABILITY_FAILED status events whenever we launch a testing
2349 circuit or notice that one has failed. Instead, only tell the
2350 controller when we want to inform the user of overall success or
2351 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
2353 - Don't warn when we're using a circuit that ends with a node
2354 excluded in ExcludeExitNodes, but the circuit is not used to access
2355 the outside world. This should help fix bug 1090. Bugfix on
2357 - Work around a small memory leak in some versions of OpenSSL that
2358 stopped the memory used by the hostname TLS extension from being
2362 - Add a "getinfo status/accepted-server-descriptor" controller
2363 command, which is the recommended way for controllers to learn
2364 whether our server descriptor has been successfully received by at
2365 least on directory authority. Un-recommend good-server-descriptor
2366 getinfo and status events until we have a better design for them.
2369 Changes in version 0.2.2.5-alpha - 2009-10-11
2370 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
2373 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
2375 o New directory authorities:
2376 - Move dizum to an alternate IP address.
2379 Changes in version 0.2.2.4-alpha - 2009-10-10
2380 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
2381 introduces a new unit test framework, shifts directry authority
2382 addresses around to reduce the impact from recent blocking events,
2383 and fixes a few smaller bugs.
2386 - Fix several more asserts in the circuit_build_times code, for
2387 example one that causes Tor to fail to start once we have
2388 accumulated 5000 build times in the state file. Bugfixes on
2389 0.2.2.2-alpha; fixes bug 1108.
2391 o New directory authorities:
2392 - Move moria1 and Tonga to alternate IP addresses.
2395 - Log SSL state transitions at debug level during handshake, and
2396 include SSL states in error messages. This may help debug future
2397 SSL handshake issues.
2398 - Add a new "Handshake" log domain for activities that happen
2399 during the TLS handshake.
2400 - Revert to the "June 3 2009" ip-to-country file. The September one
2401 seems to have removed most US IP addresses.
2402 - Directory authorities now reject Tor relays with versions less than
2403 0.1.2.14. This step cuts out four relays from the current network,
2404 none of which are very big.
2407 - Fix a couple of smaller issues with gathering statistics. Bugfixes
2409 - Fix two memory leaks in the error case of
2410 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
2411 - Don't count one-hop circuits when we're estimating how long it
2412 takes circuits to build on average. Otherwise we'll set our circuit
2413 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
2414 - Directory authorities no longer change their opinion of, or vote on,
2415 whether a router is Running, unless they have themselves been
2416 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
2419 o Code simplifications and refactoring:
2420 - Revise our unit tests to use the "tinytest" framework, so we
2421 can run tests in their own processes, have smarter setup/teardown
2422 code, and so on. The unit test code has moved to its own
2423 subdirectory, and has been split into multiple modules.
2426 Changes in version 0.2.2.3-alpha - 2009-09-23
2427 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
2430 - Fix an overzealous assert in our new circuit build timeout code.
2431 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
2434 - If the networkstatus consensus tells us that we should use a
2435 negative circuit package window, ignore it. Otherwise we'll
2436 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
2439 Changes in version 0.2.2.2-alpha - 2009-09-21
2440 Tor 0.2.2.2-alpha introduces our latest performance improvement for
2441 clients: Tor tracks the average time it takes to build a circuit, and
2442 avoids using circuits that take too long to build. For fast connections,
2443 this feature can cut your expected latency in half. For slow or flaky
2444 connections, it could ruin your Tor experience. Let us know if it does!
2447 - Tor now tracks how long it takes to build client-side circuits
2448 over time, and adapts its timeout to local network performance.
2449 Since a circuit that takes a long time to build will also provide
2450 bad performance, we get significant latency improvements by
2451 discarding the slowest 20% of circuits. Specifically, Tor creates
2452 circuits more aggressively than usual until it has enough data
2453 points for a good timeout estimate. Implements proposal 151.
2454 We are especially looking for reports (good and bad) from users with
2455 both EDGE and broadband connections that can move from broadband
2456 to EDGE and find out if the build-time data in the .tor/state gets
2457 reset without loss of Tor usability. You should also see a notice
2458 log message telling you that Tor has reset its timeout.
2459 - Directory authorities can now vote on arbitary integer values as
2460 part of the consensus process. This is designed to help set
2461 network-wide parameters. Implements proposal 167.
2462 - Tor now reads the "circwindow" parameter out of the consensus,
2463 and uses that value for its circuit package window rather than the
2464 default of 1000 cells. Begins the implementation of proposal 168.
2467 - Fix a remotely triggerable memory leak when a consensus document
2468 contains more than one signature from the same voter. Bugfix on
2472 - Fix an extremely rare infinite recursion bug that could occur if
2473 we tried to log a message after shutting down the log subsystem.
2474 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
2475 - Fix parsing for memory or time units given without a space between
2476 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
2477 - A networkstatus vote must contain exactly one signature. Spec
2478 conformance issue. Bugfix on 0.2.0.3-alpha.
2479 - Fix an obscure bug where hidden services on 64-bit big-endian
2480 systems might mis-read the timestamp in v3 introduce cells, and
2481 refuse to connect back to the client. Discovered by "rotor".
2482 Bugfix on 0.2.1.6-alpha.
2483 - We were triggering a CLOCK_SKEW controller status event whenever
2484 we connect via the v2 connection protocol to any relay that has
2485 a wrong clock. Instead, we should only inform the controller when
2486 it's a trusted authority that claims our clock is wrong. Bugfix
2487 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
2488 - We were telling the controller about CHECKING_REACHABILITY and
2489 REACHABILITY_FAILED status events whenever we launch a testing
2490 circuit or notice that one has failed. Instead, only tell the
2491 controller when we want to inform the user of overall success or
2492 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
2494 - Don't warn when we're using a circuit that ends with a node
2495 excluded in ExcludeExitNodes, but the circuit is not used to access
2496 the outside world. This should help fix bug 1090, but more problems
2497 remain. Bugfix on 0.2.1.6-alpha.
2498 - Work around a small memory leak in some versions of OpenSSL that
2499 stopped the memory used by the hostname TLS extension from being
2501 - Make our 'torify' script more portable; if we have only one of
2502 'torsocks' or 'tsocks' installed, don't complain to the user;
2503 and explain our warning about tsocks better.
2506 - Add a "getinfo status/accepted-server-descriptor" controller
2507 command, which is the recommended way for controllers to learn
2508 whether our server descriptor has been successfully received by at
2509 least on directory authority. Un-recommend good-server-descriptor
2510 getinfo and status events until we have a better design for them.
2511 - Update to the "September 4 2009" ip-to-country file.
2514 Changes in version 0.2.2.1-alpha - 2009-08-26
2515 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
2516 Tor clients to bootstrap on networks where only port 80 is reachable,
2517 makes it more straightforward to support hardware crypto accelerators,
2518 and starts the groundwork for gathering stats safely at relays.
2521 - Start the process of disabling ".exit" address notation, since it
2522 can be used for a variety of esoteric application-level attacks
2523 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
2526 o New directory authorities:
2527 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
2531 - New AccelName and AccelDir options add support for dynamic OpenSSL
2532 hardware crypto acceleration engines.
2533 - Tor now supports tunneling all of its outgoing connections over
2534 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
2535 configuration options. Code by Christopher Davis.
2538 - Send circuit or stream sendme cells when our window has decreased
2539 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
2540 by Karsten when testing the "reduce circuit window" performance
2541 patch. Bugfix on the 54th commit on Tor -- from July 2002,
2542 before the release of Tor 0.0.0. This is the new winner of the
2545 o New options for gathering stats safely:
2546 - Directories that set "DirReqStatistics 1" write statistics on
2547 directory request to disk every 24 hours. As compared to the
2548 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
2549 1) stats are written to disk exactly every 24 hours; 2) estimated
2550 shares of v2 and v3 requests are determined as mean values, not at
2551 the end of a measurement period; 3) unresolved requests are listed
2552 with country code '??'; 4) directories also measure download times.
2553 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
2554 number of exit streams and transferred bytes per port to disk every
2556 - Relays that set "CellStatistics 1" write statistics on how long
2557 cells spend in their circuit queues to disk every 24 hours.
2558 - Entry nodes that set "EntryStatistics 1" write statistics on the
2559 rough number and origins of connecting clients to disk every 24
2561 - Relays that write any of the above statistics to disk and set
2562 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
2563 their extra-info documents.
2566 - New --digests command-line switch to output the digests of the
2567 source files Tor was built with.
2568 - The "torify" script now uses torsocks where available.
2569 - The memarea code now uses a sentinel value at the end of each area
2570 to make sure nothing writes beyond the end of an area. This might
2571 help debug some conceivable causes of bug 930.
2572 - Time and memory units in the configuration file can now be set to
2573 fractional units. For example, "2.5 GB" is now a valid value for
2575 - Certain Tor clients (such as those behind check.torproject.org) may
2576 want to fetch the consensus in an extra early manner. To enable this
2577 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
2578 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
2579 as only certain clients who must have this information sooner should
2581 - Instead of adding the svn revision to the Tor version string, report
2582 the git commit (when we're building from a git checkout).
2585 - If any the v3 certs we download are unparseable, we should actually
2586 notice the failure so we don't retry indefinitely. Bugfix on
2587 0.2.0.x; reported by "rotator".
2588 - If the cached cert file is unparseable, warn but don't exit.
2589 - Fix possible segmentation fault on directory authorities. Bugfix on
2591 - When Tor fails to parse a descriptor of any kind, dump it to disk.
2592 Might help diagnosing bug 1051.
2594 o Deprecated and removed features:
2595 - The controller no longer accepts the old obsolete "addr-mappings/"
2596 or "unregistered-servers-" GETINFO values.
2597 - Hidden services no longer publish version 0 descriptors, and clients
2598 do not request or use version 0 descriptors. However, the old hidden
2599 service authorities still accept and serve version 0 descriptors
2600 when contacted by older hidden services/clients.
2601 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
2602 always on; using them is necessary for correct forward-compatible
2604 - Remove support for .noconnect style addresses. Nobody was using
2605 them, and they provided another avenue for detecting Tor users
2606 via application-level web tricks.
2608 o Packaging changes:
2609 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
2610 installer bundles. See
2611 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
2612 for details of what's new in Vidalia 0.2.3.
2613 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
2614 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
2615 configuration file, rather than the old Privoxy.
2616 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
2617 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
2618 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
2619 better compatibility with OS X 10.6, aka Snow Leopard.
2620 - OS X Vidalia Bundle: The multi-package installer is now replaced
2621 by a simple drag and drop to the /Applications folder. This change
2622 occurred with the upgrade to Vidalia 0.2.3.
2625 Changes in version 0.2.1.19 - 2009-07-28
2626 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
2627 services on Tor 0.2.1.3-alpha through 0.2.1.18.
2630 - Make accessing hidden services on 0.2.1.x work right again.
2631 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
2632 part of patch provided by "optimist".
2635 - When a relay/bridge is writing out its identity key fingerprint to
2636 the "fingerprint" file and to its logs, write it without spaces. Now
2637 it will look like the fingerprints in our bridges documentation,
2638 and confuse fewer users.
2641 - Relays no longer publish a new server descriptor if they change
2642 their MaxAdvertisedBandwidth config option but it doesn't end up
2643 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
2644 fixes bug 1026. Patch from Sebastian.
2645 - Avoid leaking memory every time we get a create cell but we have
2646 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
2647 fixes bug 1034. Reported by BarkerJr.
2650 Changes in version 0.2.1.18 - 2009-07-24
2651 Tor 0.2.1.18 lays the foundations for performance improvements,
2652 adds status events to help users diagnose bootstrap problems, adds
2653 optional authentication/authorization for hidden services, fixes a
2654 variety of potential anonymity problems, and includes a huge pile of
2655 other features and bug fixes.
2658 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
2661 Changes in version 0.2.1.17-rc - 2009-07-07
2662 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
2663 candidate for the 0.2.1.x series. It lays the groundwork for further
2664 client performance improvements, and also fixes a big bug with directory
2665 authorities that were causing them to assign Guard and Stable flags
2668 The Windows bundles also finally include the geoip database that we
2669 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
2670 should actually install Torbutton rather than giving you a cryptic
2671 failure message (oops).
2674 - Clients now use the bandwidth values in the consensus, rather than
2675 the bandwidth values in each relay descriptor. This approach opens
2676 the door to more accurate bandwidth estimates once the directory
2677 authorities start doing active measurements. Implements more of
2681 - When Tor clients restart after 1-5 days, they discard all their
2682 cached descriptors as too old, but they still use the cached
2683 consensus document. This approach is good for robustness, but
2684 bad for performance: since they don't know any bandwidths, they
2685 end up choosing at random rather than weighting their choice by
2686 speed. Fixed by the above feature of putting bandwidths in the
2687 consensus. Bugfix on 0.2.0.x.
2688 - Directory authorities were neglecting to mark relays down in their
2689 internal histories if the relays fall off the routerlist without
2690 ever being found unreachable. So there were relays in the histories
2691 that haven't been seen for eight months, and are listed as being
2692 up for eight months. This wreaked havoc on the "median wfu"
2693 and "median mtbf" calculations, in turn making Guard and Stable
2694 flags very wrong, hurting network performance. Fixes bugs 696 and
2695 969. Bugfix on 0.2.0.6-alpha.
2698 - Serve the DirPortFrontPage page even when we have been approaching
2699 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
2700 - The control port would close the connection before flushing long
2701 replies, such as the network consensus, if a QUIT command was issued
2702 before the reply had completed. Now, the control port flushes all
2703 pending replies before closing the connection. Also fixed a spurious
2704 warning when a QUIT command is issued after a malformed or rejected
2705 AUTHENTICATE command, but before the connection was closed. Patch
2706 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
2707 - When we can't find an intro key for a v2 hidden service descriptor,
2708 fall back to the v0 hidden service descriptor and log a bug message.
2709 Workaround for bug 1024.
2710 - Fix a log message that did not respect the SafeLogging option.
2714 - If we're a relay and we change our IP address, be more verbose
2715 about the reason that made us change. Should help track down
2716 further bugs for relays on dynamic IP addresses.
2719 Changes in version 0.2.0.35 - 2009-06-24
2721 - Avoid crashing in the presence of certain malformed descriptors.
2722 Found by lark, and by automated fuzzing.
2723 - Fix an edge case where a malicious exit relay could convince a
2724 controller that the client's DNS question resolves to an internal IP
2725 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
2728 - Finally fix the bug where dynamic-IP relays disappear when their
2729 IP address changes: directory mirrors were mistakenly telling
2730 them their old address if they asked via begin_dir, so they
2731 never got an accurate answer about their new address, so they
2732 just vanished after a day. For belt-and-suspenders, relays that
2733 don't set Address in their config now avoid using begin_dir for
2734 all direct connections. Should fix bugs 827, 883, and 900.
2735 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
2736 that would occur on some exit nodes when DNS failures and timeouts
2737 occurred in certain patterns. Fix for bug 957.
2740 - When starting with a cache over a few days old, do not leak
2741 memory for the obsolete router descriptors in it. Bugfix on
2742 0.2.0.33; fixes bug 672.
2743 - Hidden service clients didn't use a cached service descriptor that
2744 was older than 15 minutes, but wouldn't fetch a new one either,
2745 because there was already one in the cache. Now, fetch a v2
2746 descriptor unless the same descriptor was added to the cache within
2747 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
2750 Changes in version 0.2.1.16-rc - 2009-06-20
2751 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
2752 a bunch of minor bugs.
2755 - Fix an edge case where a malicious exit relay could convince a
2756 controller that the client's DNS question resolves to an internal IP
2757 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
2759 o Major performance improvements (on 0.2.0.x):
2760 - Disable and refactor some debugging checks that forced a linear scan
2761 over the whole server-side DNS cache. These accounted for over 50%
2762 of CPU time on a relatively busy exit node's gprof profile. Found
2764 - Disable some debugging checks that appeared in exit node profile
2768 - Update to the "June 3 2009" ip-to-country file.
2769 - Do not have tor-resolve automatically refuse all .onion addresses;
2770 if AutomapHostsOnResolve is set in your torrc, this will work fine.
2772 o Minor bugfixes (on 0.2.0.x):
2773 - Log correct error messages for DNS-related network errors on
2775 - Fix a race condition that could cause crashes or memory corruption
2776 when running as a server with a controller listening for log
2778 - Avoid crashing when we have a policy specified in a DirPolicy or
2779 SocksPolicy or ReachableAddresses option with ports set on it,
2780 and we re-load the policy. May fix bug 996.
2781 - Hidden service clients didn't use a cached service descriptor that
2782 was older than 15 minutes, but wouldn't fetch a new one either,
2783 because there was already one in the cache. Now, fetch a v2
2784 descriptor unless the same descriptor was added to the cache within
2785 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
2787 o Minor bugfixes (on 0.2.1.x):
2788 - Don't warn users about low port and hibernation mix when they
2789 provide a *ListenAddress directive to fix that. Bugfix on
2791 - When switching back and forth between bridge mode, do not start
2792 gathering GeoIP data until two hours have passed.
2793 - Do not complain that the user has requested an excluded node as
2794 an exit when the node is not really an exit. This could happen
2795 because the circuit was for testing, or an introduction point.
2799 Changes in version 0.2.1.15-rc - 2009-05-25
2800 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
2801 series. It fixes a major bug on fast exit relays, as well as a variety
2804 o Major bugfixes (on 0.2.0.x):
2805 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
2806 that would occur on some exit nodes when DNS failures and timeouts
2807 occurred in certain patterns. Fix for bug 957.
2809 o Minor bugfixes (on 0.2.0.x):
2810 - Actually return -1 in the error case for read_bandwidth_usage().
2811 Harmless bug, since we currently don't care about the return value
2812 anywhere. Bugfix on 0.2.0.9-alpha.
2813 - Provide a more useful log message if bug 977 (related to buffer
2814 freelists) ever reappears, and do not crash right away.
2815 - Fix an assertion failure on 64-bit platforms when we allocated
2816 memory right up to the end of a memarea, then realigned the memory
2817 one step beyond the end. Fixes a possible cause of bug 930.
2818 - Protect the count of open sockets with a mutex, so we can't
2819 corrupt it when two threads are closing or opening sockets at once.
2820 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
2821 - Don't allow a bridge to publish its router descriptor to a
2822 non-bridge directory authority. Fixes part of bug 932.
2823 - When we change to or from being a bridge, reset our counts of
2824 client usage by country. Fixes bug 932.
2825 - Fix a bug that made stream bandwidth get misreported to the
2827 - Stop using malloc_usable_size() to use more area than we had
2828 actually allocated: it was safe, but made valgrind really unhappy.
2829 - Fix a memory leak when v3 directory authorities load their keys
2830 and cert from disk. Bugfix on 0.2.0.1-alpha.
2832 o Minor bugfixes (on 0.2.1.x):
2833 - Fix use of freed memory when deciding to mark a non-addable
2834 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
2837 Changes in version 0.2.1.14-rc - 2009-04-12
2838 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
2839 series. It begins fixing some major performance problems, and also
2840 finally addresses the bug that was causing relays on dynamic IP
2841 addresses to fall out of the directory.
2844 - Clients replace entry guards that were chosen more than a few months
2845 ago. This change should significantly improve client performance,
2846 especially once more people upgrade, since relays that have been
2847 a guard for a long time are currently overloaded.
2849 o Major bugfixes (on 0.2.0):
2850 - Finally fix the bug where dynamic-IP relays disappear when their
2851 IP address changes: directory mirrors were mistakenly telling
2852 them their old address if they asked via begin_dir, so they
2853 never got an accurate answer about their new address, so they
2854 just vanished after a day. For belt-and-suspenders, relays that
2855 don't set Address in their config now avoid using begin_dir for
2856 all direct connections. Should fix bugs 827, 883, and 900.
2857 - Relays were falling out of the networkstatus consensus for
2858 part of a day if they changed their local config but the
2859 authorities discarded their new descriptor as "not sufficiently
2860 different". Now directory authorities accept a descriptor as changed
2861 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
2863 - Avoid crashing in the presence of certain malformed descriptors.
2864 Found by lark, and by automated fuzzing.
2867 - When generating circuit events with verbose nicknames for
2868 controllers, try harder to look up nicknames for routers on a
2869 circuit. (Previously, we would look in the router descriptors we had
2870 for nicknames, but not in the consensus.) Partial fix for bug 941.
2871 - If the bridge config line doesn't specify a port, assume 443.
2872 This makes bridge lines a bit smaller and easier for users to
2874 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
2875 bytes (aka 20KB/s), to match our documentation. Also update
2876 directory authorities so they always assign the Fast flag to relays
2877 with 20KB/s of capacity. Now people running relays won't suddenly
2878 find themselves not seeing any use, if the network gets faster
2880 - Update to the "April 3 2009" ip-to-country file.
2883 - Avoid trying to print raw memory to the logs when we decide to
2884 give up on downloading a given relay descriptor. Bugfix on
2886 - In tor-resolve, when the Tor client to use is specified by
2887 <hostname>:<port>, actually use the specified port rather than
2888 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
2889 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
2890 - When starting with a cache over a few days old, do not leak
2891 memory for the obsolete router descriptors in it. Bugfix on
2893 - Avoid double-free on list of successfully uploaded hidden
2894 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
2895 - Change memarea_strndup() implementation to work even when
2896 duplicating a string at the end of a page. This bug was
2897 harmless for now, but could have meant crashes later. Fix by
2898 lark. Bugfix on 0.2.1.1-alpha.
2899 - Limit uploaded directory documents to be 16M rather than 500K.
2900 The directory authorities were refusing v3 consensus votes from
2901 other authorities, since the votes are now 504K. Fixes bug 959;
2902 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
2903 - Directory authorities should never send a 503 "busy" response to
2904 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
2908 Changes in version 0.2.1.13-alpha - 2009-03-09
2909 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
2910 cleanups. We're finally getting close to a release candidate.
2913 - Correctly update the list of which countries we exclude as
2914 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
2915 lark. Bugfix on 0.2.1.6-alpha.
2917 o Minor bugfixes (on 0.2.0.x and earlier):
2918 - Automatically detect MacOSX versions earlier than 10.4.0, and
2919 disable kqueue from inside Tor when running with these versions.
2920 We previously did this from the startup script, but that was no
2921 help to people who didn't use the startup script. Resolves bug 863.
2922 - When we had picked an exit node for a connection, but marked it as
2923 "optional", and it turned out we had no onion key for the exit,
2924 stop wanting that exit and try again. This situation may not
2925 be possible now, but will probably become feasible with proposal
2926 158. Spotted by rovv. Fixes another case of bug 752.
2927 - Clients no longer cache certificates for authorities they do not
2928 recognize. Bugfix on 0.2.0.9-alpha.
2929 - When we can't transmit a DNS request due to a network error, retry
2930 it after a while, and eventually transmit a failing response to
2931 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
2932 - If the controller claimed responsibility for a stream, but that
2933 stream never finished making its connection, it would live
2934 forever in circuit_wait state. Now we close it after SocksTimeout
2935 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
2936 - Drop begin cells to a hidden service if they come from the middle
2937 of a circuit. Patch from lark.
2938 - When we erroneously receive two EXTEND cells for the same circuit
2939 ID on the same connection, drop the second. Patch from lark.
2940 - Fix a crash that occurs on exit nodes when a nameserver request
2941 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
2942 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
2944 - Do not assume that a stack-allocated character array will be
2945 64-bit aligned on platforms that demand that uint64_t access is
2946 aligned. Possible fix for bug 604.
2947 - Parse dates and IPv4 addresses in a locale- and libc-independent
2948 manner, to avoid platform-dependent behavior on malformed input.
2949 - Build correctly when configured to build outside the main source
2950 path. Patch from Michael Gold.
2951 - We were already rejecting relay begin cells with destination port
2952 of 0. Now also reject extend cells with destination port or address
2953 of 0. Suggested by lark.
2955 o Minor bugfixes (on 0.2.1.x):
2956 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
2957 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
2958 - If we're an exit node, scrub the IP address to which we are exiting
2959 in the logs. Bugfix on 0.2.1.8-alpha.
2962 - On Linux, use the prctl call to re-enable core dumps when the user
2964 - New controller event NEWCONSENSUS that lists the networkstatus
2965 lines for every recommended relay. Now controllers like Torflow
2966 can keep up-to-date on which relays they should be using.
2967 - Update to the "February 26 2009" ip-to-country file.
2970 Changes in version 0.2.0.34 - 2009-02-08
2971 Tor 0.2.0.34 features several more security-related fixes. You should
2972 upgrade, especially if you run an exit relay (remote crash) or a
2973 directory authority (remote infinite loop), or you're on an older
2974 (pre-XP) or not-recently-patched Windows (remote exploit).
2976 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
2977 have many known flaws, and nobody should be using them. You should
2978 upgrade. If you're using a Linux or BSD and its packages are obsolete,
2979 stop using those packages and upgrade anyway.
2982 - Fix an infinite-loop bug on handling corrupt votes under certain
2983 circumstances. Bugfix on 0.2.0.8-alpha.
2984 - Fix a temporary DoS vulnerability that could be performed by
2985 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
2986 - Avoid a potential crash on exit nodes when processing malformed
2987 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
2988 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
2989 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
2992 - Fix compilation on systems where time_t is a 64-bit integer.
2993 Patch from Matthias Drochner.
2994 - Don't consider expiring already-closed client connections. Fixes
2995 bug 893. Bugfix on 0.0.2pre20.
2998 Changes in version 0.2.1.12-alpha - 2009-02-08
2999 Tor 0.2.1.12-alpha features several more security-related fixes. You
3000 should upgrade, especially if you run an exit relay (remote crash) or
3001 a directory authority (remote infinite loop), or you're on an older
3002 (pre-XP) or not-recently-patched Windows (remote exploit). It also
3003 includes a big pile of minor bugfixes and cleanups.
3006 - Fix an infinite-loop bug on handling corrupt votes under certain
3007 circumstances. Bugfix on 0.2.0.8-alpha.
3008 - Fix a temporary DoS vulnerability that could be performed by
3009 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
3010 - Avoid a potential crash on exit nodes when processing malformed
3011 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
3014 - Let controllers actually ask for the "clients_seen" event for
3015 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
3016 reported by Matt Edman.
3017 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
3019 - Fix a bug in address parsing that was preventing bridges or hidden
3020 service targets from being at IPv6 addresses.
3021 - Solve a bug that kept hardware crypto acceleration from getting
3022 enabled when accounting was turned on. Fixes bug 907. Bugfix on
3024 - Remove a bash-ism from configure.in to build properly on non-Linux
3025 platforms. Bugfix on 0.2.1.1-alpha.
3026 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
3027 headers. Bugfix on 0.2.0.10-alpha.
3028 - Don't consider expiring already-closed client connections. Fixes
3029 bug 893. Bugfix on 0.0.2pre20.
3030 - Fix another interesting corner-case of bug 891 spotted by rovv:
3031 Previously, if two hosts had different amounts of clock drift, and
3032 one of them created a new connection with just the wrong timing,
3033 the other might decide to deprecate the new connection erroneously.
3034 Bugfix on 0.1.1.13-alpha.
3035 - Resolve a very rare crash bug that could occur when the user forced
3036 a nameserver reconfiguration during the middle of a nameserver
3037 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
3038 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
3039 Bugfix on 0.2.1.7-alpha.
3040 - If we're using bridges and our network goes away, be more willing
3041 to forgive our bridges and try again when we get an application
3042 request. Bugfix on 0.2.0.x.
3045 - Support platforms where time_t is 64 bits long. (Congratulations,
3046 NetBSD!) Patch from Matthias Drochner.
3047 - Add a 'getinfo status/clients-seen' controller command, in case
3048 controllers want to hear clients_seen events but connect late.
3051 - Disable GCC's strict alias optimization by default, to avoid the
3052 likelihood of its introducing subtle bugs whenever our code violates
3053 the letter of C99's alias rules.
3056 Changes in version 0.2.0.33 - 2009-01-21
3057 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
3058 useful to users. It also finally fixes a bug where a relay or client
3059 that's been off for many days would take a long time to bootstrap.
3061 This update also fixes an important security-related bug reported by
3062 Ilja van Sprundel. You should upgrade. (We'll send out more details
3063 about the bug once people have had some time to upgrade.)
3066 - Fix a heap-corruption bug that may be remotely triggerable on
3067 some platforms. Reported by Ilja van Sprundel.
3070 - When a stream at an exit relay is in state "resolving" or
3071 "connecting" and it receives an "end" relay cell, the exit relay
3072 would silently ignore the end cell and not close the stream. If
3073 the client never closes the circuit, then the exit relay never
3074 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
3076 - When sending CREATED cells back for a given circuit, use a 64-bit
3077 connection ID to find the right connection, rather than an addr:port
3078 combination. Now that we can have multiple OR connections between
3079 the same ORs, it is no longer possible to use addr:port to uniquely
3080 identify a connection.
3081 - Bridge relays that had DirPort set to 0 would stop fetching
3082 descriptors shortly after startup, and then briefly resume
3083 after a new bandwidth test and/or after publishing a new bridge
3084 descriptor. Bridge users that try to bootstrap from them would
3085 get a recent networkstatus but would get descriptors from up to
3086 18 hours earlier, meaning most of the descriptors were obsolete
3087 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
3088 - Prevent bridge relays from serving their 'extrainfo' document
3089 to anybody who asks, now that extrainfo docs include potentially
3090 sensitive aggregated client geoip summaries. Bugfix on
3092 - If the cached networkstatus consensus is more than five days old,
3093 discard it rather than trying to use it. In theory it could be
3094 useful because it lists alternate directory mirrors, but in practice
3095 it just means we spend many minutes trying directory mirrors that
3096 are long gone from the network. Also discard router descriptors as
3097 we load them if they are more than five days old, since the onion
3098 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
3101 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
3102 could make gcc generate non-functional binary search code. Bugfix
3104 - Build correctly on platforms without socklen_t.
3105 - Compile without warnings on solaris.
3106 - Avoid potential crash on internal error during signature collection.
3107 Fixes bug 864. Patch from rovv.
3108 - Correct handling of possible malformed authority signing key
3109 certificates with internal signature types. Fixes bug 880.
3110 Bugfix on 0.2.0.3-alpha.
3111 - Fix a hard-to-trigger resource leak when logging credential status.
3113 - When we can't initialize DNS because the network is down, do not
3114 automatically stop Tor from starting. Instead, we retry failed
3115 dns_init() every 10 minutes, and change the exit policy to reject
3116 *:* until one succeeds. Fixes bug 691.
3117 - Use 64 bits instead of 32 bits for connection identifiers used with
3118 the controller protocol, to greatly reduce risk of identifier reuse.
3119 - When we're choosing an exit node for a circuit, and we have
3120 no pending streams, choose a good general exit rather than one that
3121 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
3122 - Fix another case of assuming, when a specific exit is requested,
3123 that we know more than the user about what hosts it allows.
3124 Fixes one case of bug 752. Patch from rovv.
3125 - Clip the MaxCircuitDirtiness config option to a minimum of 10
3126 seconds. Warn the user if lower values are given in the
3127 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
3128 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
3129 user if lower values are given in the configuration. Bugfix on
3130 0.1.1.17-rc. Patch by Sebastian.
3131 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
3132 the cache because we already had a v0 descriptor with the same ID.
3133 Bugfix on 0.2.0.18-alpha.
3134 - Fix a race condition when freeing keys shared between main thread
3135 and CPU workers that could result in a memory leak. Bugfix on
3136 0.1.0.1-rc. Fixes bug 889.
3137 - Send a valid END cell back when a client tries to connect to a
3138 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
3139 840. Patch from rovv.
3140 - Check which hops rendezvous stream cells are associated with to
3141 prevent possible guess-the-streamid injection attacks from
3142 intermediate hops. Fixes another case of bug 446. Based on patch
3144 - If a broken client asks a non-exit router to connect somewhere,
3145 do not even do the DNS lookup before rejecting the connection.
3146 Fixes another case of bug 619. Patch from rovv.
3147 - When a relay gets a create cell it can't decrypt (e.g. because it's
3148 using the wrong onion key), we were dropping it and letting the
3149 client time out. Now actually answer with a destroy cell. Fixes
3150 bug 904. Bugfix on 0.0.2pre8.
3152 o Minor bugfixes (hidden services):
3153 - Do not throw away existing introduction points on SIGHUP. Bugfix on
3154 0.0.6pre1. Patch by Karsten. Fixes bug 874.
3157 - Report the case where all signatures in a detached set are rejected
3158 differently than the case where there is an error handling the
3160 - When we realize that another process has modified our cached
3161 descriptors, print out a more useful error message rather than
3162 triggering an assertion. Fixes bug 885. Patch from Karsten.
3163 - Implement the 0x20 hack to better resist DNS poisoning: set the
3164 case on outgoing DNS requests randomly, and reject responses that do
3165 not match the case correctly. This logic can be disabled with the
3166 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
3167 of servers that do not reliably preserve case in replies. See
3168 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
3170 - Check DNS replies for more matching fields to better resist DNS
3172 - Never use OpenSSL compression: it wastes RAM and CPU trying to
3173 compress cells, which are basically all encrypted, compressed, or
3177 Changes in version 0.2.1.11-alpha - 2009-01-20
3178 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
3179 week it will take a long time to bootstrap again" bug. It also fixes
3180 an important security-related bug reported by Ilja van Sprundel. You
3181 should upgrade. (We'll send out more details about the bug once people
3182 have had some time to upgrade.)
3185 - Fix a heap-corruption bug that may be remotely triggerable on
3186 some platforms. Reported by Ilja van Sprundel.
3189 - Discard router descriptors as we load them if they are more than
3190 five days old. Otherwise if Tor is off for a long time and then
3191 starts with cached descriptors, it will try to use the onion
3192 keys in those obsolete descriptors when building circuits. Bugfix
3193 on 0.2.0.x. Fixes bug 887.
3196 - Try to make sure that the version of Libevent we're running with
3197 is binary-compatible with the one we built with. May address bug
3199 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
3200 for bug 905. Bugfix on 0.2.1.7-alpha.
3201 - Add a new --enable-local-appdata configuration switch to change
3202 the default location of the datadir on win32 from APPDATA to
3203 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
3204 entirely. Patch from coderman.
3207 - Make outbound DNS packets respect the OutboundBindAddress setting.
3208 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
3209 - When our circuit fails at the first hop (e.g. we get a destroy
3210 cell back), avoid using that OR connection anymore, and also
3211 tell all the one-hop directory requests waiting for it that they
3212 should fail. Bugfix on 0.2.1.3-alpha.
3213 - In the torify(1) manpage, mention that tsocks will leak your
3217 Changes in version 0.2.1.10-alpha - 2009-01-06
3218 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
3219 would make the bridge relay not so useful if it had DirPort set to 0,
3220 and one that could let an attacker learn a little bit of information
3221 about the bridge's users), and a bug that would cause your Tor relay
3222 to ignore a circuit create request it can't decrypt (rather than reply
3223 with an error). It also fixes a wide variety of other bugs.
3226 - If the cached networkstatus consensus is more than five days old,
3227 discard it rather than trying to use it. In theory it could
3228 be useful because it lists alternate directory mirrors, but in
3229 practice it just means we spend many minutes trying directory
3230 mirrors that are long gone from the network. Helps bug 887 a bit;
3232 - Bridge relays that had DirPort set to 0 would stop fetching
3233 descriptors shortly after startup, and then briefly resume
3234 after a new bandwidth test and/or after publishing a new bridge
3235 descriptor. Bridge users that try to bootstrap from them would
3236 get a recent networkstatus but would get descriptors from up to
3237 18 hours earlier, meaning most of the descriptors were obsolete
3238 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
3239 - Prevent bridge relays from serving their 'extrainfo' document
3240 to anybody who asks, now that extrainfo docs include potentially
3241 sensitive aggregated client geoip summaries. Bugfix on
3245 - New controller event "clients_seen" to report a geoip-based summary
3246 of which countries we've seen clients from recently. Now controllers
3247 like Vidalia can show bridge operators that they're actually making
3249 - Build correctly against versions of OpenSSL 0.9.8 or later built
3250 without support for deprecated functions.
3251 - Update to the "December 19 2008" ip-to-country file.
3253 o Minor bugfixes (on 0.2.0.x):
3254 - Authorities now vote for the Stable flag for any router whose
3255 weighted MTBF is at least 5 days, regardless of the mean MTBF.
3256 - Do not remove routers as too old if we do not have any consensus
3257 document. Bugfix on 0.2.0.7-alpha.
3258 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
3259 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
3260 - When an exit relay resolves a stream address to a local IP address,
3261 do not just keep retrying that same exit relay over and
3262 over. Instead, just close the stream. Addresses bug 872. Bugfix
3263 on 0.2.0.32. Patch from rovv.
3264 - If a hidden service sends us an END cell, do not consider
3265 retrying the connection; just close it. Patch from rovv.
3266 - When we made bridge authorities stop serving bridge descriptors over
3267 unencrypted links, we also broke DirPort reachability testing for
3268 bridges. So bridges with a non-zero DirPort were printing spurious
3269 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
3270 - When a relay gets a create cell it can't decrypt (e.g. because it's
3271 using the wrong onion key), we were dropping it and letting the
3272 client time out. Now actually answer with a destroy cell. Fixes
3273 bug 904. Bugfix on 0.0.2pre8.
3274 - Squeeze 2-5% out of client performance (according to oprofile) by
3275 improving the implementation of some policy-manipulation functions.
3277 o Minor bugfixes (on 0.2.1.x):
3278 - Make get_interface_address() function work properly again; stop
3279 guessing the wrong parts of our address as our address.
3280 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
3281 send on that circuit. Otherwise we might violate the proposal-110
3282 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
3284 - When we're sending non-EXTEND cells to the first hop in a circuit,
3285 for example to use an encrypted directory connection, we don't need
3286 to use RELAY_EARLY cells: the first hop knows what kind of cell
3287 it is, and nobody else can even see the cell type. Conserving
3288 RELAY_EARLY cells makes it easier to cannibalize circuits like
3290 - Stop logging nameserver addresses in reverse order.
3291 - If we are retrying a directory download slowly over and over, do
3292 not automatically give up after the 254th failure. Bugfix on
3294 - Resume reporting accurate "stream end" reasons to the local control
3295 port. They were lost in the changes for Proposal 148. Bugfix on
3298 o Deprecated and removed features:
3299 - The old "tor --version --version" command, which would print out
3300 the subversion "Id" of most of the source files, is now removed. It
3301 turned out to be less useful than we'd expected, and harder to
3304 o Code simplifications and refactoring:
3305 - Change our header file guard macros to be less likely to conflict
3306 with system headers. Adam Langley noticed that we were conflicting
3307 with log.h on Android.
3308 - Tool-assisted documentation cleanup. Nearly every function or
3309 static variable in Tor should have its own documentation now.
3312 Changes in version 0.2.1.9-alpha - 2008-12-25
3313 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
3315 o New directory authorities:
3316 - gabelmoo (the authority run by Karsten Loesing) now has a new
3320 - Never use a connection with a mismatched address to extend a
3321 circuit, unless that connection is canonical. A canonical
3322 connection is one whose address is authenticated by the router's
3323 identity key, either in a NETINFO cell or in a router descriptor.
3324 - Avoid a possible memory corruption bug when receiving hidden service
3325 descriptors. Bugfix on 0.2.1.6-alpha.
3328 - Fix a logic error that would automatically reject all but the first
3329 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
3330 part of bug 813/868. Bug spotted by coderman.
3331 - When a stream at an exit relay is in state "resolving" or
3332 "connecting" and it receives an "end" relay cell, the exit relay
3333 would silently ignore the end cell and not close the stream. If
3334 the client never closes the circuit, then the exit relay never
3335 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
3337 - When we can't initialize DNS because the network is down, do not
3338 automatically stop Tor from starting. Instead, retry failed
3339 dns_init() every 10 minutes, and change the exit policy to reject
3340 *:* until one succeeds. Fixes bug 691.
3343 - Give a better error message when an overzealous init script says
3344 "sudo -u username tor --user username". Makes Bug 882 easier for
3346 - When a directory authority gives us a new guess for our IP address,
3347 log which authority we used. Hopefully this will help us debug
3348 the recent complaints about bad IP address guesses.
3349 - Detect svn revision properly when we're using git-svn.
3350 - Try not to open more than one descriptor-downloading connection
3351 to an authority at once. This should reduce load on directory
3352 authorities. Fixes bug 366.
3353 - Add cross-certification to newly generated certificates, so that
3354 a signing key is enough information to look up a certificate.
3355 Partial implementation of proposal 157.
3356 - Start serving certificates by <identity digest, signing key digest>
3357 pairs. Partial implementation of proposal 157.
3358 - Clients now never report any stream end reason except 'MISC'.
3359 Implements proposal 148.
3360 - On platforms with a maximum syslog string length, truncate syslog
3361 messages to that length ourselves, rather than relying on the
3362 system to do it for us.
3363 - Optimize out calls to time(NULL) that occur for every IO operation,
3364 or for every cell. On systems where time() is a slow syscall,
3365 this fix will be slightly helpful.
3366 - Exit servers can now answer resolve requests for ip6.arpa addresses.
3367 - When we download a descriptor that we then immediately (as
3368 a directory authority) reject, do not retry downloading it right
3369 away. Should save some bandwidth on authorities. Fix for bug
3370 888. Patch by Sebastian Hahn.
3371 - When a download gets us zero good descriptors, do not notify
3372 Tor that new directory information has arrived.
3373 - Avoid some nasty corner cases in the logic for marking connections
3374 as too old or obsolete or noncanonical for circuits. Partial
3377 o Minor features (controller):
3378 - New CONSENSUS_ARRIVED event to note when a new consensus has
3379 been fetched and validated.
3380 - When we realize that another process has modified our cached
3381 descriptors file, print out a more useful error message rather
3382 than triggering an assertion. Fixes bug 885. Patch from Karsten.
3383 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
3384 controllers to prevent SIGHUP from reloading the
3385 configuration. Fixes bug 856.
3388 - Resume using the correct "REASON=" stream when telling the
3389 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
3390 - When a canonical connection appears later in our internal list
3391 than a noncanonical one for a given OR ID, always use the
3392 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
3394 - Clip the MaxCircuitDirtiness config option to a minimum of 10
3395 seconds. Warn the user if lower values are given in the
3396 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
3397 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
3398 user if lower values are given in the configuration. Bugfix on
3399 0.1.1.17-rc. Patch by Sebastian.
3400 - Fix a race condition when freeing keys shared between main thread
3401 and CPU workers that could result in a memory leak. Bugfix on
3402 0.1.0.1-rc. Fixes bug 889.
3404 o Minor bugfixes (hidden services):
3405 - Do not throw away existing introduction points on SIGHUP (bugfix on
3406 0.0.6pre1); also, do not stall hidden services because we're
3407 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
3408 by John Brooks. Patch by Karsten. Fixes bug 874.
3409 - Fix a memory leak when we decline to add a v2 rendezvous
3410 descriptor to the cache because we already had a v0 descriptor
3411 with the same ID. Bugfix on 0.2.0.18-alpha.
3413 o Deprecated and removed features:
3414 - RedirectExits has been removed. It was deprecated since
3416 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
3417 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
3418 - Cell pools are now always enabled; --disable-cell-pools is ignored.
3420 o Code simplifications and refactoring:
3421 - Rename the confusing or_is_obsolete field to the more appropriate
3422 is_bad_for_new_circs, and move it to or_connection_t where it
3424 - Move edge-only flags from connection_t to edge_connection_t: not
3425 only is this better coding, but on machines of plausible alignment,
3426 it should save 4-8 bytes per connection_t. "Every little bit helps."
3427 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
3428 for consistency; keep old option working for backward compatibility.
3429 - Simplify the code for finding connections to use for a circuit.
3432 Changes in version 0.2.1.8-alpha - 2008-12-08
3433 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
3434 builds better on unusual platforms like Solaris and old OS X, and
3435 fixes a variety of other issues.
3438 - New DirPortFrontPage option that takes an html file and publishes
3439 it as "/" on the DirPort. Now relay operators can provide a
3440 disclaimer without needing to set up a separate webserver. There's
3441 a sample disclaimer in contrib/tor-exit-notice.html.
3444 - When the client is choosing entry guards, now it selects at most
3445 one guard from a given relay family. Otherwise we could end up with
3446 all of our entry points into the network run by the same operator.
3447 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
3450 - Fix a DOS opportunity during the voting signature collection process
3451 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
3452 - Fix a possible segfault when establishing an exit connection. Bugfix
3456 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
3458 - Made Tor a little less aggressive about deleting expired
3459 certificates. Partial fix for bug 854.
3460 - Stop doing unaligned memory access that generated bus errors on
3461 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
3462 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
3463 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
3464 - Make USR2 log-level switch take effect immediately. Bugfix on
3466 - If one win32 nameserver fails to get added, continue adding the
3467 rest, and don't automatically fail.
3468 - Use fcntl() for locking when flock() is not available. Should fix
3469 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
3470 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
3471 could make gcc generate non-functional binary search code. Bugfix
3473 - Build correctly on platforms without socklen_t.
3474 - Avoid potential crash on internal error during signature collection.
3475 Fixes bug 864. Patch from rovv.
3476 - Do not use C's stdio library for writing to log files. This will
3477 improve logging performance by a minute amount, and will stop
3478 leaking fds when our disk is full. Fixes bug 861.
3479 - Stop erroneous use of O_APPEND in cases where we did not in fact
3480 want to re-seek to the end of a file before every last write().
3481 - Correct handling of possible malformed authority signing key
3482 certificates with internal signature types. Fixes bug 880. Bugfix
3484 - Fix a hard-to-trigger resource leak when logging credential status.
3488 - Directory mirrors no longer fetch the v1 directory or
3489 running-routers files. They are obsolete, and nobody asks for them
3490 anymore. This is the first step to making v1 authorities obsolete.
3492 o Minor features (controller):
3493 - Return circuit purposes in response to GETINFO circuit-status. Fixes
3497 Changes in version 0.2.0.32 - 2008-11-20
3498 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
3499 packages (and maybe other packages) noticed by Theo de Raadt, fixes
3500 a smaller security flaw that might allow an attacker to access local
3501 services, further improves hidden service performance, and fixes a
3502 variety of other issues.
3505 - The "User" and "Group" config options did not clear the
3506 supplementary group entries for the Tor process. The "User" option
3507 is now more robust, and we now set the groups to the specified
3508 user's primary group. The "Group" option is now ignored. For more
3509 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
3510 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
3511 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
3512 - The "ClientDNSRejectInternalAddresses" config option wasn't being
3513 consistently obeyed: if an exit relay refuses a stream because its
3514 exit policy doesn't allow it, we would remember what IP address
3515 the relay said the destination address resolves to, even if it's
3516 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
3519 - Fix a DOS opportunity during the voting signature collection process
3520 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
3522 o Major bugfixes (hidden services):
3523 - When fetching v0 and v2 rendezvous service descriptors in parallel,
3524 we were failing the whole hidden service request when the v0
3525 descriptor fetch fails, even if the v2 fetch is still pending and
3526 might succeed. Similarly, if the last v2 fetch fails, we were
3527 failing the whole hidden service request even if a v0 fetch is
3528 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
3529 - When extending a circuit to a hidden service directory to upload a
3530 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
3531 requests failed, because the router descriptor has not been
3532 downloaded yet. In these cases, do not attempt to upload the
3533 rendezvous descriptor, but wait until the router descriptor is
3534 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
3535 descriptor from a hidden service directory for which the router
3536 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
3540 - Fix several infrequent memory leaks spotted by Coverity.
3541 - When testing for libevent functions, set the LDFLAGS variable
3542 correctly. Found by Riastradh.
3543 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
3544 bootstrapping with tunneled directory connections. Bugfix on
3545 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
3546 - When asked to connect to A.B.exit:80, if we don't know the IP for A
3547 and we know that server B rejects most-but-not all connections to
3548 port 80, we would previously reject the connection. Now, we assume
3549 the user knows what they were asking for. Fixes bug 752. Bugfix
3550 on 0.0.9rc5. Diagnosed by BarkerJr.
3551 - If we overrun our per-second write limits a little, count this as
3552 having used up our write allocation for the second, and choke
3553 outgoing directory writes. Previously, we had only counted this when
3554 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
3555 Bugfix on 0.2.0.x (??).
3556 - Remove the old v2 directory authority 'lefkada' from the default
3557 list. It has been gone for many months.
3558 - Stop doing unaligned memory access that generated bus errors on
3559 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
3560 - Make USR2 log-level switch take effect immediately. Bugfix on
3563 o Minor bugfixes (controller):
3564 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
3565 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
3568 Changes in version 0.2.1.7-alpha - 2008-11-08
3569 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
3570 packages (and maybe other packages) noticed by Theo de Raadt, fixes
3571 a smaller security flaw that might allow an attacker to access local
3572 services, adds better defense against DNS poisoning attacks on exit
3573 relays, further improves hidden service performance, and fixes a
3574 variety of other issues.
3577 - The "ClientDNSRejectInternalAddresses" config option wasn't being
3578 consistently obeyed: if an exit relay refuses a stream because its
3579 exit policy doesn't allow it, we would remember what IP address
3580 the relay said the destination address resolves to, even if it's
3581 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
3582 - The "User" and "Group" config options did not clear the
3583 supplementary group entries for the Tor process. The "User" option
3584 is now more robust, and we now set the groups to the specified
3585 user's primary group. The "Group" option is now ignored. For more
3586 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
3587 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
3588 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
3589 - Do not use or believe expired v3 authority certificates. Patch
3590 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
3593 - Now NodeFamily and MyFamily config options allow spaces in
3594 identity fingerprints, so it's easier to paste them in.
3595 Suggested by Lucky Green.
3596 - Implement the 0x20 hack to better resist DNS poisoning: set the
3597 case on outgoing DNS requests randomly, and reject responses that do
3598 not match the case correctly. This logic can be disabled with the
3599 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
3600 of servers that do not reliably preserve case in replies. See
3601 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
3603 - Preserve case in replies to DNSPort requests in order to support
3604 the 0x20 hack for resisting DNS poisoning attacks.
3606 o Hidden service performance improvements:
3607 - When the client launches an introduction circuit, retry with a
3608 new circuit after 30 seconds rather than 60 seconds.
3609 - Launch a second client-side introduction circuit in parallel
3610 after a delay of 15 seconds (based on work by Christian Wilms).
3611 - Hidden services start out building five intro circuits rather
3612 than three, and when the first three finish they publish a service
3613 descriptor using those. Now we publish our service descriptor much
3614 faster after restart.
3617 - Minor fix in the warning messages when you're having problems
3618 bootstrapping; also, be more forgiving of bootstrap problems when
3619 we're still making incremental progress on a given bootstrap phase.
3620 - When we're choosing an exit node for a circuit, and we have
3621 no pending streams, choose a good general exit rather than one that
3622 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
3623 - Send a valid END cell back when a client tries to connect to a
3624 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
3625 840. Patch from rovv.
3626 - If a broken client asks a non-exit router to connect somewhere,
3627 do not even do the DNS lookup before rejecting the connection.
3628 Fixes another case of bug 619. Patch from rovv.
3629 - Fix another case of assuming, when a specific exit is requested,
3630 that we know more than the user about what hosts it allows.
3631 Fixes another case of bug 752. Patch from rovv.
3632 - Check which hops rendezvous stream cells are associated with to
3633 prevent possible guess-the-streamid injection attacks from
3634 intermediate hops. Fixes another case of bug 446. Based on patch
3636 - Avoid using a negative right-shift when comparing 32-bit
3637 addresses. Possible fix for bug 845 and bug 811.
3638 - Make the assert_circuit_ok() function work correctly on circuits that
3639 have already been marked for close.
3640 - Fix read-off-the-end-of-string error in unit tests when decoding
3641 introduction points.
3642 - Fix uninitialized size field for memory area allocation: may improve
3643 memory performance during directory parsing.
3644 - Treat duplicate certificate fetches as failures, so that we do
3645 not try to re-fetch an expired certificate over and over and over.
3646 - Do not say we're fetching a certificate when we'll in fact skip it
3647 because of a pending download.
3650 Changes in version 0.2.1.6-alpha - 2008-09-30
3651 Tor 0.2.1.6-alpha further improves performance and robustness of
3652 hidden services, starts work on supporting per-country relay selection,
3653 and fixes a variety of smaller issues.
3656 - Implement proposal 121: make it possible to build hidden services
3657 that only certain clients are allowed to connect to. This is
3658 enforced at several points, so that unauthorized clients are unable
3659 to send INTRODUCE cells to the service, or even (depending on the
3660 type of authentication) to learn introduction points. This feature
3661 raises the bar for certain kinds of active attacks against hidden
3662 services. Code by Karsten Loesing.
3663 - Relays now store and serve v2 hidden service descriptors by default,
3664 i.e., the new default value for HidServDirectoryV2 is 1. This is
3665 the last step in proposal 114, which aims to make hidden service
3666 lookups more reliable.
3667 - Start work to allow node restrictions to include country codes. The
3668 syntax to exclude nodes in a country with country code XX is
3669 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
3670 refinement to decide what config options should take priority if
3671 you ask to both use a particular node and exclude it.
3672 - Allow ExitNodes list to include IP ranges and country codes, just
3673 like the Exclude*Nodes lists. Patch from Robert Hogan.
3676 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
3677 Tor to fail to start if you had it configured to use a bridge
3678 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
3679 - When extending a circuit to a hidden service directory to upload a
3680 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
3681 requests failed, because the router descriptor had not been
3682 downloaded yet. In these cases, we now wait until the router
3683 descriptor is downloaded, and then retry. Likewise, clients
3684 now skip over a hidden service directory if they don't yet have
3685 its router descriptor, rather than futilely requesting it and
3686 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
3688 - When fetching v0 and v2 rendezvous service descriptors in parallel,
3689 we were failing the whole hidden service request when the v0
3690 descriptor fetch fails, even if the v2 fetch is still pending and
3691 might succeed. Similarly, if the last v2 fetch fails, we were
3692 failing the whole hidden service request even if a v0 fetch is
3693 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
3694 - DNS replies need to have names matching their requests, but
3695 these names should be in the questions section, not necessarily
3696 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
3699 - Update to the "September 1 2008" ip-to-country file.
3700 - Allow ports 465 and 587 in the default exit policy again. We had
3701 rejected them in 0.1.0.15, because back in 2005 they were commonly
3702 misconfigured and ended up as spam targets. We hear they are better
3703 locked down these days.
3704 - Use a lockfile to make sure that two Tor processes are not
3705 simultaneously running with the same datadir.
3706 - Serve the latest v3 networkstatus consensus via the control
3707 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
3708 - Better logging about stability/reliability calculations on directory
3710 - Drop the requirement to have an open dir port for storing and
3711 serving v2 hidden service descriptors.
3712 - Directory authorities now serve a /tor/dbg-stability.txt URL to
3713 help debug WFU and MTBF calculations.
3714 - Implement most of Proposal 152: allow specialized servers to permit
3715 single-hop circuits, and clients to use those servers to build
3716 single-hop circuits when using a specialized controller. Patch
3717 from Josh Albrecht. Resolves feature request 768.
3718 - Add a -p option to tor-resolve for specifying the SOCKS port: some
3719 people find host:port too confusing.
3720 - Make TrackHostExit mappings expire a while after their last use, not
3721 after their creation. Patch from Robert Hogan.
3722 - Provide circuit purposes along with circuit events to the controller.
3725 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
3727 - Fixed some memory leaks -- some quite frequent, some almost
3728 impossible to trigger -- based on results from Coverity.
3729 - When testing for libevent functions, set the LDFLAGS variable
3730 correctly. Found by Riastradh.
3731 - Fix an assertion bug in parsing policy-related options; possible fix
3733 - Catch and report a few more bootstrapping failure cases when Tor
3734 fails to establish a TCP connection. Cleanup on 0.2.1.x.
3735 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
3736 bootstrapping with tunneled directory connections. Bugfix on
3737 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
3738 - When asked to connect to A.B.exit:80, if we don't know the IP for A
3739 and we know that server B rejects most-but-not all connections to
3740 port 80, we would previously reject the connection. Now, we assume
3741 the user knows what they were asking for. Fixes bug 752. Bugfix
3742 on 0.0.9rc5. Diagnosed by BarkerJr.
3743 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
3744 service directories if they have no advertised dir port. Bugfix
3746 - If we overrun our per-second write limits a little, count this as
3747 having used up our write allocation for the second, and choke
3748 outgoing directory writes. Previously, we had only counted this when
3749 we had met our limits precisely. Fixes bug 824. Patch by rovv.
3750 Bugfix on 0.2.0.x (??).
3751 - Avoid a "0 divided by 0" calculation when calculating router uptime
3752 at directory authorities. Bugfix on 0.2.0.8-alpha.
3753 - Make DNS resolved controller events into "CLOSED", not
3754 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
3756 - Fix a bug where an unreachable relay would establish enough
3757 reachability testing circuits to do a bandwidth test -- if
3758 we already have a connection to the middle hop of the testing
3759 circuit, then it could establish the last hop by using the existing
3760 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
3761 circuits no longer use entry guards in 0.2.1.3-alpha.
3762 - If we have correct permissions on $datadir, we complain to stdout
3763 and fail to start. But dangerous permissions on
3764 $datadir/cached-status/ would cause us to open a log and complain
3765 there. Now complain to stdout and fail to start in both cases. Fixes
3766 bug 820, reported by seeess.
3767 - Remove the old v2 directory authority 'lefkada' from the default
3768 list. It has been gone for many months.
3770 o Code simplifications and refactoring:
3771 - Revise the connection_new functions so that a more typesafe variant
3772 exists. This will work better with Coverity, and let us find any
3773 actual mistakes we're making here.
3774 - Refactor unit testing logic so that dmalloc can be used sensibly
3775 with unit tests to check for memory leaks.
3776 - Move all hidden-service related fields from connection and circuit
3777 structure to substructures: this way they won't eat so much memory.
3780 Changes in version 0.2.0.31 - 2008-09-03
3781 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
3782 a big bug we're seeing where in rare cases traffic from one Tor stream
3783 gets mixed into another stream, and fixes a variety of smaller issues.
3786 - Make sure that two circuits can never exist on the same connection
3787 with the same circuit ID, even if one is marked for close. This
3788 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
3789 - Relays now reject risky extend cells: if the extend cell includes
3790 a digest of all zeroes, or asks to extend back to the relay that
3791 sent the extend cell, tear down the circuit. Ideas suggested
3793 - If not enough of our entry guards are available so we add a new
3794 one, we might use the new one even if it overlapped with the
3795 current circuit's exit relay (or its family). Anonymity bugfix
3796 pointed out by rovv.
3799 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
3800 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
3801 - Correctly detect the presence of the linux/netfilter_ipv4.h header
3802 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
3803 - Pick size of default geoip filename string correctly on windows.
3804 Fixes bug 806. Bugfix on 0.2.0.30.
3805 - Make the autoconf script accept the obsolete --with-ssl-dir
3806 option as an alias for the actually-working --with-openssl-dir
3807 option. Fix the help documentation to recommend --with-openssl-dir.
3808 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
3809 - When using the TransPort option on OpenBSD, and using the User
3810 option to change UID and drop privileges, make sure to open
3811 /dev/pf before dropping privileges. Fixes bug 782. Patch from
3812 Christopher Davis. Bugfix on 0.1.2.1-alpha.
3813 - Try to attach connections immediately upon receiving a RENDEZVOUS2
3814 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
3815 on the client side when connecting to a hidden service. Bugfix
3816 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
3817 - When closing an application-side connection because its circuit is
3818 getting torn down, generate the stream event correctly. Bugfix on
3819 0.1.2.x. Anonymous patch.
3822 Changes in version 0.2.1.5-alpha - 2008-08-31
3823 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
3824 in a lot of the infrastructure for adding authorization to hidden
3825 services, lays the groundwork for having clients read their load
3826 balancing information out of the networkstatus consensus rather than
3827 the individual router descriptors, addresses two potential anonymity
3828 issues, and fixes a variety of smaller issues.
3831 - Convert many internal address representations to optionally hold
3833 - Generate and accept IPv6 addresses in many protocol elements.
3834 - Make resolver code handle nameservers located at ipv6 addresses.
3835 - Begin implementation of proposal 121 ("Client authorization for
3836 hidden services"): configure hidden services with client
3837 authorization, publish descriptors for them, and configure
3838 authorization data for hidden services at clients. The next
3839 step is to actually access hidden services that perform client
3841 - More progress toward proposal 141: Network status consensus
3842 documents and votes now contain bandwidth information for each
3843 router and a summary of that router's exit policy. Eventually this
3844 will be used by clients so that they do not have to download every
3845 known descriptor before building circuits.
3847 o Major bugfixes (on 0.2.0.x and before):
3848 - When sending CREATED cells back for a given circuit, use a 64-bit
3849 connection ID to find the right connection, rather than an addr:port
3850 combination. Now that we can have multiple OR connections between
3851 the same ORs, it is no longer possible to use addr:port to uniquely
3852 identify a connection.
3853 - Relays now reject risky extend cells: if the extend cell includes
3854 a digest of all zeroes, or asks to extend back to the relay that
3855 sent the extend cell, tear down the circuit. Ideas suggested
3857 - If not enough of our entry guards are available so we add a new
3858 one, we might use the new one even if it overlapped with the
3859 current circuit's exit relay (or its family). Anonymity bugfix
3860 pointed out by rovv.
3863 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
3864 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
3865 - When using the TransPort option on OpenBSD, and using the User
3866 option to change UID and drop privileges, make sure to open /dev/pf
3867 before dropping privileges. Fixes bug 782. Patch from Christopher
3868 Davis. Bugfix on 0.1.2.1-alpha.
3869 - Correctly detect the presence of the linux/netfilter_ipv4.h header
3870 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
3871 - Add a missing safe_str() call for a debug log message.
3872 - Use 64 bits instead of 32 bits for connection identifiers used with
3873 the controller protocol, to greatly reduce risk of identifier reuse.
3874 - Make the autoconf script accept the obsolete --with-ssl-dir
3875 option as an alias for the actually-working --with-openssl-dir
3876 option. Fix the help documentation to recommend --with-openssl-dir.
3877 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
3880 - Rate-limit too-many-sockets messages: when they happen, they happen
3881 a lot. Resolves bug 748.
3882 - Resist DNS poisoning a little better by making sure that names in
3883 answer sections match.
3884 - Print the SOCKS5 error message string as well as the error code
3885 when a tor-resolve request fails. Patch from Jacob.
3888 Changes in version 0.2.1.4-alpha - 2008-08-04
3889 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
3892 - The address part of exit policies was not correctly written
3893 to router descriptors. This generated router descriptors that failed
3894 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
3896 - Tor triggered a false assert when extending a circuit to a relay
3897 but we already have a connection open to that relay. Noticed by
3898 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
3901 - Fix a hidden service logging bug: in some edge cases, the router
3902 descriptor of a previously picked introduction point becomes
3903 obsolete and we need to give up on it rather than continually
3904 complaining that it has become obsolete. Observed by xiando. Bugfix
3908 - Take out the TestVia config option, since it was a workaround for
3909 a bug that was fixed in Tor 0.1.1.21.
3912 Changes in version 0.2.1.3-alpha - 2008-08-03
3913 Tor 0.2.1.3-alpha implements most of the pieces to prevent
3914 infinite-length circuit attacks (see proposal 110); fixes a bug that
3915 might cause exit relays to corrupt streams they send back; allows
3916 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
3917 ExcludeExitNodes config options; and fixes a big pile of bugs.
3919 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
3920 - Send a bootstrap problem "warn" event on the first problem if the
3921 reason is NO_ROUTE (that is, our network is down).
3924 - Implement most of proposal 110: The first K cells to be sent
3925 along a circuit are marked as special "early" cells; only K "early"
3926 cells will be allowed. Once this code is universal, we can block
3927 certain kinds of DOS attack by requiring that EXTEND commands must
3928 be sent using an "early" cell.
3931 - Try to attach connections immediately upon receiving a RENDEZVOUS2
3932 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
3933 on the client side when connecting to a hidden service. Bugfix
3934 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
3935 - Ensure that two circuits can never exist on the same connection
3936 with the same circuit ID, even if one is marked for close. This
3937 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
3940 - When relays do their initial bandwidth measurement, don't limit
3941 to just our entry guards for the test circuits. Otherwise we tend
3942 to have multiple test circuits going through a single entry guard,
3943 which makes our bandwidth test less accurate. Fixes part of bug 654;
3944 patch contributed by Josh Albrecht.
3945 - Add an ExcludeExitNodes option so users can list a set of nodes
3946 that should be be excluded from the exit node position, but
3947 allowed elsewhere. Implements proposal 151.
3948 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
3949 ExcludeNodes and ExcludeExitNodes lists.
3950 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
3951 be more efficient. Formerly it was quadratic in the number of
3952 servers; now it should be linear. Fixes bug 509.
3953 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
3954 and n_conn_id_digest fields into a separate structure that's
3955 only needed when the circuit has not yet attached to an n_conn.
3958 - Change the contrib/tor.logrotate script so it makes the new
3959 logs as "_tor:_tor" rather than the default, which is generally
3960 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
3961 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
3962 warnings (occasionally), but it can also cause the compiler to
3963 eliminate error-checking code. Suggested by Peter Gutmann.
3964 - When a hidden service is giving up on an introduction point candidate
3965 that was not included in the last published rendezvous descriptor,
3966 don't reschedule publication of the next descriptor. Fixes bug 763.
3968 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
3969 HiddenServiceExcludeNodes as obsolete: they never worked properly,
3970 and nobody claims to be using them. Fixes bug 754. Bugfix on
3971 0.1.0.1-rc. Patch from Christian Wilms.
3972 - Fix a small alignment and memory-wasting bug on buffer chunks.
3975 o Minor bugfixes (controller):
3976 - When closing an application-side connection because its circuit
3977 is getting torn down, generate the stream event correctly.
3978 Bugfix on 0.1.2.x. Anonymous patch.
3981 - Remove all backward-compatibility code to support relays running
3982 versions of Tor so old that they no longer work at all on the
3986 Changes in version 0.2.0.30 - 2008-07-15
3988 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
3989 warnings (occasionally), but it can also cause the compiler to
3990 eliminate error-checking code. Suggested by Peter Gutmann.
3993 Changes in version 0.2.0.29-rc - 2008-07-08
3994 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
3995 hidden-service performance bugs, and fixes a bunch of smaller bugs.
3998 - If you have more than one bridge but don't know their keys,
3999 you would only launch a request for the descriptor of the first one
4000 on your list. (Tor considered launching requests for the others, but
4001 found that it already had a connection on the way for $0000...0000
4002 so it didn't open another.) Bugfix on 0.2.0.x.
4003 - If you have more than one bridge but don't know their keys, and the
4004 connection to one of the bridges failed, you would cancel all
4005 pending bridge connections. (After all, they all have the same
4006 digest.) Bugfix on 0.2.0.x.
4007 - When a hidden service was trying to establish an introduction point,
4008 and Tor had built circuits preemptively for such purposes, we
4009 were ignoring all the preemptive circuits and launching a new one
4010 instead. Bugfix on 0.2.0.14-alpha.
4011 - When a hidden service was trying to establish an introduction point,
4012 and Tor *did* manage to reuse one of the preemptively built
4013 circuits, it didn't correctly remember which one it used,
4014 so it asked for another one soon after, until there were no
4015 more preemptive circuits, at which point it launched one from
4016 scratch. Bugfix on 0.0.9.x.
4017 - Make directory servers include the X-Your-Address-Is: http header in
4018 their responses even for begin_dir conns. Now clients who only
4019 ever use begin_dir connections still have a way to learn their IP
4020 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
4023 - Fix a macro/CPP interaction that was confusing some compilers:
4024 some GCCs don't like #if/#endif pairs inside macro arguments.
4026 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
4027 Fixes bug 704; fix from Steven Murdoch.
4028 - When opening /dev/null in finish_daemonize(), do not pass the
4029 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
4030 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
4031 - Correctly detect transparent proxy support on Linux hosts that
4032 require in.h to be included before netfilter_ipv4.h. Patch
4034 - Disallow session resumption attempts during the renegotiation
4035 stage of the v2 handshake protocol. Clients should never be trying
4036 session resumption at this point, but apparently some did, in
4037 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
4038 found by Geoff Goodell.
4041 Changes in version 0.2.1.2-alpha - 2008-06-20
4042 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
4043 make it easier to set up your own private Tor network; fixes several
4044 big bugs with using more than one bridge relay; fixes a big bug with
4045 offering hidden services quickly after Tor starts; and uses a better
4046 API for reporting potential bootstrapping problems to the controller.
4049 - New TestingTorNetwork config option to allow adjustment of
4050 previously constant values that, while reasonable, could slow
4051 bootstrapping. Implements proposal 135. Patch from Karsten.
4054 - If you have more than one bridge but don't know their digests,
4055 you would only learn a request for the descriptor of the first one
4056 on your list. (Tor considered launching requests for the others, but
4057 found that it already had a connection on the way for $0000...0000
4058 so it didn't open another.) Bugfix on 0.2.0.x.
4059 - If you have more than one bridge but don't know their digests,
4060 and the connection to one of the bridges failed, you would cancel
4061 all pending bridge connections. (After all, they all have the
4062 same digest.) Bugfix on 0.2.0.x.
4063 - When establishing a hidden service, introduction points that
4064 originate from cannibalized circuits are completely ignored and not
4065 included in rendezvous service descriptors. This might be another
4066 reason for delay in making a hidden service available. Bugfix
4067 from long ago (0.0.9.x?)
4070 - Allow OpenSSL to use dynamic locks if it wants.
4071 - When building a consensus, do not include routers that are down.
4072 This will cut down 30% to 40% on consensus size. Implements
4074 - In directory authorities' approved-routers files, allow
4075 fingerprints with or without space.
4076 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
4077 controller can query our current bootstrap state in case it attaches
4078 partway through and wants to catch up.
4079 - Send an initial "Starting" bootstrap status event, so we have a
4080 state to start out in.
4083 - Asking for a conditional consensus at .../consensus/<fingerprints>
4084 would crash a dirserver if it did not already have a
4085 consensus. Bugfix on 0.2.1.1-alpha.
4086 - Clean up some macro/CPP interactions: some GCC versions don't like
4087 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
4090 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
4091 - Directory authorities shouldn't complain about bootstrapping
4092 problems just because they do a lot of reachability testing and
4093 some of the connection attempts fail.
4094 - Start sending "count" and "recommendation" key/value pairs in
4095 bootstrap problem status events, so the controller can hear about
4096 problems even before Tor decides they're worth reporting for sure.
4097 - If you're using bridges, generate "bootstrap problem" warnings
4098 as soon as you run out of working bridges, rather than waiting
4099 for ten failures -- which will never happen if you have less than
4101 - If we close our OR connection because there's been a circuit
4102 pending on it for too long, we were telling our bootstrap status
4103 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
4106 Changes in version 0.2.1.1-alpha - 2008-06-13
4107 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
4108 were making the Tor process bloat especially on Linux; makes our TLS
4109 handshake blend in better; sends "bootstrap phase" status events to
4110 the controller, so it can keep the user informed of progress (and
4111 problems) fetching directory information and establishing circuits;
4112 and adds a variety of smaller features.
4115 - More work on making our TLS handshake blend in: modify the list
4116 of ciphers advertised by OpenSSL in client mode to even more
4117 closely resemble a common web browser. We cheat a little so that
4118 we can advertise ciphers that the locally installed OpenSSL doesn't
4120 - Start sending "bootstrap phase" status events to the controller,
4121 so it can keep the user informed of progress fetching directory
4122 information and establishing circuits. Also inform the controller
4123 if we think we're stuck at a particular bootstrap phase. Implements
4125 - Resume using OpenSSL's RAND_poll() for better (and more portable)
4126 cross-platform entropy collection again. We used to use it, then
4127 stopped using it because of a bug that could crash systems that
4128 called RAND_poll when they had a lot of fds open. It looks like the
4129 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
4130 at startup, and to call RAND_poll() when we reseed later only if
4131 we have a non-buggy OpenSSL version.
4134 - When we choose to abandon a new entry guard because we think our
4135 older ones might be better, close any circuits pending on that
4136 new entry guard connection. This fix should make us recover much
4137 faster when our network is down and then comes back. Bugfix on
4138 0.1.2.8-beta; found by lodger.
4140 o Memory fixes and improvements:
4141 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
4142 to avoid unused RAM in buffer chunks and memory pools.
4143 - Speed up parsing and cut down on memory fragmentation by using
4144 stack-style allocations for parsing directory objects. Previously,
4145 this accounted for over 40% of allocations from within Tor's code
4146 on a typical directory cache.
4147 - Use a Bloom filter rather than a digest-based set to track which
4148 descriptors we need to keep around when we're cleaning out old
4149 router descriptors. This speeds up the computation significantly,
4150 and may reduce fragmentation.
4151 - Reduce the default smartlist size from 32 to 16; it turns out that
4152 most smartlists hold around 8-12 elements tops.
4153 - Make dumpstats() log the fullness and size of openssl-internal
4155 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
4156 patch to their OpenSSL, turn it on to save memory on servers. This
4157 patch will (with any luck) get included in a mainline distribution
4159 - Never use OpenSSL compression: it wastes RAM and CPU trying to
4160 compress cells, which are basically all encrypted, compressed,
4164 - Stop reloading the router list from disk for no reason when we
4165 run out of reachable directory mirrors. Once upon a time reloading
4166 it would set the 'is_running' flag back to 1 for them. It hasn't
4167 done that for a long time.
4168 - In very rare situations new hidden service descriptors were
4169 published earlier than 30 seconds after the last change to the
4170 service. (We currently think that a hidden service descriptor
4171 that's been stable for 30 seconds is worth publishing.)
4174 - Allow separate log levels to be configured for different logging
4175 domains. For example, this allows one to log all notices, warnings,
4176 or errors, plus all memory management messages of level debug or
4177 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
4178 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
4179 and stop using a warning that had become unfixably verbose under
4181 - New --hush command-line option similar to --quiet. While --quiet
4182 disables all logging to the console on startup, --hush limits the
4183 output to messages of warning and error severity.
4184 - Servers support a new URL scheme for consensus downloads that
4185 allows the client to specify which authorities are trusted.
4186 The server then only sends the consensus if the client will trust
4187 it. Otherwise a 404 error is sent back. Clients use this
4188 new scheme when the server supports it (meaning it's running
4189 0.2.1.1-alpha or later). Implements proposal 134.
4190 - New configure/torrc options (--enable-geoip-stats,
4191 DirRecordUsageByCountry) to record how many IPs we've served
4192 directory info to in each country code, how many status documents
4193 total we've sent to each country code, and what share of the total
4194 directory requests we should expect to see.
4195 - Use the TLS1 hostname extension to more closely resemble browser
4197 - Lots of new unit tests.
4198 - Add a macro to implement the common pattern of iterating through
4199 two parallel lists in lockstep.
4202 Changes in version 0.2.0.28-rc - 2008-06-13
4203 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
4204 performance bug, and fixes a bunch of smaller bugs.
4207 - Fix a bug where, when we were choosing the 'end stream reason' to
4208 put in our relay end cell that we send to the exit relay, Tor
4209 clients on Windows were sometimes sending the wrong 'reason'. The
4210 anonymity problem is that exit relays may be able to guess whether
4211 the client is running Windows, thus helping partition the anonymity
4212 set. Down the road we should stop sending reasons to exit relays,
4213 or otherwise prevent future versions of this bug.
4216 - While setting up a hidden service, some valid introduction circuits
4217 were overlooked and abandoned. This might be the reason for
4218 the long delay in making a hidden service available. Bugfix on
4222 - Update to the "June 9 2008" ip-to-country file.
4223 - Run 'make test' as part of 'make dist', so we stop releasing so
4224 many development snapshots that fail their unit tests.
4227 - When we're checking if we have enough dir info for each relay
4228 to begin establishing circuits, make sure that we actually have
4229 the descriptor listed in the consensus, not just any descriptor.
4231 - Bridge relays no longer print "xx=0" in their extrainfo document
4232 for every single country code in the geoip db. Bugfix on
4234 - Only warn when we fail to load the geoip file if we were planning to
4235 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
4236 - If we change our MaxAdvertisedBandwidth and then reload torrc,
4237 Tor won't realize it should publish a new relay descriptor. Fixes
4238 bug 688, reported by mfr. Bugfix on 0.1.2.x.
4239 - When we haven't had any application requests lately, don't bother
4240 logging that we have expired a bunch of descriptors. Bugfix
4242 - Make relay cells written on a connection count as non-padding when
4243 tracking how long a connection has been in use. Bugfix on
4244 0.2.0.1-alpha. Spotted by lodger.
4245 - Fix unit tests in 0.2.0.27-rc.
4246 - Fix compile on Windows.
4249 Changes in version 0.2.0.27-rc - 2008-06-03
4250 Tor 0.2.0.27-rc adds a few features we left out of the earlier
4251 release candidates. In particular, we now include an IP-to-country
4252 GeoIP database, so controllers can easily look up what country a
4253 given relay is in, and so bridge relays can give us some sanitized
4254 summaries about which countries are making use of bridges. (See proposal
4255 126-geoip-fetching.txt for details.)
4258 - Include an IP-to-country GeoIP file in the tarball, so bridge
4259 relays can report sanitized summaries of the usage they're seeing.
4262 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
4263 Robert Hogan. Fixes the first part of bug 681.
4264 - Make bridge authorities never serve extrainfo docs.
4265 - Add support to detect Libevent versions in the 1.4.x series
4267 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
4268 - Include a new contrib/tor-exit-notice.html file that exit relay
4269 operators can put on their website to help reduce abuse queries.
4272 - When tunneling an encrypted directory connection, and its first
4273 circuit fails, do not leave it unattached and ask the controller
4274 to deal. Fixes the second part of bug 681.
4275 - Make bridge authorities correctly expire old extrainfo documents
4279 Changes in version 0.2.0.26-rc - 2008-05-13
4280 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
4281 in Debian's OpenSSL packages. All users running any 0.2.0.x version
4282 should upgrade, whether they're running Debian or not.
4284 o Major security fixes:
4285 - Use new V3 directory authority keys on the tor26, gabelmoo, and
4286 moria1 V3 directory authorities. The old keys were generated with
4287 a vulnerable version of Debian's OpenSSL package, and must be
4288 considered compromised. Other authorities' keys were not generated
4289 with an affected version of OpenSSL.
4292 - List authority signatures as "unrecognized" based on DirServer
4293 lines, not on cert cache. Bugfix on 0.2.0.x.
4296 - Add a new V3AuthUseLegacyKey option to make it easier for
4297 authorities to change their identity keys if they have to.
4300 Changes in version 0.2.0.25-rc - 2008-04-23
4301 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
4304 - Remember to initialize threading before initializing logging.
4305 Otherwise, many BSD-family implementations will crash hard on
4306 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
4309 - Authorities correctly free policies on bad servers on
4310 exit. Fixes bug 672. Bugfix on 0.2.0.x.
4313 Changes in version 0.2.0.24-rc - 2008-04-22
4314 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
4315 v3 directory authority, makes relays with dynamic IP addresses and no
4316 DirPort notice more quickly when their IP address changes, fixes a few
4317 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
4319 o New directory authorities:
4320 - Take lefkada out of the list of v3 directory authorities, since
4321 it has been down for months.
4322 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
4326 - Detect address changes more quickly on non-directory mirror
4327 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
4329 o Minor features (security):
4330 - Reject requests for reverse-dns lookup of names that are in
4331 a private address space. Patch from lodger.
4332 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
4335 o Minor bugfixes (crashes):
4336 - Avoid a rare assert that can trigger when Tor doesn't have much
4337 directory information yet and it tries to fetch a v2 hidden
4338 service descriptor. Fixes bug 651, reported by nwf.
4339 - Initialize log mutex before initializing dmalloc. Otherwise,
4340 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
4341 - Use recursive pthread mutexes in order to avoid deadlock when
4342 logging debug-level messages to a controller. Bug spotted by nwf,
4343 bugfix on 0.2.0.16-alpha.
4345 o Minor bugfixes (resource management):
4346 - Keep address policies from leaking memory: start their refcount
4347 at 1, not 2. Bugfix on 0.2.0.16-alpha.
4348 - Free authority certificates on exit, so they don't look like memory
4349 leaks. Bugfix on 0.2.0.19-alpha.
4350 - Free static hashtables for policy maps and for TLS connections on
4351 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
4352 - Avoid allocating extra space when computing consensuses on 64-bit
4353 platforms. Bug spotted by aakova.
4355 o Minor bugfixes (misc):
4356 - Do not read the configuration file when we've only been told to
4357 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
4358 based on patch from Sebastian Hahn.
4359 - Exit relays that are used as a client can now reach themselves
4360 using the .exit notation, rather than just launching an infinite
4361 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
4362 - When attempting to open a logfile fails, tell us why.
4363 - Fix a dumb bug that was preventing us from knowing that we should
4364 preemptively build circuits to handle expected directory requests.
4365 Fixes bug 660. Bugfix on 0.1.2.x.
4366 - Warn less verbosely about clock skew from netinfo cells from
4367 untrusted sources. Fixes bug 663.
4368 - Make controller stream events for DNS requests more consistent,
4369 by adding "new stream" events for DNS requests, and removing
4370 spurious "stream closed" events" for cached reverse resolves.
4371 Patch from mwenge. Fixes bug 646.
4372 - Correctly notify one-hop connections when a circuit build has
4373 failed. Possible fix for bug 669. Found by lodger.
4376 Changes in version 0.2.0.23-rc - 2008-03-24
4377 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
4378 makes bootstrapping faster if the first directory mirror you contact
4379 is down. The bundles also include the new Vidalia 0.1.2 release.
4382 - When a tunneled directory request is made to a directory server
4383 that's down, notice after 30 seconds rather than 120 seconds. Also,
4384 fail any begindir streams that are pending on it, so they can
4385 retry elsewhere. This was causing multi-minute delays on bootstrap.
4388 Changes in version 0.2.0.22-rc - 2008-03-18
4389 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
4390 enables encrypted directory connections by default for non-relays, fixes
4391 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
4392 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
4395 - Enable encrypted directory connections by default for non-relays,
4396 so censor tools that block Tor directory connections based on their
4397 plaintext patterns will no longer work. This means Tor works in
4398 certain censored countries by default again.
4401 - Make sure servers always request certificates from clients during
4402 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
4403 - Do not enter a CPU-eating loop when a connection is closed in
4404 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
4405 diagnosed by lodger; bugfix on 0.2.0.20-rc.
4406 - Fix assertion failure that could occur when a blocked circuit
4407 became unblocked, and it had pending client DNS requests. Bugfix
4408 on 0.2.0.1-alpha. Fixes bug 632.
4410 o Minor bugfixes (on 0.1.2.x):
4411 - Generate "STATUS_SERVER" events rather than misspelled
4412 "STATUS_SEVER" events. Caught by mwenge.
4413 - When counting the number of bytes written on a TLS connection,
4414 look at the BIO actually used for writing to the network, not
4415 at the BIO used (sometimes) to buffer data for the network.
4416 Looking at different BIOs could result in write counts on the
4417 order of ULONG_MAX. Fixes bug 614.
4418 - On Windows, correctly detect errors when listing the contents of
4419 a directory. Fix from lodger.
4421 o Minor bugfixes (on 0.2.0.x):
4422 - Downgrade "sslv3 alert handshake failure" message to INFO.
4423 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
4424 left BandwidthRate and BandwidthBurst at the default, we would be
4425 silently limited by those defaults. Now raise them to match the
4426 RelayBandwidth* values.
4427 - Fix the SVK version detection logic to work correctly on a branch.
4428 - Make --enable-openbsd-malloc work correctly on Linux with alpha
4429 CPUs. Fixes bug 625.
4430 - Logging functions now check that the passed severity is sane.
4431 - Use proper log levels in the testsuite call of
4432 get_interface_address6().
4433 - When using a nonstandard malloc, do not use the platform values for
4434 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
4435 - Make the openbsd malloc code use 8k pages on alpha CPUs and
4437 - Detect mismatched page sizes when using --enable-openbsd-malloc.
4438 - Avoid double-marked-for-close warning when certain kinds of invalid
4439 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
4440 for bug 617. Bugfix on 0.2.0.1-alpha.
4441 - Make sure that the "NULL-means-reject *:*" convention is followed by
4442 all the policy manipulation functions, avoiding some possible crash
4443 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
4444 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
4445 actually works, and doesn't warn about every single reverse lookup.
4446 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
4449 - Only log guard node status when guard node status has changed.
4450 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
4451 make "INFO" 75% less verbose.
4454 Changes in version 0.2.0.21-rc - 2008-03-02
4455 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
4456 makes Tor work well with Vidalia again, fixes a rare assert bug,
4457 and fixes a pair of more minor bugs. The bundles also include Vidalia
4458 0.1.0 and Torbutton 1.1.16.
4461 - The control port should declare that it requires password auth
4462 when HashedControlSessionPassword is set too. Patch from Matt Edman;
4463 bugfix on 0.2.0.20-rc. Fixes bug 615.
4464 - Downgrade assert in connection_buckets_decrement() to a log message.
4465 This may help us solve bug 614, and in any case will make its
4466 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
4467 - We were sometimes miscounting the number of bytes read from the
4468 network, causing our rate limiting to not be followed exactly.
4469 Bugfix on 0.2.0.16-alpha. Reported by lodger.
4472 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
4473 OpenSSL versions should have been working fine. Diagnosis and patch
4474 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
4475 Bugfix on 0.2.0.20-rc.
4478 Changes in version 0.2.0.20-rc - 2008-02-24
4479 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
4480 makes more progress towards normalizing Tor's TLS handshake, makes
4481 hidden services work better again, helps relays bootstrap if they don't
4482 know their IP address, adds optional support for linking in openbsd's
4483 allocator or tcmalloc, allows really fast relays to scale past 15000
4484 sockets, and fixes a bunch of minor bugs reported by Veracode.
4487 - Enable the revised TLS handshake based on the one designed by
4488 Steven Murdoch in proposal 124, as revised in proposal 130. It
4489 includes version negotiation for OR connections as described in
4490 proposal 105. The new handshake is meant to be harder for censors
4491 to fingerprint, and it adds the ability to detect certain kinds of
4492 man-in-the-middle traffic analysis attacks. The version negotiation
4493 feature will allow us to improve Tor's link protocol more safely
4495 - Choose which bridge to use proportional to its advertised bandwidth,
4496 rather than uniformly at random. This should speed up Tor for
4497 bridge users. Also do this for people who set StrictEntryNodes.
4498 - When a TrackHostExits-chosen exit fails too many times in a row,
4499 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
4502 - Resolved problems with (re-)fetching hidden service descriptors.
4503 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
4505 - If we only ever used Tor for hidden service lookups or posts, we
4506 would stop building circuits and start refusing connections after
4507 24 hours, since we falsely believed that Tor was dormant. Reported
4508 by nwf; bugfix on 0.1.2.x.
4509 - Servers that don't know their own IP address should go to the
4510 authorities for their first directory fetch, even if their DirPort
4511 is off or if they don't know they're reachable yet. This will help
4512 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
4513 - When counting the number of open sockets, count not only the number
4514 of sockets we have received from the socket() call, but also
4515 the number we've gotten from accept() and socketpair(). This bug
4516 made us fail to count all sockets that we were using for incoming
4517 connections. Bugfix on 0.2.0.x.
4518 - Fix code used to find strings within buffers, when those strings
4519 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
4520 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
4521 - Add a new __HashedControlSessionPassword option for controllers
4522 to use for one-off session password hashes that shouldn't get
4523 saved to disk by SAVECONF --- Vidalia users were accumulating a
4524 pile of HashedControlPassword lines in their torrc files, one for
4525 each time they had restarted Tor and then clicked Save. Make Tor
4526 automatically convert "HashedControlPassword" to this new option but
4527 only when it's given on the command line. Partial fix for bug 586.
4529 o Minor features (performance):
4530 - Tune parameters for cell pool allocation to minimize amount of
4532 - Add OpenBSD malloc code from phk as an optional malloc
4533 replacement on Linux: some glibc libraries do very poorly
4534 with Tor's memory allocation patterns. Pass
4535 --enable-openbsd-malloc to get the replacement malloc code.
4536 - Add a --with-tcmalloc option to the configure script to link
4537 against tcmalloc (if present). Does not yet search for
4538 non-system include paths.
4539 - Stop imposing an arbitrary maximum on the number of file descriptors
4540 used for busy servers. Bug reported by Olaf Selke; patch from
4543 o Minor features (other):
4544 - When SafeLogging is disabled, log addresses along with all TLS
4546 - When building with --enable-gcc-warnings, check for whether Apple's
4547 warning "-Wshorten-64-to-32" is available.
4548 - Add a --passphrase-fd argument to the tor-gencert command for
4551 o Minor bugfixes (memory leaks and code problems):
4552 - We were leaking a file descriptor if Tor started with a zero-length
4553 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
4554 - Detect size overflow in zlib code. Reported by Justin Ferguson and
4556 - We were comparing the raw BridgePassword entry with a base64'ed
4557 version of it, when handling a "/tor/networkstatus-bridges"
4558 directory request. Now compare correctly. Noticed by Veracode.
4559 - Recover from bad tracked-since value in MTBF-history file.
4561 - Alter the code that tries to recover from unhandled write
4562 errors, to not try to flush onto a socket that's given us
4563 unhandled errors. Bugfix on 0.1.2.x.
4564 - Make Unix controlsockets work correctly on OpenBSD. Patch from
4565 tup. Bugfix on 0.2.0.3-alpha.
4567 o Minor bugfixes (other):
4568 - If we have an extra-info document for our server, always make
4569 it available on the control port, even if we haven't gotten
4570 a copy of it from an authority yet. Patch from mwenge.
4571 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
4572 - Directory mirrors no longer include a guess at the client's IP
4573 address if the connection appears to be coming from the same /24
4574 network; it was producing too many wrong guesses.
4575 - Make the new hidden service code respect the SafeLogging setting.
4576 Bugfix on 0.2.0.x. Patch from Karsten.
4577 - When starting as an authority, do not overwrite all certificates
4578 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
4579 - If we're trying to flush the last bytes on a connection (for
4580 example, when answering a directory request), reset the
4581 time-to-give-up timeout every time we manage to write something
4582 on the socket. Bugfix on 0.1.2.x.
4583 - Change the behavior of "getinfo status/good-server-descriptor"
4584 so it doesn't return failure when any authority disappears.
4585 - Even though the man page said that "TrackHostExits ." should
4586 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
4587 - Report TLS "zero return" case as a "clean close" and "IO error"
4588 as a "close". Stop calling closes "unexpected closes": existing
4589 Tors don't use SSL_close(), so having a connection close without
4590 the TLS shutdown handshake is hardly unexpected.
4591 - Send NAMESERVER_STATUS messages for a single failed nameserver
4594 o Code simplifications and refactoring:
4595 - Remove the tor_strpartition function: its logic was confused,
4596 and it was only used for one thing that could be implemented far
4600 Changes in version 0.2.0.19-alpha - 2008-02-09
4601 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
4602 handshake, makes path selection for relays more secure and IP address
4603 guessing more robust, and generally fixes a lot of bugs in preparation
4604 for calling the 0.2.0 branch stable.
4607 - Do not include recognizeable strings in the commonname part of
4608 Tor's x509 certificates.
4611 - If we're a relay, avoid picking ourselves as an introduction point,
4612 a rendezvous point, or as the final hop for internal circuits. Bug
4613 reported by taranis and lodger. Bugfix on 0.1.2.x.
4614 - Patch from "Andrew S. Lists" to catch when we contact a directory
4615 mirror at IP address X and he says we look like we're coming from
4616 IP address X. Bugfix on 0.1.2.x.
4618 o Minor features (security):
4619 - Be more paranoid about overwriting sensitive memory on free(),
4620 as a defensive programming tactic to ensure forward secrecy.
4622 o Minor features (directory authority):
4623 - Actually validate the options passed to AuthDirReject,
4624 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
4625 - Reject router descriptors with out-of-range bandwidthcapacity or
4626 bandwidthburst values.
4628 o Minor features (controller):
4629 - Reject controller commands over 1MB in length. This keeps rogue
4630 processes from running us out of memory.
4632 o Minor features (misc):
4633 - Give more descriptive well-formedness errors for out-of-range
4634 hidden service descriptor/protocol versions.
4635 - Make memory debugging information describe more about history
4636 of cell allocation, so we can help reduce our memory use.
4638 o Deprecated features (controller):
4639 - The status/version/num-versioning and status/version/num-concurring
4640 GETINFO options are no longer useful in the v3 directory protocol:
4641 treat them as deprecated, and warn when they're used.
4644 - When our consensus networkstatus has been expired for a while, stop
4645 being willing to build circuits using it. Fixes bug 401. Bugfix
4647 - Directory caches now fetch certificates from all authorities
4648 listed in a networkstatus consensus, even when they do not
4649 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
4650 - When connecting to a bridge without specifying its key, insert
4651 the connection into the identity-to-connection map as soon as
4652 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
4653 - Detect versions of OS X where malloc_good_size() is present in the
4654 library but never actually declared. Resolves bug 587. Bugfix
4656 - Stop incorrectly truncating zlib responses to directory authority
4657 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
4658 - Stop recommending that every server operator send mail to tor-ops.
4659 Resolves bug 597. Bugfix on 0.1.2.x.
4660 - Don't trigger an assert if we start a directory authority with a
4661 private IP address (like 127.0.0.1).
4662 - Avoid possible failures when generating a directory with routers
4663 with over-long versions strings, or too many flags set. Bugfix
4665 - If an attempt to launch a DNS resolve request over the control
4666 port fails because we have overrun the limit on the number of
4667 connections, tell the controller that the request has failed.
4668 - Avoid using too little bandwidth when our clock skips a few
4669 seconds. Bugfix on 0.1.2.x.
4670 - Fix shell error when warning about missing packages in configure
4671 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
4672 - Do not become confused when receiving a spurious VERSIONS-like
4673 cell from a confused v1 client. Bugfix on 0.2.0.x.
4674 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
4675 introduction points for a hidden service have failed. Patch from
4676 Karsten Loesing. Bugfix on 0.2.0.x.
4678 o Code simplifications and refactoring:
4679 - Remove some needless generality from cpuworker code, for improved
4681 - Stop overloading the circuit_t.onionskin field for both "onionskin
4682 from a CREATE cell that we are waiting for a cpuworker to be
4683 assigned" and "onionskin from an EXTEND cell that we are going to
4684 send to an OR as soon as we are connected". Might help with bug 600.
4685 - Add an in-place version of aes_crypt() so that we can avoid doing a
4686 needless memcpy() call on each cell payload.
4689 Changes in version 0.2.0.18-alpha - 2008-01-25
4690 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
4691 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
4692 that can warn or reject connections to ports generally associated with
4693 vulnerable-plaintext protocols.
4695 o New directory authorities:
4696 - Set up dannenberg (run by CCC) as the sixth v3 directory
4700 - Fix a major memory leak when attempting to use the v2 TLS
4701 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
4702 - We accidentally enabled the under-development v2 TLS handshake
4703 code, which was causing log entries like "TLS error while
4704 renegotiating handshake". Disable it again. Resolves bug 590.
4705 - We were computing the wrong Content-Length: header for directory
4706 responses that need to be compressed on the fly, causing clients
4707 asking for those items to always fail. Bugfix on 0.2.0.x; partially
4711 - Avoid going directly to the directory authorities even if you're a
4712 relay, if you haven't found yourself reachable yet or if you've
4713 decided not to advertise your dirport yet. Addresses bug 556.
4714 - If we've gone 12 hours since our last bandwidth check, and we
4715 estimate we have less than 50KB bandwidth capacity but we could
4716 handle more, do another bandwidth test.
4717 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
4718 Tor can warn and/or refuse connections to ports commonly used with
4719 vulnerable-plaintext protocols. Currently we warn on ports 23,
4720 109, 110, and 143, but we don't reject any.
4723 - When we setconf ClientOnly to 1, close any current OR and Dir
4724 listeners. Reported by mwenge.
4725 - When we get a consensus that's been signed by more people than
4726 we expect, don't log about it; it's not a big deal. Reported
4730 - Don't answer "/tor/networkstatus-bridges" directory requests if
4731 the request isn't encrypted.
4732 - Make "ClientOnly 1" config option disable directory ports too.
4733 - Patches from Karsten Loesing to make v2 hidden services more
4734 robust: work even when there aren't enough HSDir relays available;
4735 retry when a v2 rend desc fetch fails; but don't retry if we
4736 already have a usable v0 rend desc.
4739 Changes in version 0.2.0.17-alpha - 2008-01-17
4740 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
4743 - Make the tor-gencert man page get included correctly in the tarball.
4746 Changes in version 0.2.0.16-alpha - 2008-01-17
4747 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
4748 Loesing, and generally cleans up a lot of features and minor bugs.
4750 o New directory authorities:
4751 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
4754 o Major performance improvements:
4755 - Switch our old ring buffer implementation for one more like that
4756 used by free Unix kernels. The wasted space in a buffer with 1mb
4757 of data will now be more like 8k than 1mb. The new implementation
4758 also avoids realloc();realloc(); patterns that can contribute to
4759 memory fragmentation.
4762 - Configuration files now accept C-style strings as values. This
4763 helps encode characters not allowed in the current configuration
4764 file format, such as newline or #. Addresses bug 557.
4765 - Although we fixed bug 539 (where servers would send HTTP status 503
4766 responses _and_ send a body too), there are still servers out
4767 there that haven't upgraded. Therefore, make clients parse such
4768 bodies when they receive them.
4769 - When we're not serving v2 directory information, there is no reason
4770 to actually keep any around. Remove the obsolete files and directory
4771 on startup if they are very old and we aren't going to serve them.
4773 o Minor performance improvements:
4774 - Reference-count and share copies of address policy entries; only 5%
4775 of them were actually distinct.
4776 - Never walk through the list of logs if we know that no log is
4777 interested in a given message.
4780 - When an authority has not signed a consensus, do not try to
4781 download a nonexistent "certificate with key 00000000". Bugfix
4782 on 0.2.0.x. Fixes bug 569.
4783 - Fix a rare assert error when we're closing one of our threads:
4784 use a mutex to protect the list of logs, so we never write to the
4785 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
4786 bug 575, which is kind of the revenge of bug 222.
4787 - Patch from Karsten Loesing to complain less at both the client
4788 and the relay when a relay used to have the HSDir flag but doesn't
4789 anymore, and we try to upload a hidden service descriptor.
4790 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
4792 - Do not try to download missing certificates until we have tried
4793 to check our fallback consensus. Fixes bug 583.
4794 - Make bridges round reported GeoIP stats info up to the nearest
4795 estimate, not down. Now we can distinguish between "0 people from
4796 this country" and "1 person from this country".
4797 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
4798 - Avoid possible segfault if key generation fails in
4799 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
4800 - Avoid segfault in the case where a badly behaved v2 versioning
4801 directory sends a signed networkstatus with missing client-versions.
4803 - Avoid segfaults on certain complex invocations of
4804 router_get_by_hexdigest(). Bugfix on 0.1.2.
4805 - Correct bad index on array access in parse_http_time(). Bugfix
4807 - Fix possible bug in vote generation when server versions are present
4808 but client versions are not.
4809 - Fix rare bug on REDIRECTSTREAM control command when called with no
4810 port set: it could erroneously report an error when none had
4812 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
4813 compressing large objects and find ourselves with more than 4k
4814 left over. Bugfix on 0.2.0.
4815 - Fix a small memory leak when setting up a hidden service.
4816 - Fix a few memory leaks that could in theory happen under bizarre
4818 - Fix an assert if we post a general-purpose descriptor via the
4819 control port but that descriptor isn't mentioned in our current
4820 network consensus. Bug reported by Jon McLachlan; bugfix on
4823 o Minor features (controller):
4824 - Get NS events working again. Patch from tup.
4825 - The GETCONF command now escapes and quotes configuration values
4826 that don't otherwise fit into the torrc file.
4827 - The SETCONF command now handles quoted values correctly.
4829 o Minor features (directory authorities):
4830 - New configuration options to override default maximum number of
4831 servers allowed on a single IP address. This is important for
4832 running a test network on a single host.
4833 - Actually implement the -s option to tor-gencert.
4834 - Add a manual page for tor-gencert.
4836 o Minor features (bridges):
4837 - Bridge authorities no longer serve bridge descriptors over
4838 unencrypted connections.
4840 o Minor features (other):
4841 - Add hidden services and DNSPorts to the list of things that make
4842 Tor accept that it has running ports. Change starting Tor with no
4843 ports from a fatal error to a warning; we might change it back if
4844 this turns out to confuse anybody. Fixes bug 579.
4847 Changes in version 0.1.2.19 - 2008-01-17
4848 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
4849 exit policy a little bit more conservative so it's safer to run an
4850 exit relay on a home system, and fixes a variety of smaller issues.
4853 - Exit policies now reject connections that are addressed to a
4854 relay's public (external) IP address too, unless
4855 ExitPolicyRejectPrivate is turned off. We do this because too
4856 many relays are running nearby to services that trust them based
4860 - When the clock jumps forward a lot, do not allow the bandwidth
4861 buckets to become negative. Fixes bug 544.
4862 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
4863 on every successful resolve. Reported by Mike Perry.
4864 - Purge old entries from the "rephist" database and the hidden
4865 service descriptor database even when DirPort is zero.
4866 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
4867 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
4868 crashing or mis-answering these requests.
4869 - When we decide to send a 503 response to a request for servers, do
4870 not then also send the server descriptors: this defeats the whole
4871 purpose. Fixes bug 539.
4874 - Changing the ExitPolicyRejectPrivate setting should cause us to
4875 rebuild our server descriptor.
4876 - Fix handling of hex nicknames when answering controller requests for
4877 networkstatus by name, or when deciding whether to warn about
4878 unknown routers in a config option. (Patch from mwenge.)
4879 - Fix a couple of hard-to-trigger autoconf problems that could result
4880 in really weird results on platforms whose sys/types.h files define
4881 nonstandard integer types.
4882 - Don't try to create the datadir when running --verify-config or
4883 --hash-password. Resolves bug 540.
4884 - If we were having problems getting a particular descriptor from the
4885 directory caches, and then we learned about a new descriptor for
4886 that router, we weren't resetting our failure count. Reported
4888 - Although we fixed bug 539 (where servers would send HTTP status 503
4889 responses _and_ send a body too), there are still servers out there
4890 that haven't upgraded. Therefore, make clients parse such bodies
4891 when they receive them.
4892 - Run correctly on systems where rlim_t is larger than unsigned long.
4893 This includes some 64-bit systems.
4894 - Run correctly on platforms (like some versions of OS X 10.5) where
4895 the real limit for number of open files is OPEN_FILES, not rlim_max
4896 from getrlimit(RLIMIT_NOFILES).
4897 - Avoid a spurious free on base64 failure.
4898 - Avoid segfaults on certain complex invocations of
4899 router_get_by_hexdigest().
4900 - Fix rare bug on REDIRECTSTREAM control command when called with no
4901 port set: it could erroneously report an error when none had
4905 Changes in version 0.2.0.15-alpha - 2007-12-25
4906 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
4907 features added in 0.2.0.13-alpha.
4910 - Fix several remotely triggerable asserts based on DirPort requests
4911 for a v2 or v3 networkstatus object before we were prepared. This
4912 was particularly bad for 0.2.0.13 and later bridge relays, who
4913 would never have a v2 networkstatus and would thus always crash
4914 when used. Bugfixes on 0.2.0.x.
4915 - Estimate the v3 networkstatus size more accurately, rather than
4916 estimating it at zero bytes and giving it artificially high priority
4917 compared to other directory requests. Bugfix on 0.2.0.x.
4920 - Fix configure.in logic for cross-compilation.
4921 - When we load a bridge descriptor from the cache, and it was
4922 previously unreachable, mark it as retriable so we won't just
4923 ignore it. Also, try fetching a new copy immediately. Bugfixes
4925 - The bridge GeoIP stats were counting other relays, for example
4926 self-reachability and authority-reachability tests.
4929 - Support compilation to target iPhone; patch from cjacker huang.
4930 To build for iPhone, pass the --enable-iphone option to configure.
4933 Changes in version 0.2.0.14-alpha - 2007-12-23
4935 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
4936 without a datadirectory from a previous Tor install. Reported
4938 - Fix a crash when we fetch a descriptor that turns out to be
4939 unexpected (it used to be in our networkstatus when we started
4940 fetching it, but it isn't in our current networkstatus), and we
4941 aren't using bridges. Bugfix on 0.2.0.x.
4942 - Fix a crash when accessing hidden services: it would work the first
4943 time you use a given introduction point for your service, but
4944 on subsequent requests we'd be using garbage memory. Fixed by
4945 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
4946 - Fix a crash when we load a bridge descriptor from disk but we don't
4947 currently have a Bridge line for it in our torrc. Bugfix on
4951 - If bridge authorities set BridgePassword, they will serve a
4952 snapshot of known bridge routerstatuses from their DirPort to
4953 anybody who knows that password. Unset by default.
4956 - Make the unit tests build again.
4957 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
4958 - Make PublishServerDescriptor default to 1, so the default doesn't
4959 have to change as we invent new directory protocol versions.
4960 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
4961 be included unless sys/time.h is already included. Fixes
4962 bug 553. Bugfix on 0.2.0.x.
4963 - If we receive a general-purpose descriptor and then receive an
4964 identical bridge-purpose descriptor soon after, don't discard
4965 the next one as a duplicate.
4968 - If BridgeRelay is set to 1, then the default for
4969 PublishServerDescriptor is now "bridge" rather than "v2,v3".
4970 - If the user sets RelayBandwidthRate but doesn't set
4971 RelayBandwidthBurst, then make them equal rather than erroring out.
4974 Changes in version 0.2.0.13-alpha - 2007-12-21
4975 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
4976 Goodell, fixes many more bugs, and adds a lot of infrastructure for
4979 o New directory authorities:
4980 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
4984 - Only update guard status (usable / not usable) once we have
4985 enough directory information. This was causing us to always pick
4986 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
4987 causing us to discard all our guards on startup if we hadn't been
4988 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
4989 - Purge old entries from the "rephist" database and the hidden
4990 service descriptor databases even when DirPort is zero. Bugfix
4992 - We were ignoring our RelayBandwidthRate for the first 30 seconds
4993 after opening a circuit -- even a relayed circuit. Bugfix on
4995 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
4996 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
4997 crashing or mis-answering these types of requests.
4998 - Relays were publishing their server descriptor to v1 and v2
4999 directory authorities, but they didn't try publishing to v3-only
5000 authorities. Fix this; and also stop publishing to v1 authorities.
5002 - When we were reading router descriptors from cache, we were ignoring
5003 the annotations -- so for example we were reading in bridge-purpose
5004 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
5005 - When we decided to send a 503 response to a request for servers, we
5006 were then also sending the server descriptors: this defeats the
5007 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
5010 - Bridge relays now behave like clients with respect to time
5011 intervals for downloading new consensus documents -- otherwise they
5012 stand out. Bridge users now wait until the end of the interval,
5013 so their bridge relay will be sure to have a new consensus document.
5014 - Three new config options (AlternateDirAuthority,
5015 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
5016 user selectively replace the default directory authorities by type,
5017 rather than the all-or-nothing replacement that DirServer offers.
5018 - Tor can now be configured to read a GeoIP file from disk in one
5019 of two formats. This can be used by controllers to map IP addresses
5020 to countries. Eventually, it may support exit-by-country.
5021 - When possible, bridge relays remember which countries users
5022 are coming from, and report aggregate information in their
5023 extra-info documents, so that the bridge authorities can learn
5024 where Tor is blocked.
5025 - Bridge directory authorities now do reachability testing on the
5026 bridges they know. They provide router status summaries to the
5027 controller via "getinfo ns/purpose/bridge", and also dump summaries
5028 to a file periodically.
5029 - Stop fetching directory info so aggressively if your DirPort is
5030 on but your ORPort is off; stop fetching v2 dir info entirely.
5031 You can override these choices with the new FetchDirInfoEarly
5035 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
5036 consensus documents when there are too many relays at a single
5037 IP address. Now clear it in v2 network status documents too, and
5038 also clear it in routerinfo_t when the relay is no longer listed
5039 in the relevant networkstatus document.
5040 - Don't crash if we get an unexpected value for the
5041 PublishServerDescriptor config option. Reported by Matt Edman;
5042 bugfix on 0.2.0.9-alpha.
5043 - Our new v2 hidden service descriptor format allows descriptors
5044 that have no introduction points. But Tor crashed when we tried
5045 to build a descriptor with no intro points (and it would have
5046 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
5048 - Fix building with dmalloc 5.5.2 with glibc.
5049 - Reject uploaded descriptors and extrainfo documents if they're
5050 huge. Otherwise we'll cache them all over the network and it'll
5051 clog everything up. Reported by Aljosha Judmayer.
5052 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
5053 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
5054 - When the DANGEROUS_VERSION controller status event told us we're
5055 running an obsolete version, it used the string "OLD" to describe
5056 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
5057 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
5058 - If we can't expand our list of entry guards (e.g. because we're
5059 using bridges or we have StrictEntryNodes set), don't mark relays
5060 down when they fail a directory request. Otherwise we're too quick
5061 to mark all our entry points down. Bugfix on 0.1.2.x.
5062 - Fix handling of hex nicknames when answering controller requests for
5063 networkstatus by name, or when deciding whether to warn about unknown
5064 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
5065 - Fix a couple of hard-to-trigger autoconf problems that could result
5066 in really weird results on platforms whose sys/types.h files define
5067 nonstandard integer types. Bugfix on 0.1.2.x.
5068 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
5069 - Don't crash on name lookup when we have no current consensus. Fixes
5070 bug 538; bugfix on 0.2.0.x.
5071 - Only Tors that want to mirror the v2 directory info should
5072 create the "cached-status" directory in their datadir. (All Tors
5073 used to create it.) Bugfix on 0.2.0.9-alpha.
5074 - Directory authorities should only automatically download Extra Info
5075 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
5078 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
5079 consumers. (We already do this on HUP.)
5080 - Authorities and caches fetch the v2 networkstatus documents
5081 less often, now that v3 is encouraged.
5082 - Add a new config option BridgeRelay that specifies you want to
5083 be a bridge relay. Right now the only difference is that it makes
5084 you answer begin_dir requests, and it makes you cache dir info,
5085 even if your DirPort isn't on.
5086 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
5087 ask about source, timestamp of arrival, purpose, etc. We need
5088 something like this to help Vidalia not do GeoIP lookups on bridge
5090 - Allow multiple HashedControlPassword config lines, to support
5091 multiple controller passwords.
5092 - Authorities now decide whether they're authoritative for a given
5093 router based on the router's purpose.
5094 - New config options AuthDirBadDir and AuthDirListBadDirs for
5095 authorities to mark certain relays as "bad directories" in the
5096 networkstatus documents. Also supports the "!baddir" directive in
5097 the approved-routers file.
5100 Changes in version 0.2.0.12-alpha - 2007-11-16
5101 This twelfth development snapshot fixes some more build problems as
5102 well as a few minor bugs.
5105 - Make it build on OpenBSD again. Patch from tup.
5106 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
5107 package-building for Red Hat, OS X, etc.
5109 o Minor bugfixes (on 0.1.2.x):
5110 - Changing the ExitPolicyRejectPrivate setting should cause us to
5111 rebuild our server descriptor.
5113 o Minor bugfixes (on 0.2.0.x):
5114 - When we're lacking a consensus, don't try to perform rendezvous
5115 operations. Reported by Karsten Loesing.
5116 - Fix a small memory leak whenever we decide against using a
5117 newly picked entry guard. Reported by Mike Perry.
5118 - When authorities detected more than two relays running on the same
5119 IP address, they were clearing all the status flags but forgetting
5120 to clear the "hsdir" flag. So clients were being told that a
5121 given relay was the right choice for a v2 hsdir lookup, yet they
5122 never had its descriptor because it was marked as 'not running'
5124 - If we're trying to fetch a bridge descriptor and there's no way
5125 the bridge authority could help us (for example, we don't know
5126 a digest, or there is no bridge authority), don't be so eager to
5127 fall back to asking the bridge authority.
5128 - If we're using bridges or have strictentrynodes set, and our
5129 chosen exit is in the same family as all our bridges/entry guards,
5130 then be flexible about families.
5133 - When we negotiate a v2 link-layer connection (not yet implemented),
5134 accept RELAY_EARLY cells and turn them into RELAY cells if we've
5135 negotiated a v1 connection for their next step. Initial code for
5139 Changes in version 0.2.0.11-alpha - 2007-11-12
5140 This eleventh development snapshot fixes some build problems with
5141 the previous snapshot. It also includes a more secure-by-default exit
5142 policy for relays, fixes an enormous memory leak for exit relays, and
5143 fixes another bug where servers were falling out of the directory list.
5146 - Exit policies now reject connections that are addressed to a
5147 relay's public (external) IP address too, unless
5148 ExitPolicyRejectPrivate is turned off. We do this because too
5149 many relays are running nearby to services that trust them based
5150 on network address. Bugfix on 0.1.2.x.
5153 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
5154 on every successful resolve. Reported by Mike Perry; bugfix
5156 - On authorities, never downgrade to old router descriptors simply
5157 because they're listed in the consensus. This created a catch-22
5158 where we wouldn't list a new descriptor because there was an
5159 old one in the consensus, and we couldn't get the new one in the
5160 consensus because we wouldn't list it. Possible fix for bug 548.
5161 Also, this might cause bug 543 to appear on authorities; if so,
5162 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
5164 o Packaging fixes on 0.2.0.10-alpha:
5165 - We were including instructions about what to do with the
5166 src/config/fallback-consensus file, but we weren't actually
5167 including it in the tarball. Disable all of that for now.
5170 - Allow people to say PreferTunnelledDirConns rather than
5171 PreferTunneledDirConns, for those alternate-spellers out there.
5174 - Don't reevaluate all the information from our consensus document
5175 just because we've downloaded a v2 networkstatus that we intend
5176 to cache. Fixes bug 545; bugfix on 0.2.0.x.
5179 Changes in version 0.2.0.10-alpha - 2007-11-10
5180 This tenth development snapshot adds a third v3 directory authority
5181 run by Mike Perry, adds most of Karsten Loesing's new hidden service
5182 descriptor format, fixes a bad crash bug and new bridge bugs introduced
5183 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
5184 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
5185 addresses many more minor issues.
5187 o New directory authorities:
5188 - Set up ides (run by Mike Perry) as the third v3 directory authority.
5191 - Allow tunnelled directory connections to ask for an encrypted
5192 "begin_dir" connection or an anonymized "uses a full Tor circuit"
5193 connection independently. Now we can make anonymized begin_dir
5194 connections for (e.g.) more secure hidden service posting and
5196 - More progress on proposal 114: code from Karsten Loesing to
5197 implement new hidden service descriptor format.
5198 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
5199 accommodate the growing number of servers that use the default
5200 and are reaching it.
5201 - Directory authorities use a new formula for selecting which nodes
5202 to advertise as Guards: they must be in the top 7/8 in terms of
5203 how long we have known about them, and above the median of those
5204 nodes in terms of weighted fractional uptime.
5205 - Make "not enough dir info yet" warnings describe *why* Tor feels
5206 it doesn't have enough directory info yet.
5209 - Stop servers from crashing if they set a Family option (or
5210 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
5212 - Make bridge users work again -- the move to v3 directories in
5213 0.2.0.9-alpha had introduced a number of bugs that made bridges
5214 no longer work for clients.
5215 - When the clock jumps forward a lot, do not allow the bandwidth
5216 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
5218 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
5219 - When the consensus lists a router descriptor that we previously were
5220 mirroring, but that we considered non-canonical, reload the
5221 descriptor as canonical. This fixes bug 543 where Tor servers
5222 would start complaining after a few days that they don't have
5223 enough directory information to build a circuit.
5224 - Consider replacing the current consensus when certificates arrive
5225 that make the pending consensus valid. Previously, we were only
5226 considering replacement when the new certs _didn't_ help.
5227 - Fix an assert error on startup if we didn't already have the
5228 consensus and certs cached in our datadirectory: we were caching
5229 the consensus in consensus_waiting_for_certs but then free'ing it
5231 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
5232 Request) if we need more v3 certs but we've already got pending
5233 requests for all of them.
5234 - Correctly back off from failing certificate downloads. Fixes
5236 - Authorities don't vote on the Running flag if they have been running
5237 for less than 30 minutes themselves. Fixes bug 547, where a newly
5238 started authority would vote that everyone was down.
5241 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
5242 it, it had no AES, and it hasn't seen any security patches since
5246 - Clients now hold circuitless TLS connections open for 1.5 times
5247 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
5248 rebuild a new circuit over them within that timeframe. Previously,
5249 they held them open only for KeepalivePeriod (5 minutes).
5250 - Use "If-Modified-Since" to avoid retrieving consensus
5251 networkstatuses that we already have.
5252 - When we have no consensus, check FallbackNetworkstatusFile (defaults
5253 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
5254 we start knowing some directory caches.
5255 - When we receive a consensus from the future, warn about skew.
5256 - Improve skew reporting: try to give the user a better log message
5257 about how skewed they are, and how much this matters.
5258 - When we have a certificate for an authority, believe that
5259 certificate's claims about the authority's IP address.
5260 - New --quiet command-line option to suppress the default console log.
5261 Good in combination with --hash-password.
5262 - Authorities send back an X-Descriptor-Not-New header in response to
5263 an accepted-but-discarded descriptor upload. Partially implements
5265 - Make the log message for "tls error. breaking." more useful.
5266 - Better log messages about certificate downloads, to attempt to
5267 track down the second incarnation of bug 546.
5269 o Minor features (bridges):
5270 - If bridge users set UpdateBridgesFromAuthority, but the digest
5271 they ask for is a 404 from the bridge authority, they now fall
5272 back to trying the bridge directly.
5273 - Bridges now use begin_dir to publish their server descriptor to
5274 the bridge authority, even when they haven't set TunnelDirConns.
5276 o Minor features (controller):
5277 - When reporting clock skew, and we know that the clock is _at least
5278 as skewed_ as some value, but we don't know the actual value,
5279 report the value as a "minimum skew."
5282 - Update linux-tor-prio.sh script to allow QoS based on the uid of
5283 the Tor process. Patch from Marco Bonetti with tweaks from Mike
5287 - Refuse to start if both ORPort and UseBridges are set. Bugfix
5288 on 0.2.0.x, suggested by Matt Edman.
5289 - Don't stop fetching descriptors when FetchUselessDescriptors is
5290 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
5291 reported by tup and ioerror.
5292 - Better log message on vote from unknown authority.
5293 - Don't log "Launching 0 request for 0 router" message.
5295 o Minor bugfixes (memory leaks):
5296 - Stop leaking memory every time we parse a v3 certificate. Bugfix
5298 - Stop leaking memory every time we load a v3 certificate. Bugfix
5299 on 0.2.0.1-alpha. Fixes bug 536.
5300 - Stop leaking a cached networkstatus on exit. Bugfix on
5302 - Stop leaking voter information every time we free a consensus.
5303 Bugfix on 0.2.0.3-alpha.
5304 - Stop leaking signed data every time we check a voter signature.
5305 Bugfix on 0.2.0.3-alpha.
5306 - Stop leaking a signature every time we fail to parse a consensus or
5307 a vote. Bugfix on 0.2.0.3-alpha.
5308 - Stop leaking v2_download_status_map on shutdown. Bugfix on
5310 - Stop leaking conn->nickname every time we make a connection to a
5311 Tor relay without knowing its expected identity digest (e.g. when
5312 using bridges). Bugfix on 0.2.0.3-alpha.
5314 - Minor bugfixes (portability):
5315 - Run correctly on platforms where rlim_t is larger than unsigned
5316 long, and/or where the real limit for number of open files is
5317 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
5318 particular, these may be needed for OS X 10.5.
5321 Changes in version 0.1.2.18 - 2007-10-28
5322 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
5323 hidden service introduction that were causing huge delays, and a big
5324 bug that was causing some servers to disappear from the network status
5325 lists for a few hours each day.
5327 o Major bugfixes (crashes):
5328 - If a connection is shut down abruptly because of something that
5329 happened inside connection_flushed_some(), do not call
5330 connection_finished_flushing(). Should fix bug 451:
5331 "connection_stop_writing: Assertion conn->write_event failed"
5332 Bugfix on 0.1.2.7-alpha.
5333 - Fix possible segfaults in functions called from
5334 rend_process_relay_cell().
5336 o Major bugfixes (hidden services):
5337 - Hidden services were choosing introduction points uniquely by
5338 hexdigest, but when constructing the hidden service descriptor
5339 they merely wrote the (potentially ambiguous) nickname.
5340 - Clients now use the v2 intro format for hidden service
5341 connections: they specify their chosen rendezvous point by identity
5342 digest rather than by (potentially ambiguous) nickname. These
5343 changes could speed up hidden service connections dramatically.
5345 o Major bugfixes (other):
5346 - Stop publishing a new server descriptor just because we get a
5347 HUP signal. This led (in a roundabout way) to some servers getting
5348 dropped from the networkstatus lists for a few hours each day.
5349 - When looking for a circuit to cannibalize, consider family as well
5350 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
5351 circuit cannibalization).
5352 - When a router wasn't listed in a new networkstatus, we were leaving
5353 the flags for that router alone -- meaning it remained Named,
5354 Running, etc -- even though absence from the networkstatus means
5355 that it shouldn't be considered to exist at all anymore. Now we
5356 clear all the flags for routers that fall out of the networkstatus
5357 consensus. Fixes bug 529.
5360 - Don't try to access (or alter) the state file when running
5361 --list-fingerprint or --verify-config or --hash-password. Resolves
5363 - When generating information telling us how to extend to a given
5364 router, do not try to include the nickname if it is
5365 absent. Resolves bug 467.
5366 - Fix a user-triggerable segfault in expand_filename(). (There isn't
5367 a way to trigger this remotely.)
5368 - When sending a status event to the controller telling it that an
5369 OR address is reachable, set the port correctly. (Previously we
5370 were reporting the dir port.)
5371 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
5372 command. Bugfix on 0.1.2.17.
5373 - When loading bandwidth history, do not believe any information in
5374 the future. Fixes bug 434.
5375 - When loading entry guard information, do not believe any information
5377 - When we have our clock set far in the future and generate an
5378 onion key, then re-set our clock to be correct, we should not stop
5379 the onion key from getting rotated.
5380 - On some platforms, accept() can return a broken address. Detect
5381 this more quietly, and deal accordingly. Fixes bug 483.
5382 - It's not actually an error to find a non-pending entry in the DNS
5383 cache when canceling a pending resolve. Don't log unless stuff
5384 is fishy. Resolves bug 463.
5385 - Don't reset trusted dir server list when we set a configuration
5386 option. Patch from Robert Hogan.
5387 - Don't try to create the datadir when running --verify-config or
5388 --hash-password. Resolves bug 540.
5391 Changes in version 0.2.0.9-alpha - 2007-10-24
5392 This ninth development snapshot switches clients to the new v3 directory
5393 system; allows servers to be listed in the network status even when they
5394 have the same nickname as a registered server; and fixes many other
5395 bugs including a big one that was causing some servers to disappear
5396 from the network status lists for a few hours each day.
5398 o Major features (directory system):
5399 - Clients now download v3 consensus networkstatus documents instead
5400 of v2 networkstatus documents. Clients and caches now base their
5401 opinions about routers on these consensus documents. Clients only
5402 download router descriptors listed in the consensus.
5403 - Authorities now list servers who have the same nickname as
5404 a different named server, but list them with a new flag,
5405 "Unnamed". Now we can list servers that happen to pick the same
5406 nickname as a server that registered two years ago and then
5407 disappeared. Partially implements proposal 122.
5408 - If the consensus lists a router as "Unnamed", the name is assigned
5409 to a different router: do not identify the router by that name.
5410 Partially implements proposal 122.
5411 - Authorities can now come to a consensus on which method to use to
5412 compute the consensus. This gives us forward compatibility.
5415 - Stop publishing a new server descriptor just because we HUP or
5416 when we find our DirPort to be reachable but won't actually publish
5417 it. New descriptors without any real changes are dropped by the
5418 authorities, and can screw up our "publish every 18 hours" schedule.
5420 - When a router wasn't listed in a new networkstatus, we were leaving
5421 the flags for that router alone -- meaning it remained Named,
5422 Running, etc -- even though absence from the networkstatus means
5423 that it shouldn't be considered to exist at all anymore. Now we
5424 clear all the flags for routers that fall out of the networkstatus
5425 consensus. Fixes bug 529; bugfix on 0.1.2.x.
5426 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
5427 extrainfo documents and then discard them immediately for not
5428 matching the latest router. Bugfix on 0.2.0.1-alpha.
5430 o Minor features (v3 directory protocol):
5431 - Allow tor-gencert to generate a new certificate without replacing
5433 - Allow certificates to include an address.
5434 - When we change our directory-cache settings, reschedule all voting
5435 and download operations.
5436 - Reattempt certificate downloads immediately on failure, as long as
5437 we haven't failed a threshold number of times yet.
5438 - Delay retrying consensus downloads while we're downloading
5439 certificates to verify the one we just got. Also, count getting a
5440 consensus that we already have (or one that isn't valid) as a failure,
5441 and count failing to get the certificates after 20 minutes as a
5443 - Build circuits and download descriptors even if our consensus is a
5444 little expired. (This feature will go away once authorities are
5447 o Minor features (router descriptor cache):
5448 - If we find a cached-routers file that's been sitting around for more
5449 than 28 days unmodified, then most likely it's a leftover from
5450 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
5452 - When we (as a cache) download a descriptor because it was listed
5453 in a consensus, remember when the consensus was supposed to expire,
5454 and don't expire the descriptor until then.
5456 o Minor features (performance):
5457 - Call routerlist_remove_old_routers() much less often. This should
5458 speed startup, especially on directory caches.
5459 - Don't try to launch new descriptor downloads quite so often when we
5460 already have enough directory information to build circuits.
5461 - Base64 decoding was actually showing up on our profile when parsing
5462 the initial descriptor file; switch to an in-process all-at-once
5463 implementation that's about 3.5x times faster than calling out to
5466 o Minor features (compilation):
5467 - Detect non-ASCII platforms (if any still exist) and refuse to
5468 build there: some of our code assumes that 'A' is 65 and so on.
5470 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
5471 - Make the "next period" votes into "current period" votes immediately
5472 after publishing the consensus; avoid a heisenbug that made them
5473 stick around indefinitely.
5474 - When we discard a vote as a duplicate, do not report this as
5476 - Treat missing v3 keys or certificates as an error when running as a
5477 v3 directory authority.
5478 - When we're configured to be a v3 authority, but we're only listed
5479 as a non-v3 authority in our DirServer line for ourself, correct
5481 - If an authority doesn't have a qualified hostname, just put
5482 its address in the vote. This fixes the problem where we referred to
5483 "moria on moria:9031."
5484 - Distinguish between detached signatures for the wrong period, and
5485 detached signatures for a divergent vote.
5486 - Fix a small memory leak when computing a consensus.
5487 - When there's no concensus, we were forming a vote every 30
5488 minutes, but writing the "valid-after" line in our vote based
5489 on our configured V3AuthVotingInterval: so unless the intervals
5490 matched up, we immediately rejected our own vote because it didn't
5491 start at the voting interval that caused us to construct a vote.
5493 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
5494 - Delete unverified-consensus when the real consensus is set.
5495 - Consider retrying a consensus networkstatus fetch immediately
5496 after one fails: don't wait 60 seconds to notice.
5497 - When fetching a consensus as a cache, wait until a newer consensus
5498 should exist before trying to replace the current one.
5499 - Use a more forgiving schedule for retrying failed consensus
5500 downloads than for other types.
5502 o Minor bugfixes (other directory issues):
5503 - Correct the implementation of "download votes by digest." Bugfix on
5505 - Authorities no longer send back "400 you're unreachable please fix
5506 it" errors to Tor servers that aren't online all the time. We're
5507 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
5509 o Minor bugfixes (controller):
5510 - Don't reset trusted dir server list when we set a configuration
5511 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
5512 - Respond to INT and TERM SIGNAL commands before we execute the
5513 signal, in case the signal shuts us down. We had a patch in
5514 0.1.2.1-alpha that tried to do this by queueing the response on
5515 the connection's buffer before shutting down, but that really
5516 isn't the same thing at all. Bug located by Matt Edman.
5518 o Minor bugfixes (misc):
5519 - Correctly check for bad options to the "PublishServerDescriptor"
5520 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
5521 - Stop leaking memory on failing case of base32_decode, and make
5522 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
5523 - Don't try to download extrainfo documents when we're trying to
5524 fetch enough directory info to build a circuit: having enough
5525 info should get priority. Bugfix on 0.2.0.x.
5526 - Don't complain that "your server has not managed to confirm that its
5527 ports are reachable" if we haven't been able to build any circuits
5528 yet. Bug found by spending four hours without a v3 consensus. Bugfix
5530 - Detect the reason for failing to mmap a descriptor file we just
5531 wrote, and give a more useful log message. Fixes bug 533. Bugfix
5534 o Code simplifications and refactoring:
5535 - Remove support for the old bw_accounting file: we've been storing
5536 bandwidth accounting information in the state file since
5537 0.1.2.5-alpha. This may result in bandwidth accounting errors
5538 if you try to upgrade from 0.1.1.x or earlier, or if you try to
5539 downgrade to 0.1.1.x or earlier.
5540 - New convenience code to locate a file within the DataDirectory.
5541 - Move non-authority functionality out of dirvote.c.
5542 - Refactor the arguments for router_pick_{directory_|trusteddir}server
5543 so that they all take the same named flags.
5546 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
5547 Unix users an easy way to script their Tor process (e.g. by
5548 adjusting bandwidth based on the time of the day).
5551 Changes in version 0.2.0.8-alpha - 2007-10-12
5552 This eighth development snapshot fixes a crash bug that's been bothering
5553 us since February 2007, lets bridge authorities store a list of bridge
5554 descriptors they've seen, gets v3 directory voting closer to working,
5555 starts caching v3 directory consensus documents on directory mirrors,
5556 and fixes a variety of smaller issues including some minor memory leaks.
5558 o Major features (router descriptor cache):
5559 - Store routers in a file called cached-descriptors instead of in
5560 cached-routers. Initialize cached-descriptors from cached-routers
5561 if the old format is around. The new format allows us to store
5562 annotations along with descriptors.
5563 - Use annotations to record the time we received each descriptor, its
5564 source, and its purpose.
5565 - Disable the SETROUTERPURPOSE controller command: it is now
5567 - Controllers should now specify cache=no or cache=yes when using
5568 the +POSTDESCRIPTOR command.
5569 - Bridge authorities now write bridge descriptors to disk, meaning
5570 we can export them to other programs and begin distributing them
5573 o Major features (directory authorities):
5574 - When a v3 authority is missing votes or signatures, it now tries
5576 - Directory authorities track weighted fractional uptime as well as
5577 weighted mean-time-between failures. WFU is suitable for deciding
5578 whether a node is "usually up", while MTBF is suitable for deciding
5579 whether a node is "likely to stay up." We need both, because
5580 "usually up" is a good requirement for guards, while "likely to
5581 stay up" is a good requirement for long-lived connections.
5583 o Major features (v3 directory system):
5584 - Caches now download v3 network status documents as needed,
5585 and download the descriptors listed in them.
5586 - All hosts now attempt to download and keep fresh v3 authority
5587 certificates, and re-attempt after failures.
5588 - More internal-consistency checks for vote parsing.
5590 o Major bugfixes (crashes):
5591 - If a connection is shut down abruptly because of something that
5592 happened inside connection_flushed_some(), do not call
5593 connection_finished_flushing(). Should fix bug 451. Bugfix on
5596 o Major bugfixes (performance):
5597 - Fix really bad O(n^2) performance when parsing a long list of
5598 routers: Instead of searching the entire list for an "extra-info "
5599 string which usually wasn't there, once for every routerinfo
5600 we read, just scan lines forward until we find one we like.
5602 - When we add data to a write buffer in response to the data on that
5603 write buffer getting low because of a flush, do not consider the
5604 newly added data as a candidate for immediate flushing, but rather
5605 make it wait until the next round of writing. Otherwise, we flush
5606 and refill recursively, and a single greedy TLS connection can
5607 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
5609 o Minor features (v3 authority system):
5610 - Add more ways for tools to download the votes that lead to the
5612 - Send a 503 when low on bandwidth and a vote, consensus, or
5613 certificate is requested.
5614 - If-modified-since is now implemented properly for all kinds of
5615 certificate requests.
5617 o Minor bugfixes (network statuses):
5618 - Tweak the implementation of proposal 109 slightly: allow at most
5619 two Tor servers on the same IP address, except if it's the location
5620 of a directory authority, in which case allow five. Bugfix on
5623 o Minor bugfixes (controller):
5624 - When sending a status event to the controller telling it that an
5625 OR address is reachable, set the port correctly. (Previously we
5626 were reporting the dir port.) Bugfix on 0.1.2.x.
5628 o Minor bugfixes (v3 directory system):
5629 - Fix logic to look up a cert by its signing key digest. Bugfix on
5631 - Only change the reply to a vote to "OK" if it's not already
5632 set. This gets rid of annoying "400 OK" log messages, which may
5633 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
5634 - When we get a valid consensus, recompute the voting schedule.
5635 - Base the valid-after time of a vote on the consensus voting
5636 schedule, not on our preferred schedule.
5637 - Make the return values and messages from signature uploads and
5638 downloads more sensible.
5639 - Fix a memory leak when serving votes and consensus documents, and
5640 another when serving certificates.
5642 o Minor bugfixes (performance):
5643 - Use a slightly simpler string hashing algorithm (copying Python's
5644 instead of Java's) and optimize our digest hashing algorithm to take
5645 advantage of 64-bit platforms and to remove some possibly-costly
5647 - Fix a minor memory leak whenever we parse guards from our state
5648 file. Bugfix on 0.2.0.7-alpha.
5649 - Fix a minor memory leak whenever we write out a file. Bugfix on
5651 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
5652 command. Bugfix on 0.2.0.5-alpha.
5654 o Minor bugfixes (portability):
5655 - On some platforms, accept() can return a broken address. Detect
5656 this more quietly, and deal accordingly. Fixes bug 483.
5657 - Stop calling tor_strlower() on uninitialized memory in some cases.
5658 Bugfix in 0.2.0.7-alpha.
5660 o Minor bugfixes (usability):
5661 - Treat some 403 responses from directory servers as INFO rather than
5662 WARN-severity events.
5663 - It's not actually an error to find a non-pending entry in the DNS
5664 cache when canceling a pending resolve. Don't log unless stuff is
5665 fishy. Resolves bug 463.
5667 o Minor bugfixes (anonymity):
5668 - Never report that we've used more bandwidth than we're willing to
5669 relay: it leaks how much non-relay traffic we're using. Resolves
5671 - When looking for a circuit to cannibalize, consider family as well
5672 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
5673 circuit cannibalization).
5675 o Code simplifications and refactoring:
5676 - Make a bunch of functions static. Remove some dead code.
5677 - Pull out about a third of the really big routerlist.c; put it in a
5678 new module, networkstatus.c.
5679 - Merge the extra fields in local_routerstatus_t back into
5680 routerstatus_t: we used to need one routerstatus_t for each
5681 authority's opinion, plus a local_routerstatus_t for the locally
5682 computed consensus opinion. To save space, we put the locally
5683 modified fields into local_routerstatus_t, and only the common
5684 stuff into routerstatus_t. But once v3 directories are in use,
5685 clients and caches will no longer need to hold authority opinions;
5686 thus, the rationale for keeping the types separate is now gone.
5687 - Make the code used to reschedule and reattempt downloads more
5689 - Turn all 'Are we a directory server/mirror?' logic into a call to
5691 - Remove the code to generate the oldest (v1) directory format.
5692 The code has been disabled since 0.2.0.5-alpha.
5695 Changes in version 0.2.0.7-alpha - 2007-09-21
5696 This seventh development snapshot makes bridges work again, makes bridge
5697 authorities work for the first time, fixes two huge performance flaws
5698 in hidden services, and fixes a variety of minor issues.
5700 o New directory authorities:
5701 - Set up moria1 and tor26 as the first v3 directory authorities. See
5702 doc/spec/dir-spec.txt for details on the new directory design.
5704 o Major bugfixes (crashes):
5705 - Fix possible segfaults in functions called from
5706 rend_process_relay_cell(). Bugfix on 0.1.2.x.
5708 o Major bugfixes (bridges):
5709 - Fix a bug that made servers send a "404 Not found" in response to
5710 attempts to fetch their server descriptor. This caused Tor servers
5711 to take many minutes to establish reachability for their DirPort,
5712 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
5713 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
5714 users configure that and specify a bridge with an identity
5715 fingerprint, now they will lookup the bridge descriptor at the
5716 default bridge authority via a one-hop tunnel, but once circuits
5717 are established they will switch to a three-hop tunnel for later
5718 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
5720 o Major bugfixes (hidden services):
5721 - Hidden services were choosing introduction points uniquely by
5722 hexdigest, but when constructing the hidden service descriptor
5723 they merely wrote the (potentially ambiguous) nickname.
5724 - Clients now use the v2 intro format for hidden service
5725 connections: they specify their chosen rendezvous point by identity
5726 digest rather than by (potentially ambiguous) nickname. Both
5727 are bugfixes on 0.1.2.x, and they could speed up hidden service
5728 connections dramatically. Thanks to Karsten Loesing.
5730 o Minor features (security):
5731 - As a client, do not believe any server that tells us that an
5732 address maps to an internal address space.
5733 - Make it possible to enable HashedControlPassword and
5734 CookieAuthentication at the same time.
5736 o Minor features (guard nodes):
5737 - Tag every guard node in our state file with the version that
5738 we believe added it, or with our own version if we add it. This way,
5739 if a user temporarily runs an old version of Tor and then switches
5740 back to a new one, she doesn't automatically lose her guards.
5742 o Minor features (speed):
5743 - When implementing AES counter mode, update only the portions of the
5744 counter buffer that need to change, and don't keep separate
5745 network-order and host-order counters when they are the same (i.e.,
5746 on big-endian hosts.)
5748 o Minor features (controller):
5749 - Accept LF instead of CRLF on controller, since some software has a
5750 hard time generating real Internet newlines.
5751 - Add GETINFO values for the server status events
5752 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
5756 - Routers no longer include bandwidth-history lines in their
5757 descriptors; this information is already available in extra-info
5758 documents, and including it in router descriptors took up 60%
5759 (!) of compressed router descriptor downloads. Completes
5760 implementation of proposal 104.
5761 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
5762 and TorControl.py, as they use the old v0 controller protocol,
5763 and are obsoleted by TorFlow anyway.
5764 - Drop support for v1 rendezvous descriptors, since we never used
5765 them anyway, and the code has probably rotted by now. Based on
5766 patch from Karsten Loesing.
5767 - On OSX, stop warning the user that kqueue support in libevent is
5768 "experimental", since it seems to have worked fine for ages.
5771 - When generating information telling us how to extend to a given
5772 router, do not try to include the nickname if it is absent. Fixes
5773 bug 467. Bugfix on 0.2.0.3-alpha.
5774 - Fix a user-triggerable (but not remotely-triggerable) segfault
5775 in expand_filename(). Bugfix on 0.1.2.x.
5776 - Fix a memory leak when freeing incomplete requests from DNSPort.
5777 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
5778 - Don't try to access (or alter) the state file when running
5779 --list-fingerprint or --verify-config or --hash-password. (Resolves
5780 bug 499.) Bugfix on 0.1.2.x.
5781 - Servers used to decline to publish their DirPort if their
5782 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
5783 were below a threshold. Now they only look at BandwidthRate and
5784 RelayBandwidthRate. Bugfix on 0.1.2.x.
5785 - Remove an optimization in the AES counter-mode code that assumed
5786 that the counter never exceeded 2^68. When the counter can be set
5787 arbitrarily as an IV (as it is by Karsten's new hidden services
5788 code), this assumption no longer holds. Bugfix on 0.1.2.x.
5789 - Resume listing "AUTHORITY" flag for authorities in network status.
5790 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
5792 o Code simplifications and refactoring:
5793 - Revamp file-writing logic so we don't need to have the entire
5794 contents of a file in memory at once before we write to disk. Tor,
5796 - Turn "descriptor store" into a full-fledged type.
5797 - Move all NT services code into a separate source file.
5798 - Unify all code that computes medians, percentile elements, etc.
5799 - Get rid of a needless malloc when parsing address policies.
5802 Changes in version 0.1.2.17 - 2007-08-30
5803 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
5804 X bundles. Vidalia 0.0.14 makes authentication required for the
5805 ControlPort in the default configuration, which addresses important
5806 security risks. Everybody who uses Vidalia (or another controller)
5809 In addition, this Tor update fixes major load balancing problems with
5810 path selection, which should speed things up a lot once many people
5813 o Major bugfixes (security):
5814 - We removed support for the old (v0) control protocol. It has been
5815 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
5816 become more of a headache than it's worth.
5818 o Major bugfixes (load balancing):
5819 - When choosing nodes for non-guard positions, weight guards
5820 proportionally less, since they already have enough load. Patch
5822 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
5823 will allow fast Tor servers to get more attention.
5824 - When we're upgrading from an old Tor version, forget our current
5825 guards and pick new ones according to the new weightings. These
5826 three load balancing patches could raise effective network capacity
5827 by a factor of four. Thanks to Mike Perry for measurements.
5829 o Major bugfixes (stream expiration):
5830 - Expire not-yet-successful application streams in all cases if
5831 they've been around longer than SocksTimeout. Right now there are
5832 some cases where the stream will live forever, demanding a new
5833 circuit every 15 seconds. Fixes bug 454; reported by lodger.
5835 o Minor features (controller):
5836 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
5837 is valid before any authentication has been received. It tells
5838 a controller what kind of authentication is expected, and what
5839 protocol is spoken. Implements proposal 119.
5841 o Minor bugfixes (performance):
5842 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
5843 greatly speeding up loading cached-routers from disk on startup.
5844 - Disable sentinel-based debugging for buffer code: we squashed all
5845 the bugs that this was supposed to detect a long time ago, and now
5846 its only effect is to change our buffer sizes from nice powers of
5847 two (which platform mallocs tend to like) to values slightly over
5848 powers of two (which make some platform mallocs sad).
5850 o Minor bugfixes (misc):
5851 - If exit bandwidth ever exceeds one third of total bandwidth, then
5852 use the correct formula to weight exit nodes when choosing paths.
5853 Based on patch from Mike Perry.
5854 - Choose perfectly fairly among routers when choosing by bandwidth and
5855 weighting by fraction of bandwidth provided by exits. Previously, we
5856 would choose with only approximate fairness, and correct ourselves
5857 if we ran off the end of the list.
5858 - If we require CookieAuthentication but we fail to write the
5859 cookie file, we would warn but not exit, and end up in a state
5860 where no controller could authenticate. Now we exit.
5861 - If we require CookieAuthentication, stop generating a new cookie
5862 every time we change any piece of our config.
5863 - Refuse to start with certain directory authority keys, and
5864 encourage people using them to stop.
5865 - Terminate multi-line control events properly. Original patch
5867 - Fix a minor memory leak when we fail to find enough suitable
5868 servers to choose a circuit.
5869 - Stop leaking part of the descriptor when we run into a particularly
5870 unparseable piece of it.
5873 Changes in version 0.2.0.6-alpha - 2007-08-26
5874 This sixth development snapshot features a new Vidalia version in the
5875 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
5876 the ControlPort in the default configuration, which addresses important
5879 In addition, this snapshot fixes major load balancing problems
5880 with path selection, which should speed things up a lot once many
5881 people have upgraded. The directory authorities also use a new
5882 mean-time-between-failure approach to tracking which servers are stable,
5883 rather than just looking at the most recent uptime.
5885 o New directory authorities:
5886 - Set up Tonga as the default bridge directory authority.
5889 - Directory authorities now track servers by weighted
5890 mean-times-between-failures. When we have 4 or more days of data,
5891 use measured MTBF rather than declared uptime to decide whether
5892 to call a router Stable. Implements proposal 108.
5894 o Major bugfixes (load balancing):
5895 - When choosing nodes for non-guard positions, weight guards
5896 proportionally less, since they already have enough load. Patch
5898 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
5899 will allow fast Tor servers to get more attention.
5900 - When we're upgrading from an old Tor version, forget our current
5901 guards and pick new ones according to the new weightings. These
5902 three load balancing patches could raise effective network capacity
5903 by a factor of four. Thanks to Mike Perry for measurements.
5905 o Major bugfixes (descriptor parsing):
5906 - Handle unexpected whitespace better in malformed descriptors. Bug
5907 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
5910 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
5911 GETINFO for Torstat to use until it can switch to using extrainfos.
5912 - Optionally (if built with -DEXPORTMALLINFO) export the output
5913 of mallinfo via http, as tor/mallinfo.txt. Only accessible
5917 - Do not intermix bridge routers with controller-added
5918 routers. (Bugfix on 0.2.0.x)
5919 - Do not fail with an assert when accept() returns an unexpected
5920 address family. Addresses but does not wholly fix bug 483. (Bugfix
5922 - Let directory authorities startup even when they can't generate
5923 a descriptor immediately, e.g. because they don't know their
5925 - Stop putting the authentication cookie in a file called "0"
5926 in your working directory if you don't specify anything for the
5927 new CookieAuthFile option. Reported by Matt Edman.
5928 - Make it possible to read the PROTOCOLINFO response in a way that
5929 conforms to our control-spec. Reported by Matt Edman.
5930 - Fix a minor memory leak when we fail to find enough suitable
5931 servers to choose a circuit. Bugfix on 0.1.2.x.
5932 - Stop leaking part of the descriptor when we run into a particularly
5933 unparseable piece of it. Bugfix on 0.1.2.x.
5934 - Unmap the extrainfo cache file on exit.
5937 Changes in version 0.2.0.5-alpha - 2007-08-19
5938 This fifth development snapshot fixes compilation on Windows again;
5939 fixes an obnoxious client-side bug that slowed things down and put
5940 extra load on the network; gets us closer to using the v3 directory
5941 voting scheme; makes it easier for Tor controllers to use cookie-based
5942 authentication; and fixes a variety of other bugs.
5945 - Version 1 directories are no longer generated in full. Instead,
5946 authorities generate and serve "stub" v1 directories that list
5947 no servers. This will stop Tor versions 0.1.0.x and earlier from
5948 working, but (for security reasons) nobody should be running those
5951 o Major bugfixes (compilation, 0.2.0.x):
5952 - Try to fix Win32 compilation again: improve checking for IPv6 types.
5953 - Try to fix MSVC compilation: build correctly on platforms that do
5954 not define s6_addr16 or s6_addr32.
5955 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
5958 o Major bugfixes (stream expiration):
5959 - Expire not-yet-successful application streams in all cases if
5960 they've been around longer than SocksTimeout. Right now there are
5961 some cases where the stream will live forever, demanding a new
5962 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
5965 o Minor features (directory servers):
5966 - When somebody requests a list of statuses or servers, and we have
5967 none of those, return a 404 rather than an empty 200.
5969 o Minor features (directory voting):
5970 - Store v3 consensus status consensuses on disk, and reload them
5973 o Minor features (security):
5974 - Warn about unsafe ControlPort configurations.
5975 - Refuse to start with certain directory authority keys, and
5976 encourage people using them to stop.
5978 o Minor features (controller):
5979 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
5980 is valid before any authentication has been received. It tells
5981 a controller what kind of authentication is expected, and what
5982 protocol is spoken. Implements proposal 119.
5983 - New config option CookieAuthFile to choose a new location for the
5984 cookie authentication file, and config option
5985 CookieAuthFileGroupReadable to make it group-readable.
5987 o Minor features (unit testing):
5988 - Add command-line arguments to unit-test executable so that we can
5989 invoke any chosen test from the command line rather than having
5990 to run the whole test suite at once; and so that we can turn on
5991 logging for the unit tests.
5993 o Minor bugfixes (on 0.1.2.x):
5994 - If we require CookieAuthentication but we fail to write the
5995 cookie file, we would warn but not exit, and end up in a state
5996 where no controller could authenticate. Now we exit.
5997 - If we require CookieAuthentication, stop generating a new cookie
5998 every time we change any piece of our config.
5999 - When loading bandwidth history, do not believe any information in
6000 the future. Fixes bug 434.
6001 - When loading entry guard information, do not believe any information
6003 - When we have our clock set far in the future and generate an
6004 onion key, then re-set our clock to be correct, we should not stop
6005 the onion key from getting rotated.
6006 - Clean up torrc sample config file.
6007 - Do not automatically run configure from autogen.sh. This
6008 non-standard behavior tended to annoy people who have built other
6011 o Minor bugfixes (on 0.2.0.x):
6012 - Fix a bug with AutomapHostsOnResolve that would always cause
6013 the second request to fail. Bug reported by Kate. Bugfix on
6015 - Fix a bug in ADDRMAP controller replies that would sometimes
6016 try to print a NULL. Patch from tup.
6017 - Read v3 directory authority keys from the right location.
6018 - Numerous bugfixes to directory voting code.
6021 Changes in version 0.1.2.16 - 2007-08-01
6022 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
6023 remote attacker in certain situations to rewrite the user's torrc
6024 configuration file. This can completely compromise anonymity of users
6025 in most configurations, including those running the Vidalia bundles,
6026 TorK, etc. Or worse.
6028 o Major security fixes:
6029 - Close immediately after missing authentication on control port;
6030 do not allow multiple authentication attempts.
6033 Changes in version 0.2.0.4-alpha - 2007-08-01
6034 This fourth development snapshot fixes a critical security vulnerability
6035 for most users, specifically those running Vidalia, TorK, etc. Everybody
6036 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
6038 o Major security fixes:
6039 - Close immediately after missing authentication on control port;
6040 do not allow multiple authentication attempts.
6042 o Major bugfixes (compilation):
6043 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
6046 o Minor features (performance):
6047 - Be even more aggressive about releasing RAM from small
6048 empty buffers. Thanks to our free-list code, this shouldn't be too
6049 performance-intensive.
6050 - Disable sentinel-based debugging for buffer code: we squashed all
6051 the bugs that this was supposed to detect a long time ago, and
6052 now its only effect is to change our buffer sizes from nice
6053 powers of two (which platform mallocs tend to like) to values
6054 slightly over powers of two (which make some platform mallocs sad).
6055 - Log malloc statistics from mallinfo() on platforms where it
6059 Changes in version 0.2.0.3-alpha - 2007-07-29
6060 This third development snapshot introduces new experimental
6061 blocking-resistance features and a preliminary version of the v3
6062 directory voting design, and includes many other smaller features
6066 - The first pieces of our "bridge" design for blocking-resistance
6067 are implemented. People can run bridge directory authorities;
6068 people can run bridges; and people can configure their Tor clients
6069 with a set of bridges to use as the first hop into the Tor network.
6070 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
6072 - Create listener connections before we setuid to the configured
6073 User and Group. Now non-Windows users can choose port values
6074 under 1024, start Tor as root, and have Tor bind those ports
6075 before it changes to another UID. (Windows users could already
6077 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
6078 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
6079 on "vserver" accounts. (Patch from coderman.)
6080 - Be even more aggressive about separating local traffic from relayed
6081 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
6083 o Major features (experimental):
6084 - First cut of code for "v3 dir voting": directory authorities will
6085 vote on a common network status document rather than each publishing
6086 their own opinion. This code needs more testing and more corner-case
6087 handling before it's ready for use.
6090 - Directory authorities now call routers Fast if their bandwidth is
6091 at least 100KB/s, and consider their bandwidth adequate to be a
6092 Guard if it is at least 250KB/s, no matter the medians. This fix
6093 complements proposal 107. [Bugfix on 0.1.2.x]
6094 - Directory authorities now never mark more than 3 servers per IP as
6095 Valid and Running. (Implements proposal 109, by Kevin Bauer and
6097 - Minor change to organizationName and commonName generation
6098 procedures in TLS certificates during Tor handshakes, to invalidate
6099 some earlier censorware approaches. This is not a long-term
6100 solution, but applying it will give us a bit of time to look into
6101 the epidemiology of countermeasures as they spread.
6103 o Major bugfixes (directory):
6104 - Rewrite directory tokenization code to never run off the end of
6105 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
6107 o Minor features (controller):
6108 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
6109 match requests to applications. (Patch from Robert Hogan.)
6110 - Report address and port correctly on connections to DNSPort. (Patch
6112 - Add a RESOLVE command to launch hostname lookups. (Original patch
6114 - Add GETINFO status/enough-dir-info to let controllers tell whether
6115 Tor has downloaded sufficient directory information. (Patch
6117 - You can now use the ControlSocket option to tell Tor to listen for
6118 controller connections on Unix domain sockets on systems that
6119 support them. (Patch from Peter Palfrader.)
6120 - STREAM NEW events are generated for DNSPort requests and for
6121 tunneled directory connections. (Patch from Robert Hogan.)
6122 - New "GETINFO address-mappings/*" command to get address mappings
6123 with expiry information. "addr-mappings/*" is now deprecated.
6126 o Minor features (misc):
6127 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
6129 - The tor-gencert tool for v3 directory authorities now creates all
6130 files as readable to the file creator only, and write-protects
6131 the authority identity key.
6132 - When dumping memory usage, list bytes used in buffer memory
6134 - When running with dmalloc, dump more stats on hup and on exit.
6135 - Directory authorities now fail quickly and (relatively) harmlessly
6136 if they generate a network status document that is somehow
6139 o Traffic load balancing improvements:
6140 - If exit bandwidth ever exceeds one third of total bandwidth, then
6141 use the correct formula to weight exit nodes when choosing paths.
6142 (Based on patch from Mike Perry.)
6143 - Choose perfectly fairly among routers when choosing by bandwidth and
6144 weighting by fraction of bandwidth provided by exits. Previously, we
6145 would choose with only approximate fairness, and correct ourselves
6146 if we ran off the end of the list. [Bugfix on 0.1.2.x]
6148 o Performance improvements:
6149 - Be more aggressive with freeing buffer RAM or putting it on the
6151 - Use Critical Sections rather than Mutexes for synchronizing threads
6152 on win32; Mutexes are heavier-weight, and designed for synchronizing
6155 o Deprecated and removed features:
6156 - RedirectExits is now deprecated.
6157 - Stop allowing address masks that do not correspond to bit prefixes.
6158 We have warned about these for a really long time; now it's time
6159 to reject them. (Patch from croup.)
6161 o Minor bugfixes (directory):
6162 - Fix another crash bug related to extra-info caching. (Bug found by
6163 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
6164 - Directories no longer return a "304 not modified" when they don't
6165 have the networkstatus the client asked for. Also fix a memory
6166 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
6167 - We had accidentally labelled 0.1.2.x directory servers as not
6168 suitable for begin_dir requests, and had labelled no directory
6169 servers as suitable for uploading extra-info documents. [Bugfix
6172 o Minor bugfixes (dns):
6173 - Fix a crash when DNSPort is set more than once. (Patch from Robert
6174 Hogan.) [Bugfix on 0.2.0.2-alpha]
6175 - Add DNSPort connections to the global connection list, so that we
6176 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
6178 - Fix a dangling reference that could lead to a crash when DNSPort is
6179 changed or closed (Patch from Robert Hogan.) [Bugfix on
6182 o Minor bugfixes (controller):
6183 - Provide DNS expiry times in GMT, not in local time. For backward
6184 compatibility, ADDRMAP events only provide GMT expiry in an extended
6185 field. "GETINFO address-mappings" always does the right thing.
6186 - Use CRLF line endings properly in NS events.
6187 - Terminate multi-line control events properly. (Original patch
6188 from tup.) [Bugfix on 0.1.2.x-alpha]
6189 - Do not include spaces in SOURCE_ADDR fields in STREAM
6190 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
6193 Changes in version 0.1.2.15 - 2007-07-17
6194 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
6195 problems, fixes compilation on BSD, and fixes a variety of other
6196 bugs. Everybody should upgrade.
6198 o Major bugfixes (compilation):
6199 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
6201 o Major bugfixes (crashes):
6202 - Try even harder not to dereference the first character after
6203 an mmap(). Reported by lodger.
6204 - Fix a crash bug in directory authorities when we re-number the
6205 routerlist while inserting a new router.
6206 - When the cached-routers file is an even multiple of the page size,
6207 don't run off the end and crash. (Fixes bug 455; based on idea
6209 - Fix eventdns.c behavior on Solaris: It is critical to include
6210 orconfig.h _before_ sys/types.h, so that we can get the expected
6211 definition of _FILE_OFFSET_BITS.
6213 o Major bugfixes (security):
6214 - Fix a possible buffer overrun when using BSD natd support. Bug
6216 - When sending destroy cells from a circuit's origin, don't include
6217 the reason for tearing down the circuit. The spec says we didn't,
6218 and now we actually don't. Reported by lodger.
6219 - Keep streamids from different exits on a circuit separate. This
6220 bug may have allowed other routers on a given circuit to inject
6221 cells into streams. Reported by lodger; fixes bug 446.
6222 - If there's a never-before-connected-to guard node in our list,
6223 never choose any guards past it. This way we don't expand our
6224 guard list unless we need to.
6226 o Minor bugfixes (guard nodes):
6227 - Weight guard selection by bandwidth, so that low-bandwidth nodes
6228 don't get overused as guards.
6230 o Minor bugfixes (directory):
6231 - Correctly count the number of authorities that recommend each
6232 version. Previously, we were under-counting by 1.
6233 - Fix a potential crash bug when we load many server descriptors at
6234 once and some of them make others of them obsolete. Fixes bug 458.
6236 o Minor bugfixes (hidden services):
6237 - Stop tearing down the whole circuit when the user asks for a
6238 connection to a port that the hidden service didn't configure.
6241 o Minor bugfixes (misc):
6242 - On Windows, we were preventing other processes from reading
6243 cached-routers while Tor was running. Reported by janbar.
6244 - Fix a possible (but very unlikely) bug in picking routers by
6245 bandwidth. Add a log message to confirm that it is in fact
6246 unlikely. Patch from lodger.
6247 - Backport a couple of memory leak fixes.
6248 - Backport miscellaneous cosmetic bugfixes.
6251 Changes in version 0.2.0.2-alpha - 2007-06-02
6252 o Major bugfixes on 0.2.0.1-alpha:
6253 - Fix an assertion failure related to servers without extra-info digests.
6254 Resolves bugs 441 and 442.
6256 o Minor features (directory):
6257 - Support "If-Modified-Since" when answering HTTP requests for
6258 directories, running-routers documents, and network-status documents.
6259 (There's no need to support it for router descriptors, since those
6260 are downloaded by descriptor digest.)
6262 o Minor build issues:
6263 - Clear up some MIPSPro compiler warnings.
6264 - When building from a tarball on a machine that happens to have SVK
6265 installed, report the micro-revision as whatever version existed
6266 in the tarball, not as "x".
6269 Changes in version 0.2.0.1-alpha - 2007-06-01
6270 This early development snapshot provides new features for people running
6271 Tor as both a client and a server (check out the new RelayBandwidth
6272 config options); lets Tor run as a DNS proxy; and generally moves us
6273 forward on a lot of fronts.
6275 o Major features, server usability:
6276 - New config options RelayBandwidthRate and RelayBandwidthBurst:
6277 a separate set of token buckets for relayed traffic. Right now
6278 relayed traffic is defined as answers to directory requests, and
6279 OR connections that don't have any local circuits on them.
6281 o Major features, client usability:
6282 - A client-side DNS proxy feature to replace the need for
6283 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
6284 for DNS requests on port 9999, use the Tor network to resolve them
6285 anonymously, and send the reply back like a regular DNS server.
6286 The code still only implements a subset of DNS.
6287 - Make PreferTunneledDirConns and TunnelDirConns work even when
6288 we have no cached directory info. This means Tor clients can now
6289 do all of their connections protected by TLS.
6291 o Major features, performance and efficiency:
6292 - Directory authorities accept and serve "extra info" documents for
6293 routers. These documents contain fields from router descriptors
6294 that aren't usually needed, and that use a lot of excess
6295 bandwidth. Once these fields are removed from router descriptors,
6296 the bandwidth savings should be about 60%. [Partially implements
6298 - Servers upload extra-info documents to any authority that accepts
6299 them. Authorities (and caches that have been configured to download
6300 extra-info documents) download them as needed. [Partially implements
6302 - Change the way that Tor buffers data that it is waiting to write.
6303 Instead of queueing data cells in an enormous ring buffer for each
6304 client->OR or OR->OR connection, we now queue cells on a separate
6305 queue for each circuit. This lets us use less slack memory, and
6306 will eventually let us be smarter about prioritizing different kinds
6308 - Use memory pools to allocate cells with better speed and memory
6309 efficiency, especially on platforms where malloc() is inefficient.
6310 - Stop reading on edge connections when their corresponding circuit
6311 buffers are full; start again as the circuits empty out.
6313 o Major features, other:
6314 - Add an HSAuthorityRecordStats option that hidden service authorities
6315 can use to track statistics of overall hidden service usage without
6316 logging information that would be very useful to an attacker.
6317 - Start work implementing multi-level keys for directory authorities:
6318 Add a standalone tool to generate key certificates. (Proposal 103.)
6321 - Directory authorities now call routers Stable if they have an
6322 uptime of at least 30 days, even if that's not the median uptime
6323 in the network. Implements proposal 107, suggested by Kevin Bauer
6326 o Minor fixes (resource management):
6327 - Count the number of open sockets separately from the number
6328 of active connection_t objects. This will let us avoid underusing
6329 our allocated connection limit.
6330 - We no longer use socket pairs to link an edge connection to an
6331 anonymous directory connection or a DirPort test connection.
6332 Instead, we track the link internally and transfer the data
6333 in-process. This saves two sockets per "linked" connection (at the
6334 client and at the server), and avoids the nasty Windows socketpair()
6336 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
6337 for every single inactive connection_t. Free items from the
6338 4k/16k-buffer free lists when they haven't been used for a while.
6340 o Minor features (build):
6341 - Make autoconf search for libevent, openssl, and zlib consistently.
6342 - Update deprecated macros in configure.in.
6343 - When warning about missing headers, tell the user to let us
6344 know if the compile succeeds anyway, so we can downgrade the
6346 - Include the current subversion revision as part of the version
6347 string: either fetch it directly if we're in an SVN checkout, do
6348 some magic to guess it if we're in an SVK checkout, or use
6349 the last-detected version if we're building from a .tar.gz.
6350 Use this version consistently in log messages.
6352 o Minor features (logging):
6353 - Always prepend "Bug: " to any log message about a bug.
6354 - Put a platform string (e.g. "Linux i686") in the startup log
6355 message, so when people paste just their logs, we know if it's
6356 OpenBSD or Windows or what.
6357 - When logging memory usage, break down memory used in buffers by
6360 o Minor features (directory system):
6361 - New config option V2AuthoritativeDirectory that all directory
6362 authorities should set. This will let future authorities choose
6363 not to serve V2 directory information.
6364 - Directory authorities allow multiple router descriptors and/or extra
6365 info documents to be uploaded in a single go. This will make
6366 implementing proposal 104 simpler.
6368 o Minor features (controller):
6369 - Add a new config option __DisablePredictedCircuits designed for
6370 use by the controller, when we don't want Tor to build any circuits
6372 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
6373 so we can exit from the middle of the circuit.
6374 - Implement "getinfo status/circuit-established".
6375 - Implement "getinfo status/version/..." so a controller can tell
6376 whether the current version is recommended, and whether any versions
6377 are good, and how many authorities agree. (Patch from shibz.)
6379 o Minor features (hidden services):
6380 - Allow multiple HiddenServicePort directives with the same virtual
6381 port; when they occur, the user is sent round-robin to one
6382 of the target ports chosen at random. Partially fixes bug 393 by
6383 adding limited ad-hoc round-robining.
6385 o Minor features (other):
6387 - Add a new AutomapHostsOnResolve option: when it is enabled, any
6388 resolve request for hosts matching a given pattern causes Tor to
6389 generate an internal virtual address mapping for that host. This
6390 allows DNSPort to work sensibly with hidden service users. By
6391 default, .exit and .onion addresses are remapped; the list of
6392 patterns can be reconfigured with AutomapHostsSuffixes.
6393 - Add an "-F" option to tor-resolve to force a resolve for a .onion
6394 address. Thanks to the AutomapHostsOnResolve option, this is no
6395 longer a completely silly thing to do.
6396 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
6397 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
6398 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
6399 minus 1 byte: the actual maximum declared bandwidth.
6402 - Removed support for the old binary "version 0" controller protocol.
6403 This has been deprecated since 0.1.1, and warnings have been issued
6404 since 0.1.2. When we encounter a v0 control message, we now send
6405 back an error and close the connection.
6406 - Remove the old "dns worker" server DNS code: it hasn't been default
6407 since 0.1.2.2-alpha, and all the servers seem to be using the new
6410 o Minor bugfixes (portability):
6411 - Even though Windows is equally happy with / and \ as path separators,
6412 try to use \ consistently on Windows and / consistently on Unix: it
6413 makes the log messages nicer.
6414 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
6415 - Read resolv.conf files correctly on platforms where read() returns
6416 partial results on small file reads.
6418 o Minor bugfixes (directory):
6419 - Correctly enforce that elements of directory objects do not appear
6420 more often than they are allowed to appear.
6421 - When we are reporting the DirServer line we just parsed, we were
6422 logging the second stanza of the key fingerprint, not the first.
6424 o Minor bugfixes (logging):
6425 - When we hit an EOF on a log (probably because we're shutting down),
6426 don't try to remove the log from the list: just mark it as
6427 unusable. (Bulletproofs against bug 222.)
6429 o Minor bugfixes (other):
6430 - In the exitlist script, only consider the most recently published
6431 server descriptor for each server. Also, when the user requests
6432 a list of servers that _reject_ connections to a given address,
6433 explicitly exclude the IPs that also have servers that accept
6434 connections to that address. (Resolves bug 405.)
6435 - Stop allowing hibernating servers to be "stable" or "fast".
6436 - On Windows, we were preventing other processes from reading
6437 cached-routers while Tor was running. (Reported by janbar)
6438 - Make the NodeFamilies config option work. (Reported by
6439 lodger -- it has never actually worked, even though we added it
6441 - Check return values from pthread_mutex functions.
6442 - Don't save non-general-purpose router descriptors to the disk cache,
6443 because we have no way of remembering what their purpose was when
6445 - Add even more asserts to hunt down bug 417.
6446 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
6447 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
6448 Add a log message to confirm that it is in fact unlikely.
6450 o Minor bugfixes (controller):
6451 - Make 'getinfo fingerprint' return a 551 error if we're not a
6452 server, so we match what the control spec claims we do. Reported
6454 - Fix a typo in an error message when extendcircuit fails that
6455 caused us to not follow the \r\n-based delimiter protocol. Reported
6458 o Code simplifications and refactoring:
6459 - Stop passing around circuit_t and crypt_path_t pointers that are
6460 implicit in other procedure arguments.
6461 - Drop the old code to choke directory connections when the
6462 corresponding OR connections got full: thanks to the cell queue
6463 feature, OR conns don't get full any more.
6464 - Make dns_resolve() handle attaching connections to circuits
6465 properly, so the caller doesn't have to.
6466 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
6467 - Keep the connection array as a dynamic smartlist_t, rather than as
6468 a fixed-sized array. This is important, as the number of connections
6469 is becoming increasingly decoupled from the number of sockets.
6472 Changes in version 0.1.2.14 - 2007-05-25
6473 Tor 0.1.2.14 changes the addresses of two directory authorities (this
6474 change especially affects those who serve or use hidden services),
6475 and fixes several other crash- and security-related bugs.
6477 o Directory authority changes:
6478 - Two directory authorities (moria1 and moria2) just moved to new
6479 IP addresses. This change will particularly affect those who serve
6480 or use hidden services.
6482 o Major bugfixes (crashes):
6483 - If a directory server runs out of space in the connection table
6484 as it's processing a begin_dir request, it will free the exit stream
6485 but leave it attached to the circuit, leading to unpredictable
6486 behavior. (Reported by seeess, fixes bug 425.)
6487 - Fix a bug in dirserv_remove_invalid() that would cause authorities
6488 to corrupt memory under some really unlikely scenarios.
6489 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
6490 - Avoid segfaults when reading from mmaped descriptor file. (Reported
6493 o Major bugfixes (security):
6494 - When choosing an entry guard for a circuit, avoid using guards
6495 that are in the same family as the chosen exit -- not just guards
6496 that are exactly the chosen exit. (Reported by lodger.)
6498 o Major bugfixes (resource management):
6499 - If a directory authority is down, skip it when deciding where to get
6500 networkstatus objects or descriptors. Otherwise we keep asking
6501 every 10 seconds forever. Fixes bug 384.
6502 - Count it as a failure if we fetch a valid network-status but we
6503 don't want to keep it. Otherwise we'll keep fetching it and keep
6504 not wanting to keep it. Fixes part of bug 422.
6505 - If all of our dirservers have given us bad or no networkstatuses
6506 lately, then stop hammering them once per minute even when we
6507 think they're failed. Fixes another part of bug 422.
6510 - Actually set the purpose correctly for descriptors inserted with
6512 - When we have k non-v2 authorities in our DirServer config,
6513 we ignored the last k authorities in the list when updating our
6515 - Correctly back-off from requesting router descriptors that we are
6516 having a hard time downloading.
6517 - Read resolv.conf files correctly on platforms where read() returns
6518 partial results on small file reads.
6519 - Don't rebuild the entire router store every time we get 32K of
6520 routers: rebuild it when the journal gets very large, or when
6521 the gaps in the store get very large.
6524 - When routers publish SVN revisions in their router descriptors,
6525 authorities now include those versions correctly in networkstatus
6527 - Warn when using a version of libevent before 1.3b to run a server on
6528 OSX or BSD: these versions interact badly with userspace threads.
6531 Changes in version 0.1.2.13 - 2007-04-24
6532 This release features some major anonymity fixes, such as safer path
6533 selection; better client performance; faster bootstrapping, better
6534 address detection, and better DNS support for servers; write limiting as
6535 well as read limiting to make servers easier to run; and a huge pile of
6536 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
6538 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
6539 of the Freenode IRC network, remembering his patience and vision for
6540 free speech on the Internet.
6543 - Fix a memory leak when we ask for "all" networkstatuses and we
6544 get one we don't recognize.
6545 - Add more asserts to hunt down bug 417.
6546 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
6549 Changes in version 0.1.2.12-rc - 2007-03-16
6551 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
6552 directory information requested inside Tor connections (i.e. via
6553 begin_dir cells). It only triggered when the same connection was
6554 serving other data at the same time. Reported by seeess.
6557 - When creating a circuit via the controller, send a 'launched'
6558 event when we're done, so we follow the spec better.
6561 Changes in version 0.1.2.11-rc - 2007-03-15
6562 o Minor bugfixes (controller), reported by daejees:
6563 - Correct the control spec to match how the code actually responds
6564 to 'getinfo addr-mappings/*'.
6565 - The control spec described a GUARDS event, but the code
6566 implemented a GUARD event. Standardize on GUARD, but let people
6570 Changes in version 0.1.2.10-rc - 2007-03-07
6571 o Major bugfixes (Windows):
6572 - Do not load the NT services library functions (which may not exist)
6573 just to detect if we're a service trying to shut down. Now we run
6574 on Win98 and friends again.
6576 o Minor bugfixes (other):
6577 - Clarify a couple of log messages.
6578 - Fix a misleading socks5 error number.
6581 Changes in version 0.1.2.9-rc - 2007-03-02
6582 o Major bugfixes (Windows):
6583 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
6584 of the usual GCC "%llu". This prevents a bug when saving 64-bit
6585 int configuration values: the high-order 32 bits would get
6586 truncated. In particular, we were being bitten by the default
6587 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
6588 and maybe also bug 397.)
6590 o Minor bugfixes (performance):
6591 - Use OpenSSL's AES implementation on platforms where it's faster.
6592 This could save us as much as 10% CPU usage.
6594 o Minor bugfixes (server):
6595 - Do not rotate onion key immediately after setting it for the first
6598 o Minor bugfixes (directory authorities):
6599 - Stop calling servers that have been hibernating for a long time
6600 "stable". Also, stop letting hibernating or obsolete servers affect
6601 uptime and bandwidth cutoffs.
6602 - Stop listing hibernating servers in the v1 directory.
6604 o Minor bugfixes (hidden services):
6605 - Upload hidden service descriptors slightly less often, to reduce
6606 load on authorities.
6608 o Minor bugfixes (other):
6609 - Fix an assert that could trigger if a controller quickly set then
6610 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
6611 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
6613 - Fix a potential race condition in the rpm installer. Found by
6615 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
6616 of 2 as indicating that the server is completely bad; it sometimes
6617 means that the server is just bad for the request in question. (may fix
6618 the last of bug 326.)
6619 - Disable encrypted directory connections when we don't have a server
6620 descriptor for the destination. We'll get this working again in
6624 Changes in version 0.1.2.8-beta - 2007-02-26
6625 o Major bugfixes (crashes):
6626 - Stop crashing when the controller asks us to resetconf more than
6627 one config option at once. (Vidalia 0.0.11 does this.)
6628 - Fix a crash that happened on Win98 when we're given command-line
6629 arguments: don't try to load NT service functions from advapi32.dll
6630 except when we need them. (Bug introduced in 0.1.2.7-alpha;
6632 - Fix a longstanding obscure crash bug that could occur when
6633 we run out of DNS worker processes. (Resolves bug 390.)
6635 o Major bugfixes (hidden services):
6636 - Correctly detect whether hidden service descriptor downloads are
6637 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
6639 o Major bugfixes (accounting):
6640 - When we start during an accounting interval before it's time to wake
6641 up, remember to wake up at the correct time. (May fix bug 342.)
6643 o Minor bugfixes (controller):
6644 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
6645 clear the corresponding on_circuit variable, and remember later
6646 that we don't need to send a redundant CLOSED event. (Resolves part
6648 - Report events where a resolve succeeded or where we got a socks
6649 protocol error correctly, rather than calling both of them
6651 - Change reported stream target addresses to IP consistently when
6652 we finally get the IP from an exit node.
6653 - Send log messages to the controller even if they happen to be very
6656 o Minor bugfixes (other):
6657 - Display correct results when reporting which versions are
6658 recommended, and how recommended they are. (Resolves bug 383.)
6659 - Improve our estimates for directory bandwidth to be less random:
6660 guess that an unrecognized directory will have the average bandwidth
6661 from all known directories, not that it will have the average
6662 bandwidth from those directories earlier than it on the list.
6663 - If we start a server with ClientOnly 1, then set ClientOnly to 0
6664 and hup, stop triggering an assert based on an empty onion_key.
6665 - On platforms with no working mmap() equivalent, don't warn the
6666 user when cached-routers doesn't exist.
6667 - Warn the user when mmap() [or its equivalent] fails for some reason
6668 other than file-not-found.
6669 - Don't warn the user when cached-routers.new doesn't exist: that's
6670 perfectly fine when starting up for the first time.
6671 - When EntryNodes are configured, rebuild the guard list to contain,
6672 in order: the EntryNodes that were guards before; the rest of the
6673 EntryNodes; the nodes that were guards before.
6674 - Mask out all signals in sub-threads; only the libevent signal
6675 handler should be processing them. This should prevent some crashes
6676 on some machines using pthreads. (Patch from coderman.)
6677 - Fix switched arguments on memset in the implementation of
6678 tor_munmap() for systems with no mmap() call.
6679 - When Tor receives a router descriptor that it asked for, but
6680 no longer wants (because it has received fresh networkstatuses
6681 in the meantime), do not warn the user. Cache the descriptor if
6682 we're a cache; drop it if we aren't.
6683 - Make earlier entry guards _really_ get retried when the network
6685 - On a malformed DNS reply, always give an error to the corresponding
6687 - Build with recent libevents on platforms that do not define the
6688 nonstandard types "u_int8_t" and friends.
6690 o Minor features (controller):
6691 - Warn the user when an application uses the obsolete binary v0
6692 control protocol. We're planning to remove support for it during
6693 the next development series, so it's good to give people some
6695 - Add STREAM_BW events to report per-entry-stream bandwidth
6696 use. (Patch from Robert Hogan.)
6697 - Rate-limit SIGNEWNYM signals in response to controllers that
6698 impolitely generate them for every single stream. (Patch from
6699 mwenge; closes bug 394.)
6700 - Make REMAP stream events have a SOURCE (cache or exit), and
6701 make them generated in every case where we get a successful
6702 connected or resolved cell.
6704 o Minor bugfixes (performance):
6705 - Call router_have_min_dir_info half as often. (This is showing up in
6706 some profiles, but not others.)
6707 - When using GCC, make log_debug never get called at all, and its
6708 arguments never get evaluated, when no debug logs are configured.
6709 (This is showing up in some profiles, but not others.)
6712 - Remove some never-implemented options. Mark PathlenCoinWeight as
6714 - Implement proposal 106: Stop requiring clients to have well-formed
6715 certificates; stop checking nicknames in certificates. (Clients
6716 have certificates so that they can look like Tor servers, but in
6717 the future we might want to allow them to look like regular TLS
6718 clients instead. Nicknames in certificates serve no purpose other
6719 than making our protocol easier to recognize on the wire.)
6720 - Revise messages on handshake failure again to be even more clear about
6721 which are incoming connections and which are outgoing.
6722 - Discard any v1 directory info that's over 1 month old (for
6723 directories) or over 1 week old (for running-routers lists).
6724 - Do not warn when individual nodes in the configuration's EntryNodes,
6725 ExitNodes, etc are down: warn only when all possible nodes
6726 are down. (Fixes bug 348.)
6727 - Always remove expired routers and networkstatus docs before checking
6728 whether we have enough information to build circuits. (Fixes
6730 - Put a lower-bound on MaxAdvertisedBandwidth.
6733 Changes in version 0.1.2.7-alpha - 2007-02-06
6734 o Major bugfixes (rate limiting):
6735 - Servers decline directory requests much more aggressively when
6736 they're low on bandwidth. Otherwise they end up queueing more and
6737 more directory responses, which can't be good for latency.
6738 - But never refuse directory requests from local addresses.
6739 - Fix a memory leak when sending a 503 response for a networkstatus
6741 - Be willing to read or write on local connections (e.g. controller
6742 connections) even when the global rate limiting buckets are empty.
6743 - If our system clock jumps back in time, don't publish a negative
6744 uptime in the descriptor. Also, don't let the global rate limiting
6745 buckets go absurdly negative.
6746 - Flush local controller connection buffers periodically as we're
6747 writing to them, so we avoid queueing 4+ megabytes of data before
6750 o Major bugfixes (NT services):
6751 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
6752 command-line flag so that admins can override the default by saying
6753 "tor --service install --user "SomeUser"". This will not affect
6754 existing installed services. Also, warn the user that the service
6755 will look for its configuration file in the service user's
6756 %appdata% directory. (We can't do the 'hardwire the user's appdata
6757 directory' trick any more, since we may not have read access to that
6760 o Major bugfixes (other):
6761 - Previously, we would cache up to 16 old networkstatus documents
6762 indefinitely, if they came from nontrusted authorities. Now we
6763 discard them if they are more than 10 days old.
6764 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
6766 - Detect and reject malformed DNS responses containing circular
6768 - If exits are rare enough that we're not marking exits as guards,
6769 ignore exit bandwidth when we're deciding the required bandwidth
6771 - When we're handling a directory connection tunneled over Tor,
6772 don't fill up internal memory buffers with all the data we want
6773 to tunnel; instead, only add it if the OR connection that will
6774 eventually receive it has some room for it. (This can lead to
6775 slowdowns in tunneled dir connections; a better solution will have
6778 o Minor bugfixes (dns):
6779 - Add some defensive programming to eventdns.c in an attempt to catch
6780 possible memory-stomping bugs.
6781 - Detect and reject DNS replies containing IPv4 or IPv6 records with
6782 an incorrect number of bytes. (Previously, we would ignore the
6784 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
6785 in the correct order, and doesn't crash.
6786 - Free memory held in recently-completed DNS lookup attempts on exit.
6787 This was not a memory leak, but may have been hiding memory leaks.
6788 - Handle TTL values correctly on reverse DNS lookups.
6789 - Treat failure to parse resolv.conf as an error.
6791 o Minor bugfixes (other):
6792 - Fix crash with "tor --list-fingerprint" (reported by seeess).
6793 - When computing clock skew from directory HTTP headers, consider what
6794 time it was when we finished asking for the directory, not what
6796 - Expire socks connections if they spend too long waiting for the
6797 handshake to finish. Previously we would let them sit around for
6798 days, if the connecting application didn't close them either.
6799 - And if the socks handshake hasn't started, don't send a
6800 "DNS resolve socks failed" handshake reply; just close it.
6801 - Stop using C functions that OpenBSD's linker doesn't like.
6802 - Don't launch requests for descriptors unless we have networkstatuses
6803 from at least half of the authorities. This delays the first
6804 download slightly under pathological circumstances, but can prevent
6805 us from downloading a bunch of descriptors we don't need.
6806 - Do not log IPs with TLS failures for incoming TLS
6807 connections. (Fixes bug 382.)
6808 - If the user asks to use invalid exit nodes, be willing to use
6810 - Stop using the reserved ac_cv namespace in our configure script.
6811 - Call stat() slightly less often; use fstat() when possible.
6812 - Refactor the way we handle pending circuits when an OR connection
6813 completes or fails, in an attempt to fix a rare crash bug.
6814 - Only rewrite a conn's address based on X-Forwarded-For: headers
6815 if it's a parseable public IP address; and stop adding extra quotes
6816 to the resulting address.
6819 - Weight directory requests by advertised bandwidth. Now we can
6820 let servers enable write limiting but still allow most clients to
6821 succeed at their directory requests. (We still ignore weights when
6822 choosing a directory authority; I hope this is a feature.)
6825 - Create a new file ReleaseNotes which was the old ChangeLog. The
6826 new ChangeLog file now includes the summaries for all development
6828 - Check for addresses with invalid characters at the exit as well
6829 as at the client, and warn less verbosely when they fail. You can
6830 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
6831 - Adapt a patch from goodell to let the contrib/exitlist script
6832 take arguments rather than require direct editing.
6833 - Inform the server operator when we decide not to advertise a
6834 DirPort due to AccountingMax enabled or a low BandwidthRate. It
6835 was confusing Zax, so now we're hopefully more helpful.
6836 - Bring us one step closer to being able to establish an encrypted
6837 directory tunnel without knowing a descriptor first. Still not
6838 ready yet. As part of the change, now assume we can use a
6839 create_fast cell if we don't know anything about a router.
6840 - Allow exit nodes to use nameservers running on ports other than 53.
6841 - Servers now cache reverse DNS replies.
6842 - Add an --ignore-missing-torrc command-line option so that we can
6843 get the "use sensible defaults if the configuration file doesn't
6844 exist" behavior even when specifying a torrc location on the command
6847 o Minor features (controller):
6848 - Track reasons for OR connection failure; make these reasons
6849 available via the controller interface. (Patch from Mike Perry.)
6850 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
6851 can learn when clients are sending malformed hostnames to Tor.
6852 - Clean up documentation for controller status events.
6853 - Add a REMAP status to stream events to note that a stream's
6854 address has changed because of a cached address or a MapAddress
6858 Changes in version 0.1.2.6-alpha - 2007-01-09
6860 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
6861 connection handles more than 4 gigs in either direction, we crash.
6862 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
6863 advertised exit node, somebody might try to exit from us when
6864 we're bootstrapping and before we've built our descriptor yet.
6865 Refuse the connection rather than crashing.
6868 - Warn if we (as a server) find that we've resolved an address that we
6869 weren't planning to resolve.
6870 - Warn that using select() on any libevent version before 1.1 will be
6871 unnecessarily slow (even for select()).
6872 - Flush ERR-level controller status events just like we currently
6873 flush ERR-level log events, so that a Tor shutdown doesn't prevent
6874 the controller from learning about current events.
6876 o Minor features (more controller status events):
6877 - Implement EXTERNAL_ADDRESS server status event so controllers can
6878 learn when our address changes.
6879 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
6880 can learn when directories reject our descriptor.
6881 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
6882 can learn when a client application is speaking a non-socks protocol
6884 - Implement DANGEROUS_SOCKS client status event so controllers
6885 can learn when a client application is leaking DNS addresses.
6886 - Implement BUG general status event so controllers can learn when
6887 Tor is unhappy about its internal invariants.
6888 - Implement CLOCK_SKEW general status event so controllers can learn
6889 when Tor thinks the system clock is set incorrectly.
6890 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
6891 server status events so controllers can learn when their descriptors
6892 are accepted by a directory.
6893 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
6894 server status events so controllers can learn about Tor's progress in
6895 deciding whether it's reachable from the outside.
6896 - Implement BAD_LIBEVENT general status event so controllers can learn
6897 when we have a version/method combination in libevent that needs to
6899 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
6900 and DNS_USELESS server status events so controllers can learn
6901 about changes to DNS server status.
6903 o Minor features (directory):
6904 - Authorities no longer recommend exits as guards if this would shift
6905 too much load to the exit nodes.
6908 Changes in version 0.1.2.5-alpha - 2007-01-06
6910 - Enable write limiting as well as read limiting. Now we sacrifice
6911 capacity if we're pushing out lots of directory traffic, rather
6912 than overrunning the user's intended bandwidth limits.
6913 - Include TLS overhead when counting bandwidth usage; previously, we
6914 would count only the bytes sent over TLS, but not the bytes used
6916 - Support running the Tor service with a torrc not in the same
6917 directory as tor.exe and default to using the torrc located in
6918 the %appdata%\Tor\ of the user who installed the service. Patch
6920 - Servers now check for the case when common DNS requests are going to
6921 wildcarded addresses (i.e. all getting the same answer), and change
6922 their exit policy to reject *:* if it's happening.
6923 - Implement BEGIN_DIR cells, so we can connect to the directory
6924 server via TLS to do encrypted directory requests rather than
6925 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
6926 config options if you like.
6928 o Minor features (config and docs):
6929 - Start using the state file to store bandwidth accounting data:
6930 the bw_accounting file is now obsolete. We'll keep generating it
6931 for a while for people who are still using 0.1.2.4-alpha.
6932 - Try to batch changes to the state file so that we do as few
6933 disk writes as possible while still storing important things in
6935 - The state file and the bw_accounting file get saved less often when
6936 the AvoidDiskWrites config option is set.
6937 - Make PIDFile work on Windows (untested).
6938 - Add internal descriptions for a bunch of configuration options:
6939 accessible via controller interface and in comments in saved
6941 - Reject *:563 (NNTPS) in the default exit policy. We already reject
6942 NNTP by default, so this seems like a sensible addition.
6943 - Clients now reject hostnames with invalid characters. This should
6944 avoid some inadvertent info leaks. Add an option
6945 AllowNonRFC953Hostnames to disable this behavior, in case somebody
6946 is running a private network with hosts called @, !, and #.
6947 - Add a maintainer script to tell us which options are missing
6948 documentation: "make check-docs".
6949 - Add a new address-spec.txt document to describe our special-case
6950 addresses: .exit, .onion, and .noconnnect.
6952 o Minor features (DNS):
6953 - Ongoing work on eventdns infrastructure: now it has dns server
6954 and ipv6 support. One day Tor will make use of it.
6955 - Add client-side caching for reverse DNS lookups.
6956 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
6957 - When we change nameservers or IP addresses, reset and re-launch
6958 our tests for DNS hijacking.
6960 o Minor features (directory):
6961 - Authorities now specify server versions in networkstatus. This adds
6962 about 2% to the size of compressed networkstatus docs, and allows
6963 clients to tell which servers support BEGIN_DIR and which don't.
6964 The implementation is forward-compatible with a proposed future
6965 protocol version scheme not tied to Tor versions.
6966 - DirServer configuration lines now have an orport= option so
6967 clients can open encrypted tunnels to the authorities without
6968 having downloaded their descriptors yet. Enabled for moria1,
6969 moria2, tor26, and lefkada now in the default configuration.
6970 - Directory servers are more willing to send a 503 "busy" if they
6971 are near their write limit, especially for v1 directory requests.
6972 Now they can use their limited bandwidth for actual Tor traffic.
6973 - Clients track responses with status 503 from dirservers. After a
6974 dirserver has given us a 503, we try not to use it until an hour has
6975 gone by, or until we have no dirservers that haven't given us a 503.
6976 - When we get a 503 from a directory, and we're not a server, we don't
6977 count the failure against the total number of failures allowed
6978 for the thing we're trying to download.
6979 - Report X-Your-Address-Is correctly from tunneled directory
6980 connections; don't report X-Your-Address-Is when it's an internal
6981 address; and never believe reported remote addresses when they're
6983 - Protect against an unlikely DoS attack on directory servers.
6984 - Add a BadDirectory flag to network status docs so that authorities
6985 can (eventually) tell clients about caches they believe to be
6988 o Minor features (controller):
6989 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
6990 - Reimplement GETINFO so that info/names stays in sync with the
6992 - Implement "GETINFO fingerprint".
6993 - Implement "SETEVENTS GUARD" so controllers can get updates on
6994 entry guard status as it changes.
6996 o Minor features (clean up obsolete pieces):
6997 - Remove some options that have been deprecated since at least
6998 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
6999 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
7001 - We no longer look for identity and onion keys in "identity.key" and
7002 "onion.key" -- these were replaced by secret_id_key and
7003 secret_onion_key in 0.0.8pre1.
7004 - We no longer require unrecognized directory entries to be
7007 o Major bugfixes (security):
7008 - Stop sending the HttpProxyAuthenticator string to directory
7009 servers when directory connections are tunnelled through Tor.
7010 - Clients no longer store bandwidth history in the state file.
7011 - Do not log introduction points for hidden services if SafeLogging
7013 - When generating bandwidth history, round down to the nearest
7014 1k. When storing accounting data, round up to the nearest 1k.
7015 - When we're running as a server, remember when we last rotated onion
7016 keys, so that we will rotate keys once they're a week old even if
7017 we never stay up for a week ourselves.
7019 o Major bugfixes (other):
7020 - Fix a longstanding bug in eventdns that prevented the count of
7021 timed-out resolves from ever being reset. This bug caused us to
7022 give up on a nameserver the third time it timed out, and try it
7023 10 seconds later... and to give up on it every time it timed out
7025 - Take out the '5 second' timeout from the connection retry
7026 schedule. Now the first connect attempt will wait a full 10
7027 seconds before switching to a new circuit. Perhaps this will help
7028 a lot. Based on observations from Mike Perry.
7029 - Fix a bug on the Windows implementation of tor_mmap_file() that
7030 would prevent the cached-routers file from ever loading. Reported
7034 - Fix an assert failure when a directory authority sets
7035 AuthDirRejectUnlisted and then receives a descriptor from an
7036 unlisted router. Reported by seeess.
7037 - Avoid a double-free when parsing malformed DirServer lines.
7038 - Fix a bug when a BSD-style PF socket is first used. Patch from
7040 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
7041 to resolve an address at a given exit node even when they ask for
7043 - Servers no longer ever list themselves in their "family" line,
7044 even if configured to do so. This makes it easier to configure
7045 family lists conveniently.
7046 - When running as a server, don't fall back to 127.0.0.1 when no
7047 nameservers are configured in /etc/resolv.conf; instead, make the
7048 user fix resolv.conf or specify nameservers explicitly. (Resolves
7050 - Stop accepting certain malformed ports in configured exit policies.
7051 - Don't re-write the fingerprint file every restart, unless it has
7053 - Stop warning when a single nameserver fails: only warn when _all_ of
7054 our nameservers have failed. Also, when we only have one nameserver,
7055 raise the threshold for deciding that the nameserver is dead.
7056 - Directory authorities now only decide that routers are reachable
7057 if their identity keys are as expected.
7058 - When the user uses bad syntax in the Log config line, stop
7059 suggesting other bad syntax as a replacement.
7060 - Correctly detect ipv6 DNS capability on OpenBSD.
7062 o Minor bugfixes (controller):
7063 - Report the circuit number correctly in STREAM CLOSED events. Bug
7064 reported by Mike Perry.
7065 - Do not report bizarre values for results of accounting GETINFOs
7066 when the last second's write or read exceeds the allotted bandwidth.
7067 - Report "unrecognized key" rather than an empty string when the
7068 controller tries to fetch a networkstatus that doesn't exist.
7071 Changes in version 0.1.1.26 - 2006-12-14
7072 o Security bugfixes:
7073 - Stop sending the HttpProxyAuthenticator string to directory
7074 servers when directory connections are tunnelled through Tor.
7075 - Clients no longer store bandwidth history in the state file.
7076 - Do not log introduction points for hidden services if SafeLogging
7080 - Fix an assert failure when a directory authority sets
7081 AuthDirRejectUnlisted and then receives a descriptor from an
7082 unlisted router (reported by seeess).
7085 Changes in version 0.1.2.4-alpha - 2006-12-03
7087 - Add support for using natd; this allows FreeBSDs earlier than
7088 5.1.2 to have ipfw send connections through Tor without using
7089 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
7092 - Make all connections to addresses of the form ".noconnect"
7093 immediately get closed. This lets application/controller combos
7094 successfully test whether they're talking to the same Tor by
7095 watching for STREAM events.
7096 - Make cross.sh cross-compilation script work even when autogen.sh
7097 hasn't been run. (Patch from Michael Mohr.)
7098 - Statistics dumped by -USR2 now include a breakdown of public key
7099 operations, for profiling.
7102 - Fix a major leak when directory authorities parse their
7103 approved-routers list, a minor memory leak when we fail to pick
7104 an exit node, and a few rare leaks on errors.
7105 - Handle TransPort connections even when the server sends data before
7106 the client sends data. Previously, the connection would just hang
7107 until the client sent data. (Patch from tup based on patch from
7109 - Avoid assert failure when our cached-routers file is empty on
7113 - Don't log spurious warnings when we see a circuit close reason we
7114 don't recognize; it's probably just from a newer version of Tor.
7115 - Have directory authorities allow larger amounts of drift in uptime
7116 without replacing the server descriptor: previously, a server that
7117 restarted every 30 minutes could have 48 "interesting" descriptors
7119 - Start linking to the Tor specification and Tor reference manual
7120 correctly in the Windows installer.
7121 - Add Vidalia to the OS X uninstaller script, so when we uninstall
7122 Tor/Privoxy we also uninstall Vidalia.
7123 - Resume building on Irix64, and fix a lot of warnings from its
7125 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
7126 when we're running as a client.
7129 Changes in version 0.1.1.25 - 2006-11-04
7131 - When a client asks us to resolve (rather than connect to)
7132 an address, and we have a cached answer, give them the cached
7133 answer. Previously, we would give them no answer at all.
7134 - We were building exactly the wrong circuits when we predict
7135 hidden service requirements, meaning Tor would have to build all
7136 its circuits on demand.
7137 - If none of our live entry guards have a high uptime, but we
7138 require a guard with a high uptime, try adding a new guard before
7139 we give up on the requirement. This patch should make long-lived
7140 connections more stable on average.
7141 - When testing reachability of our DirPort, don't launch new
7142 tests when there's already one in progress -- unreachable
7143 servers were stacking up dozens of testing streams.
7145 o Security bugfixes:
7146 - When the user sends a NEWNYM signal, clear the client-side DNS
7147 cache too. Otherwise we continue to act on previous information.
7150 - Avoid a memory corruption bug when creating a hash table for
7152 - Avoid possibility of controller-triggered crash when misusing
7153 certain commands from a v0 controller on platforms that do not
7154 handle printf("%s",NULL) gracefully.
7155 - Avoid infinite loop on unexpected controller input.
7156 - Don't log spurious warnings when we see a circuit close reason we
7157 don't recognize; it's probably just from a newer version of Tor.
7158 - Add Vidalia to the OS X uninstaller script, so when we uninstall
7159 Tor/Privoxy we also uninstall Vidalia.
7162 Changes in version 0.1.2.3-alpha - 2006-10-29
7164 - Prepare for servers to publish descriptors less often: never
7165 discard a descriptor simply for being too old until either it is
7166 recommended by no authorities, or until we get a better one for
7167 the same router. Make caches consider retaining old recommended
7168 routers for even longer.
7169 - If most authorities set a BadExit flag for a server, clients
7170 don't think of it as a general-purpose exit. Clients only consider
7171 authorities that advertise themselves as listing bad exits.
7172 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
7173 headers for content, so that we can work better in the presence of
7174 caching HTTP proxies.
7175 - Allow authorities to list nodes as bad exits by fingerprint or by
7178 o Minor features, controller:
7179 - Add a REASON field to CIRC events; for backward compatibility, this
7180 field is sent only to controllers that have enabled the extended
7181 event format. Also, add additional reason codes to explain why
7182 a given circuit has been destroyed or truncated. (Patches from
7184 - Add a REMOTE_REASON field to extended CIRC events to tell the
7185 controller about why a remote OR told us to close a circuit.
7186 - Stream events also now have REASON and REMOTE_REASON fields,
7187 working much like those for circuit events.
7188 - There's now a GETINFO ns/... field so that controllers can ask Tor
7189 about the current status of a router.
7190 - A new event type "NS" to inform a controller when our opinion of
7191 a router's status has changed.
7192 - Add a GETINFO events/names and GETINFO features/names so controllers
7193 can tell which events and features are supported.
7194 - A new CLEARDNSCACHE signal to allow controllers to clear the
7195 client-side DNS cache without expiring circuits.
7197 o Security bugfixes:
7198 - When the user sends a NEWNYM signal, clear the client-side DNS
7199 cache too. Otherwise we continue to act on previous information.
7202 - Avoid sending junk to controllers or segfaulting when a controller
7203 uses EVENT_NEW_DESC with verbose nicknames.
7204 - Stop triggering asserts if the controller tries to extend hidden
7205 service circuits (reported by mwenge).
7206 - Avoid infinite loop on unexpected controller input.
7207 - When the controller does a "GETINFO network-status", tell it
7208 about even those routers whose descriptors are very old, and use
7209 long nicknames where appropriate.
7210 - Change NT service functions to be loaded on demand. This lets us
7211 build with MinGW without breaking Tor for Windows 98 users.
7212 - Do DirPort reachability tests less often, since a single test
7213 chews through many circuits before giving up.
7214 - In the hidden service example in torrc.sample, stop recommending
7215 esoteric and discouraged hidden service options.
7216 - When stopping an NT service, wait up to 10 sec for it to actually
7217 stop. (Patch from Matt Edman; resolves bug 295.)
7218 - Fix handling of verbose nicknames with ORCONN controller events:
7219 make them show up exactly when requested, rather than exactly when
7221 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
7222 printing a duplicate "$" in the keys we send (reported by mwenge).
7223 - Correctly set maximum connection limit on Cygwin. (This time
7225 - Try to detect Windows correctly when cross-compiling.
7226 - Detect the size of the routers file correctly even if it is
7227 corrupted (on systems without mmap) or not page-aligned (on systems
7228 with mmap). This bug was harmless.
7229 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
7230 to open a stream fails; now we do in more cases. This should
7231 make clients able to find a good exit faster in some cases, since
7232 unhandleable requests will now get an error rather than timing out.
7233 - Resolve two memory leaks when rebuilding the on-disk router cache
7234 (reported by fookoowa).
7235 - Clean up minor code warnings suggested by the MIPSpro C compiler,
7236 and reported by some Centos users.
7237 - Controller signals now work on non-Unix platforms that don't define
7238 SIGUSR1 and SIGUSR2 the way we expect.
7239 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
7240 values before failing, and always enables eventdns.
7241 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
7242 Try to fix this in configure.in by checking for most functions
7243 before we check for libevent.
7246 Changes in version 0.1.2.2-alpha - 2006-10-07
7248 - Make our async eventdns library on-by-default for Tor servers,
7249 and plan to deprecate the separate dnsworker threads.
7250 - Add server-side support for "reverse" DNS lookups (using PTR
7251 records so clients can determine the canonical hostname for a given
7252 IPv4 address). Only supported by servers using eventdns; servers
7253 now announce in their descriptors whether they support eventdns.
7254 - Specify and implement client-side SOCKS5 interface for reverse DNS
7255 lookups (see doc/socks-extensions.txt).
7256 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
7257 connect to directory servers through Tor. Previously, clients needed
7258 to find Tor exits to make private connections to directory servers.
7259 - Avoid choosing Exit nodes for entry or middle hops when the
7260 total bandwidth available from non-Exit nodes is much higher than
7261 the total bandwidth available from Exit nodes.
7262 - Workaround for name servers (like Earthlink's) that hijack failing
7263 DNS requests and replace the no-such-server answer with a "helpful"
7264 redirect to an advertising-driven search portal. Also work around
7265 DNS hijackers who "helpfully" decline to hijack known-invalid
7266 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
7267 lets you turn it off.
7268 - Send out a burst of long-range padding cells once we've established
7269 that we're reachable. Spread them over 4 circuits, so hopefully
7270 a few will be fast. This exercises our bandwidth and bootstraps
7271 us into the directory more quickly.
7273 o New/improved config options:
7274 - Add new config option "ResolvConf" to let the server operator
7275 choose an alternate resolve.conf file when using eventdns.
7276 - Add an "EnforceDistinctSubnets" option to control our "exclude
7277 servers on the same /16" behavior. It's still on by default; this
7278 is mostly for people who want to operate private test networks with
7279 all the machines on the same subnet.
7280 - If one of our entry guards is on the ExcludeNodes list, or the
7281 directory authorities don't think it's a good guard, treat it as
7282 if it were unlisted: stop using it as a guard, and throw it off
7283 the guards list if it stays that way for a long time.
7284 - Allow directory authorities to be marked separately as authorities
7285 for the v1 directory protocol, the v2 directory protocol, and
7286 as hidden service directories, to make it easier to retire old
7287 authorities. V1 authorities should set "HSAuthoritativeDir 1"
7288 to continue being hidden service authorities too.
7289 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
7291 o Minor features, controller:
7292 - Fix CIRC controller events so that controllers can learn the
7293 identity digests of non-Named servers used in circuit paths.
7294 - Let controllers ask for more useful identifiers for servers. Instead
7295 of learning identity digests for un-Named servers and nicknames
7296 for Named servers, the new identifiers include digest, nickname,
7297 and indication of Named status. Off by default; see control-spec.txt
7298 for more information.
7299 - Add a "getinfo address" controller command so it can display Tor's
7300 best guess to the user.
7301 - New controller event to alert the controller when our server
7302 descriptor has changed.
7303 - Give more meaningful errors on controller authentication failure.
7305 o Minor features, other:
7306 - When asked to resolve a hostname, don't use non-exit servers unless
7307 requested to do so. This allows servers with broken DNS to be
7308 useful to the network.
7309 - Divide eventdns log messages into warn and info messages.
7310 - Reserve the nickname "Unnamed" for routers that can't pick
7311 a hostname: any router can call itself Unnamed; directory
7312 authorities will never allocate Unnamed to any particular router;
7313 clients won't believe that any router is the canonical Unnamed.
7314 - Only include function names in log messages for info/debug messages.
7315 For notice/warn/err, the content of the message should be clear on
7316 its own, and printing the function name only confuses users.
7317 - Avoid some false positives during reachability testing: don't try
7318 to test via a server that's on the same /24 as us.
7319 - If we fail to build a circuit to an intended enclave, and it's
7320 not mandatory that we use that enclave, stop wanting it.
7321 - When eventdns is enabled, allow multithreaded builds on NetBSD and
7322 OpenBSD. (We had previously disabled threads on these platforms
7323 because they didn't have working thread-safe resolver functions.)
7325 o Major bugfixes, anonymity/security:
7326 - If a client asked for a server by name, and there's a named server
7327 in our network-status but we don't have its descriptor yet, we
7328 could return an unnamed server instead.
7329 - Fix NetBSD bug that could allow someone to force uninitialized RAM
7330 to be sent to a server's DNS resolver. This only affects NetBSD
7331 and other platforms that do not bounds-check tolower().
7332 - Reject (most) attempts to use Tor circuits with length one. (If
7333 many people start using Tor as a one-hop proxy, exit nodes become
7334 a more attractive target for compromise.)
7335 - Just because your DirPort is open doesn't mean people should be
7336 able to remotely teach you about hidden service descriptors. Now
7337 only accept rendezvous posts if you've got HSAuthoritativeDir set.
7339 o Major bugfixes, other:
7340 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
7341 - When a client asks the server to resolve (not connect to)
7342 an address, and it has a cached answer, give them the cached answer.
7343 Previously, the server would give them no answer at all.
7344 - Allow really slow clients to not hang up five minutes into their
7345 directory downloads (suggested by Adam J. Richter).
7346 - We were building exactly the wrong circuits when we anticipated
7347 hidden service requirements, meaning Tor would have to build all
7348 its circuits on demand.
7349 - Avoid crashing when we mmap a router cache file of size 0.
7350 - When testing reachability of our DirPort, don't launch new
7351 tests when there's already one in progress -- unreachable
7352 servers were stacking up dozens of testing streams.
7354 o Minor bugfixes, correctness:
7355 - If we're a directory mirror and we ask for "all" network status
7356 documents, we would discard status documents from authorities
7358 - Avoid a memory corruption bug when creating a hash table for
7360 - Avoid controller-triggered crash when misusing certain commands
7361 from a v0 controller on platforms that do not handle
7362 printf("%s",NULL) gracefully.
7363 - Don't crash when a controller sends a third argument to an
7364 "extendcircuit" request.
7365 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
7366 response; fix error code when "getinfo dir/status/" fails.
7367 - Avoid crash when telling controller stream-status and a stream
7369 - Patch from Adam Langley to fix assert() in eventdns.c.
7370 - Fix a debug log message in eventdns to say "X resolved to Y"
7371 instead of "X resolved to X".
7372 - Make eventdns give strings for DNS errors, not just error numbers.
7373 - Track unreachable entry guards correctly: don't conflate
7374 'unreachable by us right now' with 'listed as down by the directory
7375 authorities'. With the old code, if a guard was unreachable by
7376 us but listed as running, it would clog our guard list forever.
7377 - Behave correctly in case we ever have a network with more than
7378 2GB/s total advertised capacity.
7379 - Make TrackExitHosts case-insensitive, and fix the behavior of
7380 ".suffix" TrackExitHosts items to avoid matching in the middle of
7382 - Finally fix the openssl warnings from newer gccs that believe that
7383 ignoring a return value is okay, but casting a return value and
7384 then ignoring it is a sign of madness.
7385 - Prevent the contrib/exitlist script from printing the same
7386 result more than once.
7387 - Patch from Steve Hildrey: Generate network status correctly on
7388 non-versioning dirservers.
7389 - Don't listen to the X-Your-Address-Is hint if you did the lookup
7390 via Tor; otherwise you'll think you're the exit node's IP address.
7392 o Minor bugfixes, performance:
7393 - Two small performance improvements on parsing descriptors.
7394 - Major performance improvement on inserting descriptors: change
7395 algorithm from O(n^2) to O(n).
7396 - Make the common memory allocation path faster on machines where
7397 malloc(0) returns a pointer.
7398 - Start remembering X-Your-Address-Is directory hints even if you're
7399 a client, so you can become a server more smoothly.
7400 - Avoid duplicate entries on MyFamily line in server descriptor.
7402 o Packaging, features:
7403 - Remove architecture from OS X builds. The official builds are
7404 now universal binaries.
7405 - The Debian package now uses --verify-config when (re)starting,
7406 to distinguish configuration errors from other errors.
7407 - Update RPMs to require libevent 1.1b.
7409 o Packaging, bugfixes:
7410 - Patches so Tor builds with MinGW on Windows.
7411 - Patches so Tor might run on Cygwin again.
7412 - Resume building on non-gcc compilers and ancient gcc. Resume
7413 building with the -O0 compile flag. Resume building cleanly on
7415 - Run correctly on OS X platforms with case-sensitive filesystems.
7416 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
7417 - Add autoconf checks so Tor can build on Solaris x86 again.
7420 - Documented (and renamed) ServerDNSSearchDomains and
7421 ServerDNSResolvConfFile options.
7422 - Be clearer that the *ListenAddress directives can be repeated
7426 Changes in version 0.1.1.24 - 2006-09-29
7428 - Allow really slow clients to not hang up five minutes into their
7429 directory downloads (suggested by Adam J. Richter).
7430 - Fix major performance regression from 0.1.0.x: instead of checking
7431 whether we have enough directory information every time we want to
7432 do something, only check when the directory information has changed.
7433 This should improve client CPU usage by 25-50%.
7434 - Don't crash if, after a server has been running for a while,
7435 it can't resolve its hostname.
7438 - Allow Tor to start when RunAsDaemon is set but no logs are set.
7439 - Don't crash when the controller receives a third argument to an
7440 "extendcircuit" request.
7441 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
7442 response; fix error code when "getinfo dir/status/" fails.
7443 - Fix configure.in to not produce broken configure files with
7444 more recent versions of autoconf. Thanks to Clint for his auto*
7446 - Fix security bug on NetBSD that could allow someone to force
7447 uninitialized RAM to be sent to a server's DNS resolver. This
7448 only affects NetBSD and other platforms that do not bounds-check
7450 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
7451 methods: these are known to be buggy.
7452 - If we're a directory mirror and we ask for "all" network status
7453 documents, we would discard status documents from authorities
7457 Changes in version 0.1.2.1-alpha - 2006-08-27
7459 - Add "eventdns" async dns library from Adam Langley, tweaked to
7460 build on OSX and Windows. Only enabled if you pass the
7461 --enable-eventdns argument to configure.
7462 - Allow servers with no hostname or IP address to learn their
7463 IP address by asking the directory authorities. This code only
7464 kicks in when you would normally have exited with a "no address"
7465 error. Nothing's authenticated, so use with care.
7466 - Rather than waiting a fixed amount of time between retrying
7467 application connections, we wait only 5 seconds for the first,
7468 10 seconds for the second, and 15 seconds for each retry after
7469 that. Hopefully this will improve the expected user experience.
7470 - Patch from Tup to add support for transparent AP connections:
7471 this basically bundles the functionality of trans-proxy-tor
7472 into the Tor mainline. Now hosts with compliant pf/netfilter
7473 implementations can redirect TCP connections straight to Tor
7474 without diverting through SOCKS. Needs docs.
7475 - Busy directory servers save lots of memory by spooling server
7476 descriptors, v1 directories, and v2 networkstatus docs to buffers
7477 as needed rather than en masse. Also mmap the cached-routers
7478 files, so we don't need to keep the whole thing in memory too.
7479 - Automatically avoid picking more than one node from the same
7480 /16 network when constructing a circuit.
7481 - Revise and clean up the torrc.sample that we ship with; add
7482 a section for BandwidthRate and BandwidthBurst.
7485 - Split circuit_t into origin_circuit_t and or_circuit_t, and
7486 split connection_t into edge, or, dir, control, and base structs.
7487 These will save quite a bit of memory on busy servers, and they'll
7488 also help us track down bugs in the code and bugs in the spec.
7489 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
7490 or later. Log when we are doing this, so we can diagnose it when
7491 it fails. (Also, recommend libevent 1.1b for kqueue and
7492 win32 methods; deprecate libevent 1.0b harder; make libevent
7493 recommendation system saner.)
7494 - Start being able to build universal binaries on OS X (thanks
7496 - Export the default exit policy via the control port, so controllers
7497 don't need to guess what it is / will be later.
7498 - Add a man page entry for ProtocolWarnings.
7499 - Add TestVia config option to the man page.
7500 - Remove even more protocol-related warnings from Tor server logs,
7501 such as bad TLS handshakes and malformed begin cells.
7502 - Stop fetching descriptors if you're not a dir mirror and you
7503 haven't tried to establish any circuits lately. [This currently
7504 causes some dangerous behavior, because when you start up again
7505 you'll use your ancient server descriptors.]
7506 - New DirPort behavior: if you have your dirport set, you download
7507 descriptors aggressively like a directory mirror, whether or not
7509 - Get rid of the router_retry_connections notion. Now routers
7510 no longer try to rebuild long-term connections to directory
7511 authorities, and directory authorities no longer try to rebuild
7512 long-term connections to all servers. We still don't hang up
7513 connections in these two cases though -- we need to look at it
7514 more carefully to avoid flapping, and we likely need to wait til
7515 0.1.1.x is obsolete.
7516 - Drop compatibility with obsolete Tors that permit create cells
7517 to have the wrong circ_id_type.
7518 - Re-enable per-connection rate limiting. Get rid of the "OP
7519 bandwidth" concept. Lay groundwork for "bandwidth classes" --
7520 separate global buckets that apply depending on what sort of conn
7522 - Start publishing one minute or so after we find our ORPort
7523 to be reachable. This will help reduce the number of descriptors
7524 we have for ourselves floating around, since it's quite likely
7525 other things (e.g. DirPort) will change during that minute too.
7526 - Fork the v1 directory protocol into its own spec document,
7527 and mark dir-spec.txt as the currently correct (v2) spec.
7530 - When we find our DirPort to be reachable, publish a new descriptor
7531 so we'll tell the world (reported by pnx).
7532 - Publish a new descriptor after we hup/reload. This is important
7533 if our config has changed such that we'll want to start advertising
7534 our DirPort now, etc.
7535 - Allow Tor to start when RunAsDaemon is set but no logs are set.
7536 - When we have a state file we cannot parse, tell the user and
7537 move it aside. Now we avoid situations where the user starts
7538 Tor in 1904, Tor writes a state file with that timestamp in it,
7539 the user fixes her clock, and Tor refuses to start.
7540 - Fix configure.in to not produce broken configure files with
7541 more recent versions of autoconf. Thanks to Clint for his auto*
7543 - "tor --verify-config" now exits with -1(255) or 0 depending on
7544 whether the config options are bad or good.
7545 - Resolve bug 321 when using dnsworkers: append a period to every
7546 address we resolve at the exit node, so that we do not accidentally
7547 pick up local addresses, and so that failing searches are retried
7548 in the resolver search domains. (This is already solved for
7549 eventdns.) (This breaks Blossom servers for now.)
7550 - If we are using an exit enclave and we can't connect, e.g. because
7551 its webserver is misconfigured to not listen on localhost, then
7552 back off and try connecting from somewhere else before we fail.
7555 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
7556 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
7557 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
7558 when the IP address is mapped through MapAddress to a hostname.
7559 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
7560 useless IPv6 DNS resolves.
7561 - Patch suggested by Karsten Loesing: respond to SIGNAL command
7562 before we execute the signal, in case the signal shuts us down.
7563 - Clean up AllowInvalidNodes man page entry.
7564 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
7565 - Add more asserts to track down an assert error on a windows Tor
7566 server with connection_add being called with socket == -1.
7567 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
7568 - Fix misleading log messages: an entry guard that is "unlisted",
7569 as well as not known to be "down" (because we've never heard
7570 of it), is not therefore "up".
7571 - Remove code to special-case "-cvs" ending, since it has not
7572 actually mattered since 0.0.9.
7573 - Make our socks5 handling more robust to broken socks clients:
7574 throw out everything waiting on the buffer in between socks
7575 handshake phases, since they can't possibly (so the theory
7576 goes) have predicted what we plan to respond to them.
7579 Changes in version 0.1.1.23 - 2006-07-30
7581 - Fast Tor servers, especially exit nodes, were triggering asserts
7582 due to a bug in handling the list of pending DNS resolves. Some
7583 bugs still remain here; we're hunting them.
7584 - Entry guards could crash clients by sending unexpected input.
7585 - More fixes on reachability testing: if you find yourself reachable,
7586 then don't ever make any client requests (so you stop predicting
7587 circuits), then hup or have your clock jump, then later your IP
7588 changes, you won't think circuits are working, so you won't try to
7589 test reachability, so you won't publish.
7592 - Avoid a crash if the controller does a resetconf firewallports
7593 and then a setconf fascistfirewall=1.
7594 - Avoid an integer underflow when the dir authority decides whether
7595 a router is stable: we might wrongly label it stable, and compute
7596 a slightly wrong median stability, when a descriptor is published
7598 - Fix a place where we might trigger an assert if we can't build our
7599 own server descriptor yet.
7602 Changes in version 0.1.1.22 - 2006-07-05
7604 - Fix a big bug that was causing servers to not find themselves
7605 reachable if they changed IP addresses. Since only 0.1.1.22+
7606 servers can do reachability testing correctly, now we automatically
7607 make sure to test via one of these.
7608 - Fix to allow clients and mirrors to learn directory info from
7609 descriptor downloads that get cut off partway through.
7610 - Directory authorities had a bug in deciding if a newly published
7611 descriptor was novel enough to make everybody want a copy -- a few
7612 servers seem to be publishing new descriptors many times a minute.
7614 - Fix a rare bug that was causing some servers to complain about
7615 "closing wedged cpuworkers" and skip some circuit create requests.
7616 - Make the Exit flag in directory status documents actually work.
7619 Changes in version 0.1.1.21 - 2006-06-10
7620 o Crash and assert fixes from 0.1.1.20:
7621 - Fix a rare crash on Tor servers that have enabled hibernation.
7622 - Fix a seg fault on startup for Tor networks that use only one
7623 directory authority.
7624 - Fix an assert from a race condition that occurs on Tor servers
7625 while exiting, where various threads are trying to log that they're
7626 exiting, and delete the logs, at the same time.
7627 - Make our unit tests pass again on certain obscure platforms.
7630 - Add support for building SUSE RPM packages.
7631 - Speed up initial bootstrapping for clients: if we are making our
7632 first ever connection to any entry guard, then don't mark it down
7634 - When only one Tor server in the network is labelled as a guard,
7635 and we've already picked him, we would cycle endlessly picking him
7636 again, being unhappy about it, etc. Now we specifically exclude
7637 current guards when picking a new guard.
7638 - Servers send create cells more reliably after the TLS connection
7639 is established: we were sometimes forgetting to send half of them
7640 when we had more than one pending.
7641 - If we get a create cell that asks us to extend somewhere, but the
7642 Tor server there doesn't match the expected digest, we now send
7643 a destroy cell back, rather than silently doing nothing.
7644 - Make options->RedirectExit work again.
7645 - Make cookie authentication for the controller work again.
7646 - Stop being picky about unusual characters in the arguments to
7647 mapaddress. It's none of our business.
7648 - Add a new config option "TestVia" that lets you specify preferred
7649 middle hops to use for test circuits. Perhaps this will let me
7650 debug the reachability problems better.
7652 o Log / documentation fixes:
7653 - If we're a server and some peer has a broken TLS certificate, don't
7654 log about it unless ProtocolWarnings is set, i.e., we want to hear
7655 about protocol violations by others.
7656 - Fix spelling of VirtualAddrNetwork in man page.
7657 - Add a better explanation at the top of the autogenerated torrc file
7658 about what happened to our old torrc.
7661 Changes in version 0.1.1.20 - 2006-05-23
7663 - Downgrade a log severity where servers complain that they're
7665 - Avoid a compile warning on FreeBSD.
7666 - Remove string size limit on NEWDESC messages; solve bug 291.
7667 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
7668 more thoroughly when we're running on windows.
7671 Changes in version 0.1.1.19-rc - 2006-05-03
7673 - Regenerate our local descriptor if it's dirty and we try to use
7674 it locally (e.g. if it changes during reachability detection).
7675 - If we setconf our ORPort to 0, we continued to listen on the
7676 old ORPort and receive connections.
7677 - Avoid a second warning about machine/limits.h on Debian
7679 - Be willing to add our own routerinfo into the routerlist.
7680 Now authorities will include themselves in their directories
7681 and network-statuses.
7682 - Stop trying to upload rendezvous descriptors to every
7683 directory authority: only try the v1 authorities.
7684 - Servers no longer complain when they think they're not
7685 registered with the directory authorities. There were too many
7687 - Backport dist-rpm changes so rpms can be built without errors.
7690 - Implement an option, VirtualAddrMask, to set which addresses
7691 get handed out in response to mapaddress requests. This works
7692 around a bug in tsocks where 127.0.0.0/8 is never socksified.
7695 Changes in version 0.1.1.18-rc - 2006-04-10
7697 - Work harder to download live network-statuses from all the
7698 directory authorities we know about. Improve the threshold
7699 decision logic so we're more robust to edge cases.
7700 - When fetching rendezvous descriptors, we were willing to ask
7701 v2 authorities too, which would always return 404.
7704 - Stop listing down or invalid nodes in the v1 directory. This will
7705 reduce its bulk by about 1/3, and reduce load on directory
7707 - When deciding whether a router is Fast or Guard-worthy, consider
7708 his advertised BandwidthRate and not just the BandwidthCapacity.
7709 - No longer ship INSTALL and README files -- they are useless now.
7710 - Force rpmbuild to behave and honor target_cpu.
7711 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
7712 - Start to include translated versions of the tor-doc-*.html
7713 files, along with the screenshots. Still needs more work.
7714 - Start sending back 512 and 451 errors if mapaddress fails,
7715 rather than not sending anything back at all.
7716 - When we fail to bind or listen on an incoming or outgoing
7717 socket, we should close it before failing. otherwise we just
7718 leak it. (thanks to weasel for finding.)
7719 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
7720 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
7721 - Make NoPublish (even though deprecated) work again.
7722 - Fix a minor security flaw where a versioning auth dirserver
7723 could list a recommended version many times in a row to make
7724 clients more convinced that it's recommended.
7725 - Fix crash bug if there are two unregistered servers running
7726 with the same nickname, one of them is down, and you ask for
7727 them by nickname in your EntryNodes or ExitNodes. Also, try
7728 to pick the one that's running rather than an arbitrary one.
7729 - Fix an infinite loop we could hit if we go offline for too long.
7730 - Complain when we hit WSAENOBUFS on recv() or write() too.
7731 Perhaps this will help us hunt the bug.
7732 - If you're not a versioning dirserver, don't put the string
7733 "client-versions \nserver-versions \n" in your network-status.
7734 - Lower the minimum required number of file descriptors to 1000,
7735 so we can have some overhead for Valgrind on Linux, where the
7736 default ulimit -n is 1024.
7739 - Add tor.dizum.com as the fifth authoritative directory server.
7740 - Add a new config option FetchUselessDescriptors, off by default,
7741 for when you plan to run "exitlist" on your client and you want
7742 to know about even the non-running descriptors.
7745 Changes in version 0.1.1.17-rc - 2006-03-28
7747 - Clients and servers since 0.1.1.10-alpha have been expiring
7748 connections whenever they are idle for 5 minutes and they *do*
7749 have circuits on them. Oops. With this new version, clients will
7750 discard their previous entry guard choices and avoid choosing
7751 entry guards running these flawed versions.
7752 - Fix memory leak when uncompressing concatenated zlib streams. This
7753 was causing substantial leaks over time on Tor servers.
7754 - The v1 directory was including servers as much as 48 hours old,
7755 because that's how the new routerlist->routers works. Now only
7756 include them if they're 20 hours old or less.
7759 - Resume building on irix64, netbsd 2.0, etc.
7760 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
7762 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
7763 and it is confusing some users.
7764 - Mirrors stop caching the v1 directory so often.
7765 - Make the max number of old descriptors that a cache will hold
7766 rise with the number of directory authorities, so we can scale.
7767 - Change our win32 uname() hack to be more forgiving about what
7768 win32 versions it thinks it's found.
7771 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
7773 - When the controller's *setconf commands fail, collect an error
7774 message in a string and hand it back to the controller.
7775 - Make the v2 dir's "Fast" flag based on relative capacity, just
7776 like "Stable" is based on median uptime. Name everything in the
7777 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
7778 - Log server fingerprint on startup, so new server operators don't
7779 have to go hunting around their filesystem for it.
7780 - Return a robots.txt on our dirport to discourage google indexing.
7781 - Let the controller ask for GETINFO dir/status/foo so it can ask
7782 directly rather than connecting to the dir port. Only works when
7783 dirport is set for now.
7785 o New config options rather than constants in the code:
7786 - SocksTimeout: How long do we let a socks connection wait
7787 unattached before we fail it?
7788 - CircuitBuildTimeout: Cull non-open circuits that were born
7789 at least this many seconds ago.
7790 - CircuitIdleTimeout: Cull open clean circuits that were born
7791 at least this many seconds ago.
7794 Changes in version 0.1.1.16-rc - 2006-03-18
7795 o Bugfixes on 0.1.1.15-rc:
7796 - Fix assert when the controller asks to attachstream a connect-wait
7797 or resolve-wait stream.
7798 - Now do address rewriting when the controller asks us to attach
7799 to a particular circuit too. This will let Blossom specify
7800 "moria2.exit" without having to learn what moria2's IP address is.
7801 - Make the "tor --verify-config" command-line work again, so people
7802 can automatically check if their torrc will parse.
7803 - Authoritative dirservers no longer require an open connection from
7804 a server to consider him "reachable". We need this change because
7805 when we add new auth dirservers, old servers won't know not to
7807 - Let Tor build on Sun CC again.
7808 - Fix an off-by-one buffer size in dirserv.c that magically never
7809 hit our three authorities but broke sjmurdoch's own tor network.
7810 - If we as a directory mirror don't know of any v1 directory
7811 authorities, then don't try to cache any v1 directories.
7812 - Stop warning about unknown servers in our family when they are
7813 given as hex digests.
7814 - Stop complaining as quickly to the server operator that he
7815 hasn't registered his nickname/key binding.
7816 - Various cleanups so we can add new V2 Auth Dirservers.
7817 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
7818 reflect the updated flags in our v2 dir protocol.
7819 - Resume allowing non-printable characters for exit streams (both
7820 for connecting and for resolving). Now we tolerate applications
7821 that don't follow the RFCs. But continue to block malformed names
7824 o Bugfixes on 0.1.0.x:
7825 - Fix assert bug in close_logs(): when we close and delete logs,
7826 remove them all from the global "logfiles" list.
7827 - Fix minor integer overflow in calculating when we expect to use up
7828 our bandwidth allocation before hibernating.
7829 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
7830 there are multiple SSLs installed with different versions.
7831 - When we try to be a server and Address is not explicitly set and
7832 our hostname resolves to a private IP address, try to use an
7833 interface address if it has a public address. Now Windows machines
7834 that think of themselves as localhost can work by default.
7837 - Let the controller ask for GETINFO dir/server/foo so it can ask
7838 directly rather than connecting to the dir port.
7839 - Let the controller tell us about certain router descriptors
7840 that it doesn't want Tor to use in circuits. Implement
7841 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
7842 - New config option SafeSocks to reject all application connections
7843 using unsafe socks protocols. Defaults to off.
7846 Changes in version 0.1.1.15-rc - 2006-03-11
7847 o Bugfixes and cleanups:
7848 - When we're printing strings from the network, don't try to print
7849 non-printable characters. This protects us against shell escape
7850 sequence exploits, and also against attacks to fool humans into
7851 misreading their logs.
7852 - Fix a bug where Tor would fail to establish any connections if you
7853 left it off for 24 hours and then started it: we were happy with
7854 the obsolete network statuses, but they all referred to router
7855 descriptors that were too old to fetch, so we ended up with no
7856 valid router descriptors.
7857 - Fix a seg fault in the controller's "getinfo orconn-status"
7858 command while listing status on incoming handshaking connections.
7859 Introduce a status name "NEW" for these connections.
7860 - If we get a linelist or linelist_s config option from the torrc
7861 (e.g. ExitPolicy) and it has no value, warn and skip rather than
7862 silently resetting it to its default.
7863 - Don't abandon entry guards until they've been down or gone for
7865 - Cleaner and quieter log messages.
7868 - New controller signal NEWNYM that makes new application requests
7870 - Add a new circuit purpose 'controller' to let the controller ask
7871 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
7872 controller command to let you specify the purpose if you're
7873 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
7874 command to let you change a circuit's purpose after it's been
7876 - Accept "private:*" in routerdesc exit policies; not generated yet
7877 because older Tors do not understand it.
7878 - Add BSD-style contributed startup script "rc.subr" from Peter
7882 Changes in version 0.1.1.14-alpha - 2006-02-20
7883 o Bugfixes on 0.1.1.x:
7884 - Don't die if we ask for a stdout or stderr log (even implicitly)
7885 and we're set to RunAsDaemon -- just warn.
7886 - We still had a few bugs in the OR connection rotation code that
7887 caused directory servers to slowly aggregate connections to other
7888 fast Tor servers. This time for sure!
7889 - Make log entries on Win32 include the name of the function again.
7890 - We were treating a pair of exit policies if they were equal even
7891 if one said accept and the other said reject -- causing us to
7892 not always publish a new descriptor since we thought nothing
7894 - Retry pending server downloads as well as pending networkstatus
7895 downloads when we unexpectedly get a socks request.
7896 - We were ignoring the IS_FAST flag in the directory status,
7897 meaning we were willing to pick trivial-bandwidth nodes for "fast"
7899 - If the controller's SAVECONF command fails (e.g. due to file
7900 permissions), let the controller know that it failed.
7903 - If we're trying to be a Tor server and running Windows 95/98/ME
7904 as a server, explain that we'll likely crash.
7905 - When we're a server, a client asks for an old-style directory,
7906 and our write bucket is empty, don't give it to him. This way
7907 small servers can continue to serve the directory *sometimes*,
7908 without getting overloaded.
7909 - Compress exit policies even more -- look for duplicate lines
7911 - Clients now honor the "guard" flag in the router status when
7912 picking entry guards, rather than looking at is_fast or is_stable.
7913 - Retain unrecognized lines in $DATADIR/state file, so that we can
7914 be forward-compatible.
7915 - Generate 18.0.0.0/8 address policy format in descs when we can;
7916 warn when the mask is not reducible to a bit-prefix.
7917 - Let the user set ControlListenAddress in the torrc. This can be
7918 dangerous, but there are some cases (like a secured LAN) where it
7920 - Split ReachableAddresses into ReachableDirAddresses and
7921 ReachableORAddresses, so we can restrict Dir conns to port 80
7922 and OR conns to port 443.
7923 - Now we can target arch and OS in rpm builds (contributed by
7924 Phobos). Also make the resulting dist-rpm filename match the
7926 - New config options to help controllers: FetchServerDescriptors
7927 and FetchHidServDescriptors for whether to fetch server
7928 info and hidserv info or let the controller do it, and
7929 PublishServerDescriptor and PublishHidServDescriptors.
7930 - Also let the controller set the __AllDirActionsPrivate config
7931 option if you want all directory fetches/publishes to happen via
7932 Tor (it assumes your controller bootstraps your circuits).
7935 Changes in version 0.1.0.17 - 2006-02-17
7936 o Crash bugfixes on 0.1.0.x:
7937 - When servers with a non-zero DirPort came out of hibernation,
7938 sometimes they would trigger an assert.
7940 o Other important bugfixes:
7941 - On platforms that don't have getrlimit (like Windows), we were
7942 artificially constraining ourselves to a max of 1024
7943 connections. Now just assume that we can handle as many as 15000
7944 connections. Hopefully this won't cause other problems.
7946 o Backported features:
7947 - When we're a server, a client asks for an old-style directory,
7948 and our write bucket is empty, don't give it to him. This way
7949 small servers can continue to serve the directory *sometimes*,
7950 without getting overloaded.
7951 - Whenever you get a 503 in response to a directory fetch, try
7952 once more. This will become important once servers start sending
7953 503's whenever they feel busy.
7954 - Fetch a new directory every 120 minutes, not every 40 minutes.
7955 Now that we have hundreds of thousands of users running the old
7956 directory algorithm, it's starting to hurt a lot.
7957 - Bump up the period for forcing a hidden service descriptor upload
7958 from 20 minutes to 1 hour.
7961 Changes in version 0.1.1.13-alpha - 2006-02-09
7962 o Crashes in 0.1.1.x:
7963 - When you tried to setconf ORPort via the controller, Tor would
7964 crash. So people using TorCP to become a server were sad.
7965 - Solve (I hope) the stack-smashing bug that we were seeing on fast
7966 servers. The problem appears to be something do with OpenSSL's
7967 random number generation, or how we call it, or something. Let me
7968 know if the crashes continue.
7969 - Turn crypto hardware acceleration off by default, until we find
7970 somebody smart who can test it for us. (It appears to produce
7971 seg faults in at least some cases.)
7972 - Fix a rare assert error when we've tried all intro points for
7973 a hidden service and we try fetching the service descriptor again:
7974 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
7977 - Fix a major load balance bug: we were round-robining in 16 KB
7978 chunks, and servers with bandwidthrate of 20 KB, while downloading
7979 a 600 KB directory, would starve their other connections. Now we
7980 try to be a bit more fair.
7981 - Dir authorities and mirrors were never expiring the newest
7982 descriptor for each server, causing memory and directory bloat.
7983 - Fix memory-bloating and connection-bloating bug on servers: We
7984 were never closing any connection that had ever had a circuit on
7985 it, because we were checking conn->n_circuits == 0, yet we had a
7986 bug that let it go negative.
7987 - Make Tor work using squid as your http proxy again -- squid
7988 returns an error if you ask for a URL that's too long, and it uses
7989 a really generic error message. Plus, many people are behind a
7990 transparent squid so they don't even realize it.
7991 - On platforms that don't have getrlimit (like Windows), we were
7992 artificially constraining ourselves to a max of 1024
7993 connections. Now just assume that we can handle as many as 15000
7994 connections. Hopefully this won't cause other problems.
7995 - Add a new config option ExitPolicyRejectPrivate which defaults to
7996 1. This means all exit policies will begin with rejecting private
7997 addresses, unless the server operator explicitly turns it off.
8000 - Clients no longer download descriptors for non-running
8002 - Before we add new directory authorities, we should make it
8003 clear that only v1 authorities should receive/publish hidden
8004 service descriptors.
8007 - As soon as we've fetched some more directory info, immediately
8008 try to download more server descriptors. This way we don't have
8009 a 10 second pause during initial bootstrapping.
8010 - Remove even more loud log messages that the server operator can't
8012 - When we're running an obsolete or un-recommended version, make
8013 the log message more clear about what the problem is and what
8014 versions *are* still recommended.
8015 - Provide a more useful warn message when our onion queue gets full:
8016 the CPU is too slow or the exit policy is too liberal.
8017 - Don't warn when we receive a 503 from a dirserver/cache -- this
8018 will pave the way for them being able to refuse if they're busy.
8019 - When we fail to bind a listener, try to provide a more useful
8020 log message: e.g., "Is Tor already running?"
8021 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
8022 Goldberg can prove things about our handshake protocol more
8024 - MaxConn has been obsolete for a while now. Document the ConnLimit
8025 config option, which is a *minimum* number of file descriptors
8026 that must be available else Tor refuses to start.
8027 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
8028 if you log to syslog and want something other than LOG_DAEMON.
8029 - Make dirservers generate a separate "guard" flag to mean,
8030 "would make a good entry guard". Make clients parse it and vote
8031 on it. Not used by clients yet.
8032 - Implement --with-libevent-dir option to ./configure. Also, improve
8033 search techniques to find libevent, and use those for openssl too.
8034 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
8035 - Only start testing reachability once we've established a
8036 circuit. This will make startup on dirservers less noisy.
8037 - Don't try to upload hidden service descriptors until we have
8038 established a circuit.
8039 - Fix the controller's "attachstream 0" command to treat conn like
8040 it just connected, doing address remapping, handling .exit and
8041 .onion idioms, and so on. Now we're more uniform in making sure
8042 that the controller hears about new and closing connections.
8045 Changes in version 0.1.1.12-alpha - 2006-01-11
8046 o Bugfixes on 0.1.1.x:
8047 - The fix to close duplicate server connections was closing all
8048 Tor client connections if they didn't establish a circuit
8049 quickly enough. Oops.
8050 - Fix minor memory issue (double-free) that happened on exit.
8052 o Bugfixes on 0.1.0.x:
8053 - Tor didn't warn when it failed to open a log file.
8056 Changes in version 0.1.1.11-alpha - 2006-01-10
8057 o Crashes in 0.1.1.x:
8058 - Include all the assert/crash fixes from 0.1.0.16.
8059 - If you start Tor and then quit very quickly, there were some
8060 races that tried to free things that weren't allocated yet.
8061 - Fix a rare memory stomp if you're running hidden services.
8062 - Fix segfault when specifying DirServer in config without nickname.
8063 - Fix a seg fault when you finish connecting to a server but at
8064 that moment you dump his server descriptor.
8065 - Extendcircuit and Attachstream controller commands would
8066 assert/crash if you don't give them enough arguments.
8067 - Fix an assert error when we're out of space in the connection_list
8068 and we try to post a hidden service descriptor (reported by weasel).
8069 - If you specify a relative torrc path and you set RunAsDaemon in
8070 your torrc, then it chdir()'s to the new directory. If you HUP,
8071 it tries to load the new torrc location, fails, and exits.
8072 The fix: no longer allow a relative path to torrc using -f.
8075 - Implement "entry guards": automatically choose a handful of entry
8076 nodes and stick with them for all circuits. Only pick new guards
8077 when the ones you have are unsuitable, and if the old guards
8078 become suitable again, switch back. This will increase security
8079 dramatically against certain end-point attacks. The EntryNodes
8080 config option now provides some hints about which entry guards you
8081 want to use most; and StrictEntryNodes means to only use those.
8082 - New directory logic: download by descriptor digest, not by
8083 fingerprint. Caches try to download all listed digests from
8084 authorities; clients try to download "best" digests from caches.
8085 This avoids partitioning and isolating attacks better.
8086 - Make the "stable" router flag in network-status be the median of
8087 the uptimes of running valid servers, and make clients pay
8088 attention to the network-status flags. Thus the cutoff adapts
8089 to the stability of the network as a whole, making IRC, IM, etc
8090 connections more reliable.
8093 - Tor servers with dynamic IP addresses were needing to wait 18
8094 hours before they could start doing reachability testing using
8095 the new IP address and ports. This is because they were using
8096 the internal descriptor to learn what to test, yet they were only
8097 rebuilding the descriptor once they decided they were reachable.
8098 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
8099 to download certain server descriptors, throw them away, and then
8100 fetch them again after 30 minutes. Now mirrors throw away these
8101 server descriptors so clients can't get them.
8102 - We were leaving duplicate connections to other ORs open for a week,
8103 rather than closing them once we detect a duplicate. This only
8104 really affected authdirservers, but it affected them a lot.
8105 - Spread the authdirservers' reachability testing over the entire
8106 testing interval, so we don't try to do 500 TLS's at once every
8110 - If the network is down, and we try to connect to a conn because
8111 we have a circuit in mind, and we timeout (30 seconds) because the
8112 network never answers, we were expiring the circuit, but we weren't
8113 obsoleting the connection or telling the entry_guards functions.
8114 - Some Tor servers process billions of cells per day. These statistics
8115 need to be uint64_t's.
8116 - Check for integer overflows in more places, when adding elements
8117 to smartlists. This could possibly prevent a buffer overflow
8118 on malicious huge inputs. I don't see any, but I haven't looked
8120 - ReachableAddresses kept growing new "reject *:*" lines on every
8122 - When you "setconf log" via the controller, it should remove all
8123 logs. We were automatically adding back in a "log notice stdout".
8124 - Newly bootstrapped Tor networks couldn't establish hidden service
8125 circuits until they had nodes with high uptime. Be more tolerant.
8126 - We were marking servers down when they could not answer every piece
8127 of the directory request we sent them. This was far too harsh.
8128 - Fix the torify (tsocks) config file to not use Tor for localhost
8130 - Directory authorities now go to the proper authority when asking for
8131 a networkstatus, even when they want a compressed one.
8132 - Fix a harmless bug that was causing Tor servers to log
8133 "Got an end because of misc error, but we're not an AP. Closing."
8134 - Authorities were treating their own descriptor changes as cosmetic,
8135 meaning the descriptor available in the network-status and the
8136 descriptor that clients downloaded were different.
8137 - The OS X installer was adding a symlink for tor_resolve but
8138 the binary was called tor-resolve (reported by Thomas Hardly).
8139 - Workaround a problem with some http proxies where they refuse GET
8140 requests that specify "Content-Length: 0" (reported by Adrian).
8141 - Fix wrong log message when you add a "HiddenServiceNodes" config
8142 line without any HiddenServiceDir line (reported by Chris Thomas).
8145 - Write the TorVersion into the state file so we have a prayer of
8146 keeping forward and backward compatibility.
8147 - Revive the FascistFirewall config option rather than eliminating it:
8148 now it's a synonym for ReachableAddresses *:80,*:443.
8149 - Clients choose directory servers from the network status lists,
8150 not from their internal list of router descriptors. Now they can
8151 go to caches directly rather than needing to go to authorities
8153 - Directory authorities ignore router descriptors that have only
8154 cosmetic differences: do this for 0.1.0.x servers now too.
8155 - Add a new flag to network-status indicating whether the server
8156 can answer v2 directory requests too.
8157 - Authdirs now stop whining so loudly about bad descriptors that
8158 they fetch from other dirservers. So when there's a log complaint,
8159 it's for sure from a freshly uploaded descriptor.
8160 - Reduce memory requirements in our structs by changing the order
8162 - There used to be two ways to specify your listening ports in a
8163 server descriptor: on the "router" line and with a separate "ports"
8164 line. Remove support for the "ports" line.
8165 - New config option "AuthDirRejectUnlisted" for auth dirservers as
8166 a panic button: if we get flooded with unusable servers we can
8167 revert to only listing servers in the approved-routers file.
8168 - Auth dir servers can now mark a fingerprint as "!reject" or
8169 "!invalid" in the approved-routers file (as its nickname), to
8170 refuse descriptors outright or include them but marked as invalid.
8171 - Servers store bandwidth history across restarts/crashes.
8172 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
8173 get a better idea of why their circuits failed. Not used yet.
8174 - Directory mirrors now cache up to 16 unrecognized network-status
8175 docs. Now we can add new authdirservers and they'll be cached too.
8176 - When picking a random directory, prefer non-authorities if any
8178 - New controller option "getinfo desc/all-recent" to fetch the
8179 latest server descriptor for every router that Tor knows about.
8182 Changes in version 0.1.0.16 - 2006-01-02
8183 o Crash bugfixes on 0.1.0.x:
8184 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8185 corrupting the heap, losing FDs, or crashing when we need to resize
8186 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8187 - It turns out sparc64 platforms crash on unaligned memory access
8188 too -- so detect and avoid this.
8189 - Handle truncated compressed data correctly (by detecting it and
8191 - Fix possible-but-unlikely free(NULL) in control.c.
8192 - When we were closing connections, there was a rare case that
8193 stomped on memory, triggering seg faults and asserts.
8194 - Avoid potential infinite recursion when building a descriptor. (We
8195 don't know that it ever happened, but better to fix it anyway.)
8196 - We were neglecting to unlink marked circuits from soon-to-close OR
8197 connections, which caused some rare scribbling on freed memory.
8198 - Fix a memory stomping race bug when closing the joining point of two
8199 rendezvous circuits.
8200 - Fix an assert in time parsing found by Steven Murdoch.
8202 o Other bugfixes on 0.1.0.x:
8203 - When we're doing reachability testing, provide more useful log
8204 messages so the operator knows what to expect.
8205 - Do not check whether DirPort is reachable when we are suppressing
8206 advertising it because of hibernation.
8207 - When building with -static or on Solaris, we sometimes needed -ldl.
8208 - When we're deciding whether a stream has enough circuits around
8209 that can handle it, count the freshly dirty ones and not the ones
8210 that are so dirty they won't be able to handle it.
8211 - When we're expiring old circuits, we had a logic error that caused
8212 us to close new rendezvous circuits rather than old ones.
8213 - Give a more helpful log message when you try to change ORPort via
8214 the controller: you should upgrade Tor if you want that to work.
8215 - We were failing to parse Tor versions that start with "Tor ".
8216 - Tolerate faulty streams better: when a stream fails for reason
8217 exitpolicy, stop assuming that the router is lying about his exit
8218 policy. When a stream fails for reason misc, allow it to retry just
8219 as if it was resolvefailed. When a stream has failed three times,
8220 reset its failure count so we can try again and get all three tries.
8223 Changes in version 0.1.1.10-alpha - 2005-12-11
8224 o Correctness bugfixes on 0.1.0.x:
8225 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8226 corrupting the heap, losing FDs, or crashing when we need to resize
8227 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8228 - Stop doing the complex voodoo overkill checking for insecure
8229 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
8230 - When we were closing connections, there was a rare case that
8231 stomped on memory, triggering seg faults and asserts.
8232 - We were neglecting to unlink marked circuits from soon-to-close OR
8233 connections, which caused some rare scribbling on freed memory.
8234 - When we're deciding whether a stream has enough circuits around
8235 that can handle it, count the freshly dirty ones and not the ones
8236 that are so dirty they won't be able to handle it.
8237 - Recover better from TCP connections to Tor servers that are
8238 broken but don't tell you (it happens!); and rotate TLS
8239 connections once a week.
8240 - When we're expiring old circuits, we had a logic error that caused
8241 us to close new rendezvous circuits rather than old ones.
8242 - Fix a scary-looking but apparently harmless bug where circuits
8243 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
8244 servers, and never switch to state CIRCUIT_STATE_OPEN.
8245 - When building with -static or on Solaris, we sometimes needed to
8247 - Give a useful message when people run Tor as the wrong user,
8248 rather than telling them to start chowning random directories.
8249 - We were failing to inform the controller about new .onion streams.
8251 o Security bugfixes on 0.1.0.x:
8252 - Refuse server descriptors if the fingerprint line doesn't match
8253 the included identity key. Tor doesn't care, but other apps (and
8254 humans) might actually be trusting the fingerprint line.
8255 - We used to kill the circuit when we receive a relay command we
8256 don't recognize. Now we just drop it.
8257 - Start obeying our firewall options more rigorously:
8258 . If we can't get to a dirserver directly, try going via Tor.
8259 . Don't ever try to connect (as a client) to a place our
8260 firewall options forbid.
8261 . If we specify a proxy and also firewall options, obey the
8262 firewall options even when we're using the proxy: some proxies
8263 can only proxy to certain destinations.
8264 - Fix a bug found by Lasse Overlier: when we were making internal
8265 circuits (intended to be cannibalized later for rendezvous and
8266 introduction circuits), we were picking them so that they had
8267 useful exit nodes. There was no need for this, and it actually
8268 aids some statistical attacks.
8269 - Start treating internal circuits and exit circuits separately.
8270 It's important to keep them separate because internal circuits
8271 have their last hops picked like middle hops, rather than like
8272 exit hops. So exiting on them will break the user's expectations.
8274 o Bugfixes on 0.1.1.x:
8275 - Take out the mis-feature where we tried to detect IP address
8276 flapping for people with DynDNS, and chose not to upload a new
8277 server descriptor sometimes.
8278 - Try to be compatible with OpenSSL 0.9.6 again.
8279 - Log fix: when the controller is logging about .onion addresses,
8280 sometimes it didn't include the ".onion" part of the address.
8281 - Don't try to modify options->DirServers internally -- if the
8282 user didn't specify any, just add the default ones directly to
8283 the trusted dirserver list. This fixes a bug where people running
8284 controllers would use SETCONF on some totally unrelated config
8285 option, and Tor would start yelling at them about changing their
8287 - Let the controller's redirectstream command specify a port, in
8288 case the controller wants to change that too.
8289 - When we requested a pile of server descriptors, we sometimes
8290 accidentally launched a duplicate request for the first one.
8291 - Bugfix for trackhostexits: write down the fingerprint of the
8292 chosen exit, not its nickname, because the chosen exit might not
8294 - When parsing foo.exit, if foo is unknown, and we are leaving
8295 circuits unattached, set the chosen_exit field and leave the
8296 address empty. This matters because controllers got confused
8298 - Directory authorities no longer try to download server
8299 descriptors that they know they will reject.
8301 o Features and updates:
8302 - Replace balanced trees with hash tables: this should make stuff
8303 significantly faster.
8304 - Resume using the AES counter-mode implementation that we ship,
8305 rather than OpenSSL's. Ours is significantly faster.
8306 - Many other CPU and memory improvements.
8307 - Add a new config option FastFirstHopPK (on by default) so clients
8308 do a trivial crypto handshake for their first hop, since TLS has
8309 already taken care of confidentiality and authentication.
8310 - Add a new config option TestSocks so people can see if their
8311 applications are using socks4, socks4a, socks5-with-ip, or
8312 socks5-with-hostname. This way they don't have to keep mucking
8313 with tcpdump and wondering if something got cached somewhere.
8314 - Warn when listening on a public address for socks. I suspect a
8315 lot of people are setting themselves up as open socks proxies,
8316 and they have no idea that jerks on the Internet are using them,
8317 since they simply proxy the traffic into the Tor network.
8318 - Add "private:*" as an alias in configuration for policies. Now
8319 you can simplify your exit policy rather than needing to list
8320 every single internal or nonroutable network space.
8321 - Add a new controller event type that allows controllers to get
8322 all server descriptors that were uploaded to a router in its role
8323 as authoritative dirserver.
8324 - Start shipping socks-extensions.txt, tor-doc-unix.html,
8325 tor-doc-server.html, and stylesheet.css in the tarball.
8326 - Stop shipping tor-doc.html in the tarball.
8329 Changes in version 0.1.1.9-alpha - 2005-11-15
8330 o Usability improvements:
8331 - Start calling it FooListenAddress rather than FooBindAddress,
8332 since few of our users know what it means to bind an address
8334 - Reduce clutter in server logs. We're going to try to make
8335 them actually usable now. New config option ProtocolWarnings that
8336 lets you hear about how _other Tors_ are breaking the protocol. Off
8338 - Divide log messages into logging domains. Once we put some sort
8339 of interface on this, it will let people looking at more verbose
8340 log levels specify the topics they want to hear more about.
8341 - Make directory servers return better http 404 error messages
8342 instead of a generic "Servers unavailable".
8343 - Check for even more Windows version flags when writing the platform
8344 string in server descriptors, and note any we don't recognize.
8345 - Clean up more of the OpenSSL memory when exiting, so we can detect
8346 memory leaks better.
8347 - Make directory authorities be non-versioning, non-naming by
8348 default. Now we can add new directory servers without requiring
8349 their operators to pay close attention.
8350 - When logging via syslog, include the pid whenever we provide
8351 a log entry. Suggested by Todd Fries.
8353 o Performance improvements:
8354 - Directory servers now silently throw away new descriptors that
8355 haven't changed much if the timestamps are similar. We do this to
8356 tolerate older Tor servers that upload a new descriptor every 15
8357 minutes. (It seemed like a good idea at the time.)
8358 - Inline bottleneck smartlist functions; use fast versions by default.
8359 - Add a "Map from digest to void*" abstraction digestmap_t so we
8360 can do less hex encoding/decoding. Use it in router_get_by_digest()
8361 to resolve a performance bottleneck.
8362 - Allow tor_gzip_uncompress to extract as much as possible from
8363 truncated compressed data. Try to extract as many
8364 descriptors as possible from truncated http responses (when
8365 DIR_PURPOSE_FETCH_ROUTERDESC).
8366 - Make circ->onionskin a pointer, not a static array. moria2 was using
8367 125000 circuit_t's after it had been up for a few weeks, which
8368 translates to 20+ megs of wasted space.
8369 - The private half of our EDH handshake keys are now chosen out
8370 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
8372 o Security improvements:
8373 - Start making directory caches retain old routerinfos, so soon
8374 clients can start asking by digest of descriptor rather than by
8375 fingerprint of server.
8376 - Add half our entropy from RAND_poll in OpenSSL. This knows how
8377 to use egd (if present), openbsd weirdness (if present), vms/os2
8378 weirdness (if we ever port there), and more in the future.
8380 o Bugfixes on 0.1.0.x:
8381 - Do round-robin writes of at most 16 kB per write. This might be
8382 more fair on loaded Tor servers, and it might resolve our Windows
8383 crash bug. It might also slow things down.
8384 - Our TLS handshakes were generating a single public/private
8385 keypair for the TLS context, rather than making a new one for
8386 each new connections. Oops. (But we were still rotating them
8387 periodically, so it's not so bad.)
8388 - When we were cannibalizing a circuit with a particular exit
8389 node in mind, we weren't checking to see if that exit node was
8390 already present earlier in the circuit. Oops.
8391 - When a Tor server's IP changes (e.g. from a dyndns address),
8392 upload a new descriptor so clients will learn too.
8393 - Really busy servers were keeping enough circuits open on stable
8394 connections that they were wrapping around the circuit_id
8395 space. (It's only two bytes.) This exposed a bug where we would
8396 feel free to reuse a circuit_id even if it still exists but has
8397 been marked for close. Try to fix this bug. Some bug remains.
8398 - If we would close a stream early (e.g. it asks for a .exit that
8399 we know would refuse it) but the LeaveStreamsUnattached config
8400 option is set by the controller, then don't close it.
8402 o Bugfixes on 0.1.1.8-alpha:
8403 - Fix a big pile of memory leaks, some of them serious.
8404 - Do not try to download a routerdesc if we would immediately reject
8406 - Resume inserting a newline between all router descriptors when
8407 generating (old style) signed directories, since our spec says
8409 - When providing content-type application/octet-stream for
8410 server descriptors using .z, we were leaving out the
8411 content-encoding header. Oops. (Everything tolerated this just
8412 fine, but that doesn't mean we need to be part of the problem.)
8413 - Fix a potential seg fault in getconf and getinfo using version 1
8414 of the controller protocol.
8415 - Avoid crash: do not check whether DirPort is reachable when we
8416 are suppressing it because of hibernation.
8417 - Make --hash-password not crash on exit.
8420 Changes in version 0.1.1.8-alpha - 2005-10-07
8421 o New features (major):
8422 - Clients don't download or use the directory anymore. Now they
8423 download and use network-statuses from the trusted dirservers,
8424 and fetch individual server descriptors as needed from mirrors.
8425 See dir-spec.txt for all the gory details.
8426 - Be more conservative about whether to advertise our DirPort.
8427 The main change is to not advertise if we're running at capacity
8428 and either a) we could hibernate or b) our capacity is low and
8429 we're using a default DirPort.
8430 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
8432 o New features (minor):
8433 - Try to be smart about when to retry network-status and
8434 server-descriptor fetches. Still needs some tuning.
8435 - Stop parsing, storing, or using running-routers output (but
8436 mirrors still cache and serve it).
8437 - Consider a threshold of versioning dirservers (dirservers who have
8438 an opinion about which Tor versions are still recommended) before
8439 deciding whether to warn the user that he's obsolete.
8440 - Dirservers can now reject/invalidate by key and IP, with the
8441 config options "AuthDirInvalid" and "AuthDirReject". This is
8442 useful since currently we automatically list servers as running
8443 and usable even if we know they're jerks.
8444 - Provide dire warnings to any users who set DirServer; move it out
8445 of torrc.sample and into torrc.complete.
8446 - Add MyFamily to torrc.sample in the server section.
8447 - Add nicknames to the DirServer line, so we can refer to them
8448 without requiring all our users to memorize their IP addresses.
8449 - When we get an EOF or a timeout on a directory connection, note
8450 how many bytes of serverdesc we are dropping. This will help
8451 us determine whether it is smart to parse incomplete serverdesc
8453 - Add a new function to "change pseudonyms" -- that is, to stop
8454 using any currently-dirty circuits for new streams, so we don't
8455 link new actions to old actions. Currently it's only called on
8456 HUP (or SIGNAL RELOAD).
8457 - On sighup, if UseHelperNodes changed to 1, use new circuits.
8458 - Start using RAND_bytes rather than RAND_pseudo_bytes from
8459 OpenSSL. Also, reseed our entropy every hour, not just at
8460 startup. And entropy in 512-bit chunks, not 160-bit chunks.
8462 o Fixes on 0.1.1.7-alpha:
8463 - Nobody ever implemented EVENT_ADDRMAP for control protocol
8464 version 0, so don't let version 0 controllers ask for it.
8465 - If you requested something with too many newlines via the
8466 v1 controller protocol, you could crash tor.
8467 - Fix a number of memory leaks, including some pretty serious ones.
8468 - Re-enable DirPort testing again, so Tor servers will be willing
8469 to advertise their DirPort if it's reachable.
8470 - On TLS handshake, only check the other router's nickname against
8471 its expected nickname if is_named is set.
8473 o Fixes forward-ported from 0.1.0.15:
8474 - Don't crash when we don't have any spare file descriptors and we
8475 try to spawn a dns or cpu worker.
8476 - Make the numbers in read-history and write-history into uint64s,
8477 so they don't overflow and publish negatives in the descriptor.
8480 - For the OS X package's modified privoxy config file, comment
8481 out the "logfile" line so we don't log everything passed
8483 - We were whining about using socks4 or socks5-with-local-lookup
8484 even when it's an IP in the "virtual" range we designed exactly
8486 - We were leaking some memory every time the client changes IPs.
8487 - Never call free() on tor_malloc()d memory. This will help us
8488 use dmalloc to detect memory leaks.
8489 - Check for named servers when looking them up by nickname;
8490 warn when we'recalling a non-named server by its nickname;
8491 don't warn twice about the same name.
8492 - Try to list MyFamily elements by key, not by nickname, and warn
8493 if we've not heard of the server.
8494 - Make windows platform detection (uname equivalent) smarter.
8495 - It turns out sparc64 doesn't like unaligned access either.
8498 Changes in version 0.1.0.15 - 2005-09-23
8499 o Bugfixes on 0.1.0.x:
8500 - Reject ports 465 and 587 (spam targets) in default exit policy.
8501 - Don't crash when we don't have any spare file descriptors and we
8502 try to spawn a dns or cpu worker.
8503 - Get rid of IgnoreVersion undocumented config option, and make us
8504 only warn, never exit, when we're running an obsolete version.
8505 - Don't try to print a null string when your server finds itself to
8506 be unreachable and the Address config option is empty.
8507 - Make the numbers in read-history and write-history into uint64s,
8508 so they don't overflow and publish negatives in the descriptor.
8509 - Fix a minor memory leak in smartlist_string_remove().
8510 - We were only allowing ourselves to upload a server descriptor at
8511 most every 20 minutes, even if it changed earlier than that.
8512 - Clean up log entries that pointed to old URLs.
8515 Changes in version 0.1.1.7-alpha - 2005-09-14
8516 o Fixes on 0.1.1.6-alpha:
8517 - Exit servers were crashing when people asked them to make a
8518 connection to an address not in their exit policy.
8519 - Looking up a non-existent stream for a v1 control connection would
8521 - Fix a seg fault if we ask a dirserver for a descriptor by
8522 fingerprint but he doesn't know about him.
8523 - SETCONF was appending items to linelists, not clearing them.
8524 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
8525 out and refuse the setconf if it would fail.
8526 - Downgrade the dirserver log messages when whining about
8530 - Add Peter Palfrader's check-tor script to tor/contrib/
8531 It lets you easily check whether a given server (referenced by
8532 nickname) is reachable by you.
8533 - Numerous changes to move towards client-side v2 directories. Not
8537 - If the user gave tor an odd number of command-line arguments,
8538 we were silently ignoring the last one. Now we complain and fail.
8539 [This wins the oldest-bug prize -- this bug has been present since
8540 November 2002, as released in Tor 0.0.0.]
8541 - Do not use unaligned memory access on alpha, mips, or mipsel.
8542 It *works*, but is very slow, so we treat them as if it doesn't.
8543 - Retry directory requests if we fail to get an answer we like
8544 from a given dirserver (we were retrying before, but only if
8545 we fail to connect).
8546 - When writing the RecommendedVersions line, sort them first.
8547 - When the client asked for a rendezvous port that the hidden
8548 service didn't want to provide, we were sending an IP address
8549 back along with the end cell. Fortunately, it was zero. But stop
8551 - Correct "your server is reachable" log entries to indicate that
8552 it was self-testing that told us so.
8555 Changes in version 0.1.1.6-alpha - 2005-09-09
8556 o Fixes on 0.1.1.5-alpha:
8557 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
8558 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
8559 - Fix bug with tor_memmem finding a match at the end of the string.
8560 - Make unit tests run without segfaulting.
8561 - Resolve some solaris x86 compile warnings.
8562 - Handle duplicate lines in approved-routers files without warning.
8563 - Fix bug where as soon as a server refused any requests due to his
8564 exit policy (e.g. when we ask for localhost and he tells us that's
8565 127.0.0.1 and he won't do it), we decided he wasn't obeying his
8566 exit policy using him for any exits.
8567 - Only do openssl hardware accelerator stuff if openssl version is
8570 o New controller features/fixes:
8571 - Add a "RESETCONF" command so you can set config options like
8572 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
8573 a config option in the torrc with no value, then it clears it
8574 entirely (rather than setting it to its default).
8575 - Add a "GETINFO config-file" to tell us where torrc is.
8576 - Avoid sending blank lines when GETINFO replies should be empty.
8577 - Add a QUIT command for the controller (for using it manually).
8578 - Fix a bug in SAVECONF that was adding default dirservers and
8579 other redundant entries to the torrc file.
8581 o Start on the new directory design:
8582 - Generate, publish, cache, serve new network-status format.
8583 - Publish individual descriptors (by fingerprint, by "all", and by
8585 - Publish client and server recommended versions separately.
8586 - Allow tor_gzip_uncompress() to handle multiple concatenated
8587 compressed strings. Serve compressed groups of router
8588 descriptors. The compression logic here could be more
8590 - Distinguish v1 authorities (all currently trusted directories)
8591 from v2 authorities (all trusted directories).
8592 - Change DirServers config line to note which dirs are v1 authorities.
8593 - Add configuration option "V1AuthoritativeDirectory 1" which
8594 moria1, moria2, and tor26 should set.
8595 - Remove option when getting directory cache to see whether they
8596 support running-routers; they all do now. Replace it with one
8597 to see whether caches support v2 stuff.
8600 - Dirservers now do their own external reachability testing of each
8601 Tor server, and only list them as running if they've been found to
8602 be reachable. We also send back warnings to the server's logs if
8603 it uploads a descriptor that we already believe is unreachable.
8604 - Implement exit enclaves: if we know an IP address for the
8605 destination, and there's a running Tor server at that address
8606 which allows exit to the destination, then extend the circuit to
8607 that exit first. This provides end-to-end encryption and end-to-end
8608 authentication. Also, if the user wants a .exit address or enclave,
8609 use 4 hops rather than 3, and cannibalize a general circ for it
8611 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
8612 controller. Also, rotate dns and cpu workers if the controller
8613 changes options that will affect them; and initialize the dns
8614 worker cache tree whether or not we start out as a server.
8615 - Only upload a new server descriptor when options change, 18
8616 hours have passed, uptime is reset, or bandwidth changes a lot.
8617 - Check [X-]Forwarded-For headers in HTTP requests when generating
8618 log messages. This lets people run dirservers (and caches) behind
8619 Apache but still know which IP addresses are causing warnings.
8621 o Config option changes:
8622 - Replace (Fascist)Firewall* config options with a new
8623 ReachableAddresses option that understands address policies.
8624 For example, "ReachableAddresses *:80,*:443"
8625 - Get rid of IgnoreVersion undocumented config option, and make us
8626 only warn, never exit, when we're running an obsolete version.
8627 - Make MonthlyAccountingStart config option truly obsolete now.
8630 - Reject ports 465 and 587 in the default exit policy, since
8631 people have started using them for spam too.
8632 - It turns out we couldn't bootstrap a network since we added
8633 reachability detection in 0.1.0.1-rc. Good thing the Tor network
8634 has never gone down. Add an AssumeReachable config option to let
8635 servers and dirservers bootstrap. When we're trying to build a
8636 high-uptime or high-bandwidth circuit but there aren't enough
8637 suitable servers, try being less picky rather than simply failing.
8638 - Our logic to decide if the OR we connected to was the right guy
8639 was brittle and maybe open to a mitm for unverified routers.
8640 - We weren't cannibalizing circuits correctly for
8641 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
8642 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
8643 build those from scratch. This should make hidden services faster.
8644 - Predict required circuits better, with an eye toward making hidden
8645 services faster on the service end.
8646 - Retry streams if the exit node sends back a 'misc' failure. This
8647 should result in fewer random failures. Also, after failing
8648 from resolve failed or misc, reset the num failures, so we give
8649 it a fair shake next time we try.
8650 - Clean up the rendezvous warn log msgs, and downgrade some to info.
8651 - Reduce severity on logs about dns worker spawning and culling.
8652 - When we're shutting down and we do something like try to post a
8653 server descriptor or rendezvous descriptor, don't complain that
8654 we seem to be unreachable. Of course we are, we're shutting down.
8655 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
8656 We don't use them yet, but maybe one day our DNS resolver will be
8657 able to discover them.
8658 - Make ContactInfo mandatory for authoritative directory servers.
8659 - Require server descriptors to list IPv4 addresses -- hostnames
8660 are no longer allowed. This also fixes some potential security
8661 problems with people providing hostnames as their address and then
8662 preferentially resolving them to partition users.
8663 - Change log line for unreachability to explicitly suggest /etc/hosts
8664 as the culprit. Also make it clearer what IP address and ports we're
8665 testing for reachability.
8666 - Put quotes around user-supplied strings when logging so users are
8667 more likely to realize if they add bad characters (like quotes)
8669 - Let auth dir servers start without specifying an Address config
8671 - Make unit tests (and other invocations that aren't the real Tor)
8672 run without launching listeners, creating subdirectories, and so on.
8675 Changes in version 0.1.1.5-alpha - 2005-08-08
8676 o Bugfixes included in 0.1.0.14.
8678 o Bugfixes on 0.1.0.x:
8679 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
8680 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
8681 it would silently using ignore the 6668.
8684 Changes in version 0.1.0.14 - 2005-08-08
8685 o Bugfixes on 0.1.0.x:
8686 - Fix the other half of the bug with crypto handshakes
8688 - Fix an assert trigger if you send a 'signal term' via the
8689 controller when it's listening for 'event info' messages.
8692 Changes in version 0.1.1.4-alpha - 2005-08-04
8693 o Bugfixes included in 0.1.0.13.
8696 - Improve tor_gettimeofday() granularity on windows.
8697 - Make clients regenerate their keys when their IP address changes.
8698 - Implement some more GETINFO goodness: expose helper nodes, config
8699 options, getinfo keys.
8702 Changes in version 0.1.0.13 - 2005-08-04
8703 o Bugfixes on 0.1.0.x:
8704 - Fix a critical bug in the security of our crypto handshakes.
8705 - Fix a size_t underflow in smartlist_join_strings2() that made
8706 it do bad things when you hand it an empty smartlist.
8707 - Fix Windows installer to ship Tor license (thanks to Aphex for
8708 pointing out this oversight) and put a link to the doc directory
8710 - Explicitly set no-unaligned-access for sparc: it turns out the
8711 new gcc's let you compile broken code, but that doesn't make it
8715 Changes in version 0.1.1.3-alpha - 2005-07-23
8716 o Bugfixes on 0.1.1.2-alpha:
8717 - Fix a bug in handling the controller's "post descriptor"
8719 - Fix several bugs in handling the controller's "extend circuit"
8721 - Fix a bug in handling the controller's "stream status" event.
8722 - Fix an assert failure if we have a controller listening for
8723 circuit events and we go offline.
8724 - Re-allow hidden service descriptors to publish 0 intro points.
8725 - Fix a crash when generating your hidden service descriptor if
8726 you don't have enough intro points already.
8728 o New features on 0.1.1.2-alpha:
8729 - New controller function "getinfo accounting", to ask how
8730 many bytes we've used in this time period.
8731 - Experimental support for helper nodes: a lot of the risk from
8732 a small static adversary comes because users pick new random
8733 nodes every time they rebuild a circuit. Now users will try to
8734 stick to the same small set of entry nodes if they can. Not
8735 enabled by default yet.
8737 o Bugfixes on 0.1.0.12:
8738 - If you're an auth dir server, always publish your dirport,
8739 even if you haven't yet found yourself to be reachable.
8740 - Fix a size_t underflow in smartlist_join_strings2() that made
8741 it do bad things when you hand it an empty smartlist.
8744 Changes in version 0.1.0.12 - 2005-07-18
8745 o New directory servers:
8746 - tor26 has changed IP address.
8748 o Bugfixes on 0.1.0.x:
8749 - Fix a possible double-free in tor_gzip_uncompress().
8750 - When --disable-threads is set, do not search for or link against
8752 - Don't trigger an assert if an authoritative directory server
8753 claims its dirport is 0.
8754 - Fix bug with removing Tor as an NT service: some people were
8755 getting "The service did not return an error." Thanks to Matt
8759 Changes in version 0.1.1.2-alpha - 2005-07-15
8760 o New directory servers:
8761 - tor26 has changed IP address.
8763 o Bugfixes on 0.1.0.x, crashes/leaks:
8764 - Port the servers-not-obeying-their-exit-policies fix from
8766 - Fix an fd leak in start_daemon().
8767 - On Windows, you can't always reopen a port right after you've
8768 closed it. So change retry_listeners() to only close and re-open
8769 ports that have changed.
8770 - Fix a possible double-free in tor_gzip_uncompress().
8772 o Bugfixes on 0.1.0.x, usability:
8773 - When tor_socketpair() fails in Windows, give a reasonable
8774 Windows-style errno back.
8775 - Let people type "tor --install" as well as "tor -install" when
8777 want to make it an NT service.
8778 - NT service patch from Matt Edman to improve error messages.
8779 - When the controller asks for a config option with an abbreviated
8780 name, give the full name in our response.
8781 - Correct the man page entry on TrackHostExitsExpire.
8782 - Looks like we were never delivering deflated (i.e. compressed)
8783 running-routers lists, even when asked. Oops.
8784 - When --disable-threads is set, do not search for or link against
8787 o Bugfixes on 0.1.1.x:
8788 - Fix a seg fault with autodetecting which controller version is
8792 - New hidden service descriptor format: put a version in it, and
8793 let people specify introduction/rendezvous points that aren't
8794 in "the directory" (which is subjective anyway).
8795 - Allow the DEBUG controller event to work again. Mark certain log
8796 entries as "don't tell this to controllers", so we avoid cycles.
8799 Changes in version 0.1.0.11 - 2005-06-30
8800 o Bugfixes on 0.1.0.x:
8801 - Fix major security bug: servers were disregarding their
8802 exit policies if clients behaved unexpectedly.
8803 - Make OS X init script check for missing argument, so we don't
8804 confuse users who invoke it incorrectly.
8805 - Fix a seg fault in "tor --hash-password foo".
8806 - The MAPADDRESS control command was broken.
8809 Changes in version 0.1.1.1-alpha - 2005-06-29
8811 - Make OS X init script check for missing argument, so we don't
8812 confuse users who invoke it incorrectly.
8813 - Fix a seg fault in "tor --hash-password foo".
8814 - Fix a possible way to DoS dirservers.
8815 - When we complain that your exit policy implicitly allows local or
8816 private address spaces, name them explicitly so operators can
8818 - Make the log message less scary when all the dirservers are
8819 temporarily unreachable.
8820 - We were printing the number of idle dns workers incorrectly when
8824 - Revised controller protocol (version 1) that uses ascii rather
8825 than binary. Add supporting libraries in python and java so you
8826 can use the controller from your applications without caring how
8828 - Spiffy new support for crypto hardware accelerators. Can somebody
8832 Changes in version 0.0.9.10 - 2005-06-16
8833 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
8834 - Refuse relay cells that claim to have a length larger than the
8835 maximum allowed. This prevents a potential attack that could read
8836 arbitrary memory (e.g. keys) from an exit server's process
8840 Changes in version 0.1.0.10 - 2005-06-14
8841 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
8842 libevent before 1.1a.
8845 Changes in version 0.1.0.9-rc - 2005-06-09
8847 - Reset buf->highwater every time buf_shrink() is called, not just on
8848 a successful shrink. This was causing significant memory bloat.
8849 - Fix buffer overflow when checking hashed passwords.
8850 - Security fix: if seeding the RNG on Win32 fails, quit.
8851 - Allow seeding the RNG on Win32 even when you're not running as
8853 - Disable threading on Solaris too. Something is wonky with it,
8854 cpuworkers, and reentrant libs.
8855 - Reenable the part of the code that tries to flush as soon as an
8856 OR outbuf has a full TLS record available. Perhaps this will make
8857 OR outbufs not grow as huge except in rare cases, thus saving lots
8858 of CPU time plus memory.
8859 - Reject malformed .onion addresses rather then passing them on as
8860 normal web requests.
8861 - Adapt patch from Adam Langley: fix possible memory leak in
8862 tor_lookup_hostname().
8863 - Initialize libevent later in the startup process, so the logs are
8864 already established by the time we start logging libevent warns.
8865 - Use correct errno on win32 if libevent fails.
8866 - Check and warn about known-bad/slow libevent versions.
8867 - Pay more attention to the ClientOnly config option.
8868 - Have torctl.in/tor.sh.in check for location of su binary (needed
8870 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
8871 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
8872 HttpProxyAuthenticator
8873 - Stop warning about sigpipes in the logs. We're going to
8874 pretend that getting these occassionally is normal and fine.
8875 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
8877 installer screens; and don't put stuff into StartupItems unless
8878 the user asks you to.
8879 - Require servers that use the default dirservers to have public IP
8880 addresses. We have too many servers that are configured with private
8881 IPs and their admins never notice the log entries complaining that
8882 their descriptors are being rejected.
8883 - Add OSX uninstall instructions. An actual uninstall script will
8887 Changes in version 0.1.0.8-rc - 2005-05-23
8889 - It turns out that kqueue on OS X 10.3.9 was causing kernel
8890 panics. Disable kqueue on all OS X Tors.
8891 - Fix RPM: remove duplicate line accidentally added to the rpm
8893 - Disable threads on openbsd too, since its gethostaddr is not
8895 - Tolerate libevent 0.8 since it still works, even though it's
8897 - Enable building on Red Hat 9.0 again.
8898 - Allow the middle hop of the testing circuit to be running any
8899 version, now that most of them have the bugfix to let them connect
8900 to unknown servers. This will allow reachability testing to work
8901 even when 0.0.9.7-0.0.9.9 become obsolete.
8902 - Handle relay cells with rh.length too large. This prevents
8903 a potential attack that could read arbitrary memory (maybe even
8904 keys) from the exit server's process.
8905 - We screwed up the dirport reachability testing when we don't yet
8906 have a cached version of the directory. Hopefully now fixed.
8907 - Clean up router_load_single_router() (used by the controller),
8908 so it doesn't seg fault on error.
8909 - Fix a minor memory leak when somebody establishes an introduction
8910 point at your Tor server.
8911 - If a socks connection ends because read fails, don't warn that
8912 you're not sending a socks reply back.
8915 - Add HttpProxyAuthenticator config option too, that works like
8916 the HttpsProxyAuthenticator config option.
8917 - Encode hashed controller passwords in hex instead of base64,
8918 to make it easier to write controllers.
8921 Changes in version 0.1.0.7-rc - 2005-05-17
8923 - Fix a bug in the OS X package installer that prevented it from
8924 installing on Tiger.
8925 - Fix a script bug in the OS X package installer that made it
8926 complain during installation.
8927 - Find libevent even if it's hiding in /usr/local/ and your
8928 CFLAGS and LDFLAGS don't tell you to look there.
8929 - Be able to link with libevent as a shared library (the default
8930 after 1.0d), even if it's hiding in /usr/local/lib and even
8931 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
8932 assuming you're running gcc. Otherwise fail and give a useful
8934 - Fix a bug in the RPM packager: set home directory for _tor to
8935 something more reasonable when first installing.
8936 - Free a minor amount of memory that is still reachable on exit.
8939 Changes in version 0.1.0.6-rc - 2005-05-14
8941 - Implement --disable-threads configure option. Disable threads on
8942 netbsd by default, because it appears to have no reentrant resolver
8944 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
8945 release (1.1) detects and disables kqueue if it's broken.
8946 - Append default exit policy before checking for implicit internal
8947 addresses. Now we don't log a bunch of complaints on startup
8948 when using the default exit policy.
8949 - Some people were putting "Address " in their torrc, and they had
8950 a buggy resolver that resolved " " to 0.0.0.0. Oops.
8951 - If DataDir is ~/.tor, and that expands to /.tor, then default to
8952 LOCALSTATEDIR/tor instead.
8953 - Fix fragmented-message bug in TorControl.py.
8954 - Resolve a minor bug which would prevent unreachable dirports
8955 from getting suppressed in the published descriptor.
8956 - When the controller gave us a new descriptor, we weren't resolving
8957 it immediately, so Tor would think its address was 0.0.0.0 until
8958 we fetched a new directory.
8959 - Fix an uppercase/lowercase case error in suppressing a bogus
8960 libevent warning on some Linuxes.
8963 - Begin scrubbing sensitive strings from logs by default. Turn off
8964 the config option SafeLogging if you need to do debugging.
8965 - Switch to a new buffer management algorithm, which tries to avoid
8966 reallocing and copying quite as much. In first tests it looks like
8967 it uses *more* memory on average, but less cpu.
8968 - First cut at support for "create-fast" cells. Clients can use
8969 these when extending to their first hop, since the TLS already
8970 provides forward secrecy and authentication. Not enabled on
8972 - When dirservers refuse a router descriptor, we now log its
8973 contactinfo, platform, and the poster's IP address.
8974 - Call tor_free_all instead of connections_free_all after forking, to
8975 save memory on systems that need to fork.
8976 - Whine at you if you're a server and you don't set your contactinfo.
8977 - Implement --verify-config command-line option to check if your torrc
8978 is valid without actually launching Tor.
8979 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
8980 rather than just rejecting it.
8983 Changes in version 0.1.0.5-rc - 2005-04-27
8985 - Stop trying to print a null pointer if an OR conn fails because
8986 we didn't like its cert.
8988 - Switch our internal buffers implementation to use a ring buffer,
8989 to hopefully improve performance for fast servers a lot.
8990 - Add HttpsProxyAuthenticator support (basic auth only), based
8991 on patch from Adam Langley.
8992 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
8993 the fast servers that have been joining lately.
8994 - Give hidden service accesses extra time on the first attempt,
8995 since 60 seconds is often only barely enough. This might improve
8997 - Improve performance for dirservers: stop re-parsing the whole
8998 directory every time you regenerate it.
8999 - Add more debugging info to help us find the weird dns freebsd
9000 pthreads bug; cleaner debug messages to help track future issues.
9003 Changes in version 0.0.9.9 - 2005-04-23
9004 o Bugfixes on 0.0.9.x:
9005 - If unofficial Tor clients connect and send weird TLS certs, our
9006 Tor server triggers an assert. This release contains a minimal
9007 backport from the broader fix that we put into 0.1.0.4-rc.
9010 Changes in version 0.1.0.4-rc - 2005-04-23
9012 - If unofficial Tor clients connect and send weird TLS certs, our
9013 Tor server triggers an assert. Stop asserting, and start handling
9014 TLS errors better in other situations too.
9015 - When the controller asks us to tell it about all the debug-level
9016 logs, it turns out we were generating debug-level logs while
9017 telling it about them, which turns into a bad loop. Now keep
9018 track of whether you're sending a debug log to the controller,
9019 and don't log when you are.
9020 - Fix the "postdescriptor" feature of the controller interface: on
9021 non-complete success, only say "done" once.
9023 - Clients are now willing to load balance over up to 2mB, not 1mB,
9024 of advertised bandwidth capacity.
9025 - Add a NoPublish config option, so you can be a server (e.g. for
9026 testing running Tor servers in other Tor networks) without
9027 publishing your descriptor to the primary dirservers.
9030 Changes in version 0.1.0.3-rc - 2005-04-08
9031 o Improvements on 0.1.0.2-rc:
9032 - Client now retries when streams end early for 'hibernating' or
9033 'resource limit' reasons, rather than failing them.
9034 - More automated handling for dirserver operators:
9035 - Automatically approve nodes running 0.1.0.2-rc or later,
9036 now that the the reachability detection stuff is working.
9037 - Now we allow two unverified servers with the same nickname
9038 but different keys. But if a nickname is verified, only that
9039 nickname+key are allowed.
9040 - If you're an authdirserver connecting to an address:port,
9041 and it's not the OR you were expecting, forget about that
9042 descriptor. If he *was* the one you were expecting, then forget
9043 about all other descriptors for that address:port.
9044 - Allow servers to publish descriptors from 12 hours in the future.
9045 Corollary: only whine about clock skew from the dirserver if
9046 he's a trusted dirserver (since now even verified servers could
9047 have quite wrong clocks).
9048 - Adjust maximum skew and age for rendezvous descriptors: let skew
9049 be 48 hours rather than 90 minutes.
9050 - Efficiency improvements:
9051 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
9052 it much faster to look up a circuit for each relay cell.
9053 - Remove most calls to assert_all_pending_dns_resolves_ok(),
9054 since they're eating our cpu on exit nodes.
9055 - Stop wasting time doing a case insensitive comparison for every
9056 dns name every time we do any lookup. Canonicalize the names to
9057 lowercase and be done with it.
9058 - Start sending 'truncated' cells back rather than destroy cells,
9059 if the circuit closes in front of you. This means we won't have
9060 to abandon partially built circuits.
9061 - Only warn once per nickname from add_nickname_list_to_smartlist
9062 per failure, so an entrynode or exitnode choice that's down won't
9064 - Put a note in the torrc about abuse potential with the default
9066 - Revise control spec and implementation to allow all log messages to
9067 be sent to controller with their severities intact (suggested by
9068 Matt Edman). Update TorControl to handle new log event types.
9069 - Provide better explanation messages when controller's POSTDESCRIPTOR
9071 - Stop putting nodename in the Platform string in server descriptors.
9072 It doesn't actually help, and it is confusing/upsetting some people.
9074 o Bugfixes on 0.1.0.2-rc:
9075 - We were printing the host mask wrong in exit policies in server
9076 descriptors. This isn't a critical bug though, since we were still
9077 obeying the exit policy internally.
9078 - Fix Tor when compiled with libevent but without pthreads: move
9079 connection_unregister() from _connection_free() to
9081 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
9082 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
9083 when we look through the connection array, we'll find any of the
9084 cpu/dnsworkers. This is no good.
9086 o Bugfixes on 0.0.9.8:
9087 - Fix possible bug on threading platforms (e.g. win32) which was
9088 leaking a file descriptor whenever a cpuworker or dnsworker died.
9089 - When using preferred entry or exit nodes, ignore whether the
9090 circuit wants uptime or capacity. They asked for the nodes, they
9092 - chdir() to your datadirectory at the *end* of the daemonize process,
9093 not the beginning. This was a problem because the first time you
9094 run tor, if your datadir isn't there, and you have runasdaemon set
9095 to 1, it will try to chdir to it before it tries to create it. Oops.
9096 - Handle changed router status correctly when dirserver reloads
9097 fingerprint file. We used to be dropping all unverified descriptors
9098 right then. The bug was hidden because we would immediately
9099 fetch a directory from another dirserver, which would include the
9100 descriptors we just dropped.
9101 - When we're connecting to an OR and he's got a different nickname/key
9102 than we were expecting, only complain loudly if we're an OP or a
9103 dirserver. Complaining loudly to the OR admins just confuses them.
9104 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
9105 artificially capped at 500kB.
9108 Changes in version 0.0.9.8 - 2005-04-07
9109 o Bugfixes on 0.0.9.x:
9110 - We have a bug that I haven't found yet. Sometimes, very rarely,
9111 cpuworkers get stuck in the 'busy' state, even though the cpuworker
9112 thinks of itself as idle. This meant that no new circuits ever got
9113 established. Here's a workaround to kill any cpuworker that's been
9114 busy for more than 100 seconds.
9117 Changes in version 0.1.0.2-rc - 2005-04-01
9118 o Bugfixes on 0.1.0.1-rc:
9119 - Fixes on reachability detection:
9120 - Don't check for reachability while hibernating.
9121 - If ORPort is reachable but DirPort isn't, still publish the
9122 descriptor, but zero out DirPort until it's found reachable.
9123 - When building testing circs for ORPort testing, use only
9124 high-bandwidth nodes, so fewer circuits fail.
9125 - Complain about unreachable ORPort separately from unreachable
9126 DirPort, so the user knows what's going on.
9127 - Make sure we only conclude ORPort reachability if we didn't
9128 initiate the conn. Otherwise we could falsely conclude that
9129 we're reachable just because we connected to the guy earlier
9130 and he used that same pipe to extend to us.
9131 - Authdirservers shouldn't do ORPort reachability detection,
9132 since they're in clique mode, so it will be rare to find a
9133 server not already connected to them.
9134 - When building testing circuits, always pick middle hops running
9135 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
9136 bug. (This is a kludge; it will go away when 0.0.9.x becomes
9138 - When we decide we're reachable, actually publish our descriptor
9140 - Fix bug in redirectstream in the controller.
9141 - Fix the state descriptor strings so logs don't claim edge streams
9142 are in a different state than they actually are.
9143 - Use recent libevent features when possible (this only really affects
9144 win32 and osx right now, because the new libevent with these
9145 features hasn't been released yet). Add code to suppress spurious
9147 - Prevent possible segfault in connection_close_unattached_ap().
9148 - Fix newlines on torrc in win32.
9149 - Improve error msgs when tor-resolve fails.
9151 o Improvements on 0.0.9.x:
9152 - New experimental script tor/contrib/ExerciseServer.py (needs more
9153 work) that uses the controller interface to build circuits and
9154 fetch pages over them. This will help us bootstrap servers that
9155 have lots of capacity but haven't noticed it yet.
9156 - New experimental script tor/contrib/PathDemo.py (needs more work)
9157 that uses the controller interface to let you choose whole paths
9159 "<hostname>.<path,separated by dots>.<length of path>.path"
9160 - When we've connected to an OR and handshaked but didn't like
9161 the result, we were closing the conn without sending destroy
9162 cells back for pending circuits. Now send those destroys.
9165 Changes in version 0.0.9.7 - 2005-04-01
9166 o Bugfixes on 0.0.9.x:
9167 - Fix another race crash bug (thanks to Glenn Fink for reporting).
9168 - Compare identity to identity, not to nickname, when extending to
9169 a router not already in the directory. This was preventing us from
9170 extending to unknown routers. Oops.
9171 - Make sure to create OS X Tor user in <500 range, so we aren't
9172 creating actual system users.
9173 - Note where connection-that-hasn't-sent-end was marked, and fix
9174 a few really loud instances of this harmless bug (it's fixed more
9178 Changes in version 0.1.0.1-rc - 2005-03-28
9180 - Add reachability testing. Your Tor server will automatically try
9181 to see if its ORPort and DirPort are reachable from the outside,
9182 and it won't upload its descriptor until it decides they are.
9183 - Handle unavailable hidden services better. Handle slow or busy
9184 hidden services better.
9185 - Add support for CONNECTing through https proxies, with "HttpsProxy"
9187 - New exit policy: accept most low-numbered ports, rather than
9188 rejecting most low-numbered ports.
9189 - More Tor controller support (still experimental). See
9190 http://tor.eff.org/doc/control-spec.txt for all the new features,
9191 including signals to emulate unix signals from any platform;
9192 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
9193 closestream; closecircuit; etc.
9194 - Make nt services work and start on startup on win32 (based on
9195 patch by Matt Edman).
9196 - Add a new AddressMap config directive to rewrite incoming socks
9197 addresses. This lets you, for example, declare an implicit
9198 required exit node for certain sites.
9199 - Add a new TrackHostExits config directive to trigger addressmaps
9200 for certain incoming socks addresses -- for sites that break when
9201 your exit keeps changing (based on patch by Mike Perry).
9202 - Redo the client-side dns cache so it's just an addressmap too.
9203 - Notice when our IP changes, and reset stats/uptime/reachability.
9204 - When an application is using socks5, give him the whole variety of
9205 potential socks5 responses (connect refused, host unreachable, etc),
9206 rather than just "success" or "failure".
9207 - A more sane version numbering system. See
9208 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
9209 - New contributed script "exitlist": a simple python script to
9210 parse directories and find Tor nodes that exit to listed
9212 - New contributed script "privoxy-tor-toggle" to toggle whether
9213 Privoxy uses Tor. Seems to be configured for Debian by default.
9214 - Report HTTP reasons to client when getting a response from directory
9215 servers -- so you can actually know what went wrong.
9216 - New config option MaxAdvertisedBandwidth which lets you advertise
9217 a low bandwidthrate (to not attract as many circuits) while still
9218 allowing a higher bandwidthrate in reality.
9220 o Robustness/stability fixes:
9221 - Make Tor use Niels Provos's libevent instead of its current
9222 poll-but-sometimes-select mess. This will let us use faster async
9223 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
9225 - pthread support now too. This was forced because when we forked,
9226 we ended up wasting a lot of duplicate ram over time. Also switch
9227 to foo_r versions of some library calls to allow reentry and
9229 - Better handling for heterogeneous / unreliable nodes:
9230 - Annotate circuits w/ whether they aim to contain high uptime nodes
9231 and/or high capacity nodes. When building circuits, choose
9233 - This means that every single node in an intro rend circuit,
9234 not just the last one, will have a minimum uptime.
9235 - New config option LongLivedPorts to indicate application streams
9236 that will want high uptime circuits.
9237 - Servers reset uptime when a dir fetch entirely fails. This
9238 hopefully reflects stability of the server's network connectivity.
9239 - If somebody starts his tor server in Jan 2004 and then fixes his
9240 clock, don't make his published uptime be a year.
9241 - Reset published uptime when you wake up from hibernation.
9242 - Introduce a notion of 'internal' circs, which are chosen without
9243 regard to the exit policy of the last hop. Intro and rendezvous
9244 circs must be internal circs, to avoid leaking information. Resolve
9245 and connect streams can use internal circs if they want.
9246 - New circuit pooling algorithm: make sure to have enough circs around
9247 to satisfy any predicted ports, and also make sure to have 2 internal
9248 circs around if we've required internal circs lately (and with high
9249 uptime if we've seen that lately too).
9250 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
9251 which describes how often we retry making new circuits if current
9252 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
9253 how long we're willing to make use of an already-dirty circuit.
9254 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
9255 circ as necessary, if there are any completed ones lying around
9256 when we try to launch one.
9257 - Make hidden services try to establish a rendezvous for 30 seconds,
9258 rather than for n (where n=3) attempts to build a circuit.
9259 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
9260 "ShutdownWaitLength".
9261 - Try to be more zealous about calling connection_edge_end when
9262 things go bad with edge conns in connection.c.
9263 - Revise tor-spec to add more/better stream end reasons.
9264 - Revise all calls to connection_edge_end to avoid sending "misc",
9265 and to take errno into account where possible.
9268 - Fix a race condition that can trigger an assert, when we have a
9269 pending create cell and an OR connection fails right then.
9270 - Fix several double-mark-for-close bugs, e.g. where we were finding
9271 a conn for a cell even if that conn is already marked for close.
9272 - Make sequence of log messages when starting on win32 with no config
9273 file more reasonable.
9274 - When choosing an exit node for a new non-internal circ, don't take
9275 into account whether it'll be useful for any pending x.onion
9276 addresses -- it won't.
9277 - Turn addr_policy_compare from a tristate to a quadstate; this should
9278 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
9279 for google.com" problem.
9280 - Make "platform" string in descriptor more accurate for Win32 servers,
9281 so it's not just "unknown platform".
9282 - Fix an edge case in parsing config options (thanks weasel).
9283 If they say "--" on the commandline, it's not an option.
9284 - Reject odd-looking addresses at the client (e.g. addresses that
9285 contain a colon), rather than having the server drop them because
9287 - tor-resolve requests were ignoring .exit if there was a working circuit
9288 they could use instead.
9289 - REUSEADDR on normal platforms means you can rebind to the port
9290 right after somebody else has let it go. But REUSEADDR on win32
9291 means to let you bind to the port _even when somebody else
9292 already has it bound_! So, don't do that on Win32.
9293 - Change version parsing logic: a version is "obsolete" if it is not
9294 recommended and (1) there is a newer recommended version in the
9295 same series, or (2) there are no recommended versions in the same
9296 series, but there are some recommended versions in a newer series.
9297 A version is "new" if it is newer than any recommended version in
9299 - Stop most cases of hanging up on a socks connection without sending
9303 - Require BandwidthRate to be at least 20kB/s for servers.
9304 - When a dirserver causes you to give a warn, mention which dirserver
9306 - New config option DirAllowPrivateAddresses for authdirservers.
9307 Now by default they refuse router descriptors that have non-IP or
9308 private-IP addresses.
9309 - Stop publishing socksport in the directory, since it's not
9310 actually meant to be public. For compatibility, publish a 0 there
9312 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
9313 smart" value, that is low for servers and high for clients.
9314 - If our clock jumps forward by 100 seconds or more, assume something
9315 has gone wrong with our network and abandon all not-yet-used circs.
9316 - Warn when exit policy implicitly allows local addresses.
9317 - If we get an incredibly skewed timestamp from a dirserver mirror
9318 that isn't a verified OR, don't warn -- it's probably him that's
9320 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
9321 cookies to disk and doesn't log each web request to disk. (Thanks
9322 to Brett Carrington for pointing this out.)
9323 - When a client asks us for a dir mirror and we don't have one,
9324 launch an attempt to get a fresh one.
9325 - If we're hibernating and we get a SIGINT, exit immediately.
9326 - Add --with-dmalloc ./configure option, to track memory leaks.
9327 - And try to free all memory on closing, so we can detect what
9329 - Cache local dns resolves correctly even when they're .exit
9331 - Give a better warning when some other server advertises an
9332 ORPort that is actually an apache running ssl.
9333 - Add "opt hibernating 1" to server descriptor to make it clearer
9334 whether the server is hibernating.
9337 Changes in version 0.0.9.6 - 2005-03-24
9338 o Bugfixes on 0.0.9.x (crashes and asserts):
9339 - Add new end stream reasons to maintainance branch. Fix bug where
9340 reason (8) could trigger an assert. Prevent bug from recurring.
9341 - Apparently win32 stat wants paths to not end with a slash.
9342 - Fix assert triggers in assert_cpath_layer_ok(), where we were
9343 blowing away the circuit that conn->cpath_layer points to, then
9344 checking to see if the circ is well-formed. Backport check to make
9345 sure we dont use the cpath on a closed connection.
9346 - Prevent circuit_resume_edge_reading_helper() from trying to package
9347 inbufs for marked-for-close streams.
9348 - Don't crash on hup if your options->address has become unresolvable.
9349 - Some systems (like OS X) sometimes accept() a connection and tell
9350 you the remote host is 0.0.0.0:0. If this happens, due to some
9351 other mis-features, we get confused; so refuse the conn for now.
9353 o Bugfixes on 0.0.9.x (other):
9354 - Fix harmless but scary "Unrecognized content encoding" warn message.
9355 - Add new stream error reason: TORPROTOCOL reason means "you are not
9356 speaking a version of Tor I understand; say bye-bye to your stream."
9357 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
9358 into the future, now that we are more tolerant of skew. This
9359 resolves a bug where a Tor server would refuse to cache a directory
9360 because all the directories it gets are too far in the future;
9361 yet the Tor server never logs any complaints about clock skew.
9362 - Mac packaging magic: make man pages useable, and do not overwrite
9363 existing torrc files.
9364 - Make OS X log happily to /var/log/tor/tor.log
9367 Changes in version 0.0.9.5 - 2005-02-22
9368 o Bugfixes on 0.0.9.x:
9369 - Fix an assert race at exit nodes when resolve requests fail.
9370 - Stop picking unverified dir mirrors--it only leads to misery.
9371 - Patch from Matt Edman to make NT services work better. Service
9372 support is still not compiled into the executable by default.
9373 - Patch from Dmitri Bely so the Tor service runs better under
9374 the win32 SYSTEM account.
9375 - Make tor-resolve actually work (?) on Win32.
9376 - Fix a sign bug when getrlimit claims to have 4+ billion
9377 file descriptors available.
9378 - Stop refusing to start when bandwidthburst == bandwidthrate.
9379 - When create cells have been on the onion queue more than five
9380 seconds, just send back a destroy and take them off the list.
9383 Changes in version 0.0.9.4 - 2005-02-03
9384 o Bugfixes on 0.0.9:
9385 - Fix an assert bug that took down most of our servers: when
9386 a server claims to have 1 GB of bandwidthburst, don't
9388 - Don't crash as badly if we have spawned the max allowed number
9389 of dnsworkers, or we're out of file descriptors.
9390 - Block more file-sharing ports in the default exit policy.
9391 - MaxConn is now automatically set to the hard limit of max
9392 file descriptors we're allowed (ulimit -n), minus a few for
9394 - Give a clearer message when servers need to raise their
9395 ulimit -n when they start running out of file descriptors.
9396 - SGI Compatibility patches from Jan Schaumann.
9397 - Tolerate a corrupt cached directory better.
9398 - When a dirserver hasn't approved your server, list which one.
9399 - Go into soft hibernation after 95% of the bandwidth is used,
9400 not 99%. This is especially important for daily hibernators who
9401 have a small accounting max. Hopefully it will result in fewer
9402 cut connections when the hard hibernation starts.
9403 - Load-balance better when using servers that claim more than
9404 800kB/s of capacity.
9405 - Make NT services work (experimental, only used if compiled in).
9408 Changes in version 0.0.9.3 - 2005-01-21
9409 o Bugfixes on 0.0.9:
9410 - Backport the cpu use fixes from main branch, so busy servers won't
9411 need as much processor time.
9412 - Work better when we go offline and then come back, or when we
9413 run Tor at boot before the network is up. We do this by
9414 optimistically trying to fetch a new directory whenever an
9415 application request comes in and we think we're offline -- the
9416 human is hopefully a good measure of when the network is back.
9417 - Backport some minimal hidserv bugfixes: keep rend circuits open as
9418 long as you keep using them; actually publish hidserv descriptors
9419 shortly after they change, rather than waiting 20-40 minutes.
9420 - Enable Mac startup script by default.
9421 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
9422 - When you update AllowUnverifiedNodes or FirewallPorts via the
9423 controller's setconf feature, we were always appending, never
9425 - When you update HiddenServiceDir via setconf, it was screwing up
9426 the order of reading the lines, making it fail.
9427 - Do not rewrite a cached directory back to the cache; otherwise we
9428 will think it is recent and not fetch a newer one on startup.
9429 - Workaround for webservers that lie about Content-Encoding: Tor
9430 now tries to autodetect compressed directories and compression
9431 itself. This lets us Proxypass dir fetches through apache.
9434 Changes in version 0.0.9.2 - 2005-01-04
9435 o Bugfixes on 0.0.9 (crashes and asserts):
9436 - Fix an assert on startup when the disk is full and you're logging
9438 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
9439 style address, then we'd crash.
9440 - Fix an assert trigger when the running-routers string we get from
9441 a dirserver is broken.
9442 - Make worker threads start and run on win32. Now win32 servers
9444 - Bandaid (not actually fix, but now it doesn't crash) an assert
9445 where the dns worker dies mysteriously and the main Tor process
9446 doesn't remember anything about the address it was resolving.
9448 o Bugfixes on 0.0.9 (Win32):
9449 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
9450 name out of the warning/assert messages.
9451 - Fix a superficial "unhandled error on read" bug on win32.
9452 - The win32 installer no longer requires a click-through for our
9453 license, since our Free Software license grants rights but does not
9455 - Win32: When connecting to a dirserver fails, try another one
9456 immediately. (This was already working for non-win32 Tors.)
9457 - Stop trying to parse $HOME on win32 when hunting for default
9459 - Make tor-resolve.c work on win32 by calling network_init().
9461 o Bugfixes on 0.0.9 (other):
9462 - Make 0.0.9.x build on Solaris again.
9463 - Due to a fencepost error, we were blowing away the \n when reporting
9464 confvalue items in the controller. So asking for multiple config
9465 values at once couldn't work.
9466 - When listing circuits that are pending on an opening OR connection,
9467 if we're an OR we were listing circuits that *end* at us as
9468 being pending on every listener, dns/cpu worker, etc. Stop that.
9469 - Dirservers were failing to create 'running-routers' or 'directory'
9470 strings if we had more than some threshold of routers. Fix them so
9471 they can handle any number of routers.
9472 - Fix a superficial "Duplicate mark for close" bug.
9473 - Stop checking for clock skew for OR connections, even for servers.
9474 - Fix a fencepost error that was chopping off the last letter of any
9475 nickname that is the maximum allowed nickname length.
9476 - Update URLs in log messages so they point to the new website.
9477 - Fix a potential problem in mangling server private keys while
9478 writing to disk (not triggered yet, as far as we know).
9479 - Include the licenses for other free software we include in Tor,
9480 now that we're shipping binary distributions more regularly.
9483 Changes in version 0.0.9.1 - 2004-12-15
9484 o Bugfixes on 0.0.9:
9485 - Make hibernation actually work.
9486 - Make HashedControlPassword config option work.
9487 - When we're reporting event circuit status to a controller,
9488 don't use the stream status code.
9491 Changes in version 0.0.9 - 2004-12-12
9493 - Clean up manpage and torrc.sample file.
9494 - Clean up severities and text of log warnings.
9496 - Make servers trigger an assert when they enter hibernation.
9499 Changes in version 0.0.9rc7 - 2004-12-08
9500 o Bugfixes on 0.0.9rc:
9501 - Fix a stack-trashing crash when an exit node begins hibernating.
9502 - Avoid looking at unallocated memory while considering which
9503 ports we need to build circuits to cover.
9504 - Stop a sigpipe: when an 'end' cell races with eof from the app,
9505 we shouldn't hold-open-until-flush if the eof arrived first.
9506 - Fix a bug with init_cookie_authentication() in the controller.
9507 - When recommending new-format log lines, if the upper bound is
9508 LOG_ERR, leave it implicit.
9510 o Bugfixes on 0.0.8.1:
9511 - Fix a whole slew of memory leaks.
9512 - Fix isspace() and friends so they still make Solaris happy
9513 but also so they don't trigger asserts on win32.
9514 - Fix parse_iso_time on platforms without strptime (eg win32).
9515 - win32: tolerate extra "readable" events better.
9516 - win32: when being multithreaded, leave parent fdarray open.
9517 - Make unit tests work on win32.
9520 Changes in version 0.0.9rc6 - 2004-12-06
9521 o Bugfixes on 0.0.9pre:
9522 - Clean up some more integer underflow opportunities (not exploitable
9524 - While hibernating, hup should not regrow our listeners.
9525 - Send an end to the streams we close when we hibernate, rather
9526 than just chopping them off.
9527 - React to eof immediately on non-open edge connections.
9529 o Bugfixes on 0.0.8.1:
9530 - Calculate timeout for waiting for a connected cell from the time
9531 we sent the begin cell, not from the time the stream started. If
9532 it took a long time to establish the circuit, we would time out
9533 right after sending the begin cell.
9534 - Fix router_compare_addr_to_addr_policy: it was not treating a port
9535 of * as always matching, so we were picking reject *:* nodes as
9536 exit nodes too. Oops.
9539 - New circuit building strategy: keep a list of ports that we've
9540 used in the past 6 hours, and always try to have 2 circuits open
9541 or on the way that will handle each such port. Seed us with port
9542 80 so web users won't complain that Tor is "slow to start up".
9543 - Make kill -USR1 dump more useful stats about circuits.
9544 - When warning about retrying or giving up, print the address, so
9545 the user knows which one it's talking about.
9546 - If you haven't used a clean circuit in an hour, throw it away,
9547 just to be on the safe side. (This means after 6 hours a totally
9548 unused Tor client will have no circuits open.)
9551 Changes in version 0.0.9rc5 - 2004-12-01
9552 o Bugfixes on 0.0.8.1:
9553 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
9554 - Let resolve conns retry/expire also, rather than sticking around
9556 - If we are using select, make sure we stay within FD_SETSIZE.
9558 o Bugfixes on 0.0.9pre:
9559 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
9560 but doesn't seem to be currently; thanks to Ilja van Sprundel for
9562 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
9563 instead. Impose minima and maxima for all *Period options; impose
9564 even tighter maxima for fetching if we are a caching dirserver.
9565 Clip rather than rejecting.
9566 - Fetch cached running-routers from servers that serve it (that is,
9567 authdirservers and servers running 0.0.9rc5-cvs or later.)
9570 - Accept *:706 (silc) in default exit policy.
9571 - Implement new versioning format for post 0.1.
9572 - Support "foo.nickname.exit" addresses, to let Alice request the
9573 address "foo" as viewed by exit node "nickname". Based on a patch
9575 - Make tor --version --version dump the cvs Id of every file.
9578 Changes in version 0.0.9rc4 - 2004-11-28
9579 o Bugfixes on 0.0.8.1:
9580 - Make windows sockets actually non-blocking (oops), and handle
9581 win32 socket errors better.
9583 o Bugfixes on 0.0.9rc1:
9584 - Actually catch the -USR2 signal.
9587 Changes in version 0.0.9rc3 - 2004-11-25
9588 o Bugfixes on 0.0.8.1:
9589 - Flush the log file descriptor after we print "Tor opening log file",
9590 so we don't see those messages days later.
9592 o Bugfixes on 0.0.9rc1:
9593 - Make tor-resolve work again.
9594 - Avoid infinite loop in tor-resolve if tor hangs up on it.
9595 - Fix an assert trigger for clients/servers handling resolves.
9598 Changes in version 0.0.9rc2 - 2004-11-24
9599 o Bugfixes on 0.0.9rc1:
9600 - I broke socks5 support while fixing the eof bug.
9601 - Allow unitless bandwidths and intervals; they default to bytes
9603 - New servers don't start out hibernating; they are active until
9604 they run out of bytes, so they have a better estimate of how
9605 long it takes, and so their operators can know they're working.
9608 Changes in version 0.0.9rc1 - 2004-11-23
9609 o Bugfixes on 0.0.8.1:
9610 - Finally fix a bug that's been plaguing us for a year:
9611 With high load, circuit package window was reaching 0. Whenever
9612 we got a circuit-level sendme, we were reading a lot on each
9613 socket, but only writing out a bit. So we would eventually reach
9614 eof. This would be noticed and acted on even when there were still
9615 bytes sitting in the inbuf.
9616 - When poll() is interrupted, we shouldn't believe the revents values.
9618 o Bugfixes on 0.0.9pre6:
9619 - Fix hibernate bug that caused pre6 to be broken.
9620 - Don't keep rephist info for routers that haven't had activity for
9621 24 hours. (This matters now that clients have keys, since we track
9623 - Never call close_temp_logs while validating log options.
9624 - Fix backslash-escaping on tor.sh.in and torctl.in.
9627 - Implement weekly/monthly/daily accounting: now you specify your
9628 hibernation properties by
9629 AccountingMax N bytes|KB|MB|GB|TB
9630 AccountingStart day|week|month [day] HH:MM
9631 Defaults to "month 1 0:00".
9632 - Let bandwidth and interval config options be specified as 5 bytes,
9633 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
9634 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
9635 get back to normal.)
9636 - If your requested entry or exit node has advertised bandwidth 0,
9638 - Be more greedy about filling up relay cells -- we try reading again
9639 once we've processed the stuff we read, in case enough has arrived
9640 to fill the last cell completely.
9641 - Apply NT service patch from Osamu Fujino. Still needs more work.
9644 Changes in version 0.0.9pre6 - 2004-11-15
9645 o Bugfixes on 0.0.8.1:
9646 - Fix assert failure on malformed socks4a requests.
9647 - Use identity comparison, not nickname comparison, to choose which
9648 half of circuit-ID-space each side gets to use. This is needed
9649 because sometimes we think of a router as a nickname, and sometimes
9650 as a hex ID, and we can't predict what the other side will do.
9651 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
9652 write() call will fail and we handle it there.
9653 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
9654 and smartlist_len, which are two major profiling offenders.
9656 o Bugfixes on 0.0.9pre5:
9657 - Fix a bug in read_all that was corrupting config files on windows.
9658 - When we're raising the max number of open file descriptors to
9659 'unlimited', don't log that we just raised it to '-1'.
9660 - Include event code with events, as required by control-spec.txt.
9661 - Don't give a fingerprint when clients do --list-fingerprint:
9662 it's misleading, because it will never be the same again.
9663 - Stop using strlcpy in tor_strndup, since it was slowing us
9665 - Remove warn on startup about missing cached-directory file.
9666 - Make kill -USR1 work again.
9667 - Hibernate if we start tor during the "wait for wakeup-time" phase
9668 of an accounting interval. Log our hibernation plans better.
9669 - Authoritative dirservers now also cache their directory, so they
9670 have it on start-up.
9673 - Fetch running-routers; cache running-routers; compress
9674 running-routers; serve compressed running-routers.z
9675 - Add NSI installer script contributed by J Doe.
9676 - Commit VC6 and VC7 workspace/project files.
9677 - Commit a tor.spec for making RPM files, with help from jbash.
9678 - Add contrib/torctl.in contributed by Glenn Fink.
9679 - Implement the control-spec's SAVECONF command, to write your
9680 configuration to torrc.
9681 - Get cookie authentication for the controller closer to working.
9682 - Include control-spec.txt in the tarball.
9683 - When set_conf changes our server descriptor, upload a new copy.
9684 But don't upload it too often if there are frequent changes.
9685 - Document authentication config in man page, and document signals
9687 - Clean up confusing parts of man page and torrc.sample.
9688 - Make expand_filename handle ~ and ~username.
9689 - Use autoconf to enable largefile support where necessary. Use
9690 ftello where available, since ftell can fail at 2GB.
9691 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
9692 log more informatively.
9693 - Give a slightly more useful output for "tor -h".
9694 - Refuse application socks connections to port 0.
9695 - Check clock skew for verified servers, but allow unverified
9696 servers and clients to have any clock skew.
9697 - Break DirFetchPostPeriod into:
9698 - DirFetchPeriod for fetching full directory,
9699 - StatusFetchPeriod for fetching running-routers,
9700 - DirPostPeriod for posting server descriptor,
9701 - RendPostPeriod for posting hidden service descriptors.
9702 - Make sure the hidden service descriptors are at a random offset
9703 from each other, to hinder linkability.
9706 Changes in version 0.0.9pre5 - 2004-11-09
9707 o Bugfixes on 0.0.9pre4:
9708 - Fix a seg fault in unit tests (doesn't affect main program).
9709 - Fix an assert bug where a hidden service provider would fail if
9710 the first hop of his rendezvous circuit was down.
9711 - Hidden service operators now correctly handle version 1 style
9712 INTRODUCE1 cells (nobody generates them still, so not a critical
9714 - If do_hup fails, actually notice.
9715 - Handle more errnos from accept() without closing the listener.
9716 Some OpenBSD machines were closing their listeners because
9717 they ran out of file descriptors.
9718 - Send resolve cells to exit routers that are running a new
9719 enough version of the resolve code to work right.
9720 - Better handling of winsock includes on non-MSV win32 compilers.
9721 - Some people had wrapped their tor client/server in a script
9722 that would restart it whenever it died. This did not play well
9723 with our "shut down if your version is obsolete" code. Now people
9724 don't fetch a new directory if their local cached version is
9726 - Make our autogen.sh work on ksh as well as bash.
9729 - Hibernation: New config option "AccountingMaxKB" lets you
9730 set how many KBytes per month you want to allow your server to
9731 consume. Rather than spreading those bytes out evenly over the
9732 month, we instead hibernate for some of the month and pop up
9733 at a deterministic time, work until the bytes are consumed, then
9734 hibernate again. Config option "MonthlyAccountingStart" lets you
9735 specify which day of the month your billing cycle starts on.
9736 - Control interface: a separate program can now talk to your
9737 client/server over a socket, and get/set config options, receive
9738 notifications of circuits and streams starting/finishing/dying,
9739 bandwidth used, etc. The next step is to get some GUIs working.
9740 Let us know if you want to help out. See doc/control-spec.txt .
9741 - Ship a contrib/tor-control.py as an example script to interact
9742 with the control port.
9743 - "tor --hash-password zzyxz" will output a salted password for
9744 use in authenticating to the control interface.
9745 - New log format in config:
9746 "Log minsev[-maxsev] stdout|stderr|syslog" or
9747 "Log minsev[-maxsev] file /var/foo"
9750 - DirPolicy config option, to let people reject incoming addresses
9751 from their dirserver.
9752 - "tor --list-fingerprint" will list your identity key fingerprint
9754 - Add "pass" target for RedirectExit, to make it easier to break
9755 out of a sequence of RedirectExit rules.
9756 - Clients now generate a TLS cert too, in preparation for having
9757 them act more like real nodes.
9758 - Ship src/win32/ in the tarball, so people can use it to build.
9759 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
9761 - New "router-status" line in directory, to better bind each verified
9762 nickname to its identity key.
9763 - Deprecate unofficial config option abbreviations, and abbreviations
9764 not on the command line.
9765 - Add a pure-C tor-resolve implementation.
9766 - Use getrlimit and friends to ensure we can reach MaxConn (currently
9767 1024) file descriptors.
9769 o Code security improvements, inspired by Ilja:
9770 - Replace sprintf with snprintf. (I think they were all safe, but
9772 - Replace strcpy/strncpy with strlcpy in more places.
9773 - Avoid strcat; use snprintf or strlcat instead.
9774 - snprintf wrapper with consistent (though not C99) overflow behavior.
9777 Changes in version 0.0.9pre4 - 2004-10-17
9778 o Bugfixes on 0.0.9pre3:
9779 - If the server doesn't specify an exit policy, use the real default
9780 exit policy, not reject *:*.
9781 - Ignore fascistfirewall when uploading/downloading hidden service
9782 descriptors, since we go through Tor for those; and when using
9783 an HttpProxy, since we assume it can reach them all.
9784 - When looking for an authoritative dirserver, use only the ones
9785 configured at boot. Don't bother looking in the directory.
9786 - The rest of the fix for get_default_conf_file() on older win32.
9787 - Make 'Routerfile' config option obsolete.
9790 - New 'MyFamily nick1,...' config option for a server to
9791 specify other servers that shouldn't be used in the same circuit
9792 with it. Only believed if nick1 also specifies us.
9793 - New 'NodeFamily nick1,nick2,...' config option for a client to
9794 specify nodes that it doesn't want to use in the same circuit.
9795 - New 'Redirectexit pattern address:port' config option for a
9796 server to redirect exit connections, e.g. to a local squid.
9799 Changes in version 0.0.9pre3 - 2004-10-13
9800 o Bugfixes on 0.0.8.1:
9801 - Better torrc example lines for dirbindaddress and orbindaddress.
9802 - Improved bounds checking on parsed ints (e.g. config options and
9803 the ones we find in directories.)
9804 - Better handling of size_t vs int, so we're more robust on 64
9806 - Fix the rest of the bug where a newly started OR would appear
9807 as unverified even after we've added his fingerprint and hupped
9809 - Fix a bug from 0.0.7: when read() failed on a stream, we would
9810 close it without sending back an end. So 'connection refused'
9811 would simply be ignored and the user would get no response.
9813 o Bugfixes on 0.0.9pre2:
9814 - Serving the cached-on-disk directory to people is bad. We now
9815 provide no directory until we've fetched a fresh one.
9816 - Workaround for bug on windows where cached-directories get crlf
9818 - Make get_default_conf_file() work on older windows too.
9819 - If we write a *:* exit policy line in the descriptor, don't write
9820 any more exit policy lines.
9823 - Use only 0.0.9pre1 and later servers for resolve cells.
9824 - Make the dirservers file obsolete.
9825 - Include a dir-signing-key token in directories to tell the
9826 parsing entity which key is being used to sign.
9827 - Remove the built-in bulky default dirservers string.
9828 - New config option "Dirserver %s:%d [fingerprint]", which can be
9829 repeated as many times as needed. If no dirservers specified,
9830 default to moria1,moria2,tor26.
9831 - Make moria2 advertise a dirport of 80, so people behind firewalls
9832 will be able to get a directory.
9833 - Http proxy support
9834 - Dirservers translate requests for http://%s:%d/x to /x
9835 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
9836 be routed through this host.
9837 - Clients ask for /tor/x rather than /x for new enough dirservers.
9838 This way we can one day coexist peacefully with apache.
9839 - Clients specify a "Host: %s%d" http header, to be compatible
9840 with more proxies, and so running squid on an exit node can work.
9843 Changes in version 0.0.8.1 - 2004-10-13
9845 - Fix a seg fault that can be triggered remotely for Tor
9846 clients/servers with an open dirport.
9847 - Fix a rare assert trigger, where routerinfos for entries in
9848 our cpath would expire while we're building the path.
9849 - Fix a bug in OutboundBindAddress so it (hopefully) works.
9850 - Fix a rare seg fault for people running hidden services on
9851 intermittent connections.
9852 - Fix a bug in parsing opt keywords with objects.
9853 - Fix a stale pointer assert bug when a stream detaches and
9855 - Fix a string format vulnerability (probably not exploitable)
9856 in reporting stats locally.
9857 - Fix an assert trigger: sometimes launching circuits can fail
9858 immediately, e.g. because too many circuits have failed recently.
9859 - Fix a compile warning on 64 bit platforms.
9862 Changes in version 0.0.9pre2 - 2004-10-03
9864 - Make fetching a cached directory work for 64-bit platforms too.
9865 - Make zlib.h a required header, not an optional header.
9868 Changes in version 0.0.9pre1 - 2004-10-01
9870 - Stop using separate defaults for no-config-file and
9871 empty-config-file. Now you have to explicitly turn off SocksPort,
9872 if you don't want it open.
9873 - Fix a bug in OutboundBindAddress so it (hopefully) works.
9874 - Improve man page to mention more of the 0.0.8 features.
9875 - Fix a rare seg fault for people running hidden services on
9876 intermittent connections.
9877 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
9879 - Fix more dns related bugs: send back resolve_failed and end cells
9880 more reliably when the resolve fails, rather than closing the
9881 circuit and then trying to send the cell. Also attach dummy resolve
9882 connections to a circuit *before* calling dns_resolve(), to fix
9883 a bug where cached answers would never be sent in RESOLVED cells.
9884 - When we run out of disk space, or other log writing error, don't
9885 crash. Just stop logging to that log and continue.
9886 - We were starting to daemonize before we opened our logs, so if
9887 there were any problems opening logs, we would complain to stderr,
9888 which wouldn't work, and then mysteriously exit.
9889 - Fix a rare bug where sometimes a verified OR would connect to us
9890 before he'd uploaded his descriptor, which would cause us to
9891 assign conn->nickname as though he's unverified. Now we look through
9892 the fingerprint list to see if he's there.
9893 - Fix a rare assert trigger, where routerinfos for entries in
9894 our cpath would expire while we're building the path.
9897 - Clients can ask dirservers for /dir.z to get a compressed version
9898 of the directory. Only works for servers running 0.0.9, of course.
9899 - Make clients cache directories and use them to seed their router
9900 lists at startup. This means clients have a datadir again.
9901 - Configuration infrastructure support for warning on obsolete
9903 - Respond to content-encoding headers by trying to uncompress as
9905 - Reply with a deflated directory when a client asks for "dir.z".
9906 We could use allow-encodings instead, but allow-encodings isn't
9907 specified in HTTP 1.0.
9908 - Raise the max dns workers from 50 to 100.
9909 - Discourage people from setting their dirfetchpostperiod more often
9910 than once per minute.
9911 - Protect dirservers from overzealous descriptor uploading -- wait
9912 10 seconds after directory gets dirty, before regenerating.
9915 Changes in version 0.0.8 - 2004-08-25
9916 o Port it to SunOS 5.9 / Athena
9919 Changes in version 0.0.8rc2 - 2004-08-20
9920 o Make it compile on cygwin again.
9921 o When picking unverified routers, skip those with low uptime and/or
9922 low bandwidth, depending on what properties you care about.
9925 Changes in version 0.0.8rc1 - 2004-08-18
9926 o Changes from 0.0.7.3:
9928 - Fix assert triggers: if the other side returns an address 0.0.0.0,
9929 don't put it into the client dns cache.
9930 - If a begin failed due to exit policy, but we believe the IP address
9931 should have been allowed, switch that router to exitpolicy reject *:*
9932 until we get our next directory.
9934 - Clients choose nodes proportional to advertised bandwidth.
9935 - Avoid using nodes with low uptime as introduction points.
9936 - Handle servers with dynamic IP addresses: don't replace
9937 options->Address with the resolved one at startup, and
9938 detect our address right before we make a routerinfo each time.
9939 - 'FascistFirewall' option to pick dirservers and ORs on specific
9940 ports; plus 'FirewallPorts' config option to tell FascistFirewall
9941 which ports are open. (Defaults to 80,443)
9942 - Be more aggressive about trying to make circuits when the network
9943 has changed (e.g. when you unsuspend your laptop).
9944 - Check for time skew on http headers; report date in response to
9946 - If the entrynode config line has only one node, don't pick it as
9948 - Add strict{entry|exit}nodes config options. If set to 1, then
9949 we refuse to build circuits that don't include the specified entry
9951 - OutboundBindAddress config option, to bind to a specific
9952 IP address for outgoing connect()s.
9953 - End truncated log entries (e.g. directories) with "[truncated]".
9955 o Patches to 0.0.8preX:
9957 - Patches to compile and run on win32 again (maybe)?
9958 - Fix crash when looking for ~/.torrc with no $HOME set.
9959 - Fix a race bug in the unit tests.
9960 - Handle verified/unverified name collisions better when new
9961 routerinfo's arrive in a directory.
9962 - Sometimes routers were getting entered into the stats before
9963 we'd assigned their identity_digest. Oops.
9964 - Only pick and establish intro points after we've gotten a
9967 - AllowUnverifiedNodes config option to let circuits choose no-name
9968 routers in entry,middle,exit,introduction,rendezvous positions.
9969 Allow middle and rendezvous positions by default.
9970 - Add a man page for tor-resolve.
9973 Changes in version 0.0.7.3 - 2004-08-12
9974 o Stop dnsworkers from triggering an assert failure when you
9975 ask them to resolve the host "".
9978 Changes in version 0.0.8pre3 - 2004-08-09
9979 o Changes from 0.0.7.2:
9980 - Allow multiple ORs with same nickname in routerlist -- now when
9981 people give us one identity key for a nickname, then later
9982 another, we don't constantly complain until the first expires.
9983 - Remember used bandwidth (both in and out), and publish 15-minute
9984 snapshots for the past day into our descriptor.
9985 - You can now fetch $DIRURL/running-routers to get just the
9986 running-routers line, not the whole descriptor list. (But
9987 clients don't use this yet.)
9988 - When people mistakenly use Tor as an http proxy, point them
9989 at the tor-doc.html rather than the INSTALL.
9990 - Remove our mostly unused -- and broken -- hex_encode()
9991 function. Use base16_encode() instead. (Thanks to Timo Lindfors
9992 for pointing out this bug.)
9993 - Rotate onion keys every 12 hours, not every 2 hours, so we have
9994 fewer problems with people using the wrong key.
9995 - Change the default exit policy to reject the default edonkey,
9996 kazaa, gnutella ports.
9997 - Add replace_file() to util.[ch] to handle win32's rename().
9999 o Changes from 0.0.8preX:
10000 - Fix two bugs in saving onion keys to disk when rotating, so
10001 hopefully we'll get fewer people using old onion keys.
10002 - Fix an assert error that was making SocksPolicy not work.
10003 - Be willing to expire routers that have an open dirport -- it's
10004 just the authoritative dirservers we want to not forget.
10005 - Reject tor-resolve requests for .onion addresses early, so we
10006 don't build a whole rendezvous circuit and then fail.
10007 - When you're warning a server that he's unverified, don't cry
10008 wolf unpredictably.
10009 - Fix a race condition: don't try to extend onto a connection
10010 that's still handshaking.
10011 - For servers in clique mode, require the conn to be open before
10012 you'll choose it for your path.
10013 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
10014 end relay cell, etc.
10015 - Measure bandwidth capacity over the last 24 hours, not just 12
10016 - Bugfix: authoritative dirservers were making and signing a new
10017 directory for each client, rather than reusing the cached one.
10020 Changes in version 0.0.8pre2 - 2004-08-04
10021 o Changes from 0.0.7.2:
10023 - Check directory signature _before_ you decide whether you're
10024 you're running an obsolete version and should exit.
10025 - Check directory signature _before_ you parse the running-routers
10026 list to decide who's running or verified.
10027 - Bugfixes and features:
10028 - Check return value of fclose while writing to disk, so we don't
10029 end up with broken files when servers run out of disk space.
10030 - Log a warning if the user uses an unsafe socks variant, so people
10031 are more likely to learn about privoxy or socat.
10032 - Dirservers now include RFC1123-style dates in the HTTP headers,
10033 which one day we will use to better detect clock skew.
10035 o Changes from 0.0.8pre1:
10036 - Make it compile without warnings again on win32.
10037 - Log a warning if you're running an unverified server, to let you
10038 know you might want to get it verified.
10039 - Only pick a default nickname if you plan to be a server.
10042 Changes in version 0.0.8pre1 - 2004-07-23
10044 - Made our unit tests compile again on OpenBSD 3.5, and tor
10045 itself compile again on OpenBSD on a sparc64.
10046 - We were neglecting milliseconds when logging on win32, so
10047 everything appeared to happen at the beginning of each second.
10049 o Protocol changes:
10050 - 'Extend' relay cell payloads now include the digest of the
10051 intended next hop's identity key. Now we can verify that we're
10052 extending to the right router, and also extend to routers we
10053 hadn't heard of before.
10056 - Tor nodes can now act as relays (with an advertised ORPort)
10057 without being manually verified by the dirserver operators.
10058 - Uploaded descriptors of unverified routers are now accepted
10059 by the dirservers, and included in the directory.
10060 - Verified routers are listed by nickname in the running-routers
10061 list; unverified routers are listed as "$<fingerprint>".
10062 - We now use hash-of-identity-key in most places rather than
10063 nickname or addr:port, for improved security/flexibility.
10064 - To avoid Sybil attacks, paths still use only verified servers.
10065 But now we have a chance to play around with hybrid approaches.
10066 - Nodes track bandwidth usage to estimate capacity (not used yet).
10067 - ClientOnly option for nodes that never want to become servers.
10068 - Directory caching.
10069 - "AuthoritativeDir 1" option for the official dirservers.
10070 - Now other nodes (clients and servers) will cache the latest
10071 directory they've pulled down.
10072 - They can enable their DirPort to serve it to others.
10073 - Clients will pull down a directory from any node with an open
10074 DirPort, and check the signature/timestamp correctly.
10075 - Authoritative dirservers now fetch directories from other
10076 authdirservers, to stay better synced.
10077 - Running-routers list tells who's down also, along with noting
10078 if they're verified (listed by nickname) or unverified (listed
10080 - Allow dirservers to serve running-router list separately.
10081 This isn't used yet.
10082 - ORs connect-on-demand to other ORs
10083 - If you get an extend cell to an OR you're not connected to,
10084 connect, handshake, and forward the create cell.
10085 - The authoritative dirservers stay connected to everybody,
10086 and everybody stays connected to 0.0.7 servers, but otherwise
10087 clients/servers expire unused connections after 5 minutes.
10088 - When servers get a sigint, they delay 30 seconds (refusing new
10089 connections) then exit. A second sigint causes immediate exit.
10090 - File and name management:
10091 - Look for .torrc if no CONFDIR "torrc" is found.
10092 - If no datadir is defined, then choose, make, and secure ~/.tor
10094 - If torrc not found, exitpolicy reject *:*.
10095 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
10096 - If no nickname is defined, derive default from hostname.
10097 - Rename secret key files, e.g. identity.key -> secret_id_key,
10098 to discourage people from mailing their identity key to tor-ops.
10099 - Refuse to build a circuit before the directory has arrived --
10100 it won't work anyway, since you won't know the right onion keys
10102 - Try other dirservers immediately if the one you try is down. This
10103 should tolerate down dirservers better now.
10104 - Parse tor version numbers so we can do an is-newer-than check
10105 rather than an is-in-the-list check.
10106 - New socks command 'resolve', to let us shim gethostbyname()
10108 - A 'tor_resolve' script to access the socks resolve functionality.
10109 - A new socks-extensions.txt doc file to describe our
10110 interpretation and extensions to the socks protocols.
10111 - Add a ContactInfo option, which gets published in descriptor.
10112 - Publish OR uptime in descriptor (and thus in directory) too.
10113 - Write tor version at the top of each log file
10114 - New docs in the tarball:
10116 - Document that you should proxy your SSL traffic too.
10119 Changes in version 0.0.7.2 - 2004-07-07
10120 o A better fix for the 0.0.0.0 problem, that will hopefully
10121 eliminate the remaining related assertion failures.
10124 Changes in version 0.0.7.1 - 2004-07-04
10125 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
10126 since internally we use 0.0.0.0 to signify "not yet resolved".
10129 Changes in version 0.0.7 - 2004-06-07
10130 o Updated the man page to reflect the new features.
10133 Changes in version 0.0.7rc2 - 2004-06-06
10134 o Changes from 0.0.7rc1:
10135 - Make it build on Win32 again.
10136 o Changes from 0.0.6.2:
10137 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
10141 Changes in version 0.0.7rc1 - 2004-06-02
10143 - On sighup, we were adding another log without removing the first
10144 one. So log messages would get duplicated n times for n sighups.
10145 - Several cases of using a connection after we'd freed it. The
10146 problem was that connections that are pending resolve are in both
10147 the pending_resolve tree, and also the circuit's resolving_streams
10148 list. When you want to remove one, you must remove it from both.
10149 - Fix a double-mark-for-close where an end cell arrived for a
10150 resolving stream, and then the resolve failed.
10151 - Check directory signatures based on name of signer, not on whom
10152 we got the directory from. This will let us cache directories more
10155 - Crank up some of our constants to handle more users.
10158 Changes in version 0.0.7pre1 - 2004-06-02
10159 o Fixes for crashes and other obnoxious bugs:
10160 - Fix an epipe bug: sometimes when directory connections failed
10161 to connect, we would give them a chance to flush before closing
10163 - When we detached from a circuit because of resolvefailed, we
10164 would immediately try the same circuit twice more, and then
10165 give up on the resolve thinking we'd tried three different
10167 - Limit the number of intro circuits we'll attempt to build for a
10168 hidden service per 15-minute period.
10169 - Check recommended-software string *early*, before actually parsing
10170 the directory. Thus we can detect an obsolete version and exit,
10171 even if the new directory format doesn't parse.
10172 o Fixes for security bugs:
10173 - Remember which nodes are dirservers when you startup, and if a
10174 random OR enables his dirport, don't automatically assume he's
10175 a trusted dirserver.
10177 - Directory connections were asking the wrong poll socket to
10178 start writing, and not asking themselves to start writing.
10179 - When we detached from a circuit because we sent a begin but
10180 didn't get a connected, we would use it again the first time;
10181 but after that we would correctly switch to a different one.
10182 - Stop warning when the first onion decrypt attempt fails; they
10183 will sometimes legitimately fail now that we rotate keys.
10184 - Override unaligned-access-ok check when $host_cpu is ia64 or
10185 arm. Apparently they allow it but the kernel whines.
10186 - Dirservers try to reconnect periodically too, in case connections
10188 - Fix some memory leaks in directory servers.
10189 - Allow backslash in Win32 filenames.
10190 - Made Tor build complain-free on FreeBSD, hopefully without
10191 breaking other BSD builds. We'll see.
10193 - Doxygen markup on all functions and global variables.
10194 - Make directory functions update routerlist, not replace it. So
10195 now directory disagreements are not so critical a problem.
10196 - Remove the upper limit on number of descriptors in a dirserver's
10197 directory (not that we were anywhere close).
10198 - Allow multiple logfiles at different severity ranges.
10199 - Allow *BindAddress to specify ":port" rather than setting *Port
10200 separately. Allow multiple instances of each BindAddress config
10201 option, so you can bind to multiple interfaces if you want.
10202 - Allow multiple exit policy lines, which are processed in order.
10203 Now we don't need that huge line with all the commas in it.
10204 - Enable accept/reject policies on SOCKS connections, so you can bind
10205 to 0.0.0.0 but still control who can use your OP.
10208 Changes in version 0.0.6.2 - 2004-05-16
10209 o Our integrity-checking digest was checking only the most recent cell,
10210 not the previous cells like we'd thought.
10211 Thanks to Stefan Mark for finding the flaw!
10214 Changes in version 0.0.6.1 - 2004-05-06
10215 o Fix two bugs in our AES counter-mode implementation (this affected
10216 onion-level stream encryption, but not TLS-level). It turns
10217 out we were doing something much more akin to a 16-character
10218 polyalphabetic cipher. Oops.
10219 Thanks to Stefan Mark for finding the flaw!
10220 o Retire moria3 as a directory server, and add tor26 as a directory
10224 Changes in version 0.0.6 - 2004-05-02
10225 [version bump only]
10228 Changes in version 0.0.6rc4 - 2004-05-01
10229 o Update the built-in dirservers list to use the new directory format
10230 o Fix a rare seg fault: if a node offering a hidden service attempts
10231 to build a circuit to Alice's rendezvous point and fails before it
10232 reaches the last hop, it retries with a different circuit, but
10234 o Handle windows socket errors correctly.
10237 Changes in version 0.0.6rc3 - 2004-04-28
10238 o Don't expire non-general excess circuits (if we had enough
10239 circuits open, we were expiring rendezvous circuits -- even
10240 when they had a stream attached. oops.)
10241 o Fetch randomness from /dev/urandom better (not via fopen/fread)
10242 o Better debugging for tls errors
10243 o Some versions of openssl have an SSL_pending function that erroneously
10244 returns bytes when there is a non-application record pending.
10245 o Set Content-Type on the directory and hidserv descriptor.
10246 o Remove IVs from cipher code, since AES-ctr has none.
10247 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
10248 o We were using an array of length zero in a few places.
10249 o win32's gethostbyname can't resolve an IP to an IP.
10250 o win32's close can't close a socket.
10253 Changes in version 0.0.6rc2 - 2004-04-26
10254 o Fix a bug where we were closing tls connections intermittently.
10255 It turns out openssl keeps its errors around -- so if an error
10256 happens, and you don't ask about it, and then another openssl
10257 operation happens and succeeds, and you ask if there was an error,
10258 it tells you about the first error. Fun fun.
10259 o Fix a bug that's been lurking since 27 may 03 (!)
10260 When passing back a destroy cell, we would use the wrong circ id.
10261 'Mostly harmless', but still worth fixing.
10262 o Since we don't support truncateds much, don't bother sending them;
10263 just close the circ.
10264 o check for <machine/limits.h> so we build on NetBSD again (I hope).
10265 o don't crash if a conn that sent a begin has suddenly lost its circuit
10266 (this was quite rare).
10269 Changes in version 0.0.6rc1 - 2004-04-25
10270 o We now rotate link (tls context) keys and onion keys.
10271 o CREATE cells now include oaep padding, so you can tell
10272 if you decrypted them correctly.
10273 o Add bandwidthburst to server descriptor.
10274 o Directories now say which dirserver signed them.
10275 o Use a tor_assert macro that logs failed assertions too.
10278 Changes in version 0.0.6pre5 - 2004-04-18
10279 o changes from 0.0.6pre4:
10280 - make tor build on broken freebsd 5.2 installs
10281 - fix a failed assert when you try an intro point, get a nack, and try
10282 a second one and it works.
10283 - when alice uses a port that the hidden service doesn't accept,
10284 it now sends back an end cell (denied by exit policy). otherwise
10285 alice would just have to wait to time out.
10286 - fix another rare bug: when we had tried all the intro
10287 points for a hidden service, we fetched the descriptor
10288 again, but we left our introcirc thinking it had already
10289 sent an intro, so it kept waiting for a response...
10290 - bugfix: when you sleep your hidden-service laptop, as soon
10291 as it wakes up it tries to upload a service descriptor, but
10292 socketpair fails for some reason (localhost not up yet?).
10293 now we simply give up on that upload, and we'll try again later.
10294 i'd still like to find the bug though.
10295 - if an intro circ waiting for an ack dies before getting one, then
10297 - we were reusing stale service descriptors and refetching usable
10301 Changes in version 0.0.6pre4 - 2004-04-14
10302 o changes from 0.0.6pre3:
10303 - when bob fails to connect to the rendezvous point, and his
10304 circ didn't fail because of the rendezvous point itself, then
10305 he retries a couple of times
10306 - we expire introduction and rendezvous circs more thoroughly
10307 (sometimes they were hanging around forever)
10308 - we expire unattached rendezvous streams that have been around
10309 too long (they were sticking around forever).
10310 - fix a measly fencepost error that was crashing everybody with
10314 Changes in version 0.0.6pre3 - 2004-04-14
10315 o changes from 0.0.6pre2:
10316 - make hup work again
10317 - fix some memory leaks for dirservers
10318 - allow more skew in rendezvous descriptor timestamps, to help
10319 handle people like blanu who don't know what time it is
10320 - normal circs are 3 hops, but some rend/intro circs are 4, if
10321 the initiator doesn't get to choose the last hop
10322 - send acks for introductions, so alice can know whether to try
10324 - bob publishes intro points more correctly
10325 o changes from 0.0.5:
10326 - fix an assert trigger that's been plaguing us since the days
10327 of 0.0.2prexx (thanks weasel!)
10328 - retry stream correctly when we fail to connect because of
10329 exit-policy-reject (should try another) or can't-resolve-address
10330 (also should try another, because dns on random internet servers
10332 - when we hup a dirserver and we've *removed* a server from the
10333 approved-routers list, now we remove that server from the
10334 in-memory directories too
10337 Changes in version 0.0.6pre2 - 2004-04-08
10338 o We fixed our base32 implementation. Now it works on all architectures.
10341 Changes in version 0.0.6pre1 - 2004-04-08
10343 - Hidden services and rendezvous points are implemented. Go to
10344 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
10345 hidden services. (This only works via a socks4a proxy such as
10346 Privoxy, and currently it's quite slow.)
10349 Changes in version 0.0.5 - 2004-03-30
10350 [version bump only]
10353 Changes in version 0.0.5rc3 - 2004-03-29
10354 o Install torrc as torrc.sample -- we no longer clobber your
10356 o Re-enable recommendedversion checking (we broke it in rc2, oops)
10357 o Add in a 'notice' log level for things the operator should hear
10358 but that aren't warnings
10361 Changes in version 0.0.5rc2 - 2004-03-29
10362 o Hold socks connection open until reply is flushed (if possible)
10363 o Make exit nodes resolve IPs to IPs immediately, rather than asking
10364 the dns farm to do it.
10365 o Fix c99 aliasing warnings in rephist.c
10366 o Don't include server descriptors that are older than 24 hours in the
10368 o Give socks 'reject' replies their whole 15s to attempt to flush,
10369 rather than seeing the 60s timeout and assuming the flush had failed.
10370 o Clean automake droppings from the cvs repository
10373 Changes in version 0.0.5rc1 - 2004-03-28
10374 o Fix mangled-state bug in directory fetching (was causing sigpipes).
10375 o Only build circuits after we've fetched the directory: clients were
10376 using only the directory servers before they'd fetched a directory.
10377 This also means longer startup time; so it goes.
10378 o Fix an assert trigger where an OP would fail to handshake, and we'd
10379 expect it to have a nickname.
10380 o Work around a tsocks bug: do a socks reject when AP connection dies
10381 early, else tsocks goes into an infinite loop.
10384 Changes in version 0.0.4 - 2004-03-26
10385 o When connecting to a dirserver or OR and the network is down,
10389 Changes in version 0.0.3 - 2004-03-26
10390 o Warn and fail if server chose a nickname with illegal characters
10391 o Port to Solaris and Sparc:
10392 - include missing header fcntl.h
10393 - have autoconf find -lsocket -lnsl automatically
10394 - deal with hardware word alignment
10395 - make uname() work (solaris has a different return convention)
10396 - switch from using signal() to sigaction()
10397 o Preliminary work on reputation system:
10398 - Keep statistics on success/fail of connect attempts; they're published
10399 by kill -USR1 currently.
10400 - Add a RunTesting option to try to learn link state by creating test
10401 circuits, even when SocksPort is off.
10402 - Remove unused open circuits when there are too many.
10405 Changes in version 0.0.2 - 2004-03-19
10406 - Include strlcpy and strlcat for safer string ops
10407 - define INADDR_NONE so we compile (but still not run) on solaris
10410 Changes in version 0.0.2pre27 - 2004-03-14
10412 - Allow internal tor networks (we were rejecting internal IPs,
10413 now we allow them if they're set explicitly).
10414 - And fix a few endian issues.
10417 Changes in version 0.0.2pre26 - 2004-03-14
10419 - If a stream times out after 15s without a connected cell, don't
10420 try that circuit again: try a new one.
10421 - Retry streams at most 4 times. Then give up.
10422 - When a dirserver gets a descriptor from an unknown router, it
10423 logs its fingerprint (so the dirserver operator can choose to
10424 accept it even without mail from the server operator).
10425 - Inform unapproved servers when we reject their descriptors.
10426 - Make tor build on Windows again. It works as a client, who knows
10428 - Clearer instructions in the torrc for how to set up a server.
10429 - Be more efficient about reading fd's when our global token bucket
10430 (used for rate limiting) becomes empty.
10432 - Stop asserting that computers always go forward in time. It's
10434 - When we sent a cell (e.g. destroy) and then marked an OR connection
10435 expired, we might close it before finishing a flush if the other
10436 side isn't reading right then.
10437 - Don't allow dirservers to start if they haven't defined
10438 RecommendedVersions
10439 - We were caching transient dns failures. Oops.
10440 - Prevent servers from publishing an internal IP as their address.
10441 - Address a strcat vulnerability in circuit.c
10444 Changes in version 0.0.2pre25 - 2004-03-04
10446 - Put the OR's IP in its router descriptor, not its fqdn. That way
10447 we'll stop being stalled by gethostbyname for nodes with flaky dns,
10450 - If the user typed in an address that didn't resolve, the server
10454 Changes in version 0.0.2pre24 - 2004-03-03
10456 - Fix an assertion failure in dns.c, where we were trying to dequeue
10457 a pending dns resolve even if it wasn't pending
10458 - Fix a spurious socks5 warning about still trying to write after the
10459 connection is finished.
10460 - Hold certain marked_for_close connections open until they're finished
10461 flushing, rather than losing bytes by closing them too early.
10462 - Correctly report the reason for ending a stream
10463 - Remove some duplicate calls to connection_mark_for_close
10464 - Put switch_id and start_daemon earlier in the boot sequence, so it
10465 will actually try to chdir() to options.DataDirectory
10466 - Make 'make test' exit(1) if a test fails; fix some unit tests
10467 - Make tor fail when you use a config option it doesn't know about,
10468 rather than warn and continue.
10469 - Make --version work
10470 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
10473 Changes in version 0.0.2pre23 - 2004-02-29
10475 - Print a statement when the first circ is finished, so the user
10476 knows it's working.
10477 - If a relay cell is unrecognized at the end of the circuit,
10478 send back a destroy. (So attacks to mutate cells are more
10480 - New config option 'excludenodes' to avoid certain nodes for circuits.
10481 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
10482 so you can collect coredumps there.
10484 - Fix a bug in tls flushing where sometimes data got wedged and
10485 didn't flush until more data got sent. Hopefully this bug was
10486 a big factor in the random delays we were seeing.
10487 - Make 'connected' cells include the resolved IP, so the client
10488 dns cache actually gets populated.
10489 - Disallow changing from ORPort=0 to ORPort>0 on hup.
10490 - When we time-out on a stream and detach from the circuit, send an
10491 end cell down it first.
10492 - Only warn about an unknown router (in exitnodes, entrynodes,
10493 excludenodes) after we've fetched a directory.
10496 Changes in version 0.0.2pre22 - 2004-02-26
10498 - Servers publish less revealing uname information in descriptors.
10499 - More memory tracking and assertions, to crash more usefully when
10501 - If the default torrc isn't there, just use some default defaults.
10502 Plus provide an internal dirservers file if they don't have one.
10503 - When the user tries to use Tor as an http proxy, give them an http
10504 501 failure explaining that we're a socks proxy.
10505 - Dump a new router.desc on hup, to help confused people who change
10506 their exit policies and then wonder why router.desc doesn't reflect
10508 - Clean up the generic tor.sh init script that we ship with.
10510 - If the exit stream is pending on the resolve, and a destroy arrives,
10511 then the stream wasn't getting removed from the pending list. I
10512 think this was the one causing recent server crashes.
10513 - Use a more robust poll on OSX 10.3, since their poll is flaky.
10514 - When it couldn't resolve any dirservers, it was useless from then on.
10515 Now it reloads the RouterFile (or default dirservers) if it has no
10517 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
10518 many users don't even *have* a /usr/local/sbin/.
10521 Changes in version 0.0.2pre21 - 2004-02-18
10523 - There's a ChangeLog file that actually reflects the changelog.
10524 - There's a 'torify' wrapper script, with an accompanying
10525 tor-tsocks.conf, that simplifies the process of using tsocks for
10526 tor. It even has a man page.
10527 - The tor binary gets installed to sbin rather than bin now.
10528 - Retry streams where the connected cell hasn't arrived in 15 seconds
10529 - Clean up exit policy handling -- get the default out of the torrc,
10530 so we can update it without forcing each server operator to fix
10532 - Allow imaps and pop3s in default exit policy
10534 - Prevent picking middleman nodes as the last node in the circuit
10537 Changes in version 0.0.2pre20 - 2004-01-30
10539 - We now have a deb package, and it's in debian unstable. Go to
10540 it, apt-getters. :)
10541 - I've split the TotalBandwidth option into BandwidthRate (how many
10542 bytes per second you want to allow, long-term) and
10543 BandwidthBurst (how many bytes you will allow at once before the cap
10544 kicks in). This better token bucket approach lets you, say, set
10545 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
10546 performance while not exceeding your monthly bandwidth quota.
10547 - Push out a tls record's worth of data once you've got it, rather
10548 than waiting until you've read everything waiting to be read. This
10549 may improve performance by pipelining better. We'll see.
10550 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
10551 from failed circuits (if they haven't been connected yet) and attach
10553 - Expire old streams that haven't managed to connect. Some day we'll
10554 have them reattach to new circuits instead.
10557 - Fix several memory leaks that were causing servers to become bloated
10559 - Fix a few very rare assert triggers. A few more remain.
10560 - Setuid to User _before_ complaining about running as root.
10563 Changes in version 0.0.2pre19 - 2004-01-07
10565 - Fix deadlock condition in dns farm. We were telling a child to die by
10566 closing the parent's file descriptor to him. But newer children were
10567 inheriting the open file descriptor from the parent, and since they
10568 weren't closing it, the socket never closed, so the child never read
10569 eof, so he never knew to exit. Similarly, dns workers were holding
10570 open other sockets, leading to all sorts of chaos.
10571 - New cleaner daemon() code for forking and backgrounding.
10572 - If you log to a file, it now prints an entry at the top of the
10573 logfile so you know it's working.
10574 - The onionskin challenge length was 30 bytes longer than necessary.
10575 - Started to patch up the spec so it's not quite so out of date.
10578 Changes in version 0.0.2pre18 - 2004-01-02
10580 - Fix endian issues with the 'integrity' field in the relay header.
10581 - Fix a potential bug where connections in state
10582 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
10585 Changes in version 0.0.2pre17 - 2003-12-30
10587 - Made --debuglogfile (or any second log file, actually) work.
10588 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
10589 adversary could force us into an infinite loop.
10592 - Each onionskin handshake now includes a hash of the computed key,
10593 to prove the server's identity and help perfect forward secrecy.
10594 - Changed cell size from 256 to 512 bytes (working toward compatibility
10596 - Changed cell length to 2 bytes, and moved it to the relay header.
10597 - Implemented end-to-end integrity checking for the payloads of
10599 - Separated streamid from 'recognized' (otherwise circuits will get
10600 messed up when we try to have streams exit from the middle). We
10601 use the integrity-checking to confirm that a cell is addressed to
10603 - Randomize the initial circid and streamid values, so an adversary who
10604 breaks into a node can't learn how many circuits or streams have
10608 Changes in version 0.0.2pre16 - 2003-12-14
10610 - Fixed a bug that made HUP trigger an assert
10611 - Fixed a bug where a circuit that immediately failed wasn't being
10612 counted as a failed circuit in counting retries.
10615 - Now we close the circuit when we get a truncated cell: otherwise we're
10616 open to an anonymity attack where a bad node in the path truncates
10617 the circuit and then we open streams at him.
10618 - Add port ranges to exit policies
10619 - Add a conservative default exit policy
10620 - Warn if you're running tor as root
10621 - on HUP, retry OR connections and close/rebind listeners
10622 - options.EntryNodes: try these nodes first when picking the first node
10623 - options.ExitNodes: if your best choices happen to include any of
10624 your preferred exit nodes, you choose among just those preferred
10626 - options.ExcludedNodes: nodes that are never picked in path building
10629 Changes in version 0.0.2pre15 - 2003-12-03
10630 o Robustness and bugfixes:
10631 - Sometimes clients would cache incorrect DNS resolves, which would
10632 really screw things up.
10633 - An OP that goes offline would slowly leak all its sockets and stop
10635 - A wide variety of bugfixes in exit node selection, exit policy
10636 handling, and processing pending streams when a new circuit is
10638 - Pick nodes for a path only from those the directory says are up
10639 - Choose randomly from all running dirservers, not always the first one
10640 - Increase allowed http header size for directory fetch.
10641 - Stop writing to stderr (if we're daemonized it will be closed).
10642 - Enable -g always, so cores will be more useful to me.
10643 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
10646 - Wrote a man page. It lists commonly used options.
10649 - Change default loglevel to warn.
10650 - Make PidFile default to null rather than littering in your CWD.
10651 - OnionRouter config option is now obsolete. Instead it just checks
10653 - Moved to a single unified torrc file for both clients and servers.
10656 Changes in version 0.0.2pre14 - 2003-11-29
10657 o Robustness and bugfixes:
10658 - Force the admin to make the DataDirectory himself
10659 - to get ownership/permissions right
10660 - so clients no longer make a DataDirectory and then never use it
10661 - fix bug where a client who was offline for 45 minutes would never
10662 pull down a directory again
10663 - fix (or at least hide really well) the dns assert bug that was
10664 causing server crashes
10665 - warnings and improved robustness wrt clockskew for certs
10666 - use the native daemon(3) to daemonize, when available
10667 - exit if bind() fails
10668 - exit if neither socksport nor orport is defined
10669 - include our own tor_timegm (Win32 doesn't have its own)
10670 - bugfix for win32 with lots of connections
10671 - fix minor bias in PRNG
10672 - make dirserver more robust to corrupt cached directory
10675 - Wrote the design document (woo)
10677 o Circuit building and exit policies:
10678 - Circuits no longer try to use nodes that the directory has told them
10680 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
10681 bitcounts (18.0.0.0/8).
10682 - Make AP connections standby for a circuit if no suitable circuit
10683 exists, rather than failing
10684 - Circuits choose exit node based on addr/port, exit policies, and
10685 which AP connections are standing by
10686 - Bump min pathlen from 2 to 3
10687 - Relay end cells have a payload to describe why the stream ended.
10688 - If the stream failed because of exit policy, try again with a new
10690 - Clients have a dns cache to remember resolved addresses.
10691 - Notice more quickly when we have no working circuits
10694 - APPort is now called SocksPort
10695 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
10697 - RecommendedVersions is now a config variable rather than
10698 hardcoded (for dirservers)
10699 - Reloads config on HUP
10700 - Usage info on -h or --help
10701 - If you set User and Group config vars, it'll setu/gid to them.
10704 Changes in version 0.0.2pre13 - 2003-10-19
10705 o General stability:
10706 - SSL_write no longer fails when it returns WANTWRITE and the number
10707 of bytes in the buf has changed by the next SSL_write call.
10708 - Fix segfault fetching directory when network is down
10709 - Fix a variety of minor memory leaks
10710 - Dirservers reload the fingerprints file on HUP, so I don't have
10711 to take down the network when I approve a new router
10712 - Default server config file has explicit Address line to specify fqdn
10715 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
10716 - Make listener connections not ever alloc bufs
10718 o Autoconf improvements:
10719 - don't clobber an external CFLAGS in ./configure
10720 - Make install now works
10721 - create var/lib/tor on make install
10722 - autocreate a tor.sh initscript to help distribs
10723 - autocreate the torrc and sample-server-torrc with correct paths
10725 o Log files and Daemonizing now work:
10726 - If --DebugLogFile is specified, log to it at -l debug
10727 - If --LogFile is specified, use it instead of commandline
10728 - If --RunAsDaemon is set, tor forks and backgrounds on startup